And Gateway BUG?. bonita 6.3.1

1
0
-1

I imported some projects from Bonita 6.04 wich worked perfectly there and now it's showing this error: "All Incoming transactions must come from the same gateway (explicit or implicit)." The error is displayed in every "and" gateway that i use when all inputs must be received before the process can continue . if what the error is saying is right, then the documentation is wrong and i don't know how to do it, if it's not right then what? downgrade or wait for new version?

Thanks

In the link there is an image that i exported with bonita and since it's not showing the error, I coloured all 5 gateways throwing it. there is no loop and I think it's not too complex ... just very long https://www.mediafire.com/?7kgdl5jmm9rqzgt

http://www.mediafire.com/download/7kgdl5jmm9rqzgt/Diagrama+de+entrada+de...
4 answers

1
0
-1
This one is the BEST answer!

In my company is not strange that different branches do things at the same time and then have to wait for each other time and time again...

So i have this two easy fixes for what i think is a bug (I wasn't able to report it) . You can fork with AND GATEWAY send a signal when it's finished and catch it and then use AND Gateway for merging or you can use an INCLUSIVE GATEWAY to split and then an AND GATEWAY to merge. Both worked as expected

I hope it helps the community

1
0
-1

Appreciate some of the corrections but you are missing the bug

I reached the same error with this "simple" example and only 5 steps:

  • Step 1 and step 2 start at the begining,

  • Step 3 needs Step 1 and Step 2 finished

  • Step 4 needs only step 1

  • Step 5 needs Step 3 and Step 4 finished

i did it like I would on other bonita versions and got the same error, please explain me how i am supossed to acomplish or model this example, below its a picture of what i did and get error on gateway 1 and 3 http://www.mediafire.com/view/drud6roy549t9b3/BUG-1.0.png

I think Bonita is thinking that it's a loop but it's not a loop

Comments

Submitted by Pierre-yves Monnet on Wed, 07/02/2014 - 10:38

Hello, The second example is typicaly strange, and if bonita detect it, thank to it !

In this example, 1/ you have an explite AND between step 1 and Step 2. So, the you have 2 flow node at this moment. 2/ the Gateway 2 split the case in two : you have then 3 flow node 3/ the Gateway 1 expect at input 2 flow node to continue... but because the expected flow node is split by Gateway 2, I assume the engine will wait for ever at this moment. Let's imagine the engine can merge the 2 flow node. It continue on step 3 4/ on Gateway 3, engine expect two flow node, but the flownode splited at Gateway 2 not exist anymore : it is merged at Gateway 1... But it may be accept it and then you will have one flow node.

So, in that case, I really don't know how the engine can work. If it is based on only flownode attach to the case, it should works... if it mark the flownode in order to merge them, and because you split / merge them, it will not find the correct information.

Do you have a use case with this example ? In general, it's better to use EXPLICITE "and" Gateway.

Submitted by efrados on Wed, 07/02/2014 - 11:52

I think is not that strange, processes tend to split into different sections of the company and reunite at some tasks and that happens several times. I am not saying that is logical, that's the way they do it here so it's what i need to be able to do. The example doesn't work on bonita 6.3.1 if it's not a bug, can you give me an example that does what i asked and works? ( Step 1 and step 2 start at the begining, Step 3 needs Step 1 and Step 2 finished Step 4 needs only step 1 Step 5 needs Step 3 and Step 4 finished )

1
-1
-1

Ok, got it. 1/ ALL path from a Gateway AND must arrive to a Gateway AND. Your activity "MailMemoA3" does not respect this rule. 2/ the path vetween Copuerta3 to Compuerta5, and then again to Compuerta4 is very strange : do you really need the Gateway Compuerta3 ?? 3/ you have a Gateway Compuerta10 which do... nothing : why this Gateway ? 4/ the construction on activity mailMemo R8 is incorrect : you have a Rendez vous on Compuerta5, but the two path CAN'T BE FIRE AT THE SAME TIME : the path is then the normal one, else the Erreur Event trap (not both) : so in this Gateway, case is blocked.

Comments

Submitted by efrados on Fri, 06/27/2014 - 17:40

some corrections are ok but you are missing the point please check my last answer

1
-1
-1

Hello,

The engine verify on a AND Gateway that all the path arriving on this AND Gateway has no loop and have a correct AND Gateway which split the case. If you have a loop in your process between the two Gateway, you may have this issue. Could you share the process (take a picture for example, host it somewhere then share the link ?)

Note we detect in 6.3.x some use case where the design it too complex for the algorithm.

Comments

Submitted by efrados on Fri, 06/20/2014 - 19:08

i extended my question, please let me know what do you think asap

Notifications