Expand my Community achievements bar.

SOLVED

Best way to run modified DAM Update Workflow to large number of the assets

Avatar

Level 3

I had a requirement to modify the OOTB DAM Upload asset workflow in order to add multiple renditions. I have made the required changes to the OOTB Workflow. There are lot of digital assets (more than 100 GB) in production. I am looking for the best option to run the modified DAM Upload asset workflow for all the assets so the required renditions are created for each of them.

Please do let me know the best option to execute the workflow without creating much load in the server.

Note: Need to execute in this is the AEM Inhouse Server

Topics

Topics help categorize Community content and increase your ability to discover relevant content.

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

@BinaryAlchemy11 

 

ACS Commons provides a Bulk Workflow manager. It can execute workflow in batches with delay between consecutive batch

https://adobe-consulting-services.github.io/acs-aem-commons/features/bulk-workflow-manager/index.htm...

 


Aanchal Sikka

View solution in original post

3 Replies

Avatar

Correct answer by
Community Advisor

@BinaryAlchemy11 

 

ACS Commons provides a Bulk Workflow manager. It can execute workflow in batches with delay between consecutive batch

https://adobe-consulting-services.github.io/acs-aem-commons/features/bulk-workflow-manager/index.htm...

 


Aanchal Sikka

Avatar

Community Advisor

@BinaryAlchemy11 

Other choice might be to try executing the DAM Update Asset workflow on folder level or via Collection 

 

https://experienceleague.adobe.com/en/docs/experience-manager-65/content/assets/managing/manage-coll... 

 

ACS Commons would be easier to manage.


Aanchal Sikka

The following has evaluated to null or missing: ==> liql("SELECT id, subject, body, depth, post_time, author.login, author.id, author.rank, metrics.views FROM messages WHERE topic.id = '${topicId}' AND is_solution = true").data.items[0] [in template "analytics-container" at line 82, column 31] ---- Tip: It's the final [] step that caused this error, not those before it. ---- Tip: If the failing expression is known to be legally refer to something that's sometimes null or missing, either specify a default value like myOptionalVar!myDefault, or use <#if myOptionalVar??>when-present<#else>when-missing. (These only cover the last step of the expression; to cover the whole expression, use parenthesis: (myOptionalVar.foo)!myDefault, (myOptionalVar.foo)?? ---- ---- FTL stack trace ("~" means nesting-related): - Failed at: #assign acceptedAnswer = liql("SELECT... [in template "analytics-container" at line 82, column 5] ----