Within the use cases a UML sequence is provided against each. The UML sequence diagrams show the points at which a request & response is exchanged with TruService. All requests submitted to TruService must follow the published version of the schema being used. The UML sequence diagrams use a common set of command names, always shown between quotes (e.g. “GetQuestion” , “GetRating”). The tables below show how the command names used in the UML sequences map into the TruService schema.
NOTE: The tables below only show the first two or three levels of complex types from the schema. Please refer to the TruService schema for a complete reference.
This command in the UML sequences indicates the point at which a request to TruService is submitted to retrieve a rating question. The request can provide TruService with runtime details around language support, device characteristics etc. The response from TruService will indicate if a question is available and if so will provide the question, the relevant acknowledgment text and the receipt text based on the data passed when the question was requested.
This command in the UML sequences indicates the point at which a rating or result of a rating question is sent to TruService.
(This is optional and in use cases is shown as separate message)
This command in the UML sequences indicates the point at which the result of a transaction (for dwell time or dwell time extend) or card payment (payment request or card presentation) is submitted to TruService
This command in the UML sequences indicates one of the supported POS events being submitted to TruService. TruService can acknowledge this event, indicate an active question should be cleared or inform the caller that a question is available.
NOTE: An alternative to sending multiple instances of tsi::RequestPOSEvent is to send a single tsi::RequestPosEventList that enables multiple POS events to be sent to TruService in a single delivery.