Handling of values for DateTime-columns (DialogColumn.DateTimeDetail = 0) with time-part equal to “00:00:00” with OIM Version 9.0.x & 9.1.x. and new handling in 9.2.x. (4371110)

Handling of values for DateTime-columns (DialogColumn.DateTimeDetail = 0) with time-part equal to “00:00:00” with OIM Version 9.0.x & 9.1.x. and new handling in 9.2.x.

The new behavior is not a defect and it was introduced in Identity Manager versions 9.0/9.1 with Change Request #33472.  In earlier versions (including 8.1.5) the handling of dates with time part "00:00:00" was erroneous.

This time part "00:00:00" has a special handling in the object-layer.  Here it is necessary to understand two things:

1. The Front-End tools show time in current Time zone, whereas object layer (VI.DB) and the DataBase itself work always with the UTC times.

2. There are several formats of DateTime in Identity Manager, which are defined by value of DialogColumn.DateTimeDetail for the column.  Some DateTime-columns do not contain time part, but rather only the date part, for example, Person.EntryDate (DateTimeDetail = 1) and for such columns there is no conversion in/from UTC and such dates have always "00:00:00" time-part in the DataBase.  Some DateTime-columns, on the other hand, require time-part (DateTimeDetail = 0), for example "Person.DeactivationStart".

Prior to hotfix 33472, the object-layer could not work correctly with time-part for such columns and has always interpreted "00:00:00" part as date only and never did UTC conversion for such times.  If, for example, in version 8.1.5 in Manager or Object Browser you would input a date with time "00:00:00" (in CET, e.g.), you would expect that the time in the DataBase would be saved as "23:00:00", but no UTC-conversion took place there and the date would have been saved erroneously in the DataBase as "00:00:00".

On OIM Version 9.0.x, 9.1.x:

Due to the special handling of "00:00:00" times by the object-layer, you will also see an additional second in the DataBase in case the time-part of the DateTime-columns with DateTimeDetail = 0 corresponds to UTC time "00:00:00".  But only this special time "00:00:00" is affected, which in the case of DateTime-columns with DateTimeDetail = 0, will always be saved as "00:00:01".  This should have no negative consequences and the object-layer (Manager/Object Browser) always removes this additional second, which explains why the additional second is not seen there.

On OIM Version 9.2.x:

Thanks to changes made with Fix #36945, no marker in the object layer and no additional second in the DB will be present anymore. At the time, the changes will affect only the upcoming 9.2.