A Custom Event Action meant to block cancelling a Reserved Customer Order line also incorrectly fires when a user tries to undo a Manual Reservation on that same line (since Rowstate changes away from 'Reserved' in both cases) — checking for a populated Cancel Reason doesn't reliably distinguish the two scenarios. What's a more robust condition to use?

All FAQ questions / Platform, Aurena, and customization

Answer

Rather than relying on a proxy field like Cancel Reason being populated, check the record's actual resulting state directly — add a condition that the record's NEW Rowstate specifically equals 'Cancelled', rather than just checking that it changed away from 'Reserved' or that some other related field has a value. Checking the actual target-state transition explicitly (Rowstate = 'Cancelled') distinguishes a genuine cancellation from other operations — like undoing a manual reservation — that also move the line's Rowstate out of 'Reserved' without actually cancelling it.

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

← Browse Platform, Aurena, and customization questions