What's New in Align 25R2.0

The 25R2.0 release includes features for:

Release Dates

  • Sandbox Release - August 7, 2025
  • Production Release - August 21, 2025

New Fields are also included.

Managing Align Territories – Available on Browser

Align operational users can manage and maintain territory hierarchies directly within Vault CRM, enabling managing those territories and their related records. This streamlines territory management by providing a single location for these processes.

Managing Field Forces – Available on Browser

Field forces are a collection of Align territories sharing a common focus and are grouped together for reporting purposes. Align operational users can create and define field forces, streamlining the overall territory management process.

Managing Geographies in Align – Available on Browser

Align operational users can automatically generate geography records for supported countries, then use those geographies to manage geography-to-territory assignments, providing greater control and flexibility when defining territory alignments.

Managing Footprints in Align – Available on Browser

Footprints are groupings of geographies that Align operational users can use to assign entire groups of geographies to one or more territories at once, instead of individually. This reduces the setup required when assigning geographies to territories and helps maintain assignment consistency.

Managing Product Assignments in Align – Available on Browser

Align operational users can manage and maintain product assignments for field forces and territories. This enables control over which products are associated with a specific territory, ensuring a clear and accurate overview of product responsibilities. Product assignments for a field force can also automatically cascade down to all associated territories, simplifying product management.

Assigning Roster Members in Align – Available on Browser

Align operational users can manage their rosters directly within Vault CRM using a dedicated Roster Management tab to create, edit, and delete roster members in. Users can also manage roster members' territory assignments, ensuring roster members correctly associate with their territories.

Using Account Assignment Rules in Align – Available on Browser

Align Operational Users can create and manage rules to automatically assign accounts to Align territories. This enables users to control how accounts are distributed, run assignment rules, preview the results, and then commit those changes.

Manually Managing Account Assignments in Align – Available on Browser

Align Operational Users can directly assign accounts to Align territories by creating explicit account assignments. Additionally, users can also create account exclusion records that prevent a certain account from ever being assigned to a particular Align territory or field force, improving flexibility in the account assignment process.

Handling Account Merges in Align – Available on Browser

Account merges are reflected in Vault CRM through regular imports. Record conflicts can occur during an import when values from external ID fields from a losing account__v are copied into winning accounts. The conflict arises from the same external ID being used across two account__v records for which Align is not supported.

Managing Users in Align – Available on Browser

Align operational users can create and manage Vault CRM users via aln_roster_member__v records within Align, simplifying the alignment process. Align operational users can perform the following tasks via User Management:

Managing Application Profiles in Align – Available on Browser

Application profiles enable admins to create groups of users that all share a similar set of application configurations. Align operational users can import application profiles and assign them to functional profiles as part of managing roster members, then push those assignments back to the corresponding user__sys record.

Assigning Application Roles to Individual Roster Members – Available on Browser

To support individual business requirements for users who require additional permissions than their assigned functional profile, Align operational users can assign application roles directly to individual roster members.

Managing Groups with Functional Profiles – Available on Browser

Align operational users can manage group membership in Align via associations with functional profiles.

End-Dating Users in Align – Available on Browser

Roster members mastered by Align can be end-dated in Align and be appropriately deactivated in CRM via a push, enabling Align operational users to handle a user leaving their organization from their Align roster member record, eliminating the need to manually deactivate a user after the fact.

Using Functional Profiles – Available on Browser

Functional profiles group together Security Profiles and Application Roles associated with job functions in Vault CRM. Align operational users can use functional profiles to automate the assignment of permissions to users, enabling quick configuration of Vault CRM features.

Managing Layout Profiles in Align – Available on Browser

Layout profiles control the layouts of various objects and object types. Align operational users can import layout profiles, control the assignment of layout profiles for each roster member, and push those assignments.

Managing User Security Policies in Align – Available on Browser

Security policies 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..

25R2.0 Feature Enablement and Availability

The following table provides an explanation of feature enablement and user impact.

Vault CRM Feature Availability and Enablement

Feature

User
Visible
Change

Configuration
Required

Browser

CRM Desktop
(Windows)

iPad

iPhone

Managing Align Territories – Available on Browser

No

Yes

Managing Field Forces – Available on Browser

No

Yes

Managing Geographies in Align – Available on Browser

No

Yes

Managing Footprints in Align – Available on Browser

No

Yes

Managing Product Assignments in Align – Available on Browser

No

Yes

Assigning Roster Members in Align – Available on Browser

No

Yes

Using Account Assignment Rules in Align – Available on Browser

No

Yes

Manually Managing Account Assignments in Align – Available on Browser

No

Yes

Handling Account Merges in Align – Available on Browser

No

Yes

Managing Users in Align – Available on Browser

No

Yes

Managing Application Profiles in Align – Available on Browser

No

Yes

Assigning Application Roles to Individual Roster Members – Available on Browser

No

Yes

Managing Groups with Functional Profiles – Available on Browser

No

Yes

End-Dating Users in Align – Available on Browser

No

Yes

Using Functional Profiles – Available on Browser

No

Yes

Managing Layout Profiles in Align – Available on Browser

No

Yes

Managing User Security Policies in Align – Available on Browser

No

Yes

New Fields

The table below contains all fields added in Align 25R2.0. The fields are organized by object.

Object

Field Name

Field Label

Description

Type

mc_cycle__v aln_clone_source__v Clone Source Source cycle. Populated if cycle was cloned. Object
mc_cycle__v aln_country__v Country n/a Object
mc_cycle__v aln_cycle_capacity__v Cycle Capacity n/a Number
mc_cycle__v aln_days_in_cycle__v Days In Cycle n/a Number
mc_cycle__v aln_days_off_cycle__v Days Off Cycle n/a Number
mc_cycle__v aln_end_datetime__v End Date/Time n/a DateTime
mc_cycle__v aln_field_force__v ADD Field Force n/a Object
mc_cycle__v aln_field_force_model__v ADD Field Force Model n/a Object
mc_cycle__v aln_legacy_align_id__v Legacy Align Id n/a Text
mc_cycle__v aln_lower_utilization_threshold__v Lower Utilization Threshold n/a Number
mc_cycle__v aln_start_datetime__v Start Date/Time n/a DateTime
mc_cycle__v aln_support_child_account_targets__v Support Child Account Targets n/a Picklist
mc_cycle__v aln_territory_assigned_accounts__v Territory Assigned Accounts n/a Number
mc_cycle__v aln_territory_assigned_targets__v Territory Assigned Targets n/a Number
mc_cycle__v aln_territory_capacity__v Territory Capacity n/a Number
mc_cycle__v aln_upper_utilization_threshold__v Upper Utilization Threshold n/a Number
mc_cycle_channel__v aln_channel_template__v Channel Template n/a Object
mc_cycle_channel__v aln_channel_template__v MC Cycle Channels n/a Object
mc_cycle_channel__v aln_clone_source__v Clone Source Source cycle. Populated if cycle was cloned. Object
mc_cycle_channel__v aln_daily_activity_goal__v Daily Activity Goal n/a Number
mc_cycle_channel__v aln_default_goal__v Default Goal Provides field users with a default goal value whenever they add a target via Feedback. ADD Field users will still be able to modify this during feedback. Number
mc_cycle_channel__v aln_default_max_goal__v Default Max Goal Sets a maximum possible goal value for field users whenever they attempt to add a target via Feedback. ADD Field users will not be able to adjust the goal higher than this value during feedback. Number
mc_cycle_channel__v aln_legacy_align_id__v Legacy Align Id n/a Text
mc_cycle_plan__v aln_activity_goals__v Activity Goals n/a Number
mc_cycle_plan__v aln_align_rule_id__v Align Rule ID n/a Text
mc_cycle_plan__v aln_end_datetime__v End Date/Time n/a DateTime
mc_cycle_plan__v aln_legacy_align_id__v Legacy Align Id n/a Text
mc_cycle_plan__v aln_start_datetime__v Start Date/Time n/a DateTime
mc_cycle_plan__v aln_targeting_id__v Targeting ID n/a Text
mc_cycle_plan__v aln_territory__v Territory n/a Object
mc_cycle_plan__v aln_territory_assigned_accounts__v Territory Assigned Accounts n/a Number
mc_cycle_plan__v aln_territory_model__v Territory Model n/a Object
mc_cycle_plan_channel__v aln_align_rule_id__v Align Rule ID n/a Text
mc_cycle_plan_channel__v aln_channel_label__v Channel Label n/a Text
mc_cycle_plan_channel__v aln_channel_segmentation__v Channel Segmentation n/a Text
mc_cycle_plan_channel__v aln_channel_segmentation_clone_source__v Channel Segmentation (Clone Source) Label of the originating channel group from the source cycle plan. Applicable if cycle was cloned. Text
mc_cycle_plan_channel__v aln_feedback_activity_goal__v Feedback Activity Goal n/a Number
mc_cycle_plan_channel__v aln_legacy_align_id__v Legacy Align Id n/a Text
mc_cycle_plan_channel__v aln_segment_change__v Segment Change Indicates if originating channel group differs with that from the source cycle plan. Applicable if cycle was cloned. Yes/No
mc_cycle_plan_channel__v aln_source_goal__v Source Goal Channel goal from the source cycle plan. Applicable if cycle was cloned. Number
mc_cycle_plan_channel__v aln_targeting_id__v Targeting ID n/a Text
mc_cycle_plan_channel__v aln_targeting_rule_channel_group__v Targeting Rule Channel Group Populated if record was generated by targeting rule. Represents originating channel group. Object
mc_cycle_plan_product__v aln_align_rule_id__v Align Rule ID n/a Text
mc_cycle_plan_product__v aln_channel_label__v Channel Label n/a Text
mc_cycle_plan_product__v aln_feedback_activity_goal__v Feedback Activity Goal n/a Number
mc_cycle_plan_product__v aln_legacy_align_id__v Legacy Align Id n/a Text
mc_cycle_plan_product__v aln_product_segmentation__v Product Segmentation n/a Text
mc_cycle_plan_product__v aln_product_segmentation_clone_source__v Product Segmentation (Clone Source) Label of the originating product group from the source cycle plan. Applicable if cycle was cloned. Text
mc_cycle_plan_product__v aln_segment_change__v Segment Change Indicates if originating product group differs with that from the source cycle plan. Applicable if cycle was cloned. Yes/No
mc_cycle_plan_product__v aln_source_goal__v Source Goal Product goal from the source cycle plan. Applicable if cycle was cloned. Number
mc_cycle_plan_product__v aln_targeting_id__v Targeting ID n/a Text
mc_cycle_plan_product__v aln_targeting_rule_product_group__v Targeting Rule Product Group Populated if record was generated by targeting rule. Represents originating product group. Object
mc_cycle_plan_summary__v aln_legacy_align_id__v Legacy Align Id n/a Text
mc_cycle_plan_target__v aln_aggregate_goal__v Aggregate Goals n/a Text
mc_cycle_plan_target__v aln_align_rule_id__v Align Rule ID n/a Text
mc_cycle_plan_target__v aln_challenge_reason__v Challenge Reason This field holds the reasons for which a user logged a challenge in Feedback Picklist
mc_cycle_plan_target__v aln_challenge_status__v Challenge Status n/a Picklist
mc_cycle_plan_target__v aln_challenge_type__v Challenge Type n/a Picklist
mc_cycle_plan_target__v aln_challenged__v Challenged n/a Yes/No
mc_cycle_plan_target__v aln_end_datetime__v End Date/Time n/a DateTime
mc_cycle_plan_target__v aln_feedback_provider__v Feedback Provider n/a Text
mc_cycle_plan_target__v aln_legacy_align_id__v Legacy Align Id n/a Text
mc_cycle_plan_target__v aln_source__v Source n/a Picklist
mc_cycle_plan_target__v aln_start_datetime__v Start Date/Time n/a DateTime
mc_cycle_plan_target__v aln_targeting_id__v Targeting ID n/a Text
mc_cycle_product__v aln_clone_source__v Clone Source Source product. Populated if cycle was cloned. Object
mc_cycle_product__v aln_default_goal__v Default Goal Provides field users with a default goal value whenever they add a target via Feedback. ADD Field users will still be able to modify this during feedback. Number
mc_cycle_product__v aln_default_max_goal__v Default Max Goal Sets a maximum possible goal value for field users whenever they attempt to add a target via Feedback. ADD Field users will not be able to adjust the goal higher than this value during feedback. Number
mc_cycle_product__v aln_detail_priority__v Detail Priority n/a Number
mc_cycle_product__v aln_legacy_align_id__v Legacy Align Id n/a Text
product__v aln_vcountry__v Country n/a Object
product__v aln_vcountry__v Products n/a Object
product_metrics__v aln_data_date__v Data as of Date n/a DateTime
product_metrics__v aln_period_length__v Period Length in Days n/a Number
vcountry__v aln_primary_time_zone__v Primary Time Zone n/a Picklist
vcountry__v aln_shape_identifier__v Shape Identifier Used by the Geo Shape Generator to determine which shape an address record belongs to. Values represent the API names of Text fields on the Address object (e.g. postal_code__aln). Picklist