You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

We are excited to announce the Evolve Contact Suite (ECS) v2024.9.0.50 release will be available on September 22, 2024.

NOTICE:

ECS will deprecate API v1 by EOY 2024. Make sure you are implementing V2 using this URL https://ecs-api.voip.evolveip.net/API/v2/<XXX>


This release contains the following feature enhancements and bug fixes.

Enhancements

  1. eSupervisor - Supervised Agents View enhancements.
  2. eAgent - Prevent page reload while handling a call using webRTC Internal softphone.
  3. eAgent - Directory UI Change.
  4. eAgent - Present CNAM on call offer screen.
  5. eAgent - Improve fetching historical chat messages.
  6. SETUP - Option to disable private interactions per org. Also regardless of this new option, ECS will not allow private interactions with business entities (agents, BP, channel) while on break.
  7. Reports - Report 4.01, 4.02 alignment.

 Bug Fix

  1. eAgent can switch to Ready while on a direct call.
  2. The eAgent Interaction window shows invalid data after a callback was blindly transferred to an agent with an internal ECS device.
  3. SETUP - Rename org
  4. SETUP - Agent Queue feature fixes.
  5. SETUP - Chats are not timing out according to Timeout parameters.
  6. Reports - 2.04 report shows incorrect data.
  7. Reports - Agent Handling segment should be omitted after transferring an interaction.
  8. Directory favorites disappear after version upgrade.


What do you need to know?

  1. Any changes made to your environment must be fully deployed via Setup before the upgrade and previously deployed versions will no longer be available after the upgrade.
  2. If your organization is staffed during maintenance, they will experience a short period of downtime (less than 10 minutes).
  3. Users will get a notification on their first login after the upgrade to accept and download the newest update. Please instruct your users to accept the application update.
  4. For more details about the steps, each customer can take after the release, see the Post-Release Testing.


  • No labels