Configuration Server 8.5.x Release Notes
|Release Date||Release Type||Restrictions||AIX||Linux||Solaris||Windows|
This release contains the following new features and enhancements:
More secure and efficient agent data retrieval: You can now configure Configuration Server to execute requests, submitted via an internal brief API, taking into account permissions of the parties involved. This reduces the volume of object data downloaded by an application when it discovers available objects. Check with Genesys documentation specific to an application to determine if the application supports using the brief API and if the application can benefit from getting a limited list of brief objects. Use the following new option to enable this functionality:
Default Value: false
Valid Values: true, false
Changes Take Effect: Immediately
When set to true, the results returned by the brief API calls are based on the permissions of the client account that submitted the request.
- Implementing Support of Load-Balancing by Configuration Server Proxy: For one of the ways in which this functionality can be implemented, refer to the "Load Balancing Using Clusters" section of the Workspace Desktop Edition Deployment Guide.
- Secure connections with Microsoft SQL DBMS: You can now configure secure connections between Microsoft SQL databases and Genesys components running Microsoft SQL database client software.
This release contains the following resolved issues:
Configuration Server no longer resets an agent's Wrap-up Time when an annex entry of the Agent Login object associated with that agent is changed. Previously in this scenario, Configuration Server reset the Wrap-up Time to zero (0).
This issue was introduced in 8.1.3; it did not occur in earlier releases.
Configuration Server Proxy no longer terminates unexpectedly when reconnecting to the master Configuration Server Proxy. Previously, this scenario occurred in very rare cases. (MFWK-17172)
Configuration Server no longer returns an empty history log to a client trying to restore a session if, while the client was disconnected, there were failed attempts to update any configuration objects using Configuration Server. Previously in this scenario, Configuration Server returned a history log containing no history records to the client. (MFWK-16946)
Setting or changing the value of the level-reassign-<event> configuration option now always takes effect immediately, as described in the Framework Configuration Options Reference Manual. Previously, when configured on Configuration Server 8.5.x, setting or changing to this option did not take effect until Configuration Server is restarted. (MFWK-16411)
No special procedure is required to upgrade to release 18.104.22.168.