Non interruptive boundary timers: why they are not repeatable ?

1
0
-1

Hello,

It seems a common situation to have to remind about a task several times, for example: (A) after 1, 3, 7 days, or sometimes (B) every 2nd day after some initial delay.

For such a reminder, it is better to use a non interruptive boundary timer (instead of an interruptive timer that would eventually start again the task), because the task remains active and one knows when it originally started, it keeps its task variables, the link to the task remains valid, etc.

But the boundary timers cannot be repeatable, nor can have several successive delays. Thus the designer must in case (A) define on his task one timer per delay, which can be confusing and heavy, or in case (B) it is not possible.

My questions are: - Why this choice ? - Why not a flexible, programmable kind of timer with the ability both to repeat regularly the event and to use a list of periods ? - Is it possible to use one's own implementation of a non interruptible boundary timer ?

My Bonita version: Community 6.5 but as far as I could see, nothing changed in Bonita 7.0.

Thank you.

1 answer

1
0
-1
This one is the BEST answer!
  1. As far as I know these are NOT Bonita choices. these are the choices of the Standard...
  2. As far as I know the standard doesn't allow this...
  3. Of course if you write it...why not?

you can read the standard here:

http://www.bpmn.org/

regards

Comments

Submitted by michel.rv on Wed, 08/05/2015 - 18:52

Ok I see. Thank you.

Fortunately in some other cases Bonita slightly relaxes some rules of the standard which makes it possible to build actual workflows and not only theoretical ones.

Notifications