IConstraint is indeed used for storing the constraint for each of the outgoing connections
of an (X)OR split. This constraint is currently represented as a String, but this does
not mean it will be interpreted at runtime. We are currently thinking about making these
conditions similar to the normal LHS of a rule, so you could say something like when
"Person(age > 20)" as constraint. These constraints will then be evaluated
the same way as the LHS of a rule. I'm pretty close to getting (X)OR splits working,
the tooling (eclipse) is still the hardest part though.
The definition of variables for a ruleflow would allow you to define variables local to
one specific ruleflow (instance). They are similar to globals but their scope is
different: globals have one value for an entire workingMemory, ruleflow variables would be
local to one ruleflow (instance). Note that these variables are still on the TODO list as
well.
Kris
----- Original Message -----
From: Anstis, Michael (M.)
To: Rules Dev List
Sent: Tuesday, May 15, 2007 1:16 PM
Subject: [rules-dev] RE: [rules-users] Using the Rule Flow Builder GUI
So I'm increasingly excited with ruleflow.... but I'm afraid I want to
understand more... Is the decision stuff for ruleflow set to be in 4.0? Can more
information as to the role of IConstraint and IVariable be given? Will IConstraint
continue to be Strings (that are evaluated at runtime)? What purpose do IVariables have;
are they bound to (WorkingMemory) Global variables? Can IConstraints access Fact
properties (so decisions are made on a per-fact basis - probably horredous truth
maintenance issues - rather than global to the process). I'd love to try and
contribute...
----------------------------------------------------------------------------
From: rules-users-bounces(a)lists.jboss.org [mailto:rules-users-bounces@lists.jboss.org]
On Behalf Of Kris Verlaenen
Sent: 14 May 2007 22:57
To: Rules Users List
Subject: Re: [rules-users] Using the Rule Flow Builder GUI
1) Yes kris is still working on the decision stuff for ruleflow.
Some of the stuff is already partially implemented, but an (X)OR split (where
you can define which path(s) to follow based on some conditions) is still on the TODO
list.
3) The Eclipse GUI ruleflow builder doesn't seem to allow loops
in the flow.
It does support the creation of loops: create an XOR split as the
starting point of your loop, you can then always create nodes that link back to this
starting point, resulting in a loop. Note that looping kind of depends on the (X)OR split
as well, as that would allow you to exit the loop in specific conditions (now you will
probably create an endless loop). I hope I'll be able to add that piece of
functionality pretty soon to trunk.
Kris
------------------------------------------------------------------------------
_______________________________________________
rules-dev mailing list
rules-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-dev