...
| Application | Handling |
|---|---|
Database Collection Agent | Collected UDRs are updated. |
Decoder (using MZ Tagged) | Processed UDRs are updated. |
Aggregation Sessions | All UDRs belonging to the same format definition - historic and updated - will be considered valid for comparison. If historic UDRs exist within old sessions, or the session format itself has been updated, the session and its content will be updated the next time it is accessed. |
ECS | UDRs will be updated whenever they are read from ECS by the ECS collection agent or accessed through the ECS Inspector. |
| Note | ||
|---|---|---|
| ||
Attempts to collect, process or update historic UDR data when the automatic conversion for a specific format is disabled causes the workflow to abort (or an exception, when done outside workflow processing). |
Conversion Rules
Fields removed from the format definition are deleted and cannot be retrieved. Added fields are by default either set to 0 (zero) (numeric types), false (boolean types), or null (all other types). Changing the type of existing fields may cause the field content to be deleted. For instance, changing from string to int sets the field to 0 (zero), provided that no valid default value is defined.
Only numerical types (int, long, etc) are directly interchangeable. If a numeric value exceeds the number of bytes allowed in the new type, it will be truncated.
Disabling Automatic Conversion
It is possible to disable the automatic conversion to new format versions, and instead define default values for UDR fields added in the new version. This is done from the Ultra Format Converter which is accessed by clicking the Tools button in the upper left part of the Desktop window, and then selecting Ultra Format Converter from the menu.
...