Move from a report record to an integrity-signed deliverable, covering report types, the async queue, multi-format output, and immutable versioning.
This guide shows how to produce a project technical report in PMAP. You create a report record scoped to one project, pick its output format, and kick off async generation while the status moves through the queue from queued to completed. You also learn what the worker builds from the shared ViewModel pipeline.
It is written for consultants and reporting owners who deliver to clients. By the end you can render the same data as PDF, DOCX, or HTML, confirm that every successful run is versioned as an immutable and separately downloadable file, SHA-256 sign the deliverable for integrity, and read the activity log to reconstruct who generated, downloaded, and signed it.
Inside this guide
- Understand the six report types and the status lifecycle.
- Create a project technical report record and choose its output format.
- Trigger async generation and watch the queue move to completed.
- Download the finished file and learn what the worker assembled.
- Regenerate in another format without losing the first version.
- Inspect version history and SHA-256 sign the file for integrity.
- Reconstruct the full run from the activity log.
Before you start
- A PMAP account with report read and create permissions in your working company scope.
- A project with imported, triaged findings so the report has real content to render.
- A report template chosen for the project_technical type, or the bare report type if you start without one.
- Awareness of which format your client expects, because PDF, DOCX, and HTML render the same data differently.
- The report:sign capability if your deliverable must be integrity-verifiable with a SHA-256 signature.
