Skip to main content
Wiv workflows and automations are built using Steps. Steps comprise two fundamental components:
  1. Flow Controls
  2. Actions

​
Flow Control Steps

Flow Control elements manage workflow progression. Every workflow starts with the “Entry” step, and controlled by the following components
image
  • Exit: Concludes the entire workflow execution, and can return execution values
  • If: Enables conditional branching based on specified criteria
  • Wait: Introduces a timed pause in execution
  • Loop: Executes a sequence of steps repeatedly
    • Collect - A Flow Control step that captures and aggregates information during each loop iteration, making the collected data available for use after the loop completes
    • Break - A Flow Control step that immediately terminates the loop’s execution when triggered
  • Flow: Incorporates a separate workflow as a component
  • Approve: Implement a powerful feedback loop
  • **Comment: **Apply comments to explain workflows assumptions and functionality 
**Did you know?**  
Collect and Break steps are only available and visible in the scope of a Loop

​
Action Steps

Action steps execute specific actions within the workflow. We support multiple action steps in multiple areas, like cloud commands, notifications, ticketing, and utilities.
image

​
Action Step Configuration

Action steps operate on workflow data, with the ability to receive data from previous steps, generate new data, and process existing information. While many action steps perform straightforward operations, we’ve developed enhanced functionality through “Combo steps.”

​
Combo Steps

Combo steps are designed to simplify complex operations by:
  • Consolidating data collection from multiple sources
  • Pre-processing data to streamline user interactions
  • Providing integrated functionality that reduces the need for multiple individual steps
These specialized steps make the platform more accessible and efficient for end users. 
**Costs**  
[](https://docs.aws.amazon.com/cost-management/latest/userguide/ce-configuring-data.html)To access detailed cost information directly from a combo step and include monthly and annual cost breakdowns in CLI responses, [enable Resource Level granularity](https://docs.aws.amazon.com/cost-management/latest/userguide/ce-configuring-data.html) in AWS Billing. This service provides cost data for up to 14 days at no additional charge.
image

​
How to Add a new Step to the Workflow

You can add a step by clicking on the plus icon. When you click on the plus icon, you can add flow control steps, the most common steps, or brows all the steps
  • Click on the plus icon within the workflow area.
  • Choose either flow control or action steps
  • Select the desired step, and it will be added to the workflow
image

​
Step Parameters

  • Name: Each step has a unique name that is also used for the step ID; you can edit it. Avoid using special characters when naming your steps
  • Parameters: Fill in specific parameters (e.g. the relevant integration, filters, messages, code, etc.).
  • Workflow Data: Whenever is needed, you can use the parameters icon (or use the “Command+Click” on MacOs, or “Control+Click” on Windows) to insert data from a previously executed step
image

​
Testing a Step

  • Click on the Setup Testing tab
  • Fill in all the required parameters.
  • Press on Setup Testing to initiate testing.
  • Review the output to validate functionality and gather reference data for subsequent steps
image
Note: Testing is highly recommended to ensure accurate functionality.

​
Step Statuses

This section outlines Wiv’s step status system and its associated best practices. Mastering these concepts enables you to build reliable, efficient workflows that align with operational requirements.
  1. Initial State - The step appears without any status indicators upon initial addition to the workflow
image
  1. Configuration Required - Indicates mandatory parameters or integration settings need to be defined before the step can be executed.
image
  1. Test Running - Status that indicates that the step is currently running
image
  1. Test Success - Confirms successful configuration and testing completion with validated results
image
  1. Test Failure - Indicates unsuccessful test execution, requiring configuration review and adjustment
image
  1. Outdated Configuration - Signals that previous test results may no longer be valid due to configuration changes, suggesting retesting is necessary
image

​
Best Practices

  1. Testing individual steps serves two critical functions: it validates expected outcomes and simplifies parameter configuration through the tree helper for subsequent steps. This validation approach ensures workflow reliability and streamlines development.
  2. Keep track of each step’s current status to ensure accurate testing and data processing. Working with outdated steps may lead to inconsistencies in results and configurations, potentially affecting your workflow’s reliability.
A thorough understanding of step statuses and adherence to best practices will ensure successful workflow implementation in Wiv. Remember to maintain diligent testing and validation procedures throughout your development process

​
Conclusion

Wiv’s component architecture of Flow Control and Action steps provides a comprehensive framework for creating sophisticated FinOps automation workflows. This structure enables users to build efficient, responsive, and reliable automated processes. For additional assistance, please contact our support team.