Thats a reallly really really bad rule - unless I misunderstand what you
are doing. you are creating a cross product of 16 with that, although we
now remove instance equals cross product. So that means you would have
to assert 4 QueryObjects for this to work. If it was working before
thats because the rule was firing repeatedly for the same object and
doing the same set, so you weren't noticing.
To understand what I mean try this in RC1 and RC2 in the audit view and
you will understand the difference.
Mitch Christensen wrote:
The following used to work in previous versions (though I'm not sure which),
rule "All Application Traffic by Org Unit Template Selection Logic"
when
qo : QueryObject(selectApplication == true)
qo : QueryObject(selectUser == true)
qo : QueryObject(orgNetObjectType == ObjectType.pmi_net_user)
qo : QueryObject(reportType == Constants.REPORT_TYPE_WINDOW)
then
qo.setTemplate("AppUserByOU.ftl");
end
But when I upgraded to RC-2 in order to get it to fire I needed to change it
to this,
rule "All Application Traffic by Org Unit Template Selection Logic"
when
qo : QueryObject(selectApplication == true,
selectUser == true,
orgNetObjectType ==
ObjectType.pmi_net_user,
reportType ==
Constants.REPORT_TYPE_WINDOW)
then
qo.setTemplate("AppUserByOU.ftl");
end
Which is fine, I understand that the latter is completely resolved within
the alpha/pattern network, but what impact will it have on my ability to
define DSL? It seems the former would lend itself to a more straightforward
DSL implementation.
Also, it seems that the former should still be valid, though less efficient.
-Mitch
