Is it possible to create a MSM rollout configuration to only edit properties | Community
Skip to main content
james-mke
Level 3
July 28, 2020
Solved

Is it possible to create a MSM rollout configuration to only edit properties

  • July 28, 2020
  • 1 reply
  • 892 views

Hello,

We are looking to create a rollout configuration that enables authors to only update page properties and not impact the page content. The intent is to help reduce the need to send pages through translation workflows when non-translatable attributes like tags and time stamps are updated within a page property. We are running 6.5.

 

I found this article that I think is on the right path:

https://docs.adobe.com/content/help/en/experience-manager-65/administering/introduction/msm-sync.html

 

I'm assuming that the editProperties Sync Action is the trigger element that we need to focus on to include all of the relevant properties that should be synced, but then as part of the rollout config, need to set the other actions to be "inactive" so that they do not change the page content. 

 

Am I on the right track, or is there something else I should consider?

 

Thank you!

 

James

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by user05162

I believe you are on the right path. Rollout configs consist of various actions like "contentCopy" , "editProperties" etc.

 

You can create a new rollout config based on the OOTB one and then add/remove the actions you want to perform as part of that rollout config.

 

Lastly, apply that rollout config to the site to make sure it's getting used in the rollout process.

1 reply

user05162Adobe EmployeeAccepted solution
Adobe Employee
July 28, 2020

I believe you are on the right path. Rollout configs consist of various actions like "contentCopy" , "editProperties" etc.

 

You can create a new rollout config based on the OOTB one and then add/remove the actions you want to perform as part of that rollout config.

 

Lastly, apply that rollout config to the site to make sure it's getting used in the rollout process.