| Name | Description | Date |
| Sandbox Update | For customers enrolled in automatic updates, Sandbox environments will be updated Thursday, June 4, 2026 at 10:00 pm PDT | 6/04/2026 |
| Production Update | For customers enrolled in automatic updates, Production environments will be updated Thursday, June 11, 2026 at 10:00 pm PDT. | 6/11/2026 |
Fixes
Campaign Member History Button
Resolved an issue where clicking the packaged See History button on a Campaign Member record would return an error indicating that the Visualforce page could not be found. The button URL has been updated to use a page reference, ensuring the Campaign Member History page opens correctly without requiring a custom workaround button.
Who does it benefit?
All customers who have enabled the Campaign Member History feature introduced in Release 1.54.
What problem does this fix solve?
The packaged See History button was referencing the Visualforce page without the managed package namespace prefix, causing Salesforce to be unable to locate the page. Customers were required to create a custom button as a workaround. The button now uses a page reference, resolving the issue for all customers.
Enablement Instructions
This fix does not require enablement.
Maintenance
Salesforce Summer '26 Compatibility Updates
As part of our ongoing commitment to platform compatibility, we've made two updates to ensure our products continue to work seamlessly following Salesforce's Summer '26 release.
[UPDATE] Updated Custom Funnels configuration to remove a dependency on getSessionId, which Salesforce is deprecating for managed packages in the Summer '26 release.
[UPDATE] Updated the file download method used throughout the application to comply with Salesforce Summer '26 platform changes.
Who does it benefit?
All Full Circle Response Management customers.
What problem does these updates solve?
Salesforce is introducing platform-level changes in Summer '26 that would have broken both the Custom Funnels configuration tab state management and the file download functionality within the application. These updates ensure we remain fully compatible with the Summer '26 release.
Enablement Instructions
These updates do not require enablement.
Comments
0 comments
Article is closed for comments.