<outbound-flow-counters>
Contains information about the number of provisioning changes and exported attributes.
Schema Hierarchy
<run-history>
<run-details>
<step-details>
Syntax
<outbound-flow-counters>
<provisioned-add-no-flow>
</provisioned-add-no-flow>
<provisioned-add-flow>
</provisioned-add-flow>
<provisioned-rename-flow>
</provisioned-rename-flow>
<provisioned-rename-no-flow>
</provisioned-rename-no-flow>
<provisioned-disconnect>
</provisioned-disconnect>
<provisioned-delete-add-no-flow>
</provisioned-delete-add-no-flow>
<provisioned-delete-add-flow>
</provisioned-delete-add-flow>
<connector-flow>
</connector-flow>
<connector-no-flow>
</connector-no-flow>
</outbound-flow-counters>
element
Attributes and Elements
The following sections describe attributes, child elements, and parent elements.
Attributes
| Attribute | Description |
|---|---|
ma |
The name of the management agent to which the counters apply. |
ma-id |
The GUID of the management agent to which the counters apply. |
Child Elements
| Element | Min Occurs | Max Occurs | Description |
|---|---|---|---|
0 |
1 |
Contains information about the number of connectors where the export attribute flow process flowed attributes from the metaverse to this object. |
|
0 |
1 |
Contains information about the number of connectors where the export attribute flow process ran, but there was no attribute flow. If no export attribute flow was defined for this management agent, the value for this element is zero. |
|
0 |
1 |
Contains information about the number of newly provisioned connectors that were added to the connector space of this management agent where there was some actual export attribute flow from metaverse to connector space (in addition to initial values the provisioning process may have set at the time of provisioning). |
|
0 |
1 |
Contains information about the number of newly provisioned connectors that were added to the connector space of this management agent where there was no export attribute flow from metaverse to the connector space (although the provisioning process may have set some initial values at the time of provisioning). |
|
0 |
1 |
Contains information about the number of connectors that were first provisioned for a connector delete, and then were provisioned for an add with the same distinguished name, where there was some export attribute flow from the metaverse to the connector space (in addition to initial values that the provisioning process may have set at the time of provisioning). |
|
0 |
1 |
Contains information about the number of connectors that were first provisioned for a connector delete, and then were provisioned for an add with the same distinguished name, where there was no export attribute flow from the metaverse to the connector space (although the provisioning process may have set some initial values at the time of provisioning). |
|
0 |
1 |
Contains information about the number of provisioned disconnects during this run. |
|
0 |
1 |
Contains information about the number of provisioned renames during this run management agent where export attributes flowed from the metaverse to the connector space. |
|
0 |
1 |
Contains information about the number of provisioned renames during this management agent run where there was no actual export attribute flow from metaverse to the connector space. |
Parent Elements
| Element | Description |
|---|---|
Stores run information about one step of the management agent run. |
Remarks
If the step involves applying changes from the connector space to the metaverse, there may be one or more provisioning changes or export attribute flow. For each management agent for which provisioning or non-trivial export attribute flow occurs, there is an <outbound-flow-counters> element.