Position the newly created configuration(PageMoveAction) before the standard rollout configuration is not deleting the pages in their old location under live copy on page move.

Hi,

As per the documentation MSM Best Practices , placing the new configuration before standard rollout configuration is not deleting the pages in the old location of live copy.

To fully realize a page move from a blueprint to live copies, consider the following best practices:

1. Create a custom rollout configuration:
   • This new configuration must include the action:
     PageMoveAction
     Do not add other actions to this configuration.
2. Position the new configuration:
   • To fully roll out the page move, while deleting respective pages at their old location in the live copy
     • Position the newly created configuration before the standard rollout configuration.
       The standard rollout configuration will take care of deleting the pages in their old location.

The behavior what we are seeing is :

Let's take a Blueprint website /content/BP with a Livecopy /content/LC

1) Renamed/moved  /content/BP/a/page to /content/BP/a/pageRNM

2)After rollout, both the live copy pages are present /content/LP/a/page and also /content/LP/a/pageRNM .. as per the documentation with PageMoveAction custom rollout placed before standard rollout configuration it should delete the page in the old location( in this case /content/LP/a/page) which is not happening.

Would appreciate any kind of help.