Skip to main content
Version: 1.5

Release Notes

What's new

Contact Center

  • Making fact tables and taskLegId visible again (custom filtering and data comparison)
  • RONA enhancements (new fields that Cisco provided with this feature)
  • YoY % Measures and visual updates (new KPI visual)
  • Additional max. measures
  • Set missing end time to start time to include incomplete tasks
  • Data import filter to reduce the scope of the purchased service
  • CC Forwarding measures for tasks and contacts
  • Measure updates due to GA testing of taskLegDetails API (separated consult legs and transfer completed legs)

Calling

  • Calling data model update to support same number per Location
  • Improve fact view performance by extracting data during ETL process
  • Data import filter to reduce the scope of the purchased service

System

  • Supporting custom user domain for RLS in Power BI
  • Real Time usage monitoring
  • Concurrent agents monitoring (new license model)
  • Monitoring dataset performance improvements by extracting all monitoring data
  • Converted Bing map visuals to Azure Maps visual
  • Connection parameters in datasets
  • Several performance improvements and bugfixes

Important notes

None

New Features

This section lists new features or functionality for this version.

#365 - Use parameters for dataset connection


#364 - Remove sys_get_min_createdtime


#360 - Update FQDN for CDR API


#358 - Add new fields from taskLegDetails API


#355 - Create separate file group for facts


#353 - Measure updates due to GA testing of taskLegDetails API


#352 - Set missing end time to start time


#351 - Convert Bing map visuals to Azure Maps visual

Description: Bing map visuals will be removed from Power BI Desktop by November 2025.

Requirements: Migrate all map visuals that are used in reports to Azure Maps.


#348 - Improve performance of monitoring process


#347 - Align data retention time to Webex premium tier of 3 years


#343 - Improve performance by decoding calling ids in staging procedure


#342 - Improve procedure staging_calling_Group_Member


#341 - Improve procedure staging_calling_People


#340 - Improve performance of Intraday and real time load procedures


#338 - Review and update indexes and optimize query performance based on index seek


#335 - Supporting custom user domain for RLS in Power BI


#333 - Making fact tables and taskLegId visible again


#331 - Store Calling results in fact table to support large deployments


#326 - Move load fact dimensions to a nightly execution


#325 - taskLegDetails API GA re-testing


#322 - RONA enhancements

Description: RONA is measured from the not-reponding event of agent activity today, because no RONA field was available. On July 24 2025 Cisco enhanced the RONA feature by separating real RONA timer counts, rejects and errors and included those fields in the API.

Requirements: We need the same RONA detail counting as available in Analyzer.

Proposed solution: Add all new fields from the tasklegDetail API and add the task RONA, rejected and connect error counts as new measures also for Intraday and RealTime. Keep the existing Agent RONA because it provides the RONA per agent. The RONA count for tasks does not count the RONA and rejects for the correct agent. This is just an overall count and does not create a leg for every agent being involved.


#321 - Update rate limit for People API


#320 - Reorganize ETL job and remove multi tenant execution loops


#318 - Improve load procedure for license assignment


#317 - Data Import Filter


#316 - Only keep integer values of system settings in PBI model


#314 - Update monitoring to support concurrent agents (WxCC only)


#311 - Direct Query Monitoring for Intraday & Real Time


#304 - Remove select function within load dim procedures for variables


#302 - Improve to refresh the datasets for upgrades


#297 - Add new measures with max values for several KPIs

Description: Max values are only available for the Wait Time but not for agent KPIs

Requirements: We should also have the max values where we have the averages

Proposed solution: Create the following new Inbound and outdial measures in (s) and (hh:mm:ss):

  • Max. Handle Time
  • Max. Hold Time
  • Max. Talk Time
  • Max. Wrapup Time

#281 - Contact Center Forwarding

Description: We should be able to measure forwarded tasks and contacts.

Requirements: We should be able to measure forwarded tasks in general. If possible from where and when they are forwarded (selfservice/queue).

Proposed solution: Add Forwarded and Forwarded % as new measures as part of the Total Inbound Service Tasks/Contacts and add it to all visuals.

Add Selfservice Forwarded for contacts (where this handle type is available).


#274 - Remove Intraday View vFACT_TASKDETAILS_INTRADAY


#119 - Create YoY % measures

Description: The formula for YoY sales growth is period sales, minus sales for the same period last year, divided by sales for the same period last year.

Requirements: Next to the Last Year measures there should also be the year-over-year comparison in percentage.

Proposed solution: Create the YoY % measure for all existing LY measures.


Bug Fixes

This section lists bug fixes for this version.

#345 - Procedure staging_calling_LicenseAssignment does not work


#344 - Function "decodeBase64IdWithLenCheck" does not work for all licenses


#334 - Agent Comparison report contains wrong target value for Avg Handle Time

Symptom: Avg Handle Time KPI chart uses the total instead of the average value as target

Workaround: Changing the report and taking the avg field


#332 - Procedure "staging_AgentSession" loads duplicate records


#330 - Procedure staging_UserProfile does not give response from API


#329 - Update Calling data model to support the same numbers for different locations


#327 - Numbers in view vDIM_PHONE_NUMBER must be unique for the PBI model


#310 - Dial Number slicer not filtering data correctly

Symptom: The Dial Number dimension only filters the list of Entry Points instead of filtering the data.

Conditions: Data is not filtered per number, if several Dial Numbers use the same Entry Point

Workaround: Use the "destination" field instead of the Dial Number