08 Render HTML Report

Not the product export. This step builds a page client-side, inside Bruno, from the JSON report โ€” it is a convenience preview, not the server-rendered audit-trail HTML. For the real self-contained export (ten tabbed sections, live plot map, with section content identical to the PDF's), see Download Interactive HTML Export and Download Audit Trail HTML.

Step 8: Render an HTML report (helper visualisation)

A convenience step that turns the JSON report from step 07 into a standalone, self-contained HTML page โ€” no server, no assets โ€” rendered in the response Visualize tab, and easy to copy out to save or attach to an email.

It re-fetches the same GET /regulations/eudr/audit-trail/{{fac_record_id}}/report and, in its after-response script, builds the HTML from res.body.attributes:

  • A header band naming the tag the record was selected by ({{fac_tag}}) โ€” the through-line of this workflow.
  • Scope cards โ€” commodity, country, plot count, total area, submission status.
  • Deforestation assessment cards โ€” the summary rollup.
  • Plot register table โ€” one row per plot_register entry, with a colour-coded deforestation-alert badge and one column per report_data_fields projection (if any are configured).

Output

WhereWhat
Visualize tabThe report renders directly as an HTML visualization (bru.visualize) โ€” open the response Visualize tab to view it. No filesystem write.
{{fac_report_html}}The full HTML string is also stashed on this run variable so later steps (or your own tooling) can reuse it.

This is purely presentational โ€” it makes no new API calls beyond the re-fetch and changes no server state.