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…






This E-mail message and any attachments may contain
legally privileged, confidential or proprietary
information. If you are not the intended recipient(s),
or the employee or agent responsible for delivery of
this message to the intended recipient(s), you are
hereby notified that any dissemination, distribution
or copying of this E-mail message is strictly
prohibited. If you have received this message in
error, please immediately notify the sender and
delete this E-mail message from your computer.