What's New in 20R3.3
The Align 20R3.3 release includes the following User Visible and Behavior Changes.
Our release notes offer brief, high-level descriptions of enhancements and new features.
Announcements
Updates to Align Release Versioning
Align’s release versioning now matches both CRM and Vault release versioning, while maintaining the same two-month release cycle.
The current version that will be deployed to sandboxes on February 11th and to production environments on February 18th is 20R3.2. The April release will be 21R1.0.
See About Align Releases for more information.
Updated Assignment Rules Engine
A version of the Assignment Rules Engine with improved performance is available in a beta release. At this time, this feature can only be enabled in sandbox environments. Veeva will reach out to customers with high data volumes to participate in the beta program.
Migration to High Volume Objects
The Vault 20R3 Release includes support for High Volume Objects (HVOs). Align uses HVO for several objects to improve the performance of key processes, including committing assignment previews, importing and publishing explicit assignments between modeling and production, and pushing data to CRM. HVOs also improve the performance of manually data loading explicit assignments into production and model territories.
Sandbox migrations will begin the week of March 29, 2021. Once sandbox migrations are complete, production migrations will occur over weekends. Veeva will notify Align Vault Owners via email one month in advance of the scheduled migration dates for sandbox and production environments.
The following Align objects will migrate to Vault’s HVO model:
- account_territory__aln – Stores production account-to-territory assignments
- integration_status__aln – Stores send and delete statuses between Align and CRM for Territory Management 1.0
- integration_status_2__aln – Stores send and delete statuses between Align and CRM for Territory Management 2.0
The account_territory_model__aln object was removed from the current list of planned HVO migrations.
Sandbox migrations are managed by Veeva and begin on March 29, 2021. Production migrations follow after all sandbox migrations are complete.
What to Expect and Actions Required
Downtime is not expected during the migration, but customers should expect a longer maintenance window if heavy data-usage (modifying more than 100k records) on the migrated objects occurs during the migration.
All functionality is maintained after the migration, with the following exceptions:
- Sharing Rules
- Lookup FIelds
- Multivalue Picklists
- The search bar in the Business Admin menu – Filters are recommended as an alternative to this functionality
Data within these objects is preserved during the migration process, including unique identifiers, object names, and custom reports. Previously created Saved Views on these objects will be removed. Users can recreate these Saved Views after the migration is complete.
To prepare for the migration, customers should perform the following actions:
- Upgrade integrations using API calls against HVO objects to Vault API version 20.3
- Remove all of the following from the HVO objects:
- Sharing Rules
- Lookup Fields
- Multivalue Picklists
The country__aln lookup field on the Account_Territory__aln object will be converted automatically to an Object field type. Existing data will be migrated. The new field will have a formula-derived default value that evaluates to the Country of the associated Territory.
Territory Management 2.0 in Align
Align is able to assist the transition from Salesforce’s original Territory Management Salesforce module (TM1.0) to Territory Management 2.0 (TM2.0). All Veeva CRM customers must migrate to TM2.0 before June 2021.
See Territory Management 2.0 in Align for more information.
User Visible and Behavior Changes
Users are able to view the following changes immediately:
General
- The top navigation bar is now preserved when opening the detail view for records in a new tab
Targeting Feedback
- Error messages in Targeting Feedback that originated from triggers now localize to the user’s language instead of the language of the Align Integration user.
Map Shape Changes
Country |
State/Province |
Code |
Notes |
---|---|---|---|
US |
CA |
90899 |
Postal point was deleted |
US |
CA |
92878 |
Postal point was converted to postal district |
US |
CA |
93606 |
Postal point was converted to postal district |
US |
CA |
93624 |
Postal point was converted to postal district |
US |
CA |
93673 |
Postal point was converted to postal district |
US |
CA |
95225 |
Postal point was converted to postal district |
US |
CA |
95254 |
Postal point was converted to postal district |
US |
CA |
95319 |
Postal point was converted to postal district |
US |
CA |
96110 |
Postal point was converted to postal district |
US |
CO |
80251 |
Postal point was deleted |
US |
CO |
80646 |
Postal point was converted to postal district |
US |
CT |
6814 |
Postal point was deleted |
US |
CT |
6816 |
Postal point was deleted |
US |
CT |
6817 |
Postal point was deleted |
US |
DC |
56971 |
Postal point was added |
US |
IA |
50102 |
Postal point was converted to postal district |
US |
IA |
50652 |
Postal point was converted to postal district |
US |
IA |
50673 |
Postal point was converted to postal district |
US |
IA |
52752 |
Postal point was converted to postal district |
US |
ID |
83230 |
Postal point was deleted |
US |
ND |
58335 |
Postal point was converted to postal district |
US |
NY |
10519 |
Postal point was converted to postal district |
US |
NY |
10953 |
Postal point was converted to postal district |
US |
PA |
15532 |
Postal point was converted to postal district |
US |
PA |
15553 |
Postal point was converted to postal district |
US |
PA |
15695 |
Postal point was converted to postal district |
US |
PA |
15727 |
Postal point was converted to postal district |
US |
PA |
15847 |
Postal point was converted to postal district |
US |
PA |
15925 |
Postal point was converted to postal district |
US |
PA |
15959 |
Postal point was converted to postal district |
US |
PA |
15962 |
Postal point was converted to postal district |
US |
PA |
16024 |
Postal point was converted to postal district |
US |
PA |
16416 |
Postal point was converted to postal district |
US |
PA |
16663 |
Postal point was converted to postal district |
US |
PA |
16733 |
Postal point was converted to postal district |
US |
PA |
17235 |
Postal point was converted to postal district |
US |
PA |
18084 |
Postal point was converted to postal district |
US |
SD |
57621 |
Postal point was converted to postal district |
US |
VT |
5840 |
Postal point was converted to postal district |
US |
WI |
54857 |
Postal point was converted to postal district |