What's New in 24R2.0
The Align 24R2.0 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
Integrated Territory Feedback
Integrated Territory Feedback Overview
Align enables end-users to provide feedback regarding targeting assignments and changes to their territory. This streamlines the planning process by allowing end-users to view changes to their territory directly on their devices as well as enabling administrators to configure rules to automatically accept or reject certain challenges to that territory.
Integrated Territory Feedback utilizes both Vault CRM and Align to enable end users to review and provide feedback regarding upcoming changes to the assignments and targets within their territory.
Reviewing Feedback as a Manager
Managers can review feedback provided by end users via the Territory Feedback tab in Vault CRM in the browser. Managers can view a dashboard displaying the current status of their team’s feedback as well as their feedback metrics. Managers can quickly approve all outstanding feedback with a single action, or they can view an individual territory to review the individual challenges created by end users.
CRM Integration
Aligning Content in Vault CRM Using Align
Content alignment enables customers to give the right users access to the right Approved Email and CLM content by using content groups, grouping users and content together.
The country__aln field on roster_member__aln records can reference customer-defined custom countries. These custom countries can be pushed to Vault CRM for sharing and reporting purposes by creating a custom outbound field mapping from the country__aln field in Align to the vcountry__v field in Vault CRM.
User Management
Managing Vault CRM Application Profiles in Align
Application profiles simplify the process of managing Vault CRM by allowing admins to create groups of users that all share a similar set of application configurations. Align admins can import application profiles from Vault CRM, assign them to the appropriate functional profiles and individual roster members, then push those assignments back to Vault CRM, enabling admins to avoid inputting data in both systems.
Managing Vault CRM Layout Profiles in Align
Layout profiles control the layouts of various Vault CRM objects a user can for each available object type. Align admins can import layout profiles from Vault CRM, control the assignment of layout profiles for each roster member, and push those assignments back to Vault CRM, enabling admins to avoid inputting data in both systems.
Managing Vault CRM User Security Policies in Align
Security policies in Vault CRM control various session and security settings for Vault CRM users, including Customer SSO policies, password expiration durations, and more. While Vault CRM provides standard security policies used by default, custom security policies can be created in Vault CRM, imported into Align, and assigned to the appropriate functional profiles or individual roster members, enabling admins to avoid defining security profiles in both systems.
Resetting Vault CRM User Passwords in Align
To avoid unnecessary work in both Align and Vault CRM, admins can reset user’s passwords via their associated roster_member__aln record in Align. When a roster member marked for a password reset is pushed to Vault CRM, the associated user is notified to reset their password via Vault’s standard reset password email.
Common Data Architecture Updates
The 24R2.0 Release includes following updates to the data model as part of the implementation of the Common Data Architecture for Life Sciences (CDA.LS or CDA). Data model updates include adding new fields to existing objects and updating the API names of some existing fields. Due to the updates to existing field names, customers must review their custom content to see if the content needs to be updated to use the new field names.
Certain new fields introduced are automatically mapped to corresponding fields in Vault CRM.
Updated Fields
|
Object |
Original Field Name |
New Field Name |
Field Mapping Type |
|---|---|---|---|
|
account__aln |
first_name__aln |
first_name_cda__v |
System |
|
account__aln |
last_name__aln |
last_name_cda__v |
System |
|
address__aln |
address_line_2__aln |
street_address_2_cda__v |
System |
|
address__aln |
city__aln |
city_cda__v |
System |
|
address__aln |
latitude__aln |
latitude_cda__v |
Custom |
|
address__aln |
longitude__aln |
longitude_cda__v |
Custom |
|
address__aln |
postal_code__aln |
postal_code_cda__v |
Custom |
|
address__aln |
primary__aln |
primary_cda__v |
System |
New Fields
|
Object |
Field Name |
Label |
Type |
Field Mapping Type |
|---|---|---|---|---|
|
account__aln |
veevaid__v |
Veeva ID |
Text |
System |
|
account__aln |
hcp_type_cda__v |
HCP Type |
Picklist |
System |
|
account__aln |
spec_1_cda__v |
Primary Specialty |
Picklist |
System |
|
account__aln |
all_spec_cda__v |
All Specialties |
Multivalue Picklist |
System |
|
account__aln |
spec_group_1_cda__v |
Primary Specialty Group |
Picklist |
System |
|
account__aln |
all_spec_group_cda__v |
All Specialty Groups |
Multivalue Picklist |
System |
|
account__aln |
status_cda__v |
Status |
Picklist |
System |
|
account__aln |
level_cda__v |
Level |
Picklist |
System |
|
account__aln |
degree_1_cda__v |
Primary Medical Degree |
Picklist |
System |
|
account__aln |
all_degree_cda__v |
All Medical Degrees |
Multivalue Picklist |
System |
|
account__aln |
adopter_type_cda__v |
Adopter Type |
Picklist |
System |
|
account__aln |
clin_researcher_cda__v |
Clinical Researcher |
Picklist |
System |
|
account__aln |
nhid_cda__v |
National Healthcare ID |
Text |
Custom |
|
account__aln |
target_cda__v |
Target |
Yes/No |
Custom |
|
account__aln |
prescriber_cda__v |
Prescriber |
Yes/No |
Custom |
|
account__aln |
kol_cda__v |
Key Opinion Leader |
Yes/No |
Custom |
|
account__aln |
investigator_cda__v |
Investigator |
Yes/No |
Custom |
|
account__aln |
speaker_cda__v |
Speaker |
Yes/No |
Custom |
|
address__aln |
status_cda__v |
Status |
Picklist |
System |
|
address__aln |
street_address_1_cda__v |
Street Address 1 |
Formula |
Custom |
|
address__aln |
home_cda__v |
Home |
Yes/No |
Custom |
|
address__aln |
business_cda__v |
Business |
Yes/No |
Custom |
|
address__aln |
billing_cda__v |
Billing |
Yes/No |
Custom |
|
address__aln |
shipping_cda__v |
Shipping |
Yes/No |
Custom |
|
address__aln |
sample_shipping_cda__v |
Sample Shipping |
Yes/No |
Custom |
Map Shape Changes
| Country | State/Province | Code | Description |
|---|---|---|---|
| US | AZ | 85039 | Postal point was deleted |
| US | AZ | 85065 | Postal point was deleted |
| US | AZ | 85073 | Postal point was deleted |
| US | AZ | 85075 | Postal point was deleted |
| US | AZ | 85671 | Postal point was deleted |
| US | AZ | 85720 | Postal point was deleted |
| US | AZ | 85722 | Postal point was deleted |
| US | CA | 91526 | Postal point was deleted |
| US | CA | 94207 | Postal point was deleted |
| US | CA | 94208 | Postal point was deleted |
| US | CA | 94211 | Postal point was deleted |
| US | CA | 94234 | Postal point was deleted |
| US | CA | 94245 | Postal point was deleted |
| US | CA | 94282 | Postal point was deleted |
| US | CA | 94291 | Postal point was deleted |
| US | FL | 33072 | Postal point was deleted |
| US | HI | 96737 | Postal point was converted to postal district |
| US | MO | 63774 | Postal point was converted to postal district |
| US | PA | 15422 | Postal point was converted to postal district |
| US | PA | 15454 | Postal point was converted to postal district |
| US | PR | 00636 | Postal point was deleted |
| US | PR | 00930 | Postal point was deleted |
| US | TX | 77209 | Postal point was deleted |
| US | TX | 78472 | Postal point was deleted |
| US | WA | 98350 | Postal point was converted to postal district |
To access new postal codes, admins must update the status__v field of the appropriate country__aln record to Inactive, save the record, then update the status__v field again to reactivate the country__aln record.
