2:03 a.m.
Hello,
I'm trying tp understand how does the Rule Set works and I'm experiencing
some problems. I need it to stop
when the process finds a 'rule set' and it doesn't match with the
conditions, however, the process continues even the facts do not fulfill the
conditions.
Can someone explain me how does the 'rule set' works or can u give an
example?
thank you very much
--
View this message in context:
http://drools.46999.n3.nabble.com/RuleSet-RuleFlowGroup-tp3165058p3165058...
Sent from the Drools: User forum mailing list archive at Nabble.com.
7:56 a.m.
Hi,
The thing you explain is actually the expected behaviour. If the process
encounters a rule task, it will examine all rules inside the ruleflowgroup
in question. Rule execution continues until no more matching conditions are
found. From then on, the process continues to the next task.
If you would like to stop the process based on some business rules, you will
have to guide it towards a terminate node or kill it by calling the API.
Guiding towards a terminate node can be done with the help of decision
gateways and (rule) outcomes. The code to kill it via the API can be found
in the documentation.
Regards,
Frank
rchemisa wrote:
Hello,
I'm trying tp understand how does the Rule Set works and I'm experiencing
some problems. I need it to stop
when the process finds a 'rule set' and it doesn't match with the
conditions, however, the process continues even the facts do not fulfill
the conditions.
Can someone explain me how does the 'rule set' works or can u give an
example?
thank you very much
--
View this message in context:
http://drools.46999.n3.nabble.com/RuleSet-RuleFlowGroup-tp3165058p3165831...
Sent from the Drools: User forum mailing list archive at Nabble.com.
8:57 a.m.
Ty so much for answering FrankVhh,
I dont understand if you can stop the process (just wait) in the Rule Set
waiting to be inserted in the session some fact that makes the rules
associated conditions are met (the result of the conditions true)
So, the "Rule Set" act as a Wait State but may outsource the rules in the
drl.
Regards
--
View this message in context:
http://drools.46999.n3.nabble.com/RuleSet-RuleFlowGroup-tp3165058p3166044...
Sent from the Drools: User forum mailing list archive at Nabble.com.
10:43 a.m.
A rule engine will reason upon all the facts that are in its working memory,
no matter what facts are in there. Therefore, it can not natively know
whether it has "enough" facts, neither does it (natively) know which facts
are missing. Call fire all rules, the engines starts thinking and will stop
thinking from the moment there are no more rules that are matching. Whether
the "results" make sense or not... well, it actually doesn't care.
In theory, you should provide all necessary facts before calling the rule
engine. I.e. add a task/step before calling the engine to collect all
missing facts.
In practice, you are able to "hack the philosophy", as the THEN part of a
rule is pure JAVA code, you can pretty much do what you want and add a
rule/rules that go after the required inputs (WHEN not veryImportantObject()
THEN getMyVeryImportantObject();END
Does this make sense to you?
Regards,
Frank
rchemisa wrote:
Ty so much for answering FrankVhh,
I dont understand if you can stop the process (just wait) in the Rule Set
waiting to be inserted in the session some fact that makes the rules
associated conditions are met (the result of the conditions true)
So, the "Rule Set" act as a Wait State but may outsource the rules in the
drl.
Regards
--
View this message in context:
http://drools.46999.n3.nabble.com/RuleSet-RuleFlowGroup-tp3165058p3166451...
Sent from the Drools: User forum mailing list archive at Nabble.com.
10:52 a.m.
Drools 5.1 has a StateNode (Wait) that will wait for a rule to
evaluate to true before proceeding on one of its outgoing connections.
Each outgoing connection can have a different constraint.
I don't know what the equivalent node type is in JBPM5 since BPMN2
doesn't support an equivalent node type AFAIK.
Regards,
Dan Nathanson
On Wed, Jul 13, 2011 at 8:43 AM, FrankVhh <frank.vanhoenshoven(a)agserv.eu> wrote:
A rule engine will reason upon all the facts that are in its working
memory,
no matter what facts are in there. Therefore, it can not natively know
whether it has "enough" facts, neither does it (natively) know which facts
are missing. Call fire all rules, the engines starts thinking and will stop
thinking from the moment there are no more rules that are matching. Whether
the "results" make sense or not... well, it actually doesn't care.
In theory, you should provide all necessary facts before calling the rule
engine. I.e. add a task/step before calling the engine to collect all
missing facts.
In practice, you are able to "hack the philosophy", as the THEN part of a
rule is pure JAVA code, you can pretty much do what you want and add a
rule/rules that go after the required inputs (WHEN not veryImportantObject()
THEN getMyVeryImportantObject();END
Does this make sense to you?
Regards,
Frank
rchemisa wrote:
>
> Ty so much for answering FrankVhh,
>
> I dont understand if you can stop the process (just wait) in the Rule Set
> waiting to be inserted in the session some fact that makes the rules
> associated conditions are met (the result of the conditions true)
>
> So, the "Rule Set" act as a Wait State but may outsource the rules in the
> drl.
>
> Regards
>
--
View this message in context:
http://drools.46999.n3.nabble.com/RuleSet-RuleFlowGroup-tp3165058p3166451...
Sent from the Drools: User forum mailing list archive at Nabble.com.
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users
4889
days inactive
4889
days old
4 comments
3 participants
participants (3)
-
Dan Nathanson -
FrankVhh -
rchemisa