Filter views on Tags

To filter the UI on one or more Tags, click the Tag Name in the Tag Bar to activate in any View (e.g. the Chapter View). The Tag Bar includes all available Tags as badges.

The active Tags are displayed as Green badges in the Tag bar and can be switched off by clicking on them.

Light Grey Tag Badges means that the Tag does not include any Document Objects of the Document Object Type used in the current view (i.e. filtering on that tag would not produce any visible change).

Dark grey Tag Badges (not disabled) are viable for activation but currently not active.

A view that is filtered on some Tags, will only displaying objects belonging to the Tags.

An Example on how Tag-filtering Works

We have created a Tag with the name 'My Requirements'. The Tag include 3 document objects: RQ 3, RQ 7 and RQ 14. The system contains plenty more Requirements and Specifications.

Since the Tag 'My Requirements' only include document objects of the type 'Requirements', the tag can only be switch active from chapters of the Requirement type. When the tag is activated and displayed as green, only RQ 3, RQ 7 and RQ 14 appear in the chapter tree. Also all chapters that now are empty due to tag filtering are hidden from the view. Chapters that really are empty or contain one of the document objects above are still visible.

With the tag still active, let's switch to the chapter view for all Specifications. Here all document objects are displayed since no document object in the active tag is of type 'Specification'. However if we display one Specification which has traces from multiple Requirements and inspect the Traced From tab, it would only display the traces RQ 3, RQ 7 or RQ 14. Also this content is affected by the active tag.

The option 'Add new Objects if Active' in action

If our tag would have the option Add new Objects if Active checked in the tag, any newly created document objects would automatically be added to the tag if the tag is active when they are created. This also includes document objects that are created via copy, generate or execute.