# Configuring Claims Management (Veeva Claims)

[Veeva Claims](/en/lr/54331/) provides a standardized way for legal and regulatory teams to manage how your organization requests, develops, reviews, approves and, if needed, withdraws product claims in the consumer goods industry. [Claims Management](/en/lr/54337/) keeps substantiation documents and legal and regulatory approvals organized in a single place, which gives users a clear line of sight to all the claims your organization has in the market.

Claims Management also provides the ability to [create a statement library][1] of desired messages which users can use when creating claims. A statement is a standalone desired message, such as "100% Organic." Statements are not tied to a product. With the availability of a statement library, users can create claims quickly by selecting a statement and the product to which they want to apply the selected statement. A claim is a statement about a particular product.

Veeva Claims allows you to edit and add to your [application data model](/en/lr/15298/) by [customizing standard objects](/en/lr/15057/), creating custom objects, and [configuring object relationships](/en/lr/28740/). You can also configure business rules using lifecycle and workflow options.

## Configuration Overview {#overview}

Configuring your Vault to use Claims Management involves the following steps:

1. [Define the _Claim Tier Setting_][14]
2. [Configure statement uniqueness][15]
3. [Configure self-referencing _Statements_][1]
4. [Configure substantiation on _Claims_][11]
5. [Configure local adaptations][4]
6. [Configure product line extensions][5]
7. Optional: [Configure view and assign available product _Claims_][16]
8. Optional: [Configure comments][3]
9. Optional: [Review the _Claims_ lifecycles and adding custom lifecycle states][7]
10. Optional: [Review the _Claims_ workflows and adding customization][8]

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



## Defining the Claim Tier Setting {#claim-tier}

You must define the claim tier setting by creating a _Claim Tier Setting_ type of _Claim Admin Setting_. This enables the layer of _Statement_ object in a Vault's configuration, allowing users to create _Claims_ by selecting existing _Statements_ from the statement library (after the statement library is [populated with records](/en/lr/54337/#create_statement)).

To define the claim tier setting:

  1. Navigate to **Business Admin > Objects > Claim Admin Settings**.
  2. Click **Create**.
  3. For **Setting Type**, select **Claim Tier Setting**.
  4. Select **Enable 3rd Layer (Statement)**.
  5. Click **Save**.

## Configuring Statement Uniqueness {#uniqueness}

You can configure your Vault to enforce uniqueness criteria for a single statement text and language combination. When configured, users cannot [create](/en/lr/54337/#create_statement) duplicate _Statements_ for the same language. To configure statement uniqueness:

1. Navigate to **Admin > Configuration > Objects > Statement > Fields > Statement Uniqueness**.
2. Click **Edit**.
3. Select the **Values must be unique** checkbox. 
4. Click **Save**.

## Configuring Self-Referencing Statements {#statements}

We recommend configuring self-referencing _Statements_ so that users can store translations or dialect variations of _Statements_. By using self-referencing _Statements_, you can tie translated _Statements_ to one (1) global parent _Statement_. A global _Statement_ can be in any language; however, we recommend committing to a single language for all global _Statements_ in your Vault.

To configure self-referencing _Statements_:

* Configure the _Statement_ [object layout](/en/lr/26387/):
  * Include the _Statement Language_ and _Global Statement_ fields.
  * Include a [related object section](/en/lr/26387/#related-object) for the _Statement_ object. Include the _Statement Language_ field to display as a column for this section.
* Review the values in the _Country Language_ [picklist](/en/lr/1269/) and add values as needed. Users select a language value from this picklist when creating _Statements_.

## Configuring Local Adaptations {#la-config}

See [Configuring Local Adaptations](/en/lr/76206/) for more details.

## 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 Product Line Extensions {#pl-extensions}

Veeva Claims allow users to copy _Claims_ from one (1) _Product_ to another to improve efficiency in cases where another _Product_ needs to utilize the same set of _Claims_.

Review the following behavior regarding the process of copying from the source set of _Claims_ to the target set of _Claims_:

* If a _Claim_ has a field that has both _Values must be unique_ and _Users must always enter a value (required)_ selected, the copy process will not copy the record. If you want Vault to copy required custom fields when users create product line extensions, do not select the _Values must be unique_ checkbox.
* If a _Claim_ has a field that has _Values must be unique_ selected but _Users must always enter a value (required)_ not selected, the copy process will copy the record but not the field; however, if the unique but not required field is set as required for the object type, the copy process will not copy records of that object type.
* If a _Claim_ has a field that has _Do not copy this field in Copy Record_ selected, the copy process will copy the record but not the field.
* Fields are copied for a record in an object type only if you've enabled the field on that object type.
* Vault copies only _Claims_ to which users have _Edit_ permission but copies all related _Substantiations_, including those they may not have permission to _Read_.

### How to Configure Product Line Extensions {#ple-how}

To configure your Vault to support product line extensions:

* Assign the _Bulk Copy Claims_ [action](/en/lr/43127/#assign-actions) to the _Product_ object to allow users to copy _Claims_ from one (1) _Product_ to another. We suggest labeling this action "Copy Claims to Another Product".
* Optional: Add the _Copy Related Substantiation Records_ field to the _Copy Claims To Another Product_ [object layout](/en/lr/26387/). This allows users to specify if they want to copy existing active _Substantiations_ and their related documents to the new _Claims_, generating new _Claim Substantiation Joins_.

## Configuring Configuring View & Assign Product Claims {#view-assign}

You can configure the _Available Parent Claims_ and _Available Child Claims_ sections on the _Product_ object layout, which allows users to review all _Claims_ in the _Product's_ hierarchy based on the related _Product Compositiosn_. You can also configure the _Assign Available Claims_ action on the _Product_ object, which allows users to selectively assign available _Claims_ by generating new _Claims_ for the _Product_. See [Configuring View & Assign Product Claims](/en/lr/725562/) for more details.

## Configuring Comments {#claims-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 certain object records. See [Configuring Comments](/en/lr/523453/) for details.

##  Claims Management Lifecycles {#lifecycles}

Veeva Claims includes the following [object lifecycles](/en/lr/29798/):

* **Claim Lifecycle**: Newly-created _Claims_ begin in the _Proposed_ lifecycle state. If your Vault includes [Pack Copy](/en/lr/63393/), you can optionally configure the [_Auto Create Element_](/en/lr/63393/#auto-create-element) action as an entry action in the _Claim Lifecycle_.
* **Statement Lifecycle**: Newly-created _Statements_ begin in the _Draft_ lifecycle state and have other states of: _In Use_ and _Rejected_. This lifecycle is available only if your Vault's configuration [includes a statement library][1].
* **Substantiation Lifecycle**: Newly created _Substantiations_ begin in the _Draft_ lifecycle state and have the other states of: _Approved_, and _Rejected_.

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

## Claims Workflows {#workflows}

The _Claim Lifecycle_ includes the following standard [workflows](/en/lr/33498/):

* **Claim Substantiation Development**: Sends a task to provide substantiation for a _Claim_ and ends in a state change to _Substantiation Development Complete_ or, if no supporting evidence was found, _Substantiation Unavailable_.
* **Claim Review**: Sends a review task to evaluate a claim and provide feedback prior to approval. If reviewers accept the _Claim_ as is, the _Claim_ changes to _Review Complete_ state. Reviewers can also ask for changes to the _Claim_, which changes the _Claim_ state to _Revise and Resubmit_.
* **Claim Approval**: Sends a task to give final approval to a _Claim_. When the workflow completes successfully, the _Claim_ ends in _Approved_ state. Approvers may also reject the _Claim_, which ends the _Claim_ in _Rejected_ state.

You can [customize standard workflows](/en/lr/33550/) or create custom workflows. If your Vault includes [Pack Copy](/en/lr/63393/), you can configure the [_Auto Create Element_](/en/lr/63393/#auto-create-element) action as a workflow system step in the _Claim Approval_ workflow or a custom workflow.

## 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: Object Workflows: Create, Edit</td>
    <td>Ability to create and modify workflows.</td>
  </tr>
  <tr>
    <td>Security Profile</td>
    <td>Admin: Configuration: Objects: Create, Edit</td>
    <td>Ability to create and modify 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]: #statements
[2]: #cm-objects
[3]: #claims-comments
[4]: #la-config
[5]: #pl-extensions
[6]: #object_config
[7]: #lifecycles
[8]: #workflows
[9]: #user-perms
[10]: #bulk-comments
[11]: #substantiation
[12]: #bulk-substantiation
[13]: #cleanup-job
[14]: #claim-tier
[15]: #uniqueness
[16]: #view-assign