Customizing Preferences

You can access and customize preferences for Traceable Requirements Management.

You can set default values for requirement and specification presentation, along with rich text options. There are other general preference options for conversions, home page, time/date format, language, and format for exporting table data.

Required access roles:

Baseline: Reader, Author, or Leader

This task shows you how to:

Set Structure Display Options
Set Specification Structure Options
Set Tree Display Options
Set Ownership Inheritance Options

Set Structure Display Options

You can specify the default structure display for requirements, specifications, and other requirement objects.

Required access roles:

Baseline: Reader, Author, or Leader

Before you begin: From the top bar, select

> Preferences. On the Preferences page, select Requirements.

Select the Structure Display category to set your preferences for requirement object displays:


Options in this tab...	Allow you to customize...
Default Filters:
Specifications list	Which specifications should be listed by default: Owned: List only specifications and specification folders that you own. Owned Specifications: List only specifications that you own. All: List all specifications and specification folders. All Specifications: List all specifications.
Requirements list	Which requirements should be listed by default: Owned: List only requirements that you own. Granted: List only requirements that you have been granted access to. All: List all requirements.
Expand Options:
Expand options	How many levels of requirement and specification structures that you want to display by default: 1 2 3 4 5 All Which other requirements objects that you want this to apply to: Sub Requirements Test Cases Parameters

Click Apply.
If you have set all of the preferences, click Done.

Set Specification Structure Options

You can specify whether sub requirements and downstream requirements are displayed in various contexts.

Required access roles:

Baseline: Reader, Author, or Leader

Before you begin: From the top bar, select

> Preferences. On the Preferences page, select Requirements.

Select the Specification Structure category to set your preferences for sub requirements display in various contexts:


Options in this tab...	Allow you to customize...
Structure Compare	Whether you want sub requirements to be displayed when comparing specification structures: Include Sub Requirements
Requirement-Test Case Traceability	Whether you want sub requirements to be displayed in this report: Include Sub Requirements
Requirement-Feature Traceability	Whether you want sub requirements to be displayed in this report: Include Sub Requirements
Delete Selected Object and Children	Whether you want sub requirements to be deleted when deleting the parent object in this context: Include Sub Requirements
Lock/Unlock	Whether you want sub requirements to be locked or unlocked along with their parent requirements: Include Sub Requirements
RFLP Traceability	Whether you want sub requirements to be displayed for RFLP traceability. This option displays only when VPLM is installed.

Click Apply.
If you have set all of the preferences, click Done.

Set Tree Display Options

You can specify what information is displayed in the report tree display for each type of object when you check the consistency of derivation links in specifications. These settings are also used as the default settings in Requirements Capture when displaying the requirement specification structure when managing tags and importing captures.

Required access roles:

Baseline: Reader, Author, or Leader

Before you begin: From the top bar, select

> Preferences. On the Preferences page, select Requirements.

Select the Tree Display category to set your preferences for what information is displayed in the tree display for each type of requirement object.

Select which fields are displayed in the right-side tree columns for identification:


Options in this tab...	Allow you to customize...
Name	Whether the Name field is displayed in the right-side tree columns for identification.
Title	Whether the Title field is displayed in the right-side tree columns for identification.

Select which fields are used as tree nodes for identification:


Options in this tab...	Allow you to customize...
Specification Folders	Which fields are displayed in the tree structure for specification folders: Name: The name will be displayed in the tree structure. Title: The title will be displayed in the tree structure. Revision: The revision level will be shown at the end. Field Separator: The field separator will be \| instead of two blank spaces.
Requirement Specifications	Which fields are displayed in the tree structure for specifications: Name: The name will be displayed in the tree structure. Title: The title will be displayed in the tree structure. Revision: The revision level will be shown at the end. Field Separator: The field separator will be \| instead of two blank spaces.
Chapters	Which fields are displayed in the tree structure for chapters: Name: The name will be displayed in the tree structure. Title: The title will be displayed in the tree structure. Revision: The revision level will be shown at the end. Field Separator: The field separator will be \| instead of two blank spaces.
Requirements	Which fields are displayed in the tree structure for requirements: Name: The name will be displayed in the tree structure. Title: The title will be displayed in the tree structure. Revision: The revision level will be shown at the end. Field Separator: The field separator will be \| instead of two blank spaces.
Comments	Which fields are displayed in the tree structure for comments: Name: The name will be displayed in the tree structure. Title: The title will be displayed in the tree structure. Revision: The revision level will be shown at the end. Field Separator: The field separator will be \| instead of two blank spaces.
Test Cases	Which fields are displayed in the tree structure for test cases: Name: The name will be displayed in the tree structure. Title: The title will be displayed in the tree structure. Revision: The revision level will be shown at the end. Field Separator: The field separator will be \| instead of two blank spaces.
Parameters	Which fields are displayed in the tree structure for parameters: Name: The name will be displayed in the tree structure. Title: The title will be displayed in the tree structure. Revision: The revision level will be shown at the end. Field Separator: The field separator will be \| instead of two blank spaces.

Click Apply.
If you have set all of the preferences, click Done.

Set Ownership Inheritance Options

If your Business Administrator has enabled the access through ownership inheritance capability, you can specify whether Traceable Requirements Management propagates access to all child objects through ownership inheritance from the parent object and allows access to child objects through ownership inheritance from the parent object. These settings are the default options selected in the Create form for each type of requirement object, but you can override them when you create an individual requirement object. You can also specify whether you want propagated or inherited access through ownership inheritance to use the default values for that requirements object type when it is cloned or revised.

Required access roles:

Baseline: Author or Leader

Select the Ownership Inheritance category to set your preferences to propagate access to all child objects through ownership inheritance from the parent object and to allow access to child objects through ownership inheritance from the parent object:

Options in this tab...

Allow you to customize...

Default Ownership Inheritance Behavior on Object Creation

Whether you want propagated or inherited access through ownership inheritance enabled by default when that type of requirement object is created:


Types	Propagate Access	Inherit Access
Specification Folders	Select to allow specification folders to propagate access to all child objects through ownership inheritance.	Select to allow access to specification folders through ownership inheritance from the parent object.
Requirement Specifications	Select to allow requirement specifications to propagate access to all child objects through ownership inheritance.	Select to allow access to requirement specifications through ownership inheritance from the parent object.
Chapters	Select to allow chapters to propagate access to all child objects through ownership inheritance.	Select to allow access to chapters through ownership inheritance from the parent object.
Requirements	Select to allow requirements to propagate access to all child objects through ownership inheritance.	Select to allow access to requirements through ownership inheritance from the parent object.
Comments	Not applicable.	Select to allow access to comments through ownership inheritance from the parent object.

Reset the Default Value on Clone/Major Revise?

Whether you want propagated or inherited access through ownership inheritance to use the default values for that requirements object type when it is cloned or revised:


Events	Propagate Access	Inherit Access
Clone	Select to allow a cloned object to use the default access propagation value defined for that requirements object type.	Select to allow a cloned object to use the default access inheritance value defined for that requirements object type.
Major Revise	Select to allow a revised object to use the default access propagation value defined for that requirements object type.	Select to allow a revised object to use the default access inheritance value defined for that requirements object type.

Note: If you do not specify the use of the default values for that requirements object type, the access through ownership inheritance values defined for source object are copied to the cloned or revised object.