In this release, we have focused on small changes and usability improvements, as well as technical advancements and bug fixes:
-
Clinical
-
Settings
Also included, the following bug fixes for Ascend Academic.
Clinical
Scrollbar Added to New Perio Exam and Edit Perio Exam windows
With the latest release, a scrollbar has been added to the Perio tab in the Clinical > New Perio Exam and Clinical > Edit Perio Exam windows, significantly enhancing the navigation experience. Ascend Academic users can now view all the information on-screen without zooming in or out. The integrated scrollbar ensures smooth, seamless navigation, making it easier to make multiple selections throughout the window with ease.
Additionally, the Start Exam button is now more prominently displayed, ensuring it's visible regardless of zoom settings.


Settings
Updated Terminology for Calculus Levels
The terminology for Calculus levels has been updated in Settings > Plaque and Calculus Levels > Calculus Levels to remove the term ‘soft’. The change will apply to the default configurations for dental school users. However, users with custom settings will not be affected by this change.

Bug Fixes
Simulation Patients No Longer Visible after Template Name Change
Issue: Under Settings > Simulation Patients, when a simulation template was renamed, the existing simulation patients created under the original template name were no longer visible.
Solution: Fixed to ensure simulation patients remain visible after template name is updated.
Email Confirmation Link for Appointments Not Working
Issue: Email appointment confirmations did not work as expected, as clicking the confirmation link led patients to a page displaying an error.
Solution: Fixed the appointment confirmation link to ensure patients are directed to the correct page when confirming their appointments.
Warning Message Missing for Comments Exceeding Character Limit
Issue: In the Faculty Evaluations > Create Sessional Evaluation section, when a user entered a general comment in the form that surpassed the 5000-character limit, no warning message appeared. This caused the form submission to fail, leading to the loss of any unsaved input.
Solution: Fixed to ensure that a warning message appears if the general comment exceeds 5000 characters.
Comments
0 comments
Please sign in to leave a comment.