1. Introducing the Editor
2. Some ticket template examples and important information
4. Create a model and link it to the product
The template editor allows you to design ticket templates:
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:
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).
The black bar area (in gray below) should contain nothing but the black bar!
The barcode print area must be plain (possibly light-coloured) with a 3mm margin on each side.
Paper quality: Thermosensitive 300DPI - Rapid revelation - 190 Microns – 175 Grams
Validation process:
NB The print proof from the printer (in scaled PDF) must be validated by SECUTIX before ordering.
1 - Ticket section: contains all the necessary information and the barcodes
2 - General conditions: an image (1530x276 pixels) containing the legal aspects
3 - Free section: an image (1530x1130 pixels) containing information about the venue, entrance, etc.
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.
Ticket background: 470x611 pixels, with a white area for the barcode.
Second page: the right microstructure of the A4 ticket is generally taken, but another image (with the same dimensions) can also be provided.
A text field can have different properties:
Formulas can be entered in a compound field (to combine several parameters and static text) are the following:
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:
"You are invited by SECUTIX which is located in Hall 14 at stand A52."
If you want to display a nice looking voucher code, you can use this value in a custom field on the template:
${Voucher_identifier;max=4;upperCase}-${Voucher_identifier;min=4;max=8;upperCase}-${Voucher_identifier;min=8;max=12;upperCase}-${Voucher_identifier;min=12;max=16;upperCase} ${Voucher_identifier;min=16;upperCase}
This will display the code in groups of 4 characters, separated by dashes, like 1234-ABCD-5678-EFAB
To obtain a good alignment of the different fields positioned on the layout, we recommend that you fix their position in the Style tab.
This tab is also used to specify the size of the field and the font used.
A Visible edge check box lets you draw a frame around a field.
The Alignment drop-down menu is used to indicate the position of the text in the field (left, right, center). The Auto Align option (thermal tickets only) scales the text to the width of the field.
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).
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
According to each specif national regulations, some fields must be kept in ticket template.
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 Overheads or any other commission fee must not be included in certified tickets: such amounts should be invoiced by they organization outside of the ticketing platform. Single tickets (specific fields for single entries and general fiscal fields)
Season tickets (specific fields for Cards "Abbonamenti padre". General fiscal fields as above)
|
Once the template has been created and tested, it is associated with a model in the Tools module of the Organization context
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.