Rhythm 2.0 Specifications

Appearance

WF-PFM-QRY-007Render a report to PDF or Excel

Markdown

WF-PFM-QRY-007

Render a report to PDF or Excel

Markdown
  • DocumentDraft
  • ImplementationObserved

Planning

Implements
CAP-PFM-QRY-013

KindWorkflowProduct areaPlatformModuleQuestions, record exploration and data deliveryRevision1

Read atservices-platform ad3f6a65react-console baf6dae3

Render a report to PDF or Excel ​

What It Does ​

A person with report-use access requests a PDF or supported Excel rendering. Status and downloads use the existing export-file operations.

The Flow ​

Open the report, check the requested format for its kind and commit the queued export with queued work. Dispatch the report export to the rendering queue and remove accepted queued-work entries. Start unfinished rendering and check that the requester still has report-use access and can open the report. Open the print page without a browser session and intercept allowed Platform reads as the requester, rejecting other requests. The print component loads source data and signals readiness or error on its document. Produce a bounded PDF or validate the page’s Excel output, store under the request key and settle success.

When Something Fails ​

Refuse source or format problems before admission. No file request is created by those checks. Leave unsuccessful publication for another dispatch pass. A render can remain queued or be redelivered after a publish/delete interruption. Settle source removal or lost access as access_lost. No browser starts for a refused source. A refused in-page request fails rendering. The browser result is not accepted as a valid report after a refused request. Page errors or readiness timeout fail the render. There is no accepted printable file until readiness succeeds. File-limit refusals settle without acceptance; infrastructure failures retry and become internal failure on the final receive. An upload followed by failed settlement can leave the object ahead of its running row.

Idempotency and Concurrency ​

The render request retains its export identity and storage key; terminal status prevents restarting settled work on redelivery. Rendering uses its own queue and headless-browser worker limits. It does not share the interactive query-file generator.

Controls

36 controls apply, from the corpus control catalogue.

TC-AVL-004 TC-AVL-005 TC-AZ-001 TC-AZ-002 TC-AZ-003 TC-AZ-004 TC-DAT-001 TC-DAT-002 TC-DAT-003 TC-DAT-004 TC-DAT-005 TC-IAM-001 TC-IAM-002 TC-IAM-004 TC-IAM-005 TC-IAM-006 TC-LOG-001 TC-LOG-004 TC-LOG-005 TC-MON-001 TC-MON-002 TC-PI-001 TC-PI-002 TC-PI-003 TC-PI-004 TC-PI-005 TC-SEC-001 TC-SEC-002 TC-SEC-003 TC-SEC-004 TC-TEN-001 TC-TEN-002 TC-TEN-003 TC-VEN-001 TC-VEN-002 TC-VEN-003

The Markdown files under specs/ in rhythmsoftware/rhythm-v2-docs are the canonical source of truth. This reader is a generated, read-only projection of them.

Rhythm Software