DMS and archives

Scan into the record already open.

Keep document capture inside the case, folder or customer context. ScanBridge returns the reviewed file to your handler; your application keeps control of metadata, storage and permissions.

Replace the upload detour.

A scan-to-folder process makes the user leave the record, choose a separate scan destination and find the file again. An integrated workflow already knows where the document belongs.

1. Open recordThe user selects the case, customer or folder in your DMS.
2. ScanThe widget connects to the workstation's TWAIN or WIA scanner.
3. ReviewProfessional adds multi-page capture, reorder, remove and editing.
4. SaveYour handler receives the Blob with the record context still available.
Your application owns context

Metadata stays attached to the workflow

The customer ID, case number, document type and access rules remain values in your own page and backend.

ScanBridge owns acquisition

Driver handling and scan UI are ready

The local helper discovers devices while the widget exposes only the controls the connected scanner reports.

Your backend owns storage

No ScanBridge document cloud

The saved event returns the file to your code. Your application decides where it is uploaded and retained.

A minimal handoff.

The current record ID is ordinary application state. Add it to the upload alongside the PDF returned by the widget.

scanner.addEventListener('saved', async (event) => {
  if (event.detail.fileType !== 'pdf') return;

  const form = new FormData();
  form.append('recordId', currentRecordId);
  form.append('document', event.detail.blob, 'scan.pdf');

  await fetch('/api/documents', {
    method: 'POST',
    body: form,
  });
});

The endpoint and metadata are examples; ScanBridge does not prescribe your storage model.

Evaluation

Test one complete record workflow.

Choose one real document type, one scanner model and one upload endpoint. Measure the time to first successful scan and any driver or deployment friction.