How to store custom workflows and launcher into codebase

[manlosa2]

Hi there, 

    What is the best practice in storing workflows and launcher configs into your github repository?

Thanks,

-Leo

[Avinash_Gupta_ · Accepted solution]

@manlosa2 : Custom workflows model and launchers need to created under this path /conf/global/settings/workflow. Same folder path would need to be created in your repo as well.

Here is the link for extending the workflows and create a custom workflow https://experienceleague.adobe.com/docs/experience-manager-65/developing/extending-aem/extending-wor... 

Hope this helps.

[Mani_kumar_]

Simple Funda for committing the changes to git for anything in AEM is take the package for those content extract the zip once package is downloaded and then copy the structure in the respective project folder.

Add the filter in the module filter.xml to make sure it is available in the next deployment.

[manlosa2]

Thanks, Manikumar. This gave me the clarity I needed.

[Mayank_Gandhi]

@manlosa2 

Custom workflow models can be kept under /conf/global/settings/workflow/models/<My Project>/MyCustomWF

Locations - Workflow Models

Workflow models are stored in the repository according to type:

• Out-of-the-box workflow designs are held under the following path:
  /libs/settings/workflow/models/
  Do not:

  • place any of your custom workflow models in this folder
  • edit anything in /libs

  As any changes may be overwritten at upgrade or when installing hot-fixes, cumulative fix packs or service packs.
• Custom workflow designs are held under:

  /conf/global/settings/workflow/models/...
  
  
  

• Runtime workflow designs (both out-of-the-box and custom) are held under the following path:
  /var/workflow/models/

here is adobe best practice for Workflows:

https://experienceleague.adobe.com/docs/experience-manager-65/developing/extending-aem/extending-wor...

[manlosa2]

Thank you everyone.