Bulk Editing allows you to make comprehensive changes on multiple data entities within Nimbus. This feature will allow any User with Nimbus Administrators role to Bulk Edit Services or Users by selecting multiple entries in the respectivee Admin overview simultaneously. And while doing so:
- … compare multiple entries and their settings, highlighting differences.
- … standardize licenses, related features and settings.
- … review the changes in post, using the Bulk Operation Overview.
Before You Start
Licensing Constraints
Same as in single editing, Bulk Editing allows to apply licenses and thus enable (or remove) features per User or Service. Refer to Nimbus Features for a comprehensive overview, and check on your License Management view to ensure you have sufficient licenses to bulk-apply.
☝This feature is quite powerful, but also allows you to make sweeping changes that may undo prior work in User configuration. Please ensure to read the following chapters thoroughly to understand all the concepts.
🔎Also refer to our Best Practices - Bulk Editing for tips and considerations.
KNOWN LIMITATIONS - BULK EDITING
☝Bulk Editing is in active development. We are continuously updating this feature over the coming months.
☝Please read the following topics carefully to understand where the limitations lie. We also continuously update our Latest Release Notes whenever changes and improvements to this feature will be made.
🤔 Which features are available for Bulk Editing?
Bulk Editing - Services and Users only: This feature is currently intended to allow only service and user bulk editing. Further configuration entities will be made available at a later date.
| Entity | What can be changed in Bulk | What can't be changed in Bulk |
|---|---|---|
| Users |
|
|
| Services |
|
|
1 Changing User “Services” and “Roles” tabs are disabled during Bulk Editing. Changing roles would have large-scale implications on the existing Service Provisioning and User Assignment Types in Nimbus.
2 Cannot be changed in Bulk (yet) as these settings rely on many dependencies configured on additional tabs.
3 Addon licenses can be (un)assigned in bulk - same as via License Management. However, each service needs to be individually configured, as the related Settings tabs are not yet supported in Bulk Edit.
4 Must remain unique for the selected entities during bulk edit, e.g. due to a Service being fixed/synched to a "MS Teams-based" channel.
🤔 What design limitations are there?
💡By design: Listed below are active design decisions, please do not report these as issues.
☝ No Undo Option - Bulk editing does NOT provide any way of undoing your changes. We recommend making small changes at first to see the effects.
-
Maximum 25 entities can be edited at the same time.
- If the total number in a list is larger than 25, “Select All” is disabled.
- You can filter your entries below this threshold to apply changes.
- No bulk creation/deletion - While in bulk edit mode, entities cannot be mass created or deleted (as a precaution).
- Dependent change confirm - Certain features rely on dependencies (e.g. an applied change showing additional feature tabs). For this reason you need you to confirm pending tab changes first before applying further bulk changes.
💡Known Limitations: (technical limitations and issues that we already know about.)
-
Users with only Custom Roles assigned don't have the Bulk Edit feature available. → An “Organization Unit Admin Role" needs to be granted to Bulk Edit entities within the corresponding OU.
⮑ The OU entities that the Custom Role has access to cannot bulk edited due to a lack of permissions.
- “Disappearing” Details view - Confirming a bulk change via tab change shows a saving dialog as intended. However, the “Details” inspection feature was only visible on the previous tab bottom and thus cannot be shown on the new tab.
-
Limited Bulk Operation view - The “Details” of bulk operations - next to the “Save & Apply” button - only show a complete set of changes, not the delta changes.
🤔 Other things to consider?
With Bulk Editing it is possible to modify Organization Units of many entities (e.g. users) simultaneously. ☝ This will inevitably create “Non-Path References” (NPR) warnings in your UI.
What does Non-Path Reference mean?
A Non-Path Reference (NPR) is signaled with a small warning icon in the UI, indicating that “Reading along the path / up to the root” rules were violated with a prior Organization Units change on an entity.
🤔What is an entity? Anything configured within Nimbus that has its own OU - users, services, workflows, profiles, etc.
🤔Is there a risk to creating NPRs? Your existing Nimbus references (and related services) will continue to operate even with NPR warnings, but the changed entity (e.g. a OU-moved user) will not be visible for selection anymore once removed. All existing dependent entities (e.g. a service defining an “NPR” flagged user) will still consider this user for tasks distribution as long as the user itself is not actively removed from the configuration.
💡 Note that the Non-path Reference warning (caused when changing Organization Units) is currently not shown in the Roles tab. This is a known limitation and subject for future improvement.
🔎 Related Best Practices: We also recommend reading our Best Practices - Bulk Editing for tips and tricks as well as considerations before engaging with this feature. We will continuously update the page, alongside with any known limitations.
How to Start Bulk Editing
To start Bulk Editing, perform the following steps:
-
Depending on if you want to edit Users or Services, go to User Administration / Service Administration respectively and select at least one entity via the checkbox on the left side of the display name. 💡In the example below we show Users, the same method applies for Services.
⮑ The “Bulk Edit” Popup window is shown near your selection.
⮑ You can now select more entries via their checkbox, or by clicking into the rows. -
Use the search or filters to narrow down your choices.
⮑ Your already selected entries (even those outside of the filter or search view) remain selected.
☝Note that “Select all” is not an option if your choice would exceed 25 entries. Refer to the → Bulk Editing Limitations for more details. - Once satisfied with your selection, click on “Bulk Edit” to start editing all the entries.
⮑ The bulk edit process will always start on the General tab.
Simultaneous Editing
Good to know: When two or more administrators are editing the same Users, a banner will be shown informing that the User is part of an ongoing bulk operation.
⮑ In such cases you will be informed once the bulk operation is complete. Once complete the banner will contain a refresh option to ensure you are working with the latest information.
Inspecting Bulk Operation Details
Whenever you save your changes during Bulk Edit, the bottom footer in the UI will show Details which can be clicked on.
⮑ A click opens the “Bulk Operation” window that reveals:
- … the entities (Users, Services) that were modified.
- … the property (e.g. License, Organization Unit) that was changed
- … the value written on that property. 💡Note that this shows the new full value set, not a delta from the previous values.
- … the result of that operation on the individual data entity. 💡More about this in the "Troubleshooting" section → below.
🔎Related: Change History
All bulk operations are summarized and listed in the Change History
Example JSON Output
💡 Note that the entire (JSON) value set stored by Nimbus is shown here, including not only your changes, but also already enabled properties. An example showing all written values looks as follows - in this example for a User:
{
"operationId": "ddb67970-ca48-411a-af5d-846185432309",
"requesterName": "Ada Lovelace",
"status": "Successful",
"errorCount": 0,
"timestamp": "11/08/2024, 9:30 AM",
"users": [
{
"id": "f319e87a-b982-43b0-a904-78e04e084552",
"displayName": "Scientist Leonardo da Vinci",
"properties": [
{
"propertyName": "Licenses",
"status": "Successful",
"value": "Contact Center, Interact, Attendant Console, Assistant, External Task, Audio/Video"
}
]
}
]
}Troubleshooting
In any regular scenario, bulk-updating users should run and show as successful. If the operation fails for any reason (e.g. an operation timeout or contradicting operations by other admins), the Bulk Operation will show as partially successful when some data entities were updated or failed when no entities were updated at all.
If your Bulk Operation fails repeatedly:
- Retry the bulk operation with the failed users.
- Check if single-editing those users is possible.
If workarounds are not effective even after repeated attempts, please download the JSON, take a screenshot of the operations window - preferably with a visible timestamp of your failed operation - and get in touch with Luware for technical analysis.
| Luware Website | https://luware.com/support/ |
|---|---|
| Luware Helpdesk | https://helpdesk.luware.cloud |
| Cloud Service Status | https://status.luware.com/ |