Veeva Claims provides Brand Managers the abilty to initiate a project and group claims pertaining to a particular initiative in this project so that key R&D, regulatory, and legal stakeholders can track and work on the related claims as a group. From a Project, users can generate multiple Claim records and multiple Local Adaptations.
Brand Managers in the consumer goods industry typically work on initiatives such as new product development, product line extensions, and packaging refresh initiatives. Proposing, substantiating, reviewing and approving product marketing claims is a sub-activity of these initiatives.
Project Management is automatically active on all Veeva Claims Vaults and allows you to edit and add to your application data model by customizing standard objects, creating custom objects, and configuring object relationships. You can also configure business rules using lifecycle and workflow options.
Project Management Objects
Veeva Claims uses the following core objects to support Project Management:
- Project (
project__v): This object represents a project and contains the system-managed Copied from Project (copied_from_project__v) field which allows users to see the record from which a Project was copied. - Claim Project Join (
claim_project_join__v): This object joins the Claim and Project objects and allows a Claim to be associated with multiple Projects. - Claim (
claim__v): This object represents an individual claim and contains information about the Statement, the footnote, and which Products use the Claim. - Statement (
statement__v): This object represents the standalone desired messaging. - Project Statement (
project_statement_join__v): This object joins the Project and Statment objects and allows a Statement to be associated with multiple Projects. - Project Product Join (
project_product_join__v): This object This object joins the Project and Product objects and allows a Product to be associated with multiple Projects. - Project Country Join (
project_country_join__v): This object joins the Project and Location (country__v) objects and allows a Location to be associated with multiple Projects. - Project Local Adaptation Join (
project_local_adaptation__v): This object joins the Project and Local Adaptation objects and allows a Local Adaptation to be associated with multiple Projects.
Configuration Overview
Configuring your Vault to use Project Management involves the following steps:
- Configure Project cloning
- Configure project teams
- Configure Claim generation from a Project
- Configure Local Adaptation from a Project
- Configure the Project Hierarchy Viewer
- Configure comments
- Configure statement and related record removal
- Configure user permissions
Note: 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.
Configuring Project Cloning
The Project object contains the Clone Project action, which allows users to dynamically deep copy (or “clone”) an existing Project record and selectively copy related records from the existing Project to reference in the new Project.
After users select the Clone Project action, make their selections to copy, and finish the action, and then click Clone Project, Vault does the following:
- Copies the Project record and includes “Copy of [Project Name of cloned record]” in the Project Name of the new record.
- Creates new join records to the users-selected groups of records such as Claims, Local Adaptations, Locations, Products, and Statements.
- Excludes any child records in the existing project, such as Project Comments.
Review the following behavior regarding the way Vault handles fields on the existing Project during the cloning process:
- All custom field values are copied over.
- All fields with the attribute Users must always enter a value (required) selected (including custom fields) are copied over.
- If a field has the attribute Values must be unique selected and Users must always enter a value (required) unselected, Vault does not copy over the field.
- If a field has the attribute Values must be unique selected and Users must always enter a value (required) selected, the action will fail.
- If any Picklist type field has an inactive field value, the action will fail.
How to Configure Project Cloning
To configure project cloning:
- Navigate to Admin > Configuration > Pages > Clone Project.
- In the Layouts section, click Clone Project.
- Click Edit.
- Optional: Specify up to ten (10) Exclusion Rules.
- Optional: Select Enforce Claim - Statement and Product Dependency to automatically select the related Statement and Product records when users select a Claim for cloning.
- Optional: Select Enforce Local Adaptation - Claim and Country Dependency to automatically select the related Claim and Location (country) records when users select a Local Adaptation for cloning.
- Click Save.
Note: If you enforce dependencies, users cannot unselect the automatically selected related records without unselecting the record with dependencies.
About Exclusion Rules
When configuring the Clone Project page, you can specify Exclusion Rules to instruct Vault to exclude records in specific states from appearing to users to select when they run the Clone Project action. You can specify only one (1) Exclusion Rule per object; however, you can include multiple lifecycle states using a comma (“,”) delimiter. If you don’t specify any Exclusion Rules, Vault displays all records in all lifecycle states for users to select when cloning a project.
Use the following format for Exclusion Rules:
{"objectName":"object_name", "statesToBeExcluded":["state_id", "state_id"]}
Where object name and state id are the Object Name and State Name, respectively, such as claim__v and rejected_state__c. For example, you could use the following Exclusion Rule to ensure that join records are not created in the new Project to Claim records in the Rejected or Withdrawn lifecycle states:
{"objectName":"claim__v", "statesToBeExcluded":["rejected_state__c", "withdrawn_state__c"]}
Configuring the Clone Project Action
You can configure the Clone Project action as a user action:
- Assign the Clone Project action to the Project object.
- Configure the user action on the appropriate lifecycle states for the Project Lifecycle.
Configuring the Project Object Layout
We recommend configuring the Project object layout to include the system-managed field Copied from Project (copied_from_project__v) so that users can see which record a project was copied from.
Configuring Project Teams
To support project teams, you must update the Project object layout to include a related object section for the Project Team User object.
Configuring Claim Generation For a Project
You can configure Projects to allow users to create and add Claims to a Project. See Configuring Claim Generation For a Project for more details.
Configuring Local Adaptation Generation From a Project
You can configure Projects to allow users to generate Local Adaptations from a Project. See Configuring Local Adaptation Generation From a Project for more details.
Configuring the Project Hierarchy Viewer
You can configure the Project Hierarchy Viewer, allowing users to easily visualize and interact with a Project’s hierarchy. Users can review all related records within the context of a Project to make an informed assessment. See Configuring the Project Hierarchy Viewer 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 Project object records. See Configuring Comments for details.
Configuring Statement & Related Record Removal
Veeva Claims allows users to remove Statements, Claims, and Local Adaptations from a Project to quickly remove all records they don’t need before moving the project forward.
You must add the Remove Statement and Related Records action as a record action to the Project object. When users run the action, Vault displays the Remove Statement and Related Records from Project page, where users can select which Project Statements, Claims, and Local Adaptations they want to remove from a Project. When users complete the action, Vault deletes the applicable Project Statement, Claim Project Join, and Project Local Adaptation Join records.
Configuring the Remove Statement and Related Records from Project Page
To configure the Remove Statement and Related Records from Project page to customize the details users see on the page:
- Navigate to Admin > Configuration > Pages > Remove Statement and Related Records from Project.
- In the Layouts section, click Remove Statement and Related Records from Project.
- Click Edit.
- Optional: Modify the Label for the page that appears to users as the page title.
- Optional: Enter Instructional Text that appears to users on the top of the page.
- Optional: Select or clear the Remove Statement checkbox to determine the default value displayed to users on the Remove Statement and Related Records from Project page. When selected by a user, Vault removes the Project Statements in addition to any related Claim Project Joins and Project Local Adaptation Joins selected by the user. When cleared by a user, Vault deletes only the related Claim Project Joins and Project Local Adaptation Joins selected by the user.
- Click Save.
Project Lifecycle
The Project lifecycle is an object lifecycle which applies to all Project object records. New projects begin in the New lifecycle state.
You can configure and use state changes as simple actions to move Projects from one (1) state to another, and also configure custom workflows for Projects to suit your specific needs.
Project States
The Project lifecycle includes the following standard states:
- New: The initial state of the Project.
- In Progress: Claims within the Project are in various stages of approval.
- Completed: All Claims within the Project have been approved.
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:
Clone Project
Users must have the following permissions to be able to run the Clone Project action and be able to select sections of objects on the Clone Project page:
- Create permission on the Project object.
- Create permission on the appropriate Project join objects.
- Execute permission on the Clone Project object action.
If users do not have Create permissions on any of the Project join objects, they cannot view or select any records to copy for that object when they clone a Project.
Statement & Related Record Removal
Users must have the following permissions to remove Statements, Claims, and Local Adaptations from a Project:
- Pages: Remove Statement and Related Records from Project: View
- Read permission on the following objects:
- Statements
- Claim
- Local Adaptation
- Delete permission on the following objects, including any relevant object types users need to remove from Projects:
- Project Statement
- Claim Project Join
- Project Local Adaptation Join
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 Lifecycle: Edit | Ability to 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. |
| Security Profile | Pages: All Pages: Remove Statement and Related Records from Project: View | Ability to configure the Remove Statement and Related Records from Project page. |