Release Schedule
| Name | Description | Date |
|---|---|---|
| Sandbox Update | All 1.39.X installs in sandboxes will receive the update automatically | 4/20/2021 |
| Production Update | All 1.39.X installs in production orgs will receive the update automatically | 4/27/2021 |
Improvements & Fixes
Version 1.39.15 contains the following improvements and fixes.
- Fixed an issue where changing the configuration of a funnel field stage from a formula to non-formula was not being saved properly.
- Implemented improvement to optimize response processing to mitigate the risk of record lock errors occurring.
- Fixed UI validation issue on the Reactivation configuration page where the delay field on Score and Active Status Reactivation should not allow fractions of a minute. Users with fractions will be forced to update to a whole number next time they edit either of these configurations.
- If a customer application modifies the lead/contact status or a sync field during their before-trigger, and their before-trigger runs after ours, our trigger will not see the change to the status or sync field, and thus will not sync to the CampaignMember. To handle this situation, we’ve implemented a feature that allows movement of our test for status or sync field changes from the before-trigger to the after-trigger. Customers that need to utilize this feature should contact your Full Circle account manager for help implementing.
- Implemented improvement that mitigates the risk of a large number of queueable Apex jobs being executed in a busy org where there are no Scheduled Apex slots available.
- Fixed a rare issue when a campaign has two different Member Status Values with the same name but different capitalizations. This fix makes response detection case sensitive.
Comments
0 comments
Please sign in to leave a comment.