8.5.101.26
Configuration Server Release Notes
| Release Date | Release Type | Restrictions | AIX | Linux | Solaris | Windows |
|---|---|---|---|---|---|---|
| 09/28/18 | General | X | X | X | X |
Contents
Helpful Links
Releases Info
Product Documentation
Genesys Products
What's New
This release contains the following new feature or enhancement:
- Configuration Server now supports selecting objects using their DBIDs, according to the delegated user permission while passing the delegate_dbid and delegate_type filters. This enhancement is done for the Pulse application needs starting from Pulse 9.0.002.xx release.
Resolved Issues
This release contains the following resolved issues:
With certain databases such as MS SQL, Configuration Server in the single-language mode with multibyte locales (such as Japanese) had failed to save long (>254 bytes) values of application options or object annex entries, which contained multiple multibyte characters with 0x27 and 0x60 bytes as trailing bytes. In this scenario, Configuration Server now stores the whole string correctly in the database. Previously, an error was generated stating that the string was too long and would be truncated. (MFWK-20647)
Configuration Server now updates the force-offline option correctly restricting it to master Configuration Server object only. Previously, the option was allowed to add to other Configuration Server type application object, and if any application object was deleted and update request came for the deleted application object, then this lead to unexpected termination of Configuration Server. (MFWK-20575)
When using Kerberos/GSS authentication, Configuration Server now releases file handles when authentication is complete. Previously, the file handles were not released, which caused the maximum number of handles to be reached, after which authentication requests were denied. (MFWK-19890)
When changing permissions of container objects, if any access group allows propagation of a certain permission, this permission now propagates correctly without revoking the affected objects from the connected clients. Previously, if a permission change on a container object resulted in access groups having unequal permission propagation setting—for example, the Propagate setting was disabled for EVERYONE group and it was enabled for the SYSTEM group—the containing objects unexpectedly disappeared from the view of the connected clients. (MFWK-18269)
Upgrade Notes
No special procedure is required to upgrade to release 8.5.101.26.