You are reading the AEM 6.1 version of Launches.
This documentation is also available for the following versions:  AEM 6.2  AEM 6.0  AEM 5.6.1  AEM 5.6 

Launches enable you to efficiently develop the content for a future release of one or more activated web pages.

A launch is created to allow you to make changes ready for future publication (while maintaining your current pages). After editing and updating your launch pages you promote them back to the source, then activate the source pages (top-level). Promoting duplicates the launch content back to the source pages and can be done either manually or automatically (dependent on fields set when creating and editing the launch). 

For example, the seasonal product pages of your online store are updated quarterly so that the featured products align with the current season. To prepare for the next quarterly update, you can create a launch of the appropriate web pages. Throughout the quarter, the following changes are accumulated in the launch copy:

  • Changes to the source pages that occur as a result of normal maintenance tasks. These changes are automatically duplicated in the launch pages.
  • Edits that are performed directly on the launch pages in preparation for the next quarter.

When the next quarter arrives, you promote the launch pages so that you can publish the source pages (holding the updated content).

This section descibes how to create, edit and promote (and if necessary delete) launch pages:

Launches - the Order of Events

Launches enable you to efficiently develop content for a future release of one or more activated web pages.

Launches allow you to:

  • Create a copy of your source pages:

    • The copy is your launch.
    • The top-level source pages are known as Production.
  • You can promote and publish the content either manually or automatically:

    • Manually:
      • Promote your launch content back to the Target (source pages) when it is ready to be published.
      • Publish the content from the source (after promoting back) pages.
    • Automatically - this involves the following:
      • The Launch(Live) date field: this can be set when creating or editing a launch.
      • The Production Ready flag: this can only be set when editing a launch.
      • If the Production Ready flag is set, the launch will be automatically promoted to the production pages on the specified Launch(Live) date. After the promotion, the production pages are automatically published.
        If no date has been set, the flag will have no effect.
  • Update your source and launch pages in parallel:

    • Changes to the source pages are automatically implemented in the launch copy (if set up as with inheritance; i.e. as a live copy).
    • Changes to your launch copy can be made without disrupting these automatic updates or the source pages.
  • Create a nested launch - a launch within a launch:

    • The source is an existing launch.
    • You can promote a nested launch to any target; this can be a parent launch or the top-level source pages (Production).


Creating and editing launches requires access rights to /content/launches - as with the default group content-authors.

Please contact your system administrator if you experience any problems.