The Conformance issue relation consists of a source object dimension Preceding function, a target object dimension Non-conforming function, a single level text dimension Conformance issue type containing a keyword for the issue type, and a measure Number of conformance issues that counts issues within a process instance.
The XML structure of the conformance issue relation REL_CONFORMANCE_ISSUE looks like this:
<relation name="REL_CONFORMANCE_ISSUE">
<description name="Conformance issue" language="en" />
<sourcedim name="D_PRECEDING_FUNCTION" />
<targetdim name="D_NONCONFORMING_FUNCTION" />
<refki name="RNUM_REL_CONFORMANCE_ISSUE" />
<refdim name="D_CONFORMANCE_ISSUE_TYPE" />
</relation>
The relation must have a dependency on AT_KI_CONFORMANCE_RATE due to the internal workings of the calculation. The calculation rule is
<calcrel name="REL_CONFORMANCE_ISSUE">
<depends attrname="AT_KI_CONFORMANCE_RATE" type="PROCESS" />
<calcclass name="com.idsscheer.ppm.server.keyindicator.relation.calculator.
ZRelationCalculatorConformanceIssues" loglevel="VERBOSE" />
</calcrel>
The relation is calculated by calculation class ZRelationCalculatorConformanceIssues.
The issue type information is stored in the key attribute of the relation that was configured for the assigned dimension. The attribute name can be freely chosen. The dimension must be a single level text dimension with keyword D_CONFORMANCE_ISSUE_TYPE. Otherwise, the relation is not calculated and none of the associated measures and dimensions have a value. If you need to use a different keyword, for example because there already is another dimension D_CONFORMANCE_ISSUE_TYPE in the customizing, you can supply that keyword to the calculation class ZRelationCalculatorConformanceIssues as the value of the parameter issue_type_dimension_keyword.