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:
After you promote the launch pages to the target (Production), you can activate the Production pages as an entity (to make the process quicker). Add the pages to a workflow package and use it as the payload for a workflow that activates a package of pages. You need to create the workflow package before promoting the launch. See Processing Promoted Pages Using AEM Workflow.
A single launch cannot be promoted concurrently. This means that two promote actions on the same launch at the same time can result in an error -
Launch could not be promoted (together with conflict errors in the log).
When promoting launches for modified pages, modifications in both the source and launch branches are considered.
You can promote launches from either the Sites console or the Launches console:
In the first step you can specify:
For example, when selecting to only promote modified pages:
This covers a single launch, if you have nested launches see Promoting a Nested Launch.
You can review the pages to be promoted; these will depend on the range of pages you have chosen:
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.
This is available for single and nested launches.
After creating a nested launch you can promote it back to any of the sources, including the root source (production).
As with Creating a Nested Launch, navigate to and select the required launch in either the Launches console or the References rail.
Select Promote launch to open the wizard.
Enter the required details:
Review the promotion details before selecting Promote:
The pages listed will depend on the Scope defined and possibly the pages that have actually been edited.
Your changes will be promoted and reflected in the Launches console:
Use workflow models to perform bulk processing of promoted Launches pages:
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.