1. Introducing the Editor
2. Some ticket template examples and important information
Thermal ticket
A4/Print@home
Mobile
Editor basic functions
Properties of a text field
Style tab
2D barcodes
Visibility options
Variable sets
Important fiscal information (Italy)
4. Create a model and link it to the product
...
The template editor allows you to design ticket templates:
From a new template: New
From an existing model: Copy or Import
For thermal printers: for Boca format tickets
For pdf tickets: for A4/print@home formats
For Mobile-pdf: for tickets downloaded to a mobile phone
The editor works with a set of variables explained in List of variables page in the ticket layout editor.
When a modification of the templates is needed during the season, it is recommended:
to copy the model used in production
to make all the desired changes
test the new model using variable sets
to associate the new model to the product
to archive the old model
| Anchor | ||||
|---|---|---|---|---|
|
Thermal ticket
The black bar is on the right below, when looking at the printer from the front. It is placed by the printer (it should not be indicated on the template sent to the printer).
...
Validation process:
NB The print proof from the printer (in scaled PDF) must be validated by SECUTIX before ordering.
Paperless A4 ticket
...
1 - Ticket section: contains all the necessary information and the barcodes
...
4 - Footer section: for printing quality checks, with barcode content
...
It is also possible to deliver a single image, of size 960x423, which will be cut into three parts by SECUTIX.
Mobile ticket
Ticket background: 470x611 pixels, with a white area for the barcode.
...
| Anchor | ||||
|---|---|---|---|---|
|
Editor basic functions
Add a new text-type field
Add a new image-type field
Add a new barcode-type field
Variable set selection
Field selection (by clicking on it or via the list of fields)
View properties of the selected field
Properties of a text field
A text field can have different properties:
Parameter: selection of one of the variables
Static: text input
Composed: entering a text and selecting variables (ex. date and time).
Multilingual: display in French or English depending on the language of the institution or the preferred language of the contact
Formulas can be entered in a compound field (to combine several parameters and static text) are the following:
Each parameter is formatted as follows: ${parameter;attribute list}
The attribute list is optional. It can contain one or more attributes separated by semicolons.
min=xxx → allows you to truncate the beginning of the parameter. xxx is the index of the first character of the parameter to keep.
max=xxx → allows you to truncate the end of the parameter. xxx is the index of the last character of the parameter to keep.
upperCase → converts the parameter to uppercase.
lowerCase → transform the parameter to lowercase.
format=xxx → defines the format of a number or a date (see tables below, or use the SimpleDateFormat parameters).
language=CodeISO → for dates, it defines the language in which the date will be formatted
Date formats | Number formats | ||
|---|---|---|---|
y | Year | 0 | Number |
M | Month | # | Numbers |
d | Day of the month | , | Thousands separator |
E | Day of the week | . | Decimal separator |
H | Hour | ||
m | Minute | ||
s | Second |
In some cases tables are transmitted in the following format:
Contact_hostCriterion;array_code=[PerPref='Hypologica13';Hall='Halle14';Stand='A52']
In the case of promotions with a single-use code as well as during the distribution of tickets, it is possible to display on the ticket the name of the structure which invites, as well as the contact criteria of this structure.
Example of display on the ticket:
...
This will display the code in groups of 4 characters, separated by dashes, like 1234-ABCD-5678-EFAB
Style tab
...
To obtain a good alignment of the different fields positioned on the layout, we recommend that you fix their position in the Style tab.
...
To put a 2D barcode on a template, create a barcode-type field, and use a compound value and enter:
${Ticket_barcode;min=14}
Choose the type of barcode in the field just next to the value. This composite value is needed to truncate the parameter that contains encoding information.
...
A field can only be made visible if it meets certain conditions.
A condition is the association of a parameter, a operator and a given value.
The value entered must exactly match the actual value of the parameter in the system (also case sensitive).
For the "like" sign, the value must be surrounded by * For example with the condition $Tarif_nomPublic like *invit*, the field will only be displayed if the ticket price contains invite (es. guest, invitation, special invite...).
The character ? can be used as a wildcard (e.g. "AB??" will work for "AB01" or "AB23" but not "AB2" or "AB123").
The "matches" sign allows you to write a regular expression (regex).
...
Variable sets
The sets of variables are used to test ticket models by replacing the name of the parameters with texts
Tip: Create enough variable sets to test each condition
Back in the editor tool, select the set of variables created and print a specimen ticket
...
Important fiscal information
According to each specif national regulations, some fields must be kept in ticket template.
| Info | |||||||
|---|---|---|---|---|---|---|---|
| title | Italian Certification | Specific requirements
Single tickets (specific fields for single entries and general fiscal fields)  |
Italian clients using a Certified S-360 license will need to keep all the following fields and conditions in the ticket templates (both thermal and digital) as provided with the licence 
Name | Custom value | Type | Visibility | Condition |
|---|---|---|---|---|
01_EventTitle_M | EVENTO: |
...
${ita_title} | Text |
...
 | |
02_EventDateTime_M | DATA |
...
EVENTO: |
...
${ita_performanceDate} |
...
${ita_performanceTime} | Text |
...
 | |
03_Space_M | LOCALE: |
...
${ita_spaceName} | Text |
...
 | |
04A_PriceN_M | PREZZO: |
...
${ita_grossAmount} |
...
${Amount_currency} |
...
- |
...
PREVENDITA: |
...
${ita_presaleAmount} |
...
${Amount_currency} |
...
- |
...
TOTALE: |
...
${ita_totalAmount} |
...
${Amount_currency} | Text |
...
 |
...
 | |
04B_PriceBF_M | PREZZO: |
...
0,00 |
...
${Amount_currency} |
...
- |
...
PREVENDITA: |
...
0,00 |
...
${Amount_currency} |
...
- |
...
TOTALE: |
...
0,00 |
...
${Amount_currency} | Text |
...
 |
...
 | |
05A_FigurativeF_M | IMP.FIG.: |
...
${ita_figurativeAmount} |
...
${Amount_currency} |
...
- |
...
PREV.FIG.: |
...
${ita_presaleAmount} |
...
${Amount_currency} |
...
- |
...
TOT.FIG.: |
...
${ita_totalAmount} |
...
${Amount_currency} | Text |
...
 |
...
 | |
05B_FigurativeB_M | BIGLIETTO |
...
ABBONAMENTO |
...
- |
...
CODICE: |
...
${ita_sstkCode} |
...
- |
...
PROGRESSIVO: |
...
${ita_sstkProgressiveNb} |
...
- |
...
RATEO: |
...
${ita_totalAmount} |
...
${Amount_currency} | Text |
...
 |
...
 | |
06_EventType_M | TIPO |
...
EVENTO: |
...
${ita_eventType} |
...
- |
...
${ita_eventTypeDescription} | Text |
...
| |
07A_SectorNoSeat_M | ORDINE: |
...
${ita_seatCategoryCode} |
...
- |
...
${ita_seatCategoryName} | Text |
...
|
...
 | |
07B_SectorSeat_M | ORDINE: |
...
${ita_seatCategoryCode} |
...
- |
...
FILA |
...
${Seat_row} |
...
- |
...
POSTO: |
...
${Seat_nb} | Text |
...
|
...
 | |
08_Tariff_M | TIPO |
...
TITOLO: |
...
${ita_tariffCode} |
...
- |
...
${ita_tariffName} |
...
${ita_vatPrepayment} | Text |
...
| |
09_Organizer_M | ORGANIZZATORE: |
...
${ita_organizer} |
...
- |
...
C.F./P.I. |
...
${ita_organizerFiscalCode} | Text |
...
| |
10_Owner_M | TITOLARE: |
...
${ita_ownername} |
...
- |
...
C.F./P.I. |
...
${ita_ownerFiscalCode} | Text |
...
| |
11_FiscalData1_M | SISTEMA: |
...
${ita_ticketingSystem} |
...
- |
...
CARTA: |
...
${ita_smartCardId} |
...
- |
...
PROGRESSIVO: |
...
${ita_progressiveNumber} | Text |
...
| |
12_FiscalData2_M | SF: |
...
${ita_fiscalSeal} |
...
- |
...
EMISSIONE: |
...
${ita_issuingDate} |
...
${ita_issuingTime} |
...
- |
...
PV: |
...
${ita_posCode} | Text |
...
| |
13_ID_M | FILE: |
...
${Operation_fileId} |
...
- |
...
CODICE: |
...
${Ticket_taxNumber} |
...
- |
...
BARCODE: |
...
${Ticket_barcodeText} | Text |
...
| |
Barcode |
...
 | Barcode |
...
|
| Info |
|---|
Season tickets (specific fields for Cards "Abbonamenti padre". General fiscal fields as above) |
Name | Custom value | Type | Visibility | Condition |
|---|---|---|---|---|
01_SeasonTicket1_M | ABBONAMENTO: |
...
${Product_externalName} |
...
- |
...
CODICE: |
...
${ita_sstkCode} |
...
- |
...
PROGRESSIVO: |
...
${ita_sstkProgressiveNb} | Text |
...
| |
02A_SeasonTicket2_M | EVENTI: |
...
${ita_nbEventsIncluded} |
...
- |
...
TURNO: |
...
${ita_sstkType} |
...
- |
...
VALIDITÀ: |
...
${ita_validityDate} | Text |
...
|
...
 | |
02B_SeasonTicket2_M | TITOLO |
...
OPEN |
...
- |
...
EVENTI: |
...
${ita_nbEventsIncluded} |
...
- |
...
TURNO: |
...
${ita_sstkType} |
...
- |
...
VALIDITÀ: |
...
${ita_validityDate} | Text | |
...
 |
| Info |
|---|
| Anchor | ||||
|---|---|---|---|---|
|
...
Within the model, the previously created template is associated with a ticket type, a material family and a ticket support. More info in Organization | Tools | Ticket models
...
After having validated them, it is possible to associate these models to the products. For example, in the catalog module of the organization context, the model can be associated with an event. 
