Skip to main content
Skip table of contents

Release Notes

Summary

This ECM release includes minor front-end changes and bug fixing.

Front-end Changes

The latest uploaded contact appears on top in ECM Report

Previously the latest uploaded contact goes at the bottom of the report. Now in this release, the latest will appears on the top of the report.

Start & End Date filter on ECM Report

In this release, the filter is applied on the Request Date of the contact.  The user filters the records on the base of Start and End & sees the most relevant records.

Fixed Issues

Summary

Jira Link

Handle exception in API container & it remains in an unhealthy state while running smoothly (Health status is not correct)

EAP-11699

PCS Surveys are not appearing when the user uploads the contact in Survey Campaign.

EAP-11695

While uploading the Contact CSV from the front-end, ECM is not taking the dialTime attribute from the CSV

EAP-11706

Open Issues

Summary

Jira Links

Resolution Plan

When the campaign is active, the cisco campaign menu should be disabled (the user should not be able to change the cisco campaign when the ECM campaign is active)

EAP-11767

Marked for next release

When there are 2k or more agents synced on UMM, the assigning and removing of the permissions to the Agent role is taking too much time (40 to 50 seconds approx)  

EAP-11347

Marked for the next release

ECM takes too much time to login user, which has a profile picture of large size.

EAP-11594

Marked for the next release of UMM

After defining the application setting from the interface of the application, the user needs to restart the docker-compose.

EAP-10979

Marked for the next release

Incorrect error messages keep on displaying during HA "Back server not working" and "UCCX is down"

EAP-10411

Marked for the next release

During the loading User Management module, it is seen that the Firefox browser displays a warning message.  Once the page loads the message disappears.

Number of Users 1000 UCCE.

EAP-10331

Marked for next release 

When an outbound call is rejected or resent to the queue by an agent, if the same call gets answered by some other agent while at the same time, ECM fetches the status of contact from CCE, then the status field might have improper values.

Marked for the next release

If a user passes a Cisco campaign with an IVR type while creating an agent-based campaign in ECM through API, the ECM campaign got successfully created

EAP-3408

Marked for the next release

Using “Update Campaign API”, the user can also change the strategy of an enabled/active campaign.

EAP-8035

Marked for the next release

Each attempt in a campaign should have a unique attempt_number otherwise, this might cause problems while rendering or modifying an attempt definition.

EAP-8040

Marked for the next release

We recommend not to press F5/CTRL+F5 to refresh the page. To refresh a list or view new changes, the user must navigate from some other page/list to the current page.

Marked for next release

Important Notes/Limitations

Some limitations in the new release are mentioned below,

Summary

Related Feature

The profile picture of the agent/supervisor on UMM should be less than 150KB in size. Otherwise, it takes too much time to login to ECM.

UMM Integration

PCS survey integration has not been tested in this release.

Survey Integration

The first phone number of the contact is mandatory while uploading the contact CSV. 

ECM Campaign Contacts

In the case of the ECM IVR campaign, It should be noted that the user cannot upload a CSV that contains some value in "Business Param 1" and "Business Param 2". This is because these two Params are used by ECM itself.

ECM Survey campaign and Callback campaign 

The current implementation in ECM only allows uploading contact CSV of 2MB size.

The current implementation in ECM only allows uploading contact CSV of 2MB size.

In the contact list of the campaign, there is no pagination and user have to click on down arrow button to get the next 25 contacts.

ECM Campaign Contacts

While creating an attempt (Voice or SMS) through the API, the attempt definition should be proper. The attempts defined in the improper way will not be accessed from the front-end interface for any modification.

Call Strategy API

With the APIs, attempts are created and stored one after the other.

ECM Call strategies APIs

The “Delay” and the “Expiry” time of SMS in the call strategy should not be more than 120 minutes

ECM Call strategies

ECM is now VM level failover supported. 

Redundancy Support

Cloud deployment of the application is not yet supported

Cloud deployment

Compatibility Guide

OS Compatibility

We require the customer/partner to install the following software on the server.

Item

Version

CentOS 7

Administrative privileges (root) are required to follow the deployment steps.

Database Requirements

Item

Notes

MS SQL Server 2014, 2016 Express/ Standard/ Enterprise


Docker Engine Requirements

ItemNotes

Docker CE

Docker CE 18+ and docker-compose (in case of CentOS)

GitGit install

Browser Compatibility

Item

Version

Notes

Firefox

the latest


Chrome

the latest


IENot testedAn on-demand testing cycle can be planned

Cisco Unified CCX Compatibility

UCCX 11.6

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.