Vocera Messaging Platform Server Release Notes

Version 5.2.2.1487

Updated: April 16, 2021

Documentation

The documentation for Vocera Messaging Platform version 5.2.2 is available online:

From these online help locations, you can download PDF versions of the VMP 5.2.2 documentation.

Upgrading to Version 5.2.2

Important: If you are currently running version 4.9.x of the Vocera Messaging Platform, you must first upgrade to version 5.1 or 5.2 before upgrading to version 5.2.2. You cannot upgrade directly from version 4.9.x to version 5.2.2.

What's Changed

This section lists important feature changes in the Vocera Messaging Platform.

What's Changed in VMP 5.2.2

The following features have been changed in Vocera Messaging Platform 5.2.2.

What's Changed in VMP 5.2.0

The following features have been changed in Vocera Messaging Platform 5.2.0.

What's New

This section summarizes the new features in this release.

What's New in VMP 5.2.2

This release includes the following new features and functionality.

What's New in VMP 5.2.0

This release includes the following new features and functionality.

What's New in Build 1395

  • You can control whether client logs are to be uploaded to the server.

    A configuration option has been added to the VMP Server to enable you to specify whether client logs can be uploaded to the server.

What's New in Build 1391

Build 1391 is a maintenance release that does not introduce any new features.

What's New in Build 1389

Build 1389 is a maintenance release that does not introduce any new features.

What's New in Build 1386

Build 1386 is a maintenance release that does not introduce any new features.

What's New in Build 1384

  • Interoperability with Vocera Secure Texting and Vocera Collaboration Suite now enabled.

    You can now configure the VMP Server to enable interoperability between VMP, Vocera Voice Server, Vocera Collaboration Suite 3.1.0, and Vocera Secure Texting 2.1. In this environment, VST, VCS, and badge clients can exchange text messages, VST clients can call any other client, and VCS clients and badge clients can call other VCS or badge clients. In all cases, the interaction is seamless, and users are not required to know the type of client with which they are communicating.

    Please contact Support at CustomerHelp@vocera.com to verify that you have the correct Vocera Secure Texting version before configuring this on the VMP Server.

  • Message auto-forwarding now available.

    When using version 3.1 or later of Vocera Collaboration Suite, a user can now specify that messages can be forwarded to another user. From the VMP Server, message forwarding can now be removed.

  • Template name search now provided.

    When you are creating a new secure message in the VMP Web Console, a template search field now enables you to display only the message templates whose names contain the search text that you have typed. If you have defined a large number of templates, this allows you to more easily find the template that you want.

  • Can now filter for VST users when creating a Distribution List.

    When you are creating a Distribution List, you can now specify that the list of VMP users to select from is to be filtered to display VST users only. This makes it easier to create a DL consisting only of these users.

  • Site information now provided for each VMP Web Console contact.

    When you are logged into the VMP Web Console and are viewing your list of contacts, the site for each contact is provided below the contact name. This enables you to distinguish between identical contact names on multiple sites. If you have no sites defined, the site is listed as Global. For VST users, the site is the organization to which they belong.

  • APNS certificate now automatically updated whenever possible.

    When the APNS certificate for your VMP Server is about to expire, the server automatically downloads and updates the certificate if possible. If a new certificate cannot be downloaded, the server now warns you that your certificate is about to expire.

  • Do Not Override settings now honored on smartphone devices.

    If a smartphone client user has set Do Not Override on their device, APNS notifications containing content that are triggered by urgent-level messages are now not pushed to the device.

  • VMP Server now includes iOS 9.3 security settings certificate.

    The VMP Server now contains the 2048-bit security settings certificate that devices running iOS version 9.3 use.

  • List pane now resizable in VMP Web Console.

    The pane that contains the list of contacts, the list of secure messages, or the list of on-call distribution lists is now resizable. This ensures that you can differentiate between entries with long prefixes, such as escalation distribution lists.

  • You can now view a list of all participants in a conversation.

    In the VMP Web Console, you can now view a list of all people who have been invited to participate in a conversation. In this list of participants, you can add a new participant if needed.

  • Auto Send Log capability has been included in the VMP installer.

    This enables logging information to be made available to technical support.

  • ASP.NET model no longer required.

    This reduces overhead and simplifies inter-domain communication and access to cache data.

  • GE MUSE integration now provided.

    The VMP Server now can read an XML file sent from GE MUSE and send a message based on its contents. This enables GE MUSE to send information to Vocera Collaboration Suite clients.

  • Contact status has been refined.

    When viewing your list of contacts in the VMP Web Console, you can now distinguish between contacts that are on the network and contacts that are available but "off campus". Off campus contacts include users who are logged into the VMP Web Console and Vocera Secure Texting users.

  • MS SQL Server 2014 now supported.

    VMP can now be used with MS SQL Server 2014, MS SQL Server 2012, MS SQL Server 2008 R2, or MS SQL Server 2008 SP2.

What's Fixed

The following list contains fixes and improvements made to the Vocera Messaging Platform.

What's Fixed in VMP 5.2.2

This release includes the following fixes:

What's Fixed in VMP 5.2.0

This release includes the fixes listed here.

What's Fixed in VMP 5.2.0 Build 1395

  • DE13706 – Delayed message notification caused by large quantities of SOAP messages now handled properly.

    Previous versions of VMP experienced message notification delay while processing a high volume of messages received through the SOAP API interface. This problem has now been resolved.

  • DE13967 - Large numbers of messages sent to single Escalation Distribution List now handled properly.

    If a user has access rights to an Escalation Distribution List, and simultaneously sends a large number of messages to this list, all messages are now processed properly.

  • DE13983 - Escalation now performed immediately if all members of a branch of an Escalation Distribution List are off campus.

    If you send a message to an Escalation Distribution List, and all members of a branch of the list are off-campus, escalation to the next branch of the list now happens immediately, instead of after the branch timeout period.

  • DE14271 - Access denied message now properly displayed in all web browsers when attempting to access unknown file.

    If you are using a browser other than Internet Explorer, and you attempt to access the VMP Server by specifying an unknown file name, you now see an "Access Denied" error message instead of a message stating that the file could not be found in the folder in which VMP has been installed.

What's Fixed in VMP 5.2.0 Build 1391

  • DE14087 – Delayed message notification caused by large quantities of messages now handled properly.

    Previous versions of VMP experienced message notification delay while processing hundreds of simultaneous messages sent to multiple devices. The behavior has been optimized to remove the delay.

What's Fixed in VMP 5.2.0 Build 1389

  • DE13374 - Reduced delay when sending messages to the VCS app on iOS devices when the app is closed.

    In previous releases, there was sometimes a significant delay before messages were received by VCS clients on iOS devices when the VCS app was closed. This was because the VMP Server was occasionally sending duplicate APNS notifications to the device, slowing down the APNS process. This problem has been resolved in this release.

  • DE13434 - Push notifications no longer repeatedly sent when large numbers of text messages sent to a single user through APNS.

    In previous releases, if a client app running on iOS received 101 or more text messages while the app was closed, multiple APNS push notifications would be sent for the 101st message and all subsequent messages. This is because the notify attempts counter was not set properly for these messages. This problem has been fixed in this release.

  • DE13503 - Duplicate registration keys no longer generated during synchronization.

    When you are synchronizing with a remote source that has 10 or more users, and field mapping is not specified for the DeviceID field, VMP no longer generates duplicate registration keys for newly created users.

What's Fixed in VMP 5.2.0 Build 1386

  • DE12457 - The connection between VMP Server and VST no longer intermittently fails.

    In the previous release of VMP 5.2.0, the connection between the VMP Server and VST may intermittently fail. This problem has been fixed.

  • DE12458 - Mass notification now received by all users if sent to more than 50 VST users and one or more VCS users.

    If you have created a Distribution List containing more than 50 Vocera Secure Texting users and one or more Vocera Collaboration Suite users and you send a mass notification to this Distribution List, all VCS and VST users now receive it.

  • DE12459 - New users from integrated VST organization now available to client devices immediately.

    If you add new users to a Vocera Secure Texting organization that is integrated with your VMP Server, the new users now appear immediately. You do not have to wait for the next synchronization of VMP and VST to see them.

What's Fixed in VMP 5.2.0 Build 1384

  • VBI Data Export capability restored. The Vocera Business Intelligence (VBI) Data Export capability that was introduced in VMP 4.9.2 but was not implemented in VMP 5.1 is now enabled again.

  • DE7813 - Notify Me icon no longer reappears in VMP Web Console after page refreshed.

    If you send a message that requires a response, and indicate that you are to be notified if a response is not sent within a specified time, the red Notify Me icon no longer incorrectly reappears after you click the message link in the Secure Messages panel and you refresh the page using the F5 key.

  • DE8912 - Upgrading from VMP version 4.9.2 no longer generates an error message during installation.

    If you attempted to upgrade from VMP version 4.9.2 to version 5.1.0.1272, an error message appeared during installation. This problem no longer occurs in VMP version 5.2.

  • DE8995 - Profile picture can no longer be edited on VCS client if permission to edit the profile picture is denied on the VMP Server.

    If you have set the "Allow User to upload personal image" configuration option in the VMP Server to No, Vocera Collaboration Suite users who are accessing this server can now no longer edit their profile pictures.

  • DE9191 - Type-ahead search results in VMP Web Console now displayed in wider window.

    When you are typing a recipient name in the To field of a new secure message, the window that displays the list of type-ahead search results is now wider, which enables longer user names to be displayed.

  • DE9667 - Timestamps now correct in Monitor View in VMP Web Console.

    In previous versions of VMP, messages displayed in the Monitor View of the VMP Web Console were displayed with incorrect time information. This problem has now been fixed.

  • DE9984 - Maximum subject length in messaging templates now 512 characters.

    When you are creating a messaging template, the text for the message subject can now be up to 512 characters in length.

  • DE10258 - Multiple-choice options in messages that contain punctuation are now processed properly when sent to badges.

    If a Vocera Collaboration Suite user sends a message to a badge user that contains multiple choice responses, and one or more of the responses contain punctuation characters, these characters are not displayed on the badge, but the VMP Server is now able to correctly identify and return the selected response.

Known Issues

This section lists known issues and limitations in the Vocera Messaging Platform.

Known Issues in VMP 5.2.2

This release includes the following known issues and limitations:

Known Issues in VMP 5.2.0

This release includes the following known issues and limitations:

  1. DE7989 - Photo preview sometimes does not work when changing the profile picture.

    If you are logged into the VMP Web Console and you attempt to change your profile picture, previewing the new profile picture sometimes yields unexpected results on some web browsers.

  2. DE9256 - Multiple users forwarding to the same user may lead to duplicate messages.

    If a message is sent to two or more users who are forwarding messages to the same user, that user receives multiple copies of the sent message.

  3. DE10259 - Members of a Vocera Voice Server sub-department are not synchronized.

    If a Vocera Voice Server department is being synchronized with a group in the VMP Server, members of any sub-department of this department are not synchronized.

  4. DE10558 - Badge users are notified when a user is added to a conversation.

    If a Vocera Collaboration Suite user and a badge user are in a conversation, and another user is added to the conversation, both the VCS user and the badge user are notified that the new user has been added.

  5. DE10811, DE10813 - Message forwarding of clinical system messages to badge users can result in inconsistent behavior.

    Forwarding of clinical system messages (VMI, CWE) from VCS users to badge users is not fully supported. This option should be disabled if your environment contains both VCS and badges.

  6. DE 11178, DE11189 - Sending SOAP API or GE MUSE XML messages to escalation distribution lists that contain dual VST and badge users can result in inconsistent behavior.

    If you send a SOAP API or GE MUSE XML message to an escalation distribution list that contains a user that is logged into both VST user and the badge, the message may not go to its intended destination.

  7. DE11289 - Message response from VST user from different organization not displayed.

    If a VCS user starts a conversation with VCS and VST users from multiple organizations, a VCS user from one organization sends a message requiring a response, and a VST user from another organization responds, the response is not displayed on either the VCS user's screen or the VMP Web Console. The message status indicates that the user has responded.

  8. DE11409 - Blank screen may appear when double-clicking a message in Monitor View in VMP Web Console after filtering.

    When you are logged into the VMP Web Console and have permission to access Monitor View, and you have used filtering to limit the messages displayed, a blank screen may appear when you double-click a message. The message is displayed properly if you single-click the message instead of double-clicking it. To restore Monitor View when the screen is blank, switch to another tab and then return to Monitor View.

  9. DE11421 - VMP contacts replaced by VST users with same email address after integration.

    If an Active Directory contact or Vocera Voice Server global address book contact has been previously synchronized with the VMP Server, and a VST user with the same email address exists, the VST user replaces the existing VMP contact when the VMP Server is integrated with VST.

  10. DE11422 - VST user visible but not accessible in Vocera Collaboration Suite client and VMP Web Console after integration if the user has the same email address as a VMP contact.

    If an Active Directory contact or Vocera Voice Server global address book contact has been previously synchronized with the VMP Server, and a VST user with the same email address exists, the VST user becomes visible on all Vocera Collaboration Suite clients and the VMP Web Console. However, because this user is not part of a VMP distribution list, you cannot send a message to this user.

  11. DE11481 - Users cannot log into the VMP Web Console after being unlinked from VST.

    If the VMP Server is integrated with a VST server, and a Vocera Voice Server user was previously merged with a VST user but has since been unlinked, this user cannot log into the VMP Web Console unless granted permission to do so in the VMP Administrator.

  12. DE11932 - In the VMP Web Console, a popup message appears when you select an Escalation Distribution List that contains a branch that has a Vocera Voice Server group as its member.

    If you are logged into the VMP Web Console, and you select an Escalation Distribution List from a list of search results that has a branch whose only member is a Vocera Voice Server group, the popup message "No recipients available in selected DL(s) to receive message" incorrectly appears.

  13. DE14300 - Web Console disclaimer not enabled.

    The Disclaimer for Web Logon configuration option is not available in the VMP Web Console in this release.

  14. US30218 - Badges unable to respond to long message responses.

    If you send a message to a badge with multiple choice responses, and the responses are longer than 15 characters, the selected response is not sent properly to the sender of the message.