The When setting is used to show when the event occurs to your client whether it's in the ticket office, confirmation email or tickets. Your events are added to the portal calendar of your activity by assigning a fixed time to it but this is for programming purposes in the calendar, the event may not be exactly at that time or it may span a period. The needs are quite large so Tixigo offers a flexible way to present the When information to your clients using this setting.

An empty value for When will use the default format and show 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 cannot 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.

Activities based on the "List of Events" and "List of Tickets" display style only rely on the When setting to decide how to display the information. For "List of Events" style each event has its own When setting so each one can be customized or rely on the activity's When setting. "List of Tickets" is normally used for a single event and has its When setting. If you have more than one event then they all share the same When setting.

"Calendar" and "List of days" styles are used for repeating events by presenting a list of available times the event is available for a given day selected in a calendar or a short list of days. The list of time for the day is presented as 3 columns of text and the centre column is the primary one where the time is shown. By default the time is shown using a fix format which can depend on your country or even the template used by the activity but in general it would show the time as HHhMM (ex. 10h30). Tixigo offers two ways to customize how to show the time either at the price list level or at the event level by using the "Time in Ticket Office" field of each event. You could display the time along with some text and even split the information on more than one line. Since the time is handled separately from the date for those two styles of activity, the event When must use a special syntax to split the date and the time too. But this is important only if you want to change the default behaviour of the When formatting as in this example for instance:

You have 2 periods per day for your activity and one will show "Morning 9h to11h" for the event set at 9h in the portal calendar and the other "Afternoon 13h to 14h" for the event set at 13h. If you use the default When then it will show the date and time so using 9h00 and 13h00 but this is misleading and you would rather want to show the date followed by "Morning 9h to11h" or "Afternoon 13h to 14h". For this situation you would want to use the special {time} code in the When setting and the {when:} code to show the date part. 

When setting:

The When setting allows you to combine the date and time of an event with text in a specific format. The use of special formatting codes means that you do not have to enter the precise moment of the event in the When in fixed text form such as "Friday March 10 at 2 pm" which is suitable if you have only one event. However, if you change the time of an event later (before the tickets go on sale) or if you copy an event to a later date or when using repeating events, it is impractical and even risky to use a fixed text which serves only one event. The When setting allows you to make the When content dynamic according to the date and time of your activity's events.

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}  or {time}

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.

The {time} code is specific to "Calendar" and "List of Days" styles. It will show the first line of text of the centre column that is presented to your clients in the ticket office. If showing the event's time is enough then there is no need to use a special When setting, the default one will work.

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
The day of the month, from 1 through 31

The day of the month, from 01 through 31

The abbreviated name of the day of the week
Mon. Tue. Wed. ...
The full name of the day of the week
Monday Tuedays ...
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

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
:The time separator. Depends on language.
typically: but could also be .
/The date separator. Depends on language.
/ - .
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

When SettingsDescriptionExemples 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:dddd, MMMM dd, yyyy}
Date onlyTuesday, June 6, 2019
{when:ddd, MMMM dd, yyyy}
Date only with short version of day of the weekTue., June 6, 2019
Hours and minutes separated with h13h30
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.
{when:ddd, MMMM dd, yyyy} {time}
Date and time when using custom time format for Calendar and List of Days styles.