Parent and Child Launches

Parent and Child launches empower organizations with a large global footprint, multiple subsidiaries, or a portfolio of brands to be able to conduct specialized reviews per launch, yet associate them together.

A child launch can be created from a parent launch. During creation of the child launch, the child is presented the option to inherit all of the workflow responses from the parent, but supports an independent review, where the responses could be modified to meet specialized requirements, such as local laws or specific needs of a subsidiary. The inheritance is unidirectional, and properties are passed on from a parent to the child when the child launch is created. These properties are captured in the section below titled “Parent Launch Properties”

The parent-child relationship can be defined on launches that already exist, though in this case, there is no pre-filling of any workflow responses from the parent. It is also possible to disassociate an existing parent-child relationship and choose a new parent launch.

You also have the flexibility of using different launch types for a parent and a child.

We restrict the parent-child relationship to a single level. So it is not possible to create a child launch of a launch that is already a child. Parent - child is restricted to a single level hierarchy. A parent launch can have multiple children though.

Creating a child launch from a parent launch

This screen snapshot shows how to create a child launch from an existing launch. The user starts from the launch titled “Expose User Preferences in the webapp”. In the Launch Summary page of that launch, below the title, the “Add Child” button presents a choice of whether to create a new launch as a child or add an existing launch as a child launch.

Viewing a child launch from the parent launch

In this example, the user has created a child launch of “Expose User Preferences in the webapp” titled “Email notifications”.

All the child launches appear under the description field on the parent launch summary page as shown below. You can navigate to the child launch by clicking on it. If a parent launch has multiple child launches, all of them will be listed in this Child Launches section.

Associate a parent launch during launch creation

During launch creation, users have the option to select a parent launch and to create this new launch as a child. The screen snapshot shows how this optional “Parent Launch” field supports searching for the parent launch and choosing it.

In the launchpad listing of launches, we use icons beside the launch title to visually highlight if the launch is a parent or a child.

In the right panel of the child launch’s summary page, we displays the parent launch as shown below.

In the right panel of the launch summary, you also have the option to remove or change a parent of an existing launch.

Any standalone launch can be attached as a parent launch if it is not already a parent of another launch.

To associate a parent to an existing launch, look for the “Attach to Parent” button on the launch summary page. Clicking on the button allows you to choose a parent launch from the drop-down menu. You are only allowed to add launches that are not already child launches.


Parent Launch Properties and Child Launch creation

The following properties can be optionally inherited from the parent launch in the child launch. These properties can also be edited right at the time of child creation.

  • Launch Type
  • Title
  • Description
  • Data Spec response
  • Launch-creation workflow (or screener) responses
  • Launch summary workflow responses

The following properties are automatically inherited. To change them, you can go to the launch summary page after creation and edit them there.

  • Labels
  • Product
  • Components

When Launch-creation workflow responses and Launch summary workflow responses are chosen to be inherited in the child launch, the response is pre-populated with the latest revision of the workflow. Any responses provided in the parent workflow are carried over based on questions that match if the workflow has evolved. Also, the publish status of the workflow does not affect the inheritance.

Note: associating a parent launch to a child launch after both launches already exist will not involve any of the properties from the lists mentioned above getting carried over.

Was this article helpful?
1 out of 1 found this helpful