Event and Automation Designer

What is it?

Things happen in the system (a record is created, a status changes, a form is submitted). An event announces that; an automation reacts: trigger, conditions, actions.

Events you can react to today

• Record events for every entity: created, updated, deleted (before and after) through rules and extension points.
• Status changes through rules with a condition on the status field, and workflow transitions.
• User actions in the UI: button clicked, form submitted, grid row clicked, dialog opened (the UI event catalog); wired to action chains on the page.
• Workflow events: started, task assigned, SLA breached, escalated.
• Schedules: jobs.

Example

Employee created
   -> rule: validate employee
   -> start workflow: IT request
   -> create asset request
   -> send welcome email (notification template)

Step by step

1. Create the notification template Welcome email under Notification templates.
2. Create a rule on employee, after create, that starts the onboarding workflow.
3. In that workflow, first stage runs a service task that creates the asset request; a notification sends the email.
4. Simulate, then create an employee and open the workflow history.

Planned (placeholders)

• A dedicated Event Designer: declare custom business events with a payload schema, and subscribers with conditions, retry and dead-letter handling. Planned.
• External webhook triggers (generic inbound receiver). Planned.
• Automation retry and error-handling policies as settings on an automation. Planned.

Security, testing, troubleshooting

Automations run as the platform in the tenant's context. Test by creating a record and reading the workflow history and Audit log. If nothing fires: check the trigger event, the condition, and that the rule or workflow is published.

Related

Business logic, Queues, Jobs.