# About Activity Dependencies (RIM)

Your organization may define country-to-country dependencies to support planned changes in your Vault. Country dependencies allow Vault to create _Activity Dependency_ records automatically each time an _Activity_ record is created. This ensures that users working at the country level are aware of dependencies for each country.



<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. An Admin must <a href="/en/lr/71816/">configure country dependencies</a> before your Vault can create <em>Activity Dependency</em> records.</p>
    </div>
  </div>
</div>



## How Vault Creates Activity Dependencies

When your Admin has configured country dependencies, Vault creates _Activity Dependency_ records automatically each time an _Activity_ record is created. The _Activity Dependency_ records that Vault creates depend on the _Event_ type, the _Product_ type, and other fields determined by your Admin. When an _Activity_ record for a reference country is submitted or reaches approval, Vault notifies users that they can proceed with implementing the required changes in their market.

For example, if you need to submit a manufacturing change to Australia, Vault may create an _Activity Dependency_ record that informs you that you can only submit this change after the change is approved in the EU.

## Viewing Activity Dependencies

To see an _Activity_ record's related dependencies, navigate to the object record detail page and expand the _Activity Dependency_ related object section. Click a record's name to open it. The following fields include details about each dependency:

  * **Reference Application**: The reference _Activity_ record’s _Related Application_.
  * **Reference Event**: The parent _Event_ record.
  * **Reference Activity**: The reference _Activity_ record.
  * **Reference Country**: The lead or parent country for this dependency.
  * **Dependency Rule**: Whether this dependency is optional or mandatory.
  * **Dependency Comments**: Additional information about the dependency's rules.
  * **Dependency Action**: Whether the dependent country must wait to take action until the _Reference Country_ submits changes or gets approval.
  * **Dependent Application**: The dependent activity's _Related Application_.
  * **Dependent Event**: The event related to the dependent activity.
  * **Dependent Activity**: The dependent activity.
  * **Dependent Country**: The country in which the dependent activity should occur.