Just a note, this bug was fixed in IDM 4.0.2 release.


While I agree that this is now the correct behaviour (as it always
should have been). We just got bitten by the consequences of fixing this
bug at a customer we had just upgraded to 4.0.2

This customer had some existing code that relied on the value from a
local variable was escaped prior to being used in a regex scenario.

alexmchugh's Profile: https://forums.netiq.com/member.php?userid=461
View this thread: https://forums.netiq.com/showthread.php?t=6283