About the 19R3.1 Release

This topic provides information about the Veeva Align 19R3.1 release, including important dates, webinar information, and release announcements.

All dates listed are subject to change.

Dates to Remember

  • October 11 – Sandbox release, release notes made available
  • October 18 – General Release to all orgs

Announcements

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. Align introduces functionality to assist in the migration process. This Align functionality 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.

This Align functionality automatically activates when Align is pushed to a CRM org with TM2.0 enabled. CRM admins should not enable TM2.0 until the CRM 19R3 release.

Using Align to Transition to Territory Management 2.0

Before synchronizing Align to a TM2.0 CRM org, perform the following process in CRM:

  1. Create a new field on the Territory2 object with the following attributes:

    • Type – Text
    • Field Label – Master Align Id
    • Field Name – Master_Align_Id_vod
    • Length – 36
  2. Delete all Territory2Model records in the org that were not created by Align.
  3. Navigate to Align.
  4. Navigate to the Align Integrations page in the Integrations tab.
  5. Select the Gear button for the appropriate org in the Veeva CRM section.
  6. Select View Field Map.
  7. Select the Align Objects tab.
  8. Navigate to Territory Fields.
  9. Select Describe & Edit to retrieve the field mappings to the Territory2 object.
  10. Select Save.

When pushing from Align to a CRM org with TM2.0 enabled, the confirmation dialog of the push displays the names of the Salesforce TM2.0 objects that will receive data.

TM1.0 Push Modal TM2.0 Push Modal

When initially pushing to a TM2.0 enabled org, Align creates a Territory2Model record named VeevaAlign and pushes the following data into that model:

  • Territory2 – The territory tree
  • UserTerritory2 – The user or users assigned to each territory
  • ObjectTerritory2Association – The list of accounts aligned to the territory

All Territory2 records require a type. Align creates a type called VeevaAlign and assigns this to all Territory2 records created by the push.

Starting with the initial push from Align to TM2.0 objects in CRM, all integration statuses are tracked using the integration_status_2__aln object in Align. The integration_status__aln object will be deprecated and removed once all Align customers have migrated to TM2.0.

When a VeevaAlign model exists in CRM, all changes from Align are pushed to this model while it is in the Planning or Active state. Align users cannot create additional models in CRM.

Do not archive the VeevaAlign model.

To use modeling capabilities, use the Modeling tab in Align to create and publish models. The results of published models are automatically pushed to the VeevaAlign model in CRM when a CRM push operation is executed.

The initial state of the Territory2Model created by Align in CRM is Planning. It must be activated before the user and account assignments take effect in CRM.

Activating a Territory2Model

Once data from Align synchronizes to the VeevaAlign Territory2Model record, CRM admins can activate the model to implement the assignments:

  1. Navigate to Feature Settings > Sales > Territories > Territory Models in the Setup menu of the appropriate CRM org.
  2. Select the VeevaAlign Territory2Model record.
  3. Select View Hierarchy.
  4. Select Activate.

What's New in 19R3.1

The Align19R3.1 release includes several new features as well as User Visible and Behavior Changes.

Our release notes offer brief, high-level descriptions of enhancements and new features. Configuration is available by selecting the feature name.

New Objects, New Fields, and Known Issues are also included.

Features

Footprint Enhancements

Modeling Footprints

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

When importing a production project into a modeling project, all footprints and associated footprint assignments automatically import as corresponding model footprint records.

Additionally, any changes made to modeling footprints or footprint assignments override corresponding production records when the project is published.

For example, Larry Lakes is an admin working on a modeling project. This modeling project contains geography assignments, footprints, and territories. When Larry publishes the model to production, all footprints and footprint assignments also publish to production. Later, when it is time for Larry to create a new modeling project, he imports the current production project into modeling. All production footprints and footprint assignments automatically import into modeling records.

 

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.

For example, Larry Lakes is an admin working on two footprints, Footprint A and Footprint B. Larry decides that one of the geographies in Footprint A would be better suited in Footprint B. Larry end dates the geography’s assignment to Footprint A and adds it to Footprint B. Since the assignment was end dated rather then deleted, the history of the geography’s assignment to Footprint A remains.

To end date a geography’s assignment to a footprint:

  1. Navigate to the appropriate footprint__aln or footprint_model__aln record.
  2. Edit the appropriate Footprint Geography record.
  3. Select an appropriate start and end date.

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.

User Visible and Behavior Changes

Most new features require some configuration, however users are able to view the following changes immediately:

Territory Assignment

  • Footprints are now supported in Modeling. See Footprints for more information.

New Objects

The list below contains all new objects added in Veeva Align 19R3.1.

Name

Label

Description

footprint_model__aln

Model Footprint

Defines modeling footprints

integration_status_2__aln

Integration Status 2

Tracks the status of the associated record in the integration process

territory_footprint_model__aln

Model Territory Footprint

Defines assignments of modeling footprints to model territories

footprint_geography_model__aln

Model Footprint Geography

Defines the assignments geographies to model footprints

New Fields

The list below contains all fields added in Veeva Align 19R3.1. The fields are organized by object.

Object

Field Name

Field Label

Description

Type

footprint_geography__aln

end_date__aln

End Date

The end of a geography’s assignment to a footprint

Date

footprint_geography__aln

start_date__aln

Start Date

The beginning of a geography’s assignment to a footprint

Date

footprint_model__aln

external_ID_vod

External ID

External ID

Text

footprint_model__aln

production_record__aln

Production Record

References the corresponding production record

Lookup

footprint_model__aln

project__aln

Project

References the project associated with the footprint

Lookup

footprint_geography_model__aln

end_date__aln

End Date

The end of a geography’s assignment to a footprint

Date

footprint_geography_model__aln

external_ID_vod

External ID

External ID

Text

footprint_geography_model__aln

footprint_model__aln

Model Footprint

References the footprint the assignment belongs to

Lookup

footprint_geography_model__aln

production_record__aln

Production Record

References the corresponding production record

Lookup

footprint_geography_model__aln

start_date__aln

Start Date

The beginning of a geography’s assignment to a footprint

Date

integration_status_2__aln

account__aln

Account

The associated account

Lookup

integration_status_2__aln

crm_delete_datetime__aln

CRM Delete Datetime

Records confirmation from CRM that the record was deleted

DateTime

integration_status_2__aln

crm_insert_datetime__aln

CRM Insert Datetime

Records confirmation from CRM that the record was inserted

DateTime

integration_status_2__aln

crm_record_id__aln

CRM Record Id

ID of the record in CRM

String

integration_status_2__aln

last_sent_datetime__aln

Last Sent Datetime

When the record was last sent to CRM

DateTime

integration_status_2__aln

process__aln

Process

The name of the process responsible for the integration

String

integration_status_2__aln

product__aln

Product

The associated product

Lookup

integration_status_2__aln

record_status__aln

Record Status

Status of the record

String

integration_status_2__aln

roster_member__aln

Roster Member

Associated roster member

Lookup

integration_status_2__aln

target_system__aln

Target System

Name of the target system

String

integration_status_2__aln

territory__aln

Territory

Associated territory record

Lookup

territory_footprint_model__aln

external_ID_vod

External ID

External ID

Text

territory_footprint_model__aln

footprint_model__aln

Model Footprint

References the footprint the assignment belongs to

Lookup

territory_footprint_model__aln

production_record__aln

Production Record

References the corresponding production record

Lookup

territory_footprint_model__aln

territory_model__aln

Model Territory

References the corresponding model territory

Lookup

19R3.1 Known Issues

Footprints

Issue Description

Issue Number

Footprints cannot be created. This will be resolved in the 19R3.1 Production Release.

ALN-17793