Fall 2024: Features summary preview

This is a preliminary list of the main features and feature enhancements that are currently targeted for inclusion in the Fall 2024 release.

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. 

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.

Editing made easier

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 dashboards

Controlling access to autorefresh

You want to control who can switch on autorefresh for dashboards. You want to reserve this feature for business critical dashboards and you want to control who can switch on autorefresh 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. And, if users want to freshen up dashboards all they have to do is click Refresh.

By default, autorefresh will be disabled when new roles are added. For existing roles, autorefresh is enabled. An ideal opportunity for system administrators to take advantage of the new feature by enabling autorefresh 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 the read-only toggle is turned off. 

In this case, the user decides to update read-only fields. So, she turns the 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. 

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 cancelled 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. 

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.

Integrations

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. 

Custom extended integrations enhancement

To make custom extended integrations more flexible, users can now create their own OAUTH 2.0 credentials to authenticate with third-party applications. As OAuth becomes the standard for API authentication, this feature will provide a more secure authentication method for connecting to the APIs of third party applications.