Genesys Web Engagement Server Release Notes
|Release Date||Release Type||Restrictions||AIX||Linux||Solaris||Windows|
This release contains the following new features and enhancements:
- Deployed rule resources are now stored in Cassandra until they are explicitly deleted. Previously, the standard time to live (TTL) value was applied to these resources.
- Web Engagement now allows you to use Agent Group objects as the primary way to configure pacing settings. You can still configure these settings in the Web Engagement Cluster or Web Engagement Server application objects, but settings configured in the Agent Group objects have a higher priority.
- The [pacing] section is no longer required in the Web Engagement Cluster application template, because the pacing algorithm is now primarily configured by Agent Group. You can still configure these options in the Web Engagement Cluster or Web Engagement Server application objects, but options configured in the Agent Group objects have a higher priority.
- A new configuration option, skipCategories, was added to the Tracker Application instrumentation script. When this option is set to true, category information will not be transmitted with the XML issued in response to Web Engagement Server/server/data/category/info requests, thereby reducing network load.
Note: This version was first released as a Hot Fix on 10/31/16.
This release contains the following resolved issues:
Tracking scripts now work correctly, even if the instrumentation does not include a path to a DSL resource. (WM-6874)
Web Engagement now allows you to pass complex JSON objects as field values inside the data property of any event, including both system and business events. Previously, fields inside the data property could only contain string values. (WM-6782)
No special procedure is required to upgrade to release 8.5.000.33.