Sign in to Community
Sign in to view all badges
Expand my Community achievements bar.
our client is using the Multi-Site Management (MSM) features a lot.
In a live copy, only a full page can be synchronized with the source.
As rolling out a component to the live copies is possible already, they would like to have a feature for synchronizing a page in the live copy on component level as well.
Business Value: This will reduce risks of publishing non-approved content and also will reduce communication effort within the editorial team.
Can this be added to AEM?
Thanks & Many regardsHendrik
Can you clarify if you are referring to sync feature that is done as part of rollout config ? When the component is rolled out is gets synced with the component in live copy. Please provide info based on the guideline.
Hi Hamid, this is about what happens when restoring the inheritance for a component, for which inheritance with the source page was cancelled before. When restoring inheritance, the option to sync with the source page is presented, but this refers to always the page as a whole. The editorial team would like to be able to have more control over this and decide to also sync just a single component instead of a whole page.
Apparently, there was already a POC done on this (I learned about this from a support request via the Admin Console).
Please note that currently AEM supports rollout at component level.
Hi @hamidk92094312 ,
thank you, I am aware of this (as mentioned in the initial comment).
This feature request is about adding the possibility to synchronize on component level in the live copies. Currently, only the option to synchronize the full page is available on live copy level.
Can you clarify what will be expected from component level sync that is not achieved by component level rollout ? I understand these are different but I am referring to the end results. Can you clarify ?
component-level rollout from the live copy source to the live copies is in place and is working fine - as mentioned by you correctly.
Component-level sync would work on the basis of a component within a live copy and should pull in the latest content from the corresponding component in the live copy source.
Today, it is only possible to sync a full page, e.g. all components configured on that page, with the live copy source. The difference here then would be that syncing on component-level would only pull in the content for a particular component and not the whole page / not all components on the given page.
I hope that helps.
@akashk22786878 can you please look at this Idea and review it? Do we need more information for this one?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.