AnsweredAssumed Answered

Using JUEL in timerEventDefinition is 'static'

Question asked by captain_kirk on Apr 29, 2015
Latest reply on Apr 30, 2015 by martin.grofcik
Hello we are using a timer start event to kick off a BP which is mainly used for sending email notifications. Currently we are using a JUEL expression as a poor mans CRON, i.e.

        <startEvent id="theStart">
            <timerEventDefinition>
                <timeCycle>${configurationService.getSendEvaluationRemindersTimer()}</timeCycle>
            </timerEventDefinition>
        </startEvent>      

which works perfectly fine. However we have observed that the job is bound to whatever value it was at deploy time. If we need to update the timeCyle we either redeploy the BPMN or delete it and add it back again.

Is there any other way we can reset the job to evaluate the JUEL expression again, kick the tires so to speak, whenever we want to change the CRON timer.

Thanks

Outcomes