Document Managementdata

Attachments & Records

How do documents stay attached to the requests and records they belong to?

A document rarely stands alone — it evidences a request, an employee record, or an order. Files upload directly against those records and running process instances, so the paperwork is on the record when an approver opens it, and still there years later.

Referenced across4 other parts of continON

How it works

Attachment is part of the working screens, not a separate filing chore. Files — several at once, where needed — upload against a running process instance, a request, or an employee record, land in the shared store, and are referenced by the record they document.

As a request advances state by state, its attachments travel with it: the approver at each stage opens the evidence from the request itself rather than hunting a drive. Documents generated from templates during the process join the same record, so uploaded evidence and produced output sit side by side.

Because the store is one shared service, the same file surfaces in every application that references the record — there is no per-app copy to drift out of date, and the grant on the file governs it identically everywhere it appears.

What is filed, and who reaches it

Attachments & Records

  • Upload against the record

    Files attach to requests, process instances, and employee records from the screens where the work happens.

  • Attachments travel with approvals

    Each stage of a running request opens the same attached evidence — no re-sending, no re-finding.

  • Generated output joins the record

    Template-generated PDFs file onto the same record as the uploads that justified them.

  • One file, referenced everywhere

    A record’s document is the same stored file in every application — never a copy.

See attachments & records running in continON.

A guided walkthrough on a sanitized demo tenant — this capability inside its module, on the shared platform.