Extended (Phase 2)

(1) If this checkbox is set, you can select a variable. This variable enables the execution of SQL statements in phase 4 if its value is true. If no variable is selected, the (set) checkbox behaves as if there was a variable with value true.

(2) Destination field values will be trimmed before written into the database in phase 4. See also (1).

(3) See section Phase 4.

(4) See section Swapping.

(5) See section Skip Record in Case of Error.

(6) This checkbox applies to source structure fields. If the checkbox is not set, fields without a value will be filled with an empty string or the default value. If the checkbox is set, the Empty Flag will be set for fields without a value.

(7) This checkbox applies to destination structure fields. If this checkbox is set, no internal data objects are generated for empty fields. This can save memory if empty fields in the destination tree are not needed.

(8) Only those source fields that are mapped or which are referenced as function parameters are kept in the main memory if the checkbox is set. This saves memory when only a few fields are used for large input files. This option has no effect for the XML parser version 4. It cannot be used for document types EDIFACT in TradaComs format or BWA. If function copy field by name(variable/result a) is used in the profile, the checkbox may not be used. If set, it will be removed when saving the profile.

(9) Indicates whether numeric data types (Integer, Float, Double, BigInteger, BigDecimal) should be filled from the left with zeros (0), even if this formatting is not explicitly set in the fields. This setting is only relevant for the output format Fix record.

(10) If a node has several match codes and you want to know which one actually matched when the node was entered, you have to set this checkbox. Then, you can simply use function get matched value(a) to read out the value. Attention: Setting this checkbox considerably increases the memory requirements for the source tree.

(11) See section Execute Response Routes per Record.

(12) If this option is set, fill settings of fields will be reapplied after the template has been applied. Only needed if you use content Fix record in a Response Route.

(13) Checks whether the input value is Base64-encoded and decodes it if it is. Note: This option only makes sense if the output format is not based on fixed lengths, since the length of the data is changed if decoded.

(14) The simple data mapper does not allow hierarchies below nodes. The normal data mapper allows complex hierarchies in the source and destination structure.

(15) All source fields that have the attribute New record if value changes set are listed here. The fields can be linked with AND or OR. You can jump directly to the corresponding field in the source structure.