Vocera Engage 7.0.13 is a maintenance release only. There are no new features in this release.

This release includes enhancements to several components of Vocera Engage.

• Data Validation Update

  The system validates that imported data is properly formatted.

• Addition of Alert Throttling

  Alert throttling is added to Engage with the following options:

  • System level throttling is enabled by default to protect the system from sending to more than 1200 recipients at a time without batching the delivery with 90 second intervals.
  • Standard throttling can be enabled on individual rules, allowing customers to batch deliveries of non-urgent alerts when there are more than 100 recipients.

• Upgrade Enhancements

  The following features are added:

  • The operating system is using RHEL 8.
  • The system configuration is validated both pre-upgrade and post-upgrade.
  • Patient data received on the active node during the upgrade of a standby node is no longer lost when using the Limited Downtime Upgrade Path.

• Scalability Enhancement

  The auto-scale feature now automatically assigns available host resources more efficiently for Engage deployments.

• High Availability Improvement

  The system performs a failover to recover if it detects that queue processing is unresponsive.

• UI Updates for Non-Voice Customers

  The Engage Console is updated. It only displays information that is relevant to the customer's configuration.

• Staff Assignment Communications Updates

  Right click roles to show a quick menu, including Messages, when using XMPP.

The following list includes the defects fixed in this version of the Vocera Engage.

• PFM-18258, PFM-18259, PFM-18260, PFM-18261, PFM-18263, PFM-18396, PFM-18413, PFM-18649 Updates to fix upgrade/migration issues are now implemented.

The following list includes the defects fixed in this version of the Vocera Engage.

• PFM-17621 Audit Log text search was currently not working.
• PFM-10929 Attribute transformations stored nil value if any capture group was nil.
• PFM-11104 Site/Facility deletion and cascade failed when users were associated with the site.
• PFM-15884 Facilites could not replace the highest priority node in a PIP cluster.
• WEB-12450 Users could not be found in a search when the search included both a full name and one of the users perferred names.
• WEB-12974 Exporting 'Assignment Locations to Beds' could fail.
• WEB-12922 Users can no longer remove either the EISUPPORT or Administrator roles.

This section provides information about known product defects and limitations in the Vocera Engage 7.0.0.13.

• PFM-18046 A failed node may fail to auto-recover into a standby state if a disk freezes for a short period of time and then recovers.

  Version Introduced: Vocera Platform 6.6.x

  Workaround: To recover the node in a bad state, disable and re-enable the node.

• PFM-18074 Interface Queue Monitor health check may cause failover loop on certain undeliverable message scenarios.

  Version Introduced: Vocera Engage 7.0.12

  Workaround: None.

• PFM-19152 The migrator is updated to not set the company name if it already exists.

  Version Introduced: Vocera Platform 6.4.x

  Workaround: None.