General Limitations

The general limitations lists the issues and limitations of Vocera Analytics under certain circumstances. Use this topic to understand the limitations of the Vocera Analytics product.

The following are the general limitations of Vocera Analytics:

Number Format issue:
- Number format is not displayed as expected in reports for English-Germany locale.
- Number format does not display as expected in reports for English-South Africa locale.
- The number format is not displayed as per the set localization in the following dashboards:
  - Group Interruptions
  - Inventory Status
  - User Interruptions
Date Format issue:
- Utilization dashboard CSV file does not display the date in ISO format.
- Date format is not displayed as expected in dashboards for English-Singapore, Australia, and Malaysia locale.
- Date format is not displayed as expected in reports for English-Canada locale.
- CSV file of dashboards that contain trends does not display the date in ISO format.
Data display issue:
- For Voice Server 5.3.2 and VS 5.3.3, the Smartbadge firmware version should be 5.0.2 and above. In case the firmware version is below 5.0.2, device activity events will not be generated and the user will be shown as Inactive. Also, asset-related dashboards and reports will not show correct data. In such cases, it is recommended that you upgrade the firmware version to display correct reporting in Analytics.
- 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.
- Rejected call entry is also considered as a dropped call when the first user rejects the call, second user accepts the call, and call gets dropped from the caller side.
- Data for the last minute of the day, that is, 23:59:00 to 23:59:59 is not considered for calculating the activity.
- The FinishedAt time for Broadcast calls displays incorrectly when a user disconnects before the Broadcast call ends.
- Data is not displayed as expected for Conversation Type and Conversation Subject columns in VMP messages table when another user is added to the conversation or subject is changed before normalization is run.
- Special characters such as double quotes and backslash used in the subject field of VCS conversation are not displayed appropriately in the Vocera Analytics database.
- If you are trying to call a group, and if the group name is not recognized, data for the subsequent call may be incorrect.
- In certain scenarios, call duration of a broadcast might not be accurate, if receiver of the broadcast disconnects before the broadcast ends.
- When an alarm is sent to a user logged in to a badge and Send Accepted Notification rule is enabled for Vocera Component, additional interruptions are generated to each user in the escalation that the notification was accepted.
- Two entries are created in the database when a user rejects a call and multiple users are available with the same display name.
- Talking duration is displayed for incomplete telephone calls and telephone calls not received by a user are considered complete.
- Speech count does not match in Speech Statistics and User Statistics dashboards when a unit is selected and the user initiated genie from phone and device.
- If a user is removed from a department or moved to any other department, it still considers the department from which the user is removed.
- Asset Details dashboard may not show correct data for VCS device, if the device information is not added through Vocera Voice Server admin console but is directly connected to Voice Server. However, this issue gets rectified within 24 hours.
- In Integration Events dashboard, when a VMI message is responded more than once, the timestamp for Event Reply Time between CSV report and dashboard differs. This happens because the timestamp for CSV considers the time that the user responded first, whereas the dashboard timestamp considers the latest response time.
- If you assign access point location through a voice command, it may take 24 hours to reflect this information in Vocera Analytics.
- If two users from different facilities are logged in with the same name and if one user is active and the other user is inactive, still both users are considered as active. This issue is seen in Login dashboard and Inactive Users report.
- In Vocera Platform 6.1, if only Engage is configured, Vina messages are displayed against Unknown facility in the following dashboards and reports:
  - User Activity Details dashboard
  - Use Activity report
  - User Interruptions dashboard
  - Conversation Activity dashboard
  - Message Details dashboard
  - Conversation Summary dashboard
- The Party Involved column in User Activity Details dashboard and report displays the name of the user that left the conversation if the username falls within the filtered date range. To view the correct data, select the From Time filter value after the user left the conversation.
- If selected date range is more than a week, Integration Group Activity report takes longer to load the data. To load data faster, apply filters specific to your search.
- Device Status filter for Badge/Mobile Last Used Report filters display devices based on the latest status of device and not on historic status of the device.
System Issue—The Tomcat temp files located in InstallDrive/VoceraAnalytics/tomcat/temp are not deleted automatically This causes the temp folder to increase in size. Workaround: Restarting the reporting service resolves the issue.
Communication between de-coupled servers fail when the servers are not on the same domain.