# Conducting Local Impact Assessments (Registration & Dossier Management)

[ Registration & Dossier Management](/en/lr/71498/) provides you with the ability to assess if a registration item's objective can be accomplished by amending an existing registration or if a new registration is required for a location's specific regulations. You can search existing active registrations and registration objectives based on Admin-defined filters. Vault identifies which of the matching records you can use to register the product or if you must amend any of the matches before you can use them to register the product. You can then select the most appropriate registration and start the appropriate registration for a country's specific regulations.

Depending on your [Admin's configuration](/en/lr/76906/), object, field, and section labels may appear differently than the labels mentioned in this article.

## Creating a Registration Item {#creating}

Before conducting a Local Impact Assessment, you must first create the new _Registration Item_ on which you will conduct the assessment. To create a _Registration Item_:

1. Navigate to the appropriate _Registration Item_.
2. Click **Create**.
3. Enter a **Name**.
4. Select a **Location** to filter the appropriate _Regulated Categories_.
5. Select a **Regulated Category** to determine which Admin-configured criteria to use to match existing _Registrations_.
6. Optional: Enter values for non-required fields as needed. After creating the record, you can automatically populate certain fields using the [_Generate Registration Data_ action][3].
7. Click **Save**.

## Conducting a Local Impact Assessment {#lia}

When configured by your Admin, your Registration & Dossier Management Vault includes several actions to support Local Impact Assessments:

* [**Generate Registration Data**][3]: Populates certain fields on a _Registration Item_ or all _Registration Items_ associated with an _Event_.
* [**Local Impact Assessment**][4]: Identifies all existing _Registrations_ and _Registration Objectives_ that you can use to register the _Registration Item_, including _Registrations_ that you must amend before submitting.
* [**Create Registration and Objective**][5]: Creates a new or relates an existing _Registration_ and _Registration Objective_ for a _Registration Item_.
* [**Create Registrations and Objectives**][5]: Creates new or relates existing _Registrations_ and _Registration Objectives_ for all _Registration Items_ associated with an _Event_.

Depending on your Admin's configuration, options may only appear in the **All Actions** menu when the _Registration Item_ or _Event_ is in a specific lifecycle state. Additionally, your Vault may run actions automatically when a record enters a specific state, either instead of or in addition to making them available in the **All Actions** menu. Ensure the applicable _Regulated Category_ field is populated. Then, change the state of the record to trigger the appropriate entry action.

### Generating Registration Data {#generating-registration-data}

When configured by your Admin, you can automatically populate certain fields on a _Registration Item_ or all _Registration Items_ associated with an _Event_ with field values of existing _Registration Items_ in the same _Regulated Category_ based on Admin-defined criteria. Vault only populates blank fields. If any Admin-specified field is already populated, Vault preserves the existing value.

To generate registration data:

1. Navigate to the appropriate _Registration Item_ or _Event_.
2. From the **All Actions** menu, select **Generate Registration Data**.
3. When notified, review the populated _Registration Item_ fields.

<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>: Depending on your Admin’s configuration, Vault may ignore certain matching <em>Registration Items</em> when running this action on an <em>Event</em>.</p>
    </div>
  </div>
</div>



### Conducting a Local Impact Assessment {#local-impact-assessment}

The _Local Impact Assessment_ action identifies any existing registrations you can use for the _Registration Item_ based on Admin-defined criteria, including any registrations that require an amendment. Vault identifies potential matches in the _Matching Registrations_ and _Matching Registration Objective_ fields and indicates the appropriate _Regulatory Process Type_ based on the matches (_New_, _No Action Required_, or _Amendment_). Then, you can review the matches and select the appropriate registrations for the _Registration Item_.

To identify potential matches, navigate to the appropriate _Registration Item_ and select **Local Impact Assessment** from the **All Actions** menu. When the action completes, Vault populates, updates, or clears the _Matching Registration_, _Matching Registration Objective_, and _Regulatory Process Type_ fields based on the number of matches:

* If zero _Registrations_ match, the _Matching Registrations_ and _Matching Registration Objectives_ fields remain blank. Vault populates the _Regulatory Process Type_ field with _New_ to indicate that a new registration is required.
* If one _Registration_ matches, Vault populates the applicable _Matching Registrations_ and _Matching Registration Objective_ fields with the matching records and populates the _Regulatory Process Type_ field with the applicable value.
* If multiple _Registrations_ match, Vault populates the _Matching Registrations_ field with _Matching Registrations Found_. The _Regulatory Process Type_ field remains blank.

If multiple _Registrations_ match or if you'd like to override the assessment result and select a specific _Registration_ for the _Registration Item_, you must [select a _Registration_][9].

<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>: Depending on your Admin’s configuration, Vault may ignore matching <em>Registration Objectives</em> in certain lifecycle states and records with parent <em>Registrations</em> in certain lifecycle states.</p>
    </div>
  </div>
</div>



#### Selecting a Registration {#select-registration}

To select a _Registration_, click on the binoculars (<img class="inline" src="https://platform.veevavault.help/assets/images/cpc-icon-binoculars.png" alt="Binoculars Icon" style="" />) icon next to the **Matching Registrations** field to open the _Search Registration_ dialog. In the dialog, you can review the matched records for the _Registration Item_, select an unmatched _Registration_, or create a new _Registration_. Details appear in the dialog's footer describing how your selection determines the _Regulatory Process Type_. After saving your selection, Vault populates or updates the _Regulatory Process Type_ and _Matching Registrations_ or _Matching Registration Objective_ fields on the _Registration Item_ based on your selection.

Complete one of the following options to select a _Registration_:

* Select a matched _Registration_ to amend:
  1. Review the list of matched records. An alert (<img class="inline" src="https://platform.veevavault.help/assets/images/cp-icon-orange-warning.png	" alt="Alert Icon" style="" />) icon appears next to unmatched fields on partially matched records.
  2. Select the appropriate record.
  3. Click **Save** to select the record for the _Registration Item_.
* Create a new _Registration_:
  1. If applicable, click the clear selection (<i class="far fa-minus-circle"></i>) icon in the grid header to clear any selected record.
  2. Click **Save**. When you [create _Registrations_ and _Objectives_][5], Vault generates the new record for the _Registration Item_.
* Select an unmatched _Registration_ to amend:
  1. Click the **Add** button to open the _Search: Registration_ dialog.
  2. Optional: Use the search bar or **Filters** to help narrow the search results. Depending on your Admin's configuration, some filters may appear by default.
  3. Select the appropriate record.
  4. Click **Close** to apply your selection and close the _Search: Registration_ dialog.
  5. In the _Search Registration_ dialog, click **Save** to select the record for the _Registration Item_. If you selected a _Registration_ with unmatched attributes, those unmatched values display in red text below the record's name in the _Search Registration_ dialog. 

<a href="https://platform.veevavault.help/assets/images/cp-rdm-serachreg.png" data-lightbox="cp-rdm-serachreg.png" data-title="" data-alt="Search Registration dialog">
  <img class="docimage" src="https://platform.veevavault.help/assets/images/cp-rdm-serachreg.png" alt="Search Registration dialog" style="max-width: 75%;"  />
</a>

### Creating Registrations & Objectives {#create-registrations}

You can create or relate the appropriate _Registration_ and _Registration Objective_ to a _Registration Item_ or to all _Registration Items_ associated with an _Event_. The _Create Registration and Objective_ and _Create Registrations and Objectives_ actions either relate a _Registration Item_ to the existing matching records you select, or create a new _Registration_. 

Depending on your Admin's configuration, you may be able to run the following actions:

* Run the _Create Registration and Objective_ action on a _Registration Item_ to generate data for that record.
* Run the _Create Registrations and Objectives_ action on an _Event_ to generate data for all _Registration Items_ associated to that record. When you run this action, Vault populates the _Event_ field on the applicable _Registration Objective_ with the record on which the action ran.

If the _Regulatory Process Type_ is _New_, you must populate the _Regulated Category_ field before running the action. If configured by your Admin, Vault will first search for an active _Registration Item_ with the same _Regulated Category_ and Admin-defined attribute mappings and, when applicable, assign the same _Registration Objective_. If multiple _Registration Items_ exist with the same attributes, Vault assigns the _Registration Objective_ with the highest _Objective Number_. If multiple records have the same _Objective Number_, Vault assigns the most recently created record. If there are no existing _Registration Items_ with the same attributes, Vault creates and relates the appropriate records based on the values in the _Matching Registration_ and _Matching Registration Objective_ fields:

<table>
  <tr>
    <th><strong>If Matching Registration is…</strong></th>
    <th><strong>And Matching Registration Objective is…</strong></th>
    <th><strong>Outcome</strong></th>
  </tr>
  <tr>
    <td>Blank</td>
    <td>Blank</td>
    <td>Vault creates and relates a new parent <em>Registration</em> to a new child <em>Registration Objective</em> and relates the <em>Registration Item</em> to the child <em>Registration</em>.</td>
  </tr>
  <tr>
    <td>[<em>Registration</em>]</td>
    <td>Blank</td>
    <td>Vault creates a new child <em>Registration Objective</em> and relates it to the matching parent <em>Registration</em> and the <em>Registration Item</em>. The existing <em>Registration</em> is up-versioned.</td>
  </tr>
  <tr>
    <td>[<em>Registration</em>]</td>
    <td>[<em>Registration Objective</em>]</td>
    <td>Vault relates the <em>Registration Item</em> to the matching parent <em>Registration</em> and incomplete child <em>Registration Objective</em>. The existing <em>Registrations</em> are up-versioned.</td>
  </tr>
  <tr>
    <td><em>Matching Registrations Found</em></td>
    <td>Any</td>
    <td>No records are created or related. You must first select an applicable <em>Registration</em>.</td>
  </tr>
</table>

If you did not previously run the _Local Impact Assessment_ job to populate the _Matching Registrations_ and _Matching Registration Objective_ fields for the _Registration Item_, Vault creates and relates new _Registrations_ when you [create _Registrations_ and _Objectives_][5].

<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>: Depending on your Admin’s configuration, Vault may ignore certain matching <em>Registrations</em> and <em>Registration Objectives</em> and generated records may be of specific object types.</p>
    </div>
  </div>
</div>



## Notifications {#notifications}

When Vault finishes each of the actions, you'll receive an email and a Vault notification. The notification lets you know if the action was successful or if there were any errors.

## Limitations {#limitations}

The following limitations apply to Local Impact Assessments:

* Vault supports up to 20 matching _Registrations_. If more than 20 records are found, the _Local Impact Assessment_ job fails.
* If a matching _Registration_ is related to just one _Registration Item_ that is also inactive, Vault displays up to 19 matching _Registrations_ in the _Search Registration_ dialog.
* The _Create Registration and Objective_ and _Create Registrations and Objectives_ actions check the first 1,000 _Registration Items_ (in ascending order) when searching for records with the same attributes.
* Vault supports up to 1,000 _Registration Objectives_ for a given _Registration_.

[1]: #creating
[2]: #lia
[3]: #generating-registration-data
[4]: #local-impact-assessment
[5]: #create-registrations
[7]: #notifications
[8]: #limitations
[9]: #select-registration
