Configuring Microsoft Word document merge fields for form templates
Before starting this task, ensure that you have created the merge field in Microsoft Word, and that you have noted the token names of questions you want to include in the document. The token name of a question is found in the Reference Name field when you add or edit a question from the Business Processestab on the Customize workspace.
To configure the merge fields in a Microsoft Word print document:
In Microsoft Word, open the document you want to add merge fields to.
Place the cursor where you want to add the merge field.
In theHome tab, click Add NexJ CRM Merge. The Add NexJ Merge dialog opens.
Select a merge field and click Add Merge Field. The Add NexJ Merge dialog closes and the merge field is inserted into the document and is denoted by «Token Name Title».
[Optional] In the merge field, select the existing token name title and replace it with a new token name title that describes what information the merge field is extracting from the form.
Right-click the merge field and select Toggle Field Codes. The merge field displays the field code as { MERGEFIELD TokenName }. This token name must match the token name of a field in the form to extract information from it. For additional information about tokens, see Using tokens.
In the merge field, select the existing token name and replace it with the new token name. The syntax for print document merge fields is: { MERGEFIELD "${fields[PageName.SectionName.QuestionName]value}"} For example, to extract a client's first name from a field in the profile section of a page named "Introduction," enter: { MERGEFIELD "${fields[Introduction.profile.firstName]value}"}
When you have finished configuring the print document merge fields, click the Savebutton .
The print document merge fields are configured to extract information from the completed form. You can now add the document to a form so that it can be printed when the form is completed.
For more information about merge fields, see "Configuring merge fields" in the technical documentation.
JavaScript errors detected
Please note, these errors can depend on your browser setup.
If this problem persists, please contact our support.