Creating a workflow

At the core of Oomnitza is the workflow engine. Fueled by the data that is ingested by Oomnitza, workflows can be created that automate the onboarding and offboarding of employees, enforce security best practices, process tickets, interact with vendor APIs, and much more. 

Contents

1. Creating a workflow
2. Anatomy of a workflow
3. Begin block
4. Automation blocks
5. End block

Creating a workflow

You can create workflows for the following objects:

• Accessories
• Assets
• Contracts
• Desktop
• Locations
• People
• SaaS
• SaaS users

To create a workflow, click Configuration > Workflows, and then select the object such as Assets. 

Anatomy of a workflow

A workflow has a Begin block, one or more automation blocks such as an API block and a Notification block, and an End block. 

When you add a workflow, the Begin and End blocks are automatically added to the workflow canvas.

Mock-up of a workflow

What you need to do when you create a workflow is:

1. Set the trigger in the Begin block.
2. Add the automation block or blocks.
3. Join the blocks.
4. Validate, test, save, and run the workflow.  

Begin block

The begin block is the workflow trigger.

In the begin block, you can schedule a workflow and add rules for running the workflow. For example, you can trigger a workflow when a change occurs to a field in Oomnitza. Or, you can trigger a workflow to run on a schedule, for example to deactivate SaaS users who haven't logged into to the application for a specified period.

Information
To check the fields that will be targeted by the workflow, always click SHOW IN LIST VIEW in the Begin block. The number of records that are processed and the time that the records are processed can affect performance. Schedule workflows to run at off-peak periods. 

Automation blocks

Depending on the complexity of the workflow, the workflow can comprise one or more automation blocks. For example, you can add a SaaS User Role Retrieval block to deactivate users and a Notification block to notify the users that they are being deactivated.

For further information, refer to Types of automation blocks

End block

The End block terminates the workflow.

For further information, refer to Introducing workflows