CoreView's Workflow provides process automation for organizations, promoting increased efficiency and empowering IT administrators to convert repetitive management tasks into automated processes.
A common example of workflow implementation is the provisioning/deprovisioning process. The diagram above illustrates a workflow designed for user onboarding. This multi-step process involves a series of tasks, which are:
- Owner/Operator approval: ensures the subsequent steps are executed only if the operator receiving this notification approves it. If so configured, the workflow owner can also approve the action.
- Create OnCloud User: creates a new user in the Cloud based on the variables entered in the input tab.
- Manage Password: sets a password for the User Principal Name and then requires the new user to change it at their first login.
- Assign License: enables you to choose the deployment that aligns with the user's role. For example, you may decide that the new user should receive the full E3 license capabilities, excluding Yammer.
- Manage MFA: allows you to enable or disable multi-factor authentication.
- Grant Mailbox Full Access to Manager: Grants the new user's manager access to the new user's mailbox.
- Send email: sends an email indicating that the workflow process is complete.
Workflow elements
The main elements of a workflow are:
- Execution inputs: the starting information the workflow needs in order to be executed.
- Actions: all the tasks the workflow is configured to execute.
Understanding workflow execution
A workflow’s execution is atomic.
In other words, a workflow can only manipulate one object at a time. You can input N variables (which is often the case when a workflow is associated with a playbook), but this will lead to N executions, that is, one for each targeted item.
Types of workflow execution
Workflows can be triggered and scheduled either manually or automatically, depending on your needs. It is also possible to configure workflows as remediation of a playbook policy.