Known Issues and Limitations
The list below shows known issues and limitations in UCS 9.1.
- RMI clients are not supported. These include:
- Knowledge Manager
- UCS Manager 8.x
- Genesys Interaction Server SDK (GIS)
- Agent Interation Layer (AIL), prior to release 7.6.609.00.
- Genesys Agent Desktop
- Custom clients built on top of the UCS API
- UCS reporting metrics by Stat Server (Java Extension) are not supported.
- IDN (International Domain Name) is not supported.
- Social Media Twitter driver 8.5.1 is not supported—the 8.5.2 driver is required. UCS 9.1 does not have an API to store Social Media information when Social Media is used with Twitter driver 8.5.1.
- eServices Manager is not supported.
- Context Services—Attribute names are now case-sensitive.
- Context Services service/state/task is not supported—only Context Services profiles are supported. In UCS 8.x with the API Context Services you could create profiles (which are extensions of contacts) and services (which are storage of information to retrieve the context of previous conversation). Sub-records state and task can be associated with a service. In the initial release of UCS 9.1, only the part of the API involved in creating, getting, updating, and deleting profiles is supported.
- The Context Services Profile API now only accepts JSON arrays in requests. Even single objects must be in a JSON array.
- Role-Based Access Control for Context Services profiles is not supported.
- Single-user mode in Context Service authentication is no longer supported. Only the multi-users mode (authenticating using Persons from Configuration Server) is supported. Configuration options mode, password and username are deprecated. The use-role option is not implemented because Role-Based Access Control (RBAC) is not yet supported.
- Query key extension (singular) is no longer supported. Only query key extensions (plural) is supported.
- The syntax ?extensions=PEPhoneNumber2,PEBodyDescription correctly returns both extensions, but ?extensions=PEPhoneNumber2&extensions=PEBodyDescription ignores the second extension. In 8.5 the second extension was understood.
- In the delete ID key (DELETE /metadata/identification-keys/id_key-name) any kind of identification key (or lookup) can be erased, even one that was not created by the Context Services profile interface.
- When creating an identification key (lookup), a verification that used attribute exists can only be performed when the source is an extension. If the id-key is based on a core profile, this verification cannot be done (because any contact attribute can be added at runtime). So, an id-key based on core profile will always succeed regardless of the attributes used.
- Metadata Cache Refresh—UCS is able to create new tables and add new metadata to handle lookup tables used for identify operations as well as Context Services profile extensions and identification keys. Each UCS node will scan for such configuration changes every 5 minutes. This means that you may have to wait up to 5 minutes to be able to use this new configuration on other nodes. The new configuration is available instantly on the node on which you executed the operation.Note that Context Service production/maintenance modes are no longer relevant—you can perform any operations at any time. However, it is strongly advised to make such changes outside of production hours. Table creation across the cluster can take few minutes and trying to access the new metadata might fail until the operation is completed.
- UCS 9.1 supports only Java 1.8 64-bit (version 22.214.171.124 and higher)—Java 1.7 (which is supported in previous versions of UCS) is no longer supported.
- When Identify is performed on a Multiple lookup (like LastNameFirstNameLookup), the order of the results is not guaranteed, and the parameter ContactId can be any one among all the ContactIdList. Besides, the limit configured in [schema]/select-limit applies to both NumberOfContactsFound and to the IDs in ContactIdList.
- Scroll size limitation—InteractionListGet and ContactListGet are now limited to a maximum display of 10,000 items. The total count will still be accurate. You can, for example, have 1,000 pages of 10 items or 100 pages of 100 items. If you want to scroll over more than 10,000 items you must use several sorted queries—for example, sort by date, and resume the next query from the last date that was returned.
This page was last modified on June 18, 2019, at 01:49.