Documentation/v9

What's New in Management Framework for 9.0

For full information about supported operating systems, databases, browsers, and virtualization platforms, refer to the Framework page of the Genesys Supported Operating Environment Reference Guide.

December 17, 2021

Oracle Database 19c Client is supported by:
- Configuration Server 8.5.101.92
- Message Server 8.5.100.36
- DB Server 8.5.100.12

November 09, 2021

Configuration Server, DB Server, and Message Server now support PostgreSQL 13.

September 30, 2021

Oracle Database 18c Client is supported by:
- Configuration Server 8.5.101.83
- Message Server 8.5.100.32
- DB Server 8.5.100.09

August 11, 2021

Configuration Server, DB Server, and Message Server now support PostgreSQL 12.
Configuration Server includes a VAG Calculation filter. This feature allows you to selectively calculate VAGs at the Configuration Server Proxy Application level.

January 29, 2021

Configuration Server is enhanced to keep track of recent user login/authentication failures to generate a standard level log message when the number/rate of failures exceeds the specified threshold. This new feature can be enabled by using the failure-alarm-* options.

June 26, 2020

Configuration Server, Message Server, and DB Server support:
- MSSQL Server 2019 database on Windows and Linux
- Oracle 19c database with Oracle client 12.x and Oracle 19c RAC database
Framework servers now support Red Hat Enterprise Linux AP 8 and virtualization (KVM) in Red Hat 8 operating system

March 27, 2020

Configuration Server supports Server Name Indication (SNI) extension in TLS handshake.

February 28, 2020

Configuration Server in Proxy Mode now supports deployment when a dedicated instance of a proxy is being used to calculate VAG membership and distribute updates to certain Genesys applications that require this information.

December 06, 2019

Configuration Server external authentication now uses OpenSSL version 1.0.2s for Windows and Linux operating systems, and OpenSSL version 1.0.2r for AIX and Solaris operating systems.
The following utilities are no longer installed by default with Solution Control Server:
- logmsg
- mlcmd
- gstuckcalls
- Scripts for gstuckcalls
- SNMP utilities and scripts.
On Windows 64-bit operating systems, Local Control Agent now uses statically linked C runtime libraries.

September 27, 2019

DB Server 8.5 does not support AIX and Solaris operating systems. You can continue to use DB Server 8.1 for AIX and Solaris environments.
Limit the number of Configuration Server proxies reloading configuration data from the master Configuration Server.

July 30, 2019

Framework servers now support Microsoft Hyper-V Server 2019 virtualization platform.

June 26, 2019

Framework servers now support Windows Server 2019 operating system.

May 28, 2019

Configuration Server, DB Server, and Message Server now support Oracle 18c RAC database.

April 26, 2019

Configuration Server, DB Server, and Message Server now support Oracle 18c database with Oracle client 12.x.
New configuration option to enable indefinite locking of an account after multiple failed connection attempts.

February 28, 2019

For Configuration Server and Solution Control Server, log events related to read access activities provide extended information, such as IP address of host, username, application name and application type.

January 31, 2019

Configuration Server external authentication now uses OpenSSL version 1.0.2q.
Language Packs for Configuration Server have been updated.
The Configuration Database Maintenance Scripts component includes a new version of locale to support a generic Linux OS type for creating Linux hosts.
Support is discontinued for Genesys Deployment Agent (GDA).

November 30, 2018

Framework servers now support:
- Oracle Linux 7 with Unbreakable Enterprise Kernel (UEK) 4.x
- SUSE Linux Enterprise 12
Enhanced Keep-Alive feature support on connections between LDAP and Configuration Server.
New configurable option to detect hang-up during the data loading process between the Configuration Server HA pair.

August 31, 2018

Configuration Server now requires LDAP server to operate at minimum TLS version 1.1 for a successful connection.
Genesys LDAP authentication supports TLS version 1.1 and 1.2.

August 10, 2018

Configuration Server can now utilize User Principal Name (UPN) usernames for Kerberos external authentication.
Configuration Server is now using extended retention policies for audit records that are stored in the database. Audit records of up to 1 year or 100 thousand entries can be stored by Configuration Server.

July 10, 2018

For Configuration Server and DB Server, there are no Visual Studio redistributable packages associated with Visual Studio 2005 for 64-bit executables.
For Message Server, Local Control Agent, and Solution Control Server, there are no Visual Studio redistributable packages associated with Visual Studio 2005 (or prior Visual 88Studio releases) for 64-bit executables. These components now use Microsoft Visual Studio 2013 for installation on Windows 64-bit platform.

June 8, 2018

Configuration Server and Message Server now support MS SQL 2016 (and later) Always On with MultiSubnet Listener for disaster recovery and business continuity scenarios involving the Configuration and Log Databases, respectively. DB Server 8.1.3, if configured, supports the same functionality for one or both databases.
Audit performance with larger databases is improved, and includes a new filter to extract records from a large set of data.

May 8, 2018

Configuration Server can now be configured to skip all or some validation of changes (empty or duplicate sections) in the Annex of a configuration object.
Users can now specify a time interval in which Local Control Agent (LCA) expects a response to its switchover request to an application. If the application does not respond within that time, LCA sets the application to Unknown mode.
Minimum required database privileges are now documented in the Management Framework Deployment Guide.

March 27, 2018

Support of optional transaction serialization.
Limit the number of Configuration Server proxies reloading configuration data from the master Configuration Server.
Support for:
- Microsoft SQL client software on Linux and Windows with support for MSSQL Server 2017
- Oracle 12.1 client software on Linux and Windows
- PostgreSQL 10.1 client software on Linux and Windows

March 6, 2018

DB Server support for:
- Microsoft SQL Server 2017 running on Linux
- Microsoft SQL client software on Linux
- Oracle 12.1 client software on Linux and Windows

January 26, 2018

Support for Oracle 12c Release 2 Multitenant Pluggable Database (PDB).
Support for the Red Hat KVM (Kernel Virtualization Machine) virtualization platform.

December 22, 2017

Support for the CentOS Linux 7 operating system.
New timeout in which Solution Control Server can expect a TCP success or failure response from the Configuration Server to which it is connecting.

September 26, 2017

Support for the Microsoft Hyper-V Server 2016 virtualization platform.

August 22, 2017

Support for the Microsoft Windows Server 2016 operating system:
New Configuration Database Maintenance scripts to help you upgrade your single-tenant Configuration Database to multi-tenant format.

What's New in Genesys Softphone 9.0.0

03/25/21

Support for macOS 11 "Big Sur" operating system. The Apple M1 processor is supported through the macOS 11 Rosetta 2 compatibility feature. See the Genesys Softphone page in the Genesys Supported Operating Environment Reference Guide.
Genesys Softphone now ships with several ringing tones corresponding to the same sound but with different levels of loudness.
In a macOS environment, it is now possible to install Genesys Softphone so that it runs automatically when the agent is opening the OS session.

12/17/20

Genesys Softphone now automatically re-tries SIP registration attempts if the DNS fails to resolve the SIP FQDN on startup.
Genesys Softphone can now be installed on macOS version 10.15 Catalina. See the Genesys Softphone page in the Genesys Supported Operating Environment Reference Guide.

09/24/20

Genesys Softphone now correctly handles G.729 codecs with a packet size of 60 msec (SDP parameter ptime=60). Previously, such packets were processed incorrectly, only taking the first 40 msec of audio, resulting in poor audio quality.
When Genesys Softphone is running in Connector mode and is used as the voice channel support for a user-facing Agent Desktop application, it does not prevent this user-facing application from claiming WCAG 2.1 levels A and AA when the application supports this format for its own UI.

06/25/20

Genesys Softphone is now localized in the following languages: Arabic, German, Spanish, French, French (Canada), Italian, Japanese, Korean, Dutch, Polish, Portuguese (Brazil), Russian, Turkish, Chinese (Traditional), and Chinese (Simplified).

11/14/19

Microsoft Windows Server 2019 support for Genesys Softphone and Microsoft Hyper-V Server 2019 support for VDI deployments.
You can now deploy Genesys Softphone in Connector Mode and control it from a custom agent desktop by using an HTTP REST API, similar to how Genesys Softphone integrates with Workspace Web Edition and Workspace Desktop Edition for configuration, registration, and volume control.

06/27/19

Genesys Softphone HTTP connector has been improved to meet the requirements of Basic Hardening practices.
Genesys Softphone secured communication channels, such as Secured RTP, are now compliant with FIPS 140-2.
Genesys Softphone VDI Adapter can now be installed on eLux RP 5 Operating Systems to support Genesys Softphone running in Citrix XenApp or XenDesktop environments.

05/10/19

Support for Windows 2016 in Citrix VDI environments. See the Genesys Softphone page in the Genesys Supported Operating Environment Reference Guide.

02/28/19

Genesys Softphone can now be deployed in the Citrix XenApp 7 and XenDesktop 7 virtual desktop infrastructures. Deployment requires Genesys Softphone VDI Adapter to be installed on the client workstations. Refer to the Supported OS and the Supported Virtualization system guides for details about the supported versions.
Genesys Softphone VDI Adapter is installed as a plugin to the Citrix Workspace App (formerly known as Citrix Receiver) on client workstations to enable Genesys Softphone to be deployed in the Citrix XenApp 7 and XenDesktop 7 virtual desktop infrastructures. Consult the Supported OS and Supported Virtualization system guides for details about the supported versions.

12/21/18

Support for TLS, up to version 1.2.

05/31/18

Genesys Softphone now supports the UNENCRYPTED_SRTCP parameter per RFC 4568, and also understands "best-effort SRTP" (optional SRTP offer) per RFC 5939, accepting or rejecting SRTP based on the configured security policy.
Genesys Softphone now supports Automatic Gain Control for the customer audio stream.

03/17/18

Real-time voice quality indicator: The Softphone icon in the system taskbar now notifies user of possible voice quality problem.

What's new in Genesys Pulse for 9.x

Introduced in 9.0.006

HTTPS support.

Introduced in 9.0.005

Support of Screen Readers.

Introduced in 9.0.004

Ability to set Genesys Pulse User Preferences in the Genesys Pulse navigation bar.

Introduced in 9.0.003

Keyboard Navigation support.
Updated Out-Of-Box Callback Activity template.
Auditing log capabilities. To enable this feature set the enable_audit_trail option in the log section of Genesys Pulse application options to true. User operations will be logged with an [AUDIT] marker.
Changes in the User Interface to match recent Genesys User Experience guidelines.

Introduced in 9.0.002

The login page and dashboard elements have Genesys branding colors.

Introduced in 9.0.001

Extended formatting of the current status is now available as a customization template based on JavaScript string literals syntax. It allows to fully replace the standard representation of the current status statistics value with a user-designed one.
The Grid widget and the Data view have new Compact and High Color Contrast modes. New options are available on the Display Options tab of the Widget Wizard for the Grid widget and in the new Customize menu of the Data view:
- Row Density:
  Comfy (default) or Compact–Enables compact presentation for the high data density
- Row Color Contrast:
  Low (default) or High–Enables High Color Contrast for better accessibility
The Text Widget supports extended styling options:
- Customize the background color of the widget
- Change the text size
- Change the text style (normal, bold, italic)
- Change the text color
Ability to show or hide the widget title for any type of widgets.
Updates on the Display Options preview for the Text Widget:
- Added preview of the pinned Text Widget.
- Preview now displays the appearance of the Text Widget with applied wallboard theme.
The pinned Text Widget on launched wallboard has an improved panning animation corresponding to the news ticker.
Ability to use a keyboard to navigate over the navigation bar in Genesys Pulse UI.
Ability to select or clear selections from columns in the Data view on the expanded widget using the new Select All option.
Extended logging configuration possibilities though the [log] section.

Introduced in 9.0.000

Genesys Pulse 9.0 is offering advanced alert capabilities to notify supervisors when your service levels are not met or when you agent occupancy is below service objective
- Ability to configure rule-based alerts with Boolean expression
- Send email notification when a condition is violated for a given period
Genesys Pulse 9.0 is offering more flexibility in showing current agent states within omnichannel contact center to be compliant with labor unions.
- Ability to break down the current status by media
- Show / hide agent status icon
- Show / hide the duration of the agent in this state
- Show Do-Not-Disturb status
Genesys Pulse 9.0 is offering better functionalities helping IT departments and/or service providers size their worldwide Pulse deployment while preventing from performance bottleneck
- Limit the number of dashboards per user
- Limit the number of widgets per user
Genesys Pulse 9.0 is supporting its community helping them build their own visualizations for real-time insights
- Empower users to create their own visualization plugin
- Collect not only the latest snapshot data but also the time series data to build more advanced visualizations
Based on the customer feedback and to be more agile in our cloud development, Genesys Pulse 9.0 can no longer be deployed as GAX plugin but supervisors with the right permissions can switch from Pulse to GAX seamlessly. Pulse users are also able to switch from Pulse to more task-driven specific dashboards like Contact Center Advisors.

Localization support

Genesys Pulse supports the following localizations:

Arabic: 9.0.005.00
Chinese (Simplified): 9.0.005.00
Czech: 9.0.005.00
Dutch 9.0.005.00
French: 9.0.005.00
French Canadian: 9.0.005.00
German: 9.0.005.00
Italian: 9.0.005.00
Japanese: 9.0.005.00
Korean: 9.0.005.00
Polish: 9.0.005.00
Portuguese: 9.0.005.00
Russian: 9.0.005.00
Spanish: 9.0.005.00
Turkish: 9.0.005.00

New in AICS 9.0.015.03/ASC 9.0.015.04/URS Strategy Subroutines 9.0.015.00 (07/19/2019)

The NGINX container is no longer included in AICS. Previously, NGINX was provided as a convenience for use in internal and/or pre-production environments.
This release enables you to log scoring details that you can then use to monitor and better understand the scoring process and outcomes. This release also includes scripts to clean up unneeded score logs from MongoDB. To how to turn on score logging, for information about what is logged, and for the cleanup script, see View the Scoring Logs.
New API endpoints have been added, enabling you to use the MinIO container to upload Agent Profile and Customer Profile data. Previously, only Dataset data used the MinIO container, which provides a performance improvement over the data_upload worker alone. For details about these new endpoints, see the Predictive Routing API Reference, which you can access from a link on this page. (Requires a password for access. Please contact your Genesys representative if you need to view this document.)
The GPR API now returns a file_path parameter in the response message when you request a presigned URL, which replaces the uploaded file name. You must now pass this file_path parameter in requests to create Datasets or the Agent Profile or Customer Profile instead of the uploaded file name, used in previous releases. For details, see the Predictive Routing API Reference, which you can access from a link on this page. (Requires a password for access. Please contact your Genesys representative if you need to view this document.)
The GPR web application has enhanced security by logging out inactive users.
GPR now accepts only CSV and zipped CSV files for upload to Datasets, the Agent Profiles, and the Customer Profile. JSON file uploads are no longer supported.
The numeric datatype now replaces both float and integer datatypes in Agent and Customer Profiles. This change resolves confusion about when to use float and integer datatypes.
This is a breaking change from previous releases of AICS and Agent State Connector (ASC). If you upgrade either component you MUST also upgrade the other. The following versions are compatible:
- AICS 9.0.015.03 and higher + ASC 9.0.015.04 and higher.
- AICS 9.0.015.00 and lower + ASC 9.0.015.01 and lower.
Improvement in the queries used to run the Feature Analysis Report improve the speed and reliability with which these reports are generated.
The Deployment and Operations Guide now contains complete instructions for configuring HTTPS connections among all GPR components: Configure GPR to Use HTTPS
You can now optionally run ASC without a connection to Stat Server. ASC automatically detects whether there is a Stat Server Application in the ASC Application Connections tab. If so, ASC connects as in previous releases. If not, ASC does not connect to Stat Server and does not send agent login status updates to the GPR platform. In this case, AICS receives agent availability information from Universal Routing Server (URS).
ASC now validates the values you enter in the include-skills and include-groups configuration options. If ASC detects a skill name or Agent Group specified in these options that does not exist in Configuration Server, ASC triggers a Standard-level log message (Message Server log event number: 60401).
A number of subroutines have been introduced or modified. They perform the following functions:
- The new GPRIxnSetup subroutine initializes all the GPR KVPs with default values, setting with gpmMode to off and gpmResult to 15 (Predictive Routing is turned off or not used for this interaction).
- The GPRIxnCompleted subroutine has been updated to include the correct value of gpmScoreAboveMedian KVP by comparing the selected agent score with the returned median score.
- The ActivatePredictiveRouting_v3 and GPRIxnCleanup subroutines have been enhanced to add connection_ids as a URL parameter in the score request and the score_log request, for easier troubleshooting in URS logs.
- The GPRIxnCleanup subroutine now performs score log and UserEvent (KVP) distribution (previously done in the GPRIxnCompleted subroutine). This subroutine can now correctly identify abandoned interactions and interactions in which GPR was unable to route the interaction and add this information to the score log and the Genesys Info Mart gpmResult KVP, with the values 13 - Call Abandoned and 14 - Call Routing Failed.
The URS Strategy Subroutines now send the following new KVPs, which are stored in the Genesys Info Mart database and are available for reporting:
- gpmAdjustedAgentScore - The final agent score used to route the associated interaction to the selected agent. This score is calculated from the gpmAgentScore combined with any agent occupancy factor.
- gpmDefaultAgentScore - This default agent score for the associated interaction. The value is the outcome, for this interaction, of the setting specified in the default-agent-score configuration option.
- gpmDefaultScoredAgents - The number of agents with default scores assigned for an interaction.
- gpmDefaultScoreUsed - Indicates whether the agent score for the associated interaction is taken from the scoring response returned by GPR or the value of the default-agent-score configuration option.
- gpmGlobalScoreCount - The number of agents scored using the Global model. This value is the content of the global_scores_count field returned by AICS in the scoring response.
- gpmInitialScoreThreshold - The initial threshold value used for the interaction, taken from the value set in the score-base-threshold configuration option.
- gpmFinalScoreThreshold - The final threshold value used to route the associated interaction to the selected agent. The routing strategy calculates the value from the configured score threshold combined with values resulting from any agent holdout options.
- gpmScoreAboveMedian - Indicates whether the score for the selected agent was better than the median score for the target group.
- gpmSuitableAgentsCount - The number of agents who had scores greater than or equal to the initial threshold value when the scoring response was received.
- gpmPredictorType (Reserved for future use)
- gpmRoutingMethod (Reserved for future use)
For additional information see the following sources:
- Integrate with Genesys Reporting
- For the corresponding changes in Genesys Info Mart, see the “New in This Release” information for release 8.5.014.09 in the Genesys Info Mart Physical Data Model for your RDBMS.
The gpmResult KVP now includes four new values:
- 12 - Reserved for future use
- 13 - Call Abandoned
- 14 - Call Routing Failed
- 15 - Predictive Routing is turned off or not used for this interaction
The value off was added to the valid values for the gpmMode KVP.
The gpmWaitTime value is now calculated using START_TS rather than gpm-ixn-timestamp.
The GetActionFilters subroutine was enhanced to identify the list of agents matching the target skill group along with the configured login status expression. This information is also reported in the action filters of the scoring request. This functionality is invoked only when the use-action-filters configuration option is set to false.
Two new documentation pages, Routing Scenarios Using GPR and How Does GPR Score Agents? provide detailed discussions of those aspects of GPR functionality.

New in Release 9.0.015.00 (03/26/2019)

This release includes an updated and improved version of the Predictive Routing API Reference, which you can access from a link on this page. In particular, there are now cURL request examples for each endpoint.
AI Core Services now requires Docker version 18.09.2, which addresses important security issues. See the Release Notes for AI Core Services 9.0.015.00 for important information about the reason for this change and for Docker deployment information.
You can now convert a regular account into an LDAP account. A toggle with label LDAP has been added to the Settings > Account update window. To enable LDAP authentication, enter your LDAP credentials and save changes. After that, you must also convert the user accounts for those who should use LDAP authentication. User configuration is done in the Settings > User Management window.
This release includes the following improvements to the user interfaces in the GPR web application:
- A new navigation panel provides a tree view of all Datasets, Predictors, and Models configured for the current Tenant. This tree-view pane is available from the Settings > Datasets and Settings > Predictors windows. Each item in the tree view links to the specified object, enabling easy access to the entire hierarchy of Datasets, Predictors, and Models.
  NOTE: Composite Predictors, which can be built on data from multiple Datasets, are not shown in this tree-view pane.
- For simplified navigation, breadcrumb links now appear at the top of windows in the GPR web application if you have drilled-down past a top-level window.

New in Release 9.0.014.00 (12/21/2018)

You can now upload Dataset, Agent Profile, and Customer Profile data to Genesys Predictive Routing (GPR) from CSV files that use certain legacy encodings (listed below). By default, GPR always assumes the CSV files are encoded with UTF-8. This change applies to uploads using both the GPR web application and the GPR API. The following encodings are supported:
- UTF-8
- Shift JIS
All data returned from GPR uses UTF-8 encoding.
GPR has optimized how cardinalities are stored. Cardinalities are now written into a dedicated database collection, so that the cardinalities for each field are stored in their own document. Previously, the cardinalities were stored along with the schema data. With high-cardinality features, this could lead to performance degradation due to additional conversions needed to extract the cardinality data.
The schema management workflow for Agent and Customer Profiles has been simplified and streamlined. The Discovered Fields tab has been removed and cardinality counts have been added to the schema view. This change ensures GPR always presents up-to-date Profile information. The schema tab always presented updated information, if available, but the Discovered Fields tab display was generated only once and did not reflect changes to the Profile schema.
The explanation for how to configure and interpret the Agent Variance Report has been clarified and expanded.
AI Core Services (AICS) now supports deployment in an environment running on a Kubernetes cluster.
AICS supports Security Enhanced Linux (SELinux) on CentOS 7.
If the ASC configuration contains non-empty values for the new filter-by-skills and/or filter-by-groups configuration options, ASC subscribes to Stat Server for agent statistics only for the agents included in the specified Agent Groups or those satisfying the configured skill expression. If both options are configured, the agents are subscribed for statistics if they either satisfy the skill expression specified in the filter-by-skills option or are included in one of the Agent Groups specified in the filter-by-groups option. This functionality enables you to limit the number of agents monitored by GPR or to use GPR in environments where multiple Stat Servers are deployed to monitor different groups of agents.
Agent State Connector (ASC) now supports email interactions, as well as voice.

New in Release 9.0.013.01 (10/25/2018)

Dataset handling has been made significantly faster by means of the following improvements:
- For the initial data upload, this release introduces the Minio container.
- The Dataset import to MongoDB now uses a multithreaded process.
The NGINX container has been removed from AICS. NGINX is an optional load balancer that had been provided only for use only in test environments.
The Sizing Guide for Genesys Predictive Routing (GPR) has been entirely reworked and expanded.
The explanation for how to use Composite Predictors has been revised and clarified.
The GPR web application and GPR API now use the same process to create Agent and Customer Profile schemas. In addition, the instructions for Configuring Agent Profiles have been revised and expanded.
The LOG_LEVEL environment variable has been added to the tango.env configuration file. By default, it is set to INFO, which is a minimal logging level, adequate for most circumstances.
This release upgrades AICS to Python 3.6 from Python 2.7.
AICS now performs automatic cleanup processes which should maintain an adequate amount of free disk space.
Memory handling for MongoDB was improved In this release.
The Lift Estimation report has been improved, adding Export functionality, the ability to toggle between graph and table displays, and showing the Aggregated view as the first tab listed.
This release includes a number of changes to the look and feel of the GPR web application interface, as well as multiple user experience improvements to provide more intuitive workflows and better presentation of information. For a complete list, refer to the AI Core Services Release Note for release 9.0.013.01.
This release provides a number of improvements and additions to the GPR API, including the ability to sync and accept Datasets, check job status and support for nesting dictionary fields. For a complete list, refer to the AI Core Services Release Note for release 9.0.013.01 and the Predictive Routing API Reference (Requires a password for access. Please contact your Genesys representative if you need to view this document.)

New in Release 9.0.012.01 (08/23/2018)

The Quality column in the Models list table on the Model configuration window now includes a new metric, Local models. The metric displays the number of local models generated for agents in the dataset on which the predictor is built.
AI Core Services (AICS) has improved handling of UTF-8 characters. Data ingestion, model training, and analysis reports are all correctly processed for data containing non-ASCII UTF-8 characters.
The Genesys Predictive Routing (GPR) API now enables you to run Lift Estimation reports. The API returns a JSON response containing the Lift Estimation results. The resulting report is also automatically available for view from the GPR web application.
The GPR API now enables you to run Feature Analysis reports. The API returns a JSON response containing a list of features ordered by weight--that is, by the strength of the impact that feature has on the value of the target metric. The resulting report is also automatically available for view from the GPR web application.
The Lift Estimation report now uses the scoring expression configured for the predictor (if any) to decide whether the target metric should be minimized or maximized.
You can now configure Agent State Connector (ASC) to monitor the StatAgentOccupancy Stat Server statistic.
You can now configure ASC to monitor a subset of the total list of agent groups present in agent profiles.
You can now choose to have ASC ignore the following unsupported ASCII characters: [Space], -, <, >.
You can now configure ASC to monitor a subset of the total list of skills present in agent profiles.
ASC now supports a connection to Stat Server running in single-server mode, without a backup.

New in Release 9.0.011.00 (07/13/2018)

This release includes a number of additions to the Predictive Routing API:
- You can now generate and purge predictor data.
- You can now create a new predictor by copying an existing one.
- You can now use GET commands to retrieve dataset and predictor details.
- The way Predictive Routing recomputes cardinalities when you append data to Agent or Customer Profiles using the API has been improved.
- You can now retrieve information on the currently deployed platform using the new version endpoint.
This release includes the following new supported platforms:
- Mongo DB 3.6 (requires a special upgrade procedure; see the AI Core Services Release Note for details)
- Oracle Linux 7.3
You can now configure parameters to control password-related behavior such as how often users must change them, blocking users after a specified number of login attempts, and adding a custom message when users are blocked.
The audit trail functionality has been improved, to record additional actions and provide the ability to specify how long audit trail records are kept. All actions related to logins, object modification/creation/deletion, and so on, whether performed using the GPR application or the API, are logged.
You can configure the Predictive Routing application to display custom messages on the login screen.
You can now upload data (agent, customer, and dataset) using zip-archived .csv files.
Predictive Routing now correctly recognizes columns with any combination of the following Boolean values: y/n, Y/N, Yes/No. Previously, only columns with true/false and 0/1 values were discovered as Booleans. The identification is case insensitive.

New in Release 9.0.010.01 (05/11/2018)

Genesys Predictive Routing complies with GDPR requirements for handling sensitive customer information. The Predictive Routing API has been expanded to provide Read and Delete functions, enabling you to locate and remove user data. For details, refer to Handling Personally Identifiable Information in Compliance with GDPR Requirements in the Genesys Predictive Routing Deployment and Operations Guide and to the Predictive Routing API Reference (access requires a password; contact your Genesys representative for assistance).
The Lift Estimation report now offers Advanced Group By functionality, which provides more flexibility in customizing the report. For details, refer to the Lift Estimation Report Overview in the Genesys Predictive Routing Help.

New in Release 9.0.009.00 (03/28/2018)

Journey Optimization Platform (JOP) was renamed to AI Core Services (AICS).
When generating the Lift Estimation report, Predictive Routing now provides the option to produce a report for each unique value for a selected column (feature). Previously, any feature with a cardinality of more than 20 was excluded, which meant that you could not produce reports with a granularity higher than 20 unique features.
The agent pool for lift estimation is now constructed on a per-day basis for the interactions in the dataset. Previously, you might have observed a negative lift for higher agent availability or an unexpectedly high lift for low agent availability due to overcorrection caused by a mismatch between the input sample size and the actual sizes encountered through daily simulation.
Predictive Routing now supports LDAP authentication when logging in.

New in Release 9.0.008.00 (03/05/2018)

You can now enable Predictive Routing to look up updated values for certain agent attributes, based on customer or interaction attributes during a scoring request. For instance, you can look up agent performance by virtual queue, enabling you to evaluate the agent’s previous performance when handling interactions from that queue. This avoids comparing agent performance for a specific queue against other agents who handle interactions from a different mixture of virtual queues.
You can now view an entire Agent Profile or Customer Profile record from the Agents Details and Customers Details tabs or an entire record on the Datasets Details tab. Click a single record to open a new window containing a table with all the related key-value pairs.
Agent State Connector now supports connection to a secured Configuration Server port and TLS 1.2 connections to Stat Server.
You can now configure Agent State Connector to automatically create an Agent Profile schema, if none exists, or to verify the existing schema.
You can now have Agent State Connector collect call connId data from Stat Server and write it to the Agent Profile schema for use in Predictive Routing.
Agent State Connector is now supported on Windows. For exact versions supported, see the Genesys Supported Operating Environment Reference Guide.
Predictive Routing now supports datasets of up to 250 columns for predictor data generation, model training, and analysis.
Model training speed has been considerably improved.
Predictive Routing now provides progress indicators when loading predictor data and generating predictors. The progress indicators show the percent complete and the number of data rows already loaded.
The maximum supported cardinality for the Group By functionality in the Lift Estimation report has been increased to 20. All features with cardinalities between 1 and 20 are now available in the Group By selection menu.
You can now enter a maximum value of 500 simulations in the Lift Estimation analysis report settings. This prevents you from entering numbers too large to efficiently analyze and which can lead to an out-of-memory situation. The Number of Simulations field accepts any value larger than 0 and less than or equal to 500.
Predictive Routing now provides a text search field for use when selecting attributes for analysis.

New in Release 9.0.007.01 (01/05/2018)

The user interface and the documentation have been updated to reflect the product name change from Genesys Predictive Matching to Genesys Predictive Routing.

Important

For now, the following Genesys Predictive Routing components retain "Predictive Matching" as a part of the component name: Predictive Matching - Agent State Connector, Predictive Matching - Composer Strategy Subroutines, and Predictive Matching - URS Strategy Subroutines.

New in Release 9.0.007.00 (12/22/2017)

The product name has changed from Genesys Predictive Matching to Genesys Predictive Routing. This change is not yet reflected in the application interface or in the documentation.
Genesys Predictive Routing now supports both single-site and multi-site HA architectures.
Genesys Predictive Routing now supports historical reporting, provided by the Genesys Reporting solution. The following reports are available in Genesys Interactive Insights/GCXI: Predictive Routing AB Testing Report, Predictive Routing Agent Occupancy Report, Predictive Routing Detail Report, Predictive Routing Operational Report, and Predictive Routing Queue Statistics Report.
Two new real-time reporting templates are available for use in Pulse dashboards: Agent Group KPIs by Predictive Model and Queue KPIs by Predictive Model.
Two new analysis reports have been added to the Genesys Predictive Routing application: Agent Variance and Lift Estimation.
The Model creation interface now includes additional model quality and agent coverage reporting.
The Feature Analysis report, the model creation and training functionality, and the dataset import functionality have been improved to handle large datasets.
You can now combine simple predictors to create composite predictors.
Health checks and monitoring have been improved for both Journey Optimization Platform (JOP) and Agent State Connector (ASC). ASC now enables you to set alarms if there are persistent connection issues with Configuration Server or Stat Server.

New in Release 9.0.006.00 (09/26/2017)

You can now deploy the Journey Optimization Platform (JOP) in Docker containers.
This release includes updates to the Predictive Matching web interface for improved usability and rebranding.
This release includes context-sensitive Help.
You can now update and retrain models that have not yet been activated. You can also make changes to activated models by cloning them, editing the parameters, then activating the new model in place of the old one.
Agent State Connector and the Strategy Subroutines components can be deployed in a high availability configuration.
Predictive Matching now supports HTTPS.
Predictive Matching now supports TLS 1.2 encryption. Support for TLS 1.1 has been discontinued.
Routing using Predictive Matching can now take agent occupancy into account when selecting the best target.
The workflow for creating Predictors has been made more logical and straightforward.
Users can now reset their passwords from the Predictive Matching web interface.

New in Release 9.0.005.00 (06/27/2017)

Predictive Matching now provides REST APIs for scoring, agent profile updates, and customer profile updates.
Predictive Matching now supports strategies created in Composer and processed by Orchestration Server (ORS). These strategies utilize common Universal Routing Server (URS) subroutines to store scores returned from the scoring server and to set callback functions in URS.
Schema modification has been extended to enable manual creation of fields not included in an imported dataset. This extended functionality also enables discovery of additional fields by uploading further data and thereby extending the schema.

New in Release 9.0.004.04 (03/28/2017)

Extended datasets functionality now includes built-in analysis capabilities to make data exploration and feature analysis more straightforward without requiring customers to first build a predictive model.
Customer profile data can now be loaded to the platform by means of a REST-API and joined at run time for scoring. This simplifies the integration requirements for deploying Predictive Matching, requiring less modification to existing routing strategies or run time CRM integrations.
Predictive Matching now enables logging of routing decisions, required for accurate A/B testing, to JOP rather than Genesys Info Mart. This simplifies Predictive Matching deployment, by removing the need to make changes to Interaction Concentrator and Genesys Info Mart to support Predictive Matching.
The new Predictive Matching Help now opens when you click the Help link in the Predictive Matching interface.

New in Release 9.0.003.00

Improvements to the analytics and reporting functionality:
- Reports can now indicate whether a predictive score was generated (that is, A/B testing), and whether it was interleaved, or time-divided.
- The range of visualization on the Reporting Dashboard page has been improved.
- Predictive Routing can now perform analysis and data discovery on factors driving the KPI that is being optimized.
You can now upload data sets in CVS format, enabling you to have Predictive Routing analyze the data, define predictors based on it, and report on it. You can use these data sets for model training and testing, and you can calculate statistics for correlation and cardinality from them.
Self-service predictor management and model creation. Note the following properties of predictors and models:
- You can have multiple models built from one related data set.
- You can only use a predictor to optimize a single metric (that is, a column in the data set); each model under the same predictor optimizes the same metric.
- You can use a subset of features from the data set to define a predictor.
- A predictor can be based on a subset of data (such as a time range, or a subset created by filtering data set column values).
- Once you define a predictor, you can append new data to its underlying data set.
- A predictor can use any source of data matching the source data set schema to retrain and update models.

New in Release 9.0.000.00

Routing subroutine support to score agents in agent-surplus mode, where there are more agents in ready status than interactions requiring agent handling. Agents can be scored on various criteria you configure so that interactions go to the most suitable agent.
Routing subroutine support to score agents in customer-surplus mode, where more customer interactions are waiting in queue than there are available agents. Interactions are scored based on criteria you define so that customers you consider highest priority are handled first.
Logging, monitoring, and alarm capabilities.
Ability to combine various criteria for scoring agents or interactions for suitability, leading to a more nuanced matching of agents and interactions.
Fault Tolerance. If Predictive Routing is unavailable, or if a Predictive Routing strategy subroutine takes more than a specified amount of time to process an interaction, the routing strategy defaults back to standard behavior.

New in 9.0.111.31

Intelligent Automation now supports direct audio streaming to Google Dialogflow Essentials using Nexus, GWS, and Google Dialogflow. A new Natural Language Audio Streaming Menu microapp has been included to support audio streaming.
The Groovy script execution in Script Blocks and the getRemoteHttpData method are optimized to use the connection pool feature. A new option, Script.RemoteHttpClient.connectTimeout is added to configure the connection timeout value.
Intelligent Automation now allows configuring the Menu Controller VXML options from the UI instead of configuring them in the fish.properties file.
To support localization, the database schema and the column sizes in the tables have been enhanced.
Intelligent Automation supports high availability (N+1) chat servers.
Intelligent Automation now supports masking user input entries in Visual IVR applications. If the Confidential Mode setting is enabled, Visual IVR masks the strings instead of displaying the actual information. This setting does not mask the currencies, dates, numbers, and phone number grammar types.

New in 9.0.110.23

A new server setting, GoogleASR.NBestValue.ConfidenceScoreBased is introduced to pick the N-Best best results based on the confidence score. Previously, only the first entry in the list was chosen.
A new server setting, VoiceXML.SSML.Play.DynamicSSML is introduced to control Dynamic Speech Synthesis Markup Language (SSML) playback with variables. SSML playback from GIA Prompts and NLM (Natural Language Menu) responses are supported. When this flag is set to true, Genesys Voice Platform (GVP) interprets the SSML tags available in a variable. Previously, GVP played the SSML values present in a variable as a string value.
Intelligent Automation now supports Enhanced ASR (Advanced Speech Recognition) properties to support Google Speech Recognizers. Two new Voice UI (VUI) preference options, google_use_enhanced and google_use_model_type are introduced to configure the Enhanced ASR properties.
Intelligent Automation now supports single utterance properties to support Google Speech Recognizers. A new VUI preference option, single_word_utterance is introduced to configure the single utterance option.
Question blocks now support the YMD, DMY, and MDY date formats.
The size of the cti_fields field in the calls and historical_calls tables of the Fish Reports database is increased from 1000 to 2000 characters.

New in 9.0.109.06

The Tomcat version has been upgraded from 9.0.27 to 9.0.37.

New in 9.0.109.03

The Tomcat Session ID can now be included in the Tomcat logs (localhost_access_log.xxxxxxx.txt) by adding the regex pattern, %S to the existing list of patterns: pattern="%h %l %u %t %r %s %S %b %T %{CallId}s".

New in 9.0.109.00

The createNativePrompt method has been enhanced to support an optional parameter (JSON) to supply Rich Media related key-value pairs in the structured transcript message. This allows IA to send Rich Media UI-related properties to be sent to Chat clients. See Adding custom rich media for more information.
The fish-cbp plugin now supports using proxy servers to communicate with IA servers. See Using Bots from more information.

New in 9.0.107.00

Intelligent Automation now supports Google Dialogflow's follow-up intents and output contexts.
Intelligent Automation now supports Microsoft Bot Framework using Direct Line v3 API.
The version number now displays on the login page.
Speech Synthesis Markup Language (SSML) pauses can now be added in increments of 50 milliseconds.
When the Debug logging is enabled, requests and responses between Genesys Dialog Engine and Google Dialogflow are now logged.
Concatenated prompt recording (CPR) packs for dynamic prompt playback, if configured, are now used even if the environment setting, VoiceXML.SSML.AlwaysUseSSML is set to true.
The Date Picker in Web IVR now supports DMY (default), MDY and YMD date formats.

New in 9.0.106.05

Multi-modal applications in IA will now check for the ORS session status before transitioning to the final vxml.jsp. This prevents IA runtime sessions from timing out while waiting for new requests.

New in 9.0.106.02

The fallback to voice on client error functionality now works properly.
Switching back to the Voice option from the Multi-modal option will no longer trigger execution of the Visual Mandatory On VUI preferences.
Browsers can now use Web IVR without requiring cookies to be set.
Additional contingency messaging is added to the VisualMessages.properties file to cover scenarios when no sessions are available.
WebIVR pages now change the location to EndSession.jsp after loading. This resolves the issue where requests made with expired sessions caused errors.
Logging has been included for multimodal sessions when a new session request is received. The logs will now include information on the validity of the session ID.
The footer buttons now display correctly in WebIVR when cookies are not enabled.

New in 9.0.106.00

The default Text Responses from Google Dialogflow can now be accessed using the NLTextResponse variable.
Session variables can now be sent to Dialog Engine or Dialogflow for slot filling purposes.
The Natural Language Menu product now displays only the first five utterances for each intent.
Intelligent Automation personas now allow selecting a TTS voice to use for both Nuance and Google TTS.
Intelligent Automation can now provide a maximum limit for the number of attempts to collect a slot value.
Intelligent Automation now allows you to use separate variables and slot names when skipping questions. Previously, the variable could only be created with the same name as the slot.
Intelligent Automation now supports Dialogflow's SmallTalk feature.
Intelligent Automation now reads the DialogFlow fulfilment messages field rather than the fulfilment text. This allows multiple messages to be returned and now supports text returned from fulfilment webhooks.
Intelligent Automation now supports fulfillment from Dialogflow.
Intelligent Automation now supports Dialogflow System Entities.
Intelligent Automation now supports the ability to pass a variable to Natural Language menu to use as the first utterance. Intelligent Automation also provides the ability to configure a path/module to use if no intent is found.

New in 9.0.105.01

Intelligent Automation now reads the Dialogflow fulfilment messages field rather than the fulfilment text. This allows multiple messages to be returned and now supports returned text from fulfilment webhooks.

New in 9.0.105.00

You can now set the length of time a HTTP connection lives in the connection pool before it is closed. This is configured by the default server setting, HttpClient.ConnectionPool.ConnectionLifetimeInSeconds. This will be useful in environments where firewalls or other systems kill idle connections without informing the client.
Intelligent Automation now supports Genesys Dialog Engine's v2 API.
Intelligent Automation now supports Google Text-To-Speech for both Genesys Engage and PureConnect voicebots.

New in 9.0.104.00

Intelligent Automation is now fully integrated with Google Dialogflow. This latest AI integration enables conversation powered by machine learning and natural language understanding to take place between customers and chat bots.
Refer to the Natural Language AI Integration page in the Intelligent Automation Help manual for more information.

Support for Windows Server 2016.

New in 9.0.103.00

Natural Language Menu modules now include an Intents List tab, which displays all Intents associated with a Dialog Engine domain. Use the Intents List tab to map each Intent to a module, and Intelligent Automation will create or update an application's callflow accordingly.
For more information, refer to the Integrating Dialog Engine page in the Intelligent Automation Deployment Guide.
Intelligent Automation now supports two types of two-factor authentication in self-service applications:
- Internal authentication - Intelligent Automation generates a code internally and delivers the code to the user's verified email address or phone number (SMS).
- External authentication - Customers use their own systems to verify a user.
For more information about this feature, refer to the Two-Factor Authentication page in the MicroApps section of the Intelligent Automation Help manual.

New in 9.0.102.00

You can now create chat personas for use in chat-based applications.
Visual elements within the user interface have been rebranded to align with the latest Genesys design standards. This includes visual enhancements to the login screen and color changes to UI elements such as buttons, toggles, menus, text fields, and icons.
These visual changes do not impact functionality.
Intelligent Automation now supports rich media in the chat channel. This includes the ability to enhance chat messages with images, videos, buttons, rich text, and hyperlinks.
Support for OpenJDK 8.
Changes to TLS support include the following:
- Intelligent Automation no longer supports SSLv2, SSLv3, or TLS 1.0 as a default supported protocol.
- Intelligent Automation now supports secure communication using only TLS 1.1 and TLS 1.2 by default.
If you require TLS 1.0 or any other configuration, you must explicitly specify it in the HttpClient.Security.SupportedProtocols default server setting. This will override the default.

New in 9.0.101.00

You can now add multiple retry and timeout prompts to Menu, Question, and Recording blocks.
You can now use TLS v1.2 connections with Genesys servers. Refer to the migration procedure in the Genesys Intelligent Automation Migration Guide for more information.
Support for Microsoft SQL Server 2016 and Microsoft SQL Server 2017 databases. See the Supported Operating Environment: Genesys Intelligent Automation page for more detailed information and a list of all supported databases.
Integration Hub processes now allow underscores in their names. Previously, using underscores in names caused an error.

New in 9.0.100.02

VoiceBots (previously known as Cognitive IVR) uses Google Cloud Speech-to-Text to improve the performance of natural-language interfaces such as Dialog Engine. VoiceBots makes it easier for callers to use spoken natural-language phrases to navigate through a Genesys Intelligent Automation application.
Important
The VoiceBots feature is currently part of the Early Adopter Program (EAP).
You can now use Personas with the Dynamic Menu builder product, which allows you to configure display labels for digital channels and separate lists of recognition phrases for voice channels.
Support for Microsoft SQL Server 2017 databases. See the Supported Operating Environment: Genesys Intelligent Automation page for more detailed information and a list of all supported databases.
The plugin for Bot Gateway Server now calls directly from the Bot Gateway Server driver (on Digital Messaging Server) to the Intelligent Automation VUI Server, bypassing the Intelligent Automation Messaging Server.
Connections to other Genesys servers (for example, Configuration Server or Interaction Server) now use Genesys ADDP functionality.

What's New in Genesys Decisions for 9.0

The following new features were added in the 9.0 release:

January 18, 2019

Extended Outbound Adapter — Genesys Decisions includes a new outbound adapter. Decisions continues to include the existing Outbound Phone adapter, but the new Extended Outbound adapter imports additional data such as Connects per attempt, List Size, Total Time for Wrong Party Connects, and Total Time for Right Party Connects. The Extended Outbound adapter specification file contains detailed information about the file requirements.
Database Timeout is added to configuration files during upgrade — The database timeout property is now added to the configuration files when you upgrade your Decisions installation.

September 25, 2018

Advanced Forecasting — Genesys Decisions now connects to the Decisions Cloud Service. The Decisions application sends historical data to the service. Based on that data, the service determines outliers and missing data, and determines which forecasting method to use and which parameters to use with the selected method. The results are then returned to Decisions and displayed. The following additional functionality is included with the new Decisions Forecasting module:
- Apply Forecast Scenarios to Planning Scenarios — Once you are satisfied with your forecast scenario and its results, you can apply that to your planning scenario. From within the Decisions application, you select a forecast scenario from a list of published scenarios and apply that to your planning scenario. Applying a forecast scenario populates the planning scenario metrics with the forecast results.
- Forecast Modifications — The forecast results that are returned from the Decisions Cloud Service are based on your historical data. If there are future events planned, such as a marketing release that will increase call volume by 10%, then you can apply modifications to the forecast results to take the future events into account, as well as the historical data.
- View Detailed Forecast Data — In addition to showing the results of a forecast scenario, you can also use the Decisions application to see the forecast model used for the results, the parameters selected for that model, the forecast error, and the points that were designated as outliers and missing.
- View Historical Values used to Generate Forecast Results — In the Decisions Forecasting module, you can view the historical values (both graphically and in tabular format) that the Decisions Cloud Service used to generate results. Use this information to help you understand what was happening in the past that contributed to the resulting forecast.

New in 9.0.025.05

This release contains the following new feature and enhancement:

When Partitioning is enabled, Outbound Analytics dashboards now display data only for the active partition.

New in 9.0.025.04

This release contains the following new features and enhancements:

The new partitioning functionality allows the split of outbound objects in a tenant to logical sections (partitions). Different departments can now store objects under different partitions, so that administrators can only operate with objects (for example, campaigns and contact lists) belonging to their department.
CX Contact now supports optional preprocessing of the input file before the List import is executed.
In the Outbound Schedules dialog, CX Contact UI now supports a condition based on the statistical value in the sequential and instant Schedule commands.
Call Result Records dashboard in Outbound Analytics now contains the new Boolean field isFinal.
The CX Contact login screen can now contain optional user-specified information about the environment you are logging into.
Small exported *.csv files are now handled correctly for List Automation Jobs of type Export Analytics.
Negative values are now supported for the Selection rules expressions.
CX Contact now expects the where query parameter in the GET /contacts API request to be encoded with a Base64 format.
In the List Automation Jobs output file, the name generation for patterns of type <fixed name>_MMDDYYYY is now processed correctly.

New in 9.0.024.04

This release contains the following new features and enhancements:

CX Contact now supports Enterprise Redis 6 over TLS.
CX Contact now supports PostgreSQL 12.x, Redis 6.x, and Elasticsearch 7.6.
CX Contact now supports PostgreSQL 11.
It is now possible to optionally utilize basic authentication on CX Contact HTTP or HTTPS connections to Elasticsearch.
The new Disposition Code field has been added to the mandatory Contact Lists fields.
You can now apply a Dialing Filter to a specific Calling List. A Dialing Filter can be applied to lists in unloaded or in active or running Campaign Groups.
When creating or editing a schedule you can now select the Time in state (Advanced) condition. This new condition enables you to configure the Set Time interval and state for a specific campaign group.
It is now possible to use a SSH Private Key (or combined SSH Private Key and Password) authentication methods to access the remote SFTP Server.
Device Mask is now supported for the Selection (Contacts) rule. It is now possible to define a Selection (Contacts) rule that operates over a Device Mask field.
The end user can now create a filter using only mobile phone numbers from the input list.
For SMS outbound campaigns, the list of keywords for help and stop signals has been expanded with the following additional keywords (in any letter case):
- help: 'aide'
- stop: 'arret' and 'unsub'

New in 9.0.023.06

This release includes only resolved issues.

New in 9.0.023.04

This release contains the following new feature and enhancement:

The Campaign Group Event Record Dashboard now contains data that indicates when pre-loading was started and completed for each Campaign Group.

New in 9.0.023.03

This release contains the following new features and enhancements:

CX Contact is now capable to decrypt PGP files encrypted with older PGP encryption standards.
CX Contact analytics Call Result Records index now contain ChainID, ChainN, and ClientID data fields.
The Attempt Rule can now be configured to govern attempts at specific time periods during the day. For example, an Attempt Rule can be configured to run 2 attempts in the morning (9am - 2pm), 1 in the afternoon (2pm - 4pm), and 2 in the evening (4pm - 9pm).
Compliance Tools Improvements
- All Compliance Tools have been significantly extended to include the ability to define the scope of each compliance rule for a particular country and for subdivisions by regions, states, and provinces within a defined country.
- The Contact Times rule can now work in strict Contact Times mode (applied during pre-loading by the Campaign Manager), and apply a Disposition Code.
- The Contact Times rule can now support device position and device type configuration options.
- Attempt Rules can now work in a Today time interval and apply a Disposition Code.
- Attempt Rules now support device position and device type configuration options.
- Location Rules now support device position and device type configuration options.
- The Custom Timezones Table has been extended to include the ability to optionally define the exchange code for each Timezone mapping.
- Custom Compliance rules can now apply a Disposition Code.

New in 9.0.022.04

This release contains the following new feature:

From the Settings > Security page you can now view information about the uploaded public key algorithm and the public key expiration date.

New in 9.0.022.03

This release contains the following new features and enhancements:

The DB field name of every Contact List field is now located under its respective column header when using List Details Viewer. When working with SQL use the DB field name to query the correct DB fields. For additional information, see Contact List Import.
You can now filter the List Details View according to the following free-form SQL entries. For additional information, see the SQL row in the List Details View table.
- Where - An SQL filtering expression applied to the selected contact list.
- Order By - An SQL ordering expression applied to the selected contact list.
You can now hide/show columns in the List Detail View. For more information, see the Important note in the Contact List Import section.
A summary of the number of contacts and devices in the entire contact list and in the selected filtered view is now provided above the List Details View you. For additional information, see List Details View
All List Details View filtering rules, and selection rules (contact and advanced) are accessible from the *Rule* drop-down list. As a result, you can now apply previously created filtering and selection rules to view previous results. For additional information, see the Rule row in the List Details View table.
The records in the List Details View are now automatically color grouped. Each color represents a different customer. Since each customer can have more than one device, the colors enable you to view which records belong to the same customer. For additional information, see the Important note under the List Details View table.
The Copy Contact option now includes a Copy as Callback option that enables you to maintain the callback information (that is, agent name, the date and time the callback occurred, and the type of callback) when a contact is copied to a new contact list. For more information, see Apply to Record Options Defined
Custom Compliance rules created using custom expressions can now be validated before they are saved and applied to campaign groups.
You can now create a filtering rule from the List Details View. Using this option, you can now test and validate SQL queries against uploaded contact lists and save the active query as a filtering rule for future use. For additional information, see the SQL row in the List Details View table.
CX Contact Analytics now supports HTTPS connection to Elasticsearch.
You can now view the import history of lists imported when working with List Automation. The new Activity Type field will show the List Automation value if imported by SFTP automation.
Campaign dashboard statistics now include the number of successful contact attempts during an active session and the total number of successful contact attempts for the selected campaign group. Note: The Aggregation of Delivered, Not Delivered and Not attempted will always match the total contact list size.

New in 9.0.021.05

This release includes only resolved issues.

New in 9.0.021.04

This release contains the following new features and enhancements:

When a Contact list encoded with PGP-encryption (that is, secured encryption) is selected, a closed padlock icon is displayed and all of the list options are disabled. Previously, the encoded Contact list details were visible and the list options were enabled.
The local timezone is now displayed in the CX Contact user interface at all times. The local timezone is configured in the CX Contact Settings page.
When working with List Automation you can now export analytics data to a .csv file via SFTP.
You can now incorporate special characters (white-space, @, -, and so on) in the List Automation SFTP directory.
The Agent Callback Error call result now includes a new action type: AssignToGroup. AssignToGroup redistributes the callback to another agent in the agent group if the original agent is unable to initiate the scheduled callback. This option is only available when the call result is: agent callback error.
Interactions that are cancelled during pre-loading and pre-dial validation are stored in Outbound Analytics with Blocking rule and Blocking Suppression list information.
The Settings > Security tab now includes a new Use strict sign out option. When this new option is enabled, users will be forced to sign out of the CX Contact UI every time the browser page is closed.
You can now select to show/hide individual columns in the Outbound Analytics Custom Table panel.
It is now possible to calculate the duration between two different date timestamps in the Outbound Analytics Custom Table panel.

New in 9.0.020.05

This release contains the following new features and enhancements:

The Settings tab now includes a strict-logout option. When enabled this option forces the user to be logged out of the CX Contact UI as soon as the browser is closed.
The Analytics Histogram panel now supports X-Axis labels to show date and time ranges.
The CX Contact UI now supports a Secure with encryption option when creating or editing a List Automation Job.

New in 9.0.020.03

This release contains the following new features and enhancements:

A new CX Contact Dashboard (Outbound Analytics) has been added for the new Schedules index.
An Attempt rule can now be defined using the Agent Disposition code. As a result, when an attempt is made to initiate an interaction, the attempt can be counted according to its Disposition value. This allows for greater granular control over agent and customer interactions.
The Schedules menu was added to CX Contact. With Schedules you can now configure instant and sequential events by determining when dialing is active. This new option enables you to:
- Schedule when a campaign group starts/finishes.
- Schedule a campaign group to run for a specified period of time or until a specific statistic is achieved.
- Sequence campaign groups. For example, starting one campaign group when another campaign group closes at a defined time.

New in 9.0.020.01

This release includes only resolved issues.

New in 9.0.019.01

This release contains the following new features and enhancements:

PGP encryption for data in transit is now supported. Contact Lists, Suppression Lists and Analytics exports can now be PGP encrypted to secure data during upload and download from CXContact.
It is now possible to create custom Compliance rules. Using JS expression users can create Bespoke Compliance rules and enable apply these rules to Campaign Groups in the same way standard Compliance rules are applied.
When editing a campaign group the Contact list dropdown menu is now listed in alphabetical order.
Analytics now provides a format configuration option for managing Time conversion for the time and duration fields. For example, milliseconds can be rounded seconds, or seconds with a decimal place to 1 or 2 or 3 positions.
Improvements have been made to the List Automation user interface to support SFTP over MPLS with new file server, directory and public key fingerprint options.
All drop down menu options are now listed alphabetically. This includes all menus found in Campaign Group, Upload rule, Label, Contact attempt, Suppression and Session Profiles.
Advanced Selection rules that are built using Visual Editor are now converted in SQL when a user disables the visual editor to access free-form SQL advanced options.
To enable detailed event logging a new Trace connection attempt option was added to List Automation.
An exported List Rule can now be imported into CX Contact.
Table panel has been enhanced to support custom column options.

New in 9.0.018.01

This release contains the following new features and enhancements:

Users can now select to view the Label column in the Create/Edit contact list preview screen.
When configuring a filtering rule, users can now select an ascending or descending order using a slider widget instead of a drop-down list.
Users can now configure the Caller ID Set modal window using a slider widget instead of a checkbox.
When a Selection rule is selected in the List Rules table, the right side of the view now includes field names. Previously, the view only included Other values.
Importing Contact Lists with Splitting rules now takes less time. The process was optimized in the List Builder.
You can now download and export a Selection Rules as a .JSON file.
A new Non-Geographic option has been added to the drop-down list for the Device Mask field option while creating/editing advanced selection rules.
Device Escalation check boxes for Answer Machine Delivery have been replaced with drop/connect switches.
The Advanced button in the Delivery Option section of the Treatment tab has been replaced with a more prominent button.
The CX Contact Analytics PDF Export document option now includes additional details. The PDF now includes a Report title, Dashboard name, Index name, and the report's time frame.
User-defined Other1-OtherN fields of type string can be added to the CX Contact Analytics Device Import Detail Records Dashboard.
CX Contact now checks for Non-Geographical numbers during the pre-loading phase of a campaign group.
A Non-Geographical numbers filter option was added to the Dialing Profile filter options.
CX Contact now supports a Caller ID set (with multiple Caller List IDs (CLI) instead of a single CLI assigned to the Campaign Group.
When configuring a Dialing Profile you can now select a Caller ID set (includes multiple CLI), instead of the single CLI assigned to the Campaign Group level.
Selection Rules can now identify the validity of devices.
CX Contact Analytics SMS/EMail Records Dashboard now supports storing the final state of the SMS Aggregator in the providerReceipt field. This field enables users to review the final SMS delivery state as it was received from the SMS Aggregator.
For auditing purposes an invalid device can now be imported into a Target Contact list. As a result, records are not rejected during the import process.

New in 9.0.000.17

This release contains the following new features and enhancements:

Due to the nature of LIFO (Last in First Out) campaigns, Time Remaining statistics are not displayed in the UI.
During the editing of an active/running Campaign Group, all Dialing Profile options that only take effect after a campaign group restart are now either disabled or show a “campaign is running” prompt when trying to edit.
Labels can now be exported and imported.
Campaign Groups / Dialing Profiles now support LIFO (Last In First Out) Dialing modes.
Outbound Analytics now displays a yellow warning ribbon and a red error ribbon.
A new Found In column has been added to the Suppression List Table view. That is, when you search for a suppression record the target Suppression List in which the match was found is now shown in the results.
A new Search option is now available for all drop-down menus.
Outbound Analytics—It is now possible to export panels to a .csv file.
Outbound Analytics—It is now possible to export panels and dashboards to a .pdf file.

New in 9.0.000.16

This release contains the following new features and enhancements:

Searching for records in suppression lists now supports multiple list search options. Previously, only one suppression list was available to search against.
The Treatments view no longer appears as a modal window. A new Summary tab has also been added to the sub-menu.
In Analytics, a new sumtable panel is now available.
A new treatment Copy Contact has been added to the list of available Retry Options. The Copy Contact treatment can be applied to the call result or disposition code and allows to copy an active contact into a different contact list either as General or as Rescheduled.

New in 9.0.000.15

This release contains the following new features and enhancements:

In the Campaign Template > Dialing Profile and Campaign Group > General tabs the Wireless filter has been renamed Mobile and a new Landline filter option has been added.
Location rules now support an asterisk wildcard as part of the postal code.
The Contact List table now includes a Caller ID column.
Horizontal scrolling is now supported for the User Actions Dashboard > Audit Panel.
The Analytics Dashboard > Terms Panel now supports more than one field.
When working with CX Contact Analytics you can now apply Time Picker settings to each field.
The Control Panel has been removed from the Dashboard Configuration options.
When importing a Contact List you can now search for the correct Upload Rule > Custom Splitting option.
An exported Data Mapping schema can now be imported into CX Contact.

New in 9.0.000.14

This release contains the following new features and enhancements:

List Builder now nullifies binary characters during ingestion.
When editing a contact list, the Caller ID is now displayed and can be modified.
Contact Time rules are no longer limited to 15-minute increments. You can now specify a value (in Minutes) in the Minutes option.
It is now possible to manually delete contact information records from a suppression list.
When creating a List Automation job for exporting contact lists, it is now possible to select a Use label option. This option replaces the Other1-OtherN fields with the field names from the associated list labeling schema.
It is now possible to configure the Time format on an Analytics dashboard.
When downloading a contact list from the User Interface, CX Contact now replaces the Other1-OtherN user-defined fields with the field labels assigned to the contact list.
CX Contact Analytics now includes a new User Actions index to audit user events. The system administrator can now track who did what and exactly when.
When importing a contact list, you now see a progress bar in the Size column. The progress bar displays the current status of the import process.
A yellow warning icon was added next to problematic services in the About Help > Current Version section of the User Interface.
The CX Contact Analytics SanKey panel can now support additional parameters. Previously, this panel only supported three parameters.
You can now edit a CX Contact Analytics dashboard label. This new option enables you to define each system field value name.
The User Interface now supports a tabular layout, meaning that pages now open in new tabs, allowing you to easily switch back and forth between tasks. Previously, the current page closed when you navigated to a new page within the User Interface.

New in 9.0.000.12

The following enhancements have been made to the Analytics tab:
- The navigation bar now continually floats at the top of the Analytics tab screen. This allows the user to access the navigation bar without scrolling to the top of the page.
- You can now save multiple dashboard views per Elasticsearch index.
- You can now resize each Analytics tab panel when editing the panel. To resize the panel, move the cursor to the edge or corner of the panel and use the double-headed arrow to increase or decrease the size.
- You can now rename a panel after it is created.
The Call wait connected timeout option is now a permanent option on a campaign object's Advanced tab. Users can now easily and quickly set a maximum value for the timeout by seconds option.
When you create or edit a Selection rule with a Device1 - Device10 field type, the following two new operators are now available.
- is valid
- is not valid
These operators provide device validation during ingestion against the Genesys Integrated Global Numbering plan.
Custom Time Zone is now stored as a script object within configuration server. As a result, you can now control permissions and access the Custom Time Zone objects.
When configuring a suppression list, you can now specify the duration of the record retention. This means that records added to the suppression list will be retained within that suppression list for the period of time they are configured and automatically purged at the end of that duration.

New in 9.0.000.11

CX Contact now includes support for the SMS channel. More specifically, you can use the CX Contact user interface to do any of the following:
- Create SMS outbound alert templates for one-way text messaging campaigns.
- Create and modify message content for initial outbound messages, opt-out/stop responses, and help responses.
- Personalize message content (for example, greet the customer by name).
Note: This functionality is available to Cloud customers only.

Refer to the Create an SMS Template page in the CX Contact Help manual for more information.

CX Contact now includes support for the Email channel. More specifically, you can use the CX Contact user interface to do any of the following:
- Create outbound email alert templates.
- Use a built-in visual editor to create message content (text and images) or upload an HTML file that contains the message content.
- Personalize message content (for example, greet the customer by name).
- Add an Unsubscribe option.
Note: This functionality is available to Cloud customers only.

Refer to the Create an Email Template page in the CX Contact Help manual for more information.

When a contact uses the Opt-out or Unsubscribe option within a text message or email, the record is automatically added to a contact suppression list, called CXContactSMSOptOut and CXContactEmailOptOut, respectively. These suppression lists have the following characteristics:
- The type is set to Device.
- The suppression list is set to Required.
- The suppression list Never expires.
- The suppression list cannot be deleted.
Note: This functionality is available to Cloud customers only.

You can now use the Analytics tab in the user interface to create custom dashboard views of the following Elasticsearch data:
- Device imports
- Pre-loading events
- Campaign Group events
- Call results
- Contact history
- SMS/Email events

New in 9.0.000.10

This release includes only resolved issues.

New in 9.0.000.09

CX Contact now supports call treatments based on disposition codes. In the event a treatment is defined for both a call result and a disposition code, CX Contact gives priority to the disposition code when applying the call treatment. Refer to the Delivery and Retry Options page in the CX Contact Help manual for more information.

For call treatments (Retry Options), the Apply to Record menu now includes a Suppress option that allows you to suppress a record (by client ID or by phone number) that meets the treatment criteria. When you select this option, you must specify a suppression list for the suppressed record from the new Suppression List menu, which contains all suppression lists set to Never expire. Refer to the Delivery and Retry Options page in the CX Contact Help manual for more information.

CX Contact now supports historical reporting of unattempted (suppressed) records through Elasticsearch and Genesys Info Mart. Once CX Contact writes the data to an Elasticsearch index, Genesys Info Mart extracts the data and transforms it into Genesys Info Mart LDR_* tables.
For detailed information about this functionality, refer to the Integrating CX Contact with Genesys Historical Reporting page in the CX Contact Deployment Guide.

On the General tab of a dialing profile, campaign template, and campaign group, a new Filtering Rule menu replaces the following menus:
- Labels
- Contact Order
- Ascending/Descending
A filtering rule encompasses all of these options.

On the Campaigns dashboard, the List Size field has been renamed List Size/Devices, and the Filtered field has been renamed Contacts Filtered/Devices Filtered. The previous release (9.0.000.08) introduced the new Devices and Devices Filtered statistics but excluded updates to the field names.

New in 9.0.000.08

A new filtering rule allows you to sort and order contact data within in a contact list. Unlike upload rules and selection rules, a filtering rule can be applied while a campaign group is running. It does not have to be applied at the time a list is being uploaded to CX Contact.
The Filtering Rule option replaces the Contact Order option on the General tab of a dialing profile, campaign template, and campaign group.

Related Documentation: Filtering Rules

There are now two types of upload rules:
- Contacts - The selection rule applies to a contact list.
- Suppression - The selection rule applies to a suppression list.
Related Documentation: Upload Rules

There are now three types of selection rules:
- Contacts - The selection rule applies to a contact list.
- Suppression - The selection rule applies to a suppression list.
- Advanced - The selection rule applies to a contact list export and filtering rules. When defining the filtering criteria for this type of rule, you can now define an SQL WHERE clause in place of the standard visual editor.
Related Documentation: Selection Rules

You can now duplicate a condition set being applied to a selection rule. Related Documentation: Conditions and Condition Sets

On the Campaigns dashboard, the Filtered cell now includes the total number of filtered devices from the contact list, in addition to the total number of filtered records. The count is displayed as Records Filtered/Devices Filtered. Related Documentation: View Campaign Statistics

On the Campaigns dashboard, the List Size cell now includes the total number of devices contained in the contact list, in addition to the total number of unique records. The count is displayed as Record Count/Device Count. Related Documentation: View Campaign Statistics

On the campaigns dashboard, the Expand All option, which is used to view campaign groups and contact lists associated with each campaign template, now functions as follows:
- Click Expand All once to view all campaign groups associated with each campaign template.
- Click Expand All again to view all contact lists associated with each campaign group.
The Collapse All functionality remains unchanged. Related Documentation: Search or Filter Campaign Statistics

Contact lists exported from CX Contact now include compliance classification data for each device (record in chain), including:
- Wireless
- Duplicate Position
- Duplicate List
- International
- Ends in 00
- Ends in 000
- TPS/DNC
- Toll Free
- Duplicate Contact
- Contains Extension
- VoIP

Contact lists exported from CX Contact now store all devices associated with each record in a chain.

You can now create a campaign group against an individual campaign template using the More Actions menu (displayed as an ellipsis) on the Campaigns dashboard. When you do this, the campaign template and associated parameters will automatically populate on the New Campaign Group page. Related Documentation: Create a Campaign Group

You can now duplicate attempt rules and location rules. The duplicated rule will inherit all settings from the original rule, but you can change any or all of them. If you do not change the name of the rule, it will inherit the name of the original rule, with _duplicate# appended to it. Related Documentation: Compliance Tools

The user interface now contains a context-sensitive Help tool that enables you to view Help content relative to the page you're viewing in the user interface. To access the tool, click the question mark icon in the top right-hand corner of the user interface.

The width of each menu on the General tab for a dialing profile, campaign template, and campaign group has increased by 50%.

New in 9.0.000.07

On the Treatment tab for a dialing profile, campaign template, or campaign group, you can now specify a URI to a stored SCXML treatment script. When you do this, the system applies all treatment configuration defined in the SCXML treatment script and ignores all treatment configuration previously defined in CX Contact.
For more information, refer to the SCXML-based Treatments page.

The new data mapping feature is an alternative to using an input specification file to map contact data to fields in a CX Contact contact list. You can create a data mapping schema for either a fixed-position file or a delimited file and then apply the schema to a list being imported into CX Contact via manual import or via list automation.
For detailed instructions, refer to the Create a Data Mapping Schema page.

For call treatments, the Increment retry option is no longer a mandatory option. Previously, if you selected Retry in from the Apply to Record menu, you had to define an increment value.

On the Campaigns dashboard, an icon now displays to the right of a campaign group name to indicate the type of dialing mode the campaign group uses. When you hover over the icon, the name of the dialing mode and associated dialing parameters display in a text box.
For more information, refer to the Create and Manage a Campaign Group page.

The media control icons on the Campaigns dashboard have increased in size and have changed in color. In addition, a new status bulb displays next to the media controls to indicate the status of the campaign group.
For more information, refer to the Create and Manage a Campaign Group page.

New in 9.0.000.06

You can now use the List Automation feature to schedule a contact list export. The file is exported out of CX Contact and sent to a remote FTP directory.
For a complete description of this feature, refer to the Create and Manage List Automation Tasks page in the CX Contact Help manual.

The new Device Escalation feature enables you to do any of the following when records in a contact list contain more than one device:
- Identify which device(s) should be contacted.
- Specify the order in which the devices should be contacted.
- Specify how to handle answering machine detection - drop the call, deliver the call to an agent, or send the call to a DN for treatment (for example, leave a pre-recorded message).
For a complete description of this feature, refer to the Apply Device Escalation page in the CX Contact Help manual.

In the Timezone source field, a new option, called Explicit, enables you to select a specific time zone for records in a contact list. When you apply this option, the system ignores all Contact and Device time zone assignments, so we do not recommend this option if your contact list contains international numbers or countries with multiple time zones.
For more information, see the Time Zone Assignment page in the CX Contact Help manual.

Support for the following operating system, databases, and browser. See the CX Contact page in the Genesys Supported Operating Environment Reference Guide for more detailed information.
- Red Hat Enterprise Linux 7
- PostgreSQL 9.5
- Elasticsearch Cluster 6.3x
- Google Chrome

What's New in Bot Gateway Server for 9.0

[+] The following new features were introduced in the 9.0.008.05 release:

[+] The following new features were introduced in the 9.0.006.04 release:

[+] The following new features were introduced in the 9.0.005.05 release:

[+] The following new features were introduced in the 9.0.004.08 release:

9.x

Find all PureEngage products that are currently part of 9.x — the latest Release Notes, as well as the particular component releases when support for 9.x started.

Important

9.x can include component releases from 9.1x, 9.0.x, and 8.5.x code streams. Use the tables below to check which component releases are part of 9.x.

Billing Data Server

No results

Product	Component	Latest	Starting
		9.x Release Notes

Bot Gateway Server

Product	Component	Latest	Starting
		9.x Release Notes
Bot Gateway Server

	Bot Gateway Server	9.0.011.02	9.0.004.08

CX Contact

Product	Component	Latest	Starting
		9.x Release Notes
CX Contact

	CX Contact	9.0.030.04	9.0.000.06

Genesys Administrator

Product	Component	Latest	Starting
		9.x Release Notes
Genesys Administrator Extension

	Genesys Administrator Extension	9.0.108.03	9.0.000.15

Genesys Decisions

Product	Component	Latest	Starting
		9.x Release Notes
Genesys Decisions

	Genesys Decisions	9.0.000.12	9.0.000.01

Genesys Intelligent Automation

Product	Component	Latest	Starting
		9.x Release Notes
Genesys Intelligent Automation

	Genesys Intelligent Automation	9.0.128.06	9.0.000.01

Genesys Knowledge Center

Product	Component	Latest	Starting
		9.x Release Notes
Genesys Knowledge Center

	Genesys Knowledge Center Plugin for Workspace Desktop Edition	9.0.006.21	9.0.000.15
	Genesys Knowledge Center Server	9.0.006.34	9.0.000.15
	Recording Processor Script	9.0.006.07	9.0.000.15

Genesys Predictive Routing

Product	Component	Latest	Starting
		9.x Release Notes
Genesys Predictive Routing

	AI Core Services	9.0.015.11	9.0.006.05
	Predictive Routing - Agent State Connector	9.0.015.04	9.0.006.06
	Predictive Routing - Composer Strategy Subroutines	9.0.009.00	9.0.006.01
	Predictive Routing - Data Loader	9.0.021.01	9.0.016.09
	Predictive Routing - URS Strategy Subroutines	9.0.020.00	9.0.006.00

Genesys Pulse

Product	Component	Latest	Starting
		9.x Release Notes
Genesys Pulse

	Genesys Pulse	9.0.010.01	9.0.000.02
	Genesys Pulse Collector	9.0.010.02	9.0.000.04

Genesys Softphone

Product	Component	Latest	Starting
		9.x Release Notes
Genesys Softphone

	Genesys Softphone	9.0.103.00	9.0.001.01
	Genesys Softphone VDI Adapter	9.0.103.00	9.0.005.06

Genesys Widgets

Product	Component	Latest	Starting
		9.x Release Notes
Genesys Widgets

	Widgets	9.0.018.07	8.5.006.07

intelligent Workload Distribution

Product	Component	Latest	Starting
		9.x Release Notes
intelligent Workload Distribution

	iWD GAX Plug-In	9.0.022.05	9.0.002.20
	iWD History Node	9.0.022.03	9.0.002.20
	iWD Manager	9.0.022.05	9.0.002.20
	iWD Runtime Node	9.0.022.01	9.0.002.20
	iWD Stat Server Extensions	9.0.022.01	9.0.002.20
	iWD Web	9.0.022.01	9.0.002.19

Management Framework

Product	Component	Latest	Starting
		9.x Release Notes
Management Framework

	Configuration Database Maintenance Scripts	8.5.100.23	8.5.100.18
	Configuration Server	8.5.102.13	8.5.101.11
	DB Server	8.5.100.27	8.5.100.01
	Local Control Agent	8.5.100.44	8.5.100.22
	Message Server	8.5.100.47	8.5.100.14
	Solution Control Server	8.5.100.65	8.5.100.25
Security Pack on UNIX

	Genesys Security Pack on UNIX	8.5.100.34	8.5.100.13

PureEngage Chat

No results

Product	Component	Latest	Starting
		9.x Release Notes

Universal Contact Server

Product	Component	Latest	Starting
		9.x Release Notes
Universal Contact Server

	Genesys Data Processing Server	9.0.000.04	9.0.000.04

Billing Data Server

Bot Gateway Server

CX Contact

Genesys Administrator

Genesys Decisions

Genesys Intelligent Automation

Genesys Knowledge Center

Genesys Predictive Routing

Genesys Pulse

Genesys Softphone

Genesys Widgets

intelligent Workload Distribution

Management Framework

PureEngage Chat

Universal Contact Server

Contact

Genesys

Customer Care

Legal

What's New in Security Pack for UNIX for 9.0

December 06, 2019

January 31, 2019

November 30, 2018

August 31, 2018

July 10, 2018

December 22, 2017

August 22, 2017

What's New in Management Framework for 9.0

December 17, 2021

November 09, 2021

September 30, 2021

August 11, 2021

January 29, 2021

June 26, 2020

March 27, 2020

February 28, 2020

December 06, 2019

September 27, 2019

July 30, 2019

June 26, 2019

May 28, 2019

April 26, 2019

February 28, 2019

January 31, 2019

November 30, 2018

August 31, 2018

August 10, 2018

July 10, 2018

June 8, 2018

May 8, 2018

March 27, 2018

March 6, 2018

January 26, 2018

December 22, 2017

September 26, 2017

August 22, 2017

What's New in Genesys Softphone 9.0.0

03/25/21

12/17/20

09/24/20

06/25/20

11/14/19

06/27/19

05/10/19

02/28/19

12/21/18

05/31/18

03/17/18

What's new in Genesys Pulse for 9.x

Introduced in 9.0.006

Introduced in 9.0.005

Introduced in 9.0.004

Introduced in 9.0.003

Introduced in 9.0.002

Introduced in 9.0.001

Introduced in 9.0.000

Localization support

New in AICS 9.0.015.03/ASC 9.0.015.04/URS Strategy Subroutines 9.0.015.00 (07/19/2019)

New in Release 9.0.015.00 (03/26/2019)

New in Release 9.0.014.00 (12/21/2018)

New in Release 9.0.013.01 (10/25/2018)

New in Release 9.0.012.01 (08/23/2018)

New in Release 9.0.011.00 (07/13/2018)

New in Release 9.0.010.01 (05/11/2018)

New in Release 9.0.009.00 (03/28/2018)

New in Release 9.0.008.00 (03/05/2018)

New in Release 9.0.007.01 (01/05/2018)

New in Release 9.0.007.00 (12/22/2017)

New in Release 9.0.006.00 (09/26/2017)

New in Release 9.0.005.00 (06/27/2017)

New in Release 9.0.004.04 (03/28/2017)

New in Release 9.0.003.00

New in Release 9.0.000.00

New in 9.0.111.31

New in 9.0.110.23

New in 9.0.109.06

New in 9.0.109.03

New in 9.0.109.00

New in 9.0.107.00