Folks,

 

When using globals in rule flow’s Split I ran into problem that changes to the global cannot be recognized by the split and it continues to route the same destination.

 

F.e. I have a Split with constrains. And a global TestValid object that has one boolean attribute - hasErrors

 

global testValid

 

Split :

-          eval(!testValid.isHasErrors())      // to No Errors action

-          eval(testValid.isHasErrors())       // to END

 

 

So it ends up with always looping to the No Errors Action, even though Make Errors sets global :  testValid.setHasErrors(true)

 

In my previous example the problem was that I was not using Shadow Proxy. But now I am and would like to use global in the split condition,

 

Please advice if it is an expected behavior and I shouldn’t be using global in split conditions…

 

Thanks,

 

-Sergey