This setting defines how to display the date and time of an event. When empty, the default format will be the date and time of the event according to the standards of the language in effect. However, it may be important to change this format for an event. For example if we want to indicate a duration for example from 17h to 20h or even for an event that lasts more than one day (Saturday and Sunday June 14th and 15th, 2019). It is also possible that your activity sells tickets that are valid every day of the summer and in this case we can not indicate a specific date so we can put "Summer 2019" for example as text.


All events in an activity must have a date and time that corresponds to its entry in the activity calendar. This moment generally corresponds to the date of the beginning of the event, but in the case of selling tickets that are valid for a long period of time, the date will be the end date of the activity - the end of a season for example. The ticket office uses the date of events to decide whether or not to include them in the list of available events to sell tickets. Note that there are some settings to control which events are shown or not in the ticket office, but in general, all upcoming events are included. For this reason a seasonal event must use the closing date and not the date of opening, because right after the opening date, the ticket office would not include the single event anymore.


The When setting is mainly used for the ticketing styles "event list" and "ticket list", because for the other styles "calendar and list of days", it is really the date and time of the events that are used for display in the ticket office because of the specialized interface used for this kind of recurring activity. On the other hand, even for these styles, the setting makes it possible to decide how to display the moment of the event when communicating with the client. For the "event list" style, each event is displayed individually and may have its own When setting if required.


The When setting allows you to enter text and combine the date and time of the event into a specific format. The use of special formatting codes makes it possible not to have to enter the precise moment of the event in the When, but to use its date and time as programmed in the calendar. Thus we can change the time for example without having to change this setting and especially to generalize how to present the When for multiple events with a single shared setting.


To insert portions of the date and time it is necessary to use a notion that uses a special syntax:


{when:format} or {whenCap:format


It's the format that decides what portion of the date and time you want to display. The difference between when and whenCap is simply that whenCap will uppercase the first letter of the text produced by the format. You can insert as many "when" syntax in the setting as required.


format consists of one or more formating codes explained in the following table. You can add literal text between codes as needed, but you must put this text between "" so that it is not interpreted as formatting codes. You can also completely avoid putting literal text in the format and instead put several {when:} sections and any text between these codes, which may be simpler.


format codes 
DescriptionExamples and Notes
d
The day of the month, from 1 through 31

dd
The day of the month, from 01 through 31

ddd
The abbreviated name of the day of the week
Mon. Tue. Wed. ...
dddd
The full name of the day of the week
Monday Tuedays ...
h
The hour, using a 12-hour clock from 1 to 12

hhThe hour, using a 12-hour clock from 01 to 12

HThe hour, using a 24-hour clock from 0 to 23

HHThe hour, using a 24-hour clock from 00 to 23

mThe minute, from 0 through 59

mmThe minute, from 00 through 59 
MThe month, from 1 through 12

MMThe month, from 01 through 12

MMM
The abbreviated name of the month
Jan. Feb. ...
MMMMThe full name of the month
January February ...
sThe second, from 0 through 59

ssThe second, from 00 through 59 
tThe first character of the AM/PM designator
A or P
ttThe AM/PM designator
AM or PM
yThe year, from 0 to 99 - last two digits

yyThe year, from 00 to 99 - last two digits

yyyyThe year as a four-digit number
2019
:The time separator. Depends on language.
typically: but could also be .
/The date separator. Depends on language.
/ - .
"string"
'string'
Literal string delimiter
h "hour" -> will output 10 hour for instance
\Single character literal delimiterSimilar to "" but only works for the next character that follows



Here are some sample settings for an event on June 6, 2019 at 1:30 pm


Réglage QuandDescriptionExemples et Notes
{when:dddd, MMMM dd, yyyy HH'h'mm}
Long version of a date and time. This is the default value of When when not specified.
Tuesday, June 6, 2019 13h30
{when:ddd, MMMM dd, yyyy HH'h'mm}
Shorter version of the day of weekTue., June 6, 2019 13h30
{when:MMMM dd, yyyy HH'h'mm}
Without the day of the weekJune 6, 2019 13h30
{when:HH'h'mm}
Hours and minutes separated with h13h30
{when:HH:mm}
Hours and minutes separated with the current language separator
13:30 (or other based on locale)



{when:dddd, MMMM dd, yyyy} 5 to 7
Date, but the time is literally written because you can not automate it with a code.
Tuesday, June 6, 2019 5 to 7
Weekend of {when:d MMMM yyyy} from 9h to 4pmHere the date of the event must be Friday or Saturday to mark the beginning of the weekend.

2019 Season
Summer 2019
Winter 2019
No reference to the date and time of the event. Ticket sales case usable at any time during a period of time.