DocMerge new template creation
Last updated
Was this helpful?
Last updated
Was this helpful?
After selecting Document Merge Builder from the two options presented, you will be presented with the following Document Merge Builder screen:
AwesomeDocs Builder | Document Merge Builder: The two tabs allow you to switch between maintaining and Kyloe DocMerge templates. NOTE: We recommend using the previous Kyloe AwesomeDocs Builder URL provided. Currently the new AwesomeDocs builder you can access from here is not as functional as the existing builder detailed under the Kyloe AwesomeDocs Builder section above.
Template entity will allow the selection of where the existing templates are associated within Bullhorn. Selecting Candidate, for example, will show all the templates created at the candidate level.
Select template to edit: Once an entity has been selected this drop-down will populate with all the previously-created templates. Selecting one of these will open up that template for editing below.
Create new template opens the DocMerge template editor for a brand-new template. This does not relate to the template entity button (2). It is not necessary to select an entity before clicking this button.
NOTE: Currently there is no way to delete a template once created, but they can be disabled - see (2) under DocMerge Template Details below.
The top section of a DocMerge template contains all the fixed information about the template. This includes where it should appear in Bullhorn and who should have access to it.
The Template name should ideally be unique. It certainly should be unique for the particular entity selected (4).
Enabled needs to be checked to allow the template to be used within Bullhorn. This can be switched on or off as desired. If the Enabled box is unchecked the template will not be available anywhere within the Bullhorn system.
Use Docusign needs to be checked to enable Docusign for the template. If the merged document is to be sent to Docusign then the template must include at least one template part. This template part must then include Docusign functionality otherwise the merged document will fail at Docusign.
The information required in this section relates directly to Docusign.
Entity: This drop-down allows the selection of where the finished template should be accessible in Bullhorn.
Selecting Candidate, for example, will show the template when running DocMerge from the actions menu on a candidate record. This also restricts the related records that can be merged to only those at the candidate level.
Selecting Placement will allow access to many more entries within Bullhorn, but will then need to be generated from a placement record.
If the template entity is set to Job Submission then an additional option of Destination Entity will be shown.
This determines the final location of the stapled file. This default is Candidate but any of the three options can be selected.
File name is where the name of the final, compiled (stapled) file should be entered. When the merge is completed the file will be attached to the selected entity (4) with this file name. Syntax can be added here to bring information from Bullhorn. This syntax should include the whole path to the field, different from Kyloe AwesomeDocs templates. An example of this would be: ${jobSubmission.candidate.name} or ${placement.jobOrder.customText4}
File type: The file type entered here should match an existing file type within Bullhorn. It is not a drop-down list so care should be taken to enter an exact match to an existing type. If the entry here does not match a Bullhorn file type then the newly-created file will not have a Bullhorn file type selected. NOTE: If Docusign is enabled the File name and File type above will not be used as the files are saved back to Bullhorn as individual documents. The File name and File type will be based on the individual template's file name and file type under the output document tab in its configuration and any part individual file's that is to be saved back to Bullhorn once the Merged document is signed in DocuSign.
Triggers: If custom code triggers are required as part of the stapling process then these can be added here.
Private label filter: This drop-down allows the template to be restricted to only those users with a matching private label.
Department filter: This drop-down allows the template to be restricted to only those users with a matching department.
User type: This drop-down allows the template to be restricted to only those users with a matching user type. NOTE: These last three filters (8, 9 & 10) are inclusive. This means it is entirely possible to select a combination where no users can access the template. Only add those filters which are absolutely necessary.
The green plus button will currently be greyed-out. This allows the addition of template parts, which can only be done once the new template has been saved for the first time.
Save will create the new template and allow access to add/ manage the template's file parts.
Save As Copy will only be available once a template has been saved for the first time. Clicking this button will create a new template based on the existing template being displayed.
By default only template parts will be saved back to Bullhorn, if Docusign is enabled. The option "Save to Bullhorn" allows non-template parts to be saved back to Bullhorn too, if checked. If Docusign is enabled then an additional will appear at the bottom of the template details.
