The output system "Internal" can be used when using multi-level scenarios to pass a document from one scenario to a subsequent scenario.

Unlike alternative transmission paths (e.g., web services or files in "InternalJson" format), the transfer takes place directly within the running program instance. This means that the target scenario must also be active in this instance. An input system of the type "Internal" must also be defined in the target scenario. In contrast to the default setup, this input system does not run in its own worker instance, but rather is executed in the context of the output system and its workers.

Input processing is not triggered asynchronously by periodic queries for new data, but by a direct call from the output system. In principle, special functionalities such as document separation and the use of input format readers can be used during input. However, error handling behaves differently in this case. If errors occur during input processing, these immediately lead to output processing being aborted. Rather than a new batch being generated that contains an error in the "Input" step, the output step is displayed with an error in the Status Monitor. The error is also usually logged in the context of the relevant output worker.

The following properties apply to the configuration of this output system: