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.
External News Resources
| Luware Cloud Status Page | Nimbus Newsletter | Events / Webinars on Luware.com |
08 Sep 2024 - 1.99 Release Notes
🔖 This is a major feature update, bringing many new changes and options into Nimbus. This update was rolled out sequentially on our clusters:
| Cluster | Update on |
|---|---|
| United Kingdom 01 | 08/09/2024 |
| Switzerland 02 / Germany 02 | 09/09/2024 |
| Switzerland 01 | 10/09/2024 |
| Australia 01 | 11/09/2024 |
| Germany 01 | 14/09/2024 |
New Clusters available
Two new clusters were deployed and are now available for use:
- Australian cluster (AU01)
- US cluster (US01)
- Note: EU cluster is now also added to the KB listings.
Changes for workflow activity "Input Customer (Advanced)"
You can now use custom and system parameters in text-to-speech prompts in the Input Customer (Advanced) Workflow Activity. This way, it is easier to guide your customers properly through IVR. To make use of the functionality:
- Ensure that Add Parameters is enabled in the Input Customer (Advanced) Workflow Activity.
- Once enabled, you can add custom and system parameters to your prompt text:
Storing voice input in custom parameters
It is now also possible to save the customer's input (voice input or DTMF) to a custom (text) parameter for further usage in the Input Customer (Advanced) Workflow Activity. We also added a new “Save on No Recognition” toggle. This will store any customer inputs in a custom Parameter even if the No Recognition (NR) exit is taken.
Behavior:
- If the Save on No Recognition toggle is enabled, the input is stored upon leaving the workflow activity through any of the exits.
- If the Save on No Recognition toggle is disabled, the input is only stored upon leaving the activity through any of the recognized exits (when matching the input with the expectation).
General limitation on voice inputs
If there is a silence on the caller's end, any noise recorded might still be considered as a “wrong” or “missing” input. This is a design limitation that can be caused by the static noise or phone system shortcomings outside of Nimbus control.
☝ For your later parameter validation within workflows, keep in mind that checking this option will override the parameter default value with anything that was picked up. → If you regularly encounter issues with erroneous customer inputs, we recommend using the Nimbus Power Automate Connector to store customer inputs to be later checked by an Agent / Supervisor, e.g. by showing the parameter in My Sessions or storing it in a list for later workflow improvements.
Replacing “Input Customer” with “Input Customer (Advanced)” in your workflows
For this activity, we're testing a new right-click context menu feature in our workflow activities. The goal is to make future transitions between activities of different feature sets easier.
✅ Right click on your regular “Input Customer” workflow activity, you can replace it with "Input Customer (Advanced)".
⮑ When replacing “Input Customer” with “Input Customer (Advanced)”, all connections (entries and exits) and all values from all properties are preserved.
☝ This only works in case the workflow doesn't have a Workflow Templates with a workflow or structure lock enabled.
☝ It is currently not possible to downgrade from Input Customer (Advanced) to Input Customer.
Changed Filter behavior
We redesigned the filtering option from scratch to provide a cleaner experience.
INC Filtering
|
When your current Nimbus view offers filters:
When filters are already active: Unless “All” is shown as filter content, your results are filtered.
|
 |
New “Presence Activity” indicator for Portal UI and flexible Dashboards
| Presence Activity can now be added as an additional column and filter to User State Tabular, User State Chart, and User Supervisor Tabular Dashboard Widgets. | The Presence Activity is now also shown in a tooltip on all avatars in Nimbus Portal. |
 |
 |
Notes
- If the Presence Activity is not available, only the Presence State is shown.
- 🔍 Refer to the Microsoft documentation to learn more about the different Presence States and Activities in MS Teams.
Power BI
From the Nimbus BI Template Release Notes:
- Session Details and User Session Details pages - fixed the filter that caused latest sessions from randomly not being shown. These pages are now restricted to show top 1000 sessions based on latest StartedAt.
- Resolved "System Error, type mismatch" when refreshing report in Power BI Services (online) after switching UserStates parameter from false to true.
Other Changes and Improvements
- Attendant Console - Category “Skill-based” available in Attendant Console - The category “Skill-based” on the My Services widget in My Overview is now also available in Attendant Console > Services widget.
- Workflow Editing / Dashboard Widgets - The height of movable popup dialog boxes like “Add Activity” (Workflows) and “Add Widgets” (Personal Dashboards) is now adjustable. Furthermore, the default max-height should now adapt to the available screen resolution more effectively.
- Role-based Access Concept (RBAC) OU Admin access in Nimbus Portal - The fields available for read/write for OU Administrators in Nimbus Portal were aligned with those available in Nimbus Admin.
- Provisioning Script PSTN error handling - Improved the error handling during PSTN number assignment inside the Provisioning Script.
-
Power Automate:
- Improved handling on Power Automate side when some flows take long time to complete (30+ seconds).
- KB pages: Complete rework of the description pages for Flow Actions and Trigger Events as well as Creating an Example Flow to reflect the newest Nimbus Power Automate Connector design and Microsoft Power automate UI.