The Data Relationship Management user interface displays date and time in local time and format according to the user's session. When converting timestamp values from releases prior to 11.1.2, the following rules apply:
Timestamps are converted to UTC using the offset of the time zone in which the Data Relationship Management console is running. If the console is running in a time zone that is different than the time zone in which the pre-11.1.2 release source data was written, then the converted dates could be earlier or later by one or more hours.
Releases prior to 11.1.2 did not consistently apply daylight savings time, therefore all dates are converted using the offset dictated by the time zone in which the console is running, regardless of when the date falls. For example, in the Eastern time zone, the standard UTC offset is -5 hours; during daylight savings time periods, the offset is -4 hours. For upgrade purposes, dates are converted using the standard offset. For all new data added after the repository is upgraded, the stored dates reflect the applicable standard and daylight savings UTC offsets.
Transaction records for deleted versions in the source repository are not copied to the target repository, thus the number of Transaction History records copied may not match the row count in the target RM_Transaction table.
If you deselect versions, transactions belonging to those versions are not copied.
The Export Run transaction type stores the export name in the Object Name field instead of the Property Abbrev field.
The Data Relationship Management upgrade process uses the following transaction name mappings:
Old Transaction Name | New Transaction Name |
|---|---|
Automator Run | Action Script Run |
Migration Extract | Migration Export |
Migration Load | Migration Import |
Add System Category | Admin Add Hierarchy Group |
Update System Category | Admin Update Hierarchy Group |
Delete System Category | Admin Delete Hierarchy Group |