Dynamic start timer value

[StephenOTT]

Fun use case!

Take a look at this:

Timer Start Event change after process deployment

It is correct as @jangalinski says that you can use an expression for the timer. However after the process instance has been created a change in the object bound to the timer will not be reflected in the timer itself. To change it runtime you would need to do it like this: /** * Sets a new value for a timer * * For use if there is only one timer in the process. Will fail if there is more than one timer with the given name waiting at runtime for the process * instance * * @param processIn…

and

Timer Start Event change after process deployment

if you use spring or cdi, you can specify an expression for the timer cycle intead of a fixed value. just use any bean in your context that returns a valid ISO cycle code. Then, that bean can dynamically determine the required value, for exampel by accessing configuration properties or environment variables. Note that this will not change an already created job, so changes will only apply to the next job in the cycle.

You can update the runtime with their code snippet. And if you update the previous versions as stated in the expression.

edit: updated with cleaner version as there was the runtime snippet already provided