These release notes were last updated May 24, 2023. Information on this page is subject to change.
Please note: In order to enable the following release changes to your environment, we recommend clearing your cache.
Release Summary
Here's a quick overview of the updates in this release:
- Improvements to accessibility and simultaneously editing records
- General bug fixes
Release Dates and Downtime
Release dates are subject to change. Release date changes will be noted in the Change Log column below.
Downtime required: 1 hour per environment
|
Environment |
Release Date |
Deployment Start Time (PST) |
Change Log |
| UAT-AU | June 1, 2023 | 10am | |
| UAT-SG | June 1, 2023 | 10am | |
| UAT-UK | June 1, 2023 | 10am | |
| UAT-CA | June 1, 2023 | 3pm | |
| UAT-US | June 1, 2023 | 3pm | |
| Prod-AU | June 15, 2023 | 10am | |
| Prod-SG | June 15, 2023 | 10am | |
| Prod-UK | June 15, 2023 | 10am | |
| Prod-US | June 15, 2023 | 6pm | |
| Prod-CA | June 15, 2023 | 6pm |
Detailed Release Notes
New and Enhanced
- Some general accessibility improvements have been made to the application.
- We made enhancements to how SP records are affected when multiple users edit them simultaneously. See below for additional details.
Fixed
- Fixed an issue that caused the “created on” values for an award and each modification to be stored with the incorrect version.
- Fixed a couple issues with Dropdown and Checkbox object types in the Simplified Form Builder that were leading to errors when trying to create an award from a proposal or award.
- Fixed a timing issue on the dashboard search that was leading to results being displayed that did not match the entered search characters.
Additional Information: Simultaneous editing by multiple users in SP records
Use cases and expected behavior
Use case #1: Multiple users are editing different portions of a record at the same time.
Expected behavior: In this case, when an auto-save occurs, it will save the value entered by the current user, and also pull in any changes to different form objects that may have occurred since the last form save.
Use case #2: Multiple users are editing the same portions of a record at the same time.
Expected behavior: In this case, if different users have entered different values for the same field, the first value will be saved, and a warning will be displayed to the user(s) whose changes were not saved, indicating which form object is impacted.
(Ref ID: 19.03.24)