# About RIM Object Configurations

_Rimobjectconfigurations_ define properties for RIM objects that are leveraged across multiple Submissions and Registrations features such as the Registrations and Submission wizards, Global Content Planning, and copying Content Plans. These properties include the display and editability of fields in the Registrations wizards and the uniqueness check for relationships in Submissions-related functionality.

_Rimobjectconfiguration_ records are provided for select standard RIM objects. Subcomponent _Rimfieldconfiguration_ records are provided for select standard fields on those objects and can also be configured for custom fields on those objects.

## Creating and Updating Records

You can configure Rimfieldconfigurations to modify the defined properties:
1. Navigate to **Admin > Configuration > RIM Object Configurations**.
2. Select the RIM Object Configuration for the object of interest. Note: The name of the RIM Object Configuration should match the object's _Name_.
    * Standard RIM Object Configurations should **not** be inactivated.
3. Select the RIM Field Configuration for the standard field of interest. Note: The name of the RIM Field Configuration should match the field's _Name_.
    * Standard RIM Field Configurations should **not** be inactivated.
4. Alternatively, you can create a custom RIM Field Configuration for a custom field of interest by clicking the **Create** button.
    * The _Name_ should be populated with the custom field name.
    * The _Object_ should be populated with the same object that the parent RIM Object Configuration record is created for. When using search functionality to find an _Object_ to add, search terms are case sensitive and the search only shows results that start with the entered search term.
    * The Field should be populated with **Field** followed by the custom field name. For example, populate **Field** with `field.description__c` for a custom field with a field name of `description__c`.
5. Populate the properties under the Registrations Settings and/or Submissions Settings sections to achieve the behavior detailed below.
6. Click **Save**.


## Submissions Settings {#submissions-settings}

These properties only apply to RIM Field Mappings that are under RIM Object Configurations for _Application_ relationships, _Regulatory Objective_ relationships, and _Submission_ relationships. If configured on other RIM Field Mappings, these properties do not apply.
* **Unique Within Application** determines which fields are used by the [Submission Wizard](/en/lr/73649/) and the [Copy Content Plan/Copy Into Content Plan](/en/lr/71665/) and [Compare and Merge Content Plans](/en/lr/45365/#compare-and-merge) actions while looking for unique relationships when the source Submission and target Submission are under the same Application. It is also used to prevent duplicate _Application_ relationships when [managing these relationships](/en/lr/73649/#managing-application-relationships) via the _Enable Application Relationships_ and _Enable Relationship Triggers_ [RIM Settings](/en/lr/53688/#rim-settings). If set to true, the field is included in the group of field values from the source relationship that are used to look for matching relationships on the target relationship.
* **Unique Across Application** determines which fields are used by the Copy Content Plan/Copy Into Content Plan and Compare and Merge Content Plans actions while looking for unique relationships when source Submission and target Submission are under different Applications. When set to _Yes_ (true), the field is included in the group of field values from the source Submission relationship that are used to look for matching relationships on the target Submission relationship.

<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>: As a best practice, the <em>Unique Within Application</em> and <em>Unique Across Application</em> RIM Field Configurations for each relationship’s two parent objects should always be set to <em>Yes</em>. This ensures, for example, an <em>Application Product</em>’s parent <em>Application</em> and <em>Product</em> records are used to look for matching relationships on a target <em>Application</em> or <em>Submission</em> relationship.</p>
    </div>
  </div>
</div>



This property only applies to RIM Field Mappings that are under RIM Object Configurations for Content Plan and Content Plan Item. If configured on other RIM Field Mappings, these properties do not apply.
* **Use in Comparison**  determines which fields are included comparing Content Plans of the same Content Plan Template (used in [Global Content Plan Dispatch](/en/lr/77853/#dispatching-a-global-content-plan)). If set to true, the field is included when comparing and dispatching Content Plans and Content Plan Items from the source Global Content Plan to the target Submission Content Plan.

This property only applies to RIM Field Mappings that are under RIM Object Configurations for _Application_ relationships. If configured on other RIM Field Mappings, these properties will not apply.
* **Editable Application Detail**: With **Enable Application Relationships** and **Enable Relationship Triggers** configured, this property determines whether an _Application_ relationship field can be edited if it is used in a _Regulatory Objective_ or _Submission_ in an excluded lifecycle state. If set to true, the field remains editable and updates to the field at the Application level are cascaded down to _Regulatory Objectives_ and _Submissions_ in non-excluded lifecycle states. The updates are applied to eligible _Regulatory Objectives_ or _Submissions_ when relationships and fields are updated manually or via the Submission Wizard. 

This property does not apply to the _Application Indication_ field on the _Application Clinical Study_ object or the _Application Product_ field on the _Application Inactive Ingredient_ object.

<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>: When <strong>Enable Application Relationships</strong> and <strong>Enable Relationship Triggers</strong> are configured, users updating RIM Object Configurations for any relationship may encounter an incorrect error message that a duplicate relationship cannot be created. This error occurs when the <em>Unique Within Application</em> or <em>Unique Across Application</em> properties are set as No (false) or are blank (null). Users encountering this error message in these circumstances should contact their Vault Admin to correct the underlying configuration issue. We plan to correct the error message and prevent misconfiguration in future Vault releases.</p>
    </div>
  </div>
</div>



## Registrations Settings
These properties only apply to RIM Field Mappings that are under RIM Object Configurations for Registration relationships. If configured on other RIM Field Mappings, these properties do not apply.
* **Editable Registered Detail**  determines whether a field is editable in [Manage Registered Details](/en/lr/60452/). If set to true, the field is editable when updating existing details using Manage Registered Details.
* **Create Display Order**  determines the display order when creating new registered details using [Create Registrations](/en/lr/57203/) or [Manage Registered Details](/en/lr/60452/). This property also applies when creating _Change Items_ in [Create & Manage Event Details](/en/lr/5498722/).
* **Update Display Order** determines the display order when updating existing details using [Manage Registered Details](/en/lr/60452/) or [Local Activity Assessment](/en/lr/9299271/#object-config).