Understanding concept architecture
Each BMC Atrium Orchestrator concept is composed of an XML file and a schema (XSD) document.
- Each element in the XML file represents a normalized field in the concept.
- The XSD file contains the data type definition for each element in the XML file.
In the concept, elements represent the abstracted fields. In the following example of a Change concept, the first two elements are <change-id xmlns="" /> and <description xmlns="" />:
<Change-Request xmlns="AutoPilot-OA-Change_Management">
<change-id xmlns="" />
<description xmlns="" />
<status xmlns="" />
<urgency xmlns="" />
<change-type xmlns="" />
<timing xmlns="" />
<risk-level xmlns="" />
<company xmlns="" />
<location-company xmlns="" />
<first-name xmlns="" />
<last-name xmlns="" />
<priority xmlns="" />
</Change-Request>
<change-id xmlns="" />
<description xmlns="" />
<status xmlns="" />
<urgency xmlns="" />
<change-type xmlns="" />
<timing xmlns="" />
<risk-level xmlns="" />
<company xmlns="" />
<location-company xmlns="" />
<first-name xmlns="" />
<last-name xmlns="" />
<priority xmlns="" />
</Change-Request>
For information about how to use the concept editor to make assignments between context items and the elements of a concept, see Working with structured data in a workflow.
In the following example of the Change XSD, the request-id is defined as an integer and the change-id is defined as a string, with a maximum length of 30 characters:
<xsd:element name="request-id" type="xsd:integer" />
<xsd:element name="change-id">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<maxLength value="30" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="change-id">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<maxLength value="30" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*