# Pausing Vault Java SDK Record Triggers in RIM Registrations

RIM Registrations Vaults include a setting which can temporarily prevent Vault from automatically creating or updating certain object records, allowing for smoother migration of data with <a href="/en/gr/26597/">Vault Loader</a> or <a class="external-link " href="https://developer.veevavault.com/" target="_blank" rel="noopener">Vault API<i class="fa fa-external-link" aria-hidden="true"></i></a>. For example, when this checkbox is cleared, Vault does not automatically create _Country Decision Detail_ records when users load or migrate _Regulatory Objective_ records.

<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>: This feature is only available on RIM Registrations Vaults.</p>
    </div>
  </div>
</div>



## How to Pause RIM Registrations Vault Java SDK Triggers

The RIM Registrations Vault Java SDK record triggers are automatically enabled in your Vault. To pause these and prevent automatic record creation and updates during Vault migrations, navigate to **Admin > Settings > Application Settings** and clear the **Execute Registrations SDK triggers** checkbox. We do not recommend turning this setting off during normal business operations.

## About RIM Registrations Record Triggers

RIM Registrations Vaults use several <a href="/en/gr/45776/#record_triggers">Vault Java SDK record triggers</a> to create or update certain records automatically:

  * **Activity Dependency records**: When users create _Activity_ records, Vault creates one (1) _Activity Dependency_ record for each _Country Dependency_ record for each country associated to the _Application_ that is referenced by the _Regulatory Objective_ record.
  * **Country Decision Details records**: When users create _Regulatory Objective_ records, Vault creates one (1) _Country Decision Detail_ record for each _Country_ associated to the _Application_ that is referenced by the _Regulatory Objective_ record.
  * **Country Decision Detail Count field**: The _Country Decision Detail Count_ field on the parent _Regulatory Objective_ record updates automatically each time Vault creates or users delete related _Country Decision Detail_ records. This allows Vault to capture the current number of records.
  * **Administered Product records**: When users create _Administered Product_ object records of object type _Administered as Manufactured_, Vault copies over active and inactive ingredient data from related _Product Variant_ records to new _Administered Product Active Substance_ and _Administered Product Inactive Ingredient_ records.
  * **Most Recent Submitted field**: Vault uses the _Most Recent Submitted_ field on _Product Data Submission_ records to track the most up-to-date submitted product report tree. When the _Product Data Submission_ record enters the _Submitted_ state, Vault sets the _Most Recent Submitted_ field to _Yes_, then sets the field in all previous _Product Data Submission_ records to _No_.
  * **Application Regulatory Objective records**: When users create a new _Regulatory Objective_ record with the _Application_ field populated, Vault creates one (1) related _Application Regulatory Objective_ record for each unique combination of _Application_ and _Regulatory Objective_. When users update the _Application_ field on an existing _Regulatory Objective_ record, Vault updates the value on the _Application Regulatory Objective_ record.

### Quality-RIM Connection Triggers

Registrations SDK triggers are also used within the <a href="/en/gr/57086/">Quality-RIM Connection</a> as follows:

  * **Manufacturing Events**: When a _Manufacturing Event_ is created in RIM, Vault sends a Spark message back to Quality with the details included in the _QMS RIM: Create RIM Event_ (`qms_rim_create_rim_event__v`) integration rule. Vault triggers the next integration point when the record reaches the object lifecycle state configured to use the _Impact Assessment Complete_ state type. This behavior does not apply when the _Manufacturing Event_ is updated manually.
  * **Activities**: Vault triggers a Spark message when an _Activity_ reaches the object lifecycle states configured to use the _Activity_ lifecycle state types associated with the connection. This behavior does not apply when the _Activity_ record is updated manually.