Radicore Forum
Fast Uncompromising Discussions. FUDforum will get your users talking.
Home » RADICORE development » Workflow » How to deal with Implicit-Or Split limitations
Re: How to deal with Implicit-Or Split limitations [message #5949 is a reply to message #5947] Thu, 06 October 2016 07:21 Go to previous messageGo to previous message
AJM is currently offline  AJM
Messages: 2386
Registered: April 2006
Location: Surrey, UK
Senior Member
The more I read this post the more I realise that what you are trying to do is perfectly logical, yet my implementation does not allow it. I have gone back to my original reference material at http://martinfowler.workflowpatterns.com/documentation/docum ents/vanderaalst98application.pdf and I now see that my implementation is too restrictive. I shall start work on modifying it so that an Implicit-OR-split can have more than 2 arcs, and that it need not have a transition with a TIMER trigger. I will post the updated code here as soon as I can.

Tony Marston
http://www.tonymarston.net
http://www.radicore.org

Report message to a moderator

[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Work item assignments
Next Topic: Why is Or-Split (Implicit) is limited only to 2 inwards arcs?
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Mon Nov 03 12:09:32 EST 2025

Total time taken to generate the page: 0.01265 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.2.0.
Copyright ©2001-2025 FUDforum Bulletin Board Software