RegulatoryOne Registration & Dossier Management Vaults allow you to create Object Mapping MDL components with Field Mapping subcomponents to automate field population of certain records. 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 also 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 also use MDL to create Object Mappings with Field Mappings. See About RegulatoryOne Component Types for more details.
The following actions populate object records based on Object Mappings:
- Generate Registration Data: When linked to a Relational Token, populates mapped fields on Registration Items with values from source Registration Items based on token resolution.
- Generate Requirements: When linked to a Relational Token, populates mapped fields on generated Registration Item Requirements, EDLs, and EDL Items with values from source records based on token resolution.
- Populate Registration Record: Populates mapped fields on Registrations with values from source Registration Items.
- Split Registration Items: When linked to a Relational Token, populates mapped fields on generated Registration Items with values from the source Registration Item based on token resolution.
You can view, create, and edit Object Mapping and related Field Mappings on the Object Mappings tab. You must activate the tab and ensure that the appropriate Admin users have permission to view the tab as well as the Object Mapping Details and Object Mapping List pages.
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. Vault automatically populates the fields in target object records with the same value as the source object record when users run supported actions. 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.
You can map multiple fields between two (2) objects but can only map fields of the same data type. 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. Field Mappings do not support lookup or formula fields.
To create an Object Mapping with Field Mappings:
- Navigate to the Object Mappings tab.
- Click Create.
- Enter a unique Object Mapping Label.
- Enter a Source Object name such as
product__v. If you plan to use this Object Mapping with the Populate Registration Record action, you must enter
- Enter a Target Object name such as
request__v. If you plan to use this Object Mapping with the Populate Registration Record action, you must enter
- Click Save to reveal the Field Mappings section.
- In the Field Mappings section, click Add.
- In the New Field Mapping dialog, select a Source Field such as ID and a Target Field such as product__v. The Target Field must be an editable field on the Target Object. The Source Field and Target Field must both be active. If either field is inactive, the job will fail when users attempt to generate new records. There are additional considerations depending on how you plan to use this Object Mapping:
- To use this Object Mapping with the Populate Registration Record action to populate Registrations, the source and target fields types must be the same. Do not map the Name field if it is a system-managed field on the Registration object.
- To use this Object Mapping in a Split Rule to split Registration Items, we recommend as a best practice that you map a unique field from the Source Object, such as the ID field, to a corresponding field on the Registration Item (
request__v) Target Object. This will help users understand which specific records Vault creates when they trigger the Split Registration Items action.
- Click Confirm.
- Optional: Click Add to add additional Field Mappings to this Object Mapping.
- Click Save.
Names of Object Mappings and Field Mappings are automatically generated by Vault and cannot be changed.
Note: If any of the Field Mappings of an Object Mapping linked to a Relational Token referenced in a Split Rule are the same as any of the Fields to Inherit on the Split Rule, Vault will display an error to users when they select that rule on a Registration Item record and trigger the Split Registration Items action.
You can link Object Mappings to Relational Tokens so that when users trigger certain supported actions, Vault automatically populates mapped fields on target records with values from source records based on token resolution in supported object records and MDL components. See Defining Relational Tokens for details about how to link an Object Mapping to a Relational Token.
The following actions support Relational Tokens linked to Object Mappings and populates fields based on token resolution:
To use an Object Mapping for a Relational Token in object records, you must specify a Source Object that matches the Object in the Relational Token. Relational Tokens support Object Mappings for the following Target Objects:
- Registration Item (
- Registration Item Requirement (
- EDL (
- EDL Item (
To link an Object Mapping to a Relational Token to use in a Registration Attribute component, you must specify a Source Object that matches the Object in the Relational Token and the Target Object value must be
request__v. See Configuring Local Impact Assessments for more details.
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:
|Security Profile||Admin: Configuration: All Configuration||Ability to create and modify Object Mappings and Field Mappings.|
|Security Profile||Pages: All Pages: Object Mapping List: View||Ability to view the Object Mapping List page on the Object Mappings tab.|
|Security Profile||Pages: All Pages: Object Mapping Details: View||Ability to view the Object Mapping Details page on the Object Mappings tab.|
|Security Profile||Tabs: All Tabs: Object Mapping: View||Ability to view the Object Mappings tab.|