Connecting the pieces
Each app works on its own; workflows break at the joins between them. You make every join from the receiving end, and the orchestrator has to exist first, because a document is always uploaded or imported into one.
Connector to orchestrator
Open the orchestrator in IntELIEDocs, select Import Channels in its left rail, and tick the connector in the Import Channels Selected drop-down. Only import connectors that are Active and Connected are offered. Ticking adds a row; select Connect in its ACTION cell to turn the channel on. It is live when that cell reads Disconnect, and the connector checks its source straight away. A connector attached to nothing does not fetch at all, so no document is lost while you set things up. Steps: Binding an import connector.
The connector's own Bindings tab in IntELIEKonnect lists everything it is attached to, which helps when one connector feeds several orchestrators.
Orchestrator to review
Nothing waits for a person unless you ask it to. On a Smart Extract, Smart Classes or Smart Redact, select Edit Settings on Overview and switch on Review Required. A Smart Redact also asks while you create it, under Redaction Behavior. A Smart Queue sets it on its Pipeline tab, under Review. The join is live when new documents stop on Waiting for Review instead of moving straight on. See Orchestrator basics and Signing off and re-running.
Orchestrator to export
On the same orchestrator, select Export Channels and tick connectors in Export Channels Selected; you can attach several. Select Connect on each new row, and look for Disconnect again. A document that needs review leaves only after Mark as Reviewed. It then shows Exporting while it goes out, or Queued for Export while a connector set to Scheduled Batch holds it for its next run, and Exported once every connector has it. Steps: Binding an export connector.
Connector to knowledge base
Import connectors can feed a knowledge base too. Open the knowledge base, select Sources, then the IntELIEKonnect card or its Manage connectors, and select Connect beside the connector. In the panel, set who may retrieve the documents it brings in (Public, or limited by Access role, Department and People group) before you select Connect; a connector carries no access rules of its own. The join is live when the row reads Connected with Enabled on. Documents it pulls in appear under Documents marked IntELIEKonnect, while files added by hand are marked Manual upload. See Sources.
If something goes wrong
| Symptom | Likely cause | What to do |
|---|---|---|
| Fetch now reports Couldn't start the fetch. | The connector is not attached anywhere live: no channel reads Disconnect. | Select Connect on the orchestrator's Import Channels tab. See Import and export channels. |
| Fetch started, but no new documents arrive. | Nothing new has reached the source since the last run. Files already imported are not fetched again. | Add a new file at the source, then select Fetch now again. |
| Documents reach Completed without stopping for anyone. | Review Required is off on that orchestrator. | Switch it on in Edit Settings. See Orchestrator basics. |
| Documents finish, nothing is delivered and no error appears. | No export channel is attached, or its row still reads Connect. | See Binding an export connector. |
| A knowledge base source reads Connected, but answers never use its documents. | The access set on the source excludes the person asking. | See Who can see a knowledge base. |
Next
- Build your first workflow - every join, in order.
- Watching a workflow run - checking each join carried a document.
- When a workflow stalls - finding the join that stopped.