Genesys Decisions Release Notes
|Release Date||Release Type||Restrictions||AIX||Linux||Solaris||Windows|
This release contains the following new features and enhancements:
- Create and Manage Data Feeds—You can create and manage data feeds from within the Genesys Decisions. Administrators can create a data feed at any time from the list of 16 data feeds included in Genesys Decisions. Administrators can make changes to the data feeds after they are created (for example, file paths and delimiter type). Administrators can test the changes before saving to ensure that Decisions reads the data appropriately. Finally, if the order of the columns in the data files does not match the specification, administrators can change it when managing data feeds.
- Running Data Feeds—You can run all data feeds at the same time by clicking a single button. You can import data from any start and end date or Genesys Decisions can find new data from the last time the data feeds ran. Once complete, Genesys Decisions generates a validation report so that you can confirm Decisions imported all data.
- Identifier Mapping—Staff and Queues are mapped from the source data to the Decisions identifiers. During the Data Feed run process, Genesys Decisions displays any identifiers that have not been mapped for disposition. You can map them to existing Decisions identifiers or create new identifiers.
- Active Directory Authorization—Decisions now leverages the Active Directory membership of users to control who can log into the applications. During the installation or upgrade process, an entry is required for which Active Directory groups users and administrators must be in to gain access to the application. This functionality eliminates the need for the separate Decisions login form, as well as the User Management functionality within the Admin application.
- Chat Concurrency Planning Best Practice—When creating staffing and hiring plans for groups that contain chat contact types, use a planned Maximum Concurrency of 1 for the most accurate answers. The Maximum Concurrency is an environmental variable that is already in the imported historical data used to build the models. The model building process already includes the concurrency that it finds within your historical data.
- Configurable Timeout for Data Feeds—If you experience extreme latency when connecting to the SQL Server containing the Decisions Core Database, you can configure the default timeout for the SQL Queries within the configuration file. Contact customer care before determining whether to use this option.
- Data Feed Migrations—The Database upgrade tool attempts to migrate all existing imports for existing customers. There may be some rare cases where the tool cannot automatically migrate the imports. The tool notifies you if any or all the imports cannot be migrated. Contact customer care if any imports cannot be migrated.
- Additional Database Support—Support for MS SQL Server 2016 database. See the Supported Operating Environment: Decisions page in the Supported Operating Environment Reference Guide for more detailed information and a list of all supported databases and database clusters.
This release contains no resolved issues.
No special procedure is required to upgrade to release 8.5.100.01.
This page was last modified on July 30, 2018, at 06:32.