Patch corrections

Patch is a correction package that fixes business-critical issues.

We list here the issues fixed from RTT (release to testing) to RTC (release to customer) and onwards.

To see which version your tenant has, open Communication Panel and go to User Menu > Settings > About. The patch number is the last digit in the Version field.

The latest patch includes fixes from all previous patches of the release. For example, corrections made in the first patch release are also in the second one, and so on.

24Q2.2 (RTC, build number 10.0.2405.2)

  • OS notifications for connection lost and automatic status change to not ready had incorrect UI texts.

  • Rmi/contactSummaries incorrectly counted only current day conversations.

  • In a specific scenario, the Pick button stopped working in Picklist.

  • In the Dashboard's Conversation Details view, sometimes a minute was shown as 60 seconds in a timestamp.

  • In Serving Status view the duration time wasn't shown in the Availability / Duration column if agent was away.

24Q2.3 (build number 10.0.2405.3)

Fetching emails via OAuth method caused high CEM CPU usage.

24Q2.4 (build number 10.0.2405.4)

  • The AnsweredOnTimeThreshold value in the database is seconds but GET /RI/rmi/contacts returned it in milliseconds. Now RI returns the value in seconds.

  • Several Dashboard issues:

    • A resized home view card was not maintained if the user navigated away and returned to home view.

    • Deleting a tab from home view may have caused focus issues when navigating away and returning to home view or resulted in an 'error' message when logging in.

    • Resizing a home view card and then changing it's configuration did not save the card's new size.

    • Cards that should have had their 'type' options chart and cumulative available had their options disabled.

  • Sinch Contact Pro provides now a deprecation cookie in HTML meta tag. The deprecation cookie is added to mitigate possible problems due to coming 3rd party cookie restrictions in Chrome and chromium based browsers (such as Edge).

  • Sending new messages via Wavy WhatsApp failed.

24Q2.5 (build number 10.0.2405.5)

  • Continuous progress tone heard. While having an embedded CP and pop-out CP window open call progress tones should only have been controlled and played by the pop-out CP. IDs: SCC-11960, SCC-12256

  • Creating a new web chat may not have been possible if a previous web chat was ended by closing a browser or tab. IDs: ID: SCC-11264, SCC-10204