Billing Data Service Release Notes

From Genesys Documentation
Jump to: navigation, search

Not all releases or changes listed below may pertain to your deployment. Check the table below to see which releases apply to you.

Released onReleased forHighlights
September 02, 2021
PrivateEdition.png
Support for arbitrary UIDs in private edition deployments on OpenShift.
June 30, 2021
PrivateEdition.png
Early Adopter Program support for Genesys Engage cloud private edition.

September 02, 2021 PrivateEdition.png

PrivateEdition.png Private edition: 100.0.001.0026 available September 10, 2021

    What's New

    • When you use the wizard to create a BDS configuration, the country parameter is now required. (CBILL-4911)
    • This Release Note describes Billing Data Server (BDS) BDS 100.0.001.0001, which is the same software as Genesys Engage on-premises release 9.0.005.02. Additionally, the product name is changed to Billing Data Service. (CBILL-4697)

      Resolved Issues

      • The transformation process now works correctly following test sessions. Previously, transformation failed following some test-session scenarios. (CBILL-5073)
      • The folder multicloud_pe now contains templates with appropriate product_id values for Genesys Engage cloud Private Edition. (CBILL-4940)
      • During startup, if BDS finds any placeholder values in the configuration files, it automatically uses values from environment variables instead. (CBILL-4788)

        For private edition

        • Billing Data Service now supports the use of arbitrary, or random, user IDs (UIDs) in OpenShift.
          • The Dockerfile has been modified to specify container and file ownership as user=500 (genesys) and group=0 (root).
          • The securityContext settings exposed in the default values.yaml file specify the user and group IDs for the genesys user (500:500:500). You must override these Helm chart values if you want OpenShift to use arbitrary UIDs. For more information, see Configure BDS.
          • Billing Data Service is deployed using a ServiceAccount that uses the restricted Security Context Constraint (SCC). If you do not want to use arbitrary UIDs in your OpenShift deployment, you must associate the ServiceAccount with the genesys-restricted SCC, as described in Deploy BDS. If you want OpenShift to use arbitrary UIDs and if you previously deployed Billing Data Service using a ServiceAccount associated with the genesys-restricted SCC, you must remove the association. To do so, execute the following command:
            oc adm policy remove-scc-from-user genesys-restricted -z <serviceaccount> -n <namespace>
          • Billing Data Service is deployed using ServiceAccounts that use the restricted Security Context Constraint (SCC). In an earlier implementation, Genesys required you to deploy all private edition services using a ServiceAccount associated with the custom genesys-restricted SCC, to control permissions for the genesys user (500). Genesys now expects OpenShift to use arbitrary UIDs in your deployment, and the genesys-restricted SCC has been deprecated. If you previously deployed Billing Data Service using the genesys-restricted SCC, Genesys recommends that you redeploy Billing Data Service so that you use arbitrary UIDs. (CBILL-5069)

          June 30, 2021 PrivateEdition.png

          PrivateEdition.png Private edition: 9.0.004.29 available June 30, 2021

            For private edition

            • Starting with this release, Billing Data Service (BDS) is available for select customers in Genesys Engage cloud private edition, as part of the Early Adopter Program. (CBILL-4628)
              More info: Billing Data Service Private Edition Guide