What you can find here
This page will always reflect the latest Release Notes, Improvements and Changes made to Nimbus.
Other areas of interest:
- Refer to the Release Note History for previous releases earlier this year.
- Updates on our Nimbus Power BI Template are distributed on request. Please refer to the Nimbus BI Template Release Notes to check for updates.
- Also visit the following sources to stay up-to-date on Nimbus in both features and (upcoming) maintenance.
INC External News Resources
Ahead Notice: Restrictive third-party cookie policies
Note: the following scenario regarding browser cookie restrictions may affect both Nimbus Teams Tab, Nimbus Personal App and has been added to the Installation Prerequisites. It is not relevant to this Nimbus release, but was added to the release notes for awareness.
✅ Administrative action MAY be required when (more restrictive future) browser cookie policies affect your Nimbus user login experience. In such cases, please read the following contents carefully.
INC Third-Party Cookie Restriction Workaround
☝ Note of third-party cookie restriction: In 2024 Google Chrome started restricting third-party cookies “by default for 1% of Chrome users to facilitate testing, and then plans to ramp up to 100% of users in H2 2024.” Other browser vendors are likely to follow suit with similar policies.
✅For Tenant Administrators: Most Enterprise users should be excluded from the 1% experiment group. However, Luware recommends that admins proactively use the BlockThirdPartyCookies and CookiesAllowedForUrls policies in Chrome to avoid sign-in issues, as described in this MS “Teams doesn't load” help article reference.
Add the following sites to the third party cookie exception list:
[*.]microsoft.com
[*.]microsoftonline.com
[*.]teams.skype.com
[*.]teams.microsoft.com
[*.]sfbassets.com
[*.]skypeforbusiness.com
[*.]luware.cloud🤔 What are the risk scenarios?
Not following the recommendations by Google involves a risk that Nimbus stops working in Chrome (or other default browsers) when the Nimbus App is launched embedded via MS Teams.
- MS Teams client in your browser: A likely cookie-related risk scenario occurs as you launch launch the Nimbus App or Nimbus Teams Tabs. This triggers a user authentication using 3rd party cookies.
- MS Teams standalone client: Microsoft claims that Nimbus should continue working in the client. Furthermore, Nimbus standalone tab will open and work when "Open app in browser tab" link is used.
To avoid either scenario, we recommend whitelisting cookie-exceptions in your browsers so that Teams can continue continue working with Nimbus. To allow (whitelist) specific URLs in your browser, refer to the steps described in this MS “Teams doesn't load” help article reference.
🤔 What are the effects/problems?
We identified the following issues in regards to cookie-related authentication:
- Warning at startup - A warning message is shown every time when the user start Nimbus in Teams. It seems it's a general error in case of the third party cookies are blocked.
- Authentication popup issue - Returns a Cancelled By User error even if the authentication was not cancelled by user.
23 Oct 2024 - 1.101-2 Release Notes
🔥 This is a hotfix update, bringing some improvements and adjustments to recently released features. This update is rolled out sequentially on our clusters:
| Cluster | Update on |
|---|---|
| United Kingdom 01 | 22/10/2024 |
| Switzerland 02 / Germany 02 | 23/10/2024 |
| United States 01 | 23/10/2024 |
| Switzerland 01 | 22/10/2024 (included with 1.101 below) |
| Australia 01 | 23/10/2024 (included with 1.101 below) |
| Europe 01 | 23/10/2024 (included with 1.101 below) |
| Germany 01 | 27/10/2024 (included with 1.101 below) |
Changes and Improvements
- Outbound Call - Fixed an issue that resulted in blocked Outbound Calls.
- Assistant (O365 ID, Licensing) - Fixed an issue that caused a user to appear as unlicensed / not found after adding Direct Call Templates.
20 Oct 2024 - 1.101 Release Notes
🔖 This is a minor update, bringing some improvements and adjustments into Nimbus. This update is rolled out sequentially on our clusters:
| Cluster | Update on |
|---|---|
| United Kingdom 01 | 20/10/2024 |
| Switzerland 02 / Germany 02 | 21/10/2024 |
| United States 01 | 22/10/2024 |
| Switzerland 01 | 22/10/2024 |
| Australia 01 | 23/10/2024 |
| Europe 01 | 23/10/2024 |
| Germany 01 | 27/10/2024 |
Workflow Activities - Adjusted RONA Timeout / Max Ring Time
Over the years we had frequent discussions about RONA timeout (max. Ring Timeout) being limited to just 30s maximum. This was due to MS Teams hard-bound limitations.
It can take several seconds before a call toast shows up on screen. We've seen customer environments where 5-12 seconds for a call toast to appear are the norm. While all of this is taking place on the Teams side - outside of Nimbus control - internal RONA timers keep ticking away until MS Teams eventually confirmed that the invited user has successfully joined the meeting session and was able to listen to the media streams.
This lead to situations where users accepted a call at around the 25s mark, but then got (wrongfully) flagged with RONA status. While Microsoft has improved the performance starting with Teams client version 2.0, certain performance impairments still remain such as:
- Various installed MS Teams client versions
- Infrastructure delays on Azure side
- End user hardware (Client) - which can negatively impact performance of the Teams client
Our recent testing has shown that Teams will terminate invitations after around 55 seconds. We have therefore increased the maximum RONA timeout wherever possible.
Changes to RONA Timeout (Max. Ring Time)
With this update, the allowed RONA Timeout will be increased from 30 to 55 seconds. The following Workflow Activities were adjusted accordingly:
-
Activities: Queue / Queue Task:
- RONA and Broadcast timeouts while inbound calls are in Queue.
☝Note: Outbound scheduled Calls will remain at a max 30s. -
Queue activity - when Distribution Type is set to either Direct or Pickup with adjustable RONA.
☝Note: Microsoft can still terminate a dialout in ~35 seconds for some Tenants. A warning limitation has been added to the KB.
✅ Service Owners / Admins: → We advise to switch your Queue Activities to Direct Conference and Pickup Conference respectively to mitigate the issue.
- RONA and Broadcast timeouts while inbound calls are in Queue.
- Activity: Transfer: Ring timeout during Workflow Transfers were adjusted.
Other Changes and Improvements
- Call Handling - Fixed an issue where customer-to-user conversation could get included into a customer's voicemail.
- Skills and Responsibilities definition - Skills with no levels are now shown as single lines to reduce space used in UI.
- Attendant Console 2.0 (AC2) - Fixed an issue preventing "Hang-up and Retrieve" buttons to work properly.
- Workflow Activities > Input Customer / Input Customer Advanced" - removed limitation where "Max Input Timeout" already started as the “Main Prompt” is playing.
- Service Call Templates - Added Trigger event “On Terminated” - Performs the template action after a Nimbus service task is finished.
-
Attendant Console 2.0 (AC2) - We have added a new series of video tutorials on YouTube. You can also watch the videos right below.
Attendant Console 2.0: Overview Videos