Does BPA Workflow avoid the classic mutating-table problem that plain Custom Events regularly hit when trying to query or update the same table that's still mid-transaction?

All FAQ questions / Workflows and automation

Answer

Yes, structurally — a BPA workflow doesn't execute inline within the same database trigger/transaction context that causes the mutating-table restriction in the first place; its steps run as their own separate process/continuation rather than as PL/SQL fired directly inside the triggering DML's own transaction. This means logic that would hit ORA-04091 if written as inline Custom Event PL/SQL against the still-mutating table can generally be handled through a Workflow instead without running into the same restriction — one more reason (beyond the various deferred-call and autonomous-transaction techniques already used for Custom Events) that Workflows are the increasingly preferred approach for this kind of same-table read/write logic.

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