Page History

JWT DC offers Time Macros for accessing date and time values like {SUNDAY} for the number of this day in the week (=7). The notion is a "macro", i.e. those keywords are enclosed in {}. In the JWT Cloud expression parser, they are noted as constants without curly brackets. 

The JWT DC expression parser offers a couple of time zones which can be used as time zone parameter for the parser functions described in Dates, times and time zones.

All the time zones in Time Zone Abbreviations - Worldwide List can be used as a value for a timezone when using the JWT DC expression parser. 

The JWT Cloud expression parser relies on the List of tz database time zones, column "TZ database name". It has to be quoted when used as a parameter in a JWT Cloud parser function.

Using these kind of timezone names is especially useful, if you relate to a region with daylight savings time (DST), since this behavior is covered as well, while for timezone abbreviations, the user has to set, e.g. CET or CEST.

Timezone abbreviations may also be ambiguous, like e.g. "CST", which stands for Central Standard time (UTC-6), Cuba Standard Time (UTC-5), and also China Standard Time (UTC+8).

Fortunately, the JWT DC parser function timeZone() accepts the same kind of parameter like JWT Cloud, e.g. "Pacific/Auckland", so you may also want to update your JWT DC parser function call accordingly.

This table shows how the constants for timezones in JWT DC can be mapped to JWT Cloud.

Image Added JWT DC	Mapping	Image Added JWT Cloud
LOCAL	-
RUN_AS_LOCAL		RUN_AS_LOCAL
SERVER_LOCAL	-

This table shows how the constants for languages in JWT DC can be mapped to JWT Cloud.

Image Added JWT DC	Mapping	Image Added JWT Cloud
RUN_AS_LANG		RUN_AS_LANG
SERVER_LANG	-
USER_LANG	-