Skip to main content

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. The Specification view showing the Delivery Fee Calculation blueprint as a structured document

Layout

The Specification view has three main areas: The navigation sidebar showing a numbered table of contents A numbered table of contents that mirrors the structure of your Blueprint. Each entry shows:
  • 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
Click any entry to scroll directly to that section in the document. The currently visible section is highlighted.

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

The Data Contract section listing inputs and outputs with their types and descriptions A collapsible section listing all inputs, outputs, and local variables with their types and descriptions. This is the same information as the Data panel in the Visual view, but presented in a document-friendly format.

Structure

The Structure mini-map showing the high-level flow of the Blueprint A compact mini-map showing the high-level flow of your Blueprint. This gives you a birds-eye view of all the sections and how they connect. You can click Expand to see it in a larger view.

Numbered sections

Section 1 expanded showing the description, Run/Clear buttons, and mini-diagram Each logical section of your Blueprint appears as a collapsible block with:
  • 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
A sub-section showing a link to a called Blueprint Sub-sections (e.g., “1.1. Cart validation check”) contain details about individual elements, including links to called sub-blueprints.

Inputs panel

The Run Logic panel showing input fields for testing directly from the Specification view Click the Inputs button at the top of the document area to open the Run Logic panel. This floating panel lets you enter test values and run the Blueprint without switching to the Visual view. Each input field matches the parameters defined in the Data Contract. The same right sidebar as in the Visual view — Tests, Prod Runs, and Comments — is available here too.

Working with the Specification view

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 caseWhy the Specification view helps
Reviewing logic before deploymentRead through the numbered sections like a document to verify each rule
Understanding a Blueprint you didn’t createThe descriptions and structure make it easier to follow unfamiliar logic
Navigating complex BlueprintsThe table of contents and numbered sections are faster than scrolling through a large diagram
Running sections in isolationTest individual parts of the logic without running the whole Blueprint
Sharing with stakeholdersThe document format is more accessible to non-technical reviewers

What to do next