Contents
General workflow blocks
- Archive
- Conditional threshold
- Decision
- Notify
- Schedule Report
- Threshold
- Relational update
- Update
- Wait block
Use the general workflow blocks to automate arduous, complex, and repetitive tasks.
Archive
You use the Archive block to automate the removal of objects, such as assets, software, and people records from Oomnitza.
The rules that you add in the Begin block determine which records are archived. As always, click SHOW IN LIST VIEW in the Begin block to make sure that you target the right records.
Conditional threshold
You use the Conditional Threshold block to set a threshold that can trigger two actions such as when the value is over or under the threshold value. For example, if the value of an asset is more than $1000, request the IT manager's approval before the asset is retired. If the value is less than $1000, retire the asset automatically.
Decision
If you want to get an action approved before you complete a workflow action, you add a Decision block. In effect, the workflow is paused until the approver responds. Different actions can be completed depending on whether the approver approves or rejects the action.
Notifiy
You can send a notification in an email, to the Oomnitza work stream, or both. You can also include a link to the the main object of the workflow such as an asset or person.
Schedule Report
You can create a scheduled report that you can send by email to track assets or other objects .
Threshold
You use the Threshold block to receive notifications when a threshold in your system is reached. For example, you can use the threshold block to send a notification when the number of available laptops in a stockroom is less than 10.
Relational update
You use the relational update block to import a value based on other related values.
Update
You use the Update block to automatically update objects when a specified event occurs. For example, you can use the Update block set the end of life date for an asset when the purchase date for the asset is set.
Wait block
The Wait block delays the execution of a workflow for a specified period to allow other workflow actions to complete, such as Update or API actions.
Integration workflow blocks
API block
You use the API block to interact with external vendor systems. For example, based on your organization's policy, you deactivate users in Oomnitza who don't log into a SaaS application for a specified period. To delete the user from the SaaS application, you can create an API workflow.
Tip
Asset and user extended integrations include presets. Presets are out-of-the-box actions that you can use in workflows to interact with vendor APIs.
Read the documentation to take advantage of the presets that Oomnitza offers to automate processes and reduce costs.Partner integrations
Apple Model
You use the Apple Model block to pull in complete, and correctly formatted Apple device model names based on the asset's serial number.
Dell
You use the Dell block to ingest information about Dell assets.
Jira
You use the Jira block to automatically create new tickets in Jira.
Lenovo Warranty and Device Info
You use the Lenovo Warranty and Device Info block to ingest information of the most recent active warranty for a Lenovo device based on its serial number.
Oomnitza block
You use the Oomnitza block in workflows to make calls to our internal API.
ServiceNow
You use the ServiceNow block to automatically create incidents in ServiceNow when changes are made to assets or specific criteria is met in Oomnitza.
SaaS User Role retrieval block
You use the SaaS User Role retrieval block to extract license utilization and role usage information for SaaS users. Once you have this data, you can utilize the API block to deactivate users in Oomnitza who haven't logged into a SaaS application for a specified period. By combining the SaaS User Role retrieval block and the API block in this manner, you can implement a comprehensive solution that optimizes your resource allocation and helps you manage your SaaS user base efficiently.
Zendesk
You use the Zendesk block to generate new tickets and update tickets. For example, you can automatically generate a Zendesk ticket when the status of an asset changes.
Other workflow blocks
Offboard Accessories, Assets, and Licenses
You use the offboard accessories, assets, and licenses blocks to automate the offboarding process for the people who leave your organization.
You use the Offboard Accessories block to offboard accessories and return them to the stockroom. You can also send a notification to the responsible parties in your organization.
You use the Offboard Assets block to change the assignment and the status of users' assets. You can also send a notification to the responsible parties in your organization.
You use the Offboard Licenses block to unassign all the software licenses that are assigned to a user. You can also send a notification to the responsible parties in your organization.
Overassigned Accessories
You use the overassigned Accessories block to monitor the usage of an accessory over a given period.
Underutilized licenses
You use the Underutilized Licenses block to automate the removal of inactive users from SaaS enterprise contracts based on their usage of SaaS apps
Update Child Records
You use the Update Child Records block to apply fields from a parent object to its child objects. For example, you can create workflows that enforce the assignment or location attribute of a parent object to its child objects.
Comments
0 comments
Please sign in to leave a comment.