How to exclude few properties only for content pages and keep the same for experience fragments during rollout process? | Community
Skip to main content
P
PraveenKM1
Level 1
February 6, 2026
Question

How to exclude few properties only for content pages and keep the same for experience fragments during rollout process?

  • February 6, 2026
  • 1 reply
  • 6 views

Hi Community,

 

We are currently using com.day.cq.wcm.msm.impl.actions.ContentUpdateActionFactory.cfg.json
to exclude certain properties from being updated during the rollout process.

This configuration is working as expected.

However, while this exclusion behavior is acceptable for content pages, authors do not want the same behavior to apply to Experience Fragments. In other words, the excluded properties should continue to be ignored during rollout for content pages, but should still be updated for Experience Fragments.

Is there a way to control or customize the rollout process separately for Experience Fragments and content pages?

Any guidance or suggestions would be greatly appreciated.

Thanks in advance,
Praveen KM

1 reply

giuseppebaglio
giuseppebaglio
Level 10
February 6, 2026

hi ​@PraveenKM1,

AEM MSM uses global OSGi configurations like com.day.cq.wcm.msm.impl.actions.ContentUpdateActionFactory.cfg.json for property exclusions during rollout, applying uniformly across all pages including Experience Fragments (XF). There is no out-of-the-box way to apply different exclusions based on resource type (e.g., content pages vs. XF under /content/experience-fragments).
On the other hand, different rollout configurations can include or exclude the contentUpdate action entirely, allowing control over whether properties are updated at all for specific hierarchies. 
Here you can find an interesting article about creating a custom configuration for XF. On this other article it goes deeper into coding perspective which can help you define your logic. 

Terms & ConditionsAccessibility statement

Loading footer...