Control Parameters for Activities - Receive Message Task and Any Activity With Inbound Message Flow

[GoogleCodeExporter]

We say that interTriggerTimer and triggerCount apply to Activities that are 
initiating the process (Event Subprocesses being a special case unto 
themselves) in the sense that they do not have incoming Sequence Flow but 
"start" a process by ramping up in Activity States from Ready to Active (and 
thus launching off the process instance).

In the case of Task, this only works if the Task is like that - i.e., that it 
only works as the first thing in the process (and thus without incoming 
Sequence Flow).  However, this would appear to conflict with the the behavior 
of the Receive Message Task or any Task that had an inbound Message Flow.

- Receive Message Task:  This Task Type really can't fire until the inbound 
Message is received, which if this were an Intermediate Catching Message Event 
(its event analog in key aspects) would have interTriggerTimer associated with 
it.  So, to be consistent, the Receive Message Task should also have it, 
regardless of whether or not there is a Message Flow attached to it.

- Task:  Any Task Type with an inbound Message Flow would appear to have an 
input requirement that must be satisfied before the Activity State can move 
from Ready to Active.  This would seemingly require an interTriggerTimer as 
well, but the case for allowing its use here may turn on how whether we want to 
support simulation with loosey-goosey (technical term, ;-)) use of Message 
Flows.

In the case of other Activity Types (i.e., not a Task), the presence of an 
inbound Message Flow would appear to suggest itself as well.  Again, the case 
for allowing use of interTriggerTimer here may turn on how we want to support 
simulation with the use of Message Flows.

Recommedation:  Receive Message Task is = Intermediate Catching Message Event, 
so it gets interTriggerTimer.  As to the others, let's dicuss?

Original issue reported on code.google.com by ldugan.b...@gmail.com on 27 Dec 2012 at 4:17

[GoogleCodeExporter]

Original comment by ldugan.b...@gmail.com on 27 Dec 2012 at 4:21

[GoogleCodeExporter]

Version 1.0 of BPSim does not go down to the level of task types. To emulate 
the delay introduced by waiting for the message to arrive Time Parameters 
introducing LAG can be used for that purpose 

Original comment by dga...@trisotech.com on 15 Jan 2013 at 2:26

• Changed state: WontFix