Hi,

Since different customers might have attributes with different names for
attributes with the same meaning (EmpNo vs. EmploymentID for example), our
team have begun making drivers with gcv values in the filters, policies
and schema mapping.

Like this (in a filter)

<filter>
<filter-class class-name="User" publisher="sync" publisher-create-
homedir="true" publisher-track-template-member="true" subscriber="sync">
<filter-attr attr-name="~drv.affil~" merge-authority="default"
publisher="ignore" publisher-optimize-modify="true" subscriber="notify"/>
<filter-attr attr-name="Group Membership" merge-authority="default"
publisher="sync" publisher-optimize-modify="true" subscriber="sync"/>
</filter-class>
<filter-class class-name="Group" publisher="sync" publisher-create-
homedir="true" publisher-track-template-member="true" subscriber="sync">
<filter-attr attr-name="~drv.sp~" merge-authority="default"
publisher="ignore" publisher-optimize-modify="true" subscriber="notify"/>
<filter-attr attr-name="Equivalent To Me" merge-authority="default"
publisher="sync" publisher-optimize-modify="true" subscriber="sync"/>
</filter-class>
</filter>

It works most of the time.
Sometimes though, the driver is not picking up events on specific
attributes, and when that happens, no kind of fiddling around with it
(changing the sequence for example), can get it to work again.
The events are not picked up by the driver. It begins to work again, when
we revert to using the actual physical attribute name.
At other times it just works.

The question is, is this at all supposed to work?
Or is this in reality not supposed to work, and we should stop doing it?

Any ideas regarding this?