Was curious if this had been resolved through subsequent versions? I too am
trying to incorporate a custom AgendaFilter (using rule metadata attributes
to control the firing of rules). I would also prefer to run my rules
through a ruleflow. However, with the AgendaFilter, my rules are not
I don't think it has. The history of the Jira ticket referenced above shows
it getting pushed along from one release to the next.
I did come up with an alternative that works, although it's a bit clunkier.
Check this thread out - hopefully it'll help you -
The ruleflow-group will control the rules to not fire until the
ruleTask is reached in your process, but all the evaluations will be
done as soon as the information goes inside the
workingmemory/ksession.
Cheers
On Thu, Dec 29, 2011 at 12:40 PM, Rob Fisher
rob.fisher.l...@statefarm.com wrote:
Bump...
I really need some help with this issue - can anyone answer even some of my
questions? If my problem or my questions aren't clear, let me know and I'll
try to clarify.
Thanks!
--
View this message in context:
Your questions are very specific to your example so providing your test
case would help for anyone to actually take a look at it.
Thanks.
On 7/28/11 11:01 AM, Jamie wrote:
Bump...
I really need some help with this issue - can anyone answer even some of my
questions? If my problem or my
Fair enough - I'll try to work out a simplified test case that demonstrates
the behavior.
In the meantime, can someone answer a very basic rules/flow question for me?
In my simple, linear test flow, if I cancel any activation, why don't any of
the remaining nodes in the flow get triggered?
--
I'm having some issues with the interaction between Flow, ruleflow-groups and
AgendaFilters. I've tried it with 5.1.1, 5.2.0 using .rf files and 5.2.0
using .bpmn files, all with the same results, so I'm sure I'm just
misunderstanding something.
I have a flow that looks like this:
