Choosing your components
Work down these tables in order. The orchestrator comes first: a document is always uploaded or imported into one.
Which orchestrator?
| Kind | Use it when | What you get |
|---|---|---|
| Smart Extract | You need named values off every document. | A value per field you defined, correctable before it leaves. |
| Smart Classes | You only need to know which type a document is. | A class per document — no fields. |
| Smart Queue | One stream carries several document types. | Each document sorted, then read by the Smart Extract you mapped to its class. |
| Smart Redact | Sensitive content must not be seen downstream. | A redacted copy for everyone; the original only for those in Original Access. |
A Smart Queue needs a Smart Class and an extract per class first — three records, not one. All four share the same tabs: Orchestrator basics.
Connector, or upload by hand?
| Situation | What to use |
|---|---|
| A few files now and then | Nothing — Upload Document, see Uploading documents |
| Documents already arrive in a mailbox, drive, folder, database or API | An import connector, attached on Import Channels |
| Results must reach another system | An export connector, attached on Export Channels |
| Both ends unattended | One of each — see Channels |
The type is fixed at creation — see Choosing a connector type.
Knowledge base, or orchestrator?
| You want to | Use |
|---|---|
| Read the same fields off every document | An orchestrator, above |
| Ask questions in plain language and get answers that cite their source | A knowledge base |
| Both | Both — separate stores; a knowledge base is filled by its own uploads or a source |
Voice IntELIEgence?
Only if your input is conversations rather than documents. A voice application transcribes and analyses them, and can push what it finds into a knowledge base.
Human review?
| Where | What turns it on |
|---|---|
| Smart Extract, Smart Classes | Review Required, from Edit Settings on Overview |
| Smart Redact | Review Required, under Redaction Behavior — or from Edit Settings on Overview |
| Voice application | Require human review |
With it on, work waits at Waiting for Review until someone selects Mark as Reviewed (Review and correct). A Smart Queue has no such switch.
Putting them together
An orchestrator, something to feed it, review where judgement is needed, an export connector to deliver. Build in that order. Leaving one out only shortens the flow — an orchestrator you upload into by hand already works.
Next
- Build your first workflow — all four, in order.
- Connecting the pieces — where each join is made.