Process Hub · Workflows and approvals
How to configure and release workflow automation
Configure approvals, notifications and chains, then release reviewed automation changes.
On this page
Before you start
- Have Manage automations and, for publication, Publish automations access. Processes must be deployed and their fields/dependencies ready for the automation.
Which change goes where?
On smaller screens, scroll the table sideways to see all columns.
| Setting | How to use it |
|---|---|
| Lifecycle stages/actions/field policy | Structural Builder draft → publish → deploy. |
| Approval, notification and rule definitions | Automation draft → validate → reviewed automation release. |
| Workflow chains | Chain configuration and its independent publish/release controls. |
| Recurring work | Published Schedule Plan, plus published calendar rules when used. |
Detailed setup guides
Shared configurations
A bulk configuration can apply shared approval/notification settings to several process-owned definitions. Review the selected Processes, Edit bulk changes and impact before release. Editing one shared set can affect more than the process you opened.
Follow these steps
Screenshots use fictional training data. Names, dates and amounts are examples. Select an image to view it at full size.
- Open Settings → Process Hub → Workflows. The Workflow operations screen groups Configure and Monitor tabs.
- Choose Approvals for submitted-record reviews, Notifications for supported event messages/recipients, Advanced rules for event/condition actions, or Workflow chains for dependencies between processes. Configure Business lifecycle stages and record actions in Builder instead.
- Create/edit the appropriate draft for the selected deployed process. Set trigger/event, conditions, target process/fields, assignees/recipients and timing as required by that automation.

Review the current release and pending automation drafts. Process deployment and automation release have separate controls. - Save the draft and review validation and shared-impact information. An automation draft remains inactive until included in a published release.
- In the release controls, use Include in release/Select changed for the reviewed definitions, add Release notes and use Release selected changes. Check the resulting active version; do not include unrelated drafts.
- Trigger a controlled representative record event and use Automation activity to verify the active version/release and result. Use Notification delivery for message failures and Schedule activity for scheduled work.

Use activity to verify which released automation ran and what it did. Check resulting records and assignments as well.
What you should see
The intended automation release is active independently of structural process publication/deployment.
If something goes wrong
Nothing happens after saving a draft
Check that the draft was included in a successful automation release and its trigger conditions actually occurred.
A rule references a removed field/version
Repair compatibility against the currently deployed structure before release.
The activity shows a retry/failure
Read the safe detail/reference and correct the underlying condition before replaying anything that could create records or send messages.