Differences

This shows you the differences between two versions of the page.

--- development:applications:ticketer:ebonding:search:start [2017/02/03 16:53] – created adowling
+++ development:applications:ticketer:ebonding:search:start [2021/06/25 10:09] (current) – external edit 127.0.0.1
@@ Line 1: / Line 1: @@
+ --- //[[anna.dowling@errigal.com|Anna Dowling]]//====== The Ticketer and eBonding ======
+==== Ticket Searching via eBonding process ====
+We receive a RETRIEVE request from the carrier via SOAP. Again, this is processed first through the soap_component, then through the ebonding_component where business logic is applied to build the message. This message is then sent on to the Ticketer. RabbitMQ is used to pass these messages between the applications.
+The attributes requested from this message are retrieved using the 'Trouble Report Id' or as we call it the ticket id. This work is all completed via the SearchMessageHandler in the ticketer codebase. This uses the incoming message taken off of the queue to populate a search query which takes the ticket id and form details as its where clause fields The classes associated with building this query are SearchTicketFormQuery and ReadTicketQuery.
+If a ticket is successfully found for the Trouble Report Id which was sent to the Ticketer, then a response is generated from the query results which is in the format of a JSON map of maps containing the keys "ticket" and "form".

Internal Errigal Collaboration Wiki