I would like to try something rather different witht eh rules engine
and i was wondering if it can be done.
Basically what i am trying to do is have my rules engines run a generic
policy over the msg file and run some rules on it. As it goes through,
I would like it to be able to decide what other policies apply to this
msg. Basically, the message has fields and the values in those fields
determine which other policies should be run that are specific to it.

So here is the question, Can i have an action "CALL Rules" with another
policy?
or is there a way that i can somehow promote a value from the rules
engine that will determine what the next path will be in the
orchestration?
or is there a way to do a switch statement in the orchestration that
will be able to run the first policy then read the values from the file
and determine which path to take.

thanks in advance for your help.
My personal email  is aewassef@gmail.com if youd like to contact me

[ Post a follow-up to this message ]

Hi Wazzy,

I've done something similiar.  The way that I did this was to create a
policy list as a fact that I then passed into a particualr policy,
let's call it Enable Policies

i.e.

<policies>
<policy name="foo" enabled="false"/>
<policy name="bar" enabled="false"/>
</policies>

Enablie Policies would then determine which other policies should be
run, and set the enable attribute for these policies to true.

Then, I iterate through the policies list and execute the policies that
are now enabled.

Make sense?

HTH

[ Post a follow-up to this message ]

It makes perfect sense, except for one part.

How do you actually call the enabled policy from within the policy. I
use the Call Rules shape from an orchestration with the policy name,
so, i would call the parent policy, and then from there, how do i
envoke the following policies.

Another question is can i add another node "on-the-fly"

ie
<policies>
<policy name="foo" enabled="false"/>
<policy name="bar" enabled="false"/>
<policy name="NEW" enabled="false"/> <---- This node would be added in
the action part of a rule.
</policies>

The reason i would lke to do this in the Rules engine is so I would not
have to go back to the xml and change it manually.
I have several stages in the process and i would like to pass that info
to the second stage "on-the-fly"

Thanks for the reply

Wazzy

[ Post a follow-up to this message ]