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

• The installation folder for new installations of VMP is now C:\Program Files\Vocera. When you upgrade an existing installation of VMP, its installation folder remains unchanged.

• The Vocera Smartphone Proxy is no longer supported in Vocera Messaging Platform 5.2.2. If you are using the Vocera Smartphone Proxy, you must remove it before upgrading.

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

• When the VMP Server is connected to any server using SSL, the SSL certificate must now be validated using the existing Windows mechanisms before an HTTPS connection is allowed. This affects connections to the Vocera Voice Server, the Vocera Secure Texting cloud server, WCTP integrations, and Exchange and other HTTP-based user synchronization sources. In particular, self-signed Vocera Voice Server are no longer accepted: they must be manually added to the Windows certificate store.

• When messages are sent using VMP (the source may be the VMP Web Console, VAI, VMI, CWE, or VCS), the VMP Server no longer automatically inserts any default response options. Previously, the default options of "on my badge" and "call sender" were inserted.

This release includes the following new features and functionality.

• Message conversations from templates can now be set to expire or to be delivered to on-campus users only.

  When you are creating a message template in the VMP Administrator or creating a message from a template in the VMP Web Console, you can specify the time in minutes after which the message conversation will expire, and you can specify that messages are to be delivered to on-campus users only. This ensures that emergency messages are sent only to people that are available, and that out-of-date emergency messages are not waiting for users when they start a later shift.

• Presence indicator option added.

  A configuration option in the VMP Administrator now enables you to specify the number of minutes that a user can be offline before being marked as being not available. This makes it easier to ensure that Vocera Collaboration Suite users do not make calls to inactive recipients.

• You can now choose whether device logout in Dual Mode forces badge logout.

  A configuration option in the VMP Administrator now enables you to specify whether users in Dual Mode are automatically logged out of their badge when they log out from the Vocera Collaboration Suite app.

• Shift scheduling over two days now easier in VMP Web Console.

  In the VMP Web Console, when you are creating a new schedule and are adding a shift to it, the Shift Period dialog box that enables you to specify the start and end time of the shift now allows you to specify the end date of the shift. This makes it easier to schedule a shift that starts in one day and ends in another.

• Integration messages can now be optionally displayed on client lock screens.

  A configuration option in the VMP Administrator now enables you to specify whether messages from systems that VMP is integrated with are displayed on the lock screens of client devices.

• SMTP connector now included in plugin configuration.

  The list of Mass Notification SMS messaging plugins in the Plugin Configuration section of the VMP Administrator now includes the SMTP connector.

• VMP Web Console access can now be automatically granted to imported users.

  When you are importing users from an external source, such as the Vocera Voice Server or an Active Directory server, you can now specify that all imported users are to be granted VMP Web Console access by default. You can then edit any individual user to take away this access if needed.

• High priority GCM now leveraged to enable push notifications when VCS Android clients are in doze mode.

  High-priority GCM is now used to enable push notifications to VCS apps running the Android operating system in doze mode. High-priority GCM is used for system option updates, text messages, on-call status changes, and messages indicating that no one has responded to a message that requires a response.

• You can now retrieve client logs for any VCS user running version 3.2 or later.

  From the Vocera Messaging Platform Administration Guide, you can now retrieve the client logs for any VCS user running version 3.2 or later for which a Device ID has been defined. This enables you to identify and resolve problems more quickly if they occur. The logs are retrieved without notifying the user.

• GE MUSE plugin improved.

  The GE MUSE plugin now includes the following enhancements:

  • You can specify the XML tag to use when mapping incoming XML text to Distribution Lists.
  • Notifications are now sent to a Distribution List instead of to an email address. This enables a consulting physician to know when a message has been accepted.
  • The number of available mappings has been increased from 10 to 40.

  If you have been using the GE MUSE plugin in previous releases, you will need to upgrade the plugin settings for the plugin to work correctly.

• VCS client can be configured to connect to the Vocera Client Gateway server.

  A new configuration option enables the VCS client to use the Vocera Client Gateway server for enhanced connection management. This setting is recommended to improve resource management on the clients. Requires Vocera Client Gateway version 5.2.2 or higher and VCS version 3.2 or higher.

• Status of On-Call Distribution List members now viewable in VMP Web Console.

  In the VMP Web Console, when you are viewing the members of an On-Call Distribution List, the current on-call status of each member is now displayed.

• New Secure Text pane of New Secure Message screen now resizable in VMP Web Console.

  When you are logged into the VMP Web Console and are creating a message, you can now resize the New Secure Text pane that appears at the left of the New Secure Message screen. This enables you to view long template names.

• Wakeup notifications now sent to VCS clients that are not active on the Vocera Voice Server.

  The VMP Server now sends a wakeup notification to clients that are offline or do not have a Vocera Voice Server ID, and that have not sent a getpushdata query to the server within the last 5 minutes and 15 seconds. When the server sends a wakeup notification, it sends a VoIP notification to clients running version 3.2 of VCS on iOS or a GCM notification to clients running version 3.2 of VCS on Android. It sends a regular APNS or GCM message to clients running older versions of VCS.

• You can now synchronize Vocera user IDs with Active Directory fields. When synchronizing users from multiple sources on the VMP Server, you can now synchronize the User ID in the Vocera Voice Server with a field in the Active Directory server (such as the account name). This enables you to synchronize between these sources when your users do not have an email address.

This release includes the following new features and functionality.

This release includes the following fixes:

• DE11178, DE11189 - Sending SOAP API or GE MUSE XML messages to escalation distribution lists that contain dual VST and badge users no longer results 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 now goes to its intended destination.

• DE11289 - Message response from VST user from different organization now 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 now displayed on the VCS user's screen and in the VMP Web Console.

• DE14300 - Web Console disclaimer now enabled.

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

• DE14484 - Long schedule titles now displayed properly in VMP Web Console.

  In previous versions of VMP, long schedule titles were sometimes not displayed properly in the VMP Web Console. This problem has now been fixed.

This release includes the fixes listed here.

This release includes the following known issues and limitations:

• DE15450 - VMP Web Console user cannot see conversation when added to it.

  If two users are in a conversation, and a VMP Web Console user is added to the conversation, the new user cannot see it until he or she logs out and logs back in again. This problem will be fixed in version 5.2.3 of VMP.

• DE15511 - Notifications do not have participants displayed in the Text Notifications report in the VMP Administrator.

  If you send a notification to a group, the Text Notifications report in the VMP Administrator does not contain information about the notification's participants. The workaround is to use the Text Messages Status - Detailed report, which contains this information.

• DE15512 - Multiple error email messages sent to administrator when attempting to send email to an incorrect SMTP server IP address or domain name.

  If the VMP Server is configured with an incorrect IP address or domain name for the SMTP server, and a user tries to send a message through this server, the administrator receives multiple email messages about the error instead of just one.

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.