Vocera Messaging Platform Server Release Notes

Version 5.2.0.1395

Updated: April 16, 2021

Documentation

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

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

Compatibility

VMP Server version 5.2 is not compatible with any version of the Vocera Collaboration Suite client prior to 3.0. You will need to upgrade your Vocera Collaboration Suite client to use this server.

To use the version 3.0 Vocera Collaboration Suite client with Vocera Smartphone Proxy, you must upgrade to VSP version 5.2. This upgrade does not have to happen at the same time as the VMP Server version 5.2 upgrade.

If you are working with the Vocera Voice Server, version 4.4.3 or later is required.

VMP Server 5.2 does not support message templates in which one or more recipients are Escalation Distribution Lists and other recipients are regular users. Only one Escalation Distribution List can be listed as a recipient, and it must be the only recipient.

What's Changed

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

What's New

This release includes the following new features and functionality.

To check whether you have the latest build of VMP 5.2.0:

  1. Log into the VMP Administrator.
  2. From the Help menu, select About. The About dialog box appears.
  3. In this dialog box, locate the Version field. This is a sequence of four numbers. The build number is the last number in this sequence. For example, if Version is 5.2.0.1395, the build number is 1395.

If you do not have the latest build of VMP 5.2.0, and you need any of the fixes or features that are listed in a more recent build than the one that you have, contact Vocera technical support to upgrade.

What's New in Build 1395

This release includes the following new features and functionality.

What's New in Build 1384

What's Fixed

This release includes the fixes listed here.

What's Fixed in VMP 5.2.0 Build 1395

What's Fixed in VMP 5.2.0 Build 1391

What's Fixed in VMP 5.2.0 Build 1389

What's Fixed in VMP 5.2.0 Build 1386

What's Fixed in VMP 5.2.0 Build 1384

Upgrading the VMP Server

Use the following steps to upgrade to VMP Server 5.2.0.

  1. Stop the Vocera Data Exchange service on the VMP Server:

    1. Open the Windows Services application:

      Windows > Start > Administrative Tools > Services

    2. Click to select Vocera Data Exchange Service.

    3. Right click and select Stop.

  2. Execute the updated VMP setup file on the VMP installation server.

  3. Accept the License Agreement, and click Next.

  4. In the Software Type dialog, select VMP Server and Administrator, and click Next.

  5. Accept the existing Install Location and click Install.

  6. At the Create VMP Database Wizard prompt, enter the following information and click Next.

    1. Enter the SQL Server name.

      Tip: Vocera recommends you type the name of the server and do not use the dropdown list to select a server.
    2. Select the SQL Server Authentication radio button.

    3. Enter the SA Login and Password.

  7. Click OK to confirm that the existing database will be upgraded, and click Next.

  8. The installer creates the VMP databases on the SQL server. When the script is complete, click OK.

  9. If the VMP Enterprise Manager opens after the database script is complete, close the application to complete the installation process. Click Finish to close the installer.

  10. Restart the server.

  11. The VMP Server is now updated. Confirm a good installation by opening a supported Web browser and pointing to the server URL. If VMP is installed correctly, the VMP Web Console opens.

Known Issues

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.