psavidis
commented
4 months ago Hello @mixaaaa ,
Thanks a lot for your interest to share with us your work! 👍
Mandatory History Time to Live upon Deployment
We decided to go with making the History Time to Live mandatory upon deployment for backwards compatibility sake and to give our users the possibility to turn it off on demand. This was a conscious decision during the define phase of the feature.
As a result of the above, we cannot consider the suggested behaviour to the product as it would be a decision will plenty of side effects for our users.
For your use case
- For newly created process definitions, you can always use the process engine
historyTimeToLiveproperty. - For the existing process definitions, a migration idea would be to deploy a new version of them with the set
historyTimeToLiveand migrate the existing versions to the new version :)- Another alternative is to set to all the process definitions a
HTTLone by one via the REST or Java API using the engine'shistoryTimeToLivenewly set property.
- Another alternative is to set to all the process definitions a
I hope the above info give you an insight on how to handle your use case. Since this feature can't be considered further, i'm closing this ticket.
Thanks a lot for your interest, Petros
mixaaaa
User Story
As we are writing some spring boot applications based on camunda 7 starting long time before history time to live was mandatory in the processes we just started to set enforce history time to live to false to be able to update and still run processes. Even more in our case the problem is that the TTL is always ProcessDefinition related and not configurable via (for example) spring boot properties. For example in our dev environment we delete process related information after five days but in prod we keep it a year.
So taking a deeper look at the ProcessEngineConfigurationImpl i recognized that there is a default time to live which is already used in many cases but not for process related stuff. So my idea would be to use this history time as second configurable option for history time removal.
Functional Requirements (Required before implementation)
Technical Requirements (Required before implementation)
Limitations of Scope
Hints
I justed forked this project and make some small adjustments which not completely use your styling guidelines. I would revert and correct that and even write tests if you are interested in this feature. If not i will just throw it away ;)
Links
Dev2QA handover