Process Hub · Lifecycle stages and record actions

Configure step actions for a business evidence timeline

Record append-only evidence of operational events, with location rules where needed.

On this page

Before you start

  • Use a process with the Step actions optional feature. Agree which event needs evidence, whether it applies to the whole record or a saved repeated row, and any location requirements.

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 → Optional process features and enable Step actions. Open the Business evidence timeline / Step actions configuration.
  2. Add an action with a clear Button label and stable Event key. Choose Applies to Main record or the supported saved repeated-row context.
  3. Set Location to required, optional or none. If a location is unavailable, choose whether to block, require a reason or allow the event according to the business need.
    Step actions editor for Delivery evidence with an event key and location requirement.View full size ↗
    Configure the action and its location policy. Test the saved timestamp and evidence in the deployed runtime.
  4. If accuracy matters, set the target in metres and choose the supported outside-target behaviour. Explain the practical requirement to mobile users.
  5. Save, publish and deploy. Open a saved training record and record the event; check its evidence in the timeline.
  6. Test unavailable location and poor accuracy with the intended device/browser permissions. Check that the required reason/block behaviour matches the configuration.

Example: warehouse handover evidence

Create a “Goods handed over” event on the saved delivery record. Make location optional with a required explanation when unavailable if that suits the business policy. Test one event with location and another with an explanation. The evidence is append-only; use the business correction process for an incorrect entry.

What you should see

Accepted actions add traceable event evidence without pretending that the action itself is a lifecycle transition or approval.

If something goes wrong

The evidence event did not change the lifecycle stage

Step actions record evidence. Configure lifecycle transitions/approvals separately when business state must change.

The action does not apply to a new unsaved row

Repeated-row evidence targets a saved row. Save the row/record first, then perform the event.

Location is unavailable

Check device permission and the action’s fallback rule. Provide the required reason when allowed; do not invent coordinates.

Need a hand?

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

How to ask for help