Uploading Documents
Documents can be uploaded through drag-and-drop areas, import jobs, e-mail inboxes, scan processes, or integrations.
After upload, centraQuest may classify the document, extract metadata, run OCR, create tasks, or start a workflow depending on configuration.
Upload Channels
| Channel | Typical use |
|---|---|
| Drag and drop | Manual upload by users from a dashboard or module page. |
| File selection | Manual upload through a file picker. |
| E-mail import | Automatic import from configured mailboxes. |
| Scan process | Import from scanner output or watched folders. |
| ERP or API integration | Technical import from external systems. |
| Portal upload | Upload by external or role-specific portal users. |
Drag and Drop
Drag and drop is the most common manual upload method. Users place one or more files on a configured upload area.
Depending on the upload area, centraQuest may already know the target document type. For example, an Invoice upload area can start invoice processing directly, while a general archive upload may ask for more metadata.
What Happens After Upload
After a document is uploaded, several automated steps may run:
- The file is stored.
- A document object is created.
- Metadata is initialized.
- OCR or preview conversion may start.
- Classification or AI analysis may run.
- A lifecycle state is assigned.
- A workflow or task may be created.
- The document appears in a dashboard, list, or inbox.
Some of these steps are asynchronous. A document can therefore appear before preview, OCR text, or analysis results are complete.
Upload Validation
If an upload fails, check:
- file type,
- file size,
- file name,
- browser connection,
- permissions on the upload area,
- target module,
- whether the file is password-protected or damaged.
If the upload succeeds but processing stops later, the issue is usually not the upload itself. Check preview conversion, OCR, classification, import logs, or module-specific processing logs.
Duplicate Documents
Some installations detect duplicate documents by filename, message ID, barcode, invoice number, checksum, or other metadata. Duplicate handling is module-specific.
If a document appears twice, check whether it was uploaded through different channels, for example once by e-mail and once manually.