Release Schedule
| Name | Description | Date |
|---|---|---|
| Sandbox Update | All {{rm_current_version}} installs in Sandboxes will receive the update automatically | 9/29/2020 |
| Production Update | All {{rm_current_version}} installs in production orgs will receive the update automatically | 10/6/2020 |
Improvements & Fixes
Version 1.37.6 contains the following improvements and fixes.
- In some edge case scenarios, asynchronous scoring doesn't complete during the first try and would get rerun after 24 hours. It now gets rerun after just a few minutes.
- Fixed an issue where Active Status Reactivation was overwriting values on fields that were configured to populate only if blank.
- Fixed the "Back" button on the New Opportunity Override lightning component so that it returns the user to the expected record, form or page.
- Fixed a date/time sync issue on the Opportunity Creation Query String feature.
- Deprecated the "Require Response Date" setting on the Opportunity attribution model, because the attribution system only considers responses that have a Response Date.
- Scoring is now subject to the configured "Scoring Batch Size" setting on the Scoring configuration page. If a batch is larger than this number (which is 200 by default), scoring will be done asynchronously. This also applies to reactivation. If a reactivation batch (scoring or active status) is larger than this setting, it will be processed asynchronously. From a practical perspective this means that if a customer is experiencing CPU time limits on response processing, instead of going to fully asynchronous scoring, they can reduce the configured batch size so that the application will automatically go to asynchronous processing when needed.
Comments
0 comments
Please sign in to leave a comment.