Registration & Dossier Management allows users to automatically populate certain fields on Registrations, including registration objective types of Registrations, with values propagated from related Registration Items based on pre-defined Object Mappings. This allows users to quickly update Registrations records with the appropriate data based on details they’ve already defined on relevant Registration Items.
Registration & Dossier Management uses the following core objects to support field propagation from Registration Items to Registrations:
- Registration (
registration__v): This object represents proof that validates clearance in a location and can be used over time using versions, stored as parent-child relationships. A registration objective type of Registration represents a snapshot of a registration and the related Registration Items at a specific point in time. A Registration can be the parent of multiple child registration objective types of Registrations.
- Registration Item (
request__v): This object represents request to identify or scope out what needs to be done to market or sell a product in a jurisdiction. A Registration Item can be directly related to a single Registration.
Note: If you adopted Registration & Dossier Management prior to 21R2, the Registration Item Requirement object may be labeled Request Requirement in your Vault.
Configuring your Vault to populate Registration fields involves the following steps:
- Create an Object Mapping with Field Mappings to map fields between the Registration Item and Registration objects
- Configure object page layouts and object types
- Configure the Populate Registration Record action
- Configure the Registration object lifecycle
- Configure user permissions
You must create an Object Mapping that defines the Registration Item as the source object and the Registration as the target object. Then, add Field Mappings to map fields from the Registration Item source object to the Registration target object to specify which fields to propagate from source Registration Items to target Registrations. See Defining Object Mappings & Field Mappings for more details.
Note: If a mapped field is not assigned to a Registration Item object type, Vault considers that field blank when propagating field values from Registration Items of that type to Registrations.
If you’ve configured object types on the Registration object, you must add the Propagate Fields Job Status field to the Registration object page layout. This field automatically updates to reflect the job’s status when users trigger the Populate Registration Record action.
After creating an Object Mapping with appropriate Field Mappings, you must configure the Populate Registration Record action on the Registration object and all relevant object types. When creating the action, select the Object Mapping you created in the Object Mapping field to specify how Vault will populate fields on Registration records.
Depending on your business needs, you can:
- Add this action as an entry action on any Registration lifecycle state.
- Add this action as a user action on any Registration lifecycle state.
When users trigger the Populate Registration Record action on a Registration, Vault identifies all active Registration Items related to that record. For parent Registrations, this includes Registration Items related to all active registration objective types of Registrations that are children of that Registration parent record. Vault then populates and updates fields on the Registration with values propagated from the related Registration Items based on the Field Mappings of the Object Mapping you linked to the action:
|If the field value on all active related source Registration Items is…||The mapped field on the target Registration is…|
|The same||Populated with the same value on the related Registration Items|
|Not the same||Cleared|
Ensure that there is an object lifecycle on the Registration object. You can add custom lifecycle states to suit your organization’s needs.
You must ensure users have the appropriate read and create permissions to access the appropriate objects and object fields in addition to the permissions outlined below:
- For the Registration object: Edit permission, including Edit permission on the Propagate Fields Job Status field.
- For the Registration Item object: Read permission.
- Read permission on all mapped fields.
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: Object Lifecycles: Create, Edit||Ability to create and modify object lifecycles.|
|Security Profile||Admin: Configuration: Objects: Create, Edit||Ability to create and modify Vault objects.|
|Security Profile||Admin: Permission Sets: Read, Create, Edit||Ability to make changes to permission sets for users.|