Process Hub · Lifecycle stages and record actions

Configure lifecycle stages for a record

Define the states a submitted record can enter and what completion means.

On this page

Before you start

  • Use a process type that exposes Business lifecycle in Builder. Agree stable state keys, responsible roles and a completion state before changing a live lifecycle.

Worked stages: a customer case

On smaller screens, scroll the table sideways to see all columns.

Stable key / labelPurpose
new / NewFirst after submit; care triages the submitted issue.
review / Quality reviewThe assigned Quality team checks the evidence.
resolution / ResolutionCare records the agreed outcome.
closed / ClosedTerminal; normal active work is complete.

Follow these steps

Screenshots use fictional training data. Names, dates and amounts are examples. Select an image to view it at full size.

  1. Open the process draft’s setup tab (Process setup, Register setup or Route setup, as appropriate) → Optional process features and enable Business lifecycle. Open Business lifecycle and record actions.
  2. Under States select Add state. Give each state a stable Key and a readable Label; choose a Tone that helps users recognise its purpose.
  3. Mark exactly the intended entry state as First after submit. Set the final state as Terminal. Keep a draft outside these stages: saving a draft does not start the lifecycle.
  4. Order the states for readability. Dragging a row changes the displayed flow order; it does not create an automatic transition.
    Lifecycle editor with New, Quality review, Resolution and Closed stages and a validation warning.View full size ↗
    Choose stage order, First after submit and Terminal deliberately. This draft warns that Close case needs confirmation; resolve validation messages before publishing.
  5. Configure Before submission access, then each state’s field/work access and After submission assignment. Add explicit actions for each permitted transition using the linked action guide.
  6. Save, validate, publish and deploy the structural process. Save one draft, submit it and move it through the stages with the intended member accounts.
  7. Before changing a live lifecycle, inspect existing records in every state. Preserve stable keys where possible and plan a migration rather than deleting a state still in use.

Test the entry rule

Save a new case as a draft and confirm it has not entered New. Submit it successfully and confirm New is shown. Reopen that same record after a process update and verify it has retained its actual stage.

What you should see

Drafts remain drafts, successful first submission enters the configured entry stage, and only configured actions move a submitted record to another stage.

If something goes wrong

The record stays in the same stage after a field changes

State order and field changes do not automatically advance the lifecycle. Configure a permitted action or a supported process-event action for that transition.

Existing records did not reset after deployment

Republishing preserves their state, ownership and revision. It is not an automatic migration into the new entry state.

Need a hand?

Contact your organisation’s Emplyr administrator using your usual internal support channel.

How to ask for help