Keep the action builder aligned with deployed applications
Purpose
Applications keep a common action catalogue current so configuration uses the actions the deployed code supports.
How It Works
An application deploy publishes the triggers it raises and the actions it offers. Platform validates and reconciles those declarations in a shared registry. Builders read the available choices for their host and trigger context. Retired type detail remains available to explain existing configuration. Platform contributes shared timers and its own action declarations. Deployment setup also refreshes shipped recipes and cross-application views. A notification-centre action stays unavailable while its dependency is absent. The product should keep catalogue availability separate from proof that every host actually raises its events and executes those actions.
Relationships
- Connects with reuse workflow recipes and working-time configuration through shared integration records.
- Connects with publish event-driven automation and follow its work through shared integration records.