Release Notes 5.3

5.3 Release Notes

Zylinc Cloud Email is here

What if managing customer emails felt smooth, structured and totally under control? With Zylinc Cloud Email, it can. Designed for teams who want to work smarter, not harder, it brings clarity, ownership, and insight to your everyday email handling. Whether you're scaling up or simply want a better way to serve your customers, this is the step forward your inbox has been waiting for.
 👉 Discover how Zylinc Cloud Email makes email effortless (Link).

Cisco On-Prem Call Manager presence

We can now offer user presence from Cisco On-premises Call Manager. This presence will be shown alongside our other presence information for the user and will cover busy/idle/offline states for the users' IP phones.

Agent session timeout reduced to 3 minutes

The platform previously waited 5 minutes of inactivity before logging agents out, during which they could still be offered calls. This led to situations where unavailable agents were offered calls for too long, increasing caller wait times. The session timeout has now been reduced to 3 minutes to better reflect agent availability and improve response times for callers.

Agent Notes

Bug Fixes

• Missing agent icon in presence view: Fixed a bug where the agent icon was not shown in the UI for some logged-in users, even though they were active and able to handle calls. This issue affected presence display and has now been resolved so that agent status icons are shown correctly.
• SMS message not updating when switching conversations:  Fixed a bug where the SMS message field did not refresh when switching between conversations. Previously, the message remained static and did not update with the new caller’s details - such as phone number - when a template using placeholders like {{caller.PhoneNumber}} was selected. This was due to the component state not updating correctly. After the fix, the message field now correctly reflects the selected conversation’s caller information.
• DTMF tones not working for specific numbers: Fixed a bug where DTMF tones didn’t work when calling certain numbers, from the Navigator. The issue was caused by the call state remaining stuck in "Alerting" due to a missing remote party address, which prevented the front-end from recognizing that the call had connected. As a result, the UI failed to display the keypad and continued to show the "Answer" button. The backend logic has been updated to process call events even when only the originator is present, ensuring that the call state transitions correctly to "Active" and DTMF input works as expected.
• Missing Icelandic language option in Zylinc Cloud workspace overview: Fixed an issue where Icelandic was not available as a language option in the Zylinc Cloud workspace overview, despite being present in both the Web Agent and Config Manager. A language mapping mechanism has now been added to ensure consistent availability across interfaces and to support automatic inclusion of future language additions.
• Mobile Agent logged out after 5 minutes without warning: Fixed an issue where Mobile Agents were automatically logged out after 5 minutes of inactivity, even though the app still appeared active. This caused confusion for agents who thought they were still logged in. The problem has now been resolved so that Mobile Agent sessions stay active as expected, without unexpected logouts.
• Web Agent reload prompt keeps reappearing: Fixed an issue where the Web Agent repeatedly showed a reload prompt about a new version of the application, even after following the instructions to refresh with Ctrl+F5 or Cmd+Shift+R. The prompt would disappear temporarily if "Continue" was clicked but would reappear after the next refresh. This behavior has now been corrected so that the message only appears when a new version is actually available.
• Missing translations in "Send Email" and "Send SMS": The label "Caller information" was shown in English for Norwegian and Swedish users due to missing translations. This has been fixed, and the correct translations now appear in both pop-up windows.
• Improved performance when editing Conditional Call Forwarding in Navigator: Editing Conditional Call Forwarding settings in Navigator now feel smoother and more responsive. Unnecessary background requests have been eliminated, reducing load times and improving the overall user experience.
• Incorrect phone number shown in messages: In some cases, the wrong phone number was shown in messages - especially after warm transfers where the colleague didn’t answer, and the call was taken back. The system would show the colleague’s details instead of the original callers. This has now been fixed, and the correct caller information is shown by default, reducing the risk of sending messages with incorrect contact details.
• Missing indication for Conditional Call Forwarding: The user status component did not show when Conditional Call Forwarding was enabled, leaving users unaware of their current forwarding status. The interface has been updated to clearly indicate when Conditional Call Forwarding is active.
• Music on Hold upload failure for large files: Uploading audio files larger than 20 MB for Music on Hold caused a white screen with no feedback in Config Manager. The UI now properly informs users about the 20 MB file size limit, but the blank screen issue remains unresolved until further notice.

Admin Notes

Bug Fixes

• Missing notifications for CSV import errors: Previously, if a CSV file used for importing users contained syntax errors or incorrect delimiters, the issue was only logged internally and not shown to the administrator, making it difficult for customers to detect problems. The Config Manager now displays clear notifications when such errors occur, like: “Error in one or more rows of CSV file upload. First error found in user row: 1, …” or “Error while reading CSV-file. Check field and keyword delimiter are correct in configuration and CSV-file.”
• Users not fully removed after sync deletion: Previously, some users stayed in the system even after being removed from syncs like Entra ID or BroadWorks, due to leftover update records. The clean-up process has been improved to fully remove these users when they no longer have any active data sources.
• Transient network errors incorrectly disable configurations: Fixed an issue where brief network glitches - specifically “Cannot assign requested address” errors - were causing Entra ID configurations to be immediately disabled, even though the underlying issue was temporary and unrelated to misconfiguration. This behavior was triggered by high container load or port exhaustion, especially during full swarm restarts. To prevent unnecessary disruptions, a retry mechanism has been implemented that attempts to recover from such errors up to three times (with delays of 10, 20 and 30 seconds) before disabling the affected configuration. This ensures more stable integration handling in production environments.
• CSV uploads unintentionally overwrote user contact details: Fixed an issue where importing a CSV file to update user information - such as adding keywords - unintentionally removed all existing contact details (like phone numbers and email addresses) for the affected users. This happened because the system incorrectly treated empty fields in the upload as a signal to overwrite existing data. The same issue also applied when editing users manually. The system now only updates the fields specified in the upload or edit and leaves all other existing details unchanged.
• Calendar view missing Sunday events in week view: Fixed a bug where calendar events on Sundays were not shown in the week view of both the Web Agent and Config Manager. This issue was caused by a mismatch between backend time handling (which starts the week on Sunday using UTC) and the frontend (which expects weeks to start on Monday). The fix ensures correct alignment by translating backend times to follow the ISO week standard, so all events - including those on Sundays - now display correctly.
• False error about missing GroupMember.Read.All permission: Fixed an issue where a misleading error was shown during Entra ID group import, incorrectly stating that the GroupMember.Read.All permission was missing. In reality, the tenant was using Group.Read.All, which also supports group syncing and includes the necessary access. The backend has been updated to recognize and validate both permissions, so group imports no longer fail or display incorrect warnings when Group.Read.All is used.