# Veeva Submissions Overview

Veeva Submissions is an end-to-end application to manage the authoring, review, approval, and assembly of regulatory submissions content, such as clinical study reports, manufacturing information, nonclinical reports, summaries, and labeling. Veeva Submissions also includes binder templates that allow assembly of content into defined submissions structures, such as the eCTD.

Veeva Submissions includes pre-configured document types and fields based on the DIA EDM Reference Model standard. A complex data model allows organizations to store additional data about submissions and documents. The application also provides several review and approval workflows to use for documents stored in the Vault.

Submissions is part of the [Veeva RIM family of applications](/en/lr/30696/). Within a single Vault, your organization can have one, two, or all of these applications. These applications share a common data model, but each provides additional pieces of functionality to help manage Health Authority applications.

## Submissions Features

Veeva Submissions is built on the Vault platform and includes the features described in the platform help topics. In addition, it includes these capabilities and configurations specific to managing documents for medical information inquiries:

  * **Document Types**: To facilitate quick on-boarding for new customers, new Vaults include a variety of default document types, subtypes, and classifications. The default document types are aligned with the required content for regulatory submissions, i.e., Clinical, Nonclinical, Quality, Regulatory, Pharmacovigilance and Literature.
  * **Lifecycles & Workflows**: Veeva Submissions includes lifecycles and associated workflows to facilitate authoring, review, and approval of content and of submission binders.
  * **Advanced Data Model**: To allow content sharing globally or locally for a specific market, and to provide rich metadata on each document, Veeva Submissions provides objects that store pertinent information and support reuse and searching of that data across multiple products and documents.
  * **Country- & Market-Specific Actions:** To allow for different review and approval processes globally, Veeva Submissions supports configurable document lifecycle and workflow actions based on a variety of document fields, including country.
  * **Content Planning**: With submission content planning, customers can move away from spreadsheets and quickly create a list of all documents they expect to collect as part of a submission in Vault. The _Content Plan_ object tracks all submission-specific information about each document.
  * **Active Dossier Viewer & Editor**: The Active Dossier Viewer lets sponsors see a document's status across multiple markets, while the Active Dossier Editor helps sponsors maintain a list of current documents for a given product and market.
  * **Report Level Content Plans & Publishing**: The _Report Level Content Plan_ object lets customers compile and publish reports outside of a submission, such as Clinical Study Reports, Nonclinical Study Reports, Periodic Safety Reports, and Investigator's Brochures.
  * **Dynamic Linking**: When publishing report level content plans, customers can create cross-document permalinks within the source document that target bookmarks and destinations within Vault. In Microsoft Word documents, links that you create can persist even as content changes during the authoring process. During publishing, Vault converts these links to standard relative PDF links.
  * **Publishing Status Indicator**: A status icon informs users if there are outstanding publishing or validation jobs. This ensures that users only review and submit content after it has been published and validated.
  * **CRF and Dataset Import:** Users can quickly and easily file all final subject CRFs and datasets into Vault. Vault automatically assigns the imported documents to the correct study/site and sets them to _Approved_ status and major version 1.0.
  * **SPL Rendition**: Vault can create PDF viewable renditions from uploaded SPL submission ZIP files.
  * **Submission Wizard**: Streamlines the process of defining the _Submission_ and _Regulatory Objective_ records and their relationships by allowing users to select from a controlled list of _Application_ relationships, which Vault copies to the selected _Submission_ or _Regulatory Objective_. This improves the data quality and data consistency of these records.

## Standard Jobs

### Delete Inactive Content Plans {#delete-inactive-content-plans}

The daily _Delete Inactive Content Plans_ job deletes unused, inactive _Content Plan_ and _Content Plan Item_ records, reducing the number of unnecessary records which can cause performance issues in some Vaults. This is especially relevant in Vaults where users prefer to [assemble a content plan](/en/lr/61032/) by starting with inactive records, then activating select records as needed.

Each time the job runs, Vault deletes up to 50,000 records that meet the following criteria:
* Status is _Inactive_
* The _Content Plan Item_'s _All Document Count_ (`all_doc_count__v`) equals zero (0) or is blank
* For [submission content plans](/en/lr/37474/), the Submission record's _Actual Submission Date_ (`actual_submission_date__rim`) is at least 365 days earlier than the current date
* For [report level content plans](/en/lr/47956/), the _Last Published Date_ (`last_published_date__v`) is at least 365 days earlier than the current date
* For [global content plans](/en/lr/77854/), the _Event Complete Date_ (`event_complete_date__v`) is at least 365 days earlier than the current date

Vault logs the deleted record details in a CSV file you can download from the [Job Status page](/en/lr/24762/).

#### Activating the Job

The _Delete Inactive Content Plans_ job is inactive in RIM Submissions Vaults by default. To schedule it, set the [Job Definition _Status_](/en/lr/22897/#how-to-edit-job-definitions) to _Active_.

We recommend Admins activate the job in most Vaults. However, the job can remain inactive in Vaults where automatic record deletion is deemed to interfere with any custom processes, configurations, or integrations.

#### Configuring & Using the Cleanup Status Field

The _Delete Inactive Content Plans_ job uses the _Cleanup Status_ picklist field to determine which records are eligible for deletion.

To view a record's _Cleanup Status_, you can add it as a column in the Content Plan Hierarchy Viewer. Optionally, you can also add the field to the page layouts of the following _Content Plan_ object types:
  * _Report_
  * _Report Level Plan Clinical Study_
  * _Report Level Plan Nonclinical Study_
  * _Root Content Plan_

As the job runs, Vault references the _Root Content Plan_'s _Cleanup Status_ field to determine whether to process the content plan records within the Root in the operation:
  * When the _Root Content Plan_ record has a status that is blank or _In Progress_, the records within the content plan are eligible for deletion when the deletion criteria is met.
  * When the root record has _Skip_ or _Error_ status, the job does not process the records within the content plan.
  * When only some of the inactive records have been cleaned up within a root record, Vault sets the status to _In Progress_. This is most likely to occur when the job reaches the limit of records it can delete during the current run.
  * When Vault encounters an error deleting records within a root record, it sets the field to _Error_.
  * When Vault successfully deletes all of the valid inactive records within a root record, it sets the field to _Success_.

All details are captured in the job log, which you can use to locate and review the _Error_ status records. Once you've resolved the error, you can clear the field on the _Root Content Plan_ record to allow Vault to assess it again during the next job run. Similarly, you can manually set the field to _Skip_ to prevent the job from processing the records within the _Root Content Plan_ during the next job run.

### Validation Results Archival

The daily _Validation Results Archival_ job allows users to reference validation results without cluttering their Vaults with unnecessary records. The job:

  * Creates an archive package ZIP file for a *Report Level Content Plan*'s validation results 365 days after the _Last Published Date_
  * Adds the archive package as an attachment on the _Report Level Content Plan_ record
  * Deletes the archived _Submission Validation Results_ records

## Standard Connections

### RIM to Clinical Operations Vault Connection

This connection between a RIM Submissions Vault and a Clinical Operations eTMF Vault automates data sharing between the two applications, supporting automatic transfer of _Product_, _Study_, and _Site_ data and documents. See details about the [RIM to Clinical Operations Vault Connection](/en/lr/60446/).

### RIM to PromoMats Vault Connection

This connection between a PromoMats vault and a RIM Submissions vault automates compliance package generation and submission to the FDA through the gateway. See details about the [RIM to PromoMats Vault Connection](/en/lr/72311/).

### Safety-RIM Connection Vault Connection

This connection between a RIM Submissions Vault and a Safety Vault automates transfer of product and registration details from RIM to Safety Vaults for case processing and reporting obligations. See details about the [Safety-RIM Connection](/en/lr/01272/).

## Related Articles

  * [Configuring Submission Content Plans](/en/lr/37474/)
  * [Using Submission Content Planning](/en/lr/37472/)
  * [Configuring Report Level Content Plans](/en/lr/47956/)
  * [Configuring Report Level Publishing](/en/lr/64522/)
  * [Using Report Level Content Plans](/en/lr/47965/)
  * [Using Dynamic Linking](/en/lr/57859/)
  * [Viewing Publishing Progress](/en/lr/67459/)
  * [Using the Content Plan Hierarchy Viewer](/en/lr/59502/)
  * [Configuring Constraints](/en/lr/43081/)
  * [Content Plan Filtering](/en/lr/46496/)
  * [Create a Document from Template for Content Plan Items](/en/lr/50478/)
  * [About SPL & XML Renditions](/en/lr/36690/)
  * [Configuring Cascading Review & Approval for Binder Content](/en/lr/38813/)
  * [Managing Content Plans with a Lifecycle](/en/lr/45365/)
  * [Creating Content Plan Templates](/en/lr/61032/)
  * [Configuring a Workflow for Matched Documents](/en/lr/59683/)
  * [Copying Into Content Plans](/en/lr/71665/)
  * [Using Keyboard Shortcuts in the Hierarchy Viewer](/en/lr/60553/)
  * [Starting a Workflow in the Content Plan Hierarchy Viewer](/en/lr/71667/)
  * [Using Saved Views](/en/lr/71666/)
  * [About the Progress Icon Field](/en/lr/64518/)
  * [Configuring Cascading State Changes for Content Plans](/en/lr/60549/)
  * [Configuring the RIM to Clinical Operations Vault Connection](/en/lr/60444/)
  * [About the RIM to Clinical Operations Vault Connection](/en/lr/60446/)
  * [Setting Up CRF & Dataset Import](/en/lr/24705/)
  * [About the RIM & PromoMats Vault Connection](/en/lr/72311/)
  * [Configuring the RIM to PromoMats Vault Connection](/en/lr/72309/)
  * [Using CRF & Dataset Import](/en/lr/24707/)
  * [Configuring Form 2253 Generation for Submissions](/en/lr/60981/)
  * [Generating Form 2253](/en/lr/24230/)
  * [About Active Dossiers](/en/lr/71782/)
  * [Active Dossier Configuration](/en/lr/71560/)
  * [Working with Active Dossiers](/en/lr/71673/)