A workflow needs to both react to a field value that's only available via a Projection Action (like a shipment line's SOURCE_REF1) and show a User Task popup to notify the user — but User Tasks only work with projection-action triggers, and the projection action itself doesn't have direct access to the field value needed, creating an apparent dead end.

All FAQ questions / Workflows and automation

Answer

The way around this is to fetch the needed value from inside the workflow itself rather than needing the trigger to supply it directly: add a Projection Task step early in the workflow that reads the shipment line and retrieves SOURCE_REF1 (or whatever field you need), then use that fetched value later in the workflow, including in a subsequent User Task notification. This lets you keep the projection-action trigger (required for the User Task to be usable at all) while still getting access to field data the action itself didn't directly expose.

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