I am not sure what you mean by "parentvalue" in this context. The problem here is that any variables created inside the branch (or editing a variable previously declared outside the branch) do not reflect those changes in the rest of the rule after the branch component, except for one special case.

The one special case is if you declare any variable before the branch component, ONE branch execution will have its variable changes reflected in the rest of the rule. This branch is the first branch executed.

There are a bunch of technical reasons for this edge case, but this is not behaviour we would want customers relying on, as it is not intended user experience. We are in the process of looking at alternatives to fix this in a non-invasive way.

Cheers
Sam

I think the problem was not understanded. "var" is not the same as "parentvalue". On the other hand, even declaring the variable before the branch, the value does not change inside the branch.

Hi there,

This is expected behaviour, and is a result of how our rules are executed. A branch is essentially a separate, sub-rule which is run asynchronously from the rest of the rule. As such, it cannot affect the rest of the rule. Variables cannot be passed back from a branch execution. Your work around you have presented is the correct approach; if you want to use the variable in the root rule, then it must be declared there.

Cheers

Sam