# Configuring Local Adaptations (Veeva Claims)

[Veeva Claims](/en/lr/54331/) provides users with the ability to [create local adaptations](/en/lr/76204/) of [claims](/en/lr/54344/) in order to review and approve claims for a product in different locations. _Local Adaptation_ records contain all information for an adaptation from a _Claim_ record, including _Statement_ text, adapted for other locations.

## Configuration Overview {#overview}

Configuring your Vault to create _Local Adaptations_ involves the following steps:

<!-- no toc -->
1. [Configure the _Local Adaptation_ object][8]
2. [Configure the _Bulk Create Local Adaptations_ action][1]
3. [Define country-language mappings][2]
4. [Configure the _Populate Statement Translation_ action][3]
5. [Configure _Local Adaptation_ generation from a _Project_][4]
6. Optional: [Configure comments on the _Local Adaptation_ object][7]
7. [Configure the _Local Adaptation_ lifecycle][5]
8. Optional: [Configure substantiation on _Local Adaptations_][10]
9. [Configure user permissions][6]

<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 Vault’s creation date and which features are currently enabled and configured, some of the steps described in this article may be unavailable or already complete in your Vault.</p>
    </div>
  </div>
</div>



## Configuring the Local Adaptation Object {#la}

You can configure your Vault to support users creating new _Local Adaptations_ by copying existing records.

### Object Types & Object Layout {#la-object}

Users often create new _Local Adaptations_ by copying existing records, either by copying a _Local Adaptation_ record or by copying the [_Local Adaptation_ hierarchy][9] when copying a _Claim_. To establish a link to the copied record and maintain traceability to the original _Local Adaptation_, [assign](/en/lr/32857/#assign) the following _Local Adaptation_ fields to all object types and add them to the [object layout](/en/lr/26387/#fields):

* _Source Local Adaptation_
* _Source Local Adaptation Claim_

### Hierarchical Local Adaptation Copy {#la-hierarchical}

You can configure your Vault to allow users to deep copy the hierarchy of child _Local Adaptations_ when copying _Claim_ records. To do this, select the [**Allow hierarchical copy**](/en/lr/28740/#create_relationships) checkbox for the _Claim_ field on the _Local Adaptation_ object.

##  Configuring the Bulk Create Local Adaptations Action {#bulk-create-config}

Local adaptations of a claim allow users to adapt a _Claim_ record for local markets, for example, other countries. When adapting a claim for other locations, certain values can be modified, such as the footnote and marketing channels. You can configure the _Bulk Create Local Adaptations_ action so that users can create multiple local adaptations at the same time.

<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>: If you add custom fields on the <em>Local Adaptation</em> (<code class="language-plaintext highlighter-rouge">local_adaptation__v</code>) object that are required, ensure you specify a default value. Having custom, required fields without a default value on the <em>Local Adaptation</em> object prevents the <em>Bulk Create Local Adaptation</em> action from working. You can add custom, non-required fields without consequence.</p>
    </div>
  </div>
</div>



To configure the _Bulk Create Local Adaptations_ action:

1. Navigate to **Admin > Configuration > Objects > Claim**.
2. On the **Actions** tab, click **Create**.
3. In the _Create Action_ dialog, select **Bulk Create Local Adaptations**, and click **Continue**.
4. Optional: Enter a **Description** of the action.
5. Optional: Select **Available in All Lifecycle States** to make the action available on all lifecycle states.
6. Click **Save**.
7. Define lifecycle behavior:
   * If you selected _Available in All Lifecycle States_, the _Atomic Action Security Defaults_ appears. Update the behavior for each lifecycle state and update as needed.
   * If you did not select _Available in All Lifecycle States_, configure the [user action](/en/lr/59885/#user-actions) on the applicable _Claim_ lifecycle states.
8.  Optional: Review and update the _Marketing Channels_ picklist values by navigating to **Business Admin > Picklists > Marketing Channels**.
9.  Optional: Review and update the list of _Locations_ by navigating to **Business Admin > Objects > Locations**.
10. Configure the _Claims_ [object layout](/en/lr/26387/) to include a _Related Object_ section for the **Local Adaptation** object.
11. Navigate to the _Bulk Create Local Adaptations_ [object layout](/en/lr/26387/) and complete the following:
    1. Add the _Select Locations_ control field with the slider (<img class="inline" src="https://platform.veevavault.help/assets/images/CPC-Icon-Slider.png" alt="Slider Icon" style="" />) icon to the _Details_ section. 
    2. Add the _Select Location_ field to the _Details_ section. 
    3. Configure a [layout rule](/en/lr/51632/) to hide the _Select Location_ field from the layout.

##  Defining Country-Language Mappings {#cl-m-config}

You must create country-language mappings before you can configure the _Populate Statement Translations_ action. See [Defining Country Language Mappings](/en/lr/76208/) for more details.

##  Configuring the Populate Statement Translations Action {#pst-action-config}

When configured, users can populate statement translations for local adaptations when the local adaptation is in a particular lifecycle state. The _Populate Statement Translations_ action uses configured country-language mappings to generate _Local Adaptation Statement Join_ records based on the global statement of each specified _Claim_.

To configure this action for users, you must first [assign](/en/lr/43127/#assign-actions) the _Populate Statement Translations_ action to the _Local Adaptation_ object. Depending on your business needs, you can:

* Add this action as a [user action](/en/lr/59885/#user-actions) on the _Local Adaptation_ object.
* Add this action as an [entry action](/en/lr/59885/#entry-actions) on any _Local Adaptation_ lifecycle state.
* Add this action as a [custom workflows](/en/lr/33550/) in the _Local Adaptation_ workflow.

##  Configuring Local Adaptation Generation From a Project {#la-project-gen}

You can also configure your Vault to allow users to generate _Local Adaptations_ from a project. See [Configuring Local Adaptation Generation From a Project](/en/lr/78539/) for more details.

## Configuring Comments {#comments}

You can configure your Vault to allow users to add comments to any object, including the ability to reply to comments in comment threads on _Local Adaptation_ object records. See [Configuring Comments](/en/lr/523453/) for details.

## Configuring the Local Adaptation Lifecycle {#la-lifecycle}

_Local Adaptation Lifecycle_ is an object lifecycle which applies to all _Local Adaptation_ object records. Newly-created _Local Adaptations_ begin in the _Proposed_ lifecycle state, and contain the following other states of:

* _Approved_
* _Rejected_
* _Challenged_

You can add [custom lifecycle states](/en/lr/30683/) to suit your organization's needs.

## Configuring Claim & Local Adaptation Substantiation {#substantiation}

Veeva Claims allows users to add _Substantiations_ to each _Claim_ and _Local Adaptation_ and link _Claims_ to reference documents to provide proof of validity. See [Configuring Claim & Local Adaptation Substantiation](/en/lr/627953/) for more details.

##  Configuring User Permissions {#user-perm}

You must ensure users have the appropriate read and create [permissions](/en/lr/22824/) to access the appropriate objects and object fields in addition to the permission outlined below:

* _Read_ permission on the following objects:
    * _Local Adaptation_
    * _Statement_
    * _Local Adaptation Statement Join_
* _Execute_ permission on the _Populate Statement Translations_ object action on the _Local Adaptation_ object.

## Related Permissions

You can complete all 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](/en/lr/22824/):

<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: Object Lifecycles: Create, Edit</td>
    <td>Ability to create and modify object lifecycles.</td>
  </tr>
  <tr>
    <td>Security Profile</td>
    <td>Admin: Configuration: Objects: Create, Edit</td>
    <td>Ability to create and modify Vault objects.</td>
  </tr>
  <tr>
    <td>Security Profile</td>
    <td>Admin: Security: Permission Sets: Edit</td>
    <td>Ability to modify permission sets for users.</td>
  </tr>
</table>

[1]: #bulk-create-config
[2]: #cl-m-config
[3]: #pst-action-config
[4]: #la-project-gen
[5]: #la-lifecycle
[6]: #user-perm
[7]: #comments
[8]: #la
[9]: #la-hierarchical
[10]: #substantiation