Expand my Community achievements bar.

SOLVED

Multiple asset activation via single workflow instaNce | AEM 6.5

Avatar

Employee

 Is it possible to activate all the assets and child assets (in subfolders) with single workflow  instance/request in 6.5 AMS?

AEM Cloud has 'Publish content tree' but 6.5 doesn't.

If I select 'Activation Model' and use a folder as payload , 1 workflow instance is started and  only folder gets activated , not sub folder/assets inside.

Looks like only option is to create a custom process or trigger workflow request for each asset. Any suggestions/thoughts?

 

 

 

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

You can write the custom logic in the workflow process step to activate the child nodes/pages as well.

This article shows how to replicate from servlet same can be applied in workflow process step.

https://aem.redquark.org/2018/10/day-19-replication-api-in-action.html

Hope this is helpful

View solution in original post

6 Replies

Avatar

Community Advisor

@digarg17  Please use this URL: <server:port>/libs/replication/treeactivation.html

to activate the tree.

Avatar

Employee

I am aware of this , but I am specifically looking for bulk activation as a workflow step when payload is a folder not direct repliction.

Avatar

Correct answer by
Community Advisor

You can write the custom logic in the workflow process step to activate the child nodes/pages as well.

This article shows how to replicate from servlet same can be applied in workflow process step.

https://aem.redquark.org/2018/10/day-19-replication-api-in-action.html

Hope this is helpful

Avatar

Employee

looking for approaches where we don't need customisation - if anything exists at all ?

Avatar

Community Advisor

I don't think we have anything as such, let us know here if you any better alternative solution.

 

Avatar

Employee

We ended up using 'AEM ACS Commons' process step called Replicate with Options , that can accept folder as payload , create a single workflow instance and activate all assets / sub assets. There is 'NO' need for customisation.

 

https://adobe-consulting-services.github.io/acs-aem-commons/features/workflow-processes/content-trav...