Output channel ERP system
The data coming from the OCR is sent from xSuite Bus Prism to xSuite Interface Prism. For this, the input channel xFlowBus2 [Input.xFlowBus2] must be selected as the inbound scenario in xSuite Interface.
The following parameters are available for configuration of the input interface:
Parameter | Description |
|---|---|
| Here, the path can be set to store the files as ZIP files after successful processing if a name is specified for this file. For these file names, the variables |
| Here, you can specify what reaction is to take place when an identical file was already stored in the backup directory. |
| Optional path of a folder in which the log files are to be stored. |
| HTTP address of the xSuite Bus Service. This web address can be traced in the IIS. The structure is always Example: |
| Parameter that assigns an Interface configuration to a client or customer set up in xSuite Bus. This allows xSuite Interface configuration to specify which xSuite Bus client or customer was assigned and which workflows or actions are to be executed. |
| When the Owner is specified, it is possible to map different xSuite Interface scenarios in an xSuite Bus instance. |
| Optional field for transfer of a field in the field catalog that is to be set as the document key and transferred as such to xSuite Bus (e.g., |
| Descriptive numeric value for the field
|
| Optional internal name of field-catalog fields that contain a global ID and/or key to be transferred to xSuite Bus in order to be able to identify a document across systems and monitor its processing. The ID must be available in the syntax UUID (xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx), whereas a numeric counter is normally used for the key. If it is to be generated as an initial name in xSuite Interface, then the field macro For example, a |
| Optional filter. You can define whether BLOB files are to be received from xSuite Bus. The pre-set value is |
| Parameter for deleting xSuite Bus items after processing. |