[
https://issues.jboss.org/browse/DROOLS-2777?page=com.atlassian.jira.plugi...
]
Guilherme Carreiro closed DROOLS-2777.
--------------------------------------
Resolution: Done
Dates are persisted with UTC timezone in Workbench. For example, the
"DateTable.gdst" provided by the sample kjar has the "2018-04-30 21:00:00.0
UTC" value, see:
<value>
<valueDate>2018-04-30 21:00:00.0 UTC</valueDate>
<valueString></valueString>
<dataType>DATE</dataType>
<isOtherwise>false</isOtherwise>
</value>
Since the server was in the "Europe/Vilnius" timezone, the inputted value was
converted from "2018-05-01 00:00:00.0 EEST" to "2018-04-30 21:00:00.0
UTC" when this GDT was persisted (as you can see in the snippet above).
When the user changes the timezone to "Europe/Prague" and opens the GDT Editor,
the value is converted from "2018-04-30 21:00:00.0 UTC" (from the
"DateTable.gdst" file) to "2018-04-30 23:00:00.0 CEST". Notice that no
date was changed, the Workbench just considers the current machine timezone for
presentation purpose.
We recommend the use of the drools.dateformat parameter as something like
-Ddrools.dateformat="dd-MM-yyyy z" (including the timezone), to avoid any
misinterpretation during the presentation of these values.
Guided Decision Table is changing date field value based on the
timezone
------------------------------------------------------------------------
Key: DROOLS-2777
URL:
https://issues.jboss.org/browse/DROOLS-2777
Project: Drools
Issue Type: Bug
Components: Guided Decision Table Editor
Reporter: Michael Anstis
Assignee: Guilherme Carreiro
Labels: drools-tools
If I set a Date Field in Guided Decision Table, then change the timezone, restart the
server, log in again, the Date Field has *different* value
Expected: decision-central should never attempt to change the rules automatically without
user's knowledge
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)