how can you migrate workflows in AEMaaCS without workflow migration tool?

[gallaghan6]

hi all,

we have a restriction wherein we cannot run the aem workflow migration tool due to security constraints for aio npm plugins.

Reffered Asset Workflow Migration Tool | Adobe Experience Manager

What is the alternate way to do so? BPA has flagged issues related to the workflow launchers being enabled.

thanks,

[h_kataria]

The workflow migration tool is offered as a standalone utility as well. Essentially you can just download the jar and run it on your project directory https://github.com/adobe/aem-cloud-migration/releases/tag/v0.6.0 
Has that been considered as well ? 
If that is also not feasible, last option would be to do the required steps (https://github.com/adobe/aem-cloud-migration/blob/master/README.md whatever is relevant) manually.

[Rohan_Garg · Accepted solution]

Custom workflow runner will replace the workflow launchers to execute workflows upon the completion of processing via the Asset Compute Service and Dynamic Media.
Please note even with the utility any complex workflow with split (OR, AND etc.) will not be able to be transformed 100%. You still might need to manually inspect and upgrade these configurations.

Please refer to the link posted by @h_kataria  as that dictates the common steps needed to manually transform workflow code - 

• Separation of mutable and immutable areas by creating separate maven projects and including them in the build sequence.
• Launchers will need to be handled via the Custom Workflow Runner service.
• Remove all unsupported steps and to add the DAM Update Asset Workflow Completed Process step where needed.
• Create an OSGi configuration for the Custom Workflow Runner.
• Creating processing profiles

Usually this is the sequence of steps that the migration script follows and will need to be followed in your custom workflows as well.

Hope this helps!

[gallaghan6]

I run the utility with the following results - 

• No Maven projects were created, No workflow launchers were disabled, No workflow runner configurations were created, No workflow models were modified and No processing profiles were created.

# Migration Issues

These issues were encountered while migrating the project by workflow migration tool.

No issues were encountered.

[Rohan_Garg]

Great! That's all you need! Now if you go to your repo and see the "git status" - If no files are present then your workflow is ready for AEM Cloud!

[kautuk_sahni]

@gallaghan6 Did you find the suggestions from users helpful? Please let us know if you require more information. Otherwise, please mark the answer as correct for posterity. If you've discovered a solution yourself, we would appreciate it if you could share it with the community. Thank you!