Managed Package v2.20x releases are for enhancements and various minor bug fixes that integrate with Salesforce. You can manually install Managed Package updates to your instance of Fullcast.
Managed Package 2.207 (02 March 2026)
Routing invalid queue ID error
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.
Managed Package 2.204 (17 November 2025)
Holdout policy custom object and schedule flows
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.
Managed Package 2.203 (10 September 2025)
Wildcard operator not grabbing all policies
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.
Managed Package 2.202 (22 August 2025)
BMA fields for lead routing not updating
The input value,
InputVal3, was not updating the BMA fields on lead routing correctly.
Managed Package 2.201 (02 July 2025)
Queueable job reduction
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.
API version update
The API version for Apex classes, Apex triggers, and visual force pages have been upgraded to API 60.0.
Managed Package 2.200 (16 June 2025)
Concurrent API request limit updates
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.
GTM Leaf Information failing
The GTM Leaf Information was failing due to too many jobs running at the same time.