Configuring Traceability Options

Create or open the text file to contain customized properties. For more information, see Editing Properties Using MQL.

To support "documents to documents" traceability (in addition to requirements to documents traceability), follow these steps:

Add or edit this line in the file used to import properties into a page object:
```
emxLPI.DHFTraceability.DesigInput.IncludeTypes
```
The default value is "type_SoftwareRequirementSpecification" which supports only requirement to documents traceability functionality.
Replace the default value with "type_DOCUMENTS" to support documents to documents traceability along with requirement to documents traceability functionality.
Add or edit this line in the file used to import properties into a page object:
```
RiskMgmt.DHFTraceability.DesigInput.IncludeTypes
```
Make this key have the same value as emxLPI.DHFTraceability.DesigInput.IncludeTypes.

To exclude document subtypes shown when expanding the Design Input bookmark in the traceability view, follow these steps:

Add or edit this line in the file used to import properties into a page object:
```
emxLPI.DHFTraceability.DesigInput.ExcludeTypes
```
The default value is blank. Only sub types of DOCUMENTS can be specified.
Specify document sub types to be excluded.
Add or edit this line in the file used to import properties into a page object:
```
RiskMgmt.DHFTraceability.DesigInput.ExcludeTypes
```
Make this key have the same value as emxLPI.DHFTraceability.DesigInput.ExcludeTypes.

To propagate DHF Traceability from lower revision content to higher revision content, follow these steps.

This traceability setting is applicable to DHF bookmark contents for Design Input, Design Output and Design Verification only.

Add or edit this line in the file used to import properties into a page object:
```
emxLPI.DHFTraceability.PropagateToHigherRevision=YES/NO
```
"Yes" enables automatic DHF Traceability propagation from lower revision content to higher revision content.

"No" disables DHF Traceability propagation from lower revision content to higher revision content.

In the following step, activate this trigger:


Trigger Name	Revision
RelationshipVaultedObjectsCreateAction	PropagateDHFTraceabilityOnContentRevision

Open MQL from the server and run the MQL command below that sets the context user as admin if the admin user does not have a password:
```
MQL>set context user creator;
```
If the admin user has a password, run the MQL command where PASSWORD is the admin user password:
```
MQL>set context user creator password PASSWORD
```
Run the MQL command to enable VERBOSE:
```
MQL> verb on;
```
Run the MQL command below to activate the triggers:
```
MQL> modify bus "eService Trigger Program Parameters" RelationshipVaultedObjectsCreateAction PropagateDHFTraceabilityOnContentRevision current Active;
```
Note: The above MQL command uses the following syntax:
MQL> Modify bus <TYPE> <NAME> <REVISION> current <STATE>;
Where
TYPE – type of business object
NAME – name of business object
REVISION – revision of business object
STATE – target state of business object (for triggers Inactive/Active)
Log in as VPLMAdminUser and reload the cache using the "Utilities > Reload Cache" command in the user interface.

When finished updating the text file with the properties you want to modify, including the ones shown here, use the text file to modify the emxLPI.properties page object and the RiskMgmt.properties page object. For more information, see Editing Properties Using MQL.