Jump to: navigation, search

Billing Data Server Release Notes

Billing Data Server is part of 9.x starting in
Release Date Release Type Restrictions AIX Linux Solaris Windows
04/15/20 General X

Helpful Links

What's New

This release contains the following new features and enhancements:

  • CIM Platform billing enhancements:
    • A new metric, Genesys CIM Premise Users (cim_platform_users), tracks the number of unique agents having active sessions.
      This metric replaces the Genesys Customer Interaction Management Platform (seats_CIM) metric, which is discontinued. The new metric provides enhanced filtration and checking. (CBILL-3155)
    • A new metric, Genesys CIM Premise Places (cim_platform_places), tracks the number of unique agent places in the deployment. (CBILL-3325)
      The following dataset changes support the cim_platform_places metric:
      • New fields, (EndPointType, PlaceID, and IVRPortID) are added to the mm_sessions and voice_sessions (secondary_statements) datasets.
      • A new DN type (type 2, ACDPosition) is added to the dn dataset. (CBILL-3324)
  • Enabled-seat calculation enhancements — Whenever possible, BDS now uses the enabled seats detailed report for the previous day to calculate enabled seats metric for the processing date. Enabled seats detailed reports are stored in a local folder, as configured in the enabled_seats_detailed_dir variable in gvars.py. If the detailed report for the previous day is not available, BDS concludes that the metric was just enabled, and uses the files for the processed date only. Previously, to calculate enabled seats for any seats metric, BDS used all relevant datasets extracted since the first day of the month, which sometimes impacted BDS performance. (CBILL-3396)
  • Error management enhancement — A new configurable parameter, raise_error_DC_aliases in gvars.py, permits you to control the outcome of scenarios where BDS uses a location dc_aliases list to process a metric, and the list includes a dataset containing a value that is not defined in any tenant location:
    • If True, BDS stops processing the metric and raises the following error: DC aliases in dataset, not configured for customer.
    • If False, BDS continues transformation. This is the default behavior.

Resolved Issues

This release contains no resolved issues.

Upgrade Notes

No special procedure is required to upgrade to release

This page was last edited on April 16, 2020, at 17:11.
blog comments powered by Disqus