Workflow Task Items Using SystemDate As CreatedGmt
(Doc ID 2780167.1)
Last updated on APRIL 03, 2023
Applies to:
Oracle Insurance Policy Administration J2EE - Version 11.2.0.29 and laterInformation in this document applies to any platform.
Symptoms
On : 11.2.0.29 version, General
ACTUAL BEHAVIOR
---------------
Workflow task items using SystemDate as CreatedGmt. When a Workflow Task item is created via requirement processing, the CreatedGMT value is being set to the current SystemDate instead of using a current timestamp. Additionally when UpdatedGmt is updated for the Workflow Task item, in most cases it also does not use a timestamp, but the date 00:00:00 (for hh:mm:ss). There is a business need to be able to assign the oldest (based on Timestamp) workflow item.
EXPECTED BEHAVIOR
-----------------------
When a Workflow Task item is created via requirement processing, the CreatedGMT should be an accurate timestamp for when the item was created.
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Created RequirementDefinition that includes a WorkflowTask
2. Process requirement to state that generates WorkflowTask
3. Verify that CreatedGMT for WorkflowTask item is set to current system date and does not include hours minutes seconds
Cause
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
| Symptoms |
| Cause |
| Solution |
| References |