Manual Precedence Examples

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:

• Handling multiple connector space objects to the same metaverse object: You can accumulate attributes from multiple connector space objects in the same management agent to a single metaverse object with manual precedence. For an example, see Example: Handling Many Connector Space Objects to One Metaverse Object in the Same Management Agent.
• Use the Last Contributing Management agent: You can specify that the value of an attribute is changed only if a specified management agent made the attribute value change. A value contributed by another management agent does not change the attribute value. For an example, see Example: Manual Precedence Using the Last Contributing Management Agent.
• Use the Attrib.LastContributionTime property: You can specify to set an attribute in the metaverse only if the incoming attribute was modified at a later time in the connected data source.

See Also

Example: Manual Precedence Using the Last Contributing Management Agent
Example: Handling Attribute Value Accumulation

Send comments about this topic to Microsoft

Build date: 2/16/2009