Process Hub · Workflows and approvals
Build workflow chains between processes
Connect deployed processes with clear unlock rules, field mappings and downstream assignments.
On this page
Before you start
- Deploy every participating process in the same profile. Have Manage automations/publication access. List the source event, destination record and expected mappings before building.
A recurring start
For normal recurring starts, create a published Schedule Plan and select the published start schedule where appropriate. Operating calendars and Schedule Plans are configured in their own sections; a chain is not the calendar.
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 → Workflow chains → Add workflow chain. Enter the Chain name, select its Owner process and open the canvas.
- Add a process card for each participating deployed process. Use a process approval, chain or group card only when that node’s behaviour is needed and understood.
- Connect the source and destination. Edit the workflow link and choose Dependency action: Create downstream draft, Update linked record or Release allocation load, as appropriate for the selected nodes.

Process cards and their links define the chain. Select a link to configure its trigger, mappings and downstream work. - Choose Starts when from the supported source events. Set a clear Button label for a manual transition. Enable Only one unsubmitted draft per source record when the next step must not create duplicate open drafts.
- Add field mappings. For each Target field choose Source field, Static value, Process number, Record ID (public) or Submitted at. Choose Overwrite or Fill empty only deliberately.

Choose compatible source and target fields, then decide whether to fill empty values or overwrite existing ones. - For joins choose AND when all incoming branches must unlock the next step, or OR when any incoming branch may unlock it. Review group branch rules separately from an individual link.
- If needed enable Create work item for downstream draft and configure a profile user, role, user field or workflow actor, plus a due rule. Use the guide below for assignment details.

Enable downstream work only when required, choose its assignment and due rule, then verify the recipient can open the resulting record. - Save, validate and publish/release the chain using its automation controls. Trigger a controlled source record event and inspect the created/updated record, assignment and Automation activity.
Example: case → corrective action
Link a submitted Customer Case to a Corrective Action draft. Map the case process number into source_case_reference and the issue description into issue_summary. Create a Quality-role task for the new draft. Test that the draft still needs its own required answers before submission.
What you should see
The intended event unlocks the correct downstream work, with predictable data mappings and a traceable chain run.
If something goes wrong
The destination process is missing or invalid
Confirm it is deployed in the same profile, has supported placement/type and is compatible with the selected dependency action.
A second click creates duplicate work
Review one-unsubmitted-draft protection and the selected trigger. Check whether an existing linked record should be updated instead of creating another.
A join never unlocks
Review AND/OR and whether the incoming records belong to the same workflow run. Unrelated Add New records do not automatically form a group.