Skip to main content
The Write Cases step transforms identified optimization opportunities into actionable Cases within the Wiv.ai platform, creating end-to-end automation stories. From discovery to implementation, each case captures the complete engineering lifecycle of resource optimization, enabling both automated and manual remediation paths through comprehensive workflow integration Each generated case functions as a comprehensive record, complete with status tracking, lifecycle management, and detailed remediation information. The step not only documents opportunities but also enables automated remediation through workflow integration. This seamless connection between discovery and action streamlines the optimization process, allowing teams to efficiently track, manage, and implement improvements through both automated workflows and the Cases interface. This capability bridges the gap between opportunity identification and implementation, ensuring that every optimization potential is properly documented, tracked, and actionable within your cloud resource management strategy
image

​
How to use

​
Understanding Write Cases Fundamentals

Data Structure Requirements The Write Cases step requires input data in a structured list format. Whether processing a single item or multiple elements, all data must be formatted as a list for proper processing. 
[
    "Account Id": 1122334455,
    "Account Name": "Prod",
    "Region": "us-east-1",
    "Owner": "Dvir@wiv.ai", 
    "Resource Id": "vol-xxxcccvvv",
    "Annual Savings": 453.1,
    ......
]
Mandatory Case Identifier Keys Your data structure must include specific keys that map to these required case identifier components. For example, if your list contains “EC2InstanceId”, “AWSRegion”, and “AccountNumber” keys, these would map to the Resource Id, Region, and Account Id elements respectively in the case identifier. The keys that are mandatory to have in your cases are: 
  1. Resource ID Field Name - A distinct identifier for each resource, which can be automatically generated from unique values or derived from an existing unique key.
  2. Region Field Name - The geographical location of the resource. For global resources, specify “Global” as the region value.
  3. Account ID Field Name - The specific account, subscription, or project ID associated with the resource, enabling proper role assumption for remediation actions.
  4. Case Owner Field Name (Optional) - A customizable field for resource ownership, which can incorporate user tags, account allocations, or other organizational ownership structures.
  5. Annual Potential Savings Field Name - The Annual Savings field must be specified in your cases data structure to indicate potential cost reduction. This value can be derived from calculated savings, predetermined business logic values, or set to 0 if no direct cost impact exists. Include this as a numeric value in your cases list structure.
Board Organization Boards function as logical containers for grouping similar cases, enhancing organization and visibility. You can create and manage boards either through the Write Cases step configuration or directly from the Cases page within a Space.

​
Writing Cases

Creating Cases in Your Workflow:
  1. Incorporate the Write Cases step into your workflow configuration
  2. Select your target Board for case creation, or establish a new board directly from the step
  3. Define the Case Type - assign a logical name to categorize your cases for efficient identification in the Cases interface
  4. Designate the appropriate Service Group to enable aggregation functionality for management and reporting
  5. Choose or customize the relevant Service from predefined options or create a custom entry
  6. Document Criteria - provide a concise explanation outlining the optimization case parameters, including tracking methods, filtering approach, and waste identification factors
  7. Establish Case Effort metrics aligned with your organization’s policies and remediation procedures
  8. Configure mandatory Case identifiers by mapping them to your existing data structure fields
  9. Input Cases Data - incorporate output from previous workflow steps (preferred method) or implement a manual case list (alternative approach)
  10. Define** Minimum Annual Saving** - set the savings threshold for case generation to manage case volume effectively. Set to 0 or implement a parameter to capture all savings-generating cases