Phase 5 (GUI)

See also the introduction to phase 5.

images/download/attachments/36576191/Phase_5_Uebersicht_EN-version-3-modificationdate-1572567180315-api-v2.png

(1) The selected Integration Unit.

(2) Documentation to (1).

(3) The execution of an Integration Unit can be made dependent on a variable of type Boolean. The Integration Unit is executed if the variable has the value true. Note: In principle, a variable of type String can also be used. In that case, an implicit type conversion takes place.

(4) The parameters of (1). Details can be found in (2).

(5) Selection of a postexecution class.

(6) Documentation of the postexecution class (5).

(7) The path to the configuration file of the postexecution class (5) (if necessary). Sometimes you need to enter a direct configuration string instead, but this will be documented in the respective class.

(8) The encoding of the output data of the Integration Unit (1).

(9) If you are using an Integration Unit in an older profile, newer versions of the Integration Unit may have new parameters added. These can be updated manually with this button. Important note: Newly added parameters are set with their respective default values. That could lead to a different behaviour. Please always check the updated parameters so that no unwanted effects occur.

Accessing Output Data of the Integration Unit in the Response Route

For a Response Route to be able to access the data created by an Integration Unit, the Content has to be set to Content of IU.

In general, please note that for binary formats, such as PDF and Excel, you always have to use the encoding ISO-8859-1 in Response Routes to ensure that the formats remain intact.