Veeva Claims Project Management allows you to configure Local Adaptations generation in several ways so that users can create Local Adaptations from a Project in the following ways:

Configuration Overview

Configuring your Vault to generate Local Adaptations from a Project involves the following steps:

  1. Configure selective Local Adaptation creation
  2. Configure bulk Local Adaptation creation
  3. Configure the auto-population of Statement translations
  4. Configure user permissions

Configuring Selective Local Adaptation Creation

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 Generate Local Adaptations dialog. 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”.

How to Configure the Create Local Adaptations Run As System Action

To configure selective Local Adaptation creation:

  1. Assign 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 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 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

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

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. You must first define bulk create action settings by creating a Project Bulk Create Action Setting type of Claim Admin Setting. This allows you to specify which lifecycle states Claims must be in to allow Local Adaptation creation. If you do not define bulk create action settings, Local Adaptations can be created from Claims in all lifecycle states. If there are no Claims in the lifecycle states you specified, Vault does not create any Local Adaptations when users run the Bulk Create Local Adaptations (Project) action.

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 custom fields on the Local Adaptation object that are required, 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. Enter the name of the lifecycle states (not the label) from which users can create Local Adaptations from Claims. Separate multiple values with a comma. This field is case-sensitive.
  5. Click Save.
  6. Assign the Bulk Create Local Adaptations (Project) action to the Project object.
  7. Optional: Configure the Bulk Create Local Adaptations (Project) action as a user action on the appropriate lifecycle states of the Project Lifecycle.

Configuring Auto-Population of Statement Translations for Local Adaptations

After users create Local Adaptations, they can automatically populate Statement translations for the Local Adaptations if you configure the Populate Statement Translations action. See Configuring Local Adaptations for more details.

Configuring User Permissions

You must ensure users have the appropriate read and create permissions 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.