Hello,
My users would like to be able to specify a large (50+) list of pages to be activated and activate them all as a bulk job rather than manually activating one by one when they are ready to publish them all. These are specific pages, not entire trees. I've found that the "Bulk Workflow Manager" in ACS Commons will let you specify this list and specify a workflow.
The default "request for activation" workflow doesn't work because a) the users don't normally request activation, they just do it, and b) because it triggers the request workflow for each page individually, so they still have 50+ requests to respond to.
I created a custom workflow that just creates a page version and activates the page, and it seems to do the job. However, there are security concerns - anyone with access to the workflow can activate any node in the repository, and it shows activated by "workflow-process-service". We have multiple sites in AEM, and users normally only have access to specific sites - this would let them activate anything.
Is there a better way to do this securely?
Solved! Go to Solution.
Views
Replies
Total Likes
Hello Andrew,
If the pages are under a specific tree, you can look into using Activate Tree. See Publishing Pages for more info.
Regarding the Activation through a workflow, you'll always see the workflow-process-service user being invoked as the workflow session is created with the service-user rather than the initiator.
Best Regards,
Aneet Arora
Hello Andrew,
If the pages are under a specific tree, you can look into using Activate Tree. See Publishing Pages for more info.
Regarding the Activation through a workflow, you'll always see the workflow-process-service user being invoked as the workflow session is created with the service-user rather than the initiator.
Best Regards,
Aneet Arora
Views
Replies
Total Likes
Views
Likes
Replies
Views
Likes
Replies