# RIM Application Settings & Configuration Options Various settings, actions, and configuration options are available across RIM Vaults. ## Settings To enable an application setting, navigate to **Admin > Settings > Application Settings** and set the appropriate checkbox: ### Active Dossier Settings * **Active Dossier Viewer - Default filter by Product Family Application**: When selected, the default when filtering by _Product Family_ in the Active Dossier Viewer is to filter records by _Product Family Applications_. When deselected, the default is to filter records by _Product Family Products_ and _Product Family Active Substances_. * **View or Edit Active Dossier from Transaction – Default filter by Transaction**: When selected, the default when viewing or editing Active Dossier from a _Submission_, _Regulatory Objective_, or _Event_ record is to filter records by that transaction record directly. When deselected, the default is to filter records by the transaction record's relationships. ### Linked Documents * **Allow creation of link annotations**: Enables or disables [link annotations](/en/lr/15303/) in RIM Vaults. * **Enable Create & Import Document Links**: When enabled, document links appear in the Doc Info pane's [**Linked Documents**](/en/lr/15303/#view-linked-documents) section. Users can create or remove document links without creating annotations. * **Allow creation of links to whole documents**: When enabled, users can link to whole documents when creating references. * **Bring forward Linked Document relationships to new versions**: Allows users to [preserve link annotations](/en/lr/18648/) as Linked Document relationships when versioning the source document. ### RIM Settings * **RIM Dynamic Linking**: [Dynamic Linking](/en/lr/57859/) allows Vault to update Microsoft Word DOCX documents to include PDF named destinations for each heading, table, figure, and title style in the document. * **Synchronize regulatory objective and submission relationship**: Enabling this setting ensures that Vault syncs data from the single-select _Regulatory Objective_ value on the _Submission_ record to many-to-many object records. Use this setting to preserve your data before you enable bundling and the many-to-many relationship between _Submissions_ and _Regulatory Objective_ records in your RIM Vault. * **Automatic creation of Submission Country records**: Enables Vault to [automatically create a _Submission Country_ record](/en/lr/65236/) based on the application's _Lead Market_ country or any _Application Country_ records that already exist when users create a _Submission_ record. * **Automatic creation of Submission Language join records**: Enables Vault to [automatically create](/en/lr/65236/#product-family-joins) _Submission Language_ join records when users create new _Submission Country_ records. This option is only available once you set the **Automatic creation of Submission Country records** checkbox. * **Automatic creation of Application Country records**: Enables Vault to [automatically create an _Application Country_ record](/en/lr/65236/) based on the selected _Lead Market_ country when users create an _Application_ record. * **Automatic creation of Product Family join records**: Enables Vault to [automatically create](/en/lr/65236/#commitment-application) _Product Family_ join records when users populate the _Primary Product Family_ (`product__v`) field on certain objects. * **Automate the Sequence ID creation**: Enables Vault to automatically calculate and assign a _Sequence ID_ (`xml_submission_id__v`) when users create a new _Submission_ record. * **Automatic creation of Commitment Application records**: Enables Vault to [automatically create](/en/lr/65236/#commitment-application) _Commitment Application_ records when users populate the _Related Application_ field while creating or updating _Commitment_ records. * **Enable Application Relationships**: This setting applies to RIM customers enabling the Submission Wizard. For Vaults with RIM Registrations, the setting also changes the behavior of the Create Related Records and Bundling wizards and Global Content Planning. Once you enable this one-way setting in any RIM Vault, you cannot disable it. * In RIM Submissions, this setting enables the [Submission Wizard](/en/lr/78228/), which guides users through creating a _Submission_, _Regulatory Objective_, and their relationships. This feature also includes several two-way settings: * **Enable Relationship Triggers** enforces validation and data automation on _Application_, _Regulatory Objective_, and _Submission_ relationships. * **Exclude Submission Lifecycle States** allows an Admin to choose _Submission_ lifecycle states in which to prevent related [_Application_ relationships](/en/lr/73649/#managing-application-relationships) from being edited or deleted. * **Exclude Regulatory Objective Lifecycle States** adds increased flexibility for updating [_Application_ relationship](/en/lr/73649/#managing-application-relationships) fields that may change throughout the life of an application. In addition, the new field values automatically cascade onto existing relationship fields on _Submissions_ and _Regulatory Objectives_ that are in non-excluded lifecycle states. Admins can determine the fields that remain editable and the Submission and Regulatory Objective lifecycle states to be excluded from the cascade updates functionality. * In RIM Registrations, this setting updates the wizards to reference _Application_ relationship records as the source of truth while [creating](/en/lr/59835/#enabling-application-relationships) _Activities_, _Submissions_, and _Regulatory Objectives_ in bulk or [bundling](/en/lr/50545/#enabling-application-relationships) _Activities_ or _Regulatory Objectives_. In Vaults created on or after 24R3, enabling this setting also automatically enables the Registrations setting for [dynamic validation][3]. * **Activate the standard Translation Relationship**: Enabling this two-way setting activates and displays the standard Translation document relationship panel on all document pages. Organizations using custom relationships can disable this setting. * **Enable Initiate Response**: Enables Vault to create a response record, start a submission, auto-generate a content plan, and create a response document from a single, guided flow. The **Select Response Templates** subsetting supports the selection of one or more formatted outputs configured in your Vault. Admins can also add the [**Pull Objective Data** user action](/en/lr/67245/) on any lifecycle state of the _Submission_ object lifecycle to enable Vault to asynchronously pull any _Regulatory Objective_ join records to any new _Submission_ record. ### RIM Query Actions * **Submission Object**: This selection controls the sort order of the Submission records in the returned CSV for the Chronology Report. Sort always shows most recent dates first and oldest dates last. * **Commitment Object**: This selection controls the sort order of the Commitment records in the returned CSV for the Chronology Report. Sort always shows most recent dates first and oldest dates last. * **Document Type**: Vault only includes documents with the specified document type in the query results. The document type you select needs to have at least one document field referencing the Application object. * **Application Field**: Vault uses this field to determine which documents are related to the application on which a user triggered the query. * **Date Field for Sorting**: Vault uses this date field to order the chronology query in reverse chronological order. ### Registrations Features * **Use regulatory objective data as source in manage registered details wizard**: When enabled, Vault pulls data from _Regulatory Objective_ records rather than _Submissions_ to [create registration data](/en/lr/43108/). * **Configure Registration History Report**: Enables the [Registration History Report](/en/lr/61211/). Use the drop-downs to select the fields on the _Regulatory Objective_, _Registration_, and registered details objects that you wish to include as columns in the report. * **Send manage registered details data for verification**: When enabled and [configured](/en/lr/71639/), Vault starts a verification workflow upon completion of the [Manage Registered Details](/en/lr/43108/#verification) wizard before creating or updating any impacted records. Along with supporting configuration, the optional **Verification State Types** and **Select Verification Groups** [subsettings](/en/lr/71639/#enable-verification) specify when verification occurs and/or the groups allowed to participate in the _Registration Data Verification_ workflow. * **Enable Configurable Impact Assessment Reports**: Allows for the use of user-defined reports and custom report types when [generating Impact Assessment Reports](/en/lr/43119/). Use the drop-down to select the report types to use for Impact Assessment Reports. * **Execute Registrations SDK triggers**: RIM Registrations Vaults include several Vault Java SDK record triggers that are automatically enabled. Clearing this setting [prevents these triggers from running during Vault migrations](/en/lr/64586/). We do not recommend turning this setting off during normal business operations. * **Set naming pattern for Regulatory Objective Name when using Create Related Records wizard**: Allows you to set the naming pattern for new _Regulatory Objective_ records created through the Create Related Records wizard. See details about [configuring naming patterns](/en/lr/59835/#naming-patterns). * **Set naming pattern for Submission Name when using Create Related Records wizard**: Allows you to set the naming pattern for new _Submission_ records created through the Create Related Records wizard. See details about [configuring naming patterns](/en/lr/59835/#naming-patterns). * **Define default Activity scope when using Create Related Records wizard**: Allows you to select the default _Activity Scope Level_ for the [Create Related Records](/en/lr/31322/) wizard. Vault automatically selects this scope when users create activities in the wizard, but users can choose a different value. * **XEVMPD Attachment Only Notification Recipients**: Allows you to select the groups who will receive notifications from the EMA related to [XEVMPD attachment-only submissions](/en/lr/57152/). * **XEVPRM Message Sender**: Allows you to enter the XEVPRM message sender for [attachment-only submissions](/en/lr/57152/). This is a label that is registered with the EMA. * **Enable Labeling Automations**: Enabling this two-way setting allows Vault to [automatically](/en/lr/73989/#automatic-record-creation) copy _Labeling Concept_ records to underlying _Activity_ records, create _Labeling Deviation_ records based upon the outcome of an _Activity_ lifecycle, and calculate _Safety Category_ and _Due Date_ based upon labeling records. Vault ignores this setting and does not create _Activity Labeling Concepts_ when the [Update Local Regulatory Information](/en/lr/8913021/) wizard is [enabled][5]. * **Skip Duplicate Check for Dependency Automation Trigger** allows Vault to cascade deviation information to dependent markets. To do this, Vault skips the check which prevents the creation of more than one _Labeling Deviation_ per _Activity_ and _Labeling Concept_. This can be useful for organizations where a single labeling concept is associated with multiple deviations. To use this setting, review and [update](/en/lr/73989/#creating-labeling-deviations-for-all-dependent-markets) your Vault's _CCDS Section_ field configuration as required. * **Add Labeling Deviation Fields to copy on Dependency Automation Trigger**: Vault copies the selected fields' values to the new records it creates when setting the _Deviation Review Disposition_ to _Accepted for Dependent Countries_. Fields which Vault already auto-populates are not available for selection. * **Enable configurable eAF Reports**: Allows users to generate [variation and product reports](/en/lr/5062580/) for working with eAF web forms in the EMA portal. * **Default Document Set on Activity**: Sets the [_Document Set_](/en/lr/77854/#configuring-document-sets) on newly-created _Activity_ records based on the _Related Application_ and _Impacted Market_ field values. When enabled, Vault overrides any configured defaults and defaults the _Document Set_ field. * **Use regulatory objective data as source when bulk creating registrations**: When enabled with Activity and Objective Bundling, Vault pulls data from _Regulatory Objective_ records rather than _Applications_ when creating product, investigational, active substance, and manufacturing site registrations [in bulk](/en/lr/57203/). * **Enable Counts of Total Events and Completed Events for Change Items**: This setting enables Vault to automatically track and display the total number of _Events_ to which a _Change Item_ is related, and the number of those _Events_ which have been completed, according to the **Completed Event States** selected in the subsetting. This provides users with a clear understanding of the completion status of _Change Items_ across all related _Events_, for example market registrations. To do this, Vault increases the _Completed Events_ field value on any related _Change Items_ when an _Event_ enters one of its configured **Completed Event States**, and decreases this value when an _Event_ moves to any non-completed state. Similarly, each time a _Change Item_ is added or removed from an _Event_, Vault increases or decreases the item's _Total Events_ field value. * **Enable Grouping of Change Items by Product Family**: This setting minimizes the number of individual *Change Item* records which must be reviewed within the [Create & Manage Event Details](/en/lr/5498722/), [Create Related Records](/en/lr/31322/), and [Update Local Regulatory Information](/en/lr/8913021/) wizards, as well as when splitting [_Activities_](/en/lr/4946040/) and [_Regulatory Objectives_](/en/lr/50022/). This can be helpful for assessing and dispositioning single changes that involve many products and/or packaging types, such as for a change to a manufacturing process. The *Change Item*, *Event Change Item*, and *Activity Change Item* objects must be configured to use the *Change Item* object type when enabling this setting. * **Enable Activity and Objective Bundling**: A one-way setting which enables users to bundle and split _Activities_ and _Regulatory Objectives_. When selected, Vault sets the _Regulatory Objective_ field on the _Submission_ object to _Inactive_, enables the _Submission Regulatory Objective_ relationship, and disables synchronization between _Submission_ and _Regulatory Objective_ records. Enabling the flag also allows Admins to configure lifecycle actions on the _Regulatory Objective_ and _Activity_ lifecycles. * **Restrict Activity bundling by state**: Filters the list of _Activities_ in the [bundling and splitting wizards](/en/lr/49520/) based on the **Lifecycle States** you select. * **Restrict Regulatory Objective bundling by state**: Filters the list of _Regulatory Objectives_ in the [bundling and splitting wizards](/en/lr/49520/) based on the **Lifecycle States** you select. * **Restrict Submission copying for worksharing**: Adds an option on the [bundling wizard](/en/lr/49520/)'s **Define Submissions** step to create additional _Submission_ records for EU worksharing. Select **Submission Types** to filter the list of _Submissions_ that may be copied for worksharing in the bundling wizard. * **Restrict Submission record creation for US grouping**: Adds an option on the [bundling wizard](/en/lr/49520/)'s **Define Submissions** step to create additional _Submission_ records for US grouping. Select **Submission Types** to filter the list of _Submissions_ that may be copied for US grouping in the bundling wizard. * **Mark Submissions as inactive during bundling**: Adds an option on the [bundling wizard](/en/lr/49520/)'s **Define Submissions** step to deactivate _Submissions_. Select **Starting States** to filter the list of _Submissions_ that may be deactivated. Select a **Target State** as the inactive lifecycle state to apply to the _Submissions_. * **Default filters for Activity**: Adds default filters to the _Activity_ list in the [bundling and splitting wizards](/en/lr/49520/). Vault applies lifecycle states you selected under **Restrict Activity bundling by state** as default filters. Select **Activity Fields** to use as filters for _Activities_ in the bundling and splitting wizards, for example _Impacted Market_. * **Default filters for Regulatory Objective**: Adds default filters to the _Regulatory Objective_ list in the [bundling and splitting wizards](/en/lr/49520/). Vault applies lifecycle states you selected under **Restrict Regulatory Objective bundling by state** as default filters. Select **Regulatory Objective Fields** to use as filters for _Regulatory Objectives_ in the bundling and splitting wizards. * **Mark Regulatory Objectives as inactive during bundling**: Adds an option on the [bundling wizard](/en/lr/49520/)'s **Define Submissions** step to deactivate _Regulatory Objectives_. Select **Starting States** to filter the list of records that may be deactivated, for example the _Planned_ state. Select a **Target State** as the inactive lifecycle state to apply to the _Regulatory Objective_ records. * **Regulatory Objective Naming Pattern**: Adds an option to define the naming pattern for new _Regulatory Objective_ records Vault creates during the [bundling process](/en/lr/49520/). The default naming pattern is `{application__rimr.name__v} - Bundle`. * **Mark Activity Labeling Concepts as inactive during bundling**: Adds an option on the [splitting wizard](/en/lr/4946040/)'s **Activity Labeling Concepts** record definition page to deactivate _Labeling Concepts_. Select **Starting States** to filter the list of records that may be deactivated, for example _Active_ and _Rejected_. Select a **Target State** as the inactive lifecycle state to apply to the _Labeling Concept_ records. * **Activity Naming Pattern**: Adds an option to define the default naming pattern for the new _Activity_ records Vault creates during the [splitting process](/en/lr/4946040/). The default naming pattern is `{impacted_market__rimr.country_code__rim}-{related_application__rimr.name__v} - Split`. * **Relate Bundled and Split Regulatory Objectives and Submissions to Events**: When users create _Regulatory Objective_ or _Submission_ records via bundling or splitting, this setting allows Vault to relate them to the _Event_ for any _Activity_ selected in the wizard. * **Enable Affiliate Home Page**: Turns on the [**Affiliate Home**](/en/lr/53864/) tab. Once you set this checkbox, you can customize what users see on the tab: * **Select activity lifecycle states to show on home page**: Allows you to show only _Activity_ records in the specified lifecycle states on the Affiliate Home tab. We recommend selecting only in progress or active lifecycle states. * **Select regulatory objective lifecycle states to show on home page**: Allows you to show only _Regulatory Objective_ records in the specified lifecycle states on the Affiliate Home tab. We recommend selecting only in progress or active lifecycle states. * **Select the actions to be displayed on the affiliate home page**: Allows you to choose which actions are available in the Quick Actions bar. * **Select the graphical data widgets to be displayed on the affiliate home page**: Allows you to choose which chart panes appear on the Affiliate Home tab. * **Enable IDMP and UDI Accelerators**: Allows Vault to automatically generate related records for certain IDMP objects. Once you enable this feature, set the individual checkboxes to enable each IDMP [accelerator](/en/lr/60772/#accelerators): * **Automatically Generate Medicinal Product Records**: When users create new _Marketed Drug Product Registration_ records, Vault automatically creates related _Medicinal Product_ and _Medicinal Product Registration_ records. You'll also need to set the **Regions** and **Lead Market Field**. Optionally select **Eligible Registration Types** for Vault to create according to your organization's requirements, such as for animal health products. This functionality is not currently intended for investigational products and will be supported in a future release. * **Automatically Generate Registered Site Role Records**: Vault creates _Registered Site Role_ records when users create certain related records. * **Automatically Generate Registered Packaged Product Records**: Vault creates _Registered Packaged Medicinal Product_ records when users create certain related records. * **Automatically Generate Alias Records**: When users create _Active Substance_ or _Inactive Ingredient_ records, Vault automatically creates a corresponding _Active Substance Alias_ (`active_substance_translation__v`) or _Inactive Ingredient Alias_ (`inactive_ingredient_translation__v`). * **Enable Global to Local Submission Type Mapping**: When creating _Submission_ records [in bulk](/en/lr/31322/), this setting allows users to select a global term for the _Submission Type_ field (such as the term used for the original application) and populate the corresponding local term on the resulting records. See [Configuration for Bulk Creating Activities, Submissions & Regulatory Objectives](/en/lr/59835/#configuring-global-to-local-mapping) and [Configuring Constraints](/en/lr/43081/) for details on how to map these terms in your Vault. * **Enable Global to Local Submission Subtype Mapping**: When enabled with **Enable Global to Local Submission Type Mapping**, users can also select a global term for the _Submission Subtype_ field when creating _Submission_ records in bulk. * **Enable Global to Local Manufacturing Site Role Mapping**: When creating _Submissions_ and _Regulatory Objectives_ in bulk, this setting allows users to select a global _Manufacturing Site Role_ and populate the corresponding local term on the resulting relationship records. Vault also uses this setting during bundling or splitting, where the underlying _Constraint_ records are referenced to populate a global value (defined on the _Event_ relationship record) to the local _Manufacturing Site Role_ term on the new _Regulatory Objective_ relationship record. See [Configuring Constraints](/en/lr/43081/) for details on how to map these terms in your Vault. * **Enable UDI Enhancements for EUDAMED**: Once you enable this feature, set the individual checkboxes for UDI submissions: * **Enable UDI Submission Viewer**: Allows users to [review and manage](/en/lr/4667940/) complex UDI data in a user-friendly format. * **Enable machine-to-machine UDI submissions to EUDAMED**: When enabled and configured with the UDI Submission Viewer, this sub-setting allows users to submit UDI data to EUDAMED directly from a Registrations Vault. * **Enable enhanced UDI attribute locations** : Allows Vault to use new source data locations for UDI Submission XML generation, updated in 23R3. This setting [supports](/en/lr/165020/#same-basic-udi) multiple _Products_ sharing the same _Basic UDI_ within a single UDI submission. * **Enable default EUDAMED XML Version**: When generating a UDI submission, Vault automatically sets the indicated **XML Version**. This setting supports situations where, for example, a newer XML version is required, but there have not been any XSD updates for UDI submissions. When Vault sets this version, users generating UDI data are not required to manually override the default version. This setting is also useful for managing different version requirements for the EUDAMED Playground. * **Enable Create Related Records Review**: When creating Activities, Submissions, and Regulatory Objectives in bulk via the Create Related Records wizard, this setting enables users to [preview](/en/lr/31322/#reviewing-and-refining-related-records) the records Vault will create, then refine the list to remove any unwanted records. * **Disable Confirmation Pop-up when Skipping Review**: By default, when a user selects **Finish** from the wizard's Confirmation page, Vault displays a dialog where they must confirm their original Finish selection, or opt to instead **Cancel** or **Generate Preview**. This setting allows users to skip this secondary step, and can be disabled or enabled as needed. * **Enable IDMP Viewer Enhancements** includes various subsettings, each of which controls options within the IDMP Viewer's **Data View Selection** dialog. See [additional details](/en/lr/60772/#idmp-viewer-enhancements) about the dialog and these subsettings, which include **Prompt for IDMP Viewer User**, **Prompt for FHIR Message Selection in IDMP Viewer**, and two related options for PMS data, **Default IDMP Data View to Include PMS Data** and **Enable PMS Data in the IDMP Viewer**. * **Enable dynamic validation for Create Related Records and Bundling**: When the [Enable Application Relationships][1] setting is enabled, this setting prompts Vault to apply enhanced validation logic in the [Create Related Records](/en/lr/59835/#dynamic-validation) and [bundling](/en/lr/50545/#enabling-dynamic-validation) wizards. * **Enable dynamic procedure countries in Create Registrations**: When users [create Registrations](/en/lr/43102/) in bulk for centrally authorised procedures, Vault can reference the _Application_'s _Procedure Type_ value to dynamically populate default countries based on Region Specific Entry [_Constraints_](/en/lr/43081/#dynamic-procedure-countries) for that procedure. When the constraint defines a Health Authority, Vault also populates this value in the resulting registrations. * **Rerun dependency checks when labeling impact is identified**: This setting and related [configuration](/en/lr/71816/#non-labeling-event-config) allows Vault to create labeling-specific _Activity Dependency_ records when labeling impact is identified for a cross-functional, non-labeling _Event_. When an _Activity_ record's _Local Labeling Impact_ field is _Yes_, Vault locates [_Country Dependency_](/en/lr/71816/#non-labeling-event-overview) matches for the activity and creates related _Activity Dependency_ records. This setting also allows [configuration](/en/lr/71816/#application-dependencies-config) for _Application_-level dependencies across different markets, within the same market, and within the same _Application_. * **Active Dossier Registration Tracking**: This setting and related [configuration](/en/lr/71560/#configuring-active-dossier-registration-and-product-information-tracking) provides users a more granular view of the Active Dossier based on the _Registration_ and select product information details. These relationships are surfaced in the Active Dossier Viewer and are editable in the Active Dossier Editor. Vault creates records according to the **Valid Registration State Types** you've selected and configured on the object's corresponding lifecycle. You can update these values or disable the feature at any time. * **Allow creation of change items in Create Event Details**: When enabled with the **Exclude change item lifecycle states from Create Event Details** setting and an _Event_ includes _Change Items_, Vault pre-populates these records in the [Create & Manage Event Details](/en/lr/5498722/) wizard. Then, users can create additional _Change Items_ for that _Event_. This setting is enabled by default but can be disabled at any time, for example to allow the Quality-RIM Vault Connection to create these records instead. * **Exclude change item lifecycle states from Create Event Details**: To manage an _Event_'s related _Change Items_ in the [Create & Manage Event Details](/en/lr/5498722/) wizard, this setting requires you to select the _Change Item_ object **Lifecycle States** which Vault should filter when selecting items to display in the wizard. See [additional details](/en/lr/549872/#supporting-event-change-items-and-labeling-concepts) on enabling this feature with recommended lifecycle states. * **Enable Updating of Local Regulatory Information**: This setting and related [configuration](/en/lr/8913022/) sets an _Event_ record's _Local Regulatory Info Last Created_ field when users create local regulatory records in bulk via the [Create Related Records](/en/lr/31322/) wizard. Then, Vault references this field when users run the [_Update Local Regulatory Information_ action](/en/lr/8913022/) to push new or updated _Event_ details in bulk to these existing records when the _Event_'s scope increases or decreases. The optional **Lifecycle States** sub-settings prevent Vault from updating _Activity_, _Submission_, or _Regulatory Objective_ records in the selected states. * **Enable Assess Local Activities**: This setting and related [configuration](/en/lr/9299271/) allows RIM Registrations users to locate and disposition all _Activity Change Items_ for which they are responsible. See additional details on how to populate the required [subsettings](/en/lr/9299271/#app-settings). ### Submissions Archive Features {#submissions-archive-features} * **Show Correspondence in Viewer** 1: Allows users to [view correspondence documents](/en/lr/450731/#viewing-correspondence-documents) tied to a _Submission_ in the Viewer tab. You can select the **Document Type** to represent correspondence. * **Import files not referenced in the eCTD XML**: Allows users to upload files that aren't referenced in the [eCTD XML](/en/lr/28082/). * **Include Correspondence documents on bulk export**: Allows Vault to include correspondence documents in [bulk submission exports](/en/lr/42262/). * **Enable Submission dossier import through Bulk Action**: Allows users to [import a single dossier to multiple submissions](/en/lr/28082/#bulk-import). * **Allow imports to proceed with invalid XML**: Allows users to import submissions with invalid XMLs through the Vault UI. Vault will display a warning but won't block the submission import. * **Enable Submission Import from File Manager**: Allows users to [upload submission content in Vault File Manager](/en/lr/62385/) for import to _Submission_ records in Vault. * **Enable identifying empty sections in the viewer** 1: Allows Vault to calculate and apply a visual styling in the submissions archive viewer, indicating which sections in a submission do not contain documents. * **Process Zip imports at the Submission level**: Allows Vault to import ZIP files located inside the submission folder when importing a submission. When attachments are enabled, files at the root of the ZIP become attachments of the submission. * **Show inactive Applications and Submissions in Viewer** 1: Allows users to select and view the content of inactive applications and submissions within the Viewer. * **Leaf source file path correction**: When Configuration Mode is enabled, Admins can select this option to allow Vault to correct leaf source file paths based on the _Application_ _Dossier Format_ parameter and the _Application Folder Name_ field. This is useful for maintaining data integrity when an application associated with a previously-imported archive requires an update to its _Application Folder Name_. See [Correcting Leaf Source File Paths](/en/lr/263539/) for more information. 1. _Setting is available for both the [legacy](/en/lr/45073/) and [new](/en/lr/450731/) Submissions Archive Viewers. If already enabled for the legacy viewer, additional configuration in the new viewer is not required. Conversely, if the feature was not already enabled for the legacy viewer, it must be enabled for the new viewer. See [About the New Submissions Archive Viewer](/en/lr/450732/) for more information.↩_ * **Automatically populate records based on Imported Submission XML**: When enabled, Vault populates select fields on Object Data from values in an incoming eCTD XML. This is a one-way setting. Once enabled, it cannot be reversed. ### Submissions Features * **Allow batch import of CRFs**: Allows users to [import Case Report Forms](/en/lr/24705/) (CRFs) to Vault in bulk. Select a **Document Type** to apply to imported CRFs. * **Allow batch import of datasets**: Allows users to [import datasets](/en/lr/24705/) to Vault in bulk. Select a **Document Type** to apply to imported datasets. * **Enable Content Plan Comparison**: When dispatching global content plans, this setting allows users to dispatch one or more sections of a content plan, as well as review and accept or reject the changes Vault will make to the market-specific _Submission Content Plan_ based on a comparison with the source _Global Content Plan_. You must also select at least one _Content Plan_ **Lifecycle State** in which Vault can generate a comparison. To dispatch _Global Content Plans_ across templates, you must enable this setting. See [Configuring Content Plan Synchronization](/en/lr/77855/) for configuration details. * **Enable Dispatch Validation:** Allows Vault to validate that target _Activities_ and _Submissions_ are in valid lifecycle states prior to dispatching. When enabling this setting, select the **Supported Activity Lifecycle States** and **Supported Submission Lifecycle States** that you want to support for dispatch. Vault only dispatches to _Activities_ and _Submissions_ that meet the lifecycle state validation requirements. For _Activities_ and _Submissions_ that do not meet the lifecycle state validation requirements, an error message lists the _Activities_ and _Submissions_ that were not dispatched. * **Enable Improved Document Set Management**: Enables use of the Document Set object data model and corresponding functionality, including display and assignment of _Document Set_ relationships from the _Event_ page layout and Content Plan Viewer. This is a one-way setting and cannot be disabled. * **Enforce Document Set Assignment**: Enables precise control over dispatching Global Content Plans. * **When disabled (default)**: Records in the GCP without an assigned _Document Set_ are dispatched to **all** valid target submissions. * **When enabled**: Records in the GCP are dispatched only when they have an assigned _Document Set_ that is **relevant to the target submission**. This enforces explicit assignment for all dispatched content. ## Configuration Options {#configuration-options} ### Generating Compliant Renditions for Source PDFs Vault is able to render PDF source files according to ICH standards and minimize validation criteria failures prior to publishing. To enable this, navigate to **Admin > Configuration > Rendition Profiles** and click the name of the desired [rendition profile](/en/lr/153330/). Under _PDF Standardization_, select **Generate compliant Viewable Rendition for Source PDFs**. [CrossLink](/en/lr/23145/) PDF documents are rendered according to the rendition profile configured for the document type. This configuration option does not apply to secured or signed PDFs, or to PDFAs.
### Creating Documents from Emails The _Vault RIM Create Documents from Email_ processor extracts the content from emails sent to Vault and creates an unclassified document for the email and each attachment in the sender's Document Inbox. It supports RIM-specific use cases for Vault's standard email processing capabilities, such as: when a user receives an email from a Health Authority with an attached approval letter, the processor extracts the approval letter and uploads it as its own document, separate from the email and any other attachments. See [Email Processing (RIM)](/en/lr/50242/) for more information and detailed use cases. The processor is automatically enabled in all RIM Vaults in **Admin > Configuration > Email Processors** but requires additional configuration steps to use it, including: * Creating and testing inbound email addresses, as well as considering business needs for shared inboxes and duplicate content detection. See [Configuring Email to Vault](/en/lr/74285/) for more information. * Adding the _Created from email_ [shared document field](/en/lr/4884/#use-shared-field) to the document types your organization uses for emailed documents. This step is only required if you wish to display this information to users in the Doc Info panel. Otherwise, Vault still sets the document metadata automatically, allowing full search and filter capabilities. ### Correspondence Email Processing 1. The *Correspondence Email Processor* automates the initial steps of the correspondence intake process. To enable this, navigate to **Admin > Configuration**. To create a new Inbound Email Address, navigate to **Admin > Configuration > Inbound Email Addresses**. Set the Email Processor to _Create Documents from Correspondence Email_. 2. (Optional) Create a user group and add users. This group can be used for assigning roles and workflow participants. 3. (Optional) Create a multi-document workflow. Set participants to be added by role by selecting the _Use role as participants_ setting and include a task to notify participants about new documents in the inbox. Add this workflow to the Inbox lifecycle’s *Incomplete* state and ensure users have permission to participate in workflows and view unclassified documents. 4. Go to **Admin > Configuration > RIM Email Processors** and create a new processor. Select the *Inbound Email Address*. Only Inbound Email Addresses set with the Email Processor _Create Documents from Correspondence Email_ are displayed in the dropdown. 5. Choose a document type to assign to all documents, or select the Unclassified document type. 6. Optionally, enter a workflow (you must use the workflow’s API name). Create RIM Email Document Roles by assigning a lifecycle role to a user group. This allows user groups to be defaulted into the document’s Sharing Settings. All documents processed by the email processor are created in the Inbox lifecycle. The RIM Email Document Role also allows users to receive the workflow notifications, if configured. 7. Ensure senders can create unclassified documents and any selected document type. ### RIM Object Layouts In 24R1, the introduction of Action Layouts provides new options for configuring an object's Record Details Page. To support RIM, Veeva delivered Action Layouts for the below objects and their object types. All delivered layouts are standard, with **Layout Names** ending in `__v`. * Application * Regulatory Objective * Submission These layouts are inactive by default and cannot be activated or edited. To use them, create a copy of each, then configure the new layout according to your organization's requirements. See [Configuring Object Page Layouts](/en/lr/26387/) for configuration details and a feature demonstration. [1]: #rim-settings-enable-app-relationships [2]: #subs-enable-app-relationships [3]: #regs-enable-dynamic-validation [4]: #submissions-archive-features [5]: #update-local-regulatory-information