Extensions (General Data)

images/download/attachments/73597691/Erweiterungen_2_EN-version-1-modificationdate-1618985989686-api-v2.png


(1) If set (only possible if there is a connected archive system), the input data will be handed over to an archive system. Note: At the moment we only support LIB-IT.

(2) If the signature system Digiseal from Secrypt is connected, signed input data is verified if the checkbox is set. If the signature is valid, Digiseal will generate a report. You can specify a profile to process that report. If the signature is invalid, an error will be generated and an error email will be sent. The configuration of Digiseal will not be described here. See also section DigiSealPostExecuter.

(3) Here you can specify an Environment Check class. See also section Phase 2. Note: A documentation of a selected class can be obtained via the question mark icon.

(4) You can execute a so-called preparser before the parser. The preparser allows you to manipulate the raw input data before the parser creates the source tree. See also section Phase 2. Note: A documentation of a selected class can be obtained via the question mark icon.

(5) and (6) See the following section.

(7) If this checkbox is set, the backup file of a job of this profile will not contain the original input data, but the data that results from the execution of the preparser. Note: The original file name and extension will be preserved.

(8) Similar to the preparser, a so-called postparser can be executed after the parser. See also section Phase 2. Note: A documentation of a selected class can be obtained via the question mark icon.

Class Chain Wizard


If checkbox (4) is set, the ChainPreParser will automatically be set in (5). This allows the chaining of several preparsers. The configuration file for the ChainPreParser can be generated with (6). The following screenshot shows an example.


images/download/attachments/73597691/Erweiterungen_3_EN-version-1-modificationdate-1618985989690-api-v2.png


Here you select the preparsers (9) and their respective parameters (10), in the order they should be executed. The configuration file for the screenshot above can be found in the example file of the ChainPreParser.