Itential’s unique automation capabilities enable NetDevOps teams to trigger workflows via different options best suited for their needs; form trigger, scheduled trigger, event-based trigger, or an API trigger.
As part of Itential’s API Trigger demo series, we’ve shown how teams can map key job variables and use data transformations to build API trigger automations from different calling systems. But what about when data validation guardrails are necessary? In part three, see step-by-step how you can easily add a layer of validation to API trigger automation by assigning JSON Schema Transformations to the body of the request, preventing incomplete or erroneous requests from completing.
In this demo, see how to:
- Validate data within an automation workflow.
- Add JSON Schema Transformations to automation workflows.
- Provide accurate documentation of northbound systems request data to DevOps teams.
Demo Notes
(So you can skip ahead, if you want.)
00:00 Introduction & Demo Overview
01:06 View of the Importance of Workflow Validation
02:02 Automation Workflow Overview
02:44 Validating Data in an Automation Workflow
03:57 Adding a JSON Schema to an Automation
06:10 Documenting API Trigger Requests for DevOps Teams
