Workflows & Automation
Last updated
Last updated
At its core, workflows in OneLens are designed to automate tasks triggered by specific conditions. These workflows help you improve governance and operational efficiency by organizing tasks in a structured sequence.
For example, workflows can automatically handle cost anomalies, policy violations, and notifications, ensuring that actions are taken at the right time.
A workflow in OneLens has two main parts: Trigger and Actions.
Triggers are the events that start a workflow. They define the specific conditions under which a workflow will be activated.
Once a workflow is triggered, actions are carried out. These actions are the responses set up to address the issue.
In a series workflow, actions are performed one after the other. The next action only begins once the previous one is complete. For instance:
Step 1: Log the anomaly in the tracking system.
Step 2: Notify the finance team via Slack.
Step 3: Create a Jira ticket for investigation.
This setup ensures that each action is completed in order before the next begins.
A parallel workflow allows multiple actions to run at the same time after the trigger is activated. For example:
Step 1: Send a Slack notification to the finance team.
Step 2: Email the engineering team.
Step 3: Log the issue in the internal system.
All these actions happen simultaneously, ensuring you can notify multiple teams concurrently without waiting for each action to complete.
The hybrid workflow combines both series and parallel execution. For example:
Step 1: Check if an unresolved Jira ticket exists (sequential).
Step 2: If no ticket exists, create a new Jira ticket (sequential).
Step 3: Simultaneously, notify the engineering team on Slack and the finance team by email (parallel).
This approach allows you to leverage both sequential and parallel actions to work together, making it suitable for more complex workflows.