Radicore Forum
Fast Uncompromising Discussions. FUDforum will get your users talking.

Home » RADICORE development » Workflow » Why is Or-Split (Implicit) is limited only to 2 inwards arcs?
Re: Why is Or-Split (Implicit) is limited only to 2 inwards arcs? [message #5940 is a reply to message #5935] Wed, 05 October 2016 12:43 Go to previous messageGo to previous message
kong is currently offline  kong
Messages: 90
Registered: December 2011
Member
Thanks for the link.

After reviewing the information and some further digging, I have the impression these constraints put on the Implicit Or split (namely: 1. The number of arcs coming out must be two and 2. One of the outgoing arcs must go to a Timed Fired transition.) are more of a design decision that the folks at project-open made for their implementation of workflow engine rather than hard Petri Net rules.

Found a nice reference website http://www.workflowpatterns.com/ by the professors who did a lot of the research on this topic. The Implicit-Or Split is referred to as Deferred Choice http://www.workflowpatterns.com/patterns/control/state/wcp16.php and described as follows:Quote:
A point in a process where one of several branches is chosen based on interaction with the operating environment. Prior to the decision, all branches represent possible future courses of execution. The decision is made by initiating the first task in one of the branches i.e. there is no explicit choice but rather a race between different branches. After the decision is made, execution alternatives in branches other than the one selected are withdrawn.

It even gives this exampleQuote:
Once a customer requests an airbag shipment, it is either picked up by the postman or a courier driver depending on who can visit the customer site first.
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: How to deal with Implicit-Or Split limitations
Next Topic: How to fix?
Goto Forum:
  


Current Time: Tue Jul 09 20:54:29 EDT 2024

Total time taken to generate the page: 0.00973 seconds