AEM workflows | AEM 6.5

[shikhasoni1]

Which all paths we need to commit if we have done some changes in the existing workflow model. (What exactly get stored in /var and /conf)?  AEM 6.5

[Siva_Sogalapalli]

All the OOTB workflows are stored under "/libs/settings/workflow/models" and If you make any changes in the existing workflow model, then changes will be stored at "/conf/global/settings/workflow/models".  

Hope this helps. 

[VeenaVikraman · Accepted solution]

@shikhasoni1 Your WF model actually gets created under /conf, but if it creates a structure under /var which is also required (sync) else your model will not be editable when it is deployed .

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

When a user starts a workflow, an instance is started; this is the corresponding runtime model, created when you Sync your changes. 

The above is from the official doc, which means the one which created under /var is the runtime modal and without that we cannot edit the models.

For models without the runtime model inside /var , you will see Not editable in the model in RED

Hope this helps 

Veena ✌

[lukasz-m]

Hi @shikhasoni1, I think you should commit both paths /var and /config.

Here is the main reason why: under /config you are storing your workflow models as a base, but under /var you are storing executable version of your model.

When you will run new instance of workflow executable version, so the one stored under /var, it will be used to create new workflow instance. If you will not keep your /var updated you will end up with state that outdated workflow models are used. It is also good to keep /conf and /var in sync, and again without committing /var you will need to manually sync (e.g using GUI) model definition from /conf to its executable form stored under /var.

You can also have a look into Adobe documentation - [1] - it clearly indicates that you should take care of both /var and /conf.

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