|Microsoft Identity Integration Server 2003 Developer Reference|
When a metaverse attribute has more than one import flow from one or more management agents, you can use attribute precedence to define what value flows when setting the value of the attribute in the metaverse. A special form of attribute precedence is the manual precedence. Manual precedence gives additional control to decide what attributes and their values contribute to the attribute in the Metaverse in case of multiple import flows.
The following are examples of manual precedence in a rules extension:
Example: Manual Precedence Using the Last Contributing Management Agent, Example: Handling Attribute Value Accumulation