51.4.2.0 51.4.1.1 51.4.1.0 51.3.0.0 51.2.0.17 51.2.0.12 51.2.0.11 51.2.0.5 51.2.0.2
51.4.2.0 51.4.1.1 51.4.1.0 51.3.0.0 51.2.0.17 51.2.0.12 51.2.0.11 51.2.0.5 51.2.0.2
Breadcrumbs

TicketExport

Description

The TicketExport component allows you to convert your tickets into an HTTP request and send it to a configured endpoint.

Implementation

  • Drag and drop the component into a RestTicketDeviceExt. 

  • image-20260112-080540.png

    Customize it

  • Trigger the execute action.

Actions

  • Execute: Triggers the conversion of your Tickets into an HTTP request and sends it.

  • SynchronizeTemplate: Synchronizes the ResponseTicketMapper with the corresponding template.

Properties

  • Status: The status of the Component.

  • State: The current state of the export process

    • Idle: The component is ready and available for a new export .

    • Pending: An export request has been received and is awaiting execution.

    • InProgress: The export operation is currently running.

  • Enabled: The enabled state of this descriptor.

  • ExecutionTime: Specifies when the component should be executed.

  • LastAttempt: Timestamp of the most recent export.

  • LastSuccess: Timestamp of the most recent successful export.

  • LastFailure: Timestamp of the most recent failed export.

  • FaultCause: Reason for the fault.

  • HttpConfig: Defines the request to send. This HttpConfig is slightly different to the one in the RestNetwork.

  • ValueSelector: JSON Key Selector targeting the updated Ticket values in the Http Response.

  • TimestampFormat: Format used to encode/decode Timestamp values.

  • ExportConfig: Component used to configure which Tickets to exports and how.

  • ResponseTicketMapper: The main task of the TicketExport is to export Tickets, but thanks to the ResponseTicketMapper, you will be able to update the exported Ticket with the data from the Http Response. The most common scenario will be to extract the id given by the api to an externalId of the Ticket. See TicketMapperFieldEditor .


Currently, the ResponseTicketMapper will only work if the batch in the ExportConfig is set to 1.


FaultCauses:

Error Message

Details

TroubleShoot

Missing BtibService

The BtibService is not present in the Services.

Add it from the palette to the Services.

Disabled BtibService

The BtibService is present but is not enabled.

Enable your BtibService.

Found no valid ‘activeTicketing' license

The system could not detect a valid activeTicketing feature.

In “station:|slot:/Services/PlatformServices/LicenseService” check that your Btib.licence contains the “activeTicketing” feature and check that it’s not expired.
Cannot be recovered until the service is restarted.

Missing TicketService

The TicketService is not present in the Services.

Add it from the palette to the Services.

The TicketService is not operational

The TicketService experienced an error.

Check the FaultCause on the TicketService.

The RestNetwork is not operational

The RestNetwork experienced an error.

Check the FaultCause on the RestNetwork.

The RestQuery is not operational

The RestQuery experienced an error.

Check the FaultCause on the RestQuery.

Missing TicketTemplate

Cannot find the associated TicketTemplate.

Add the TicketTemplate in the TicketTemplates and reselect it in the Template slot.

The TicketTemplate is not operational

The associated TicketTemplate experienced an error.

Check the FaultCause on the associated TicketTemplate.

The RestTicketDeviceExt is not operational

The RestTicketDeviceExt experienced an error.

Check the FaultCause on the RestTicketDeviceExt.