Hello everyone,
I have an issue with a model we use in our application,
We have 3 timers on a user task (one for reminder every 2d one for closing after 30d and one for tracking every 4h)
the issue is one leaving the user task to call a service task we loose job timers of 2d and 30d
and one the gateway return back to the user task these two timer are recreated so due date is beeing wrong.
if we use a non interrupting timer we could have 2 actif user task if the gateway lend us to the second user task.
Is there a trick that can be used in this case to not loose timer jobs.
Thanks
Hi @sfaxianovic,
the times are always dependent on the user task instance. Once it is completed, the jobs are deleted. If you go back into the task, the engine will create a new instance with new jobs.
You can calculate the due dates beforehand and save them in process variables. With an expression, you can set them in the next round to same values as before.
You can also try to use timeout task listeners: https://docs.camunda.org/manual/7.14/user-guide/process-engine/delegation-code/#task-listener. Technically they can call the java logic without cluttering the process diagram. But it is a matter of taste.
Hope this helps, Ingo
1 Like
Thanks @Ingo_Richtsmeier for the response, I will use the first solution to put due date into variable