Skip to main content
Version: 1.3

Release Notes

What's new​

Data Model

  • Hunt Group number dimension and measures for Calling
  • Place number dimension for Calling
  • Transfer number for Calling
  • Voice mail forwards by user and place for Calling
  • CallCenterCall flag for Calling to filter out all CC related call legs
  • PhoneNumber mapping dimension for HuntGroup-, Place-, Redirect- and Transfer-Number
  • Deprecated fields from TaskLegDetails API removed in data model

Reports

  • New Hunt Group report for Calling
  • New Transfer Destination report for Calling
  • Place devices from Workgroups added to user reporting including slicer for "Place"
  • Separated and enhanced Calling user reports for Inbound and Outdial
  • Mobile layouts for Power BI mobile app
  • System info for datamart Monitoring report
  • Other small improvements

System

  • Performance improvements for data refreshes
  • SQL Managed Instance Monitoring report in Power BI

Important notes​

None

New Features​

This section lists new features or functionality for this version.

WXR-275 - Improve performance in views against FACTs

Requirements: Dimension views should deliver objects in shorter time when historical depth in system settings is reduced. The same should also apply to the fact views themselves.

Solution Abstract: Change order in where clause and filter the records first in order of the potentially lowest number of records before evaluating them with any logic.

Limitation: None


WXR-274 - Add a Transfer Destination report

Requirements: There should be a transfer destination report available based on the transfer number.

Solution Abstract: Create a new report including the measures for transfers and a sankey chart showing from where to where the transfers went. Use the PhoneNumber mapping to use the name of the transfer destination.

Limitation: None


WXR-273 - Add a CallCenterCall flag to filter all related call legs

Requirements: There should be a flag for calls from and to the Call Center if someone wants to exclude calls that are included in the WxCC reports already.

Solution Abstract: Add a flag "CallCenterCall" to all records where the first leg belongs to a Call Center call.

Limitation: This will not include calls that are going to the Call Center at a later stage.


WXR-269 - Create separate User reports for Inbound and Outdial

Requirements: Report "User Calls" should contain Users, Places and Date/Time Charts next to the grid report.

Solution Abstract: Add the additional chart visuals and separate the reports in "Inbound User Calls" and "Outdial User Calls" reports.

Limitation: None


WXR-267 - Add TransferNumber for transferred calls

Requirements: If a user transferred a call, we should evaluate the number of the transfer target

Solution Abstract: Add the InUserTransferNumber on the incoming leg, where the call was transferred by a user or place.

Limitation: None


WXR-266 - Improve performance for calling view vFACT_DETAILEDCALLHISTORY

Requirements: The evaluation of the Origin values costs most of the time for the data extract and should be optimized.

Solution Abstract: Optimize the view query to get the origin values with a single sub query using a table join and use the smallest LocalCallID to filter the first record of a call.

Limitation: None


WXR-263 - Add Place reporting for Calling

Requirements: Calls delivered and answered from workspace places should be included the same way as the user calls.

Solution Abstract: Include calls from places into all user calls. Add the PlaceNumber to be able to join the PhoneNumberMapping as a new Place dimension.

Limitation: None


WXR-262 - Update data freshness for Calling based on Cisco's data availability

Requirements: Data freshness for Calling should be measured from when the data is available from the CDR API.

Solution Abstract: Add 5 minutes to the timestamp when the call has ended. Because the "Report time" and "Release time" are the same timestamps and because we are using "Report time" to measure our data freshness, we will add the 5 minutes to the "Report time".

As for when the data is available for this API, it's mentioned here: https://developer.webex.com/docs/api/v1/reports-detailed-call-history.

"Detailed Call History information is available 5 minutes after a call has ended and may be retrieved for up to 48 hours. For example, if a call ends at 9:46 am, the record for that call can be collected using the API from 9:51 am, and is available until 9:46 am two days later."


WXR-261 - Add system info to Monitoring report

Requirements: There should be some additional information about the Webex tenant in the Monitoring report.

Solution Abstract: Add Webex org Id, Tenant Name, Datamart version, Deployment Date, Guest Account and SQL MI information as a new system info box.

Limitation: None


WXR-251 - Change monitoring report to "Import" mode for better performance

Requirements: The monitoring report should display the SLIs faster.

Solution Abstract: Change the mode from direct connect to import and configure the same refreshes as the normal datasets. Update this configuration in the webdoc for this report.

Limitation: None


WXR-247 - Enable "search" on all slicers by default

Requirements: The search box should be enabled for all slicers.

Solution Abstract: Enable the search functionality for all slicers.

Limitation: None


WXR-246 - Enable visibility of the Description field for all dimensions

Requirements: The Description field for Entry Points, Queues, Teams, etc. should be available in all dimensions because it could be filled with grouping strings.

Solution Abstract: Make the fields visible and include them in the documentation.

Limitation: None


WXR-243 - VoiceMail forwards by user and place

Requirements: It should be possible to measure the number of forwarded calls to VoiceMail by user and places.

Solution Abstract: Add the redirecting number in general to incoming calls. If redirecting calls end at a voice mail, set a "redirected to voicemail" flag for the leg where the call was redirected.

Limitation: The "redirected to voicemail" flag only works for scenarios where a TranferRelatedCallID exists. This is normally the case if users forward their extension to voicemail but it's not the case for calls that are redirected by routing flows like Huntgroups or local gateways etc.


WXR-241 - Hunt Group reporting for Calling


WXR-235 - Replace total calls with total incoming calls in Calling Overview report

Requirements: Total calls in Calling Overview is confusing because the same call can be counted as incoming and outdial call.

Solution Abstract: Replace the general total calls with total incoming calls.

Limitation: None


WXR-213 - Create a SQL MI Monitoring Report in Power BI

Requirements: There should be a report available in Power BI (b+s Operations workspace) where the DevOps team can see the Service Level Indicators (SLI) about how the CCBI services of every customer performed during the last 30 days and how the subscription was used.

Solution Abstract: Create a new report that provides the following SLIs for every customer datamart hosted on the SQL MI:

  • data availability
  • data freshness
  • service availability
  • service consumption

Also include the inventory of the customer databases and their orgId.

Limitation: None


WXR-91 - Create mobile layout


Bug Fixes​

This section lists bug fixes for this version.

WXR-264 - Deflected calls are part of User Outdial

Symptom: If a call gets redirected at a user extension, the redirected call is also included in the outdial calls of this user.

Conditions: User is called but the extension is forwarded to voicemail.

Workaround: None

Further Problem Description: Outdial calls at user level should only include calls where the user actively dialed.