Created and Opened date/time fields automatically changing

[Sabrina10]

I've created an ticket with ServiceNow for this, but also wanted to post here, in case someone else has seen this.

After upgrading to Berlin (patch 3, hotfix 1), we've noticed that everytime a Catalog Task is updated, the values in the Created (sys_created_on) and Opened on(opened_at) fields on the Requested Item are advancing by 6 hours.

Both fields are extended from Task, and I've checked the dictionary, business rules, script includes, client scripts, ui policies and can't find anything that is initially setting these fields or causing them to advance.

We have customizations, so I'm fully aware that this could be some interaction between the upgrade and our customizations, but I'm having trouble finding it and wanted to post to see if anyone has any ideas. Also, to see if anyone knows how the values in these fields are initially set on Insert.

This is not happening on other forms that have a parent child relationship, like Change Requests and Change Tasks.

Thanks
Sabrina

[NeilH2]

Hi Sabrina

Is this happening on a paticular workflow or is it all of them?

As its happening on update and on the sc_task its one of 3 things
A Business Rule on the sc_task table
A script in the dictionary entry for that table.
A workflow script is running - if its every task generated then its unlikely to be workflow

If its dictionary then there must be an override entry in place as its not doing it on any other table.
If its a BR then its only present on the sc_task BR list

In your test instance disable all your buisness rule / client script etc and activate them in sequence, the one that changes the value is the culprit.

[Sabrina10]

It is happening on all of our Items, so I don't think it is workflow related. I've started down the path of disabling the Business rules, but I didn't think to check the dictionary override. I will look there. Thanks.