...
Provide a JSON styled text block in JSON Output.
...
Remember to wrap process field names in two @ symbols on both sides. This works for all field types, but exists primarily for complex field types like Multi-Value and Table fields.
| Tip |
|---|
Process field notations may also be embedded in the JSON string. This can be used in scenarios where you know precisely the data you want to map. For example, if the workflow logic dictates that you know row 1 column 2 of a table field should always be injected into a specific JSON field, it may be expressed in notation form like: {“Cell Value”:{p_Table Field[0][1]}} Notation can also be helpful in cases where the JSON expects descriptive fields, like: {“Item Count”:2, “Items”:[“Element 1”,”Element 2”]} Which would be expressed in notation form like: {“Item Count”:{p_MV Field_length}, “Items”:[@@MV Field@@]} Additionally, if you wish to concatenate multiple single value fields, notation can express that like: {“WholeName”:”{p_First Name} {p_Last Name}} Specifically when using notation, basic calculations can also be performed with appropriately typed fields: {“Invoice Total”:”{p_Invoice Amount} + {p_Tax Amount}”} |
...
Optionally, the JSON output can be written to a process field on the original process.
...
| Note |
|---|
There will ALWAYS be two processes on successful processing of this node. Cloud customers should note that this will add 1 page to the page count consumed. |
Field Names should not contain square brackets.
| Info |
|---|
The JSON file generated is a new process. That process does not carry through the data of the original process. If you need to link the source process and new process, note that the ORIGINALFILENAME property of the new process will contain the original Process ID. You may use this process ID to link the output JSON to the original process. |