Corinneh: Published

2022-01-12T16:44:31Z

Published

New page

{{ComponentRN
|ComponentId=e6de2642-136b-4d94-ac3f-724e317bcbc8
|JQL=issue = GES-2755 OR issue = GES-2777 OR issue = GES-2624 OR issue = GES-2670 OR issue = GES-2674 OR issue = GES-2707 OR issue = GES-2729 OR issue = GES-2756
|DeploymentTypeId=ec194bf2-b79a-436d-8ff6-eaff94d9f43a
|ReleaseDate=2022-01-13
|Highlight=*Updates to the Estimated Wait Time API.
*Resolved issues.
}}
{{Issue
|TicketNumber=GES-2756
|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
|LocalContent=If the ORS session of an incomplete callback is terminated after the callback's purge time, GES will no longer restart the ORS session. Instead, the callback will be moved to the COMPLETED state with the reason being PURGED.
}}
{{Issue
|TicketNumber=GES-2755
|IssueCategoryId=720446c8-10b6-42b8-af36-34a298aa1c72
|LocalContent=The Estimated Wait Time API response now includes a new field <tt>resultCode</tt> for the result of each virtual queue. The field has the following values:

*0: A valid estimated wait time was returned for the virtual queue.
*-1: The virtual queue provided is not known to the system. Either the provided virtual queue is invalid, or there have been no interactions in the virtual queue since the last time the system restarted.
*-2: The virtual queue is known to the system, but there are currently no agents logged in and therefore no valid estimated wait time can be returned.
}}
{{Issue
|TicketNumber=GES-2729
|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
|LocalContent=Previously, when testing a phone number on the '''Permitted & Blocked Numbers''' page in the '''Callback''' UI, a valid phone number was sometimes erroneously labeled as too long or too short when the phone number provided was not a North American number. That issue has been fixed.
}}
{{Issue
|TicketNumber=GES-2707
|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
|LocalContent=On the Create Callback API, the error message associated with error code 7055 has been changed from "Desired time can't be honored, wait is too long" to "Desired time cannot be honored – wait time is too long".
}}
{{Issue
|TicketNumber=GES-2674
|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
|LocalContent=Previously, certain types of completed callback reasons failed to display in the '''Callback''' UI. That issue has been fixed.
}}
{{Issue
|TicketNumber=GES-2670
|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
|LocalContent=Privileges-related issues have been fixed in the '''Callback''' UI.
}}
{{Issue
|TicketNumber=GES-2624
|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
|LocalContent=Previously, on the Create Callback API, when a routing point was configured for the service in the Designer CALLBACK_SETTINGS data table under the '''Routing Point''' column, the value of the optional API parameter <tt>routePoint</tt> was ignored, with the default one configured in CALLBACK_SETTINGS being used instead.

GES now uses the value specified in the optional API parameter <tt>routePoint</tt>, when provided, as the routing point used for the outbound call.
}}
{{Issue
|TicketNumber=GES-2777
|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
|LocalContent=When determining if the requested time for a scheduled callback is too close to the current time to be allowed, the estimated duration for all the calls on hold (such as snoozed callbacks) is now included in the Estimated Wait Time (EWT) calculation. Prior to this change, calls on hold were not included in the EWT calculation.

This change impacts two situations:

*Callback Create API, when the <tt>alwaysCheckCapacity</tt> option is set to <tt>true</tt>
*Availability API (always)
}}

RN/Callback/9.0.051.00 - Revision history

Corinneh: Published