05 Render Facility Report HTML

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 5: Render an HTML report (helper visualisation)

A convenience step that turns the JSON report from step 04 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/{{fp_fac_record_id}}/report and, in its after-response script, calls the shared renderer Workflows/scripts/eudr_report_html.js โ€” the same module every EUDR workflow uses, so the output is consistent everywhere. The page is laid out in the same section order as the EUDR PDF (eudr_util/eudr/base.html):

  1. Document Information โ€” operator / producer / commodity / dates / submission status
  2. Article 9(1)(a)โ€“(f) โ€” Producer Information
  3. Article 9(1)(g) โ€” Deforestation (summary cards + plot register, colour-coded alert/verdict badges)
  4. Article 9(1)(h) โ€” Legality (adverse-media)
  5. Article 10 โ€” Risk Assessment
  6. Article 11 โ€” Risk Mitigation
  7. Signature
  8. Appendix โ€” High Deforestation Confidence Plots (thumbnails)

Output

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

Expect blank operator / commodity. Fast-path records are created with the org's default operator and an empty commodity block, so those fields render blank (or "Pending operator submission") until you PATCH /regulations/eudr/audit-trail/:recordId to fill them in before submit. That's expected โ€” not missing data.

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