Release Notes
- Former user (Deleted)
Summary
This ECM release includes the bug fixes and compatibility with UCCX 11.6.
What's New
ECM 13.1 comes with the bug fixes, logs improvement and with the UCCX (11.6) compatibility.
- Compatibility of ECM with UCCX 11.6
Compatibility of ECM with UCCX11.6
This release is compatible with UCCX 11.6
Fixed Issues
| Summary | Jira Link |
|---|---|
| When the number to call is NULL, it shows error in services logs | EAP-10088 - Getting issue details... STATUS |
| An issue in syncing ECM records | BAR-37 - Getting issue details... STATUS |
Open Issues
| Summary | Jira Links | Resolution Plan |
|---|---|---|
| The version appearing on the interface of the application is not correct. | EAP-10817 - Getting issue details... STATUS | Marked for the next release |
| After defining the application setting from the interface of the application, the user needs to restart the docker-compose. | EAP-10827 - Getting issue details... STATUS | Marked for the next release |
| Incorrect error messages keep on displaying during HA "Back server not working" and "UCCX is down" | EAP-10411 - Getting issue details... STATUS | 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 - Getting issue details... STATUS | 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 - Getting issue details... STATUS | Marked for the next release |
| Using “Update Campaign API”, the user can also change the strategy of an enabled/active campaign. | EAP-8035 - Getting issue details... STATUS | 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 - Getting issue details... STATUS | 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 |
|---|---|
| PCS survey integration has not 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 |