Two separate Validation workflows (each checking a different field is not null on record create/update) are cross-triggering incorrectly — updating a record that has one field filled in but is missing the other still fires the validation error for the field that IS actually filled in.

All FAQ questions / Workflows and automation

Answer

Add an IFS Projection Read task before the Gateway/condition check, and read the actual current record explicitly, rather than relying on whatever value the workflow's own trigger context initially handed you. Checking the field's value from that fresh Read (instead of trusting the triggering event's passed-in value directly in the Gateway condition) resolved this exact cross-triggering symptom — the trigger-supplied value isn't always a reliable representation of the record's actual current state for a field-level validation check.

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