Because customers have different names for attributes with the same semantics, it would be nice to be able to use ~ notation in driver filters, schema mappings etc.
Actually it kind of works (if entered by hand), it is just, that it seems to be cached by the engine, so if it is changed, the old value persists.
by: Nicolai J. | over a year ago | Other
Comments
This is actually a two-fold issue:
a) support for using GCVs when editing filter an schema mapping policies, and
b) support to apply modified GCV values in subscriber sync filter after a driver restart (as usual for GCVs) and not only after an Edirectory restart (which is the way the current iomplementation works).
Both would help a lot when implementing schema-agnostic drivers!
I agree. I seems like it is only implemented half-way through and the mentioned enhancements would highly improve the the way we work.