Page tree

Versions Compared

Key

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

Overview

This new feature 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

...

TIXNGO Lifecycle Mode

...


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 → Contact creation and Distribution is NOT ACTIVE

How

...

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 

Image Removed

Image Removed

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.

Image Removed

Image Removed

Image Removed

When the contact accept the ticket in TIXnGO, the new contact will be created with all the information:

Image Removed

To get latest status, retrieve ticket status will need to be executed again so that S360 receives latest information.

Image Removed

Image Removed

...

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 :

  1. 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

  2. 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.
  3. create a new entry in the distribution history to mimic the transfer performed in TIXNGO.
UI Expand
titleMapping


Contact field Lifecycle Palyoad field
Title (individualTitle)spectatorDetails.title
First Name (individualFirstname)spectatorDetails.firstName
Last Name (individualLastname)spectatorDetails.lastName
Birthday (individualBirthdate)spectatorDetails.dateOfBirth
Mail (email)spectatorDetails.email
Nationality (individualCountryCode)spectatorDetails.nationality 
Passport/ID (individualIdNumber)spectatorDetails.idCardNumber
Mobile Phone (cellPhoneNumber)spectatorDetails.phoneNumber
Country (countryCode)spectatorDetails.residenceCountry
Language (individualPreferredLanguage)spectatorDetails.language
Accept communication from institution by email (CNIL_O / INSTITUTION)spectatorDetails.organizerSpectatorPreference.allowPromoEmail
Accept transmission of elec. coordinates from 3P (CNIL_T / THIRD_PARTY)spectatorDetails.organizerSpectatorPreference.allowThirdPartyEmail


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 StatusTicket Cultural ContactDistrib > Old ContactDistrib > New ContactDistrib > ActionDistrib > Status
PENDING_TRANSFER

(No changes on cultural contact)
Cultural Contact of the Sender

Cultural Contact of the SenderCultural Contact of the RecipientDistributePENDING

FAILURE 
FAILURE_TRANSFER

(No changes on cultural contact)
Cultural Contact of the Sender
Cultural Contact of the SenderCultural Contact of the RecipientDistributeCANCELLED
TRANSFERRED Cultural Contact of the RecipientCultural Contact of the SenderCultural Contact of the RecipientDistributeCONFIRMED
Transitions
UI Expand
titleAfter a transfer is initiated (Contact exists in S-360)

No cultural contact change at ticket level. New "Pending" line in the distribution history with found Contact.

Ticket detailsTicket distribution history

Image Added

Image Added



UI Expand
titleAfter a transfer is initiated (Contact does not exist in S-360)

No cultural contact change at ticket level. New "Pending" line in the distribution history with "Temporary Contact".

After contact creationTicket distribution history

Image Added

Image Added



UI Expand
titleAfter a successful transfer distribution

No cultural contact change at ticket level. New "Pending" line in the distribution history with "Temporary Contact".

Ticket detailsTicket distribution history

Image Added

Image Added