A workflow triggered from a Custom Event errors when it tries to use the event's field values (e.g. Source_Ref1, shown as NEW:Source_Ref1 in the event) in a later API Read — the workflow parameter (e.g. \${SourceRef1}) comes back unknown. How do the Custom Event's fields actually map to workflow variable names?

All FAQ questions / Workflows and automation

Answer

There's no single documented mapping table, because the exact variable name/case can depend on how the event was defined — the reliable way to find out is to use Workflow Observations (watch mode) to trigger the workflow and see exactly what variable names and values actually arrive, rather than guessing from the event's field names. If you're not sure where the failure is, temporarily strip the workflow down to just a Start and End event so it runs without error, then rebuild it step by step while watching the observations to see when the value you expect actually appears.

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