I am triggering one workflow from main workflow using container step.
The child workflow comes to an end but the main workflow is still
running. What is the procedure to complete the container step and move
to the next step?
I am trying to lock and unlock a page in workflow using page.lock() &
page.unlock(); I could lock the page in first workflow, but in the next
workflow ,while unlocking the same page it throws exception saying,
"Unable to unlock Page". page.canUnlock() returns true. Did anyone use
Thank you. I tried your solution and it works as you mentioned while
doing it manually. But I am trying to replicate asset with tags
programatically. In that case I could not see the tags getting
replicated with assets. I have given enough permissions to the system
HiAs per MSM Best Practices , positioning the newly created
configuration( PageMoveAction ) before the standard rollout
configuration, will take care of deleting the pages in their old
location in the live copy.But It is not deleting the live copy page in
old location with old name and it is in sync with Blueprint renamed
page.Moreover it is creating an another page with the new name which is
not in sync with blueprint. Would appreciate any kind of help.
Hello suprajas43649601I am facing the same issue. I maintained the same
order of rollout configuration as mentioned by AEM.Doctor, but the live
copies have old pages as well. How did you resolve? Could you help me.
HiI want to rename a page so that the url of the page gets changed.I
could do it with 'Move'.The name change reflects in blue print but not
in live copies.Do I need to do it separately (Move) for live copies as
well?Am I missing anything or Is this the recommended way?
Hi,I have an issue with tag-maker which does not overwrite the already
existing tags under etc/tags with the same name, but places the non
existing tags in the bottom hence the values won't be populated in the
expected order of tag-maker.csv file. I have to insert tag in between
the already existing tags under etc/tags.For example, If we have tags
for the year 2015, 2017 already in etc/tags and want to insert 2016,
tag-maker places this after 2017 and not following the order of .csv