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

Contains all modules used in the linear workflow of a module type definition.

Schema Hierarchy

ManagementPack
  TypeDefinitions
    ModuleTypes
      ConditionDetectionModuleType
        ModuleImplementation (ConditionDetectionModuleType)
          Composite(ConditionDetectionModuleType)
            MemberModules

Syntax

Xml 
<MemberModules>
  <ConditionDetection>…</ConditionDetection>
</MemberModules>

Attributes and Elements

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

Attributes

None.

Child Elements

Element Description

ConditionDetection (ConditionDetectionModuleType)

Optional element. The implementation of a predefined ConditionDetectionModuleType module. A probe action type’s internal workflow can end with any number of ConditionDetection (ConditionDetectionModuleType) modules.

Parent Elements

Element Description

Composite(ConditionDetectionModuleType)

Contains the module implementations and linear workflow composition in a module type definition.

Remarks

The MemberModules element of a ConditionDetectionModuleType module contains the modules that are used to structure its internal workflow. A workflow that comprises a condition detection module type takes input as a single or multiple string; performs either a filtering, mapping, or other action on the data; and outputs the result.

The condition detection module type must output data of the type that is defined in the OutputType (ConditionDetectionModuleType) element. Generally, all ConditionDetectionModuleType definitions contain one or more ConditionDetection (ConditionDetectionModuleType) members.

The ID attribute of each member module must be unique only in the scope of the module type, not the management pack.

Example

In the following sample, a composite condition detection module modularizes the functionality of two condition detection modules. The System.Discovery.FilteredClassSnapshotDataMapper module first filters the input data stream that is based on the value of the Expression parameter. If the filter returns result data, that data is used as the input for the mapper condition detection module, which maps the input data type to discovery data.

  Copy Code 
<ConditionDetectionModuleType ID="System.Discovery.FilteredClassSnapshotDataMapper" Accessibility="Public" PassThrough="false" Batching="false" Stateful="false">
  <Configuration>
	<IncludeSchemaTypes>
	<SchemaType>System.ExpressionEvaluatorSchema</SchemaType>
	<SchemaType>System.Discovery.MapperSchema</SchemaType>
	</IncludeSchemaTypes>
	<xsd:element name="Expression" type="ExpressionType"/>
	<xsd:element name="ClassId" type="xsd:string"/>
	<xsd:element name="InstanceSettings" minOccurs="0" maxOccurs="1" type="SettingsType"/>
  </Configuration>
  <ModuleImplementation Isolation="Any">
	<Composite>
	<MemberModules>
		<ConditionDetection ID="Filter" TypeID="System.ExpressionFilter">
		<Expression>$Config/Expression$</Expression>
		</ConditionDetection>
		<ConditionDetection ID="Mapper" TypeID="System.Discovery.ClassSnapshotDataMapper">
		<ClassId>$Config/ClassId$</ClassId>
		<InstanceSettings>$Config/InstanceSettings$</InstanceSettings>
		</ConditionDetection>
	</MemberModules>
	<Composition>
		<Node ID="Mapper">
		<Node ID="Filter"/>
		</Node>
	</Composition>
	</Composite>
  </ModuleImplementation>
  <OutputType>System.Discovery.Data</OutputType>
  <InputTypes>
	<InputType>System.BaseData</InputType>
  </InputTypes>
</ConditionDetectionModuleType>

See Also