| Request for Feature Enhancement (RFE) Summary: |
In Adobe Experience Manager (AEM), when promoting a Launch back to the source page, certain page properties—such as title, description, alias, and tags—are not being promoted as expected. This behavior appears to be a limitation (or bug) in the default roll out configuration and affects both customized and fresh AEM instances (e.g., 6.5.22 with We.Retail content). |
| Use-case: |
A content author creates a Launch to prepare updates for a press release page. They modify several page properties in the Launch version, including metadata and visibility settings. Upon promoting the Launch, the content updates are applied, but many of the page properties revert or are lost—leading to inconsistencies and manual rework. |
| Current/Experienced Behavior: |
Current Behavior
- Launch promotion excludes certain page properties due to default rollout configuration.
- The configuration at
/libs/msm/launches/rolloutconfigs/launch/contentUpdate includes an exclusion rule:
cq.wcm.msm.action.excludedprops = jcr:.*
- This rule prevents properties like
jcr:title, jcr:description, cq:tags, and sling:alias from being promoted.
Steps to Reproduce
- Create a new page (e.g.,
press-release-may.html).
- Create a Launch for the page using default settings.
- Modify page properties in the Launch version:
- Basic Tab: Title, Navigation Title, Description, Tag, Hide from Navigation.
- Advanced Tab: Alias, Article Date.
- Add basic content to the page.
- Promote the Launch using standard promotion steps.
- Observe the result:
- Navigation Title is promoted.
- Title, Description, Tag, and Alias are not promoted.
- Content updates are correctly applied.
|
| Improved/Expected Behavior: |
Page properties modified in the Launch should be fully promoted to the source page, including:
- Title
- Description
- Tags
- Alias
- Any other relevant metadata
|
| Environment Details (AEM version/service pack, any other specifics if applicable): |
AEM 6.5.22
Adobe team a workaround to directly make changes in "libs," and be cautious about doing so and keeping track of the impact during service pack upgrades. After discussing with our internal technical team, /libs path must remain unchanged. Since Adobe proposed a solution that involves modifying the rollout configuration, we will look forward to enhancement fix for this issue. It will likely involve updating the location where the rollout config is applied to use the resolver (which prioritizes /apps over /libs) instead of relying on a hardcoded /libs path.
Other references - E-001650598 / E-001772942
|
| Customer-name/Organization name: |
Shell |
| Screenshot (if applicable): |
attached for reference |
| Code package (if applicable): |
|
