Kyloe Partners | User guides
Nav irem #1
Kyloe Partners | User guides
  • Welcome to Kyloe User Guides
  • Kyloe DataTools
    • Overview
    • Accessing Kyloe DataTools
    • User management
    • DataCleaner
      • Entity selection, search filters and preview
      • Other Search options
      • Date filters
      • Notes filters
      • Search completion options
      • Search running options
      • Report results
      • Things to remember
    • DupliKit
      • DupliKit Dashboard
      • Database sync
      • Reviewing duplicates
      • Master/duplicate selection
      • DupliKit settings
        • DupliKit weighting system
        • DupliKit options
        • Scheduling merges
        • Master identification
      • DupliKit merge history
    • DataRules
      • DataRules dashboard
      • Building a rule: search criteria
      • Building a rule: apply actions
      • Running a rule
      • Schedule a rule to run automatically
      • Rules history
      • Reverting a rule
    • Data management playbook
      • Legacy (Clean up old data)
        • Pinpoint and manage outdated job records
      • Sweeper (Ongoing data quality)
        • Deliver a more personal experience
        • Ensure calls and texts go through smoothly
        • Discover unsearchable candidates in Bullhorn
        • Overcome Bullhorn's default 50% commission split
        • Find and merge duplicate records in Bullhorn
        • Complete and clean up address fields in Bullhorn
        • Manage visibility of files in Bullhorn
      • Gather (Enrich your data)
        • Keep candidate statuses up to date
        • Automatically keep job statuses up to date
        • Keep candidate ‘date available’ up to date
        • Update candidate data to improve your search results
        • Automate assignment credential requirements
        • Automatically assign job priority
        • Copy key info from parent to child companies
        • Auto-assign candidates to recruiters
        • Copy data between entities
        • Auto populate job requirements
  • Kyloe AI Assist
    • Getting started
      • How does Kyloe AI Assist work?
      • Working with AI prompts
      • Understanding Large Language Models (LLMs)
      • Adding the Kyloe AI Assist card to Bullhorn
    • Running Kyloe AI Assist prompts from Bullhorn
      • Choose a prompt
      • Prompt options
      • Result (generated content)
      • Using Bullhorn file attachments
      • Using Bullhorn notes
    • Different Large Language Models (LLMs) for different results
    • Kyloe AI Assist playbook
      • Prompts for Job entity records
      • Prompts for Job Submission records
      • Prompts for Candidate records
      • Prompts for Contact or Company records
      • Kyloe AI Assist & Kyloe DataTools integration
      • Kyloe AI Assist & Kyloe AwesomeDocs integration
  • Kyloe AwesomeDocs
    • Kyloe AwesomeDocs
      • Kyloe AwesomeDocs user guide
        • Accessing Kyloe AwesomeDocs in Bullhorn
        • Create a New document
        • Editing your document with Microsoft Word
        • Editing an existing document
        • Docusign integration
        • Docusign authentication
      • Kyloe AwesomeDocs admin guide
        • Accessing the Kyloe AwesomeDocs template builder
        • The Kyloe AwesomeDocs Template builder
        • Add a new template
        • The template editor
          • Add an HTML section to a template
          • Add file attachment (Formatter type templates)
        • Template configuration
          • Input Template
          • Output Document
          • Attachment Settings (Formatter templates with File attachment section enabled)
          • Recipients (Docusign enabled)
          • Form Fields (Form Fields enabled)
          • Publish (Publish enabled)
          • Docusign (Docusign enabled)
        • Using a Microsoft Word document
          • Mixing Microsoft Word and HTML
          • Add a Merge field in Word
          • Edit a Merge field in Word (Windows only)
          • Highlighting Merge fields in Word
        • Kyloe AwesomeDocs syntax
          • Identifying a Bullhorn field
          • Null-checking
          • Address fields
          • Extra field formatting
          • Docusign placeholders
        • Kyloe Publish
          • Add a new Kyloe Publish Template
          • The Config tabs to consider for Kyloe Publish templates
          • Publish syntax
    • DocMerge
      • DocMerge user guide
        • Accessing Kyloe DocMerge in Bullhorn
        • Candidate document generation
        • DocMerge template parts
        • Staple the DocMerge document
        • Docusign in DocMerge
      • DocMerge admin guide
        • Accessing the DocMerge builder
        • DocMerge new template creation
        • Company filter
        • Docusign details
        • DocMerge template parts
    • Publish
      • Accessing Publish within Bullhorn
      • Create a new Publish document
      • View Published documents
      • Edit a Published document
      • Send Published document and see activity
      • Publish mass mail
  • Kyloe Workflow
    • Kyloe Workflow user guide
      • Update submission
      • Send CV/resume
      • Schedule interview
      • Create placement
      • Notification
    • Kyloe Workflow admin guide
      • Create new configuration (config)
      • Update submission
      • CV send
      • Interview
      • Placement
      • Notification
      • Appointment
      • Creating your email templates
        • Create template
        • Edit template
        • Template HTML
      • Syntax
        • Identifying a Bullhorn field
        • Address fields
        • Kyloe Workflow specific syntax
        • Null-checking
        • Field formatting
  • Kyloe AwesomeDocs (new version)
    • Getting started
      • Accessing Kyloe AwesomeDocs in Bullhorn
      • Screen layout
    • Edit and merging files
      • Editing a file
      • Merge basket
    • Creating a Kyloe AwesomeDoc document
      • Selecting a template
      • Record selection
      • Document generation
      • DocuSign integration
        • DocuSign recipients
        • DocuSign email
  • Help
    • Submit an idea
    • Live product status
    • Request support
    • Kyloe release notes
Powered by GitBook
On this page

Was this helpful?

  1. Kyloe AwesomeDocs
  2. DocMerge
  3. DocMerge admin guide

DocMerge template parts

PreviousDocusign detailsNextPublish

Last updated 4 months ago

Was this helpful?

A DocMerge template is built from a number of parts. There can be any number of parts, including multiples of the same part. Once there are multiple parts on the template it is possible to shift their position in the list by clicking and dragging a part.

There are 6 types of part in Kyloe DocMerge:

  1. allows a single file to be uploaded directly to the template from the builder.

  2. allows a user to select from a file stored in Bullhorn.

  3. allows the user to add their own PDF or Image file to the stapling process.

  4. adds a document generated by a Kyloe AwesomeDocs template.

  5. allows the user to build a repeating section of the merged document based on records in Bullhorn.

  6. allows the inclusion of any credential files, such as driving licence, passport, right to work etc.

If DocuSign is enabled, template parts are by default saved back as separate signed PDF files to Bullhorn. For any other parts please select if available the "Save to Bullhorn" option for the part to be saved back to Bullhorn as a separate file once the merged document is signed in DocuSign - see below.

If DocuSign is Enabled, the Save to Bullhorn will be activated for relevant parts as an option. Save to Bullhorn allows the file uploaded for the part in Bullhorn to be returned to Bullhorn from DocuSign and saved as a separate file. If selected, you'll see the option to select the Bullhorn file type for the file to be save back to once it has been returned to Bullhorn.

Fixed file part

The Fixed file part allows a single file to be uploaded directly to the template. The user will not be able to change this part during the stapling process. All documents produced using this template will include this part.

The following file extensions are accepted as files to be added to the stapled document: pdf, png, jpg and gif. Any Word documents you wish to use will have to be converted to PDF before uploading.

  1. Part Name: The part can be given a descriptive name. This name is what the user will see when completing the stapling process in Bullhorn.

  2. File: Clicking Choose a file will allow you to select a file from your local machine. This can either be a PDF or image file.

  3. The green plus allows a new template part to be added below this part.

  4. The bin / trash button will remove this part from the template.

File part

The File part allows a user to select from a file stored in Bullhorn. The file must already be attached to the appropriate entity before the template is selected.

The following file extensions are accepted as files to be added to the stapled document: pdf, docx, doc, rtf, txt, xlsx, csv, png, jpg, and gif.

  1. Part Name: The part can be given a descriptive name. This name is what the user will see when completing the stapling process in Bullhorn.

  2. Required: Checking this box will force the user to select a file when building their document. It should be noted that if this is required and no files are available on the related record in Bullhorn then the user will be unable to perform the merge.

  3. Multiple: Checking this box will allow the use to add more than one file to this part. Documents will be added to the stapling process in the order they are added by the user.

  4. File Type is optional. Clicking in the search box will present the list of Bullhorn file types. Multiple file types can be selected. The user will only see files stored in Bullhorn against the appropriate entity (4) and of one of the selected file types. If this field is left blank then all files will be available.

  5. Maximum age: Clicking in this search box will present a list of date ranges. Selecting a range here will restrict the list of available files by how far in the past they were added to Bullhorn. 7 days, for example, will only display files added to Bullhorn in the last 7 days. This option works in conjunction with the Entity Type (4) and File Type (5) selections. Additionally, if DocMerge finds only single file within the date range and the Multiple (3) checkbox is checked then it will add the file automatically. If the Multiple checkbox is not checked then only if a single file matches will it be added. If multiple files are found then the user will have to select the particular file they require.

  6. The green plus allows a new template part to be added below this part.

  7. The bin / trash button will remove this part from the template.

Local file part

The Local file part simply allows the user to add/upload their own PDF or image file to the stapling process.

The following file extensions are accepted as files to be added to the stapled document: pdf, png, jpg, and gif.

Any Word documents you wish to use will have to be converted to PDF before uploading.

  1. Part Name: The part can be given a descriptive name. This name is what the user will see when completing the stapling process in Bullhorn.

  2. Required: Checking this box will force the user to upload a file when building their document. Until a file is uploaded it will not be possible to start the stapling process.

  3. The green plus allows a new template part to be added below this part.

  4. The bin / trash button will remove this part from the template.

Template part

The Template part adds a document generated by a Kyloe AwesomeDocs template. At least one AwesomeDocs template must have been previously created to use this part.

If DocuSign is enabled Template parts are by default saved back as separate signed PDF files to Bullhorn using the file name and file type you find under the template's Output document tab in its configuration options.

  1. Part Name: The part can be given a descriptive name. This name is what the user will see when completing the stapling process in Bullhorn.

  2. Required: Checking this box will force the user to generate an AwesomeDocs file when building their document.

  3. Editable: Checking this box allows the user to edit the generated AwesomeDocs document. With this unchecked the user can only generate the Awesome Doc and must accept the content of the template.

  4. Must Edit: Checking this box will force the user to open and save a change to the generated AwesomeDocs document in Word. This overrides the Editable (3) checkbox as it forces the edit process.

  5. Entity Type: The content of the Entity Type drop-down is based on the entity selected in the Template Details section. If the template is created against Candidate then only Candidate will appear in this drop-down. If template is created against Placement then more options will appear here. Something must be selected in this drop-down as the stapling process needs to know where to look for Awesome Docs templates.

  6. File Types: Clicking in this search box will present a list of file types. Selecting from this list will restrict the list of Awesome Docs templates that the user will see to only those that save back with a matching file type.

  7. Default Template: Clicking in this search box will present` a list of AwesomeDocs templates based on the Entity Type (5). Selecting a template here will auto-select it for the user. It should be noted that selecting a template then changing the Entity Type can result in a mismatch. Always clear and re-select a template after changing the Entity Type.

  8. The green plus allows a new template part to be added below this part.

  9. The bin / trash button will remove this part from the template.

To many part

The To many part allows the user to build a repeating section of the merged document based on records in Bullhorn. An example of this is a list of candidate references and their contact details.

  1. Part Name: The part can be given a descriptive name. This name is what the user will see when completing the stapling process in Bullhorn.

  2. Required: Checking this box will force the user to generate an Awesome Docs file when building their document.

  3. Editable: Checking this box will allow the user to edit the generated Awesome Doc. With this unchecked the user can only generate the Awesome Doc and must accept the content of the template.

  4. Must Edit: Checking this box will force the user to open and save a change to the generated Awesome Doc in Word. This overrides the Editable (3) checkbox as it forces the edit process.

  5. Entity Type is the entity within Bullhorn that hosts the multiple records that are to be listed. In order to access candidate references Candidate would need to be selected here.

    NOTE: At the time of writing only Candidate is functional. You can choose from Candidate Work history, Education or References.

  6. To Many Entity Type is the record that is to be included within the merged document. This list is filtered by the selection in Entity Type (5).

    NOTE: At the time of writing only Candidate is functional. Additionally, selecting Candidate Reference and then changing the Entity Type will result in an invalid selection.

  7. Default Template is the pre-selected AwesomeDocs template that is to be used to populate the merged document. For each record found within Bullhorn a copy of the populated template will be added to the final document.

  8. Columns: Clicking in the search box allows the addition of columns to a table that is displayed to the user. This allows the user to view and select records that they want to be included in the merged document.

  9. The green plus allows a new template part to be added below this part.

  10. The bin / trash button will remove this part from the template.

Certification part

The Certification part allows the inclusion of any credential files, such as driving licence, passport, right to work etc. The files will only be available if there is a valid candidate credential matching a credential requirement.

  1. Part Name: The part can be given a descriptive name. This name is what the user will see when completing the stapling process in Bullhorn.

  2. Required: Checking this box will force the user to add at least one certification file to the stapling process.

  3. Auto Select Files: Checking this box will examine the filters applied in the rest of this part and automatically add any matching certification files.

  4. Show All Candidate Certification Files: Checking this box will overrule part of the following selections. All credential records with associated files stored against the candidate will be made available to the user during the stapling process.

  5. Credential Type is the entity within Bullhorn that hosts the credential records with the associated files. This list of available types is restricted by the entity of the template. If the template is created against Candidate then only Candidate will appear in this drop-down. If template is created against Placement then more options will appear here. Select as many entity types as are required for the template.

  6. Certifications: Clicking in this search box will list the available certifications stored in Bullhorn. This will restrict the list of linked credentials to only those that having a matching certification.

  7. Statuses: Adding a certification status in this field will restrict the list of linked credentials to only those with a matching status. Multiple statuses can be entered with a comma between each, but it should be noted that the status must be entered exactly as it is in Bullhorn.

  8. The green plus allows a new template part to be added below this part.

  9. The bin / trash button will remove this part from the template.

Entity Type: The content of the Entity Type drop-down is based on the entity selected in the section. If the template is created against Candidate then only Candidate will appear in this drop-down. If template is created against Placement then more options will appear here. Something must be selected in this drop-down as the stapling process needs to know where to look for related files.

Fixed file part
File part
Local file part:
Template part
To many part
Certification part
Template Details
Screenshot of the Save to Bullhorn option.
Screenshot of the DocMerge fixed file part.
Screenshot of the DocMerge local file part.
Screenshot of the DocMerge template part.
Screenshot of the DocMerge to many part.
Screenshot of the DocMerge certification part.