This validation rule is invoked when a Document Object with outgoing traces has been updated.
If the Document Object has an outgoing trace to a Document Object (and that Document Object type also has the Suspect Trace Rule) and has been updated, an inconsistency is displayed indicating that the change in the Document Object might have an impact on the traced Document Objects and that the traced Document Objects therefore should be checked.
<SuspectTraceRule />
Set Suspect To Type Name
Per default, all traces to all traced types (types that also have a SuspectTraceRule) will be marked as 'Suspect'.
Optionally, the behavior can be moderated with the ptional SetSuspectToType name element, that contains a list of type names.
Traces to items of these type names are then set to suspect.
Traced to Type names not listed will not be set to suspect.
In cases where traced types contain very similar attributes (e.g. a Requirement with a Title and Description has a trace to a System Specification that shall have the same Title and Description values as the parent Requirement), a Inconsistency Resolution option called Transfer (relevant) changed attribute values from Source to Target can be configured to automatically copy the modified attributes in the parent to the child item.
The AttributesToTransferInResolve element can optionally be used to define which attribute names in the parent shall be transferred to the child.
If the an attribute mapping shall take place (i.e. map Description attribute value in parent to Comment attribute value in child), a attribute mapping rules can be defined in the child type Trace Holder in the parent type.