Hi all! I'm hoping to be able to set up a launch branch (A) say, from July 1s that gets promoted live (C) on July 30th. I'd like to start another branch (B) on July 15th from the same origin page, but then promote the changes from branch B to branch C, for a final live version of the origin page from branches A and B (assuming the changes don't conflict.)
Does anyone know if this is possible via launches or some other functionality?
Thanks in advance for your help!
Hi,
Launches work in a parent-child relationship, you cannot merge content between "siblings", however, you can create "nested" launches that will allow you to merge your changes to different targets(sources), so creating a nested structure can work for your use case. I am not sure if I understood correctly your use case, but I think you could create something like this:
- A (source)
- C (child) You can promote to A
- B (grandchild of A) You can promote to C or A
You can read more about Nested Launches here: https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/sites/authoring/launches/overview
Hope this helps
Hi,
Launches work in a parent-child relationship, you cannot merge content between "siblings", however, you can create "nested" launches that will allow you to merge your changes to different targets(sources), so creating a nested structure can work for your use case. I am not sure if I understood correctly your use case, but I think you could create something like this:
- A (source)
- C (child) You can promote to A
- B (grandchild of A) You can promote to C or A
You can read more about Nested Launches here: https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/sites/authoring/launches/overview
Hope this helps
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
