In Siebel, sometimes it’s difficult to know when context for background workflows is running. It’s not always obvious. I found the truth of the context for background workflow running from an email time zone issue. Let’s start with the issue first.
One day, I found an issue in the Siebel outbound email date type time zone, the date data in Siebel UI is GMT+7, but it was showing GMT+1 in the email content. I thought it must be the time zone difference causing this issue, the date data was converted to GMT+1 time zone automatically. But was this what is happening?
As we know, outbound email is handled by Communications Outbound Manager component. In all parameters of this component, there is one parameter called “Request Time Zone” that seems related with this issue. Unfortunately, after I updated this parameter to GMT+7, the issue was still there.
So, I came to another assumption. What if the time zone is decided by the component execution owner, not component itself? Under this consideration, I updated the time zone field for SADMIN user in his personalization setup. After I restarted server, the problem was solved.
In conclusion, the background workflow running context is relying on the context of component execution owner. So, we found a truth which bookshelf not telling, if meet the similar context related issue, could think from execution owner’s context for solution.
