Documentation Announcements for Vocera Analytics Release 1.2.0
Beginning this release, the upgrade and install sections are documented in a separate
guide—Vocera Analytics
Installation Guide. This new guide provides an installation workflow, a step-by-step
installation procedure, and the corresponding configuration information for different
scenarios based on your setup.
Note: The Vocera Analytics
Administration Guide will no longer include the upgrade and installation sections.
About Vocera Analytics
Vocera Analytics provides a
comprehensive view of all interruptions encountered by caregivers. Interruptions include voice
calls, text messages, and alarms and alerts from clinical and operational systems. Vocera Analytics enables clinical
leaders to review performance metrics, conduct comparisons, measure success rates, and
identify areas for improvement. Based on this information, dashboards and reports can be
constructed to monitor and drive continuous improvement.
Vocera Analytics comprises the
following functionalities:
Dashboards—Display data based on defined metrics and key performance indicators
(KPIs) that you can analyze and track.
Reports—Provide logs that the Vocera Voice Server supplies. These
reports allow you to understand your usage of the Vocera products and optimize the
deployment of your organization.
You can find documentation for this version of the product by clicking the question mark (?)
in the header pane on all the pages of the Analytics console.
You can also access the following Vocera Analytics documentation
directly from a web browser without being logged in:
Before you install Vocera Analytics, your environment must contain the necessary prerequisites. The size of your server
normally depends on the number of users that reference it and the number of beds at your
site.
Vocera Analytics hardware
prerequisites:
The details on the hardware requirements for the Vocera Analytics Server database are as
follows:
Note: The requirements are different for small, medium, and large servers.
Small
Medium
Large
Memory
32 GB
64 GB
128 GB
CPU
Octa-core
Octa-core
12 Core
Disk Space
500 GB HDD (per year) with SSD Cache
1 TB HDD (per year) with SSD Cache
2 TB HDD (per year) with SSD Cache
Operating System
Windows Server 2016
Windows Server 2012
Windows Server 2016
Windows Server 2012
Windows Server 2016
Windows Server 2012
Browser Support
Internet Explorer 11, Firefox version 45.0.1.0
or later, Safari 11.1.2 or later, Google Chrome version 70 or
later (JavaScript must be enabled).
Database (provided)
MariaDB (MySQL)
MariaDB (MySQL)
MariaDB (MySQL)
Note: To run properly, the Vocera Analytics Agent running on a Vocera Voice Server (VS) / Vocera
Platform 6.0 will require 2 GB of RAM when interacting with a small or medium Vocera Analytics
Server database and 4 GB of RAM when interacting with a large Vocera Analytics Server
database. If the VS does not have sufficient memory to meet the mandated minimum memory for
the VS plus the needs of the Vocera Analytics Agent, memory will need to be added to the VS.
For example, a VS running version 5.2.3 requires a minimum of 8 GB of RAM. If the Vocera
Analytics Agent will be interacting with a large Vocera Analytics Server database requiring 4
GB of RAM, the server running the VS and the Vocera Analytics Agent must have a minimum of 8 +
4 or 12 GB of RAM installed. If it does not, sufficient RAM to meet or exceed the 12 GB
requirement should be added. If the VS is running in a virtual environment, Memory Over
Subscription is not supported and the Host Server should have sufficient physical RAM to
support the memory allocated to the Guest Servers plus the Hypervisor.
Validation Metrics: Performance Expectations
Reports and Dashboards: One month of data displays in 10-15 seconds
Data Exports: 30–45 seconds
Data Inputs
Small
Medium
Large
Vocera Voice Server Users
450
2000
5000-20000
VMP Users
200
3000
10000
Beds
293
500
1000
Engage users
450 (225 per shift)
1000 (500 per shift)
2000 (1000 per shift)
Clinical Alarms
2200
5000
9500
Nurse Call Alerts
3200
11000
22000
Orders
400
1200
2400
Lab Alerts
24
75
150
VMI Messages
2000 messages/day
10000 messages/day
60000 messages/day
Calls Per Day
2000 calls/day
10000 calls/day
60000 calls/day
VCS Messages
9000 messages/day
40000 messages/day
400,000 messages/day
Vocera Analytics software
prerequisites:
To use the Vocera Analytics Server database, you must have the necessary software version
available:
Vocera Voice Server version 4.4.4 -
5.4.
Engage Platform version 5.5 and later, with EMDAN version 1.9x and later.
Vocera Messaging Platform version 5.2.2
- 5.4.
Note: All three systems (Voice Server, Engage Platform, VMP) are not required.
Standalone Voice Server and standalone Engage Platform are supported. However only VMP as
a source is not supported. Minimum system level versions are only applicable if previously
installed or an installation is pending. Vocera Analytics will collect data from each of
these systems only if installed.
Vocera Platform 6.1 - 6.3.
Data Export Adapter 1.4.1 SR1
Crystal Reports 2016 and MySQL Connector or ODBC 3.51 driver.
Important: Do
not install Crystal Reports Server on the same machine as Vocera Analytics Server. Vocera
Analytics Server has not been certified to work on computers where Crystal Reports Server
is also installed. You must also set up an ODBC data source.
Other Considerations
To use Vocera Analytics, you must consider the following product requirements:
A license SKU.
You can order the SKU from your Vocera Account Representative.
Vocera Analytics is the upgrade path for both Vocera Reporting Services and Engage Reporting.
It is available for all Vocera systems (Standard or Enterprise License) and includes data
migration for both VRS and Engage.
Infrastructure Considerations
To use Vocera Analytics, you must consider the following infrastructure requirements:
New VM or physical server. You cannot re-purpose the Vocera Reporting Server (VRS)
Third-party licensing: Windows 2016 OS only (No SQL Server)
Note:
New Crystal Reports desktop license is included.
You can use the previous reporting systems (VRS and Engage) side by side. Vocera
recommends that you move to Vocera Analytics to use all the enhanced features.
New and Enhanced Features
This section summarizes the new features and enhancements in this release.
New and Enhanced Features in Vocera Analytics 1.2.3
Vocera Analytics 1.2.3 is a maintenance release only. It contains no new features.
New and Enhanced Features in Vocera Analytics 1.2.0
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.
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.
New and Enhanced Features in Vocera Analytics 1.1.0
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.
New and Enhanced Features in Vocera Analytics 1.0.0
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.
Install Vocera Analytics Remote Agent 1.2.3 HF on the Voice Server
Ensure that VA 1.2.0 or VA 1.2.1 is installed.
Ensure that all services are stopped before installing Vocera Analytics
1.2.3.
Ensure that the installation drive has enough disk
space.
Note: VA 1.2.3 installer is applicable only for Windows machines. VA 1.2.3 installer is
not applicable for custom installation.
To install the remote agent on the Vocera Voice Server, perform the following
tasks:
Note: The Vocera Analytics Suite installs both the remote agent for Voice Server and
Vocera Analytics.
Login to Service Monitor using the link https://:9445/.
On the configuration page, click Stop All
Services.
Copy the iso file/installer to the install drive on the Voice Server machine
and extract the file.
Note: Ensure that you perform on both Active and Passive Voice Servers.
Right-click VoceraAnalyticsInstaller.exe> Run
as administrator to launch the installer.
The installer Welcome to the InstallShield Wizard for Vocera
Analytics Suite 1.2.3 screen appears.
Click Next.
The Initialize a Configuration Backup screen
appears.
Click Backup Cfg.
The installer takes a backup and displays the Ready to
Install screen.
Note: Do not close any installer windows that
appear during backup.
Click Install.
The Installation Progress window appears. Do not close
any installer windows that appear during installation.
Click Finish.
The InstallShield Wizard Completed screen
appears.
To validate that the remote agent is upgraded successfully and to check if the
service monitor is installed and running, use the
services.msc. The slave service monitor installed here
is used to interact with the master service monitor of the Vocera Analytics
server.
Note: In case of Voice Server cluster, you must upgrade the flume
agent on both nodes (active and standby) in the Voice Server cluster.
Perform the above steps to upgrade the flume agent on each node of the
cluster.
Install Vocera Analytics 1.2.3 HF on the Analytics Server
Ensure that Vocera Analytics 1.2.0 or Vocera Analytics 1.2.1 is installed.
Ensure that all services are stopped before installing Vocera Analytics
1.2.3.
Ensure that the installation drive has 3 times the space of VoceraAnalytics
folder available to proceed with the installation.
Note: Vocera Analytics 1.2.3 installer is applicable only for Windows machines. Vocera
Analytics 1.2.3 installer is not applicable for custom installation.
To install the Vocera Analytics Suite on the Vocera Analytics Server, perform the
following tasks:
Login to Service Monitor using the link https://:9445/.
On the configuration page, click Stop All
Services.
Right-click VoceraAnalyticsInstaller.exe> Run
as administrator to launch the installer.
The installer Welcome to the InstallShield Wizard for Vocera
Analytics Suite 1.2.3 screen appears.
Click Next.
If VMP pipeline is configured
The Select the VMP versions to backup
screen appears.
Browse to the VMP version that you want to backup.
Click Next.
If VMP pipeline is not configured
The Database Backup Option screen
appears.
Note: This screen appears only on systems that have VMP configured.
Click Next.
The Database Backup Option screen appears.
Select an option:
Backup the database and configuration
files—Select this option to backup both the database and
configuration files.
Backup configuration files only—Select this
option to backup only the configuration files.
Click Next.
The Verifying Disk Space screen appears. The
verification may take several minutes depending on the size of your
database.
Note: The installer requires 3 times the space of VoceraAnalytics folder to be
available on the installation drive to proceed with the installation.
This screen appears only when you select Backup the
database and configuration files option.
Click Next.
The Initialize a Database Backup screen appears.
Click Backup DB.
The installer takes a backup and displays the Ready to
Install screen.
Note: Do not close any installer windows that
appear during backup.
Click Install.
The Installation Progress window appears. Do not close
any installer windows that appear during installation.
Click Finish.
The InstallShield Wizard Completed screen
appears.
Upon successful installation, the ServiceMonitor
service automatically restarts and launches the Service Monitor Dashboard
page.
From the downloaded media extract, right-click
VA_1.2.3_template_patch_7.exe and select Run as
administrator.
The installer is launched, and the installer Vocera Analytics
Server 1.2.3 template_patch screen appears.
Click Yes to install the patch.
The patch is installed and a command window appears.
Type Y to view the logs.
Upon completion, go to Service Monitor on Vocera Analytics server and click
Start All Services after both Vocera Analytics server and Voice
Server are upgraded.
Troubleshooting Vocera Analytics 1.2.3 HF
If the VA 1.2.3 hot fix installer is still running and the machine reboots abruptly,
then perform the following:
Uninstall Vocera Analytics suite completely.
Install Vocera Analytics 1.2.0 version.
Restore the backup.
Upgrade to VA 1.2.3 hot fix again.
Install Vocera Analytics 1.2.1 HF on Vocera Platform
When you upgrade from VA 1.2.0 to VA 1.2.3 version, you must apply the VA 1.2.1 hot
fix manually on the Vocera Platform server by using the following steps.
Note: If
you are already using VA 1.2.1 version, the following steps are not required.
To install the Vocera Analytics Suite on Vocera Platform, perform the following
tasks:
Copy VA1.2_HF_1 hot fix.
Stop Service Monitor service using the command:
sudo systemctl stop va-monitoring
Browse to <VS_Install_Drive>/VoceraAnalytics/servicemonitor/conf/,
open the appliation.conf file, and add the following line at the
end:
monitor.pipeline.autoRecoveryCount = 3
Save and close the file.
Open the terminal and change the directory to hotfix directory.
Change the file permission for the file VA1.2_HF_1.sh by executing the
following command:
chmod 755 VA1.2_HF_1.sh
Run the hotfix VA1.2_HF_1.sh by executing the following command:
sudo sh VA1.2_HF_1.sh
Start the Service Monitoring service by running the following command
sudo systemctl start va-monitoring
Fixed Issues
The following list contains fixes and improvements made to the Vocera Analytics in this release.
Fixed Issues in Vocera Analytics 1.2.3
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.
Fixed Issues in Vocera Analytics 1.2.0
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.
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-7046)
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.
Fixed Issues in Vocera Analytics 1.1.0
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.
Known Issues
This release includes the following known issues:
Vocera Analytics Release 1.2.3
The following list is specific to Vocera Analytics 1.2.3:
VA-9193 The MySQL service gets deleted when rollback occurs after a failed
upgrade. Workaround: To rectify this issue, refer to KA 8044.
VA-9170 The Vocera Analytics 1.2.3 HF installer fails while taking a
configuration backup when upgrading Flume Agent VA 1.2.0 to VA 1.2.3 on Voice Server.
Workaround: To rectify this issue, refer to KA 8054.
VA-9164 Tomcat version 8.5.15 has the following vulnerabilities:
Severity 3: CVE-2019-10072 - Apache Tomcat Denial of Service Vulnerability
VA-9154 The Voice Server Flume entry does not appear on service monitor
statistics page after upgrading to VA 1.2.3. Workaround: To rectify this issue,
refer to KA 8046.
VA-9134 Crosswalk table (cwunit) does not get updated if the unit/department is
moved to a different facility or unit/department name is updated.
VA-9064 The Group column in Details widget of User Interruptions dashboard is
blank and does not display the distribution list name when a message is sent to any VMP
distribution list.
VA-9062 Messages sent to VMP distribution lists are not displayed in Group
Interruptions dashboard.
VA-9044 An error message, Internal Error, is displayed
when the user attempts to expand any report in Interruptions folder after disabling SSL
for visualization and reporting server.
VA-9043 The department name in Department Summary and Mobile Activity Department
reports is displayed beyond its column length.
VA-9021 Call duration data is incorrect for the first call when the user puts the
first call on hold and accepts the second call when Vocera Platform 6.2 is the source.
VA-9020 An additional call is shown when a call is made to a group and
Member Name - Singular is provided for that group when Vocera
Platform 6.2 is the source.
Vocera Analytics Release 1.2.0
The following list is specific to Vocera Analytics 1.2.0
VA-8838 Mariadb and Reporting Service of the Visualization Server displays the
message Port is not configured for this service after upgrading
from Vocera Analytics 1.0 to Vocera Analytics 1.2.
VA-8819 Invalid Up Time is displayed for services after
upgrading from Vocera Analytics 1.0 to Vocera Analytics 1.2. Workaround: Clearing
the browser cache resolves the issue.
VA-8801 Login and Logout events are not captured if the user is off-prem.
VA-8765 - When a VMI message is sent to a group, the group site is displayed
instead of user site in Integration Message User Activity Report.
VA-8729 - In Vocera Vina, data loss occurs for Device Inventory when the user
updates the status of multiple devices at the same time.
VA-8719 - Date format is not displayed as expected in reports for English-Canada
locale.
VA-8711 - The Department field displays No Department
Assigned when the user updates any group or creates a buddy on Voice Server
User Console in Tiered Administration Audit report.
VA-8680 - For date range filter that do not have a time part, "Last x
days" will consider current day + previous x days. For example, Last 7 days
will be considered as current day + previous 7 days.
VA-8668 - No user record available! message is displayed in
Import Users page when only few users are selected and assigned
roles from the displayed list.
VA-8535 - Due to a firmware issue, user activity for certain users are displayed
as Inactive in Login dashboard.
VA-8219 - Communication between de-coupled servers fails when the servers are
not on the same domain.
Vocera Analytics Release 1.1.0
The following list of known issues are existing from Vocera Analytics 1.1.0
VA-7044 - In Vocera Platform 6.0, receiver device details are not displayed when
a call to address book is made.
VA-6906 - Calls made to an extension using the keypad from Vocera Vina
application is not captured.
VA-6699 - Failed jobs are not generated and hence the user is not notified when
Flume is down after Flume and Spark are started.
VA-6531 - Restarting service monitor service requires logout and login to the
configuration user interface.
VA-6450 - Vocera logo and menu are not displayed when the user refreshes the Web
browser in Report Scheduler and User
Management screens.
VA-6421 - In Vocera Platform 6.0, the Device Types filter
in visualization server does not include Vocera Vina.
VA-6361 - Date format is not displayed as expected in dashboards for
English-Singapore, Australia and Malaysia locale.
Vocera Analytics Release 1.0.0
The following list of known issues are existing from Vocera Analytics release 1.0.0
VA-5433 - Calls from a telephone and to a telephone will be shown in Unknown
facility and Unknown unit in dashboards and reports of Interruptions and Systems Usage.
VA-5409 - In User Interruptions and Group
Interruptions page, the group ID is displayed instead of group name for
email messages.
VA-5392 - If two users with the same first name and last name exist and both
users belong to the same facility and unit but are in different groups, a data count error
occurs. The database and the dashboard counts the data as one instead of two when a group
call or broadcast to the unit is done.
VA-5373 - Broadcasts calls made from telephones do not have group information and
are displayed as Unknown or Null in dashboards and reports.
VA-5207 - The Unit Summary widget does not sort
alphabetically for units of the same name from different facilities in Interruption
Summary dashboard.
VA-5179 - The Day field displays 31 days irrespective of
the month selected in Schedule section of Add Package page.
VA-5154 - The Summary by Owner Facility widget considers
device activity with time but Details widget considers only the
date for device use status in Inventory Status dashboard.
VA-5117 - Login activity for users with same first name and last name in same or
different facilities might not be accurate in User Activity Details dashboard and report,
Login dashboard, and Inactive Users report.
VA-5102 - In situations where two users with the same name are logged in, and one
user logs out, then the logout information is displayed incorrectly in User Activity
Detail dashboard.
VA-5074 - The Source Details widget displays Interrupt
Type, Priority, and Description even for data with 0 count in Unit Interruption Report.
VA-5073 - Reports cannot be scheduled after the current session expires.
Workaround: Log out and log in again to schedule a report.
VA-5064 - Filter selection is carried forward from one dashboard to another even
when a filter is not applied.
VA-5022 - Mobile User Activity and Mobile Unit Activity Reports show a lower text
message count when events escalate.
VA-5008 - In certain scenarios, an error message is displayed in a pop-up window
in Unit Summary Report. However, you may ignore the error message and close the pop-up
window.
VA-5004 - Sending a voice message to group or unit with similar names in same or
different facilities might not be accurate in Group Usage dashboard and Group Activity
report.
VA-4983 - In the Vocera Analytics Server, after an Engage source is setup with an
invalid database hostname, it cannot be updated to a new value. Workaround: Remove
the Flume agent and rebuild it.
VA-4873 - Report and Dashboard filters do not maintain dependencies. In certain
scenarios, even if a filter is available and selected, the generated report may not
display any data.
VA-4784 - While sending a text message from an email to Voice Server users or
groups, the user ID or group name (created in Voice Server) mentioned in email subject
line must be case sensitive for Vocera Analytics to process the data correctly. Else the
message interrupts will be missing.
VA-4720 - Incorrect data is displayed for calls made to Groups with same name
from a different facility.
VA-4719 - The warning pop up window in Reports does not close automatically even
after you navigate to other pages.
VA-4667 - The option Unknown is not available in
Access Point Locations filter in Speech Recognition Location
Details Report.
VA-4398 - In certain scenarios, Reports display http error.
Workaround: Refreshing the Web page resolves the issue.
VA-4304 - The name of the user appears three times instead of once when a desktop
message is sent to a selected user that is associated to a group and a unit associated
with the respective group.
VA-4301 - The Add package page is displayed from the middle of page if you scroll
down the Report package page and click Add package.
VA-3798 - In Vocera Messaging Interface (VMI), if a client uses the same message
ID for different messages, dashboards may show inconsistent data. Workaround: For
every client ID, ensure that the message or alert sent through VMI has a unique message
ID.
VA-256 - The Call Forward functionality is not entirely supported.