Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Custom parameters

Custom parametersPurpose 
ticketIterationSize

This custom parameter is used for the Tickets external printing/ Push cancelled and validate tickets/ Push controlled tickets. To support larger batch sizes, split them into smaller calls to blockchain to send smaller batches, one after the other inside the same execution. The default split size is 50

Note: The TIXnGO side supported only 50 tickets/times, so that should be kept as default.

batchSplitSize

This custom parameter is used for the Retrieve tickets status from TIXnGO batch. To support larger batch sizes, split them into smaller calls to blockchain to retrieve smaller batches, one after the other inside the same execution. The default split size is 1000

Example: Batch size in the Retrieve tickets status from TIXnGO = 5000, batchSplitSize = 1000. It will split 5000 to 5 calls in the same execution with 1000 per call

resetInjectionInvalidationReasons

This custom parameter is used for the Tickets external printing to allow injecting mobile tickets to the latest ticket holder contact or cultural contact based on the invalidation reason, i.e., reseating

Example: After injecting ticket into TnG for contact A (cultural contact) then contact A open mobile app and transfer the ticket to contact B (latest mobile owner). On the STX side, the operator reprinted that ticket with invalidation reason THEFT and reinject it into TnG, this ticket will reinject back to contact A. If there is no invalidation reason here, the new ticket will be reinjected back to contact B

Note: All the cancellation reasons are those which appear on the list of values in the BO [Institution > Initialisation > List of values > Ticket (Cancellation cause)]. With validation reason Theft , rESEATING will work too because the invalidation causes will be modified in order to remove the spaces and to be all set in upper cases

excludeTicketResale
overrideVisibilityFlagForInvalidationReasons

Both custom parameters are used for putting blockchain tickets into the resale platform and specified for Push cancelled and validate ticket batch. The purpose of those parameters is to update the invalidation reason to TnG after putting the ticket on the resale platform or tickets is resold.

Example: excludeTicketResale=true, overrideVisibilityFlagForInvalidationReason=RESALE_PENDING, RESOLD

After putting the ticket on the resale platform, the old ticket is invalidated and the validation reason will be updated into TnG side by the Push cancelled and validate ticket with invalidation set at overrideVisibilityFlagForInvalidationReason

For more information, please refer to the US STX-110559

dumpTnPRvariables=trueTo generate tnPRVariables file ticket detail after injecting ticket into TnG. To check the variable and its value as well
enforceMandatoryParametersThe interface fails with a proper error message before calling TixNGo if the mandatory parameters of the tickets to inject are not present.
Default value : true. Do not change if you don't know what you are doing.
dumpDataModifiedByTemplateDefault value: false. Set it to true to log the values modified by the template associated to the export.
overlaySpectatirDetailsWithLastOwner

Default value: true. Set it to false to skip the rule: But, IF the tickets has been reprinted, it will be assigned to its last known holder, as retrieved from TIXnGO.
(warning) The parameter is spelled with "Spectatir" (typo included) not "Spectator" as you may expect.

TIXNGO_LIFECYCLE_MODE

Only possible value lifecycle. When enabled, activates ticket status feature related to STX-122715 - Getting issue details... STATUS
If not used, the default mode for synchronisation is the history/legacy one. For more info about lifecycle vs history, please refer to this page : Retrieve ticket status from TIXnGO

sendmultilingualjsonobject=true

To inject tickets to TIXNGO  from S360 or by CSV with multilingual support STX-127552 - Getting issue details... STATUS

usePushCancelledTicketsV1

Default value: false. Set it to true to use the deprecated query to get the list of cancelled/invalidated tickets.
(warning) DEPRECATED. Either set it explicitly to false or remove completely the custom parameter.

doPatchWhenPushingControlledTicketsBy default is set to use PATCH in the API call. If set to false (doPatchWhenPushingControlledTickets=false), the method POST will be used.
  • No labels