Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

Adobe Summit 2023 [19th to 23rd March, Las Vegas and Virtual] | Complete AEM Session & Lab list
SOLVED

AEM workflows | AEM 6.5

Avatar

Level 4

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

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

@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

 

Veena_Vikram_2-1646819842999.png

 

 

Veena_Vikram_0-1646819527993.png

Veena_Vikram_1-1646819645461.png

 

Hope this helps 

 

Veena ✌

 

View solution in original post

0 Replies

Avatar

Community Advisor

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. 

Avatar

Correct answer by
Community Advisor

@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

 

Veena_Vikram_2-1646819842999.png

 

 

Veena_Vikram_0-1646819527993.png

Veena_Vikram_1-1646819645461.png

 

Hope this helps 

 

Veena ✌

 

Avatar

Community Advisor

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

The ultimate experience is back.

Join us in Vegas to build skills, learn from the world's top brands, and be inspired.

Register Now