Defining Registration Attributes (Registration & Dossier Management)

Compliance Management allows you to create Registration Attribute components to define Registration Item field attributes and map them to object fields. You must define relevant Registration Attributes in order for the following actions to run successfully:

  • Local Impact Assessment: Identifies Registration and Registration Objective matches based on the Regulated Category Attribute Impacts you link to each component.
  • Generate Registration Data: Populates specified fields on a source Registration Item record based on the Object Mapping linked to the Relational Token you specify for a component.
  • Run Global Impact Assessment: Identifies Registration Items potentially impacted by a global operational change based on the pre-defined Global Operational Change fields you specify for each component.

You can also use MDL to create Registration Attributes. See About RegulatoryOne Component Types for more details.

Creating Object Mappings & Relational Tokens

If you are creating a Registration Attribute for the Generate Registration Data action, it must reference a Relational Token linked to an Object Mapping to specify how Vault populates fields based on token resolution. Before creating the Registration Attribute, ensure you have created the appropriate Object Mapping and Relational Token for the Registration Attribute to reference.

Creating Registration Attributes

To create a Registration Attribute:

  1. Navigate to Admin > Configuration > Registration Attribute.
  2. On the All Registration Attribute 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 attribute does not support spaces.
  5. Specify if the component is Active. If you select No, Vault ignores the inactive component when supported actions run.
  6. For Object, select Registration Item.
  7. For Field, enter the name of the Registration Item field used as an attribute, such as Field.made_in__c. This attribute supports only certain field types. If you enter a lookup field, you must leave the Relational Token attribute blank.
  8. Optional: Select an active Relational Token. If you populate this attribute, ensure that the Request Object Mapping attribute on the Relational Token references a valid Object Mapping. The Object Mapping determines how Vault populates the specified field on a Registration Item based on token resolution. Vault applies the Relational Token depending on which supported action a user runs:
    • Generate Requirements: This attribute is ignored.
    • Generate Registration Data: Determines which Object Mapping is utilized to populate the specified field on a Registration Item based on token resolution.
    • Run Global Impact Assessment: Mapped fields are blank on generated Registration Items.
  9. If you are configuring Global Change Impact Assessments, specify the following attributes. Otherwise, leave these blank:
    • Global Operational Change Field: Enter the name of an active custom Global Operational Change object field, such as Field.made_in__c. This attribute supports only certain field types and must be the same type as the Registration Item field you entered in the Field attribute.
    • Global Operational Change Object: Select Global Operational Change.
  10. Click Save.

Supported Field Types

Vault supports only certain types of object fields for Registration Attributes component attributes.

Field Attribute

Vault supports the following types of object fields for the Field attribute:

  • Date
  • Number
  • Object (excluding references to the Document and User objects)
  • Picklist (single value)
  • Text (including long text and rich text)
  • Lookup (so long as the type is a supported type listed above)

Global Operational Change Field Attribute

Vault supports the following types of object fields for the Global Operational Change Field attribute:

  • Number
  • Object (excluding references to parent objects and the User object)
  • Picklist (single value)
  • Text (including long text and rich text)

If you include a Global Operational Change Field attribute in a component, it must be the same type as the Field attribute you added to the component.

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 Registration Attributes.
Security Profile Application: Vault Actions: API: Metadata API Ability to access the All Registration Attributes page from the Application Configurations section of the Configurations page.
Security Profile Objects: All Objects: Object Permissions: Create, Edit Ability to create and modify Registration Attributes.
Security Profile Pages: All Pages: Relational Token Details: View Ability to view the Details page for individual Registration Attributes.
Security Profile Pages: All Pages: Relational Token List: View Ability to view the list of Relational Tokens on the All Registration Attributes page.