Has warnings indicator in run logs
Run logs now include a Has warnings column. If a process flow run succeeds with warnings (for example, if data of the wrong type is passed into a transform function in the map shape), a warning icon is displayed in this column.
If required, the Has warnings column can be filtered so only runs with warnings are displayed.Run logs & queue
Flow control shape - single items
When configuring a flow control shape, a new Do not wrap single records in an array option is available. Use this if you are creating payloads with a batch size of 1, and you want the output to be this:
{
"field": "value",
"field": "value",
"field": "value"
}
...rather than this:
[{
"field": "value",
"field": "value",
"field": "value"
}]
Run process flow shape - variables
When using the Run process flow shape to call one process from another, it's now possible to override flow variables with meta or flow variables defined in the Run process flow shape. When configuring this shape:
- payload variable and flow variable syntax can be used.
- Any payload provided will override the passed payload from the previous step.
Logging has been extended for cases where a process flow run fails due to a custom script issue, and also if a script fails to deploy.
Un-deployed scripts not available in map script transforms
Fixed issue where only deployed scripts/versions were available for selection when configuring a script transform function for a field mapping (via the map shape).
Now, all scripts/versions are available for selection. If an un-deployed script/version is selected it is deployed, ready for use.Script transform function