This section summarizes the new features in this release.
This section summarizes the new features in the 4.4.2 release.
Improved: Windows Server 2012 Support – The Vocera Server is now supported on the Windows Server 2012 platform. On Windows 2012, you must use "Run as administrator" to start the Vocera Server and to edit any text files that the server uses. For best results, use the Services window to start the Vocera Server.
The Vocera Report Server, Vocera SIP Telephony Gateway, and Vocera Client Gateway are also supported on the Windows Server 2012 platform. The Vocera Telephony Server requires Windows Server 2008 or 2003.
Improved: 3rd Party Software Support – The following 3rd party software updates are available with this release:
Tomcat 7.0.52
Apache 2.2.25
MySQL 5.1.73
The following list contains fixes and improvements made to the Vocera Report Server product.
Enhanced: Reports that were deprecated in Report Server 4.3 have been removed –The following deprecated reports are no longer available and have been replaced by newer reports. Make sure you update any scheduled report packages that use these reports.
| Report removed from Report Server 4.4.0 | Use this report instead |
|---|---|
|
Summary Reports > VMI Message Activity |
Integration Reports |
|
Summary Reports > Speech Recognition Distribution Chart |
Speech Reports > Speech Recognition Distribution Chart |
|
Diagnostics Reports > Recognition Results by User |
Speech Reports > Recognition Results by User |
|
Diagnostics Reports > Recognition Results by Access Point |
Speech Reports > Recognition Results by AP |
|
Diagnostics Reports > Low Recognition Results By Access Point |
Speech Reports > Recognition Results by AP |
|
Diagnostics Reports > Recognition Results by Device |
Speech Reports > Recognition Results by Device |
|
Diagnostics Reports > Low Recognition Results by Device |
Speech Reports > Recognition Results by Device |
|
Diagnostics Reports > Recognition Results by Device |
Speech Reports > Recognition Results by Device |
|
Diagnostics Reports > Low Recognition Results By User |
Speech Reports > Recognition Results by User |
|
Diagnostics Reports > High Recognition Results By User |
Speech Reports > Recognition Results by User |
|
Custom Reports > Login-Logout Report |
Call Reports > User Activity Report (select Login/Logout for the Activity Type parameter) |
Fixed: VRS dataload should fix wildcarded access points in the database to report Unassigned APs correctly – An issue where the Unassigned APs report did not include access points that were specified by wildcard, is now resolved. (Issue 17597)
Fixed: Badge Usage report returns an empty data set – An issue where the Badge Usage report returned empty data, is now resolved. (Issue 18843)
Fixed: Device Last User Access report data cannot be exported – An issue where the Device Last User Access report data could not be exported from the Vocera Report Server, is now resolved. (Issue 19721)
Before installing this release, make sure one of the following Vocera products is installed:
Vocera Report Server 4.4 or 4.4.1
After you install one of the prerequisites, you can install this service pack by following the instructions listed below.
To install this service pack, you must log in to the computer using an account with administrator privileges.
It takes approximately 20 minutes to install this service pack. However, after installation the server will be down while you restore data from a backup file. The time it takes to restore data varies based on the size of the data set. The following table provides estimated database restore times for different size backup files.
| Backup File Size (MB) | Estimated Restore Time |
|---|---|
| 50 | 45 minutes |
| 100 | 1 hour 15 minutes |
| 200 | 2 hours |
| 400 | 4 hours |
Make sure you have a recent backup of Report Server data. If you schedule daily backups, you can use the backup from the previous evening. You will need to restore data from this backup file after you install the update.
If you do not have a recent backup of Report Server data, create one now.
To back up your Report Server data:
Select the Backup task, and then click the Run Task button.
A message box opens to confirm you want to run the task.
Click OK.
The Run Task dialog box appears.
Specify the maximum number of backup files to maintain (the default is 10), and then click Run Task.
The Status dialog box appears.
If you experience any problems installing the update, please contact your Vocera Support provider for assistance.
To install the update:
Close all applications.
Create a folder called VoceraReportServer442 and download the self-extracting executable for Vocera Report Server to it.
Open the folder and run the executable.
Respond appropriately to any install wizard prompts to install the update.
When you are finished, the install wizard prompts you to restart the Vocera services. Click Yes.
After the Vocera services are started, click OK.
After service pack installation is complete, you can optionally check the log file located in the \InstallLogs-Vocera directory. The log file is named Vocera_Report_Server_4_4_2_Installer.log.
If a department group does not have sub-departments, calls made to the department group do not appear in the Incoming Calls to Groups reports - Workaround: Create a sub-department. After a dataload occurs, the reports will correctly show calls to the parent department. This issue is fixed in VRS 4.4.3. (18825)
In some situations, the Incoming Calls to User - Detail report does not show the caller's phone number - If the phone number of the incoming call is not associated with a Vocera user, the phone number does not appear in the report. This report should show phone numbers when they are avaialavle, regardless of whether the caller is a Vocera user. This issue is fixed in VRS 4.4.3. (18792)
In a high-availability telephony environment, the Telephony Usage Trend report may incorrectly represent the maximum number of ports in use - When one VSTG in an array fails, the report displays the number of available lines in the Max Number of Ports in Use field, instead of calculating and displaying the number of ports. This issue is fixed in VRS 4.4.3. (20407)
Problem printing reports to a printer with default A4 page size – If the default printer you have selected has an A4 page size, when you print a report to PDF characters along the right edge may be truncated. (15695)
Workaround: Change the page size for the printer to Letter size (8.5 x 11 inch), print a report to PDF, open the resulting report, and use page scaling (also called Fit to Printable Area) feature of your printer driver to print the file to an A4 size page.
Report Server backup does not exit and report failure if you run out of disk space – If the Report Server runs out of disk space while it is running the Backup task, the server does not exit the task or send an email alert notifying you that the Report Server disk is full. When the server runs out of disk space, subsequent backup files are incomplete. (Issue 20578)
Workaround: Schedule a monthly Report Server task to archive data older than six months and purge that data from the database. Performing such regular maintenance helps keep your Report Server running smoothly.
After a restore from archive, all items in the Report Scheduler are listed twice. - When you restore a VRS archive file all scheduled reports will be duplicated. (23601)
Workaround: Delete the duplicated scheduled reports.
Integration group report doesn't show users with different home sites receiving messages - If an integration message is sent to a group containing users with different home sites from the group’s configured sites then message activity for those users will not show up in the Integration Messages Group Activity Reports. (23183)
Workaround: Move the users to the same home site as the group.
Cannot filter by user when site name has been changed - If a site name has been changed on the Vocera server the option select a user when filtering by site will no longer be available for the site whose name has changed. (20071)
Workaround: Change the site back to the original name and perform a dataload on the report server.