Release highlights

New limit for Number of Days Out to Allow Scheduling

The Number of Days Out to Allow Scheduling settings (for Voice or Widget/API) will now allow a maximum value of 28 days. The previous maximum was 365 days.

Improved performance for Call Target updates

Load times when saving changes to Call Target configuration in the UI have been improved.

Resolved issues

An applied Access Control Policy (ACP) can now be unselected on the Scheduler API page.

When an ACP was selected and saved on the Scheduler API page, it was not possible to go back to the "Select Access Control Policy" option to remove the ACP. This issue has been resolved, and it is now possible to remove the selected ACP.

Access Control Policies no longer allow duplicate IP addresses.

Previously, no validation was in place to prevent the same IP address from being added multiple times to the same ACP. After this release, an error will be shown in this scenario, and the duplicate IP address will not be added.

The Save button will no longer remain active with no changes to save.

When Dynamic DNIS Mapping was enabled for a Call Target, the Save button remained active at all times, even with no new changes to save. Now, the button will only be active when changes are available to save.

We have resolved another potential cause of stuck calls.

Another cause of calls becoming stuck in a certain state after progressing in reality has been identified and patched.

The Retrieve Callback Offer Decision Attributes API endpoint will now return accurate values when the Max Requested Callbacks is reached.

Previously, when the number of requested callbacks met or exceeded the value of the Max Requested Callbacks setting, the following properties returned "true" when they should have returned "false":

• shouldOffer
• offeringScheduleVoice
• offeringScheduleWidget
• availableTimeslots

We have improved the error message shown when deleting an unnamed Intent response option.

Previously, the error message that was displayed when deleting an unnamed Intent response option used a placeholder for the name, which was blank. We have added a new error message that specifically calls it an "unnamed response".

The Call Target or Category filter on the Callback Status page now functions as expected.

When attempting to filter the Callback Status page by Reporting Category, the filter was not being applied. With this release, we have addressed the issue to ensure the filter works as expected.

The Voice to Text Message Widget dropdown menu will no longer include Scheduler widgets with ACPs applied.

Since widgets selected in the Voice to Text Message Widget menu are intended to be used by customers, any widgets that are secured by an ACP will not be available to select, since an ACP would prevent customers from using the widget.

An issue causing inappropriate alerts has been resolved.

In specific cases, users could see an error message stating "The Call Target doesn't have a widget selected for Scheduled Callback Experience", even when the Scheduled Callback Experience was set to "Voice". We have updated the logic behind this error to ensure it is only seen when appropriate.

An issue that obscured the Logout button in the user settings menu has been resolved.

In some cases, the Logout button in the user settings menu in the top navigation bar was hidden behind other elements on the page.

We have added a character limit to metric names on the Callback Status page to prevent potential errors.

Previously, with no limit to the number of characters allowed for metrics on the Callback Status page, it was possible to cause an error by entering an extremely long value. We have put a 50-character limit in place to prevent such errors.