Exclude a node from being promoted while Launch Promotion | AEM 6.5

[user17427320]

Hello 

We have a node under each page with the same name. When we create a launch for the page the node also get created in the launch.

On Launch promotion we do not want the information of this node to be promoted back to page as the information on this node might have been updated on page and we do not want it to be overridden.

Any suggestions how we can achieve this?

[BrianLi1]

When you create a Launch in AEM, the system copies the entire page structure, including the child node you want to exclude. On promotion, everything normally gets pushed back to the source page. If you don’t want that specific node to overwrite the existing content, you’ve got two main approaches.

The first option is to stop the node from ever being copied into the launch. When setting up the launch, you can configure exclude paths. That way, the node doesn’t exist in the launch at all, and nothing from it will be promoted later. The tradeoff is that authors working in the launch won’t be able to see or edit that node.

If you still need the node to appear in the launch (so authors can see it), but you don’t want its content to be promoted, then you’ll need a custom solution. This is usually done by creating a custom rollout action (a LiveAction). A LiveAction can check for nodes with the specific name you want to exclude and skip them when promotion happens. That way, the node exists in the launch for visibility, but its content isn’t pushed back to the live page.

A third fallback option, though less clean, is to let the node get promoted and then immediately fix it using a workflow or script that restores the original content. That’s more of a workaround than a proper solution.

Hope this helps

- Brian Li

[BrianKasingli · Accepted solution]

When you create a Launch in AEM, the system copies the entire page structure, including the child node you want to exclude. On promotion, everything normally gets pushed back to the source page. If you don’t want that specific node to overwrite the existing content, you’ve got two main approaches.

The first option is to stop the node from ever being copied into the launch. When setting up the launch, you can configure exclude paths. That way, the node doesn’t exist in the launch at all, and nothing from it will be promoted later. The tradeoff is that authors working in the launch won’t be able to see or edit that node.

If you still need the node to appear in the launch (so authors can see it), but you don’t want its content to be promoted, then you’ll need a custom solution. This is usually done by creating a custom rollout action (a LiveAction). A LiveAction can check for nodes with the specific name you want to exclude and skip them when promotion happens. That way, the node exists in the launch for visibility, but its content isn’t pushed back to the live page.

A third fallback option, though less clean, is to let the node get promoted and then immediately fix it using a workflow or script that restores the original content. That’s more of a workaround than a proper solution.

Hope this helps

- Brian Li