# Configuring Local Adaptation Generation From a Project (Veeva Claims)

<a href="/en/gr/54331/">Veeva Claims</a>
 Project Management allows you to configure _Local Adaptations_ generation in several ways so that users can <a href="/en/gr/78535/">create _Local Adaptations_ from a _Project_</a>
 in the following ways:

* [**Selectively Create Local Adaptations**][0]: Allows users to create _Local Adaptations_ for select _Location_ and _Claim_ combinations.
* [**Bulk Create Local Adaptations (Project)**][1]: Allows users to create _Local Adaptations_ for all _Location_ and _Claim_ combinations.

## Configuration Overview {#overview}

Configuring your Vault to generate _Local Adaptations_ from a _Project_ involves the following steps:

1. [Configure selective _Local Adaptation_ creation][0]
2. [Configure bulk _Local Adaptation_ creation][1]
3. [Configure the auto-population of _Statement_ translations][2]
4. [Configure user permissions][3]

<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 Selective Local Adaptation Creation {#selective}

You can configure the _Create Local Adaptations Run As System_ action on the _Project_ object to allow users to selectively create _Local Adaptations_ from a _Project_. When users run the action, they can select which _Claims_ to create as _Local Adaptations_ for the specified _Locations_ in the <a href="/en/gr/78535/#generate-la-dialog">_Generate Local Adaptations_ dialog</a>
. You can configure which _Claim_ fields display to users as column headers in the dialog. Vault generates one (1) _Local Adaptation_ for each specified combination of _Claim_ and _Location_, provided the combination of _Claim_ and _Location_ does not already exist as a _Local Adaptation_ in your Vault. Generated _Local Adaptations_ have a _Created By_ value of "System".

<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>: In Vaults created prior to 24R1, you may have configured the <em>Create Local Adaptations via User Input</em> action, which allowed users to selectively create <em>Local Adaptations</em> based on their permissions. This action is now deprecated and replaced by the <em>Create Local Adaptations Run As System</em> action, which creates all applicable <em>Local Adaptations</em>, regardless of a user’s permissions.</p>
    </div>
  </div>
</div>



### How to Configure the Create Local Adaptations Run As System Action {#user-input-how}

To configure selective _Local Adaptation_ creation:

1. <a href="/en/gr/43127/#assign-actions">Assign</a>
 the _Create Local Adaptations Run As System_ action to the _Project_ object. Do not select _Assign to All Lifecycle States_. We suggest labeling this action "Create Selective Local Adaptations".
2. Configure the user action on the appropriate lifecycle states of the _Project Lifecycle_ and specify the following:
    * Optional: Enter **Instructional Text**. This displays for users in the _Generate Local Adaptations_ dialog.
    * Optional: Specify which active _Claim_ object fields display to users in the _Generate Local Adaptations_ dialog. The order in which you add fields dictates the order of columns displayed from left to right in the dialog. If you do not specify any fields, the dialog includes the _Name_, _Select Statement_, and _Product_ fields by default.
      * In the **Claim Grid Columns (Ordered)** field, enter the names of up to ten (10) [supported][4] _Claim_ object fields, separating multiple values with a comma. This field supports up to 255 characters.
      * If you previously specified which fields to display in the _Generate Local Adaptations_ dialog using the **Grid Columns** field, we recommend clearing the field. Any values in this field are ignored when you populate the _Claim Grid Columns (Ordered)_ field.
    * In the **Location Grid Columns** field, enter the names of up to ten (10) [supported][4] _Location_ object fields, separating multiple values with a comma, to display on the _Confirmation_ page after users expand a _Claim_ section. This field supports up to 255 characters. The order in which you list fields dictates the order of columns from left to right on the page.
    *  Optional: Select up to 20 **Claim Lifecycle States** from which users can create _Local Adaptations_ from a _Claim_. If you do not specify any lifecycle states, _Claims_ in all lifecycle states are available for user selection.
    * Enter an **Action Label**. We suggest labeling this action "Create Selective Local Adaptations".

#### Supported Field Types {#supported-fields}

Vault supports the following object field types as grid columns:

* Component (for lifecycles and lifecycle states)
* Date
* Long Text
* Lookup
* Number
* Object
* Picklist
* Text
* Yes/No

If you have configured object types on the _Claim_ or _Location_ objects, ensure you assign any fields you add as grid columns to all applicable object types.

## Configuring Bulk Local Adaptation Creation {#bulk}

You can configure the _Bulk Create Local Adaptations (Project)_ action to allow users to generate _Local Adaptations_ in bulk for all _Location_ and _Claim_ combinations from a _Project_. Review the following behavior regarding the process of generating _Local Adaptations_ from a project:

* If object types are enabled on the _Local Adaptation_ object, the _Bulk Create Local Adaptations_ action creates _Local Adaptations_ records only for the default object type.
* If you add required custom fields to the _Local Adaptation_ object, ensure you specify a default value.

To configure bulk _Local Adaptation_ generation:

1. Navigate to **Business Admin > Objects > Claim Admin Settings**.
2. Click **Create** to create a **Claim Admin Setting**.
3. Select **Project Bulk Create Action Setting** as the **Setting Type**.
4. Click **Save**.
5. Define the lifecycle states from which users can create _Local Adaptations_ from _Claims_: 
  * Navigate to **Admin > Configuration > Project Bulk Create Action Setting**.
  * Click **Create**.
  * Enter a **Name**.
  * Select up to 20 **Lifecycle States**.
  * Click **Save**.
6. <a href="/en/gr/43127/#assign-actions">Assign</a>
 the _Bulk Create Local Adaptations (Project)_ action to the _Project_ object.
7. Optional: _Configure the Bulk Create Local Adaptations (Project)_ action as a <a href="/en/gr/59885/#define-actions">user action</a>
 on the appropriate lifecycle states of the _Project Lifecycle_.

If there are no _Claims_ in the specified _Lifecycle States_, Vault does not create any _Local Adaptations_ when users run the _Bulk Create Local Adaptations (Project)_ action.

## Configuring Auto-Population of Statement Translations for Local Adaptations {#auto-pop}

After users create _Local Adaptations_, they can automatically populate _Statement_ translations for the _Local Adaptations_ if you configure the _Populate Statement Translations_ action. See <a href="/en/gr/76206/">Configuring Local Adaptations</a>
 for more details.

## Configuring User Permissions {#user-perm}

You must ensure users have the appropriate read and create <a href="/en/gr/22824/">permissions</a>
 to access the appropriate objects and object fields in addition to the permissions outlined below:

### Configuring Create Selective Local Adaptations

The _Selectively Create Local Adaptations_ dialog that users see after running the _Create Local Adaptations Run As System_ action displays data based on the following user permissions:

* Grid columns for _Claim_ and _Location_ (`country__v`) fields for which they have _Read_ permission.
* _Claims and Locations_ for which they have _Read_ permission.

[0]: #selective
[1]: #bulk
[2]: #auto-pop
[3]: #user-perm
[4]: #supported-fields
[5]: #user-input-how