Migrate custom process steps in asset processing workflow when migrating to AEMaaCS | Community
Skip to main content
July 24, 2024
Solved

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

  • July 24, 2024
  • 3 replies
  • 2095 views

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 

 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

3 replies

July 24, 2024

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.

Rohan_Garg
Community Advisor
Community Advisor
July 24, 2024

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!

July 24, 2024

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

Rohan_Garg
Community Advisor
Community Advisor
July 25, 2024

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
Community Advisor and Adobe Champion
Community Advisor and Adobe Champion
July 24, 2024

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

Esteban Bustamante
July 24, 2024

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

EstebanBustamante
Community Advisor and Adobe Champion
Community Advisor and Adobe Champion
July 24, 2024

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/examples/assets-pim-integration

 

Hope this helps

Esteban Bustamante