Logic behind Rule BB

AppWorks Tips

Hi,

It's friday afternoon; Time for a (from my side) headache question…

I have 4 Rule BBs on my entity; all 4 have the same condition for a property change event (just that the name equals to 'test'). All 4 set a value of the same property. So, Rule 1 will set the value to 'test1', Rule 2 will set it to 'test2', and so on…

How on earth in runtime will I know which Rule is applied? I see it's the same Rule over and over again; So, that's consequence, but why that Rule and not the other 3. Is it because it was last added to the entity, or does it pick my first added Rule BB…What is the logic?

I'm tracking it with the History BB and I only see 1 change passing by. It would be great to have some tracking enabled, but I would not know which service container would be a possible candidate to start with as it's definitely not the 'Rule Management' managing it all.

Thx for the response.

BR and a great weekend, Antal

nssmani

@AppWorks Tips , As per the current design, AppWorks can't guaranty the rule order executing if the same entry condition is used across the rules. I can depend on the type of deployment, number of nodes, OS etc. We have a plan to enhance the rule designer to perform multiple actions in a sequential order.