Hi Everyone,

I am trying to use drools 5.5.0 to provide approval/denial for a case.  The best way to represent our business logic is through a workflow where the user-inserted facts get processed in a particular step, and the RHS of the rules in that step insert new facts for the next step in the flow, until, at the end, a decision fact is generated.  Looking at the Drools Expert tutorial, this is very similar to the driver license application, except that mine has a jbpm flow.  As such, I have been using a stateless session to get my rules to work.  

Until recently, I have been working on this problem as a local drools expert solution, referencing the rules engine and the rules package directly.  However, the final step was going to be to move this solution to drools server so that the business logic could be accessed through a RESTful interface.  I assumed that the main functionality available in the drools rules engine would remain in drools server. However, when I saw the following post, I became concerned that perhaps the functionality I took for granted in Drools Expert does not exist in Drools Server.  The post was recent and has not gotten a response, but if the response is indeed that stateless sessions do not work with rule flows in drools server, I was wondering if anyone had a suggestion for how I would tackle my workflow problem.  Is there another way in drools server (other than salience) to get different sets of rules to execute in a particular order and come up with an answer at the end of the work flow?

Best,

Yuri

PS. I have been able to reproduce the scenario described by the user in the post above.