In Appian, date and time (or datetime) data is adjusted to display in the correct time zone for the user who is viewing the data. A date and time is displayed in your preferred time zone, in a system-wide timezone setting, or in a process designer-specified time zone.
When designing an application, you can set a process time zone context for the
date and time data or date and time functions used in a process from the Process Model Properties dialog box on the General tab.
See also: General Tab
This setting can be referenced in your process models using the
pp!timezone property which is listed as the default time zone for recurring activity schedules.
Reports, rules, and dashboards take the context of the current user as shown in the table below.
|Context||Time Zone used|
|Process||Non-User-Initiated Process||As Configured|
|User-Initiated Process||As Configured (OR) Initiator's Time Zone|
|Subprocess||Parent Process' Time Zone|
|Portal||Analytics (reports)||Current User's Effective Time Zone|
|Rules Test UI|
|Web Content w/Process Details|
As Configured refers to the fact that the time zone can be specified by the designer in the Process Model Properties dialog box on the General tab. Programmatically launched processes always use the configured time zone. Subprocesses always use the parent process' time zone.
When the Time Zone Context is Used
The Date and Time Functions
today() and functions that cast a date and time value to a string of text (such as the
text() functions) use one of the process time zone contexts and take the user's time zone when the functions are evaluated in a process.
todayand whether the deadlines for tasks and processes fall within that day for the user viewing the report.
cal*) do not use the time zone context. They operate based on the calendar time zone.
Time Zone Context