Creating Report Blueprints
A Report Blueprint is a reusable template that defines the structure and content of your Reports. You author sections and typed Report Elements in the blueprint editor. Changes apply to future Stamp Report / Preview Report runs only—they do not rewrite Reports already in history.
Opening the Blueprint Editor
Section titled “Opening the Blueprint Editor”From Reports:
- Click Create to start a new Report Blueprint, or
- Open an existing blueprint from the list
The editor shows a sectioned canvas (about page width) where you place Report Elements on a 12-column grid.
When Eric is available and you have Main Eric Chat access, In-Report Eric opens on a new or header-only blueprint so you can describe the report you want. Eric can add sections, place elements, and update the live blueprint composition. Click an element on the canvas while In-Report Eric is open to attach it as context for your next message. Use Open in Eric chat to continue the same session in Main Eric Chat.
When Eric saves blueprint changes from In-Report Eric, the canvas reloads with his updates. Any unsaved local layout edits on the canvas are replaced.
Blueprint Basics
Section titled “Blueprint Basics”Title and description
Section titled “Title and description”Set the blueprint title (and optional description) in the editor. The title appears in the blueprint list and on stamped Reports. Changing the title renames the live blueprint; it does not rename historical Reports.
Unsaved changes
Section titled “Unsaved changes”The editor tracks dirty state and warns you before leaving with unsaved work. Save from the header when ready. Stamp Report and Preview Report dirty-save like Save when needed so the print path runs against the latest composition.
Report Sections
Section titled “Report Sections”A blueprint is an ordered list of Report Sections. Each section has its own grid of element placements.
- By default, each section starts on a new PDF page (Section Page Break on).
- Turn Start on new page off when adjacent sections should share a page if they fit.
Authors do not draw page boxes in the editor; pages appear when producing a Report PDF.
On the canvas, table and text elements render inside their placement tile. In the Report PDF, those elements can continue across additional pages when content exceeds the tile. Charts, metrics, and headers stay within their authored size. Use Preview Report to check PDF pagination before stamping.
Report Elements
Section titled “Report Elements”Add elements from the canvas chrome. Element types:
| Type | Role |
|---|---|
| Header | Title / framing copy for a section or band |
| Text | Supporting paragraphs and labels |
| Metric | Single-value KPI visuals |
| Table | Tabular data |
| Chart | Chart visuals |
A new blueprint seeds one header element. Data-backed metric, table, and chart elements use Query Dataset–style definitions edited in the Report Element Workspace (definition YAML, Supporting QD, and a typed visual preview).
Opening a Report Element enters the Report Element Workspace. In-Editor Eric is docked on the left and can revise the open element definition and any dirty Supporting Query Dataset buffers. Eric’s edits apply to unsaved buffers; you choose when to Save. Undo changes reverts Eric’s buffer edits from the current editing streak before you save.
Report Elements are not Dashboard widgets. Deleting a Dashboard widget does not remove or warn about Report Elements.
Layout
Section titled “Layout”- Place and resize elements on the section’s 12-column grid
- Move elements within and across sections when the Move flow is available
- Keep layouts readable for print; dense grids are harder to scan on PDF
Optional Report Style on the blueprint and per-element style nests control box model, typography, and colors for canvas preview, workspace preview, and Report PDF. Prefer the structured style fields over freeform CSS.
Report Generation Parameters
Section titled “Report Generation Parameters”Declare named Report Generation Parameters on the blueprint when queries or text interpolation need values at generation time (for example an employee id). Stamp Report and Preview Report collect those values in a modal when any are declared. Report Download from history does not re-prompt for parameters.
Canvas Preview and Reload Data
Section titled “Canvas Preview and Reload Data”While editing, the canvas loads typed visuals for placed elements (skeleton until each cell resolves). Use Reload Data in the header to re-run canvas previews for every placed element. Reload shares a busy gate with Save, Stamp, and Preview so generation and a full reload do not overlap.
Canvas preview uses empty Report Generation Parameters. Parameterized fidelity belongs to Stamp / Preview.
Preview Report and Stamp Report
Section titled “Preview Report and Stamp Report”From the blueprint editor header (requires Report Write Permission):
- Preview Report — dirty-saves if needed, collects declared parameters, renders a PDF, and downloads it without creating a Report
- Stamp Report — same path, but creates a Report, stores the Report PDF, and downloads it
Both use the product print route. Prefer Stamp when you want a durable history item; use Preview to check layout without adding history rows.
Managing Blueprints From the List
Section titled “Managing Blueprints From the List”From Reports:
- Open a row to edit
- Delete a blueprint with confirm when you have write access — this removes the template only; existing Reports and Report PDFs remain
- Open Report History (
/reports/history) for company-wide stamped Reports
Best Practices
Section titled “Best Practices”Start simple. One section and a few elements beat a dense first draft.
Author detail in the blueprint. Put supporting tables or metrics under charts instead of relying on an interactive viewer.
Name clearly. Blueprint titles show up in lists and help identify stamped Reports.
Declare parameters deliberately. Only add Report Generation Parameters you will supply at Stamp / Preview.
Check PDF early. Use Preview Report before stamping a batch of history items.