Date difference in Interface Vs Process model

Hi Sujitha,

Could you please check user time zone(date giving on interface), process model time zone as well as data base(SQL) time zones, because according to my understanding as per your comments,if any time zone is different from each time zones , this type of scenario will be the out come.

Hi Yamuna,

I Have verified all 3 time zones, In Appian both interface and process model are having PDT and SQL server is in PST.

Hi Sujitha,

While saving to the data to a process variable can you wrap the it in any one of the Date and Time functions like gmt() / local() and try.

May be the following documentation URL helps you.

docs.appian.com/.../Time_Zone_Context.html

Thanks,
Vamsi

Hi Sujitha,

can you please check the timezone setting in general tab of the processmodel properties to see if Override with the initiator's time zone is selected.

Firstly, check the time zone settings in the admin console if it set correctly or not. In the latter case, the function you are using on the interface to call date might cause the issue.
Alternatively,try using text(), local() or gmt() function and validate the same.
Also ensure that from PM properties, general tab “Override initiator’s time zone” is checked

For reference which might help - community.appian.com/.../handling-date-and-time

1) check the Time Zone settings.
2)Check PMs properties for "Override Initiators time zone".
3)check field "types" in interface and PM are of same type(Ex: Date,DateTime).

Hi sujithap,

Date component behaviour in ProcessModel:
Time zone context used by the process. This value may differ from the configured process model time zone, such as when the designer selects the option to override the configured process model time zone with the process initiator's time zone.

Interface:
When Datetime values are presented to users in the interface, they are always adjusted to the current user's time zone. This may cause the expected output to vary significantly. Additionally, the acronym of the user's local time zone (such as EDT) is appended to a displayed Datetime value when it appears in a form, an alert, or in an email.

For More Info: docs.appian.com/.../Configuring_the_Default_Language_and_Timezone.html.

I would be sure to wrap any saved date value in local() (or gmt() and then convert from there if the whole system is on one timezone). Also ensure that you are not confusing a Date with a DateTime. You could possibly be stripping out the time associated with the date and when it is read in as 00.00.00 and being converted to the previous day due to the selected time zone. Ensuring that the value being saved/selected in the form is the same value being written to the pv should correct the issue