Expand my Community achievements bar.

Applications for the 2024-2025 Adobe Experience Manager Champion Program are open!
SOLVED

rollout specific page properties

Avatar

Level 2

Do we have the ability to rollout just specific page properties (like tags or the thumbnail) so that we don't have to manually update each translated Live Copy if just a page property is updated.

We have option to roll out just one specific component on the page. However, unable to find out how to rollout only specific page properties.

 

Any thoughts? Thanks in advance!!

1 Accepted Solution

Avatar

Correct answer by
Employee Advisor

Hi @grandhip!

 

When you rollout a page using the AEM Multi Site Manager (short: MSM), the rollout is handled on page-level. It might cover a single page or multiple pages depending on your selection for rollout. As pointed out by @MayurSatav, page properties are not even stored as single nodes in the repository but rather properties on a single node. There is no such thing as rolling out single properties.

 

However, depending on your use case, your requirement might still be covered.

 

If you have rolled out a page and update the source later on (e. g. by changing one entry from the page properties), the change will still be rolled out to the target pages. If the MSM structure is setup correctly, it does not really matter that MSM actually rolls out the complete page rather than the single, changed property. Other properties (and nodes) of the page will either still hold an active live copy relationship and stay the same or will have a broken inheritance and be excluded / untouched from the roll out.

A situation where this does not apply would be if you have incorporated multiple changes (e. g. three different page property entries) to the source and want to rollout only parts of these (only of of the changed properties). This will not be possible as there is no partial/selective rollout. You could still achieve this with authoring work (e. g. create a version of your current state of work; revert to the rolled-out version; change the single property and roll it out; revert back to the initially created version holding all your changes) but it would be a bit tedious.

 

Hope this helps!

View solution in original post

3 Replies

Avatar

Community Advisor

Hi @grandhip ,

 

I don't believe it's possible. In MSM, you have the option to break the inheritance of a specific page property in live copies to prevent it from being updated during the rollout of the master copy and its page properties. However, rolling out individual properties is not feasible. While you can use the replicateNode method to programmatically replicate a specific node, it will replicate the entire node and not a specific property. In the CRX page properties, there isn't a separate node for each property.

Avatar

Correct answer by
Employee Advisor

Hi @grandhip!

 

When you rollout a page using the AEM Multi Site Manager (short: MSM), the rollout is handled on page-level. It might cover a single page or multiple pages depending on your selection for rollout. As pointed out by @MayurSatav, page properties are not even stored as single nodes in the repository but rather properties on a single node. There is no such thing as rolling out single properties.

 

However, depending on your use case, your requirement might still be covered.

 

If you have rolled out a page and update the source later on (e. g. by changing one entry from the page properties), the change will still be rolled out to the target pages. If the MSM structure is setup correctly, it does not really matter that MSM actually rolls out the complete page rather than the single, changed property. Other properties (and nodes) of the page will either still hold an active live copy relationship and stay the same or will have a broken inheritance and be excluded / untouched from the roll out.

A situation where this does not apply would be if you have incorporated multiple changes (e. g. three different page property entries) to the source and want to rollout only parts of these (only of of the changed properties). This will not be possible as there is no partial/selective rollout. You could still achieve this with authoring work (e. g. create a version of your current state of work; revert to the rolled-out version; change the single property and roll it out; revert back to the initially created version holding all your changes) but it would be a bit tedious.

 

Hope this helps!