[This topic is pre-release documentation and is subject to change in future releases. Blank topics are included as placeholders.]

Defines a workflow within a management pack.

Schema Hierarchy



<Rule ID=”RuleID” Comment=”Comment” Enabled=”True/False” Target=”TargetClassID” ConfirmDelivery=”True/False” Remotable=”True/False”><DataSources>…</DataSources>

Attributes and Elements

The following sections describe attributes, child elements, and the parent element of the Rule element.


Attribute Description


Required attribute. Represents the identity of the element. To learn how to identify your element in a management pack, see Element Identity and Namespace Conventions.


Optional attribute. Represents commentary by the management pack author.


Required attribute. Defines whether or not this workflow is by default enabled or disabled.


Required attribute. The ID of the targeted class type.


Optional attribute. Defines whether or not the module following the data source module will notify the data source that it has received the data. The default value is false.


Optional attribute. Defines whether or not this workflow will run for agentless monitoring. Default value is true.

Enabled Attribute Values

Value Description


The workflow is enabled and will run when its target class has been instantiated within the system.


The workflow is disabled and will not run even when its target class has been discovered.

Target Attribute Values

Value Description

The ID of the targeted ClassType element.

A rule is always targeted at a particular class type and runs against every instance of that class type.

Child Elements

Element Description


Required element. Contains one or more data source modules.

ConditionDetection (Rule)

Optional element. Represents an implementation of a condition detection module type definition.


Required element. Contains one or more write action modules.

Parent Elements

Element Description


Contains rule definitions targeted at a specific class or relationship type.


Rules are workflows that must conform to the following requirements:

The ConfirmDelivery attribute should be set to true only when you find that the workflow is failing to pass data from the data source to the next module in the workflow. This would happen when the amount of data surpasses a predefined system threshold. When it surpasses this threshold, data items will be dropped for performance reasons. However, when ConfirmDelivery is set to true, the data will not be dropped but the next module in the workflow will acknowledge delivery of the data item to the data source module before it receives its next piece of data.


The following XML sample demonstrates a rule that runs a Windows Foundation Workflow.

  Copy Code
<Rule ID="Microsoft.SystemCenter.MonitoringHostKeepAlive" Enabled="true" Target="Microsoft.SystemCenter.MonitoringHostKeepAlive.Workflows.WorkflowTarget" ConfirmDelivery="true" Remotable="true" Priority="Normal" DiscardLevel="100">
	<DataSource ID="DS" TypeID="System!System.Scheduler">
		<Interval Unit="Minutes">120</Interval>
		<ExcludeDates />
	<WriteAction ID="WindowsWorkflow" TypeID="Subscriptions!Microsoft.EnterpriseManagement.SystemCenter.Subscription.WindowsWorkflowTaskWriteAction">
			<WorkflowParameter Name="TimeoutInMinutes" Type="int">110</WorkflowParameter>

See Also