Process Hub · Build by process type
Build a Header Line process or transaction batch
Configure one document with repeated rows, or an explicitly closable batch of child transactions.
On this page
Before you start
- Decide whether one header owns its own lines or an open batch collects child transactions. Prepare sample header/line values and any product/supplier lookup.
Choose the subtype
On smaller screens, scroll the table sideways to see all columns.
| Setting | How to use it |
|---|---|
| Header + lines | One purchase order header with several product lines. |
| Transaction batch | An open collecting batch with child transactions; closing permanently locks its contents. |
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 → Header Line. Set Name, placement and the intended subtype: Header + lines or Transaction batch.
- Configure identity/numbering and the header fields such as supplier, order date and requested by. Give each field a stable key and suitable type.
- For Header + lines, configure repeated line fields such as product, quantity and unit cost. Set allowed line add/delete/duplicate/reorder behaviour and meaningful line labels.
- Add calculations for line amounts and header totals if needed. Use the actual entity/field keys and test two lines with known values.
![Formula editor containing ROUND([quantity] * [unit_cost], 2) and Test formula.](../assets/screenshots/studio/builder-calculations.jpg?v=7bdc57680471)
This line calculation multiplies quantity by unit cost. Use Test formula and verify the result type before release. - For Transaction batch, configure the child transaction relationship and test opening a batch, adding child transactions and closing it. Treat Close batch as a permanent lock, not a normal business-stage button.
- Configure views, validation, access and any supported lifecycle. Save, preview, validate, publish and deploy the structure.
- Create a member test document/batch, save and reopen it. Test empty/incomplete lines, final submission and the subtype-specific close/lock behaviour before releasing automation.

The example has line totals of 250 and 240 and a document total of 490. Save and reopen to verify persistence before final submission.
Try a complete business example
What you should see
Header and repeated data behave as one intended business structure, with clear totals and correctly understood batch locking.
If something goes wrong
The team used Close batch to mean “awaiting approval”
Batch close permanently locks the batch/children. Use appropriate lifecycle/approval design for ordinary business progress.
A total ignores new rows
Check calculation entity context and references to the actual repeated collection.
Allocation output refuses the batch process
Load-document output requires a separate deployed Header Line process with Header + lines subtype, not Transaction batch.