Genesys Info Mart 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.

Service Released onReleased forHighlights
Genesys Info Mart September 14, 2021
PrivateEdition.png
Support for arbitrary UIDs in private edition deployments on OpenShift. Data Export enhancements.
GIM Config Adapter September 14, 2021
PrivateEdition.png
Support for arbitrary UIDs in private edition deployments on OpenShift.
GIM Stream Processor September 14, 2021
PrivateEdition.png
Support for arbitrary UIDs in private edition deployments on OpenShift.
Genesys Info Mart June 30, 2021
PrivateEdition.png
Early Adopter Program support for Genesys Engage cloud private edition.
GIM Config Adapter June 30, 2021
PrivateEdition.png
Early Adopter Program support for Genesys Engage cloud private edition.
GIM Stream Processor June 30, 2021
PrivateEdition.png
Early Adopter Program support for Genesys Engage cloud private edition.

Genesys Info Mart: September 14, 2021 PrivateEdition.png

PrivateEdition.png Private edition: 100.0.116.1400 available September 14, 2021

    What's New

    • Data Export enhancements:
      • Two SQL scripts that support use of the Data Export feature are now made available in the output folder that contains the data export:
        • update_target_gim_db*.sql — Enables you to create or update the target database schema into which you import the exported Info Mart data. The version of the script matches the Genesys Info Mart release in effect when the data export was performed.
        • make_export_views<db-schema>.sql — Enables you to restore or troubleshoot the export views used for your data export (for example, if your views get corrupted or you want to restore an earlier version).
        Separate versions of the scripts are provided for each RDBMS that Genesys Info Mart supports, stored in RDBMS-specific sql_scripts/<dbms> folders in the Data Export output package. Previously, the scripts were available only in the sql_scripts folder in the installation directory.
      • The GIDB_GC_ANNEX table, which stores information about the configuration of contact center objects such as persons and DNs, is now included in Data Export.
        (GIM-13444, GIM-13440, GIM-13435)
      More info: About Data Export Capability

      For private edition

      • GIM 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 GIM.
        • GIM 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 GIM using the genesys-restricted SCC, Genesys recommends that you redeploy GIM so that you use arbitrary UIDs.
          (GIM-13541)
        More info: OpenShift security settings
      • GIM Data Export (also known as BI Data Feed) now supports exporting data to S3 storage. To enable this option, in the values.yaml file you must set the s3_storage_enabled parameter to true and specify values for the s3_storage object parameters, which are used to construct the environment variable that provides the connection string. You might also need to create the S3 object bucket claim if you do not want to use the same S3 storage solution as GSP (see Configure GSP). (GIM-13506)
        More info: Configure GIM

        GIM Config Adapter: September 14, 2021 PrivateEdition.png

        PrivateEdition.png Private edition: 100.0.100.1200 available September 14, 2021

          For private edition

          • GCA 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 GCA.
            • GCA 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 GCA using the genesys-restricted SCC, Genesys recommends that you redeploy GCA so that you use arbitrary UIDs.
              (GIM-13541)
            More info: OpenShift security settings

            GIM Stream Processor: September 14, 2021 PrivateEdition.png

            PrivateEdition.png Private edition: 100.0.100.0900 available September 14, 2021

              For private edition

              • GSP 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 GSP.
                • GSP 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 GSP using the genesys-restricted SCC, Genesys recommends that you redeploy GSP so that you use arbitrary UIDs.
                  (GIM-13541)
                More info: OpenShift security settings

                Genesys Info Mart: June 30, 2021 PrivateEdition.png

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

                  For private edition

                  • Starting with this release, Genesys Info Mart is available for select customers in Genesys Engage cloud private edition, as part of the Early Adopter Program. (GIM-13280)
                    More info: Genesys Info Mart Private Edition Guide

                    GIM Config Adapter: June 30, 2021 PrivateEdition.png

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

                      For private edition

                      • Starting with this release, GIM Config Adapter is available for select customers in Genesys Engage cloud private edition, as part of the Early Adopter Program. (GIM-13280)

                        GIM Stream Processor: June 30, 2021 PrivateEdition.png

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

                          For private edition

                          • Starting with this release, GIM Stream Processor is available for select customers in Genesys Engage cloud private edition, as part of the Early Adopter Program. (GIM-13280)