The Veeva Claims Project Hierarchy Viewer allows users to visualize a Project and its hierarchical structure of Claim and Local Adaptation records so they can review all related records in context and make an informed assessment. Users add filters to adjust the scope of the project’s related records that appear in the viewer.
About Filters
Users can apply filters to the viewer on a Project’s detail page to narrow the scope of displayed records for any Project, Claim, or Local Adaptation object field you configure as a column header. The hierarchy viewer displays pre-filtered values for any field that is an object reference field to the Location (country__v) object or the Product (product__v) object, such as:
- Claim > Product
- Local Adaptation > Location
These pre-filtered values ensure available values users can select include only the locations and products linked to the Project record. The number of records available for user selection for field values in any filter is limited to 100 records.
Configuration Overview
Configuring your Vault to use the Project Hierarchy Viewer involves the following steps:
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 Object Page Layouts
You must add the Hierarchy control section to the object page layouts of the following objects so that users can navigate through a project’s hierarchy:
- Project (
project__v) - Claim (
claim__v) - Local Adaptation (
local_adaptation__v)
If you don’t configure the section on all listed objects, users cannot navigate through the hierarchy’s record detail pages. For example, if you choose to configure the Hierarchy section on the Project object only but not on the Claim object and a user clicks on a Claim record in the viewer from a project’s detail page, the user cannot continue to navigate through the project’s hierarchy on the selected Claim’s detail page.
As best practice, ensure you configure the same fields in the same order on all listed objects for the following options:
- Display Project columns
- Display Claim columns
- Display Local Adaptation columns
Ensure the columns in the viewer are consistent on the Project, Claim, and Local Adaptation object record detail pages when users navigate through the hierarchy.
Configuring the Hierarchy Section
To configure the Hierarchy section for each object’s page layout:
- Navigate to the appropriate object’s page layout.
- Click Edit.
- Click Add Section and select the Hierarchy control section with the slider (
) icon. - Optional: Enter a Section Label.
- Optional: In the Show the section only in these lifecycle states field, select one (1) or more lifecycle states. This option appears only if the object uses a lifecycle.
- Optional: Enter Section Help content to provide the user with any relevant information. Help content appears below the section label.
- Select up to ten (10) supported Project fields to Display Project columns. Drag and drop fields to determine the order of columns to display to users.
- Select up to ten (10) supported Claim fields to Display Claim columns. Drag and drop fields to determine the order of columns to display to users.
- Select up to ten (10) supported Local Adaptation fields to Display Local Adaptation columns. Drag and drop fields to determine the order of columns to display to users.
- Optional: Select Expand section by default.
- Click Done.
- Click Save.
Supported Fields
Vault supports the following object field types in Display [Object] column fields:
- Component (for Lifecycle states)
- Date
- Number
- Object
- Object Reference
- Picklist
- Text/Long Text
- Yes/No
- Lookup (so long as the type is a supported type listed above)
The Display [Object] column field always includes the Name (name__v) field as the first column.
Configuring User Permissions
You must ensure users have a security profile with permissions to access the appropriate objects and object fields in order to see the Hierarchy section on an object’s detail page, including Read permission on the Claim Project Join object and Project Local Adaptation Join object.
In addition, users must have field-level permissions on the Project, Claim, and Local Adaptation objects to be able to see all configured columns in the viewer.
Understanding Filter Permissions
Lists of pre-filtered field values are pulled into the hierarchy viewer. Review the following details about pre-filtered field values:
- Users without Read permission on the Product object continue to see Product ID (
name__v) values where the Product is linked to the Claim records for which they have appropriate permissions. - Users without Read permission on the Project Product Join object see Product ID (
name__v) values where the Product is linked to the Claim records for which they do have appropriate permissions. - Users without Read permission on the Project Country Join object see Location (
country__v) values where the Location is linked to Local Adaptation records for which they do have appropriate permissions. - Users without Read permission on the Product field of the Claim object or the Location (
country__v) field of the Local Adaptation object cannot see the Product or Location field columns in the hierarchy viewer and cannot select filters for these fields or see pre-filtered field values.
Related Permissions
You can complete all the 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: Objects: Create, Edit | Ability to create and modify Vault objects. |
| Security Profile | Admin: Security: Permission Sets: Edit | Ability to modify permission sets for users. |