The Modify DOCX workflow action applies an XSL transform on a Microsoft Word document (DOCX) to change it in some way.
| Field | Description |
|---|---|
| Input | The input DOCX file. Click the Choose File icon Choose File icon and choose a file from the pop-up menu. Alternatively, enter the filename; for example, Input/my-input.docx. |
| Output | The output DOCX file. Enter a name, or click Choose File Choose File icon to choose a file from the pop-up menu. The default output name is output-1.docx. |
| Resources | The XZIP file containing the XSL transformation to run. Click Choose File icon and choose a file from the pop-up menu. Alternatively, enter the filename; for example, Transforms/my-transform.xzip. |
| Parameters* | Enter one parameter per line, or separate parameters with a semicolon. Use the format name=value; for example, output-format=print. If a parameter cannot be read, the job log shows: Cannot parse parameters: {reason}. |
*The Microsoft Word plug-in v27 added the Parameters field.
You can also use workflow variables to specify input fields. To insert a workflow variable, click the lightning bolt icon 
and choose a variable from the pop-up menu.
Stylesheet messages
New in the Microsoft Word plug-in v27.
Messages your stylesheet outputs using <xsl:message> appear in the job log. To label each entry with a severity level, start the message with a prefix:
| Prefix | Log level |
|---|---|
[DEBUG] or [TRACE]
|
Debug |
[INFO] |
Info |
[WARN] |
Warning |
[ERROR] or [FATAL]
|
Error |
Messages without a recognised prefix are logged at the INFO level. Severity prefixes affect only how the log entry is displayed — they do not affect job behaviour.
For example:
<xsl:message>[WARN] Output file already exists; overwriting.</xsl:message>
Comments
0 comments
Please sign in to leave a comment.