Case Updates Received via FireHose WebService

C.9 Case Updates Received via FireHose WebService

Retrieving case status updates from the third party system is through a FIREHOSE web service response received into OFSLL through a pull service. Each response is channelled through an individual Event ID and Event Type.

A FIREHOSE web service getGriFireHose - scheduled at specific interval using batch (GRIFRH_BJ_100_01) retrieves the case updates. This response consists of case activities recorded in third party system between specific intervals (based on Max event ID).

Note that, the FIREHOSE web service response always contains specific Event Type Code from the third party system which are updated in the database and inturn is validated for appropriate action in OFSLL. The table below indicates the list of Event Type and the corresponding action updated in the system.

Table C-4 Event Type and Description

Event Type	Event Description	Action
600	ACCEPTED CASE	Change Work order status to OPEN
601	DECLINED CASE	Change Work order status to DECLINED
602	ACKNOWLEDGED CLOSE	Change Work order status to CLOSE
603	ACKNOWLEDGED HOLD	Change Work order status to ON HOLD
300	CASE WAS REPOED	Change Work order status to REPOSSESSED And Trigger getRepossessionDetails() web service to get repossession details and update in Servicing > Repo/Foreclosure tab.
302	CASE COMPLETED	Change Work order status to COMPLETED
200	FIRST UPDATE ADDED CUSTOM	Post the received update as Inbound Comment from Interface in Servicing >Customer Service >Comments tab.
201	UPDATE EDITED	Post the received update as Inbound Comment from Interface in Servicing >Customer Service >Comments tab.
203	UPDATE UNHIDDEN	Post the received update as Inbound Comment from Interface in Servicing >Customer Service >Comments tab.
811	INVOICE SENT TO CLIENT	Call the getCaseInvoiceData() web service and create the invoices in OFSLL.
1300	CR ADDED	Update Condition Report Status = Y and Condition Report Recd Dt = Event Received Date

Based on the web service response received from third party system, the status updates are posted onto corresponding work order(s) and account(s) in OFSLL.

For example, if the FIREHOSE web service response consists of the Event Type 600, it indicates that the case is accepted by the assigned vendor in third party system and status of the work order is to be updated to OPEN in OFSLL. Also a comment is posted on the corresponding account in Customer Service > Comments tab, with the following details:

Type = SYSTEM GENERATED
Sub Type = INBOUND FROM INTERFACE
Comment = "[Case No]: <<[Vendor] ACCEPTED CASE>>"
Comment By = "INTERNAL"
Comment Dt = Comment Posted date and time

Note:

Work order status change is permitted only if the previous status matches with the defined cycle setup (Setup > Products > Cycles). Else, update is not allowed and comment is posted on the account with the message Work Order Status Update failed due to mismatch of previous status.

Parent topic: Appendix :Generic Recovery Interface (GRI)