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.
    1. 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.
    1. 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.
    1. The Name should be populated with the custom field name.
    2. The Object should be populated with the same object that the parent RIM Object Configuration record is created for.
    3. 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

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 Submission Wizard and Copy Content Plan/Copy Into Content Plan while looking for unique relationships when the source Submission and target Submission are under the same Application. It is also used when RIM Settings Enable Application relationships and Enable Relationship Triggers are enabled to prevent duplicate Application relationships from being created. 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 Copy Content Plan/Copy Into Content Plan while looking for unique relationships when source Submission and target Submission are under different Applications. If set to 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.

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). 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.

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.