This release includes the following enhancement(s) to Vocera Escalation Service.

• Changes in the Escalation Service allow the Vocera Adapter to send alerts to groups directly. (ADP-10924).
• The Escalation Service now provides the dataset name to the rule template factory when retreiving a rule form. (ADP-10911).

This release includes the following enhancement(s) toVocera Escalation Service.

• This is a hot fix. There are no new issues.

This release includes the following enhancement(s) toVocera Escalation Service.

• This is a hot fix. There are no new issues.

This release includes the following enhancement(s) toVocera Escalation Service.

• Outgoing WCTP Presets have been added for Engage Rules. (ADP-11009)

This release includes one enhancement toVocera Escalation Service.

• Audit events updated to include rule names, alert types, and alert ids.

This section provides information about fixes and improvements made to the Vocera Escalation Service 1.3.0 product.

• Starting the Escalation Service under the correct circumstances there was a potential delay of 3 to 10 seconds when matching a delivery flow for the first time. (ADP-11038)
• Engage Rules that did not have an alarm definition could cause cache issues. (ADP-11365)
• Triggering more than 60 clinical alerts per minute could cause alerts to fail delivering all alerts. (ADP-11385)
• Templated Events was sending an alert to every user or every group on the system if no user or no group were specified. (ADP-11433)
• Engage Rules was escalating to the fail-safe destination If deliver to the final assigned recipient had an error. (ADP-11561)
• Escalation Service potential would fail to find recipients for roles when the destination delay was greater than the cache expiration time. (ADP-11595)

This section provides information about fixes and improvements made to the Vocera Escalation Service 1.2.2 product.

• Sending an external alert update, and then an immediate updated alert to another user, caused the second alert to not always be delivered. (ADP-11063)
• Sending multiple 0 second delay destinations in a row are grouped together, and the Escalation Service looks for different destinations. There was a bug that was causing delays to be sent to the same destination. (ADP-11053)
• Having a registered device for two or more interfaces, while having one device offline, caused the delivery flow to potentially stop escalating. (ADP-11039)
• Using vendor specific devices that are linked to one user, but have different interface configurations, may have caused the Escalation Service to deliver to an offline device. (ADP-11037)
• VIM messages with a response of "Accept" or "Acknowledge" were not always treated as accepted by the Escalation Service. (ADP-10987)

This section provides information about fixes and improvements made to the Vocera Escalation Service 1.2.1 product.

• Sorting responsibility was moved from the database to the Escalation Service adapter to correct escalation issues. (ADP-11090)

This section provides information about fixes and improvements made to the Vocera Escalation Service 1.2.0 product.

• In certain situations, Outgoing WCTP did not trigger an escalation to the second level of notification. (SOL-3627)

This section provides information about fixes and improvements made to the Vocera Escalation Service 1.1.0 product.

• ADP-10640

  Alarms that have been accepted no longer trigger an erroneous audit event.