Execute → HTML

Endpoints

The HTML output mode is triggered by appending .html to the template code segment of the URL. An optional query parameter selects between a lightweight embeddable fragment and a fully self-contained standalone document.

Fragment vs Standalone

Choosing the right output mode depends on where and how the result will be consumed. The two modes differ in what markup is included in the response body:

Request

Headers

Path Parameters

Query Parameters

Expand / Collapse Behaviour

The rendered HTML table is interactive. Each row that has child records includes a toggle control in its leftmost cell. Clicking the toggle shows or hides the child rows for that record. The behaviour is consistent across all nesting depths:

• Root rows are always visible and cannot be collapsed.
• First-level child rows are shown expanded by default.
• Deeper child rows (grandchildren and below) are collapsed by default to keep the initial view manageable.
• Each parent cell shows a child count badge (e.g. 3 payslips) when the child rows are collapsed.
• Visual indentation increases with each depth level to make the hierarchy immediately clear.
• Expand/collapse state is maintained per-row and persists within the same page session.

Embedding in Atlas Forms

The most common use of the HTML output mode is binding a Display control in an Atlas form to a Multi-Query expression. The expression engine evaluates the directive and injects the rendered cascaded table directly into the form layout at runtime.

Set the Display control's value binding to:

{{multi-query:sqlserver.ORG_CHART|outputFormat=html}}

To use standalone output inside an iframe or embedded modal within Atlas, append the outputFormatTemplate option:

{{multi-query:sqlserver.ORG_CHART|outputFormat=html|outputFormatTemplate=standalone}}

Refer to the Expression Directive page for the full directive syntax, all supported options, and guidance on combining parameters.

Embedding in Emails

To include a Multi-Query result table in an automated email notification, place the expression directive in the email node's body field inside your flow definition. The FlowEngine resolves the expression at send time and injects the fully rendered HTML table into the email body.

Example email body field value (in the Flow Studio node editor):

<p>Please find your payroll summary below:</p>

{{multi-query:sqlserver.PAYROLL_SUMMARY|outputFormat=html|outputFormatTemplate=standalone}}

<p>Contact HR if you have any questions.</p>

Use outputFormatTemplate=standalone for email contexts so that the table's styles are inlined and do not depend on the email client loading external stylesheets (which most clients block).

Error Responses