Consider the following situation:
- a Standard "Rule Project A" with a "RuleFlowA" referencing the rule package "Rule Project A/rules/Validation Rules"
- a Standard "Rule Project B" with a "RuleFlowB" referencing the rule package "Rule Project B/rules/Validation Rules"
- a "Main Rule Project" with a "Main RuleFlow" with 2 consecutive "Subflow Task" referencing respectively "Rule Project A/rules/RuleFlowA" and "Rule Project B/rules/RuleFlowB"
- a decision operation executing "Main Rule Project/rules/Main RuleFlow"
When executing the operation, the first subflow task fires all the rules, both "Rule Project A/rules/Validation Rules" and "Rule Project B/rules/Validation Rules". In the second subflow task again all the rules are fired.
It looks like in the main project all the rule packages with same name are compiled in a single rule package. This "compiled package" is the one executed independently that you reference only the "Validation Rules" of one of the projects.
Is it working as design? Is it documented in the product?
Note that setting a different name for the rule packages ("Rule Project A/rules/Validation Rules A" and "Rule Project B/rules/Validation Rules B") makes it work well, as expected.
I have a minimal workspace to reproduce the behavior in case you need it. Just let me know and I will add an attachment to the thread.
Thanks
------------------------------
Eduardo Izquierdo Lázaro
Automation Architect
DECIDE
MADRID
+34609893677
------------------------------