Publish event-driven automation and follow its work
Purpose
Administrators publish conditions and actions for business events and inspect the resulting runs and timers.
How It Works
An administrator drafts a condition and action list for a registered business event. Publication checks the configuration and the publisher’s action permissions. The published version becomes the stable explanation for later work. When its owning application raises an event, that application evaluates applicable rules in its transaction. Draft edits prepare a later version without changing the one already running. Disabling stops new use while retirement preserves the reference needed by history. Shared views help staff find failed runs and blocked timers across hosts. Hosts remain responsible for execution and resolution on their own records. The product should prove a real event-producing host before presenting configured automation as active end-to-end behaviour.
Relationships
- Requires keep the action builder aligned with deployed applications to supply the prerequisite configuration or operation.
- Connects with reuse workflow recipes and working-time configuration through shared integration records.