Extensions

Settings


images/download/attachments/212896171/extensions-version-1-modificationdate-1751601652285-api-v2.png


(1) Hand input data over to archive system: 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) Check signing: 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.

(3) Environment check through: 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) Preparsing by: You can execute a 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. See section "Preparser" below.

(5) Chain multiple preparser classes: See section "Class chain wizard" below.

(6) Class-Chain-Wizard: See section "Class chain wizard" below.

(7) Result of preparser overrides backup file: 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) Postparsing by: Similar to the preparser, a 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.

Preparser


To configure a preparser, please execute the following steps.

First, enter the name of the properties configuration file in the “Config file” field, e.g. “./conf/example.properties”. If it doesn't exist, it will be created.


images/download/attachments/212896171/1-version-1-modificationdate-1751615167928-api-v2.png


You can then configure this file using a wizard, which you can open by clicking the icon to the right of the file name. If the preparser has no parameters, this option is inactive. Important note: In order for the wizard to function correctly when using an existing configuration file, the file must be structured correctly (which it is if it was created by the wizard). This means that you cannot use a properties file that is intended for another preparser.

If a switch is inactive, it is a mandatory parameter.

If you do not set the switch, the parameter is entered in the file (with its default value) but commented out.


images/download/thumbnails/212896171/2-version-1-modificationdate-1751615167930-api-v2.png


You can open the documentation for the respective preparser and its parameters by clicking on the question mark icon on the left. Here you will also find sample configuration files that illustrate how more complex wizard dialogues are structured.


images/download/attachments/212896171/3-version-1-modificationdate-1751615167931-api-v2.png


Alternatively, you can work directly in the properties configuration file using the second icon to the right of the file name. The wizard is only intended as an aid for editing this file. You can also check in the file which entries the wizard has actually created.


images/download/attachments/212896171/4-version-1-modificationdate-1751615167932-api-v2.png

Class chain wizard


If checkbox (5) is set, the ChainPreParser will automatically be set in (4). This allows the chaining of several preparsers. The configuration file for the ChainPreParser can be generated with (6). Select the preparsers (in the order they should be executed) and their respective parameters there.