0

We are facing an issue with Camunda orchestrator restarts.

We lose all decision rules of DMNs after deploying new versions of processes.

Could you please suggest if possible an out of the box solution to save rules and reload them after restart, if not possible an explanation of how to do it is OK also ?

Thanks

Lho Ben
  • 2,053
  • 18
  • 35

2 Answers2

1

I guess you have one version of the dmn in your src/main/resources, so it's auto deployed on start ... and then deploy updated versions "on the fly" via REST.
You have to update the table in resources as well or disable auto-deployment to not overwrite your ad-hoc changes again.

Jan Galinski
  • 11,768
  • 8
  • 54
  • 77
  • thanks Jan, You mean, that we add rules also in src/main/resources? in this case we will need to restart the application for every change. could you please suggest another way, ? maybe saving the config in a database, is there an "out of box" way to do it ? if you can point an article that will be nice. thanks – Lho Ben Aug 29 '20 at 21:44
  • 1
    The problem is your mixed mode. If you have dmns in your resources, and auto-deployment active, they will be deployed and overwrite your changes. So either you ensure that the dmns in resources are the latest versions ... or you remove them from resources completely and rely solely on runtime changes. – Jan Galinski Aug 31 '20 at 11:38
1

Please also see: Camunda load BPMN XML from database

The same explanation applies to any kind of model (BPMN,DMN,CMMN)

rob2universe
  • 7,059
  • 39
  • 54