List of available internal UDR formats stored in the Ultra and Code servers. The formats are named according to the following syntax:

<internal> (<module>)

If the decoder is to reprocess UDRs of an internal format, you must select the Decoder MZ format tagged UDRs to enable this list. Once enabled, you can select the internal format.

If you select this check box, the UDR is fully decoded before it is inserted into the workflow. This may have a negative impact on performance since all fields may not be accessed in the workflow, making decoding of all fields unnecessary.

If disabled (default), the amount of work required for decoding is minimized, using a "lazy" method of decoding sub fields. This means the actual decoding work may not be done until later in the workflow, when the field values are accessed for the first time.

Corrupt data (that is, data for which decoding fails) might not be detected during the decoding stage and may cause the UDR to be discarded at a later processing stage.

Select the required decompression algorithm:

• No Compression: The agent will not decompress the files. This is the default setting.

• LZO: The files are compressed using LZO compression. If you select this option, the Command Line field is displayed and populated by default with the command lzop -d -c -q. This command allows you to use the lzop unix command to decompress standard input with the LZO algorithm and write the output on standard output. You can enter an alternative lzop command if required. For further information on the lzop command, see https://www.lzop.org/lzop_man.php.

Select this option if you want the workflow to be run repeatedly with an interval of a specific number of seconds. The default value is 5 seconds.

If you have selected this option, when the agent encounters an error, the workflow does not abort. The error is reported in the System Log and the agent retries at the next repeat.

Select one of the error handling options to control how to react upon decoding errors:

• Cancel Batch - Processing of the current batch is stopped and skips to the next batch.

• Route Raw Data - Route the remaining, undecodable, data as raw data. This option is useful if you want to implement special error handling for batches that are partially processed.

Abort Immediately

If enabled, the workflow immediately aborts on the first Cancel Batch message from any agent in the workflow. The erroneous data batch is kept in its original place and must be moved/deleted manually before the workflow can be started again.

Abort After X Consecutive Cancel Batch

If enabled, the value of X indicates the number of allowed Cancel Batch calls, from the collection agent before the workflow will be aborted. The counter is reset between each successfully processed data batch. Thus, if 5 is entered, the workflow will abort on the 6th data batch in a row that is reported erroneous.

Never Abort

The workflow will never abort. However, as with the other error handling options, the System Log is always updated for each Cancel Batch message.

(bytes)

Volume (UDRs)

When the file contains the number of UDRs entered in this field, the file will be closed and stored in the storage directory. If nothing is entered, this file closing criteria will not be used.

Timer (sec)

When the file has been open for the number of seconds entered in this field, the file will be closed and stored in the storage directory. If nothing is entered, this file closing criteria will not be used.