Release highlights

We have improved load times in the Call Detail report.

Load times for large amounts of data should now be shorter. In addition, a loading spinner will display while the data is being retrieved.

When calling an SRV-based SIP URI, calls will now fail over to the lower/secondary endpoints when necessary.

Previously, if an SRV record was configured with differing priority values, Mindful would continue to attempt the primary endpoint after the timeout was reached. Now, calls will be sent to the secondary endpoints in this scenario.

Fixed issues

API-related issues

(MENG-1042) An issue causing the Update a Call Target endpoint to unexpectedly return an error has been resolved.

When the enableCallbackRegistration attribute was False, all requests to the Update a Call Target endpoint would return a 400 Bad Request error, and the requested update would not be made. Now, updates can be made regardless of the value of enableCallbackRegistration.

(MENG-1029) In the Get Offer Decision Attributes response, the shouldOffer attribute will no longer return True when Max ECBT or Max Requested Callbacks are exceeded.

Previously, if the Max ECBT or Max Requested Callbacks were exceeded, shouldOffer would return True, which is not expected. The shouldOffer attribute will now return False in this scenario.

(MENG-647) The Retrieve Real-Time Call Target Statistics endpoint will now validate the callTargetId path parameter and return an error for invalid formatting.

Previously, it was possible to submit a request with an improperly formatted callTargetId, which must be a numeric string with no leading zeros. The request would technically succeed but would return empty results. Now, a 400 error response will be returned instead.

(MENG-1020) The processingEnabled attribute will always be included in the response of the Retrieve Offer Decision Attributes endpoint.

Previously, processingEnabled was only included in the response when the value was False.

Other issues

(MCT-161) An error causing some Smart Rules not to trigger has been resolved.

If a Smart Rule used a Time of Day condition without a Day of Week condition, the rule could be saved, but it would not trigger when the condition was met. With this release, Smart Rules will trigger as expected in this scenario.

(MENG-1054) A loading spinner will display while the user profile page loads.

Previously, there was no visual indication that the user profile (account) page was loading.

(MENG-1067) An issue preventing some SSO users from logging in has been resolved.

A rare issue related to unexpected attribute mapping by an external SSO identity provider caused some users to see an error when attempting to log in.

(MENG-1044) New Call Targets with default configuration will no longer offer scheduled callbacks until one of the Offer Scheduled Callback options is enabled.

When a Call Target is created, the default configuration does not include scheduled callbacks. Previously, the scheduling offer was being played to clients, even though scheduled callbacks could not be registered in this scenario. Now, the scheduling offer will not be made until it is enabled for a new Call Target.

(MCB-3611) An issue causing Mindful auto-generated emails not to be sent to some users has been resolved.

After a recent change to our email provider's handling of automated out-of-office replies, Mindful began blocking outbound emails to addresses that responded with an out-of-office reply. This update will address the issue and ensure that emails will continue in this scenario.

(MCT-119) An issue preventing SSO users from disabling the session timeout on reporting pages has been resolved.

Previously, when an SSO-enabled user account was assigned a role with the session timeout disabled, the user would still be logged out when the timer expired. Now, applying such a role will prevent the automatic logout for these users.

(MENG-381) An issue causing Reporting Categories to continue displaying in the UI after being removed has been resolved.

If a saved Reporting Category was removed from a Call Target, it would continue to display in the UI until the new changes were saved. Now, the category will disappear from the UI as soon as it is removed.