topic timerEventDefinition and process runs upon startup in Alfresco Archive

timerEventDefinition and process runs upon startup

sanjiv — Tue, 09 Jul 2013 19:01:41 GMT

I'm trying to setup a simple workflow that causes one of the API's on a bean be invoked at 3:30, 4:30 and 5:30pm.I'm using the code below but what I'm seeign happen is that when the code runtimeService.startProcessInstanceByKey() is invoked, the process runs immediately as I see that mySerivce.proce

Re: timerEventDefinition and process runs upon startup

frederikherema1 — Wed, 10 Jul 2013 07:33:34 GMT

If you have a timer-start event, there is no need to call "startProcessBy…". If a process with a timer-start-event is deployed into the engine, this timer-job is added and the process will be started on the scheduled time(s).

This is mentioned in the user guide, maybe good to read the relevant sections first (http://activiti.org/userguide/index.html#bpmnTimerStartEvent😞

Note: start timer event is scheduled as soon as process is deployed. There is no need to call startProcessInstanceByXXX, although calling start process methods is not restricted and will cause one more starting of the process at the time of startProcessInstanceByXXX Invocation.

Re: timerEventDefinition and process runs upon startup

sanjiv — Wed, 10 Jul 2013 14:12:42 GMT

That works, thank you. I was hoping to use a process variable like <timeCycle>${duration}</timeCycle> but the process variables are passed when calling startProcessInstanceByXXX. Is there any way to use process variables with a timer start event?

Thanks,
Sanjiv

Re: timerEventDefinition and process runs upon startup

jbarrez — Fri, 12 Jul 2013 06:58:08 GMT

No. Also, how would you know what to pass when the timer fires?
If the variables are predefined, you can attach an execution listener that adds these variables after the start event.

Re: timerEventDefinition and process runs upon startup

sanjiv — Fri, 12 Jul 2013 13:17:25 GMT

Yes, the variables are predefined. I'll look into it, thanks.