Workflow Monitor Sets LAST_UPD Column Using Local Time Instead of UTC
(Doc ID 2843970.1)
Last updated on MARCH 18, 2022
Applies to:Siebel CRM - Version 15.7 [IP2015] and later
Information in this document applies to any platform.
Based on the business requirements, several workflow policies were created for updating data on different entities ( e.g. accounts). In Siebel version 15.7 was reported that when records are updated the workflow monitor sets the column LAST_UPD using the local time and not UTC.
The company has several branches that operate in different time zones, so the following values of the system preferences were set:
Universal Time Coordinated = TRUE
Default Time Zone = (GMT + 03: 00) Moscow, St. Petersburg, Volgograd
Database time zone = +03: 00. It was tried to change the database time zone to +00:00 but behavior was the same.
The same issue was reproduced in standard environment 21.10 version using steps:
1. Create a policy group named 'Service request' in Administration Business Processes -> Workflow Policy Groups
2. Go to Administration Business Processes ->Workflow Policy Actions and create an action with:
Program: Change SR Sub-status
Workflow Object: Service Request
Activation date: a date in the past
3. Added an argument for the action:
Argument: New Sub-Status
Value: Additional Documents Required
4. Go to Administration Business Processes -> Workflow Policies and create a workflow policy with:
Workflow object: Service Request
Policy Group: Service Request
5. In the Conditions applet add a condition: Service Request Status = Submitted
6. In the Actions applet add the policy action created in step 2.
7. Go to Administration Server Configuration screen and for the Workflow Monitor component:
Group Name=Service Request
8. Generated the triggers in Administration Server Management -> Jobs.
9. Set server time to GMT +3 Moscow time
10. Set the same time zone for the SADMIN user in Tools -> User preferences
11. Shutdown the server
12. Set the db timezone to +00:00
13. Start the siebel server
1. Create a service request, save it. Note the row id and check in the db the CREATED and LAST_UPD => they are both in UTC time.
2. Change the Status to Submitted to trigger the workflow policy and wait 1 minute.
3. Check the service request, confirm that policy was triggered (Sub status was set to 'Additional Documents Required')
4. Check in the db and see that LAST_UPD was changed to a date time in local time GMT+3
CREATED = 29-10-2021 15:49:00
LAST_UPD = 29-10-2021 18:49:36
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