Formatting Date/Time

Dates in the Platform are stored as strings in the ISO 8601 format, which has the following structure:

YYYY-MM-ddTHH:mm.ss.SSS

Examples:

  • 2024 — year 2024

  • 2023-02 — February 2023

  • 2022-04-12 — 12th of April, 2022

  • 1987-03-31T04:30 — 31st of March 1987, 4:30 a.m. UTC

Formatting dates has three use cases:

Examples

DD MMM

24 June

DD.MM.Y

24.06.2023

Formatting date/time details:

Symbol

Meaning

Type

Mask

Example

C

Century, AD

number

CC.dd.MM.yyyy

20.31.12.1909

Y

Year, AD

number

Y

1996

w

Week in a year

number

ww

27

e

Day of a week

number

e

2

E

Day of a week

text

EEEE

E

Tuesday

Tue

y

Year

number

y

1996

D

Day in a year

number

D

189

M

Month in a year

text

number

MMMM

MMM

MM

July

Jul

07

d

Day in a month

number

dd

31

a

AM/PM

text

a

a

AM

PM

H

Hour (0~23)

number

H

0

m

Minute

number

mm

36

s

Second

number

ss

25

S

millisecond

number

SSS

783

z

Time zone

text

z

Pacific Standard Time; PST

Z

Time zone / shift

text

Z

-0800; -08:00; America/Los_Angeles

Formatting date field type

Time constraints field:

{
   "hours": {
      "min": 1,
      "max": 15,
      "step": 3
   },
   "minutes": {
      "min": 10,
      "max": 30,
      "step": 20
   }
}

Remember, these constraints only affect web page components and user input in the platform. Scenarios and API calls are not limited.

Time zones

Dates are stored in the UTC format. If you select 'use user's local time zone' in settings, the platform's interface and web-page builder-based apps will automatically use the user's browser time zone. However, when working with dates in scenarios, you must manage the time zone manually using the moment({{your_date}}).zone(Z).format();function, where Z represents the timezone offset, such as -3 or +10 .

Last updated