A Custom Event needs to trigger off a read-only field (like "Active Work Assignments") that's computed and displayed on a page, but that field isn't stored in the entity's main underlying table, so a normal insert/update trigger on that table never fires when the computed value effectively changes.

All FAQ questions / Workflows and automation

Answer

Check what table the read-only field's underlying method actually reads from — a computed/read-only field like this can be sourced from a completely different table than the entity's main one, and a normal trigger only fires on real changes to the table it's attached to, not on a value that's merely displayed as computed. The correct event trigger needs to be set on that other, actual source table instead, and replicating the field's computed logic there typically requires significant additional PL/SQL (very possibly as an autonomous transaction) rather than a simple one-line trigger, since you're now reacting to raw source-table changes instead of a pre-computed display value.

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