Effective dated process definitions


I wonder, if it is already implemented somewhere(I believe it is quite popular requirement) to have the ability to have effective dated process definitions, ie one entity called for example Process and few ProcessDefinitions attached to it, which have different effective periods.
Like first will be valid from 01-01-2000 to 31-12-2018 and second will be valid from 01-01-2019 to 31-12-2099?

UPD: I’ve found docs about process definitions versioning in both Flowable and Camunda:
But I have a bit different situation, which IMHO is real world need - to find(and start) process with effective date provided.
So obviously effective period should be present - starte and end dates(nullable) - in ProcessDefinition(for those, who don’t use effective dates they can be set to null) and then there are 2 options:

  • unique constraint in ProcessDefinition should include key and effective period
  • new table called Process should be created and key should be moved from ProcessDefinition to that table


Hi @simonovdenis,

There is currently no such features. The closest to this would probably be activating/suspending process definitions based on the time periods you like, where this is the corresponding API: https://docs.camunda.org/javadoc/camunda-bpm-platform/7.9/org/camunda/bpm/engine/RepositoryService.html#activateProcessDefinitionById(java.lang.String,%20boolean,%20java.util.Date). You could also think about modeling a process that does this.



Thanks for answering.
Is there any plans on implementing it?


There are no plans at this point.