The Launch Request task type allows for parent requests to launch related requests with unique request ID's and their own process definitions. As the process administrator, you may want a process to kick off separate but related requests in order to simplify the parent process task flow, segregate data from the parent process and have different branches of a parent process work independently.
We will use a New Hire Request as an example of configuring a related request with the Launch Request task type. First, choose and add a Launch Request task type from the Tasks menu.
In this example, we will add 1 Launch Request task type that will trigger a related 'Background Check Process' after the 'HR Approved' milestone is completed.
Within the Launch Request task configuration, you will have these options for the General Settings tab:
Data Options:
Assignment Options:
Example:
Once you have made your selections for the General Settings tab, select the Advanced Settings tab from within the Launch Request task configuration. This will give you the following options:
Once you have made your configurations of the Launch Request, select Save to save your configurations. Below is an example of the Request Detail of the parent request in action.
You can see the Related Requests section is included in the parent process. Based on our configuration, we can see the child process Current Status, Request Status Update and Relationship.
If the user that is viewing the parent processes Request Detail has an open task within the child process, the user can also see that reflected under My Open Tasks. The user would be able to select the task icon here and be directed to the open task.
Based on the Launch Request visibility options that were configured, users (as shown above) can see the parent or child related requests.
Also, you should note that the request ID's are different between the parent and the children processes, indicating a segregation of data and independent process flows.
Launch Request task types allow for the last milestone from the request it launches to be used in start rules for subsequent tasks in the parent process.
For example, if you have a request that was fired from a Launch Request task that ended with one of two milestones, you could use the Data > Launch Request > Launched Request Status to create a branch in the parent process.
Below is an example. If the parent and launched requests contained tasks similar to the following:
Portion of the Parent Process | End of the Launched Process |
![]() |
![]() |
Assuming that the configuration of the Launch Request task in the parent has a value of 'Task completes when child process is completed', for its task completion requirements, it would allow the parent process to branch its flow:
Below are the start rules fort the Sales Tool Updated milestone task of the parent process: