100.0.100.05
EX Engage Connector Conversation Provider Service Release Notes
| Release Date | Release Type | Restrictions | AIX | Linux | Solaris | Windows |
|---|---|---|---|---|---|---|
| 07/28/23 | General | X |
What's New
This release contains the following new features and enhancements:
- This release includes only resolved issues.
Resolved Issues
This release contains the following resolved issues:
In agent-initiated outbound call scenarios, when a Consult call is established through a routing point and the agent released the call after transfer completion, the call was not released in Genesys Cloud. This issue has been resolved. (CCECP-653)
Previously, in a two-step transfer scenario, if the customer hung up before the transfer process started, the Genesys Cloud UI showed the call as transferred instead of showing that both the main and consult calls were released. Now, the Genesys Cloud UI correctly displays the calls as released in such scenarios. (CCECP-650)
If an agent does a single-step transfer on a call, which was previously processed on a routing point, then the GC EX Org fails to detect it as a blind transfer in the injected conversation. This issue has been resolved. (CCECP-647)
Previously, if an Engage call traverses multiple routing point DNs used by URS for target selection, then the corresponding GC conversation may be built incorrectly. In particular, it may be positioned as Abandoned and/or GC conversation may represent only part of the Engage call. Now, the correct routing point is shown as abandoned. (CCECP-642)
Upgrade Notes
No special procedure is required to upgrade to release 100.0.100.05.