Heiko Tappe [https://community.jboss.org/people/tdtappe] created the discussion "Re: Migration from 4.3 to 5.2" To view the discussion, visit: https://community.jboss.org/message/732460#732460 -------------------------------------------------------------- In addition to what I said already maybe I should explain in more detail what I like to achieve. Because I would like to know how this should be done with jBPM 5.2 (BPMN). In my app I create some object (like an order). I then start some process on this object. The process might detect that some further processing is possible (sending an email, print the order, etc). So it's done. But sometimes for further processing some conditions have to meet. Then the process has to wait until the conditions are fulfilled. As the objects (the orders) can be edited in the app at every time I want to notify the process after a modification to check for further processing. If further processing is possible the process proceeds until the next condition has to be fulfilled (or the process ends). This worked fine with jBPM 4.3 working with state nodes and decisions. After each modification I signaled the process (with a null signal). The process then checked whether a further processing was possible or it stayed in "wait mode". -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/732460#732460] Start a new discussion in jBPM at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&...]

Heiko Tappe [https://community.jboss.org/people/tdtappe] created the discussion "Re: Migration from 4.3 to 5.2" To view the discussion, visit: https://community.jboss.org/message/733741#733741 -------------------------------------------------------------- Thanks Maciej. I went for the Drools approach with conditional events. And it works :) Well - kind of. The problem is: how does the rule refer only to those facts that belong to this process? Did I make myself clear enough? For instance one of my conditions looks like this: Order(tasksComplete == true) But of course this fires for each process instance as long as there is at least ONE order fact in the whole knowledge base that has its tasks completed. It probably should look something like this (pseudo code): Order(tasksComplete == true, id = process.getVariable("orderId")) I know that some time ago I saw some thread somewhere about a similar topic. But I can't find it any longer :(( IIRC it was about inserting the WorkflowProcessInstance as a fact and include it into the LHS of the rule!? Is this the way to go? And how exactly would I have to do it? -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/733741#733741] Start a new discussion in jBPM at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&...]

Heiko Tappe [https://community.jboss.org/people/tdtappe] created the discussion "Re: Migration from 4.3 to 5.2" To view the discussion, visit: https://community.jboss.org/message/733777#733777 -------------------------------------------------------------- I see. And how do I have to put the process instance into the knowledge base? -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/733777#733777] Start a new discussion in jBPM at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&...]

Heiko Tappe [https://community.jboss.org/people/tdtappe] created the discussion "Re: Migration from 4.3 to 5.2" To view the discussion, visit: https://community.jboss.org/message/733785#733785 -------------------------------------------------------------- Oops, missed that one :8} Thank you so much! -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/733785#733785] Start a new discussion in jBPM at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&...]

Heiko Tappe [https://community.jboss.org/people/tdtappe] created the discussion "Re: Migration from 4.3 to 5.2" To view the discussion, visit: https://community.jboss.org/message/734019#734019 -------------------------------------------------------------- As for the second item: Being quite a newbie to drools/jbpm stuff I might not have the right understand of things... but thinking about it: isn't it logical that every process proceeds if the condition described above resolves to true? It's just looking for a match in the knowledge base: a process with a variable "orderId" and an order with that id and tasksComplete being true. Of course there is only one match but it will fire for every process. If there was a "then" part and it would depend on the "then" part which process to proceed then it could be done this way. But whithout!? -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/734019#734019] Start a new discussion in jBPM at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&...]

Maciej Swiderski [https://community.jboss.org/people/swiderski.maciej] created the discussion "Re: Migration from 4.3 to 5.2" To view the discussion, visit: https://community.jboss.org/message/734058#734058 -------------------------------------------------------------- could you please provide your example as test case together with process definition (bpmn2) so I could take a look at it and play around for a while. -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/734058#734058] Start a new discussion in jBPM at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&...]

Heiko Tappe [https://community.jboss.org/people/tdtappe] created the discussion "Re: Migration from 4.3 to 5.2" To view the discussion, visit: https://community.jboss.org/message/734103#734103 -------------------------------------------------------------- Sent a test project to your private email address. HTH to clarify things. Tell me if you need more information. -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/734103#734103] Start a new discussion in jBPM at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&...]

Heiko Tappe [https://community.jboss.org/people/tdtappe] created the discussion "Re: Migration from 4.3 to 5.2" To view the discussion, visit: https://community.jboss.org/message/734060#734060 -------------------------------------------------------------- Ok, now I am quite sure that it must be related to JPA persistence. Turning persistence off shows an absolutely expected behaviour. At least for having two separate knowledge bases and sessions. Inspecting it in more detail... I will report back. -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/734060#734060] Start a new discussion in jBPM at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&...]

Maciej Swiderski [https://community.jboss.org/people/swiderski.maciej] created the discussion "Re: Migration from 4.3 to 5.2" To view the discussion, visit: https://community.jboss.org/message/734095#734095 -------------------------------------------------------------- First of all, knowledge base is a runtime representation of your processes, rules, etc so there is no need to have two of them especially in terms of execution. For execution you use sessions that you can create as many as you want from the same knowledge base and these sessions are independent from each other, they share same definitions but that's it. So in your case you could create two session each for every process instance you're currently testing. Just make sure you put the facts into both sessions. Nevertheless, I do think it should be possible to achieve this with just one session, as I don't know all the details of your scenario here is a generic one: * write your rules to be aware of unique identifiers (for instance order id) * start process instance to handle an order, it will get unique order id as process variable * if needed modify the facts that your process instance operates on so it won't be hanging around if they are already processed. An example of the condition could be like this (please note I did not test it so could be not 100% executable)         o: Order()         p: WorkflowProcessInstance()         String( this == o.orderId ) from p.getVariable("OrderId") HTH -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/734095#734095] Start a new discussion in jBPM at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&...]