Downloading the Per-update Report

The per-update report is the durable evidence record for the exact laboratory test and expands as later production actions occur.

Step-by-step procedure

1. Open the tested update row.
2. Select Download Report.
3. Allow the browser to download the token-validated attachment rather than navigating away from the Laboratory page.
4. Store the report with the maintenance/change record.
5. Download it again after production actions if you want the report to include later push/validation/rollback evidence.

Why the download endpoint is separate

QCUL sends reports through a token-validated non-AJAX attachment endpoint so the browser receives a file rather than accidentally replacing/refreshing the Laboratory workspace. This also keeps the report request within Joomla permission/CSRF controls.

When to download again

A report downloaded immediately after laboratory testing may not yet contain later production safety, push, live validation, or rollback evidence. Download the updated report after production work when you need the complete maintenance record.

Read evidence in context

Use Downloading the Per-update Report together with the other evidence for the same tested item. A version check, route check, log message, screenshot, or file/database diff is strongest when it agrees with the surrounding evidence and your own reproduction in the private laboratory; no single signal should be treated as universal compatibility proof.

Community Discussion

Want to compare update-testing workflows, share practical tips, or discuss how you use this QCUL feature? Visit the QC Update Laboratory Community. For private support, bug reports, account-specific issues, or feature requests, use the QuantaCade support system.