Process Hub · Lifecycle stages and record actions
Configure lifecycle actions, claims and stage handoffs
Add record buttons that validate evidence, move stages and assign the next piece of work.
On this page
Before you start
- Configure lifecycle states first. Prepare profile users/roles or a single-select User field for assignment. Agree who can act and what evidence is mandatory.
User actions and process events
Process event actions are configured for supported events from another process, such as allocation. They are hidden from the ordinary action buttons. Do not choose Process event to create a button people should click.
Follow these steps
Screenshots use fictional training data. Names, dates and amounts are examples. Select an image to view it at full size.
- Open Business lifecycle and record actions. Add an action with a Stable key and a clear button label such as Send to Quality. Choose Execution → User action.
- Set Allowed from to the source state(s), choose Target state and Behaviour. Use Change state for a transition; use Claim record or Release claim when the task is ownership.
- Choose Button location and After success behaviour. Set Visibility and Permission deliberately; a visible button still requires server authorisation.

Give the action a clear label and select its allowed source, target and behaviour. Review its remaining permissions and confirmation settings before saving. - Set Comment to none, optional or required. Add Required fields, confirmation text and destructive/final marking where appropriate. Mark an action explicitly if it reopens a terminal state.
- For a handoff choose Complete current stage work, then enable Create and assign the next stage work item. Choose fixed user, claimable profile role or a single-select user field.
- Give the next work item its stable work key, title and description. Choose Task / My Work or Lifecycle approval / Approvals, set its due rule and review the required In-app notification plus optional channels.

Available record actions depend on the current stage and your access. This example exposes Return to Care. - Save actions and the process draft; publish and deploy. Test the complete handoff, a missing required answer, a user outside the allowed role and a stale record opened in two tabs.
Worked handoff: Send to Quality
Allowed from New → Target Quality review. Require issue_type and description, require a comment if your team needs a handover note, complete the care task and create a claimable Quality role task due in one day. Test that Quality can claim it and Care no longer sees the old task as active.
What you should see
Each accepted action records a controlled change, applies its work-item effect and creates the intended next assignment without losing required evidence.
If something goes wrong
A stage changed but the old task stayed open
With Work-item effect None and no next work, the existing work/owner/due date are preserved. Configure explicit completion plus next work for a handoff.
A required line field is blocking the action
Every existing repeated row must satisfy that required field. Fill or validly remove the incomplete row; do not assume one populated row is enough.
The action reports a record change/conflict
Reopen the current record and reassess it. Lifecycle actions check the current revision and updated timestamp; retrying stale decisions can be unsafe.