Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • 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

...

  • 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

HHour

mMinute

sSecond


In some cases tables are transmitted in the following format:

...

"You are invited by SECUTIX which is located in Hall 14 at stand A52."

Voucher code

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

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.

...

Info
titleItalian Certification | Specific requirements

(warning) Italian clients using a Certified S-360 license will need have to keep all the following fields and conditions in the ticket templates (both thermal and digital) as provided with the licence (warning)

(warning) 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.(warning)

Single tickets (specific fields for single entries and general fiscal fields)


NameCustom valueTypeVisibilityCondition
01_EventTitle_M
EVENTO: ${ita_title}
Text

Image Modified


02_EventDateTime_M
DATA EVENTO: ${ita_performanceDate} ${ita_performanceTime}
Text

Image Modified


03_Space_M
LOCALE: ${ita_spaceName}
Text

Image Modified


04A_PriceN_M
PREZZO: ${ita_grossAmount} ${Amount_currency} - PREVENDITA: ${ita_presaleAmount} ${Amount_currency} - TOTALE: ${ita_totalAmount} ${Amount_currency}
Text

Image Modified

Image Modified

04B_PriceBF_M
PREZZO: 0,00 ${Amount_currency} - PREVENDITA: 0,00 ${Amount_currency} - TOTALE: 0,00 ${Amount_currency}
Text

Image Modified

Image Modified

05A_FigurativeF_M
IMP.FIG.: ${ita_figurativeAmount} ${Amount_currency} - PREV.FIG.: ${ita_presaleAmount} ${Amount_currency} - TOT.FIG.: ${ita_totalAmount} ${Amount_currency}
Text

Image Modified

Image Modified

05B_FigurativeB_M
BIGLIETTO ABBONAMENTO - CODICE: ${ita_sstkCode} - PROGRESSIVO: ${ita_sstkProgressiveNb} - RATEO: ${ita_totalAmount} ${Amount_currency}
Text

Image Modified

Image Modified

06_EventType_M
TIPO EVENTO: ${ita_eventType} - ${ita_eventTypeDescription}
Text

Image Modified


07A_SectorNoSeat_M
ORDINE: ${ita_seatCategoryCode} - ${ita_seatCategoryName}
Text

Image Modified

Image Modified

07B_SectorSeat_M
ORDINE: ${ita_seatCategoryCode} - FILA ${
ita
Seat_
seatCategoryName
row} - POSTO: ${
ita
Seat_
seat
nb}
Text

Image Modified

Image Modified

08_Tariff_M
TIPO TITOLO: ${ita_tariffCode} - ${ita_tariffName} ${ita_vatPrepayment}
Text

Image Modified


09_Organizer_M
ORGANIZZATORE: ${ita_organizer} - C.F./P.I. ${ita_organizerFiscalCode}
Text

Image Modified


10_Owner_M
TITOLARE: ${ita_ownername} - C.F./P.I. ${ita_ownerFiscalCode}
Text

Image Modified


11_FiscalData1_M
SISTEMA: ${ita_ticketingSystem} - CARTA: ${ita_smartCardId} - PROGRESSIVO: ${ita_progressiveNumber}
Text

Image Modified


12_FiscalData2_M
SF: ${ita_fiscalSeal} - EMISSIONE: ${ita_issuingDate} ${ita_issuingTime} - PV: ${ita_posCode}
Text

Image Modified


13_ID_M
FILE: ${Operation_fileId} - CODICE: ${Ticket_taxNumber} - BARCODE: ${Ticket_barcodeText}
Text

Image Modified


Barcode

Image Modified

Barcode

Image Modified


Season tickets (specific fields for Cards "Abbonamenti padre". General fiscal fields as above)

NameCustom valueTypeVisibilityCondition
01_SeasonTicket1_M
ABBONAMENTO: ${Product_externalName} - CODICE: ${ita_sstkCode} - PROGRESSIVO: ${ita_sstkProgressiveNb}
Text

Image Added


02A_SeasonTicket2_M
EVENTI: ${ita_nbEventsIncluded} - TURNO: ${ita_sstkType} - VALIDITÀ: ${ita_validityDate}
Text

Image Added

Image Added

02B_SeasonTicket2_M
TITOLO OPEN - EVENTI: ${ita_nbEventsIncluded} - TURNO: ${ita_sstkType} - VALIDITÀ: ${ita_validityDate}
Text

Image Added

Image Added


Anchor
#Model
#Model
4. Create a model and link it to the product

...

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.