Regardless of the document class selected, the following input parameters are always available:
Parameter |
Required? |
Type |
Description |
Example |
|---|---|---|---|---|
Document |
✔ |
File |
The document to be processed must be specified here. |
|
Custom ID |
|
Varchar |
You can enter your own reference here. The reference can be used for support cases and queries. |
[jr_workflowid] |
Document Name |
|
Varchar |
You can assign your own document name here. This is helpful for recognizing the document in the Parashift interface. By default, the document name is used without a file extension. |
Invoice_[jr_incident] |
Manual document validation |
|
Checkbox |
If activated, the document must first be validated in Parashift for further processing in JobRouter. This can be changed via a process table field variable for each instance. |
Valid values: 1 0 |
Manual document validator |
|
Varchar |
This is the upload configuration that can be configured in Parashift. The “client” configuration is used by default. Only upload configurations that have been created in Parashift can be specified here. |
client |
Wait for manual validation |
|
integer |
Waiting time in minutes. If manual document validation is activated, this parameter can be used to specify the maximum waiting time that JobRouter waits before retrieving the extraction results for the document from Parashift. Important: If this function is used, subsequent changes are not synchronized to JobRouter via the validation in Parashift. The dataset is used for further processing in JobRouter when the time expires. |
300 |
Training |
|
Checkbox |
This checkbox activates all Parashift training activities. Classification training, swarm learning and one-touch learning. |
Valid values: 1 0 |
