Specification View
The Specification view presents your Blueprint as a structured, readable document. It’s designed for reviewing and understanding your logic — especially useful for larger Blueprints where the visual diagram can get complex. Switch to it by clicking the Specification button in the top-right corner of the editor.
Layout
The Specification view has three main areas:Navigation sidebar (left)

- A section number (e.g., 1, 1.1, 2, 3.2.1) reflecting the nesting depth of your logic
- The section title describing what that part of the logic does
Document area (center)
The main content area, organized into several parts: Title and description — the Blueprint’s name and a natural language summary of what it does.Data Contract

Structure

Numbered sections

- A section number and title (e.g., “1. Validate Cart Value”)
- A description explaining the business rule in plain language
- Run / Clear buttons to execute that section in isolation
- A mini-diagram showing just the elements in that section

Inputs panel

Right sidebar
The same right sidebar as in the Visual view — Tests, Prod Runs, and Comments — is available here too.Working with the Specification view
Navigating large Blueprints
For Blueprints with many sections, use the sidebar table of contents to jump between sections. The numbered structure (1, 1.1, 2, 3, 3.1, etc.) makes it easy to find specific parts of the logic.Running individual sections
Each section has its own Run and Clear buttons. This lets you test a specific part of your logic in isolation without running the entire Blueprint.Following sub-blueprints
When a section contains a Call node, the sub-section shows a link to the called Blueprint. Click it to preview that Blueprint, or Shift+click to navigate directly to it.Reviewing the Data Contract
The Data Contract section at the top gives you a clear overview of what your Blueprint expects and returns. Each parameter lists:- Name and type (number, string, boolean, etc.)
- A description explaining what the parameter represents
- Whether it’s required or optional
When to use the Specification view
| Use case | Why the Specification view helps |
|---|---|
| Reviewing logic before deployment | Read through the numbered sections like a document to verify each rule |
| Understanding a Blueprint you didn’t create | The descriptions and structure make it easier to follow unfamiliar logic |
| Navigating complex Blueprints | The table of contents and numbered sections are faster than scrolling through a large diagram |
| Running sections in isolation | Test individual parts of the logic without running the whole Blueprint |
| Sharing with stakeholders | The document format is more accessible to non-technical reviewers |
What to do next
- Visual view — switch to the interactive diagram for building and editing
- Test your Blueprint — run the full Blueprint with test inputs
- Inputs and Outputs — configure the Data Contract