We are experiencing a small problem with the different time-zones. When a Trave

RE: We are experiencing a small problem with the different time-zones. When a Trave

Mike Cichy — Mon, 04 Jun 2012 22:58:58 GMT

This is how this particular datatype works in Appian - underneath, all dates and datetimes are saved in GMT timezone. The datetime is shown to the user in their appropriate locale. If you want specific datetimes shown on dashboards/forms/reports you will have to do the conversion yourself and display data as text.

RE: We are experiencing a small problem with the different time-zones. When a Trave

Cyril — Mon, 04 Jun 2012 19:48:09 GMT

Another questions:
The Departure Date/Time and Return Date/Time are stored in their respective pvs: Why then does the task display the time within the timezone of the current viewer?

RE: We are experiencing a small problem with the different time-zones. When a Trave

Cyril — Mon, 04 Jun 2012 19:45:13 GMT

The current structure of the process (entire process is):
1. Enter the initial request to travel
2. Once approvals and bookings are done - then

A new sub-process commences that has several tasks:

a. Enter Claim details (travel or designate)
b. Submit for Manager approval
c. If approved, submit for Finance Approval

So will this still work since it is in the same process/subporcess?

RE: We are experiencing a small problem with the different time-zones. When a Trave

akhilan — Mon, 04 Jun 2012 18:06:32 GMT

If your forms for collecting the claim details are in a separate subprocess, then you could save the timezone of that process from the process properties into a process variable. This can then be passed into the process that you are using for the Manager. In the Manager's process, the out of the box function local(whateverdatetimewasselected, timezoneofthedatacollectionprocess) can be used to get the correct time based on the requestor's timezone. Hope this is of help.