Process Hub · Workflows and approvals
Configure advanced rules for process events
Combine an explicit event, matching conditions and supported actions.
On this page
Before you start
- Have deployed fields and Manage automations/publication access. Write one event, one matching example, one non-matching example and the expected change.
Status versus lifecycle state
Setting a process status does not substitute for a configured business-lifecycle transition. Use lifecycle actions for lifecycle ownership, state validation and stage handoffs.
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 → Advanced rules and create/edit a rule for the deployed process.
- Choose the trigger that really occurs: Process started, Draft saved, Record submitted, Status changed, Field value changed, Record action clicked, Schedule fired, Approval completed or Manual run.
- Add conditions using supported fields and operators. All configured conditions must match. Use Equals/Does not equal, Contains, Greater than/Less than or Is empty/Is not empty as appropriate.
- Choose the supported action and valid target fields/values. Set process status, Set field value, Create work item and Write history entry require compatible configuration. Review Send notification against the supported notification policy model.

Choose the trigger, conditions and action, then test a matching event and a non-matching event. - Save and review validation and shared-process impact. Include only the intended changed definition in the automation release.
- Trigger a new matching event and a non-matching event. Check Automation activity, record values/history and any resulting work. Confirm the non-matching record remains unaffected.
- Before release to real work, check whether the action itself can trigger another rule. Remove accidental loops and decide who monitors failures.
Example: flag an urgent request
Trigger Record submitted. Conditions: priority equals Urgent AND issue_type equals Damaged. Set a compatible needs_review field to Yes and write a history entry if configured. Test Urgent + Damaged, Normal + Damaged and Urgent + Other before release.
What you should see
A released rule responds to the intended event and matching conditions, with a visible, explainable result.
If something goes wrong
Nothing happens to older records after publication
Rules are event-driven. Saving or publishing a rule does not retroactively run it across all existing records.
An integration action appears but no external system changes
Queue outbound integration remains a placeholder in this automation path. Use supported configured connections/integration flows and verify their delivery separately.
The conditions match individually but never together
All rule conditions are ANDed. Check values and types on the same triggering record; split separate alternatives into deliberately designed rules if needed.