Process Hub · Build by process type

Configure allocation load documents, printing and lifecycle events

Extend a working allocation with persisted load output and supported source-state events.

On this page

Before you start

  • Have a tested deployed allocation flow. For load output, deploy a separate Header Line process with Header + lines subtype and compatible output fields. Agree source lifecycle Process event actions if used.

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 allocation draft and enable Finish allocations as load documents when vehicles/destinations need reusable load documents. Select the compatible deployed Header + lines output; Transaction batch is not valid output.
  2. Map load header/line values using the actual deployed fields. Test the expected relationship between a destination, its active load and later reused vehicle work.
  3. For picking lists enable Allocation print details. Choose Products across load or Each order with lines and supported deployed visible scalar columns. Define a readable print layout.
  4. For source lifecycle events, configure supported Execution → Process event actions on the source process first. Map the allocation events to those allowed source actions and preserve source field/state permissions.
    Allocation setup with Enable printing and Print allocation details or picking list.View full size ↗
    Enable the required print options in the builder. A saved allocation or load must still exist before its details can be printed.
  5. Publish/deploy the required structural changes and dependent mappings. Assign demo orders and choose Save allocations before printing or finishing a load.
  6. Inspect saved relationships, any source state changes and load document. Test reassign/release with a reason and a source record in a disallowed state.
  7. Use the applicable finish/release flow only after verifying the saved allocation and load. Confirm the output document contains the expected header/lines and evidence.

Example: a morning dispatch load

Save orders SO-1001 and SO-1002 to vehicle VAN-01. Print a saved picking list and create/finish the configured load document. If assigning orders should mark them Planned, map a valid source Process event transition and verify it occurs at Save allocations. This does not book an external carrier.

What you should see

Saved allocations can produce the configured print/load output and supported atomic source lifecycle changes with the intended permission checks.

If something goes wrong

Printing ignores a pending drag/drop change

Print and finish flows use saved allocations. Choose Save allocations and confirm success first.

Finish did not fire the allocation lifecycle transition

Source lifecycle allocation events are evaluated on actual relationship changes at Save allocations, not merely Finish allocations.

One source state prevents a batch change

Lifecycle state/permission validation can reject the operation atomically. Correct that source record or mapping rather than assuming a partial save succeeded.

Need a hand?

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

How to ask for help