# About the New Submissions Archive Viewer

Starting in 22R3, the Submissions Archive Viewer is enhanced with a new user interface that streamlines the submission review process with advanced searching, filtering, and document viewing capabilities.

This [new way to view submissions](/en/lr/450731/) in your Vault replaces the existing [legacy](/en/lr/45073/) viewer.


### Submissions Archive Viewer Demo {#viewer}


This video demonstrates how to use the Submissions Archive Viewer.
<video controls width=860 height =504  preload="metadata">
    <source src="https://platform.veevavault.help/108e9b1d-559c-4d48-918b-1e4c5b5a533c/da550d7d-c256-45ed-9605-8364245ddbd4/da550d7d-c256-45ed-9605-8364245ddbd4_source__v.mp4#t=0.5" type="video/mp4" >
    </video>


## Settings & Enablement

### Settings

The new Submissions Archive Viewer is enabled by default in all existing and new Submissions Archive Vaults as of 23R1 (22R3.4).

While the viewer itself does not have its own enablement setting, you can enable the viewer's related settings, **Enable identifying empty sections in the viewer** and **Show inactive Applications and Submissions in Viewer** in **Admin > Settings > Application Settings**. See [RIM Application Settings & Configuration Options](/en/lr/53688/) for more information.

### Enablement

The new Submissions Archive Viewer is automatically available. Admins cannot disable the new viewer or re-enable the legacy viewer.

We encourage user feedback for future enhancements, which you can provide in the RIM Submissions and Submissions Archive <a class="external-link " href="https://veevaconnect.com/login" target="_blank" rel="noopener">Veeva Connect Community<i class="fa fa-external-link" aria-hidden="true"></i></a>.

## New Viewer Highlights

The new Submissions Archive Viewer gives regulatory reviewers a greatly-improved user interface for working with submission documents and data, similar to the experience of working with content plans and active dossiers.

Admins configuring the new viewer benefit from a lower implementation time, as it includes many previously-configured legacy viewer features.

### Search & Filter in Hierarchy & Grid Views

The new Submissions Archive Viewer leverages the _Submission Metadata_ object to present _Application_ and _Submission_ data in side-by-side hierarchy tree and grid views. This new format greatly improves upon the legacy viewer's binder structure, as it allows users to:

  * Search the _Name_ column in the hierarchy tree to quickly filter nodes titled with keywords like "study reports".
  * Add, remove, and rearrange columns, corresponding to dossier metadata. Vault also remembers the selected columns and displays them each time users access the viewer.
  * Expand and collapse the view at the _Application_ root node when viewing applications with a large number of documents. Similarly, the Correspondence document node can be filtered to quickly hide or display Correspondence documents and folders tagged with an associated _Application_.

### Document Viewing

Users can apply filters to the hierarchy structure, then open documents directly in the viewer. When a user clicks a document, Vault maintains the hierarchy structure in the left-hand panel and displays the document on the right. The document view is similar to viewing a document in the Library, with bookmark, annotation, and search capabilities.

### Navigate to Content Plan and Source Document

The following User Actions are available to review in-process submissions from the new Submissions Archive Viewer:

* Open Content Plan
* Open Content Plan Item
* Open Source Document

Open Content Plan and Open Content Plan Item enable users to navigate to the Submission Content Plan in RIM Vaults with RIM Submissions Publishing.

### Related Permissions

Users with appropriate permissions to use the legacy viewer are able to access the new viewer without any additional security configuration. However, we recommend Admins confirm the intended users are assigned a _Full User_ Submissions Archive application license. (Unlike most Vault applications, [application licensing](/en/lr/5721/#application-license) directly controls user access to RIM Submissions Archive features.)

Users may have previously been able to access the new viewer with incomplete application licensing credentials. In 23R1, the licensing enforcement described here specifically includes the new viewer.

## Feature Comparison

|Category|Viewer Feature|Legacy Viewer|New Viewer|Notes & Limitations|
|--- |--- |--- |--- |--- |
|Filtering|Application selector|Y|Y||
|Filtering|Filter by Application fields|N|Y|Filter by fields to narrow Application list|
|Filtering|Filter by Name (keyword search)|N|Y||
|Filtering|Filter by Submission|Y|Y||
|Filtering|Filter by Submission related objects (join records)|Y|Y||
|Filtering|Filter on Submission fields|Y|Y|Added for the new viewer in 23R1 (22R3.4)|
|Filtering|Filter on Submission Metadata fields|N|Y|Actions menu includes an option to edit columns, and each column header is a filter. In 23R1 (22R3.4), the filter for the `sequence_order__v` date field is replaced by the _Actual Submission Date_ field on the _Submission_ object.|
|Filtering|Hide Application-level Correspondence|N|Y||
|Filtering|View inactive Applications and Submissions|Y|Y|Added for the new viewer in 23R1 (22R3.4)|
|Navigation|Collapse tree view at the Application root node|N|Y||
|Navigation|Expand all for a single Submission|Y|Y|Added for the new viewer in 23R2 (23R1.2)|
|Navigation|Expand all under a section|N|Y||
|Navigation|Expand and collapse section|Y|Y||
|Navigation|Navigate to Application and Submission record pages|Y|Y||
|Navigation|Navigate to embedded links|Y|Y||
|Navigation|Navigate to hyperlinks|Y|Y||
|Sorting|Sort Correspondence documents alphanumerically|N|Y||
|Sorting|Sort direct descendants alphanumerically|N|Y||
|User Settings|Custom layout|N|Y|Each metadata field column position and width can be manipulated|
|User Settings|Save user preferences|Y|Y||
|User Settings|Save view|Y|Y|Added for the new viewer in 23R1 (22R3.4)|
|View|Document and Section ordering|Y|Y||
|View|Empty Section Indicator|Y|Y|Added for the new viewer in 23R1 (22R3.4)|
|View|List view|Y|N|Not applicable to the new viewer, as it does not depend on Binder functionality.|
|View|Outline view|Y|Y||
|View|Section cumulative view|Y|Y||
|View|Tree view display limit|N|Y|Users can view up to 3,000 nodes in the viewer, after which filtering must be applied.|
|View|View documents, including Correspondence documents|Y|Y|Embedded document viewer overlaid on the grid|
|View|View document hovercard|Y|Y||
|View|View historical lifecycle|Y|Y||
|View|View leaf details|Y|Y||
|View Export|Export Dossier tree view to Excel|N|Y|Users must select a single Submission for the export option to appear in the Actions menu, and exports do not respect filtering.|
|User Permissions|Automatic application licensing enforcement|Y|Y|Added for the new viewer in 23R1 (22R3.4)|

## System-Managed Objects

Submissions Archive functionality manages object records in Vault. As such, Vault does not allow _Submission Metadata_ (`submission_metadata__v`) or _eCTD Metadata_ (`ectd_metadata__v`) object records to be created or deleted. Vault additionally prevents updating standard (`__v`) and system-managed fields within these records, as they are required to properly display imported and published submissions in the viewer.

<div class="note-border alert-important">
  <div class="alert alert-important" role="alert">
    <div><i class="far fa-exclamation-circle"></i></div>
    <div class="alert-text">
      <p><strong>Important</strong>: Veeva RIM does not support custom SDK triggers on the <em>Submission Metadata</em> and <em>eCTD Metadata</em> objects. These objects and their data fields are system-managed. Veeva RIM exclusively manages this data to ensure that imported and published submissions display correctly in the Submissions Archive Viewer. Attempting to use custom triggers on these objects can interfere with this core functionality.</p>
    </div>
  </div>
</div>



## Known Issues & Limitations {#known-issues-and-limitations}

The following items are known limitations to or defects of the new Submissions Archive Viewer:

  * The _Submission_ object must have a corresponding object lifecycle [enabled](/en/lr/30683/#enable-lifecycles) in the Vault. At a minimum, the object lifecycle must remain _Active_ for the viewer to properly function.
  * Vault does not respect any applied filters when exporting the hierarchy tree to Excel. Additionally, users must filter the grid to a single submission for the option to export to appear in the viewer's **Actions** menu.
  * Vault does not respect any applied filters when using the **Expand All** action. When a filter is applied, the the viewer expands all of the nodes underneath the **Expand All** section.
  * While there are no limitations on the number of _Submissions_ the viewer can display, users can only view up to 5,000 hierarchy nodes at a time. When the limit is reached, the viewer displays a message prompting the user to refine the view with filters. You can use the Collapse All action to remove sections so they do not count towards the 5,000 hierarchy node limit.

[1]: #known-issues-and-limitations
