Admin Reference
Deucalion Composer Route Reference
Understand template editing, version lifecycle, branding, preview, autosave, and render history for document outputs.
Before you start
- Template administration is enabled and you are adjusting how customer-facing outputs render.
Expected outcome
You can manage template lifecycle without confusing source-record data fixes with template fixes.
What this route is for
Deucalion Composer is the template administration desk for PDF-backed outputs such as reports, certificates, and quotes.
Visibility and capability notes
| Item | Details |
|---|---|
| Route id | pdf-templates |
| Visible nav label | Deucalion Composer |
| Visibility | Customer-facing only when template administration capability is enabled. |
| Capability notes | This is a specialist workspace and is intentionally separate from the operational desks that produce the underlying data. |
| Direct inbound | Reports, Quotes, Inspections, and direct shell navigation when enabled. |
Main regions, tabs, dialogs, and studio surfaces
| Surface | What it does |
|---|---|
| Workspace tabs | templates, versions, lifecycle, branding, render_history |
| Studio mode | Canvas-style editing layout with proof, selection, outline, and assets panels. |
| Template dialogs | Create template, import package, and confirm or destructive flows. |
| Scope controls | Switch between organization and global scope where permitted. |
Key actions
- Refresh the workspace.
- Create or import a template.
- Duplicate, archive, restore, delete, or export a template.
- Open Studio for template or version editing.
- Create a draft version.
- Save branding changes.
- Open rendered proof output.
- Review render history.
Filters and URL state
| Param | What it controls |
|---|---|
documentType | Current output type |
mode | Workspace or studio mode |
shell | Studio shell state |
previewMode | Preview behaviour |
previewSubject | Current preview subject |
scope | Organization or broader scope |
templateId | Selected template |
versionId | Selected version |
- Composer relies heavily on URL state so admins can reopen a specific template or version directly.
- Published versions become read-only even while still visible in the workspace.
Outputs and side effects
- Changes template lifecycle and branding used later in reports, certificates, and quotes.
- Stores draft or published template versions.
- Exported template packages can be moved between environments or retained for backup.
Inbound links
- Reports template-driven output decisions.
- Quote PDF actions.
- Inspection certificate or report template selection.
Outbound links
- Rendered PDF proof output
- Mostly route-local transitions between workspace and studio mode
Indirect handoffs
- Composer affects how outputs look later but does not change the inspection, quote, or report data itself.
- Troubleshooting should start by deciding whether a problem is source-data-related or template-related.
Troubleshooting
| Symptom | What to check |
|---|---|
| A published version cannot be edited | Published versions are intentionally read-only. Create or open a draft path instead. |
| The PDF looks wrong in Reports or Quotes | Confirm whether the issue is data or template structure before editing the template. |
| Studio opens without the expected context | Re-check templateId, versionId, mode, and preview-related params. |
| Branding changes do not appear where expected | Confirm the template scope and the selected branding workspace state. |
Report Writer Route Reference
Understand the review queue for generated report drafts, blocked items, preview state, and the separation between export generation and review.
AI Assistant Route Reference
Understand the route-aware office copilot, conversation context, and how assistant launches preserve the current admin desk state.