Content settings
(1) Decides which content is to be output in the Response Route and/or in what format.
|
CSV, Excel, Fix record and XML |
The data is taken from the target tree. The data is automatically formatted according to the selected content type. Note: These formats are relatively simple in structure. Alternatively, corresponding Integration Units can also be used (set to "Output of IU" then ): CSVWithHeaderUnit , CSVWithoutQuotesIU , ExcelAppenderUnit , ExcelWithHeaderUnit , FixValueUnit , XMLNoTemplateUnit . |
|
Output of IU |
Instead of the data of the target tree, the output of the Integration Unit is output. The respective Integration Unit also determines the format. |
|
as received |
Instead of the data of the target tree, the originally received data is output. This can, for example, be useful in the following cases. The manipulated data of the mapping is written into a database, but you also want to forward the unchanged input data. You want to use the same input data for several profiles. You can simply forward the unchanged input data to the next profile via a Response Route of type "Message" and save the converted data of the mapping into a file in another Response Route. If the input data is a compressed file with several files in it, the individual files will also be sent in compressed form. |
|
as received, uncompressed |
Instead of the data of the target tree, the uncompressed, originally received data is output. If the source data was a single compressed file, the output file will be uncompressed. If the source data was a compressed file, with several files included, the individual files are also passed on uncompressed. |
|
as received, uncompressed, change encoding |
Instead of the data of the target tree, the uncompressed, originally received data is output, but the encoding is changed to the one configured in field "Encoding" (2). |
|
Trigger profile |
This option is only available for Response Route "Message". See details there. |
|
No content |
This option is only available for Response Route "HTTP". See details there. |
(2) The encoding of the output data.
(3) The delimiter character between field values (only relevant for content type "CSV"). 0x = hexadecimal values, NL = newline.
(4) The quoting character for content type "CSV" (e.g. to mask/escape the CSV delimiter character (3), blanks or linebreaks in field values). Only double or single quotation marks makes sense. To avoid quoting, please use the Integration Unit CSVWithoutQuotesIU. See also (6).
(5) The line break character.
(6) All field values (not only blanks and delimiters) are put in quotes (4).
(7) If this checkbox is set, the file will not end with a line break (5).
(8) Only relevant for content type CSV. The generated CSV format complies with the conventions used by Microsoft Excel.
(9) Specifies whether and how the output data should be compressed. You can specify a (AES) password for ZIP and 7z, however, with 7z an AES password is always changed back to a normal password after saving. Note: The name of the file in an archive of the Response Route with the position number n (in the list of Response Routes) can be set via the system variable VAR_SYS_ARCHIVE_ENTRY_n.
(10) Selection of a postexecution class. Note: The documentation of a selected class can be obtained via the question mark icon.
(11) The path to the configuration file of the postexecution class (10) (if necessary). Sometimes you need to enter a direct configuration string instead, but this will be documented in the respective class.
(12) Only relevant for content type Fix record. If set, line breaks (CR and LF) in field values are replaced by blanks.