InitialFlows

This section contains all settings regarding initial flows that are performed when new objects are provisioned. There are several options for creating or building initial flows. All attribute flows derives from a single base attribute flow tag called AttributeFlowBase and all contain a type specified by the xsi:type attribute.

Reserved words

You can use the following reserved words to get to special attribute / values from either the metaverse or connector space object -

• [DN] - set the value of the connector space object's distinguished name
• [MVObjectID] - get internal GUID value of the metaverse object

AttributeFlow types

AttributeFlow xsi:type=AttributeFlowGuid

This flow allows for generating a new GUID and flowing this to an attribute. In the example below a new GUID is flowed to the built-in DN (specified by the surrounding brackets), however the target attribute could any valid connector space object attribute.

<AttributeFlowBase xsi:type="AttributeFlowGuid">
  <Target>[DN]</Target>
</AttributeFlowBase>

AttributeFlow xsi:type=AttributeFlowConstant

This type of flow rule allows flowing a constant to an attribute. In the example below the constant ‘A’ in flowed to the connector space object attribute named ‘USERTYPE’.

In the Constant value, you can refer to values from

• the metaverse object - by using the notation #mv:#, i.e. #mv:accountName# to have MRE replace that text with the value from the metaverse object. If no value is present, a blank value will be inserted.
• the [Helpers|Helpers element] - by using the notation #helper:#, i.e. #mv:DNGuid# to have MRE replace that text with the value from that specific helper. If no value is present, a blank value will be inserted.

<AttributeFlowBase xsi:type="AttributeFlowConstant">
  <EscapedCN>CN=#mv:accountName#</EscapedCN>
  <Constant>#param:EscapedCN#,OU=Users,DC=contoso,DC=com</Constant>
  <Target>[DN]</Target>
</AttributeFlowBase>

<AttributeFlowBase xsi:type="AttributeFlowConstant">
  <Constant>A</Constant>
  <Target>USERTYPE</Target>
</AttributeFlowBase>

Below is an example of using a helper value called 'DNGuid' to set that GUID in both [DN] and the anchor.

<AttributeFlowBase xsi:type="AttributeFlowConstant">
  <Constant>#helper:DNGuid#</Constant>
  <Target>[DN]</Target>
</AttributeFlowBase>
<AttributeFlowBase xsi:type="AttributeFlowConstant">
  <Constant>#helper:DNGuid#</Constant>
  <Target>AnchorGUID</Target>
</AttributeFlowBase>

AttributeFlow xsi:type=AttributeFlowMultivaluedConstant

This type of flow rule allows flowing multiple constant values to an attribute. This flow rule exposes the same features as the AttributeFlowConstant type.

<AttributeFlowBase xsi:type="AttributeFlowMultivaluedConstant">
  <Constants>
     <Constant>A</Constant>
     <Constant>B</Constant>
   </Constants>
  <Target>USERTYPE</Target>
</AttributeFlowBase>

AttributeFlow xsi:type=AttributeFlowAttribute

This type of flow rule allows for flowing a metaverse attribute value directly to a connector space object attribute. In the example below, the value of the metaverse attribute ‘userID’ is flowed directly to the connector space object attribute ‘UNAME’.

<AttributeFlowBase xsi:type="AttributeFlowAttribute">
  <Source>userID</Source>
  <Target>UNAME</Target>
</AttributeFlowBase>

You could also retrieve the GUID of the metaverse object by specifying the reservered work {MVObjectID] and source and then use that value to set in a connected system that needs a GUID as anchor, i.e. a SQL table that has uniqueidentifier as the primary key. The use of the MVGUID also for great join options later.

<AttributeFlowBase xsi:type="AttributeFlowAttribute">
  <Source>[MVObjectID]</Source>
  <Target>_id</Target>
</AttributeFlowBase>

AttributeFlow xsi:type=AttributeFlowConcatenate

This type of flow rule allow for concatenating several values (metaverse values or constants) to one target value in the connector space. This flow rule option is often used for constructing initial password and such.

In the example below an number of SourceExpressionBase of different types are concatenated and flowed to the ‘export_password’ attribute in the connector space object attribute. The example concatenates the value of the attribute ‘department’ from metaverse with the constant ‘.’ (note the type of the SourceExpressionBase being SourceExpressionConstant) and finally with the value of the attribute ‘accountName’ from the metaverse.

<AttributeFlowBase xsi:type="AttributeFlowConcatenate">
  <SourceExpressions>
    <SourceExpressionBase xsi:type="SourceExpressionAttribute">
      <Source>department</Source>
    </SourceExpressionBase>
    <SourceExpressionBase xsi:type="SourceExpressionConstant">
      <Source>.</Source>
    </SourceExpressionBase>
    <SourceExpressionBase xsi:type="SourceExpressionAttribute">
      <Source>accountName</Source>
    </SourceExpressionBase>
  </SourceExpressions>
  <Target>export_password</Target>
</AttributeFlowBase>