What's New in 21R2.2
The Align 21R2.2 release includes brief, high-level descriptions of enhancements and new features.
Announcements
Deprecating the &vaultsess URL Parameter
Beginning in 21R3.2 (currently scheduled for January 6, 2022), Vault is disallowing use of the &vaultsess URL parameter used by the Align Scheduler.
To update scheduled jobs accordingly:
- Navigate to the appropriate job.
- Remove the &vaultsess=${Session.id} parameter from the URL.
- Select the Post Session Credentials via Form Data with Key “Session.id” check box.
- Select Save.
These required updates can be made anytime and will be implemented automatically by Veeva Services for customers with active engagements with Align professional services.
See Creating a Scheduled Job for more information.
User Visible and Behavior Changes
Align Settings
- The align_settings_model__aln object was added in preparation for a future release. Admins should not create any records against this object.
- The Align Settings tab was relabeled Production Settings
-
For consistency purposes across all instance of Align, the picklist values for the Challenge Reasons settings were updated based on when the Align instance was created.
These picklist values automatically display as available for selection in Territory Feedback unless they are excluded via Context-Sensitive Challenge Reasons.
- For instances created after June 2020, the following values were added:
- access__c – Has a label of Access (Deprecated)
- add_account_to_territory__c – Has a label of Add Account to Territory (Deprecated)
- no_longer_in_practice__c – Has a label of No Longer in Practice (Deprecated)
- For instances created before June 2020, the following values were added
- good_access__c
- high_priority__c
- The Audit Trail feature is now enabled by default for Align Settings
- Automated Feedback Handling is now enabled if the automated_feedback_handling__aln setting is either null or enabled. This ensures feedback is always processed when a project is published unless Automated Feedback Handling is explicitly disabled.
Account Assignment
-
The Calculate Rollups button was relabeled Recalculate Territory Data and can now be selected in both model and production field forces, regardless if an MC Cycle is associated with the field force
Modeling Production -
Selecting Recalculate Territory Data now displays the following modals based on if the field force is a modeling or a production field force:
Modeling Production -
Selecting the Recalculate Territory Data button now creates a corresponding process_task__aln record that admins can use to track the progress of the recalculation
Modeling
- Importing field_force_product_model__aln records now also automatically creates corresponding territory_product_model__aln records
Territory Feedback
- The end_date__aln field of account_territory__aln records added to a territory via Keep Account or Add Account challenges now match the end date of the corresponding territory, rather than the end date of the associated cycle plan. This enables accounts added via Territory Feedback to remain in a user’s territory across multiple cycles.
Features
In the CRM 22R1 release (currently scheduled for April 2022), CRM Standard Metrics will be mandatory for all CRM orgs. Align supports syncing information to and from these fields for continued use by Align-mastered roster members.
Map Shape Changes
Country | State/Province | Code/Locality | Text |
---|---|---|---|
Canada | BC | Big Creek | Postal Locality was created |
Canada | QC | Sainte-Agathe-Nord | Postal Locality was deleted |
US | AZ | 85288 | Postal point was added |
US | AZ | 85923 | Postal point was converted to postal district |
US | CO | 81128 | Postal point was converted to postal district |
US | CO | 81221 | Postal point was converted to postal district |
US | FL | 33662 | Postal point was deleted |
US | FL | 33663 | Postal point was deleted |
US | IA | 50431 | Postal point was converted to postal district |
US | IA | 50631 | Postal point was converted to postal district |
US | IL | 61539 | Postal point was converted to postal district |
US | MA | 02266 | Postal point was deleted |
US | ME | 04063 | Postal point was converted to postal district |
US | MI | 48874 | Postal point was converted to postal district |
US | MN | 55460 | Postal point was deleted |
US | MO | 63839 | Postal point was converted to postal district |
US | MO | 64857 | Postal point was converted to postal district |
US | NJ | 07842 | Postal point was converted to postal district |
US | NJ | 07977 | Postal point was converted to postal district |
US | NM | 87061 | Postal point was converted to postal district |
US | NM | 87072 | Postal point was converted to postal district |
US | NM | 87311 | Postal point was converted to postal district |
US | NM | 87347 | Postal point was converted to postal district |
US | NM | 87512 | Postal point was converted to postal district |
US | NM | 87517 | Postal point was converted to postal district |
US | NM | 87569 | Postal point was converted to postal district |
US | NM | 87753 | Postal point was converted to postal district |
US | NM | 88036 | Postal point was converted to postal district |
US | NM | 88038 | Postal point was converted to postal district |
US | NM | 88051 | Postal point was converted to postal district |
US | OH | 45698 | Postal point was converted to postal district |
US | OR | 97258 | Postal point was deleted |
US | PA | 16230 | Postal point was converted to postal district |
US | PA | 17887 | Postal point was converted to postal district |
US | SD | 57639 | Postal point was converted to postal district |
US | TX | 79846 | Postal point was converted to postal district |
US | WA | 98280 | Postal point was converted to postal district |
US | WV | 25644 | Postal point was converted to postal district |
US | WV | 26563 | Postal point was converted to postal district |