Example: Using the Run for Child Action (CAD)

use the run for child action to perform an action on a child business object of a parent business object see run for child action docid umnk8lwgy34t5j3xzlqn example using the release (releaseproject) business object docid\ v6yxm cqqprxxunlrvohyexample using the problem business object docid\ v6yxm cqqprxxunlrvohyexample using the service request business object docid\ v6yxm cqqprxxunlrvohy prerequisites this example assumes you have administrator level access to and are familiar with creating both business objects and s how to create a run for child quick action to create a run for child from the configuration console, click build > automation tools > quick actions to open the actions manager workspace the list of business objects that have actions appears select a business object from the list and click add/edit in the actions center, click the create new actions tab under the create new actions tab, click run for child enter your parameters in the fields provided examples of business objects and their parameters are shown in the tables below click save example using the release (releaseproject) business object scenario a company has a number of change records linked to a release business object they want to use to update the status of these changes (rfcs) in a batch to the implemented status by leveraging the run for child , the company can easily set up a way to update these associated "child" records in field parameter enter action name update linked changes to implemented status enter action description updates the status of a linked change to implemented if its status is approved enter category form actions choose a category to place your new action in the your actions tab on the left of the screen ootb category options include no category, form actions, new milestones, print, search and link, system or windows 7 migration milestones to create your own category, type a name instead of selecting from the category drop down list relationship changeassociatedreleaseproject child object filter $(approvalcondition == "true") this means that the action only runs on change records where the field approvalcondition is true action to run update status to implemented this action is set up as follows it sets the change record's status field to implemented run the scenario log in as a change manager create a new change with type emergency run the update status to implemented the status field is set to implemented , and if the approvals and approval vote tracking tabs do not exist yet, they are created example using the problem business object scenario a company has a number of problems linked to an associated incident business object they want to use to update the status of these records in a batch so that all problems at priority 1 are set to status resolved field parameter enter action name resolve via resolution enter action description runs a resolution action for problems of highest priority enter category workflow engine the selected category determines where your new action appears in the your actions tab on the left of the screen choose from no category, knowledge articles, print, templates or workflow engine ootb categories the workflow engine category helps group actions related to altering the path of records through the system to create your own category, type a name instead of selecting from the category drop down list relationship problemassociatesincident child object filter $(priority == "1") action to run resolve incident via problem resolution this action is set up as follows it sets the incident record's cause code field to linked problem , the resolution field to resolved via problem resolution , and the status field to resolved run the scenario for a single record login as an administrator open the incident workspace and select an incident with an associated problem at priority 1 or create one increasing the values for urgency and impact fields gives you a priority 1 the resolution , cause code and status fields at the bottom of the problem are set to none , blank and active respectively click on more > form actions > resolve via resolution when the resolve via resolution is run, the three fields are updated to resolved via problem resolution , linked problem , and resolved respectively example using the service request business object scenario a company has a number of task records linked to the service request business object they want to use to update the status of these records in a batch so that once the task reaches 30 days old, its status gets sets to cancelled field parameter enter action name cancel tasks enter action description cancels the service request assignment once it reaches 30 days old enter category system the category chosen sets the location for your new action in the your actions tab on the left of the screen choose from no category, button, escalation engine or mobile ootb categories to create your own category, type a name instead of selecting from the category drop down list relationship servicereqassoctaskassignment child object filter $(beginningofday(30)) action to run cancel this action is set up as follows it sets the task record's status field to cancelled run the scenario log in as an administrator open the service request workspace and select a record with associated tasks that are older than 30 days if you cannot find tasks of that age, modify the child object filter value in the to a lower number, such as 5 days, for testing the action check that the status field is not set to cancelled already click on more > system > cancel tasks enter a reason for cancellation when prompted when the cancel tasks has been run, the status field is updated to cancelled