Resolution:
Yes, you are right that the behavior of the "Changed()" function is changed. In the older version of MB it was not working properly. For example, it would always populate "False" as the result (as a matter of fact, for a fraction of a second it would become "true" when the value changed, but then reverted back to "false" in the very next engine cycle), so the customer would complain as to why the changed() function never showed "True".

In MB 4.1, this behavior is changed and the "Changed()" function will now show "True" if the value we are checking is changed from its previous value. It will return "True" until you pass an old value again.

But there is a way to go back to the old "Changed()" function in MB 4.1.0. If you set System Property called "tibco.mb.reevaluatechanged" in your MBGUI or MBEngine batch file to "Yes" (e.g. Dtibco.mb.reevaluatechanged="Yes") then MB 4.1.0's "Changed()" function will roll back to the older "Changed()" function and you don't have to worry about modifying your old transforms!