Feature 07 / 08
Turn repeat questions into Checks
Author reusable Checks and query Validators, then run them manually against local or cloud projects in the web or terminal UI.
Reusable ChecksIn development
The problem
When the same data expectation comes up again, how do you test it consistently?
Teams repeatedly check the same business expectations by eye: an invoice total should match its lines, required fields should be present, or a customer reference should resolve in the CRM. Ad hoc queries help once, but the expectation and its result are easy to lose.
A clearer workflow
State the expectation
Attach Validators to a saved query for row-level or whole-result rules, or define reusable catalog Validators such as required values, equality, counts, uniqueness, or a nested Check.
Compose a reusable Check
Group related queries and nested Checks into one versioned definition, with named inputs mapped between steps and confirmed Case context.
Run and inspect
Choose the logical environment and review inputs, dependencies, sources, and work limits. Run manually in either UI, then inspect row and set results, affected records, retained query receipts, execution status, outcome, and severity.
Illustrative workflow
Validate invoice totals across related records
Starting question
How can reusable Checks describe expectations across an invoice and its related records?
Steps to follow
- In a project you can access, compose a Check from saved queries and any related nested Checks, mapping named inputs between steps.
- Add query Validators for row-level or whole-result expectations, such as required values, equality, counts, or uniqueness.
- Select an unambiguous logical environment and inputs, run manually, then inspect the actual row and set results, execution status, and severity.
Evidence to assemble
Checks use local or cloud project storage and are versioned so a run can be interpreted against its definition. Runs are manual; scheduling and automatic Case or Incident closure are not part of this workflow.
Open DataTugWhat changes
A recurring validation becomes a named, reviewable workflow with results that explain which expectation needs attention.