This article will help you:
- find the main features you need to generate documents with BRYTER
- understand how to add your own templates to BRYTER
- make the automated documents available as download or attachment
Main features for document generation
With BRYTER, you can create documents quickly and easily and allow end-users to generate documents only containing relevant clauses and content with ease.
Input nodes | Action nodes | Value nodes | Result nodes |
All input node types |
Create Document Send Email Handover Search and Replace in a Document PREMIUM Case Database any integration action that allows uploading or sending and processing documents PREMIUM (e.g. HighQ, DocuSign) |
Text Block
less frequently: Number
|
Result |
Create Document action
In order to generate any document, you will need to include a Create Document action node in your module.
This Create Document action node is already pre-filled with a Deafult BRYTER Template that contains one placeholder called {{Result}} and is by default set to DOCX.
You can choose to download the Default BRYTER Template by clicking into the Template drop down field and subsequently on the download icon .
The downloaded Default BRYTER Template indicates how authors can use their own docx templates to generate documents easily by placing placeholders in double curly brackets into their existing Word templates:
The placeholder {{Result}} denotes the spot in your document that should be replaced with content that you are either gathering directly from your end user via Input nodes or by defining clauses based on user input via Text Block value nodes.
All you need to do to ensure that content is populated into the Result placeholder is 'mapping' any kind of value - either directly received through selections or answers provided in input nodes or though a Text Block value that contains references and complete clauses or several sentences the author has provided.
If you are creating your own templates in Word, they could look more like the example below:
The placeholders can be added by wrapping the placeholder into two curly brackets {{ and }}. Should the entire line or row in a table be deleted if the placeholder remains empty when running through the module, authors can add commands such as delete row {{\dr}} or delete line {{\dl}} (more information on Word commands here). These placeholders are often already denoted in square brackets or have been highlighted - it's often easiest to simply search for [ / ] in Word and replace with {{ / }}.
BRYTER Word Add-in
You could also use the BRYTER Word Add-in to easily have access to these commands and placeholder indicators:
Once you have placed your placeholders where required in your template, you can upload your own template into BRYTER. In your Create Document action, click into the Template field, and select Upload. This will open up your local drive folder where you can select your template and upload it into the node.
Once uploaded all placeholders in curly brackets that the Word document contains, will be displayed and you can start mapping the nodes in your module into the placeholder fields when clicking into the fields.
Map values to template placeholders
Should the node titles correspond to the placeholder names, you can choose to automatically map all exact matches into the corresponding placeholder fields. Select Map values to placeholders and BRYTER will match the identical values and you only have to select the content for the remaining placeholders.
β Please note that you need to re-upload and replace the template in your BRYTER module whenever you make changes directly in your docx file, for example, change the formatting or add a new placeholder. The uploaded template is not linked with the source document.
How to make the generated document available
After mapping all placeholders, you could now select the Document as an attachment in an email action.
Another way to make your file easily available to the end-user is to @-mention the document in the content field of any Input or Result node.
If you are using case databases and want to write the created document into a specific database action node, you need to have a File field configured in the corresponding database and can now @-mention the relevant document into the specified database field.
π‘The Create Document action node would most likely be situated rather low in your graph just before the input node, Send Email or Integration action node, or result node that makes the generated document available or pushes it across a system or into a database.
Keywords: {}; {{}}; brakets; {{; }};