Skip To Main Content
EMS Software Update: December 19, 2024
Claire Frank

As we wrap up 2024 🎁😉, we’ve got some exciting updates and fixes to share. From fresh features to enhancements in our search tool we know you’ll love ✨—you won’t want to miss this update!

What's New

  • Search & Reports: Not one but two great improvements to the Search tool!
    • You can now reorder the columns within a search! This works for List and List with Groupings searches.
    • Now, when displaying appointments in search, if a duplicate appointment is booked for the same event, both appointments will be displayed in the date column.
       
  • Leadflow: Under Admissions > Students in Admissions > Leads, we’ve added a new column to track the date that the Lead has come in from a CMS Leadflow form!
     
  • Billing Exports: We’ve built support to include a custom date range when setting up a Billing Export. Custom date ranges in billing exports allow for better integration with QuickBooks and other systems.

Bug Fixes

  • Calendars: We fixed a couple of minor glitches in the Calendars feature:
    • We fixed an issue that prevented canceled appointments from being removed from the list without refreshing the page.
    • We also corrected an issue that was preventing schedules from showing up under the correct name within searches.
       
  • Password reset: When resetting parent portal passwords, an incorrect error message appeared when the password confirmation did not match the new password entered in the first box. This led to some small UI adjustments to that page as part of the fix.
     
  • Payment History Report: Fix for a bug on the Payment History page where failed billing payments displayed updated convenience fee amounts instead of the original fee amounts applicable at the time of the transaction.
     
  • Scheduled Emails: We resolved an issue where scheduling an email with a prefilled default date triggered a 'this field is required' error. Users were previously required to clear and re-enter the same date, but this behavior has been corrected for a smoother experience.

Explore More Recent Support Blogs