outbound.delay-voice-state-change.timeout
Section: interaction-workspace
Default Value: 0
Valid Values: An integer value greater than 0.
Changes Take Effect: When the session is started or restarted.
Specifies the duration in milliseconds for which Agent Desktop will delay changing the state of the Voice channel to Ready, to allow completion of any Outbound interaction that is being marked done.
8.5.203.05
Web Services and Applications Release Notes
| Release Date | Release Type | Restrictions | AIX | Linux | Mac | Solaris | Windows |
|---|---|---|---|---|---|---|---|
| 11/22/23 | General | X |
Helpful Links
Releases Info
Product Documentation
Genesys Products
What's New
This release includes only resolved issues.
Resolved Issues
This release contains the following resolved issues:
Workspace Web Edition
When an agent opens an inline forward email that was stored in the draft Workbin, the email along with its content is now displayed in Agent Desktop. Previously, when such emails were opened, the content was not displayed in Agent Desktop. (HTCC-32040)
The Voice channel of the agent is now correctly logged in, if the Voice server associated with that Voice channel is started. Previously, in some scenarios, the Voice channel appeared as Out Of Service after logging in and the agent could not change the state of the channel. (HTCC-32020)
For a voice interaction, the Disposition Code might be lost if the agent selects the disposition after the voice interaction is released, and after the Agent Desktop browser page is refreshed while handling the voice interaction. To avoid this problematic situation, set the interaction.disposition.check-if-voice-interaction-idle option to true. (HTCC-32019)
If the agent, after handling a push-preview interaction with a customer, re-dials the customer using the Party menu, the agent can now mark the interaction as Done once the call is completed. Previously, in such scenario, Mark Done was failed and the interaction remained open in Agent Desktop. (HTCC-32014)
When an agent sets the Voice channel as Ready immediately after marking an Outbound Campaign call as Done, the selected disposition for that record was lost. To resolve this issue, set a time delay in milliseconds in the new option outbound.delay-voice-state-change.timeout. The duration set in the option delays the request to change the state of the agent to Ready thereby allows the completion of any operation on the Outbound record before changing the state. (HTCC-32002)
Facebook interactions now display images attached to both Facebook Post and Comment. (HTCC-31960)
Web Services API
Genesys Web Services (GWS) is now compatible with browsers that support Cookies Having Independent Partitioned State (CHIPS). To enable opt-in to use CHIPS (adding Partitioned cookie attribute), add the following configuration in the application.yaml file. (HTCC-32061)
jetty:
cookies:
partitioned: trueGWS installation package now performs the correct post-installation procedure. Previously, if GWS was installed on Red Hat Enterprise Linux 8 (RHEL) in a non-default location, the post-installation script incorrectly configured the service that prevented starting the service in SystemD service manager. (HTCC-32041)
GWS now uses the blocking strategy for all internal caches to reduce the load on Cassandra nodes and CPU utilization on GWS API nodes if there are multiple concurrent API requests. To enable the blocking strategy, add the following configuration in the application.yaml file. (HTCC-32036)
serverSettings:
cachingSettings:
enableSystemWideBlockingStrategy: trueMultiple security upgrades (including SpringBoot, SpringFramework, SpringWeb, Jetty, Netty, FasterXML (Jackson), etc.) were done to remediate existing vulnerabilities. (HTCC-31997)
CRM Gplus Adapters
Workspace Web Edition deployed as an embedded application in Salesforce Lightning Experience
- The Adapter now sends DNIS in the Salesforce Screenpop's search query. To use this feature, enable the screenpop.include-dnis-in-search option in the crm-adapter section. (HTCC-31987)
Upgrade Notes
If you have used SSL (HTTPS) for Web Services API with a previous version of Web Services and Applications, extend the existing configuration in the application.yaml file by providing the certificate key alias name and an explicit configuration for TrustStore (previously it was optional). For more details, refer the following configuration:
jetty:
ssl:
certAlias: < key alias for certificate in JKS >
trustStorePath: < path to JKS, can be the same as keyStorePath >
trustStorePassword: < password for JKS >