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 (###).
1 2 ###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.
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
Assignment Options: Always Unattended
The Setup Tab displays the main property sheet used to configure the automated activity.
.docxextension are listed.
(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.
/ \ : ; < > " \* ' ?).
<b>, or the characters
>. 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.
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:
On This Page