EMS Services and Components Release Notes
V44.1, Update 33

This section describes updates to your EMS software.  

See Also: Contact Customer Support and Updating to the Latest Version of EMS (Patches and Builds).

V44.1 Update 33

Release Date: 
June 2019

Patch: 
TBD

Build #: 
TBD

Enhancement

Area

Description

Automated Reports

Reliability improvements to the Automated Reports Service

Improvements have been made to the Automated Reports Service to enhance reliability and help the service process long-running reports more efficiently. Previously, the Automated Reports Service was vulnerable to crashing if a report took too long to process.

Internal Reference # EMS-5329
(For Internal Use Only)

Fixes

Area

Description

Email Notification Service

Notification Rule emails were sent to group instead of Everyday User

Although the Notification Rule emails were configured to be sent to an Everyday User, the emails were being sent to the group.

Fix: Restored functionality so that notification emails are sent to the email address that is configured on the rule:

  • If the notification rule is configured to notify a group, then the notification will be sent to the group's email.

  • If the notification rule is configured to notify an Everyday User, then the notification will be sent to the Everyday User's email.

Internal Reference # EMS-841
(For Internal Use Only)

No Show notification rule was not updating the status on bookings

The notification rule for No Show Status was not updating the status of bookings even though the Change Status checkbox had been selected (Configuration > Administration > Check-in Notification Rules).

Fix: Restored functionality so that when the Change Status checkbox is selected, the booking status is updated appropriately for No Shows.

Internal Reference # EMS-908
(For Internal Use Only)

Automated Reports

Changing the time for an automated report updated the last sync time and the report would not run on the day the time was changed

When users changed the time to run an automated report, the report would not run at the updated time on the day the change was made if the report had already been run prior to the time change.

Example: A user creates a saved report that runs daily at 9:00 a.m. Today, after the report runs at 9:00 a.m., the user changes the time to run the report to 11:00 a.m., but the report does not run at 11:00 a.m. This issue occurred because the "last sync" time was updated for the report that was run at 9:00 a.m.; therefore, the system considered the report as already having been run for the day. Note that on subsequent days, the report would run at 11:00 a.m. as expected.

Fix: Modified functionality so that when the time is changed for running an automated report, the report runs at the time specified, even on the day the time was changed.

Internal Reference # EMS-1116
(For Internal Use Only)

Contact Customer Support

If you do not have a customer login, register here.