Promoting Launches

You need to promote launch pages to move the content back into the source (production) before publishing. When a launch page is promoted, the corresponding page of the source pages is replaced with the content of the promoted page. The following options are available when promoting a launch page:

• Whether to promote only the current page or the entire launch.
• Whether to promote the child pages of the current page.
• Whether to promote the full launch or only pages that have changed.
• Whether to delete the launch after being promoted.

Promoting Launch Pages

You can promote launches from either the Sites console or the Launches console:

1. Open:

   • The Sites console when navigating source pages:
     1. Open the references rail and select the required source page using selection mode (or select and open the references rail, the order is not important). All references will be shown.
     2. Select Launches (e.g. Launches (1)) to show a list of the specific launches.
     3. Select the specific launch to show the actions available.
     4. Select Promote launch to open the wizard.
   • The Sites console when navigating launch pages:
     1. Select the required launch page using selection mode.
     2. The Promote action will be available in the toolbar.
   • The Launches console:
     1. Select your launch (tap/click on the thumbnail).
     2. Select Promote.

2. In the first step you can specify:

   • Target

     • Delete launch after promotion

   • Scope

     • Promote full launch
     • Promote modified pages
     • Promote approved pages - dependent on the launch approval workflow
     • Promote current page
     • Promote current page and sub pages

     For example, when selecting to only promote modified pages:

     

     NOTE

     This covers a single launch, if you have nested launches see Promoting a Nested Launch.

3. Select Next to proceed.

4. You can review the pages to be promoted; these will depend on the range of pages you have chosen:

   

5. Select Promote.

Promoting Launch Pages when Editing

When you are editing a launch page, the Promote Launch action is also available from Page Information. This will open the wizard to collect the information needed.

Promoting a Nested Launch

After creating a nested launch you can promote it back to any of the sources, including the root source (production).

1. As with Creating a Nested Launch, navigate to and select the required launch in either the Launches console or the References rail.

2. Select Promote launch to open the wizard.

3. Enter the required details:

   • Target
     • Promotion target - You can promote to any of the sources.
     • Delete launch after promotion - After promotion the selected launch, and any launches nested within it, will be deleted.
   • Scope - Here you can select whether to promote the entire launch, or only pages that have actually been edited. If the latter, you can then select to include/exclude sub-pages. The default configuration is to only promote page changes for the current page:
     • Promote full launch
     • Promote modified pages
     • Promote approved pages - dependent on the launch approval workflow
     • Promote current page
     • Promote current page and sub pages

   

4. Select Next.

5. Review the promotion details before selecting Promote:

   

   NOTE

   The pages listed will depend on the Scope defined and possibly the pages that have actually been edited.

6. Your changes will be promoted and reflected in the Launches console:

   

Processing Promoted Pages Using AEM Workflow

Use workflow models to perform bulk processing of promoted Launches pages:

1. Create a workflow package.
2. When authors promote Launch pages, they store them in the workflow package.
3. Start a workflow model using the package as the payload.

To start a workflow automatically when pages are promoted, configure a workflow launcher for the package node.

For example, you can automatically generate page activation requests when authors promote Launches pages. Configure a workflow launcher to start the Request Activation workflow when the package node is modified.