2021-04-21 Release Notes

Changes and Updates

Unless otherwise noted, you will see these changes on demo sites on 2021-04-22, then on live sites on 2021-04-30.

LS-72814: Improve the load time of embedded reports, and charts on reports.

LS-74663: If the SharePoint Documents list on a case is taking too long to display, you now see a new additional message: "You can also click here to remove the timeout limit and wait for the documents and folders to load." Patient users can click the "here" to wait for SharePoint to send the data.

LS-74963: The Edit pencils on the Charges list view now properly initialize the edit form so you see the previously selected charge.

LS-75061: You've tried the new "Show non-modifiable filters" option in the Report Part block, as detailed in last week's episode of Release Notes. But you wished a shown non-modifiable filter had a fancy lock icon displayed. Some wishes do come true.

LS-75353: Advanced Grants Management was not taking the timekeeping setting "Hours Required Per-Day For OT Exempt Staff" into account when calculating required hours in a business day for OT Exempt users. It will be going forward. You probably have this setting at the default 3 hours required. You have been warned.

LS-75531: The Clinic Events list on a clinic profile now filters out inactive events by default. As usual, you can temporarily see all events by clicking the "X" to remove the default "Active = Yes" filter.

LS-75220: The Google and Microsoft variants of Single Sign On will no longer refuse to let someone login if their email address happens to match the email address of an inactive user. The Okta flavor of SSO does not suffer from this malady.

LS-75284: Don't throw an error deleting a calendar event, even if it is linked to a pending case transfer.

LS-75305: There are 3 new configuration options in Site Settings in the Security Settings subsection: (1) Passwords must contain least one upper case character; (2) Passwords must contain at least one lower case character; (c) Passwords must contain at least one special character. All of these default to "No", which preserves the existing behavior. Setting any or all to "Yes" will only affect newly chosen passwords.