Elastic Search Index Update Event for Connections (outdated)

NB: Superseded by the following documentation:
TIS Change Data Capture
GMC (DocumentDB) Change Data Capture

Trainee data insert/update to Elastic Search index

Open

• TIS Change Event
  1. When persons, contact details, placements, programme membership is created/saved on TIS
  2. Rabbit message of latest trainee information will be sent from TCS to Reval

  exchange: reval.exchange queue: reval.queue.connection.update routingKey: reval.connection.update

  3. Message will be received in Reval Connection service for handling the business logic
  4. Trainee records will be updated in Elastic Search corresponding indexes (Master, Connected, Disconnected, Exception, *All, *Hidden) according to the business logic (* TODO)

• GMC Change Event
  1. During overnight GMC sync, GMC data will be pushed from GMC-Client to Recommendation service for updating the MongoDB

  exchange: reval.exchange.gmcsync queue: reval.queue.gmcsync.recommendation routingKey: reval.gmcsync

  
  2. At the same time, GMC data will also be pushed to Connection service for updating Elastic Search Master index and the corresponding Connection indexes

  exchange: reval.exchange.gmcsync queue: reval.queue.gmcsync.connection routingKey: reval.gmcsync

• Manual Connection Change Event
  1. When a user manually updates (add/remove) connection, a request will be sent from the Connection service to GMC for updating, GMC will return a response code for the status of the update request.
  
  2. If it is successful, the Connection service will send a Rabbit message to the Recommendation service for updating DBC in Reval MongoDB; If it failed, it will add a record into the Exception Log.
  
  3. Both success and failure cases would be referred to UpdateConnectionReceiver.handleMessage(). So the new designatedBody, exceptionReason and connectionStatus of a trainee will be updated in Elastic Search Master Index.
  
  4. Then, the trainee Record will be updated in Elastic Search corresponding indexes (Connected, Disconnected, Exception, *All, *Hidden) according to the business logic (* TODO)

Trainee data retrieved from Elastic Search index

Open

Trainee data is pre-processed and stored in the indexes according to the business logic.

1. When the Reval connection summary page is loaded

2. Trainee data of the corresponding indexes will be retrieved and handled in the Connection service

3. Trainee data will be routing via Integration service and returned to the front end