This release includes the following new features and enhancements:

New Features

• Support for Preferred Name—Allows you to update the first or last name of the user stored in the Active Directory to a preferred name. All reports and dashboards display the updated (preferred) name.
• Facility-Unit Mapping—Provides a user interface that allows you to map the Voice Server Site and Department name with the corresponding Engage Facility and Unit name.
• Local User Password Reset—Allows you to reset the password for users created locally in the Vocera Analytics Visualization Server.
• Response Dashboard—The data represented in all the 8 Engage reports are now enhanced in the newly introduced Response dashboard. It provides metrics related to delivered events and responses to these delivered events, starting at the highest summary level to the most-detailed user/bed level. Hence, the following Vocera Engage reports will no be longer available:
  • Bed Detail
  • Bed Summary
  • Department Detail
  • Department Summary
  • Mobile Activity Department
  • Mobile Activity User
  • User Detail
  • User Summary

  For more information on Response dashboard, see https://pubs.vocera.com/platform/va/1.4.1/help/va_admin_help/index.html#platform/va/1.4.1/topics/va_int_user_response.html.

• Platform Support—Vocera Platform 6.6 is added in this release.
• Voice Server Support—Vocera Voice Server 5.8 is added in this release.
• VMP Support—Vocera Messaging Platform 5.8 is added in this release.

Enhancements

• Intranet Support—The dashboards and reports of Vocera Analytics now work locally over the intranet and do not require an internet connection.
• Import Users—You can override local users while importing Active Directory users that have an identical username.
• Database Metrics—The Monitoring log captures the size of the Vocera Analytics database and related metrics.

Upgrade Path

You can now upgrade from the following Vocera Analytics versions:

• Vocera Analytics version 1.3.0 to Vocera Analytics version 1.4.1
• Vocera Analytics version 1.4.0 to Vocera Analytics version 1.4.1

Third-Party Software Versions

The following third-party software versions are included in this release:

This release includes the following new features and enhancements:

New Features

• Data Backup—A new user interface to backup data is introduced in this release. You can now schedule an automatic backup along with incremental backup or run a full backup instantly.
• Data Purge—A new user interface to purge data is introduced in this release. With a few clicks, you can now purge data seamlessly. You are no longer required to run a script to purge data.
• Local User Creation—Allows you to create users locally and access Vocera Analytics Visualization Server even if Active Directory is not set up.
• Minibadge—A new device type filter is introduced in this release.
• Platform Support—Vocera Platform 6.5 is added in this release.
• Voice Server Support—Vocera Voice Server 5.7 is added in this release.
• VMP Support—Vocera Messaging Platform 5.7 is added in this release.
• System Health Report—This report provides a trend analysis of the overall site health and usage of the Vocera system.
• Tomcat Version Support—Tomcat version 9.0.59 is added in this release.
• Panic Broadcast—Panic broadcast calls data is captured and shown in some dashboards. For more information, refer to https://pubs.vocera.com/platform/va/1.4.0/help/va_admin_help/index.html#platform/va/1.4.0/topics/va-panic-bc.html

Enhancements

• The filter behavior is updated to avoid default filters set by the system, when the user logs in for the first time for every session.

This release includes the following new features and enhancements:

New Features

• Platform Support—Vocera Platform 6.4 is added in this release.
• Tomcat Version Support—Tomcat version 9.0.52 is added in this release.

Enhancements

• Badge/Mobile Last Used Report—This report is enhanced to show the latest data for device-related columns.
• Crosswalk Workflow—The Department Group to Unit mapping is now supported as part of Platform 6.4 release.
• Database Backup—Incremental backups are now supported that reduces the backup time.
• Pipeline Stabilization—Enhanced the process for handling Group membership changes.
• Search Filter—Enhanced the search functionality of lazy-loading Group filter to display relevant filter results.
• Upgrade Procedure—Enhanced the upgrade procedure for source systems to avoid data loss.

For information on What's Fixed in this release, see Fixed Issues in Vocera Analytics 1.3.1.

This release includes the following new features and enhancements:

New Features

• Platform Support—Vocera Platform 6.3.3 is added in this release.
• Tomcat Version Support—Tomcat version 9.0.37 is added in this release.

Enhancements

• Event Index Dashboard—Five new widgets are added, namely Saved Events, Interruptions, Top 10 Event Description Trend, Top 10 Interruption Description Trend and Event Details by Department. Also two existing widgets % Accepted and % Declined are removed.
• Inventory Status dashboard—Optimized the performance by considering data only for the last 6 months.
• User Interruption Dashboard—Two new fields Bed and Description are added in Details widget. The Bed field displays both the room and bed number. The Description is for alert and alarm data. Both fields are searchable through the Search option in the Details widget.
• Pipeline Enhancements—
  • For Voice Server source: Improved database query failure to avoid data loss.
  • For Engage source: By default, the SetJobProcess is set to Min.
• Email notification with problem description—Whenever all reports/dashboards in a scheduled package fail, the corresponding package recipients now receive information about the issue in the email instead of blank emails.
• Improvements to User Name Filter—Login id is displayed to differentiate two identical user names. To identify inactive users, [X] is suffixed to the user name. Data populated for this filter is lazy-loading enabled.
• Asset Tracking Improvements—Improved device activity for better tracking.

For information on What's Fixed in this release, see Fixed Issues in Vocera Analytics 1.3.0.

This release includes the following features:

New Features

• Dropped Call Dashboard—Displays details of calls that were successfully connected but due to technical reasons were cut off before the speaking parties had finished their conversation.
• Platform Support—Vocera Platform 6.3 is added in this release.
• Tomcat Version Support—Tomcat version 9.0.34 is added in this release to avoid vulnerabilities encountered with older Tomcat versions.
• Vocera Messaging Platform Support—Vocera Messaging Platform 5.4 is added in this release.
• Voice Server Support—Vocera Voice Server 5.4 is added in this release.
  Note: Vocera Voice Server 4.4.x is not supported from this release. Hence, upgrade to Vocera Voice Server 5.1 or higher before you install Vocera Analytics 1.2.4 HF.
• Windows Server Support—Windows Server 2019 is added in this release.

Enhancements

• Release Version Identification—Installed Vocera Analytics Release Version is now available in Database table and Vocera Analytics log files.
• Processor Improvements:
  • The processor execution duration is now displayed in Vocera Analytics log files.
  • When a processor aborts, the record is closed along with the timestamp when the error was detected.
• Improved connectivity between Flume service and Voice Server—Manually copying of Jar files are no longer required for Voice Server upgrade.
• Installer Improvements—Users can now upgrade from any version of Vocera Analytics (1.2.0, 1.2.1, 1.2.3) to the latest version (1.2.4).
• Pipeline Optimization—Optimized the mechanism of few processors for increased stability and performance of the pipeline.
• Sorting of Scheduled Packages—A new field Next Run at is added to the Scheduler page to sort the packages based on the package scheduled time.
• Improvements to Events Captured—Few events were captured from both active and passive Voice Servers. With VA 1.2.4, these will be processed only from active Voice Server.
• Wildcard Mask Support—Wildcard Mask feature is enhanced in affected dashboards and reports.

Vocera Analytics 1.2.3 is a maintenance release only. It contains no new features.

This release includes the following features:

New Features

• Data Purge—Allows the administrator to reduce the storage footprint of the Vocera Analytics database and delete fact data beyond the number of months being retained. The Vocera Analytics 1.2.0 suite includes an admin script that purges data from both Landing (ldg) and Vocera Analytics (vocera_analytics) databases. By default, the script is configured to retain data for 36 months but it can be modified.
• PDF export for Dashboards—Dashboards can be exported to PDF format.
• Platform Support—Vocera Platform 6.1 is added in this release.
• Role Management—Allows you to create new roles and add dashboards and reports to the role. You can also assign these roles to users based on the activities each user performs.
• Schedule Dashboards—Dashboards can be scheduled in addition to reports.
• VMP License information—Added VMP license information to License Dashboard.

Enhancements

• LDAP—Vocera Analytics now supports LDAP over SSL.
• Messaging Entities—Added support for new messaging entities such as Smartbadge, Vocera Vina, and Web console.
• Smartbadge—Smartbadge with M2 and M3 modes are now supported.
• Speech Recognition Algorithm—The formula to calculate speech recoginition is modified. For more information, refer to Speech Recognition Calculations Overview.
• Terminology Update—To be consistent with the terminology used across Vocera products, Unit is replaced with Department and Nurse is replaced with User in the respective dashboards and reports.

This release includes the following features:

New Features

• Platform Support—Vocera Platform 6.0 is added in this release.
• Dashboards—Three new dashboards are added in this release. Following are the details:
  • Conversation Summary—Provides the summary of conversation for users in a Vocera system.
  • Conversation Activity—Lists the details of every conversation that had activity for the selected date range.
  • Message Details—Provides the message count and message details categorized by facilities or units within an organization.
• Instant Conference—Added instance conference as a call type in the following dashboards and reports:
  • Dashboard
    • Call Details
    • Call Summary
    • Group Interruptions
    • Interruption Summary
    • Location Call Summary
    • Unit Interruption Summary
    • User Activity Details
    • User Call Details
    • User Interruptions
    • Voice Index
  • Reports
    • Outgoing Calls Details
    • User Activity
• Engage Support—Multi-site Engage server support is added in this release.

Enhancements

• Added Activities and Directions filters to User Activity Details dashboard and User Activity report. Also messages and conversations data are added to the report.
• Configured pipeline failure notifications for Spark.
• Introduced access permissions for users.
• A Call Type column is added to Outgoing Calls Detail report to identify whether a call is made to group or broadcast is sent, or if an instant conference is made.
• Messaging data added to User Activity Details dashboard and report.
• Improved backup and restore process.
• Updated third-party software bundled with Vocera Analytics.
• Number and date formats are localized in dashboards and reports.
  Note: ISO time formats remain unchanged.

Version 1.0.0 is the initial release of Vocera Analytics. This release includes the following features:

• 30 dashboards and 33 reports.
• 360° view of calls, broadcasts, texts, alarms, alerts in a single location that is represented visually for all Vocera solutions.
• New Vocera performance metrics.
• Usage analysis for system improvements and executive return on investment for all Vocera products.
• Modern infrastructure that provides:
  • Simple User Interface (UI) for both clinical and technical personnel.
  • Improved performance.
  • Enterprise scalability for multiple facilities.
  • Three years of data storage.
• Database schema availability for custom reporting.

• VA-11794 - Scheduled automatic backups no longer fails to create scheduled tasks due to invalid date format.
• VA-11731The data in all the widgets in the Department Interruption dashboard are now represented correctly.
• VA-11706 - The deficiency in security audit in Apache Tomcat is now fixed.
• VA-11652 - The service monitor no longer allows case-insensitive username logins.
• VA-11614 - The issue of packages not being sent via email when smtp.Office365.com is configured is now resolved.
• VA-11607 - The online help links for Complete and Missed Calls and User Interruption by Group Membership reports point to the generic help documentation page.
• VA-11594 - Vocera Analytics now recognizes the group name from Voice server logs when a call is placed to a DID number assigned to a group.
• VA-6906 - Vocera Analytics does not capture data for calls made to an extension when dialed from the keypad of Smartbadge or Vocera Vina device.

• VA-11528 - Performance of dashboards and reports.
• VA-11366 - The HSTS settings in Tomcat is enabled to avoid vulnerabilities.
• VA-11255 - The log4j.jar version is now updated to avoid vulnerabilities.

The following issues are fixed in Vocera Analytics 1.3.1:

• VA-10885 - In certain circumstances, when the location (facility/unit) gets updated for an event, the data still displayed the old location. In case the location was null, it was displayed as Unknown facility or unit. This issue is fixed now. The location field now displays the latest location (facility/unit).
• VA-10655 - Broadcast call entry was missing when call was placed via VCS device without using voice command (VCS device menu options)
• VA-10212 - Event Index dashboard might take more time to display data. For example, to display data for 1 day, it takes approximately 20 seconds.
• VA-10210 - If the device MAC address is provided in upper case in Vocera Platform, the fields Serial Number, Label are blank and Owner Facility, Owner Group display Unknown in Status Tracking dashboard even if Owner Group and Owner Facility are added.
• VA-10173 - Receiver Device ID and Name are displayed as IP address when a broadcast is done from Telephone.
• VA-10127 - Data is displayed for default date range instead of selected date range and filter if the description selected contains a percentage value in exported PDF.
• VA-10124 - From VMP 5.3.3 onwards, the MaxInUse value in License dashboard will not match with In Use value in VMP reports.
• VA-10120 - In License Dashboard, values for Latest Assigned and Max In Use fields are incorrect, if more than 10000 users are assigned to VMP License.
• VA-10023 - In exported CSV of Department Interruption Summary dashboard, if the same event has accepted or declined responses, then Others category entry will not be found.

The following issues are fixed in Vocera Analytics 1.3.0:

• VA-10144 - Location name is not displayed on dashboards and reports if the access point was provided in upper case in Vocera Platform.
• VA-10133 - Device details such as Owner Group, Owning Facility, Label, Status, Notes, Serial Number were missed as the device MAC address was provided in upper case in Vocera Platform.
• VA-9908 - Event Index dashboard did not display data for specific days.
• VA-9902 - The search operation in Description filter takes a longer time to populate the values in Event Index dashboard and reports in Interruption folder.
• VA-9808 - Data too long for column 'MC_Flat' exceptions' error resulted in broadcast call data missing in analytics.
• VA-9782 - Tomcat error displayed on the Analytics Server upon logout and login and upon reboot.
• VA-9743 - Critical vulnerability scan issue noticed on Vocera Platform servers that use admin/admin login credentials for Service Monitor.
• VA-9649 - While executing group dimensions, pipeline crashed and stopped.
• VA-9648 - Inadequate warning message was displayed when Spark failed to connect to flume.
• VA-9602 - Flume starts reading data from the beginning when status files query and conf file query does not match.
• VA-9601 - VMP Flume status files were not updated after upgrading to VA 1.2.4.
• VA-9591 - Engage Flume status files were not updated after upgrading to VA 1.2.4.
• VA-9586 - Pipeline is not processing data.
• VA-9561 - While loading dimension data, plugin error occurred.
• VA-9560 - In certain scenarios, receiver name was empty on Messaging dashboard.
• VA-9550 After failure, Clinical Report processor processes data from the default date of 1970-02-01.

The following issues are fixed in Vocera Analytics 1.2.4.2 patch:

• VA-9650 - When pipeline and database backup are running simultaneously, both pipeline and database backup failures were noticed in the log file.
• VA-9649 - While executing group dimensions, pipeline crashed and stopped.
• VA-9601 - VMP Flume status files were not updated after upgrading to VA 1.2.4.
• VA-9591 - Engage Flume status files were not updated after upgrading to VA 1.2.4.
• VA-9586 - Pipeline is not processing data.
• VA-9561 - While loading dimension data, plugin error occurred.
• VA-9550 - After failure, Clinical Report processor processes data from the default date of 1970-02-01.

The following issues are fixed in Vocera Analytics 1.2.4:

• VA-9467 - Vocera Analytics 1.2.3 upgrade failure on Voice Server machine stopped MYSQL service on Voice Server.
• VA-9246 - Three Service Monitor email templates are missing after upgrading VA 1.2 to VA 1.2.2 or VA 1.2.3.
• VA-9240 - Scheduled packages were not working post restart of Vocera Analytics server if such packages had Add contents to zip disabled.
• VA-9203 - VMP License count in License dashboard displayed incorrectly.
• VA-9196 - Errors are displayed while uninstalling VA 1.2.3 build.
• VA-9194 - Bootstrap user details are missing on service monitor in case of roll forward scenario.
• VA-9193 - The MySQL service gets deleted when rollback occurs after a failed upgrade.
• VA-9167 - Deadlock issues in va log file.
• VA-9164 - Tomcat version 8.5.15 had the following vulnerabilities:
  • Severity 5: CVE-2017-12617 - Apache Tomcat Remote Code Execution Vulnerability
  • Severity 3: CVE-2019-10072 - Apache Tomcat Denial of Service Vulnerability

  Tomcat is upgraded to version 9.0.34.

• VA-9134 - Crosswalk table (cwunit) did not get updated if the unit/department is moved to a different facility or unit/department name is updated.
• VA-9133 - Duplicate entry for key 'PRIMARY' error in va log.
• VA-9116 - Wildcard mask not honored to identify access point location name.
• VA-9096 - Unknown facilities listed users that were already mapped to existing departments.
• VA-9093 - Logout is not captured when a user logged in from a device and automatically logged out from another device.

The following issues are fixed in Vocera Analytics 1.2.3:

• VA-9128 - The default action for monitoring pipeline was set to Notify_And_Stop, which caused the Vocera Analytics services to stop. This issue is fixed now. The default action is now set to Notify_And_Restart.
• VA-9107 - The Vocera Analytics 1.2.2 installer could not connect to Mariadb Server. This issue is fixed now and is no longer seen.
  Note: The Vocera Analytics 1.2.2 installer is now replaced with the Vocera Analytics 1.2.3 installer.
• VA-9089 - Re-run of upgrade failed the when first time upgrade was interrupted due to insufficient disk space. This issue is fixed now and is no longer seen.
• VA-9023 - Facility search result did not show the entire range of existing facilities. This issues is fixed. Facility search now works as expected.
• VA-9016 - In Badge/Mobile Last Used and Badge Firmware reports, data overlapped to the next line when the location name was long. This issue is fixed now and is no longer seen.
• VA-9015 - Report calculations for Total Calls did not always match complete and incomplete calls. This issue is fixed.
• VA-9014 - After deleting old facilities from Vocera Analytics database (cwfacilities table), these schedules were not listed in the Scheduler page. This issue is fixed now as such schedules will be listed under Unknown facility.
• VA-9011 - Reports residing inside Interruption folder did not have a cover page when exported. This issue is fixed. All reports now have a cover page.
• VA-8988 - Vocera Analytics did not support Username (samAccountName) login and required DomainName\ prefix. This issue is fixed now as it is not mandatory to provide the DomainName\
• VA-8985 - NULL records were inserted when data was exported. This issue is fixed now as null records are no longer inserted.
• VA-8982 - Facility filter selection had a maximum limit of 10 filters. This issue is fixed. You can now select a maximum of 100 facilities.
• VA-8956 - The Vocera Analytics database consumed huge disk space during VMP normalization. This issue is fixed now.
• VA-8955 - A change in Site Name in Crosswalk table broke configured reports packages. This issue is fixed now and is no longer seen.
• VA-8949 - Large volumes of data took long duration to process and slowed down the performance of the Vocera Analytics system. This issue is fixed now as reprocessing is limited to 24 hours of data, thereby reducing the process time.
• VA-8938 - In Scheduler page, sorting based on Schedule caused confusion. This issue is fixed now as sorting is removed.

The following issues are fixed in Vocera Analytics 1.2.0:

• VA-8825 The max file size limit for scheduler package email attachment was 8000 KB. The user could not attach any package beyond 8000 KB. This issue is resolved as administrators can now configure the max file size limit.
• VA-8724 The Vocera Analytics Flume agent default port conflicted with Voice Server Nuance port. The default port for Vocera Analytics Flume agent is now reassigned to 7780. This issue is fixed.
• VA-8646 When the Vocera Analytics Checkpoint Directory on the Voice Server is too large, Flume agent stops sending data and Vocera Analytics services stop subsequently.
• VA-8481 The MariaDB Temp Directory consumed approximately 30% of hard disk drive when the environment was in Low on Disk Space state. This issue is fixed.
• VA-8299 A VMP source gets added into pipeline.json every time the user clicks the Add button in the service monitor, when there is an issue in the service monitor interface. This issue is fixed now and is no longer seen.
• VA-8188 Flume agent failed to pick the latest valid license file. This issue is resolved.
• VA-7904 Trusted URLs given in uppercase were not working. This issue is fixed now.
• VA-7822 The Vocera Analytics installer accepted passwords beginning with special characters that caused login errors. This issue is fixed as the installer does not accept passwords starting with special characters.
• VA-7805 Due to filter restrictions to display only 25 entries, not all filtered data was displayed for search criteria-based filters, such as Owner Group filter. The filter restrictions are now expanded to display 50 entries and this value is also configurable. Hence this issue is now resolved.
• VA-7691 Platform Health Index dashboard displayed B2000 data despite the facility not having any B2000 badge. This issue is fixed now.
• VA-7583 An error Recursion of EVENT DDL statements is forbidden is displayed in the install log while upgrading Vocera Analytics 1.0 to Vocera Analytics 1.1. This issue is fixed.
• VA-7171 Only one unit is displayed for the user in User Interruptions dashboard and exported CSV file when the user is assigned to more than one unit with the same unit name in different facilities. This issue is fixed now.
• VA-7126 Data loading error is displayed on unit-related dashboards when a unit is mapped using Manage Sites and crosswalk tables are not updated. This issue is fixed and is no longer seen.
• VA-7060 Incorrect port numbers are displayed for Flume agents of Engage, VMP, and Voice Server after an upgrade or an unplanned restart of Vocera Analytics server. This issue is fixed now. Incorrect port numbers are no longer seen after an upgrade or unplanned restart.
• VA-7046 Login event does not get updated when the user is already logged in to the badge and the same user is logged in to Vina without logging out from the badge. This issue is fixed now. Login event now gets updated accordingly.
• VA-6735 In certain situations, an error Could not start process is displayed in the monitoring log. This issue is fixed and is no longer seen.
• VA-6594 In Vocera Platform 6.0, Status Tracking dashboard does not display any data. This issue is fixed now. Status tracking dashboard now displays data.
• VA-4905 Date range was missing in exported Engage reports. This issue is fixed and is no longer seen.

The following issues are fixed in Vocera Analytics 1.1.0:

• VA-5379 - In Manage Users, after a user is imported successfully, the imported user is not displayed. You no longer need to refresh the browser to display the imported user. This issue is fixed now.
• VA-5309 - Instant Conference (Push To Talk) functionality is not supported. This issue is fixed now. Instant conference is now supported.
• VA-5067 - Breadcrumbs are not supported in Group Interruption dashboard in Firefox browser. This issue is fixed now.
• VA-4976 - The Report Scheduler does not send emails even to the correct email address if one of the recipient emails has an invalid email address. This issue is fixed now.
• VA-4971 - The drop down filters that contain multiple values with the same name are not differentiated to the user. This issue is fixed now.
• VA-4915 - Data migration is not supported for Simultaneous User Login report. This issue is fixed now and historical data are displayed.
• VA-4706 - The Location column is blank when the Access Point is not mapped to the location name in Asset Usage page. This issue is fixed and is no longer seen.
• VA-4689 - To display large datasets that include data for 1 month or all users, some dashboards or reports may take several minutes. Some of the dashboards that may take longer to display data are Integration Details, Location Statistics, User Activity Details, and User Call Details. This issue is fixed now.
• VA-4065 - Refreshing the browser incorrectly loads the landing page of Vocera Analytics. This issue is fixed and is no longer seen.