Formatting date/time data
There are three use-cases of formatting date:
- Setting standard formatting for data structure field.
Here are all the details of formatting date/time:
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 |
Time constraints field:
{
"hours": {
"min": 1,
"max": 15,
"step": 3
},
"minutes": {
"min": 10,
"max": 30,
"step": 20
}
}
Remember, all those constraints affect only web-pages components and user input in the platform. Scenarios and API-calls aren't limited.
Dates are stored in UTC. If you choose use user's local timezone in settings, interface of the platform and of an app based on web-page builder will get the user's timezone from his browser. But if you deal with the date in scenarios, you have to handle timezone manually, using
moment({{your_date}}).zone(Z).format();, where Z for example -3, or +10Last modified 1yr ago