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

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

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.

no, its overlay only

deploying the latest version worked by adding change in package-lock.jsonthanks @Rohan_Garg 

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 the...

For 1 yes, its only the ws module which gives error of 403.For 2, I am not able to access the page using my domain credentials. The .npmrc file has the credentials.For 3, the version is present in package-lock.json, I will need to first host it on JFrog first?"node_modules/ws": { "version": "8.16.0...

The permission issue should have been valid for all the other artifacts too.

There is a npmrc file which is configured and downloading artifacts for other node modules but only this one for web socket is giving an issue.