Source: fujitsu america ( keith swenson)
All date expressions, if the timezone is not explicitly mentioned, are interpreted as being in the timezone of the computer running the code. This means you can design a model that runs correctly in one timezone,a nd incorrectly in a different one.
Imagine you have a development team in Bangalore which makes a DMN model that runs correctly and passes all the tests. Then it is installed into the company server in London, and it fails.
Does anyone think this is a good idea?
The solution is simple: the model should have a default timezone. All date expressions that don't mention the timezone are interpreted according to this default time zone, and NOT according the timezone of the machine you are running on. Then, models will run exactly the same way no matter where it is run. That is a good idea, right?
See this: https://social-biz.org/2017/08/03/a-strange-feeling-about-dates/
Reported: DMN 1.2 — Wed, 18 Sep 2019 09:55 GMT
Updated: Thu, 6 Apr 2023 14:59 GMT
DMN15 — DMN Models need a default timezone
- Key: DMN15-38
- OMG Task Force: Decision Model and Notation 1.5 RTF