2.3.5.1.1.1 import-flow

Flows encapsulate mappings, providing a unique ID and scoping by source management agent and source connector space object type. Flows are defined via the import-flow XML element. The import-flow XML element MUST contain exactly one XML element to specify the attribute mapping, either the direct-mapping XML element, the scripted-mapping XML element, the constant-mapping XML element or the dn-part-mapping XML element. The XML attributes src-ma, cd-object-type, and id MUST be present on an import-flow XML element.

The following is an example of the flow XML.

 <import-flow src-ma="guid" cd-object-type="object-type" id="guid">
     <direct-mapping>
         <src-attribute>attribute-name</src-attribute>
     </direct-mapping>
 </import-flow>

The src-ma and cd-object-type attributes provide scoping for attribute mapping XML elements. The value of src-ma MUST be a GUID which is the ID of the source management agent. The value of cd-object-type MUST be the name of a connector space object type (a primary object class) defined in the source management agent's schema.

The id attribute MUST be provided by the client based on a value obtained by a previous Get of an object of the mv-data object type. This value is an identifier of the lineage information which describes how an attribute in the metaverse has been changed. This value MUST be a GUID.

Each GUID used in an import-flow MUST be unique.