Process Hub · Fields, validation and calculations
Configure an embedded child process
Capture independently structured child records under their owning parent.
On this page
Before you start
- Have a saved parent process and permission to edit solutions. Decide whether you need separate child records or merely repeated rows in the parent.
Follow these steps
Screenshots use fictional training data. Names, dates and amounts are examples. Select an image to view it at full size.
- Create a new process draft in Builder and choose Embedded child placement. Select the owning parent process and a supported process type.
- Configure the child fields, validation and layout for the subtask. Use labels that explain which parent the child belongs to.

Confirm the owning parent. A deployed child’s parent ownership is locked; its actions appear from persisted parent records. - Configure the parent’s embedded-record area and allowed child actions using the available relationship controls. Review parent/child access and the intended record ownership.
- Publish and deploy the dependencies in the order reported by validation. Reopen the deployed parent and create the child through that parent’s runtime.
- Save and reopen both records. Confirm the child appears under its own parent and the member can only perform the allowed actions.
- Test with a second parent and with a restricted user. Document how users find and finish child work before enabling the flow for real records.
Example: quality checks on a production job
Use a parent Production Job and embedded Quality Check records when each check needs its own evidence and history. Create two checks on job J-100, then verify neither is listed under J-200. Keep simple checklist rows inside the parent when independent child records are unnecessary.
What you should see
Child records are opened and managed in their parent context, with the intended structure and permissions.
If something goes wrong
You only need several product rows
Use a Header Line/repeated section when rows are part of the same business record. Embedded placement adds separately owned child records.
A child does not appear as an allocation source
Allocation sources require supported deployed standalone processes or lookups. Embedded children are not supported allocation sources.