Word Doc from Template Smart Service


The Word Doc from Template Smart Service generates a Microsoft Office 2007 (or Office 2010) Word document populated with process data.

This activity uses a Microsoft Word Document template in .docx format. To create the merge template, edit a Microsoft Word 2007/2010 document. Identify each merge field by enclosing the field with three pound symbols (###).

Example Word Template

Name: word_template.docx


 ###Name###. joined ###Department###. on ###Date of Joining###. The employee's position is ###Position###. and their 
supervisor is ### Supervisor###.

When you've created your template, upload it to a folder in Appian Document Management. You can also upload alternate templates, which can be selected at runtime using a rule or an expression.

Your keyed template fields must pass Microsoft Word's spelling and grammar tests. When viewing the template in Microsoft Word, be sure to right-click the field in your template and select Ignore for any spelling or grammar issues that are listed. Ensure that any text formatting is contiguously applied to the entire substitution key, and not any partial section of the key. Formatting creates XML tags in the template that render the substitution key unrecognizable if an opening or closing tag falls within the key.

Permissions needed

The user running the smart service must have Author rights to the folder holding the template in Document Management. Attempting to complete this task without the proper user rights generates an error message for the process administrator and pauses the process.


  • Category: Document Generation

  • Icon:

  • Assignment Options: Always Unattended

Configuration options

Setup tab

The Setup Tab displays the main property sheet used to configure the automated activity.

  • Template: Select your merge template from Appian Document Management by typing in the name or clicking Directory and browsing through Appian Document Management. Only documents that have a .docx extension are listed.
    • Once a document has been selected, the substitution keys in the document are scanned and appear as shown below.
    • Any formatting applied to a substitution key must be contiguous, meaning it cannot be applied to some characters and not others.
  • (Optional) Runtime Template: Type an expression that selects a document using a variable or a Constant. (You can create Constants that contain each desired template.) The substitution fields in the runtime template(s) must match those in the base template.

  • Destination: Choose between creating a new document and overwriting an existing document.

  • If you selected the Create a new file option, complete the following fields.
    • New document name: Enter the name of the new document that is to be created by this node. You can type the name into the text-field, or a name can be specified through an expression. Avoid using characters that are disallowed in Appian Document Management filenames (such as / \ : ; < > " \* ' ? ).
    • New document description: Type a brief description of the of document. The expression editor can also be used to formulate a description.
    • Save in folder: Specify the folder where the newly created document is to be stored. Once you have selected a folder, click the checkbox icon to check the name of the folder specified. You can also use an expression or a rule to select a folder at runtime.
  • If you selected the Overwrite an existing document option, complete the following fields.
    • Document to replace: In this field, specify the document to be updated. Click Directory to browse for a document. You can also look up the document using autocomplete by typing the document name in the text field.
  • Replace with: Assign a process variable, constant, or typed value for each replacement key listed.
    • Substitution values cannot contain HTML formatting tags, such as <i> or <b>, or the characters &, <, and >. If necessary, use the toHtml() function to remove these characters. See also: tohtml() If you've made changes to the template document, click Re-scan Template on the toolbar. The template is then rescanned for substitution keys. Whenever the template path is changed, the specified document is also parsed for substitution keys. The node supports Unicode (UTF-8) templates and generates Unicode documents.

If the node is run as a user who does not have adequate rights to: the template document, the document that is to be replaced, or the folder where the new document is generated, an error message is sent to the process administrator and the task is paused.

Data tab

Node outputs

The ID of the document that was created or replaced is returned by the node.

To retain the ID of the document so it can be referenced elsewhere in the process model:

  1. Click the Outputs tab.
  2. Select New Document Created on the Results list (the Result properties display).
  3. Create a new process variable to store the result or select an existing Process Variable with a Document data type from the available list.
Open in Github Built: Fri, Oct 22, 2021 (11:09:30 AM)

On This Page