...
Overview
This new feature is to improve the Distribution History to show all the cultural contact changes initiated in TIXNGO. It is activated through a aims to improve the tracability of Ticket Ownership Changes in S-360 with a broader and more visible more approach, by reusing the existing S-360 built-in feature of Cultural Contact & Distribution.
Once enabled, the Retrieve Ticket Status function (aka Feedback Interface) will make sure that all TIXNGO Ticket Ownership Changes are materialized in S-360 with new Cultural Contact and a proper Distribution History.
Prerequisites
Systematically inject tickets to the cultural contact (rather than last known mobile owner)
To ensure that while being injected, the function skip the step to find the current mobile owner and inject systematically them to the cultural contact, you must use overlaySpectatirDetailsWithLastOwner=true and TIXNGO_LIFECYCLE_MODE=lifecycle. (Both are activated by default)
Activate Contact Creation & Distribution
To activate this feature, a new custom parameter 'enableTicketDistributionToCulturalContact' has been introduced, and it will behave as follows:
- enableTicketDistributionToCulturalContact=true
...
- → Contact creation and Distribution is ACTIVE
- enableTicketDistributionToCulturalContact=false
...
- → Contact creation and Distribution is NOT ACTIVE
- enableTicketDistributionToCulturalContact does not appear on the custom parameter box in Interface General Screen
...
Prerequisites
It is important to make sure that also Lifecycle is active, so add also TIXNGO_LIFECYCLE_MODE=lifecycle parameter in the custom parameter box in TIXnGO Interface General Screen.
The first step is Choose TIXnGO as a shipment mode and Inject the ticket.
When the ticket is on TIXnGO system, the end customer will be able to transfer the ticket to someone else, being or not a contact in S360.
How does Distribution history works?
When retrieving ticket status, a new screen with this action is created in ticket information, the ticket is in Pending Transfer status until the recipient opens the app and accept the ticket that has been transferred. The timeframe to accept the ticket is 1 hour, if the recipient does not accept the ticket within an hour, the transferred will be cancelled and no contact will be created.
If the contact is already created, the ticket is automatically details of the recipient even if ticket is still pending transfer
If the contact is not in S360, a new contact with Dummy details will be created using the email of the recipient of the ticket.
When the contact accept the ticket in TIXnGO, the new contact will be created with all the information:
To get latest status, retrieve ticket status will need to be executed again so that S360 receives latest information.
...
- → Contact creation and Distribution is NOT ACTIVE
How Contact Sync works?
On the feedback interface side, ground rules are :
- Do not create duplicated contact, for distribution reuse an existing one with an internet account.
- Only update temporary contacts.
In other words, the feedback interface will :
- check first if a contact with this email address exist in S-360
If it’s a “normal” contact (ie with real first & last name), contact WON’T be updated.
If it’s a “temporary” contact (ie named Pending CREATION), the temporary contact will be updated according to the mapping provided below
- if it does not exist create one → If ticket status is "PENDING_TRANSFER", the feedback interface only get the recipient e-mail address. Therefore a "temporary" contact named Pending CREATION will be created using recipient e-mail address.
- create a new entry in the distribution history to mimic the transfer performed in TIXNGO.
Ui expand | ||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||
|
How Distribution history works?
Distribution history contains the list of ownership changes applied to a ticket, ie the change of the Cultural Contact.
Each history entry must answer the classical questions Who, What, When and provide context to the distribution (Action, Contacts involved [old and new contact], Status of the Distribution)
Mapping
TIXNGO Lifecycle Status | Ticket Cultural Contact | Distrib > Old Contact | Distrib > New Contact | Distrib > Action | Distrib > Status |
---|---|---|---|---|---|
PENDING_TRANSFER | (No changes on cultural contact) | Cultural Contact of the Sender | Cultural Contact of the Recipient | Distribute | PENDING |
FAILURE | (No changes on cultural contact) Cultural Contact of the Sender | Cultural Contact of the Sender | Cultural Contact of the Recipient | Distribute | CANCELLED |
TRANSFERRED | Cultural Contact of the Recipient | Cultural Contact of the Sender | Cultural Contact of the Recipient | Distribute | CONFIRMED |
Transitions
Ui expand | ||||
---|---|---|---|---|
| ||||
No cultural contact change at ticket level. New "Pending" line in the distribution history with found Contact.
|
Ui expand | ||||
---|---|---|---|---|
| ||||
No cultural contact change at ticket level. New "Pending" line in the distribution history with "Temporary Contact".
|
Ui expand | ||||
---|---|---|---|---|
| ||||
No cultural contact change at ticket level. New "Pending" line in the distribution history with "Temporary Contact".
|