Managed Package release notes v2.20x

New A GTM Team custom object for assignment data  ·  Salesforce Integration

• The package installs a GTM Team custom object related to the GTM object, carrying the assignment start and end dates, the assigned user, the assignment type, the role, an inherited flag, and an external ID so repeat upserts update a record rather than duplicate it.

• Assignment data has until now landed on the standard Salesforce Account Team, which Salesforce clears when the account owner changes. A dedicated object holds that data instead, and can carry assignment detail the Account Team has no room for.

• Upgrading an existing org adds the object and leaves your Account Team behavior unchanged.

Note

No Fullcast job writes to the GTM Team object in this version.

Enhancement Tag fields on a related Policy Status record from routing  ·  Routing

• In Default users & record tagging, the Field list now offers fields from the related Policy Status object as well as the primary routed object. Each one carries its object name, for example Account.Industry and PolicyStatus.Status__c, so you can tell the two apart.

• When the rule runs, it writes your chosen value to that field on the matching Policy Status record. Updates to fields on the primary record are unchanged.

• A record with no related Policy Status skips the tagging step and routes as normal. A value that does not fit the field type is logged and routing still completes.

• Fields you cannot edit, such as formula and auto-number fields, are left out of the list.

Improvement Routing invalid queue ID error  ·  Routing

• Leads were not being assigned due to an Invalid Queue ID error when routing to a queue. The system now correctly recognizes configured queue IDs and routes leads as intended.

Enhancement Holdout policy custom object and schedule flows  ·  Routing

• The Salesforce Lightning Web components now provides a visual indicator of holdouts and their expiration dates.

• You can use Salesforce schedule flows to clean up expired holdouts which replaces the scheduler.

• Refer to platform release notes V.3.0.5 (07 November 2025) for more information on Holdout policy updates.

Improvement Wildcard operator not grabbing all policies  ·  Routing

• The wildcard operator (*) for the input value, InputVal3, was not grabbing the policies correctly for all records in a transaction that start with the same tag operator in the bulk execution.

Improvement BMA fields for lead routing not updating  ·  Routing

• The input value, InputVal3, was not updating the BMA fields on lead routing correctly.

Improvement Queueable job reduction  ·  Salesforce Integration

• To reduce the number of queueable jobs, the GTM trigger handling action during the territory routing and round robin are being skipped.

  Note

  This does not impact the current routing queue execution.

Improvement API version update  ·  Salesforce Integration

• The API version for Apex classes, Apex triggers, and visual force pages have been upgraded to API 60.0.

Enhancement Concurrent API request limit updates  ·  Salesforce Integration

• Users were experiencing concurrent API request limit issues within Salesforce due to the average runtime of the Fullcast Managed Package taking too long. A custom metadata, Execute Territory Routing ASync, was added that allows you to execute the Territory Routing Response process asynchronously to help mitigate the request limit issues.

  Note

  By default Execute Territory Routing ASync is set to false (process runs synchronously) unless you change it to true (process runs asynchronously). Only true or false are supported to define the execution mode.

Improvement GTM Leaf Information failing  ·  Salesforce Integration

• The GTM Leaf Information was failing due to too many jobs running at the same time.