• 3.14 • 3.15

New Features

Feature	Description
Get Available Agents API Call	The scenario can use an API call to check whether or not agents in the Ready state are available to handle a specific service.
Fetch URL Can Handle HTTP Responses	The Fetch URL scenario block handles 3xx HTTP response codes for redirects.
PostgreSQL Driver	Version 3.14 adds a PostgreSQL driver.
SIP Error Counters (Influx DB Metrics)	SIP error counters are available through metrics.
Fetch URL Block Improvements	The Fetch URL scenario block fetches web content from the specified URL using more request types/methods: GET, POST, PUT, and DELETE. Administrators also have the capability to write in other methods manually.
Blacklist Chat Client	This capability allows agents to end a chat session and blacklist chat customers by typing a command in the chat message dialog.
Removed Logging to Browser Console By Chat Client	The chat client no longer logs in to the browser console.
Screen Recording Playback Fixes	Multiple instances of screen recording playback (e.g., multiple supervisors using screen recording playback simultaneously) do not cause disk and CPU overload.
Form Widget with a Confirmation Request	In the Form Builder, the Disposition button, Call Number button, and Complete button have a Validation URL parameter that, when specified, ensures that dispositions, calls, and the completion of calls must include the latest data (from form fields) in order to be set.
BPClient Improvements	A link to the newest version of the installer has been added to BPClient.
Scheduler Concurrent Task Limit	The task scheduler has a configurable limit that limits the number of tasks that can be executed concurrently by task type (e.g., two report generators, three campaign result exports, three start-stop campaign tasks, etc.). This limit allows scheduled tasks to remain open and available for execution (i.e., to not expire) until the next time it is scheduled to run. The limit is set in the advanced options.
Web Screen Pop Block with ZenDesk Integration	The scenario engine enables both web screen pop and CRM screen pop by using subsequent blocks in a scenario. The scenario engine controls such screen pop configuration and sends information about all enabled screen pops to the Agent Desktop application.