# Using the Requirement Hierarchy Viewer (Registration & Dossier Management)

<a href="/en/gr/71498/">Registration & Dossier Management</a> provides you with the Requirement Hierarchy Viewer on _Registration_ and _Registration Item_ records, which displays all related _Requirements_ in a hierarchical structure, allowing you to review and adjust the records, nested order, and matched documents before generating a <a href="/en/gr/76898/">Dossier Binder</a> for a root _Requirement_.

Depending on your <a href="/en/gr/623830/">Admin's configuration</a>, object, field, and section labels may appear differently than the labels mentioned in this article.

<a href="https://platform.veevavault.help/assets/images/cp-rdm-requirement-viewer.png" data-lightbox="cp-rdm-requirement-viewer.png" data-title="" data-alt="Requirement Hierarchy Viewer">
  <img class="docimage" src="https://platform.veevavault.help/assets/images/cp-rdm-requirement-viewer.png" alt="Requirement Hierarchy Viewer" style=""  />
</a>

## About the Requirement Hierarchy Viewer {#about}

The viewer has the following conventions and behavior:

* The viewer displays up to 500 _Requirements_, including their descendant requirements up to ten (10) depth levels, based on their _Parent Request Requirement_ values.
* By default, the viewer displays up to 100 hierarchical descendant records for each parent record.
* For _Requirements_ generated by the _Generate Requirements_ and _Update Requirements_ actions, records are initially listed according to the _Default Order_ value of the related <a href="/en/gr/71503/#define-req">_Requirement Libraries_ </a> in the associated template until any user [reorders them][1].
* The viewer displays <a href="/en/gr/32749/">matched documents</a> for each related _EDL_ and _EDL Item_.
  * Each document displays an icon denoting the file type.
  * Locked documents are denoted with a lock (<img class="inline" src="https://platform.veevavault.help/assets/images/cp-icon-lock.png" alt="Lock Icon" style="" />) icon.
  * Any requirements referencing a source display the source's matched documents unless any user <a href="/en/gr/71503/#customizing">customized</a> them.
  * If no documents match to a particular record, the viewer displays "No documents found" for that item.
  * If a _Requirement_ is not linked to any _EDLs_ or _EDL Items_, the viewer displays no document details for that item.
* The viewer hides any records, actions, <a href="/en/gr/52224/">documents</a>, headers, columns, and cell values you do not have the appropriate permissions to view.

## Interacting with the Viewer {#interact}

You can interact with the viewer in the following ways:

* Apply **Filters** to specify which records the view displays. Depending on your Admin's configuration, some filters may appear by default. 
* Click on any hyperlink name to navigate directly to that record or document. 
* Click a caret (<i class="fas fa-caret-down"></i>) icon to collapse or expand a section to view any descendant records and matched documents.
* Click **Expand All** or **Collapse All** to display or collapse all sections.
* Click **Show More Documents** to see all matched documents for a record.
* Click **Show More Records** to see all descendant records for a parent record.
* Hover over a document name to view the <a href="/en/gr/55692/">document's hovercard</a>.
* Hover over any text to display a cell's full value (up to 1,500 characters).
* Hover over an active record or document to see its **Actions** menu and click it to view and run available actions. When the action completes, the viewer refreshes to display the latest data.
  * Use the **Move Up** or **Move Down** actions to [reorder the requirements][1] and specify their order in generated [Dossier Binders][2].
  * You cannot add matched documents or upload new documents if the parent requirement has the _Use Source_ checkbox selected.

## Reordering Requirements {#reorder}

When configured by your Admin, you can reorder _Requirements_ directly in the viewer. Vault reflects the updated order in any [Dossier Binders][2] you generate for the parent _Requirement_. To do this, click the **Actions** menu for any active _Requirement_ and select **Move Up** or **Move Down** to move that item and all its descendants. You can move items within the same parent record but cannot move any item to a different parent.

Depending on your Admin's configuration, you may be able to view and select additional actions from the **Actions** menu of active records.

<a href="https://platform.veevavault.help/assets/images/cp-rdm-rh-viewer-reorder.png" data-lightbox="cp-rdm-rh-viewer-reorder.png" data-title="" data-alt="Reorder Requirement Hierarchy Viewer">
  <img class="docimage" src="https://platform.veevavault.help/assets/images/cp-rdm-rh-viewer-reorder.png" alt="Reorder Requirement Hierarchy Viewer" style="max-width: 50%;"  />
</a>

When you reorder items, Vault considers any hidden records you do not have permission to view when you reorder items above or below hidden records. For example, if you cannot see the _5 Safety Assessment_ record in your viewer and move _6 Competent Authority_ above _4 Cosmetovigilance_, another user that does have permission to view all records will see the following order in their viewer:

* _6 Competent Authority_
* _4 Cosmetovigilance_
* _5 Safety Assessment_

<div class="note-border alert-info">
  <div class="alert alert-info" role="alert">
    <div><i class="far fa-info-circle"></i></div>
    <div class="alert-text">
      <p><strong>Note</strong>: If another user is reordering <em>Requirements</em> simultaneously, you may see some records arranged according to that user’s specified order when you refresh the page after reordering.</p>
    </div>
  </div>
</div>



## Creating Dossier Binders {#binders}

After reviewing all items in the viewer and making any necessary changes, you can create a Dossier Binder for the top-level _Requirement_. See <a href="/en/gr/76898/">Working with Dossier Binders</a> for more details.

## Limitations {#limitatations}

The following limitations apply to the Requirement Hierarchy Viewer:

* If you add documents directly in the viewer before running the _Add Matched Documents_ action, those documents are not selected in the list of existing matched documents in the dialog. You do not have to re-add those documents.
* When you run actions on a _Requirement_, the viewer may not reflect changes on child records, when applicable.
* If you refresh the page immediately after uploading a new document, the document's actions may not appear when you click its **Actions** menu in the viewer. If this happens, wait a moment and refresh the page again.
* The viewer does not display full values of truncated text for Rich Text or Long Text fields.
* Some internet browsers may not display the viewer as expected when you open a duplicate tab in your browser window. We recommend using a <a href="/en/gr/7413/#veeva_snap">supported version</a>  of Google Chrome or Microsoft Edge for optimal display.

The viewer will not display, and Vault will display a message to notify you that something went wrong if it encounters any of the following issues:

* There are more than 500 related records or 2,000 matched documents.
* Any related _Requirements_ are associated with more than one (1) _EDL_ or one (1) _EDL Item_.
* There are missing descendant _Requirements_ that are not related to the _Registration Objective_ or _Registration Item_ for which you've opened the viewer but have a _Parent Request Requirement_ value for any of the _Requirements_ displayed in the viewer.
* You do not have the appropriate permissions. Contact your Admin for more details.

[1]: #reorder
[2]: #binders





