Documentation:PSAAS:RN:GPR:Public

Genesys Predictive Routing

Note: Not all changes listed below may pertain to your deployment.

• August 4, 2020 (9.0.017.05)
• May 26, 2020 (9.0.017.03)
• April 23, 2020 (9.0.016.13)
• February 20, 2020 (9.0.016.11)
• January 14, 2020 (9.0.016.07)
• December 20, 2019 (9.0.016.00)
• Known Issues

August 4, 2020 (9.0.017.05)

What's New

• Audit trail information is now available by request from your Genesys representative. This change is the result of updates to the underlying architecture that provides audit data. Previously, you could access audit data from the GPR web application Accounts tab. (PRR-6641, PRR-6642)
• The new KPI Outcome tab shows a comparison of KPI results using GPR and without. See View KPI outcome for a description of this graph and for how to configure your environment to supply the data required to use this tab. Note: The KPI Outcome tab functionality is available only to users with the STAFF role. (PRR-6477)
• The new Model Accuracy tab enables you to track how well a model functions over time. See View model accuracy for how to interpret this graph. (PRR-6539)

Resolved Issues

---

The agent feature-related dial graphs on the Feature Coverage tab no longer appear if there are no agent features included in the selected model. (PRR-6339)

---

A Clear query link no longer appears above the table listing datasets created for your account on the Settings: Datasets window. This field was introduced in error. (PRR-3623)

---

Upgrade Notes

An upgrade to technology underlying the GPR machine learning capabilities renders models made using earlier releases of GPR invalid in this and later releases. To use an updated release of GPR, you must recreate your models. (PRR-6394)

May 26, 2020 (9.0.017.03)

What's New

• If your environment has been configured for anonymization on-premises, users with the ADMIN role can only view datasets, the Agent Profile, and the Customer Profile. Users with the ADMIN role cannot use either the GPR web application or the GPR API to create, modify, or delete the specified objects. (PRR-6269)
• To improve performance, a number of changes have been made to the Agent and Customer Profile schema functionality:
  • The maximum number of indexed fields is now five fields per schema. (PRR-6260)
  • The number of features is now limited by default to 50 features per schema. If necessary, STAFF users can change the limit. Existing Agent and Customer Profile schemas are unaffected by this change. However, the limit takes effect the first time you change a schema. (PRR-6253)
  • The information displayed on the Agents and Customers pages has been simplified. The Details tabs now show tables containing the top 15 features that you marked as Visible when you prepared the schema. Details tab filtering is now done only by indexed fields, and you can select only one filter parameter at a time. The Distribution tabs no longer enable filtering. You can select from any of the indexed fields in the Distribution tab Group By parameter. (PRR-6216)
• Controls for starting, stopping, and restarting jobs have been removed from the Jobs tab in the GPR web application. The functionality these controls were intended to support was not implemented. (PRR-6202)
• The GPR web application now includes a new feature coverage report, located on the Predictors > AI Monitoring tab. For a complete description of how to use this tab, see Monitor predictor feature coverage in the Predictive Routing Help. (PRR-6009)
• A progress indicator now appears on the GPR web application Settings > Datasets page, showing the percent of data uploaded as GPR uploads the dataset. (PRR-5554)

Resolved Issues

The value for the latency field in scoring requests is now reported correctly. Previously, the returned value was always 0. (PRR-6252)

April 23, 2020 (9.0.016.13)

What's New

• The GPR Core Platform now supports data anonymization on premise, as well as anonymization in the cloud. For more details, see Data Anonymization. The Accounts window in the GPR web application now includes a read-only field that indicates where GPR anonymizes data. (PRR-6230)

February 20, 2020 (9.0.016.11)

What's New

• The Predictors analysis window has been completely replaced with new Simulator functionality, which provides improved insights into Predictor performance. You can now run simulated scoring requests to match customers in your Customer Profile with agents in your Agent Profile. For a complete description of the updated page, see Assess Predictor performance in the Predictive Routing Help.
• Audit trail records are now automatically retained for 365 days. Previously, this was a configurable field in the Account configuration window, presented in the Predictive Routing Help. The new value complies with global data retention requirements.
• The Jobs window has been updated to improve performance. The fields available for filtering the job displayed are now static lists containing all possible values. Previously, Genesys Predictive Routing (GPR) created these lists dynamically. For a full description, see Monitor jobs in the Predictive Routing Help.

January 14, 2020 (9.0.016.07)

What's New

• Users with the ADMIN role can use the Model export/import functionality. For an explanation of how to use this feature, see the following documentation topics:
  • Export a Model
  • Import a Model

  (PRR-6089)

• You can now make updates to already-uploaded records in the Agent Profile and Customer Profile datasets, even if you have reached the limit on the maximum number of records GPR supports (20,000 agents and 20 million customers). (PRR-5350)
• The GPR API response to a GET request to the /schemas endpoint now indicates whether you have reached the limit on the number of records you can upload to the Agent Profile and/ Customer profile datasets.

  For example, a response containing entity_limit_remaining : 0 indicates that you have uploaded as many records as GPR supports.

  (PRR-5290)

• During Predictor configuration, you can now enter an expression that specifies data to be skipped. See Step 6 under Create a Predictor for more information.

December 20, 2019 (9.0.016.00)

What's New

Initial release

• The Genesys Predictive Routing (GPR) Core Services platform (also known as AI Core Services) is now available in Genesys PureEngage Cloud. It provides the following functionality:
  • Account and user configuration
  • Predictors and Models
  • Agent Scoring
  • Analysis Reports (the Feature Analysis and Agent Variance Reports)
  • The GPR application
  • The GPR API
• The Dataset Trend tab has been reconstructed to make the information clearer and more intuitive. The Dataset Details tab has been removed.

Consult the following documentation for help using the Core Platform functions:

• Predictive Routing Help

Use of GPR requires on-premises components as well. Consult the following documentation for information about these components:

• Predictive Routing Deployment and Operations Guide
• Predictive Routing Configuration Options
• Data Loader Release Note
• URS Strategy Subroutines Release Note

Known Issues

• The links to the Help from the GPR web application point to an older version of the Help, which contains outdated information about the available controls and functionality. Click Predictive Routing Help for the updated Help file.
• If a scoring request contains more than 1,000 agents, the GPR Core Services Platform returns an error response with the http status code 403: {"ok": false, "error": "Number of agents per score request more than limit 1000"}. (PRR-5824)