MSM question | Community
Skip to main content
key-key
Level 4
September 13, 2019
Solved

MSM question

  • September 13, 2019
  • 3 replies
  • 3148 views

Hello,

We have a blueprint EN/Accounts /en/credit-cards/products/advance and live copy /sg/en_sg/credit-cards/products/advance

The advance page content is going to be synced with its live copy page to create a new look and feel (just for testing and sign off).  However author is not ready to put that live yet and still needs to make regular updates on the previous version of the page. 

whats the best way to handle?  Is versioning on the /sg/en_sg/credit-cards/products/advance page the best way to handle?

or do we need to make a live copy /sg/en_sg/credit-cards/products/advance1 just for sign off then rename to /sg/en_sg/credit-cards/products/advance once ready to go live?

thanks

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 leoberliant

Might be you can consider AEM launches feature: Creating Launches

By default, Live Copy automatically updates the launch pages as the source pages change. You can specify that a static copy is created to prevent automatic changes. Your authors can finish editing and promote it manually or even schedule auto-promotion.

3 replies

leoberliantAdobe EmployeeAccepted solution
Adobe Employee
September 13, 2019

Might be you can consider AEM launches feature: Creating Launches

By default, Live Copy automatically updates the launch pages as the source pages change. You can specify that a static copy is created to prevent automatic changes. Your authors can finish editing and promote it manually or even schedule auto-promotion.

Adobe Employee
September 13, 2019

You can set up the review and approval process on /sg/en_sg/credit-cards/products/advance page and once the changes are approved after making the final changes, then only start the rollout process.

SundeepKatepally
Community Advisor
Community Advisor
August 13, 2020

if your rollout is not resulting in publish. and Publish has a separate workflow then author and rollout the content as blue print and live copy both exists only in author.

If you have a preview server or preview vhost (which pulls from author) , that you can user preview to get it validated.

 

If you want to make content little more complex --> then would recommend lanches.