One of the super cool things about IDM is the way it does caching, and
read ahead queries. Put those two together, and you save a LOT of time,
reading and getting data.

I am working on a SOAP driver to and it is working fine.
The problem I have noticed is, in a condition I test, if attribute
Contact is available, which forces a query, since it is not in the op
doc. Thats fine.

But the first action is set local variable to attribute Contact.

So that should have been cached, as it JUST queried for it, in the same
rule! I know the cache is not cross policy objects, but this seems odd.

Is there something I need to do, to allow the engine to enable this
kind of caching, when in the SOAP driver? Is it a feature that needs to
be part of the driver shim?

geoffc's Profile:
View this thread: