Info: This article is work in progress and subject to change.
The Format option on Date and Datetime fields uses a Moment.js-style format string to control how the value is displayed to the user. The underlying value remains a real date — only the rendering changes.
This appendix is the working reference for the format tokens. For the conceptual material on Date and Datetime fields, see 05a — Fields reference.
Year
Token
Output
Example
YYYY
Four-digit year
2026
YY
Two-digit year
26
Month
Token
Output
Example
M
Month number
5
MM
Month number, zero-padded
05
MMM
Short month name
May
MMMM
Full month name
May
Day of month
Token
Output
Example
D
Day of month
7
DD
Day, zero-padded
07
Do
Day with ordinal
7th
Day of week
Token
Output
Example
d
Day-of-week number, 0 = Sunday
4
dd
Two-letter day-of-week
Th
ddd
Short day-of-week
Thu
dddd
Full day-of-week
Thursday
Hour
Token
Output
Example
H
24-hour
14
HH
24-hour, zero-padded
14
h
12-hour
2
hh
12-hour, zero-padded
02
Minute and second
Token
Output
Example
m
Minute
5
mm
Minute, zero-padded
05
s
Second
9
ss
Second, zero-padded
09
AM/PM
Token
Output
Example
a
Lowercase
am, pm
A
Uppercase
AM, PM
Common formats
Format string
Output
DD MMM YYYY
07 May 2026
dddd, MMMM Do YYYY
Thursday, May 7th 2026
dddd, MMMM Do YYYY, h:mm:ss a
Thursday, May 7th 2026, 2:15:30 pm
YYYY-MM-DD
2026-05-07
YYYY-MM-DD HH:mm
2026-05-07 14:15
MM/DD/YYYY
05/07/2026
DD/MM/YYYY
07/05/2026
MMM Do, YYYY
May 7th, 2026
Choosing a format
A few habits keep the format readable:
Use the format your audience is used to. A panel deployed in the United States typically uses MMM Do YYYY or MM/DD/YYYY; one deployed in Europe typically uses DD MMM YYYY or DD/MM/YYYY. Match the locale, not the developer’s preference
Be explicit about month names.MMM (May) is harder to misread than MM (05) in mixed-locale teams
Use 24-hour for technical timestamps, 12-hour with AM/PM for human-readable ones.HH:mm for log-style displays, h:mm a for “what time is the meeting”
A note on time zones
The Workflow Assistant displays dates in the user’s browser-local time zone. The format string controls the rendering; it does not control the time zone. If your workflow needs explicit time-zone handling, the Configurator’s current version does not expose a time-zone option — values are stored and rendered in the user’s local zone.
Note: If you need time-zone-aware behaviour (different zones for different audiences, for example), this is a feature gap to flag with your support representative. The current best practice is to use Datetime fields where time-zone matters and to remind users in the Hint which zone the value represents.
Comments
0 comments