# Configuring Claim Population For a Project (Veeva Claims)

[Veeva Claims](/en/lr/54331/) Project Management allows you to configure Vault so users can [populate a _Project_ with _Claims_](/en/lr/78533/) in the following ways:

* [**Add Claims to Project**][5]: Allows users to bulk add existing _Claims_ to a specified _Project_.
* [**Selectively Create Claims**][0]: Allows users to selectively create _Claims_ for specified _Statement_ and _Product_ combinations.
* [**Bulk Create Claims**][1]: Allows users to create _Claims_ for all _Statement_ and _Product_ combinations.
* [**Assign Available Product Claims**][4]: Allows users to view and assign available _Claims_ for a _Product_ and _Project_. 

## Configuration Overview {#overview}

Configuring your Vault to generate _Claims_ for a _Project_ involves the following steps:

1. [Configure bulk add _Claims_ to a _Project_][5]
2. [Configure selective _Claim_ creation][0]
3. [Configure bulk _Claim_ creation][1]
4. Optional: [Configure the _Assign Available Product Claims_ action][4]
5. [Configure user permissions][2]

<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 Bulk Add to Project {#bulk-add}

When users run the _Add to Project_ action for a list of _Claims_ from the _Claims Library_ tab, they can refine their selection and specify which _Project_ to which they want to add the _Claims_. When the action completes, Vault generates the following records:

* One (1) _Claim Project_ for each unique combination of _Claim_ and _Project_.
* One (1) _Project Statement_ for each unique combination of _Statement_ and _Project_.
* One (1) _Project Product_ for each unique combination of _Project_ and _Product_ associated with the selected _Claims_.

This action does not create duplicate records. If a combination already exists, Vault will not generate a new record for that combination. When users run this action, Vault creates temporary [_Bulk Add to Project User Input_][6] records.

### How to Configure the Add to Project Action {#bulk-add-how-to}

You can configure this action as a [record action](/en/lr/43127/) on the _Claim_ object.

1. [Assign](/en/lr/43127/#assign-actions) the _Add to Project_ action to the _Claim_ object.
2. Do one (1) of the following:
    * Select the _Available in All Lifecycle States_ checkbox and define atomic security.
    * Configure the user action on the appropriate lifecycle states for the _Claim Lifecycle_.

###  About DAC for Objects {#dac}

When users create new join records by running the _Add to Project_ action, Vault sets the _Vault Owner_ group as the owner of the generated records. If you [configure DAC](/en/lr/33946/) for the following objects, Vault assigns the current user as the owner of the generated records:

* _Claim Project Join_
* _Project Product Join_
* _Project Statement_

### Configuring the Bulk User Input Object Cleanup Job {#cleanup-job}

The _Bulk User Input Object cleanup Job_ deletes temporary user input records created from bulk actions more than 24 hours before the jobs run. You can [configure the job's schedule](/en/lr/22897/#scheduling) to run at a specific time. We recommend that you schedule this job to run daily. 

## Configuring Selective Claim Creation {#selective-claims}

<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>: Your Vault’s configuration must include the <em>Statement</em> object for users to be able to generate multiple <em>Claims</em> which are automatically included in the <em>Project</em>.</p>
    </div>
  </div>
</div>



You can configure the _Create Claims Run As System_ action on the _Project_ object to allow users to selectively create _Claims_ from a _Project_. When users run the action, they can select which _Statements_ to create as _Claims_ for the products specified in the [_Selectively Create Claims_ dialog](/en/lr/78533/#claims-dialog). You can configure which _Statement_ fields display to users as column headers in the dialog. Vault generates one (1) _Claim_ for each specified combination of _Statement_ and _Product_, provided the combination of _Statement_ and _Product_ does not already exist as a _Claim_ in your Vault. Generated _Claims_ 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>Selectively Create Claims via User Input</em> action, which allowed users to selectively create <em>Claims</em> based on their permissions. This action is now deprecated and replaced by the <em>Create Claims Run As System</em> action, which creates all applicable <em>Claims</em>, regardless of a user’s permissions.</p>
    </div>
  </div>
</div>



### How to Configure the Create Claims Run As System Action {#selective-how}

To configure selective _Claim_ creation:

1. [Assign](/en/lr/43127/#assign-actions) the _Create Claims Run As System_ action to the _Project_ object. Do not select _Available in All Lifecycle States_. We suggest labeling this action "Create Selective Claims".
2. Configure the [user action](/en/lr/59885/#define-actions) on the appropriate lifecycle states for the _Project Lifecycle_ and specify the following:
  * Optional: **Enter Instructional Text**. This displays for users in the _Selectively Create Claims_ dialog.
  * Enter the names of up to ten (10) [supported][3] _Statement_ fields to display as **Statement Grid Columns** when users view and select records while completing the action. Separate values with a comma. The order in which you list fields dictates the order of columns from left to right on the page.
  * Enter the names of up to ten (10) [supported][3] _Product_ fields to display as **Product Grid Columns** on the _Confirmation_ page after users expand a _Statement_ section. Separate values with a comma. The order in which you list fields dictates the order of columns from left to right on the page.
  * Enter an **Action Label**. We suggest labeling this action "Create Selective Claims".

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

Vault supports the following object field types as grid columns:

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

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

## Configuring Bulk Claim Creation {#bulk-create-claims}

<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>: Your Vault’s configuration must include the <em>Statement</em> object for users to be able to generate multiple <em>Claims</em> which are automatically included in the <em>Project</em>.</p>
    </div>
  </div>
</div>



When users run the _Bulk Create Claims_ action on a _Project_ record, Vault generates one (1) _Claim_ for each combination of _Statement_, _Product_, and _Scope_, provided the combination does not already exist as a _Claim_. _Scope_ is defined in the _Product Classification_ picklist and allows users to define, for example, whether to create the _Claim_ for the _Statement_ and _Product_ combination for a product, brand, or sub-brand classification. You can [define custom values](/en/lr/1269/) for the _Product Classification_ picklist.

Review the following behavior regarding the process of generating _Claims_ from a _Project_:

* The creation process adheres to users' permissions and lets users view and create only the records to which they have _Edit_ permission.
* The creation process creates _Claims_ only when the _Statement Scope_ matches the _Product Classification_ of the _Product_.
* If a _Statement_ does not have _Scope_ specified, the creation process creates one (1) _Claim_ per _Product_.
* If object types are enabled on the _Claim_ object, the _Bulk Create Claims (Project)_ action creates _Claim_ 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.

###  How to Configure the Bulk Create Claims Action {#how-bulk}

To configure the _Bulk Create Claims_ action:

1. [Assign](/en/lr/43127/#assign-actions) the _Bulk Create Claims (Project)_ action to the _Project_ object.
2. Optional: Configure the _Bulk Create Claims (Project)_ action as an [entry action](/en/lr/59885/#entry-actions).

## Configuring the Assign Available Product Claims Action {#assign}

You can configure the _Assign Available Claims_ action on the _Product_ object, which allows users to selectively assign available _Claims_ by generating new _Claims_ for a _Product_ and _Project_. See [Configuring View & Assign Product Claims](/en/lr/725562/) for more details.

## Configuring User Permissions {#user-perms}
You must ensure users have the appropriate read and create permissions to access the appropriate objects and object fields in addition to the [permissions](/en/lr/22824/) outlined below:

To bulk add _Claims_ to a _Project_:
* _Create_ permission for the _Bulk Add to Project User Input_ object, including _Edit_ permission for the _Select Project_ field.

The _Selectively Create Claims_ dialog that users see after running the _Create Claims Run As System_ action displays data based on the following user permissions:
* Grid columns for _Statement_ and _Product_ fields for which they have _Read_ permission.
* _Products_ and _Statements_ for which they have _Read_ permission.

[0]: #selective-claims
[1]: #bulk-create-claims
[2]: #user-perms
[3]: #supported-fields
[4]: #assign
[5]: #bulk-add
[6]: #cleanup-job