Migrate custom process steps in asset processing workflow when migrating to AEMaaCS

[gallaghan6]

Hi all,

I am migrating an otb "asset update workflow" which has few custom workflow process steps such as metadata modification, property renaming etc.

What is the best way to migrate these custom workflow process steps to AEM Cloud such that post the processing of the assets by the microservices these process steps are executed?

your opinions would be appreciated @arunpatidar, @EstebanBustamante, @aanchal-sikka, @h_kataria, @Rohan_Garg 

[arunpatidar · Accepted solution]

Hi @gallaghan6 
In AEMaaCS, we use custom steps using post processing 

https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/assets/asset-mic... 

https://medium.com/@bsaravanaprakash/aem-assets-post-processing-workflows-a-savior-to-resource-chang... 

[gallaghan6]

and how should we handle any workflow launchers?

We have couple of BPA issues which go like - An enabled custom asset workflow launcher was found at /conf/global/settings/workflow/launcher/config/abc. It must be migrated for use in AEM as a Cloud Service.

[arunpatidar]

Hi @gallaghan6 
Please check 

https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/migration-journe... 

https://experienceleague.adobe.com/en/docs/experience-manager-learn/cloud-service/migration/cloud-ac... 

https://github.com/adobe/aem-cloud-migration/tree/master 

[Rohan_Garg]

You can create a new workflow which is a copy of the "Assets Cloud Post-Processing" workflow. (Refer Auto Start Workflows)

This workflow can contain all the process steps which are custom to the business requirements.

For the native steps to the OTB "Asset Update Workflow", most of the process steps are not required to be modified as the Asset Compute service takes care of them.

However, you can view list of workflow process steps which are native here at Workflow Step Properties and co-relate with the Supported workflows of the Asset Workflow Migration tool.

Hope this helps!

[gallaghan6]

Same question - what should be done to handle the workflow launchers?

[Rohan_Garg]

Just run the Asset Workflow Migration Tool to handle them as mentioned by @arunpatidar.

As long as they are disabled, the BPA report will not list them.

[EstebanBustamante]

I think it depends on what your custom process does, based on that, using the methods @Rohan_Garg and @arunpatidar should be the way to go. I could even explore if there is a chance to offload that processing from AEM.

Hope this helps

[gallaghan6]

Offloading that processing from AEM - the custom workflow processes are there to update custom metadata properties and updating few JCR properties.

[EstebanBustamante]

You could explore using I/O Events for that use case and get rid of the WF launchers and custom WF steps, even better, there is exactly that use case described on this page: https://experienceleague.adobe.com/en/docs/experience-manager-learn/cloud-service/aem-eventing/examp...

Hope this helps