|
Solution
The B2B distribution features are powerful to allow your B2B customers to autonomously distribute their tickets. However, mistakes are human and correcting them, whether a wrong or misspelled email, is now possible using the take back feature. If a injected secure mobile ticket has not yet been downloaded on a phone, it remains available to be taken back.
Known issue: currently if an injected ticket has ticket holder details set, it cannot be taken back. This restriction will be lifted in the next major release. |
Getting started
In the sales channel list of the organization context, open the "Point of sales" screen of a B2B sales channel and click on the "Internet Parameters" tab of "Characteristics" screen. In the "Distribution" panel, there are two new paramters:
- "Allow taking back the injected mobile ticket that has not been downloaded" checkbox: this parameter allows activating the feature on that point of sales. Note that unchecking it does not prevent the regular take back feature available for other types of tickets or secure mobile ticket not yet injected.
- "Assign the taken back ticket to a new shipment mode" drop-down: this optional parameter allows defining the shipment mode to which the ticket being taken back should be assigned. Indeed, if the ticket remains in the same shipment mode, it risks being injected again without leaving the opportunity to be redistributed.
Note that behind the scenes, a new ticket will be created to invalidate the wrongly injected ticket. The invalidation reason used for this process will be "MOBILE_TAKE_BACK". It is thus very important to add this code to the TIXnGO interface configuration to ensure the newly ticket will not be injected back to the latest owner but to the new cultural contact instead. In the interface General screen, add the custom parameter resetInjectionInvalidationReasons to the Blockchain batch with the value "MOBILE_TAKE_BACK".
|
