Introduction to V4 Notification Content Management
Instead of customizing native TIXNGO Notifications content directly from the Multilingual screen, content will now be managed from the Communication Templates dedicated Notification's screen.
New Notifications templates list view
Overview
The list of the default Notification Templates will be now visible in the Notification tab.
Closer look on an Notification template row
To ease understanding during template’s customization Notification Templates are now supporting extra contextual information.
Email template | Breakdown | Description |
|---|---|---|
 | Notification sent to the ticket owner when a ticket has been deleted. (failover option for non-supported invalidation reason) | User-friendly description of the notification’s purpose. |
push.ticket.deleted | Standardized notification template key following the | |
 | Ticket Deletion | Straight to the point Context of the notification. |
 | DEFAULT | Audience targeted by this notification template, here DEFAULT. |
New V4 Notification Templates
We leveraged the new communication engine in V4 to rename template keys and streamline notification configuration by reducing the number of templates.
Context | V3 Notification Template Key | New Key |
|---|---|---|
Notification sent to the ticket owner when a ticket has been injected. | notification.inject | push.ticket.injected |
Notification sent to the ticket owner when a ticket has been updated. | notification.update.ticket | push.ticket.updated |
Notification sent to the ticket owner when a ticket has been deleted (failover option for non-supported invalidation reason) | notification.deleted | push.ticket.deleted |
Notification sent to the ticket owner when a ticket has been deleted with the reason REFUND | notification.deleted.<S360status> | push.ticket.deleted.refund |
Notification sent to the ticket owner when a ticket has been deleted with the reason REPRINT | notification.deleted.<S360status> | push.ticket.deleted.reprint |
Notification sent to the ticket owner when a ticket has been deleted with the reason RESEAT | notification.deleted.<S360status> | push.ticket.deleted.reseat |
Notification sent to the ticket owner when a ticket has been deleted with the reason RESALE_PENDING | notification.deleted.<S360status> | push.ticket.deleted.resale.pending |
Notification sent to the ticket owner when a ticket has been deleted with the reason RESALE_CANCELLED | notification.deleted.<S360status> | push.ticket.deleted.resale.cancelled |
Notification sent to the ticket owner when a ticket has been deleted with the reason RESOLD | notification.deleted.<S360status> | push.ticket.deleted.resale.resold |
Notification sent to the ticket owner when a ticket has been deleted with the reason DISTRIBUTION | notification.deleted.<S360status> | push.ticket.deleted.distribution |
Notification sent to the ticket owner when a ticket has been deleted with the reason THEFT_LOSS | notification.deleted.<S360status> | push.ticket.deleted.theft_loss |
Notification sent to the ticket owner when a ticket has been deleted with the reason BLACKLIST | notification.deleted.<S360status> | push.ticket.deleted.blacklist |
Notification sent to the transfer's recipient when a ticket transfer has been initiated. Recipient is ALREADY registered in TIXNGO. | notification.deleted.<S360status> | push.ticket.transfer.initiated |
Notification sent to the transfer's initiator, when the transfer's recipient accepted explicitly or implicitly the incoming tickets. | notification.acknowledge.accepted | push.ticket.transfer.accepted |
Notification sent to the transfer's initiator, when the transfer's recipient rejected the incoming tickets. | notification.acknowledge.rejected | push.ticket.transfer.rejected |
Notification sent to the transfer's recipient when the ticket's transfer has been cancelled by the sender. | notification.cancel | push.ticket.transfer.cancelled |
Notification sent to the transfer's recipient when a ticket transfer has been automatically cancelled after X days. | notification.information.automaticallycancel | push.ticket.transfer.autocancelled |
Create Notification Template
Notification templates cannot be created manually; they are introduced automatically by new features.
Edit Notification Template
By clicking on the inline Edit button of an existing template, you’ll be redirected to a new dedicated screen to edit your Notification Template.
From this screen, you can either :
Button | Action |
|---|---|
| Edit the template for a specific language |
| Preview the template for a specific language |
| Add a new language and customize the template |
© TIXNGO 2023 - Login