Download a compliance record PDF safely
Use the supported record-PDF endpoint instead of copying an internal filesystem path.
Before you start
Compliance View opens the workspace; Create is used for new intake, Edit for review/approval and Delete for deletion. Each action also validates its record.
Follow these steps
- Go to the record through the register.
- Use the visible Download or PDF action.
- Verify the browser receives a PDF rather than an error page.
- Save the file using the business-approved naming convention.
- Do not expose encoded paths, upload directories or internal server locations.
Fields, rules and limits
- Open Source Evidence for the supplied document and the record PDF for the generated compliance output. The PDF route checks the current workspace and record; never replace it with a direct upload-directory link.
Check it worked
The linked entity, saved state, dates and evidence match the intended task.
If something does not look right
If the expected result is missing, check the saved record, the current workspace and the action’s permissions. Record the exact validation message; do not repeat a state-changing action until you know whether the first attempt saved.
Questions and answers
Does a parsed document count as approved?
No. Parsing supplies suggested values. A reviewer must verify the linked entity, evidence and required fields, then use the separate approval action.
Is the generated PDF the original certificate?
No. The system PDF reflects the saved compliance record or notification. Open the original source evidence separately when checking the document supplied.