Configuring Local Adaptations (Veeva Claims)

Veeva Claims provides users with the ability to create local adaptations of claims 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.

Local Adaptations Objects

Veeva Claims uses the following core objects to support Local Adaptations:

• Statement (statement_v): This object represents the standalone desired messaging, in the specified language.
• Claim (claim__v): This object represents an individual claim and includes information about the statement, the footnote (fine print), and the product to which the claim applies.
• Local Adaptation (local_adaptation__v): This object represents an adaptation of a Claim, adapted for a specific location.
• Local Adaptation Statement Join (local_adaptation_statement_join__v): This object joins the Local Adaptation and Statement objects and allows a local adaptation to store multiple translations or variations of a global statement.
• Country Language (country_language_mapping_object__v): This object represents which languages apply to each country (Location).
• Bulk Create Local Adaptations (local_adaptation_user_input_object__v): This object represents the location and Marketing Channel selections made by users. These user input records temporarily store the selections before Vault generates all Local Adaptation records in bulk.

Configuration Overview

Configuring your Vault to create Local Adaptations involves the following steps:

1. Configuring the Local Adaptation object
2. Configuring the Bulk Create Local Adaptations action
3. Defining country-language mappings
4. Configuring the Populate Statement Translation action
5. Configuring Local Adaptation generation from a Project
6. Optional: Configuring comments on the Local Adaptation object
7. Configuring the Local Adaptation lifecycle
8. Configuring user permissions

Configuring the Local Adaptation Object

You can configure your Vault to support users creating new Local Adaptations by copying existing records.

Object Types & Page Layout

Users often create new Local Adaptations by copying existing records, either by copying a Local Adaptation record or by copying the Local Adaptation hierarchy when copying a Claim. To establish a link to the copied record and maintain traceability to the original Local Adaptation, assign the following Local Adaptation fields to all object types and add them to the object page layout:

• Source Local Adaptation
• Source Local Adaptation Claim

Hierarchical Local Adaptation Copy

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 checkbox for the Claim field on the Local Adaptation object.

Configuring the Bulk Create Local Adaptations Action

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.

To configure the Bulk Create Local Adaptations record 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 not specific to a particular lifecycle state or states. After you select this option, you cannot deselect it.
6. Click Save.
7. In the Atomic Action Security Defaults dialog, review the default action for each lifecycle state.
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 page layout to include a Related Object section for the Local Adaptation object.
11. Navigate to the Bulk Create Local Adaptations object page layout and complete the following:
    1. Add the Select Locations control field with the slider () icon to the Details section.
    2. Add the Select Location field to the Details section.
    3. Configure a layout rule to hide the Select Location field from the page layout.

Defining Country-Language Mappings

You must create country-language mappings before you can configure the Populate Statement Translations action. See Defining Country Language Mappings for more details.

Configuring the Populate Statement Translations Action

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 the Populate Statement Translations action to the Local Adaptation object. Depending on your business needs, you can:

• Add this action as a user action on the Local Adaptation object.
• Add this action as an entry action on any Local Adaptation lifecycle state.
• Add this action as a custom workflows in the Local Adaptation workflow.

Configuring Local Adaptation Generation From a Project

You can also configure your Vault to allow users to generate Local Adaptations from a project. See Configuring Local Adaptation Generation From a Project for more details.

Configuring 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 for details.

Configuring the Local Adaptation 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 to suit your organization’s needs.

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 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:

Type	Permission	Controls
Security Profile	Admin: Configuration: Object Lifecycles: Create, Edit	Ability to create and modify object lifecycles.
Security Profile	Admin: Configuration: Objects: Create, Edit	Ability to create and modify Vault objects.
Security Profile	Admin: Security: Permission Sets: Edit	Ability to modify permission sets for users.