Expiration date set

1
0
-1

Excuse me, I need a human task to no longer be available when a boundary timer event triggers.
I have set the execution time to a time limit, at the same time the boundary triggers(2 minutes).
But even when the boundary time triggers, there's still avalible the task, so there can be 2 sequence flows; that's bad.

What I want:
the human task is available.
if the task is not done in 2 minutes the boundary time will trigger advancing to the next task
if the boundary time triggers, the task should no longer be available.
Bonita Comunity 7.3.3

![][]

2 answers

1
+1
-1
This one is the BEST answer!

I think you just need to use a interruptive-boundary timer instead of a non-interruptive one.

Comments

Submitted by jmpico on Fri, 02/10/2017 - 15:08

thank you, I'm a little bit newbie. . . maybe too much

1
0
-1

The boundary timers do indeed terminate the user task (at least, they do in 7.3.2). I use this technical extensively.

Can you provide some more detail?

For example:
1: check the task ID number before and after the timer - are they the same (the task wasn’t aborted) or are they different (in which case, the task has been restarted by something in your process).

2: Are there any errors in the logs?

Comments

Submitted by jmpico on Fri, 02/10/2017 - 15:12

thank you, I solved it: it was just a non-interrupted timer, and i needed a siple boundary timer.

Thank you for your help.

Notifications