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:
Previously, in the agent-initiated outbound call scenarios, when a consult call is established via RP and the agent releases the call after transfer completion, the call is getting stuck in Genesys Cloud. Now after the fix, in the above scenario when the agent releases the call, the call is properly released from Genesys Cloud. (CCECP-653)
Previously, in a two-step transfer scenario, when the customer releases the call before the transfer process is started, instead of showing that main and consult calls are released, it is showing that call is transferred in Genesys Cloud UI. Now after the fix, the calls are correctly showed as released in Genesys Cloud. (CCECP-650)
If an agent uses a single-step transfer on a call, which was previously processed on an RP, then the GC EX Org fails to detect a blind transfer in the injected conversation. (CCECP-647)
Previously, if an Engage call traverses multiple RP DNs used by the 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 RP is shown as abandoned. (CCECP-642)
Upgrade Notes
No special procedure is required to upgrade to release 100.0.100.05.