A workflow API task tries to populate a CLOB/long-text attribute (like a RecordSelection-style field on an Engineering Revision Transfer record) but the value never actually gets set, no matter how it's formatted or escaped, and the rest of the process silently fails as a result.

All FAQ questions / Workflows and automation

Answer

This is a confirmed platform limitation, not a formatting problem — BLOB, CLOB, GIS, and File-type attributes aren't supported for direct read/write in workflows at all, except in cases where you're calling a projection action specifically designed to manipulate that kind of data behind the scenes; no amount of escaping, encoding, or reformatting the value will make a workflow set a CLOB-type attribute directly, since the datatype itself isn't supported at the workflow-engine level.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Workflows and automation questions