Creating a Parent-Child Relationship
Updated on Oct 03, 2019
As Onit workflows become more complex, it’s can be useful to associate different apps with one another by designating one app as the parent of another.
Creating parent-child relationships allows users to:
- Quickly create a child transaction using data that lives in a parent transaction.
- Display links to related transactions on either app’s View Page.
- Create hierarchy between a single transaction, (serving as the parent), and multiple other transactions (the parent's children).
A common example of a parent-child app relationship is often found within Contract Management workflows, where a contract that has received approval within a Contract Review app needs to now progress into a Contract Administration app so that a company can manage it while it remains active.
In this scenario, we’d make the Contract Review app the parent app of the Contract Administration app. While both manage contracts, they do so using different workflows, and perhaps different participants, and as a result, they are separate but related transactions.
If we set this relationship between apps up, a user could browse to the parent Contract Review transaction and click a button (highlighted in the screenshot below) to create the child transaction in the Contract Administration app without ever having to leave the Contract Review transaction. Additionally, since a lot of the data that the child transaction needs already lives inside the parent transaction (e.g., contract_name, company_name, contract_amount), this information will automatically be populated into the child app’s Launch Page, saving the user from having to manually type it in.