Stumble here while drooling...
I am not familiar with Drools.Net rule engine but in general Windows Workflow Foundation comes with a rules engine, which is not replaceable. You could create a custom activity condition, see blog post here , but it you would not be able to use it with the out of the box activities that have conditions, e.g. while, conditioned activity group & if else branch.
So essentially you are saying that I cant plugin any third party rules engine like ILOG, InRule, Blaze or open source like NxBRE, Drools. Is there a particular reason why its not possible. Does it mean that the rules that is bundled with Window Workflow is tightly coupled and there is no way to replace it
Answer :
Correct, Windows Workflow Foundation (WF) ships with a rules engine and it is not replaceable. However, you can create custom conditions that can call your custom rules engine. You can use the custom conditions with any activity but within VS you won't be able to set any of the out of the box activities to use your custom conditions. What I mean by this is you currently get "Code Condition" & "Declarative Rule Condition" in the dropdown for condition properties, you can't add "Custom Condition" to the out of the box activities.
more
Tags:
1 comments:
Its true that conditional transitions in WF are tied to the WF Rules implementation; however, ILOG's Rules for .NET integrates as an activity.
A BRMS manages the state of data and the outcome of a complex decision. Once it is complete, the WF Rules engine can be used to look at the data within the context of the process and make simple decisions about how the process should continue. WF Rules in this case, compliments the use of a full BRMS within the context of a process.
Chris Berg
Product Manager, ILOG
http://www.ilog.com/dev/brms/rfdn/
Post a Comment