Process Hub · Build by process type
Build an Allocation or Mapping process
Configure source/destination records, stable keys and permitted relationship changes.
On this page
Before you start
- Deploy supported standalone source/destination processes or lookups. Prepare unique stable keys and users with access to both sources plus the allocation process.
Follow these steps
Screenshots use fictional training data. Names, dates and amounts are examples. Select an image to view it at full size.
- Open Builder → New process → Allocation / Mapping. Choose Allocation cards for a workspace or Mapping for inline relationship work, according to the intended experience.
- Select the source and destination. Supported process sources include deployed standalone Forms, Header Line, Register and Route; embedded children are not supported.

Choose the workspace layout and relationship rule to match the business scenario before configuring sources and destinations. - Select stable identity keys and readable labels. Keys must be non-null, unique, case-sensitive values of at most 256 characters without leading/trailing spaces.
- Choose up to six useful scalar display columns and any eligibility filters. Eligibility conditions are ANDed; preview a small known source/destination sample.
- Set relationship cardinality and whether users may reassign/release, including required reasons. One source has only one current destination; choose many-to-one or one-to-one as required.
- If required, separately configure allocation print details, load-document output or supported source lifecycle events using the advanced guide. Keep the first mapping flow simple.
- Save, validate, publish and deploy. Grant access and use two source records plus two destinations to test assign, Save allocations, reopen, reassign and release.
Example: orders to a vehicle
Use submitted orders as source and a deployed Vehicle Register as destination. Set order number and vehicle code as stable keys. Allow many orders per vehicle, with an explicit reason for reassignment after planning.
Try a complete business example
What you should see
Users can save permitted relationships between real source/destination records and review the correct current mapping.
If something goes wrong
Preview shows records but a member cannot use them
Preview is a sample, not proof of runtime access. Check allocation and both underlying source grants in the active profile.
A record seems duplicated or cannot be saved
Inspect null/duplicate keys, spaces and case. Friendly labels are not reliable identity keys.
A source needs two destinations at once
The current model has one current destination per source. Agree a compatible business design rather than expecting simultaneous allocations.