What is a Child App
By adding a Child Application it creates a Hierarchy between Records. If you have a Deals app then against a Deal Record you may want to track all of the associated Events and also all of the Risks, Actions, Insights and Decisions involved in closing the Deal. In this case we would link a Events App and a RAID App as a child of the Deals App. This way the Deal becomes a Parent Record and multiple RAID and Event Records can be added as Children of the Deal.
Linking one or more basic Apps to a parent App can create very complex systems in a simple and easily-maintained way
When in the Record Edit view, linked Applications are visible in the left pane menu.
By clicking on the App in the left pane menu, it will show you all of the Records that are linked to the current Parent that you are viewing. In this example we can see that we have two Actions linked to our Deal.
Apps can have Child Applications Linked to them. An App can have multiple Child Apps and multiple levels of hierarchy are supported. A Child Record will only have one Parent, if a Record is linked to a Parent and it was already linked to a Parent already then the existing hierarchy will be removed and replaced with the one to the new Parent.
Adding a Child App
A Child App can be added in AppStudio. First click on the COGs menu and select App Studio
In App Studio, select the Parent App from the LaunchPad and then click on the Integration folder for that App. Then click on Add Item and you can define the Integration for the Child App.
There are a number of options to customise the Settings for the integration. Most of these relate to the Link Picker screen when performing a manual link of Child Records.
Child App: First choose the App that you would like to link.
Default: This sets the default type of link that is performed when using the Link Picker to manually link records from the Child App to the current Parent Record. It can be set to 'Link' the existing Record or to 'Copy and Link' a new Record to the Parent.
Force: Having selected what type of link is performed by default, you then have the option of forcing this Option. The User will then not be able to change the type of Link that is performed. It would then always be a 'Link' or 'Copy and Link' when using the Link Picker.
Show On Create: Enabling this options will mean that the Link Picker screen is displayed on creation of a new Parent Record
Show Options: Setting this to true shows the different Options available when performing a link using the Link Picker
Ignore AccessRights: This property determines which Records appear in the Link Picker screen. If Ignore AccessRights has been chosen then it will allow a User to see and Link a Record from the Link Picker screen that they do not have Full Access to.
Note: At the point of linking the Child Record will inherit the Access Rights from the Parent and so give access to the User that performed this Task. Use caution when enabling this option.
Default Copy Options: If the Link being actioned id a Copy and Link then you can set up the default options for the type of Copy that is performed. A Templated Copy will exclude any Fields that have been flagged to exclude. Including Attachments, Comments, Notes or History as part of the Copy may also be a consideration depending on the scenario.
Default Filter: This is the filter on the Child Records that will appear by default each time the Link Picker screen is opened. To set the filter click on the funnel icon next to the Filter box. This will opoen a pane from the right of the screen where filter criteria can be added. To add a filter criteria click on Add A Filter, first select a Field, then the logic (Contains, Equals, ...) and then the value for the Field to meet the logic. Having added the Filter criteria, click on the arrow in the top right of the pane to confirm the selection.
Confirm the Child App Integration
Having configured the integration, click on the tick at the top right of the screen to confirm.
Note: Once Apps have been linked in terms of setting up Parent-Child relationships, think about how either App may be enhanced by transferring data from one to the other. For example, perhaps it would be useful to display information at a Parent level that reflect the number of cumulative value of Child records – this can be done by setting up simple ‘Field Expressions’.