AEMaaCS how to replace Metadata Processor step in workflow

[IshaJa]

We're migrating workflow models from AMS to AEMaaCS, and some of our workflows used the Metadata Processor step which is no longer supported in AEMaaCS. In our workflow models, the Metadata Processor step is followed by custom workflow process steps to add some custom metadata properties.

I saw this article which describes how to apply a workflow model to a folder, but I'm a little unclear on what exactly needs to be done to replace the functionality of the Metadata Processor: https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/assets/manage/as...

To replace the functionality of the Metadata Processor, would we need to create a Metadata Profile with out custom metadata properties for our custom workflow process steps to work? Or would auto-starting the workflow on a folder be enough for our workflow models to work as before? 

Additionally, is there a way to apply a workflow model to the dam folder itself, or only folders within dam?

Appreciate any help and/or resources.  

[arunpatidar]

Hi @IshaJa 
You can use processing profile for metadata update

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

[IshaJa]

Hi @arunpatidar, this doesn't really answer my question. The issue is that in the workflows I am migrating from AMS to AEMaaCS, they use custom workflow process steps after the Metadata Processor Step, and I want to know if we can keep using these custom workflow process steps (written in java) or if we need to make changes to the code.

Also, I already included that source in my initial post, but I am asking for clarification.

[IshaJa · Accepted solution]

Actually nvm, I figured it out on my own. There was no need for code changes.