# Defining Registration Attributes (Registration & Dossier Management)

<a href="/en/gr/71498/">Registration & Dossier Management</a> allows you to create Registration Attribute <a class="external-link " href="https://developer.veevavault.com/mdl/#vault-components" target="_blank" rel="noopener">components<i class="fa fa-external-link" aria-hidden="true"></i></a> 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: 

* <a href="/en/gr/76906/#local-impact-assessment">**Local Impact Assessment**</a>: Identifies _Registration_ and _Registration Objective_ matches based on the _Regulated Category Attribute Impacts_ you link to each component. 
* <a href="/en/gr/76906/#generate-registration-data">**Generate Registration Data**</a>: Populates specified fields on _Registration Items_ based on the [Object Mapping][4] linked to the Relational Token you specify for a component.
* <a href="/en/gr/512728/#gia-action">**Run Global Impact Assessment**</a>: 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 <a class="external-link " href="https://developer.veevavault.com/mdl/#mdl-overview" target="_blank" rel="noopener">MDL<i class="fa fa-external-link" aria-hidden="true"></i></a> to create Registration Attributes. See <a href="/en/gr/494967/">About RegulatoryOne Component Types</a> for more details.

## Creating Object Mappings & Relational Tokens {#object-mapping-token}

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 <a href="/en/gr/74401/">Object Mapping</a> and <a href="/en/gr/71507/">Relational Token</a> for the Registration Attribute to reference.

## Creating Registration Attributes {#create}

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][2]. 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 <a href="/en/gr/512728/">Global Change Impact Assessments</a>, 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][3] 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**.

<div class="note-border alert-info">
  <div class="alert alert-info" role="alert">
    <div><i class="far fa-info-circle"></i></div>
    <div class="alert-text">
      <p><strong>Note</strong>: You can create only one (1) Registration Attribute component for each <em>Registration Item</em> field.</p>
    </div>
  </div>
</div>



### Supported Field Types {#field-types}

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

#### Field Attribute {#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 {#goc-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.

## Related Permissions {#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 <a href="/en/gr/22824/">permissions</a>:

<table>
  <tr>
    <th><strong>Type</strong></th>
    <th><strong>Permission</strong></th>
    <th><strong>Controls</strong></th>
  </tr>
  <tr>
    <td>Security Profile</td>
    <td>Admin: Configuration: Configuration: All Configuration</td>
    <td>Ability to create and modify Registration Attributes.</td>
  </tr>
  <tr>
    <td>Security Profile</td>
    <td>Application: Vault Actions: API: Metadata API</td>
    <td>Ability to access the <em>All Registration Attributes</em> page from the <em>Application Configurations</em> section of the <em>Configurations</em> page.</td>
  </tr>
  <tr>
    <td>Security Profile</td>
    <td>Objects: All Objects: Object Permissions: Create, Edit</td>
    <td>Ability to create and modify Registration Attributes.</td>
  </tr>
  <tr>
    <td>Security Profile</td>
    <td>Pages: All Pages: Relational Token Details: View</td>
    <td>Ability to view the <em>Details</em> page for individual Registration Attributes.</td>
  </tr>
  <tr>
    <td>Security Profile</td>
    <td>Pages: All Pages: Relational Token List: View</td>
    <td>Ability to view the list of Relational Tokens on the <em>All Registration Attributes</em> page.</td>
  </tr>
</table>


[1]: #create
[2]: #field-attribute
[3]: #goc-attribute
[4]: #object-mapping-token