this is idm 3.5.1 with the latest engine patches.

I noticed a behaviour with GCV's and libraries that I would like to
have a confirmation on:

- a driver set GCV is setting GCV "A" to "value1"
- a driver within the same driver set is setting (and thus overwriting)
GCV "A" to "value2"
- a policy in the driver is including a library function which is
consuming GCV "A"

While policies/rules belonging directly to the driver (non-includes)
are getting "value2" as expected, the library function seems to be
running outside the driver's context and is getting "value1".

Is this the expected thing to happen or (imho) a bug?

thank you for any pointers.

ursidm's Profile:
View this thread: