Rule Update Timestamps Are Out of Sequence When Migrated Rule Is Updated Same Day Via UI
(Doc ID 1541379.1)
Last updated on FEBRUARY 26, 2020
Applies to:Oracle Insurance Policy Administration J2EE - Version 8.1.0 to 8.1.0 [Release 8.1.0]
Information in this document applies to any platform.
When a rule is migrated with the Migration Tool, the value placed into ivsversionhistory.lastmodifiedgmt is a GMT date value, but when the rule is checked out and checked in again by a user via the OIPA UI, the value placed into ivsversionhistory.lastmodifiedgmt is the local server time, not the GMT. In scenarios where a migrated rule is updated via the UI on the same day as the migration, this GMT/local discrepancy leads to confusion when viewing the version history of the rule, because it looks like the manual checkout/checkin took place earlier than the migration of the rule, which is not the case. The older (migrated) version will get picked by the system as "current version".
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document