Cloning Engagement Programs with Nested Programs Inside
It appears that there is a possible bug in the Engagement Programs feature with one of the more recent releases.
Here's what I did:
I cloned an Engagement Program that contains "sub-programs" nested inside that were added to the content stream
Expected Result: A new engagement program, newly cloned subprograms, and the newly cloned subprograms added to the content stream
Actual Result: A new engagement program, newly cloned subprograms, and the old subprograms added to the content stream. This requires you to manually remove the old subprograms and add the new ones into the content stream.
Re: Cloning Engagement Programs with Nested Programs Inside
I verified that behaviour in my own instance.
I'm not sure if it's intended -- my expectation of this feature is it would function the same way you expected. If you are cloning programs with local assets, the references to those local assets should update to reflect the new program's local assets.