nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

TimerBoundaryEvent - AutoComplete task when timer expires

sredrouthu

Hi,

For a TimerBoundaryEvent, when cancelActivity is "false" and "activiti:endDate" is specified, can the original process be ended? I still see the task is assigned to the respective user.

If there is a repeating job along with the end date, TimerBoundaryEvent is not creating other jobs when it reach the end date. Along with this, our requirement is to end the original process when the timer expires.

Thanks in advance.

Find more posts tagged with

Accepted answers

gdharley

Ok thanks for the details.
So if I understand correctly.

After the Boundary Event Timer fires the 20th time you want to cancel the attached task.
If this is what you need, then you could add a counter to the boundary event either as a script task or execution listener. After you hit the last timer, throw a signal to cancel the original task.

See simple example below:

Obviously you can streamline this by throwing the signal inside the timer event boundary listener and checking the count there, but the basic approach is the same.

All comments

gdharley

If your goal is simply to close all open tasks after the timer boundary event fires, then have the flow do it's necessary cleanup work then end with a "Terminate End Event" rather than a none end event. This will close all open jobs and tasks.

Perhaps I am missing something, if you could post your process with a description of your desired goals, it may help.

Thanks,

Greg

‌

sredrouthu

Greg,

Thanks for your reply.

TimeCycle R20/PT2S will fire for every 2 seconds and 20 times (cancelActivity is set to false). When ever the timer fires, we have a service class that do some job. After the timer gets expired, we have to end the current process / task (not all the open tasks or jobs).

Thanks

vasile_dirla

Hi,

"If there is a repeating job along with the end date, TimerBoundaryEvent is not creating other jobs when it reach the end date"

could you provide a unit test for this scenario? (or at least the bpmn20.xml file of the process) it will help for reproducing the issue.

Thanks.

sredrouthu

"If there is a repeating job along with the end date, TimerBoundaryEvent is not creating other jobs when it reach the end date (after the timer expires)" which is expected and is working as the same and we don't have any issue with this.

After the timer expires, User Task is still open. Need help on ending the current process.

vasile_dirla

what about such a construction, is it solving your needs?

sredrouthu

How can we cancel a user task in Script Task?

gdharley

Ok thanks for the details.
So if I understand correctly.

See simple example below:

Obviously you can streamline this by throwing the signal inside the timer event boundary listener and checking the count there, but the basic approach is the same.

gdharley

Check the signal approach I just posted.

vasile_dirla

Is not mandatory a script task; you could use a service task which will give you a lot of power while is also very easy to develop the java code.

in the same time you could consider also the solution Greg posted "signal based solution" which I really like.

sredrouthu

Signal throw and catch worked! Thanks for your help!