What's New in 24R2.2

The Align 24R2.2 release includes brief, high-level descriptions of enhancements, new features, and more.

Announcements

Implementing the Common Data Architecture for Life Sciences

Starting in 24R2.0, Veeva is implementing the Common Data Architecture for Life Sciences (CDA.LS or CDA) in both Vault CRM and Vault CRM Align. The Align 24R2.0 release supports data model updates to the account__aln and address__v objects. Due to the updates to existing field names, customers must review their custom content (including reports, sharing rules, layouts, and other custom code) to see if the content needs to be updated to use the new field names. See Veeva CDA for more information. See Data Model Updates for the Common Data Architecture for Life Sciences for a list of data model changes.

Features

User Management

Designating a Primary Territory

To determine incentive compensation credit for territory assignments in downstream systems, establish clear territory responsibilities, and resolve integration conflicts that may occur when a user is assigned to multiple territories, Align admins can designate a territory as being a roster member’s primary territory. Primary territories are prioritized when Align configures a user in CRM using setup data inherited from their functional profiles, but the user is assigned to multiple territories with different functional profiles.

User Visible and Behavior Changes

CRM Integration

Description	Before	After
The following inbound field mappings were introduced, enabling Align admins to import a roster member's country from Vault CRM. The vcountry__v field on the user__sys object – Maps to the country__aln field on the roster_member__aln object. This field can be used to create custom country clusters. The country__v field on the user__sys object – Maps to the country__aln field on the roster_member__aln object. This field is a fixed picklist of values. These mappings are inactive by default and must be activated by the Align admin. If both field mappings are activated, the vcountry__v field is prioritized when importing from Vault CRM.

Description

Before

After

The following inbound field mappings were introduced, enabling Align admins to import a roster member's country from Vault CRM.

The vcountry__v field on the user__sys object – Maps to the country__aln field on the roster_member__aln object. This field can be used to create custom country clusters.
The country__v field on the user__sys object – Maps to the country__aln field on the roster_member__aln object. This field is a fixed picklist of values.

These mappings are inactive by default and must be activated by the Align admin. If both field mappings are activated, the vcountry__v field is prioritized when importing from Vault CRM.