Fim reference dn not updating

Using Detected Rule Entries (DREs) to calculate Set membership.

Rule instead, then the object hits a DLL error with the inbound sync. An Action workflow function instead of an inbound sync.

rule function guarantees that all objects can get to the FIM portal regardless of data quality issues. Using ‘Temporal Sets’ and ‘Transition In’ triggers to send out reminder emails about an account that was due to expire.

There are of course many ways of detecting whether an AD account is ‘active’ however, I just wanted something to work for both existing AD accounts and ones provisioned by FIM.

Also, the only system that contributes DREs is Active Directory and this avoids ‘sticky values’ where the FIM portal keeps sending old values to the Metaverse because its the last contributing system for that attribute. As part of my Active Directory outbound provisioning rule, I used a combination of multiple Action workflows to generate the right values, including calculating a unique ‘s AMAccount Name’ using a Global Catalog lookup to the Active Directory. Rule to send initial flow values as variables to the Sync.

NET or C# or try to use FIM R2’s Management Policy Rules (MPR), Sets, Sync.

Comments