A newly created Custom Event and its action don't appear to be doing anything — how do you first confirm whether the event is even triggering, before troubleshooting the action's actual logic?

All FAQ questions / Developer Studio, deployment, and upgrades

Answer

Temporarily add a simple blocking error message to an Execute Online SQL-type action on the event — for example, ERROR_SYS.record_general('', 'ERR: Test Error from Custom Event') — then make the change that should trigger the event. If the event is genuinely firing, that test error will pop up immediately; if nothing appears, the event itself isn't triggering, which tells you to focus troubleshooting on the event's trigger conditions rather than the action logic. Remove the test error message once you've confirmed triggering behavior and move on to validating the real action.

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

← Browse Developer Studio, deployment, and upgrades questions