Align 19R3.1 Production Upgrade (193.1.2) has been delivered to Production and Sandbox Orgs October 18th, 2019

This is to confirm that the Align 19R3.1 production upgrade (193.1.2) has been delivered to production and sandbox orgs on October 18th, 2019.


Territory Management 2.0 in Align

Align is able to assist the transition from Salesforce’s original Territory Management module (TM1.0) to Territory Management 2.0 (TM2.0).

All Veeva CRM customers must migrate to TM2.0 before June 2020. Align introduces functionality to assist in the migration process. The Align capability can be used after TM2.0 is enabled in the corresponding CRM org. It will be possible to enable TM2.0 in Veeva CRM after the CRM 19R3 release.

Veeva recommends reviewing the Salesforce Migration FAQ and Veeva’s Support Article on Territory Management 2.0 before transitioning.

What's new in 19R3.1

Footprint Enhancements

Modeling Footprints

Administrators can create modeling footprints to conveniently group and manage geographies when assigning geographies to territories.

Start and End Dating Geographies in Footprints

Administrators can specify the start and end date of a geography’s assignment to a footprint. This enables more flexibility when managing footprints as geographies can be freely added and removed from a footprint without deleting the footprint_geography__aln record.

CRM Integration Enhancements

Mapping Custom Territory Fields

Align enables admins to map custom fields between Align and Veeva CRM, enabling more versatile connections between the two systems.

This feature requires that the corresponding Veeva CRM org has successfully migrated to Territory Management 2.0 (Available in the CRM 19R3 release).

Rules Engine Enhancements

Using Date Operators in the Rules Engine

Admins can use Date Operators to specify that results must be either more than or less than a certain number of days in order for a result to match the query. This enables more versatile rules that match based on a relative timeframe (for example, matching all accounts visited in the last 90 days) rather than based on an exact date that must be manually updated each time the rule is run.

The full release notes can be found here.


Please sign in to leave a comment.