Defining Object Mappings & Field Mappings (Registration & Dossier Management)

Registration & Dossier Management allows you to create Object Mapping MDL components with Field Mapping subcomponents to automate field population of certain records and filter certain search results. You can map field values between a source and target object so that records created or populated from supported actions contain the same field values as related source records. You can link an Object Mapping to a Relational Token so that Vault automatically populates mapped fields based on token resolution when a supported action runs. For example, you can map the ID field on the Claim object to an object reference field on the EDL Item object, then link the mapping to a Relational Token. When users run the Generate Requirements action on a Registration Item record, Vault automatically populates the object reference field on all generated EDL Item records with the same values in the Claim source object based on token resolution.

You can map field values between the Registration Item source object to the Registration target object to include default filters in the Search Registration dialog when users select a Registration when conducting Local Impact Assessments.

You can also use MDL to create Object Mappings with Field Mappings. See About RegulatoryOne Component Types for more details.

About Supported Actions

The following actions populate object records or filter search results based on Object Mappings:

• Generate Registration Data: Populates mapped fields on Registration Items with values from source Registration Items based on how the linked Relational Token resolves.
• Local Impact Assessment: Filters Registration search results based on mapped Registration Item values.
• Create Registration and Objective: Filters Registration search results based on mapped Registration Item values.
• Generate Requirements: Populates mapped fields on generated Requirements, EDLs, and EDL Items with values from source records based on the following factors:
  • Any Object Mappings you link to the action to define default field values.
  • How the linked Relational Token resolves.
• Update Requirements: Populates mapped fields on generated Requirements, EDLs, and EDL Items with values from source records based on the following factors:
  • Any Object Mappings you link to the action to define default field values.
  • How the linked Relational Token resolves.
• Populate Registration Record: Populates mapped fields on Registrations with values from source Registration Items.
• Split Registration Items: Populates mapped fields on generated Registration Items with values from the source Registration Item based on how the linked Relational Token resolves.

Default Field Values for the Generate Requirements & Update Requirements Actions

When configuring the Generate Requirements and Update Requirements actions, you can link the action to Object Mappings to automatically populate mapped fields on generated records with default field values on the source Requirement Library. For example, you can configure default field values to support automatic document matching.

Creating Object Mappings & Field Mappings

You must first create an Object Mapping that identifies the source and target objects. Then you can create Field Mappings for that Object Mapping that map specific fields on those objects. When users run supported actions, Vault automatically populates the fields in target object records with the same value as the source object record or to include default filters in the Search Registration dialog for Local Impact Assessments. Some supported actions require you to link the Object Mapping to a Relational Token in order for Vault to automatically populate fields based on token resolution.

All objects and fields referenced in Object Mappings and Field Mappings must be active. When entering specific object field names, you must enter the values in “Field.[field_name__v]” format. For example, Field.name__v.

You can map multiple fields between two (2) objects but can only map fields of the same data type with the same attributes. For example, you can map a text type to a text type or a number type to a number type but cannot map a text type to a number type. Similarly, you cannot map two (2) number fields with different configured attributes, such as different Minimum values. Field Mappings do not support icon or link types of formula fields, nor object fields that reference fields on the Document object. If you link a supported action to an Object Mapping with unsupported fields, the action will fail when run by a user.

To create an Object Mapping with Field Mappings:

1. Navigate to Admin > Configuration > Object Mapping.
2. On the All Object Mappings page, click Create.
3. Enter a unique Name. Vault automatically adds the __c suffix to the Name you enter.
4. Enter a unique Label. This field does not support spaces.
5. Select a Source Object. To use this Object Mapping to populate Registration fields or filter assessment results, you must select the Registration Item object.
6. Select a Target Object. To use this Object Mapping to populate Registration fields or filter assessment results, you must select the Registration object. To link this Object Mapping to a Relational Token, you must select the applicable supported object.
7. Specify if the Object Mapping is Active. If you select No, Vault ignores the inactive Object Mapping when supported actions run.
8. Click Save to create the Object Mapping and reveal the Field Mappings section.
9. Expand the Field Mapping section and click Create.
10. In the Create Field Mapping dialog, enter a unique Name.
11. Select the same Source Object you selected for the Object Mapping.
12. Select the same Target Object you selected for the Object Mapping.
13. Enter the name of a Source Field.
14. Enter the name of an active Target Field of the same type and with the same configured field attributes as the Source Field.
    • If you entered Field.ID as the Source Field, you must enter a field in the Target Object that references the Source Object.
    • If you’re mapping document reference fields, ensure the Document Version Reference on the source and target fields is Latest Steady State version.
15. Specify if the Field Mapping is Active. If you select No, Vault ignores the inactive Field Mapping when supported actions run.
16. Click Save.
17. Optional: Click Create to add additional Field Mappings to this Object Mapping.

Editing Object Mappings & Field Mappings

To edit an Object Mapping or Field Mapping:

1. Navigate to the relevant Object Mapping.
2. Optional: Modify the Object Mapping:
   1. From the All Actions menu, select Edit.
   2. Make the applicable changes.
   3. Click Save.
3. Optional: Modify a Field Mapping:
   1. Expand the Field Mappings section.
   2. Click on the name of the relevant Field Mapping.
   3. From the All Actions menu, select Edit.
   4. Make the applicable changes.
   5. Click Save.

Deleting Object Mappings & Field Mappings

To delete an Object Mapping or Field Mapping, navigate to the applicable Object Mapping or Field Mapping and select Delete from the All Actions menu. Then, click Continue to proceed with the deletion.

Linking Object Mappings to Relational Tokens

You can link Object Mappings to Relational Tokens so that when users run actions that support Relational Tokens, Vault automatically populates mapped fields on target records with values from source records based on how the token resolves in supported object records and MDL components. See Defining Relational Tokens for more details about how to link an Object Mapping to a Relational Token.

Supported Actions

The following actions support Relational Tokens linked to Object Mappings and populate mapped fields based on token resolution:

• Generate Registration Data
• Generate Requirements
• Update Requirements
• Split Registration Items

Supported Objects

To link an Object Mapping to a Relational Token to populate mapped fields based on token resolution, you must specify a Source Object that matches the linked Relational Token’s Object. Relational Tokens support Object Mappings for the following Target Objects:

1. Registration Item
2. Requirement
3. EDL
4. EDL Item

Supported Component Types

To link an Object Mapping to a Relational Token to use in a Registration Attribute MDL component to support generating registration data for Local Impact Assessments, the Source Object must match the token’s Object and the Target Object must be Registration Item. See Defining Registration Attributes for more details.

Related Permissions

You can complete all the steps in this article with the standard System Administrator or Vault Owner security profile. If your Vault uses custom security profiles, your profile must grant the following permissions:

Type	Permission	Controls
Security Profile	Admin: Configuration: Configuration: All Configuration	Ability to create and modify Object Mappings and Field Mappings.
Security Profile	Application: Vault Actions: API: Metadata API	Ability to access the All Object Mappings page from the Application Configurations section of the Configurations page.
Security Profile	Objects: All Objects: Object Permissions: Create, Edit	Ability to create and modify Object Mappings and Field Mappings.
Security Profile	Pages: All Pages: Object Mapping Details: View	Ability to view the Details and Fieldmappings for individual Object Mappings.
Security Profile	Pages: All Pages: Object Mapping List: View	Ability to view the list of Object Mappings on the All Object Mappings page.