L3 - Default User Story (Required on creation):
Timer durations can be based on expressions (e.g. calling a Spring bean that returns the time cycle). For repeatable timers (start or boundary events), it is currently not possible to update the cycle by re-evaluating the expression (e.g. on application restart). That requires that users deploy a new version of the process.
Functional Requirements (Required before implementation):
- There is an API that allows to reevaluate a timer job, including an update to the underlying time cycle configuration
- There is a configuration property in the Spring Boot starter that can be set to automatically update the timer configurations for resumed deployments
- i.e. if no new deployment was made due to duplicate filtering, the previously existing deployment's timer start events are updated according to the new API)
- This works for both deployment approaches of the Spring Boot starter (process application deployment and non-process-application deployment)