The new features and enhancements in this release reflects Oomnitza’s commitment to build an innovative and robust IT asset management solution with efficiency, security, data enrichment, and data integrity at its core.
Top features
- Transforming SaaS User management
- Editing securely and efficiently
- Enhancing dashboard permissions and usability
- Enforcing data hygiene when records are imported
- Troubleshooting workflows
- Accelerating the resolution of privacy and security issues
- Performance enhancements
- New integrations
- Extended integration enhancements
- Custom integration enhancements
Transforming SaaS user management
To enhance the management of SaaS users, the foundations are being laid to add and improve the features that you need to enrich the data that is collected about SaaS users and to manage key business processes across all SaaS applications.
To make the Software SaaS Users component more configurable, flexible, and powerful, it has been transformed into an independent component which will allow us in future releases to offer our customers such features as:
- Creating dashboards to surface business-critical information about SaaS users and creating reports to share information
- Creating workflows to automatically run business processes across all SaaS applications
- Configuring views so users only see what they need to see to complete their tasks
The transformation has begun!
Check out the changes that are available in this release:
SaaS Software Users can be accessed as a separate object in the data model. Click Configuration > Data Model > Objects, and open SaaS Software Users.
Custom fields can be added to Software SaaS users in the data model. Click Configuration > Data Model > Field Configuration and open Software SaaS users. Please note enhancements are being made to Oomnitza API version 4 and it is subject to changes as the API’s functionality is extended and improved. This might require you to modify API calls in future releases.
To access version 4 of the API, click Configuration > REST APIs and select V4 Public.
The SaaS users tab has been updated and now displays the custom fields that you added to the data model. Click Software > SaaS, open a record, and click the Users tab.
Custom fields can be queried and updated in Swagger using the /api/v4/saas_users public API endpoint. In a subsequent release, you will be able to use workflows to query and update custom field values.
To access version 4 of the API, click Configuration > REST APIs and select V4 Public.
Editing securely and efficiently
You want to ensure that your records are accurate and up to date, but you also want to control access so that you decide who can bulk edit records and how many records they can update simultaneously.
No more scrolling to select the records that you want to update. Just select two or more records and click Edit.
You can decide whether you want to update the records that you selected or the maximum number of records that you are permitted to edit.
As ever, security is built in! The system administrator determines who can bulk edit records, how many records they can bulk edit simultaneously, and whether they can update read-only fields. The default number of records that can be bulk edited simultaneously has been upped from 1,000 to 2,000 records.
Enhancing dashboard permissions and usability
Controlling access to auto refresh
You want to control who can switch on auto refresh for dashboards. You want to reserve this feature for business-critical dashboards, and you want to control who can switch on auto refresh based on their role in your organization. Let's face it, not all dashboards, such as private dashboards, need to be refreshed automatically.
Remember, all users who have access to dashboards can check when the charts were last updated. When you open a dashboard, the charts are refreshed, and if you want to freshen up a dashboard all you need do is click Refresh.
By default, auto refresh will be disabled when new roles are added. For existing roles, auto refresh is enabled. An ideal opportunity for system administrators to take advantage of the new feature by enabling auto refresh only for the roles that require the automatic refresh feature.
Using private searches to create dashboard charts
Want to create charts for your eyes only? Now you can use your private searches to create charts on your private dashboards. No need to make your searches public to generate the charts that you need to make your life easy.
Enforcing data hygiene when records are imported
You want to keep your records up to date, but you don't want to compromise the integrity of your data.
Say you want to update records using the import feature, but you want to ensure that read-only fields aren't updated. No problem! System administrators can, for each object managed by Oomnitza, and for each role control who can update read-only fields when they import records.
The system administrator might want to grant permissions to certain roles and for certain objects to update read-only fields. And leave it up to the trusted user to decide when to use this option.
In this case, the user has permissions to update read-only fields, but decides not to. So, the read-only toggle is turned off.
In this case, the user decides to update read-only fields. So, she turns the read-only toggle on.
System administrators can also, on a role-by-role basis, turn off the import feature by granting read-only access to objects such as assets and accessories.
Troubleshooting workflows
Workflows running in the background, hogging system resources and slowing down performance? Of course, you want workflows to run efficiently and get the job done. But you also want to stop them when they stall, affect system performance, and stop other workflows from running. And, you want this done for you, automatically, by Oomnitza.
You also want to know what happened, when it happened, and why it happened. Vital diagnostic Information to get those workflows up and running successfully. And you want the information upfront on the Workflows Status chart so you can drill down and access the information.
Now, Oomnitza monitors workflows and automatically times out workflows that take over three days to complete. On the Workflows Status chart, you can see, at a glance, the workflows that timed out or that were canceled manually.
On the Workflows Status chart, you can click a canceled workflow and see which workflow block caused the issue and view the diagnostic information that was collected which now includes the name of the block that caused the issue so that you can resolve issues more easily.
The default system timeout is set to three days. The minimum value is two days, and the maximum is 30 days.
To change the timeout value, contact Support.
Accelerating the resolution of privacy and security issues
To efficiently resolve security and privacy issues that might arise, customers can provide the email addresses of their contacts for addressing privacy and security concerns.
Add your contacts now and review quarterly.
Performance enhancements
As ever we continue to make performance and scalability improvements to Oomnitza. The focus in this release was improving the handling of increased asset and user workloads by extending cache coverage and minimizing the number of API calls being made to load asset and user workloads. The outcome of this initiative was a significant reduction in response times for GET and POST API requests for workloads consisting of 1.5 million records.
In addition, JavaScript bundling was used to merge multiple JavaScript files together which reduced the number of server requests and resulted in an improvement of load times for pages.
New integrations
Cisco DNA. Basic and extended asset integrations.
Coda Organization. Extended user integration.
Intercom Admins. Extended user integration.
Ironclad. Two extended user integrations: Ironclad App & Ironclad Clickwrap.
Extended integration enhancements
Microsoft Entra ID and Microsoft users extended integrations. Instead of ingesting all the user records, you can add a filter to get the records that you want to manage in Oomnitza. For example, instead of retrieving all the records, you can retrieve records based on the employee type:
| Expression | <field_to filter> |
<operator> |
('value_1’, ‘value_2'...) |
| Example | employeeType | in | (‘Admin’, ‘Staff’) |
Other enhancements
DHL tracking preset. Use the new preset to retrieve shipping and tracking information for packages sent by DHL.
FreshService asset integration. Issue with retrieving serial numbers resolved.
Salesforce plugin. Search by case number added.
Custom integration enhancements
Enhancements were made to custom extended integrations to enable customers to sync with vendor applications that are not available out-of-the-box in Oomnitza.
- OAuth. To make custom extended integrations more flexible, users can now create their own OAuth 2.0 credentials to authenticate with vendor applications. As OAuth becomes the standard for API authentication, this feature will provide a more secure authentication method for connecting to the APIs of vendor applications.
- Extending the capability of custom extended integrations. To make integrations with vendor applications more flexible and to meet the requirements of some vendor application APIs, such as Splunk, customers can now create integrations that send POST requests with raw text data as payloads. POST requests are returned in XML or JSON formats so that the data can be validated to preserve the integrity of the data managed in Oomnitza.
Other enhancements
- Aruba Central. Credentials for OAuth added. To create a custom extended integration, you might require assistance. Contact Support.
- Palo Alto Networks Prisma Cloud. Credentials for session-based authentication added.
- UVExplorer. Credentials for session-based authentication added.
Upcoming deprecations
The following basic integrations will be deprecated in May 2025:
Tip
Switch now and unleash the power of extended integrations! Switch from Cisco Meraki Network Devices to Cisco Meraki assets.
Switch from Tanium to Tanium cloud assets.
Upgrades
In compliance with Oomnitza's continual improvements to our solution, Python has been upgraded to the latest stable version (3.12).
Comments
0 comments
Please sign in to leave a comment.