The following is a collection of diagrams of the current ESR interface in TIS (Pre Bi directional work).

6am Notification Daily Load

This job executes the ESR ETL and triggers 2 endpoints in the TCS service that then

using ~~Placements~~ Posts that have no following placement or placements that have no future trainee,
Next Trainee will become Current Trainee on a Post in 13 weeks where 13 weeks from daily load day is their earliest eligible date to send to ESR. (needs adding to the activity diagram below. You got both in your Sequence diagram just after)

It creates EsrNotification records for the above. These records are then picked up by two other job that run later (17:00 Application export & 17:30 Notification daily)

Activity Diagram

Sequence Diagram

15:30 Applicant Load

This job kicks off the ESR ETL, it downloads a file from Azure and generates PositionInformation, PositionReconciliation and ApplicantDetail records from these files. If there are issues creating these records they are marked with unmatched_penfing or unmatced_delete statuses accordingly for the positions and Errored status for ApplicantDetails records, then a confirmation file is created per file received and uploaded to Azure for ESR to pick up.

It then updates the records with information from Posts from TCS and pushes these records to the ESR service. Once thats done, another confirmation file is uploaded as well as RMT exceptions files are created for Position and Reconciliation. Finally the report is created for any mismatched positions.

The PositionInformation, PositionReconciliation and ApplicantDetail Records are then used by the 17:00 Applicant Export and the 17:30 Notification Daily Jobs

Activity Diagram

Sequence Diagram

17:00 Applicant Export

This job triggers the ESR-ETL, this job uses the previous data extensively to create ApplicantDetailRecords from PositionInformation and PositionReconciliation Records. To ensure that the same records are not picked up again from the ESR Service, they are updated and saved before the ApplicantDetail file is generated and uploaded to Azure

Activity Diagram

Sequence Diagram

17:30 Notification Daily Export

Triggered at 17:30, Use all the notifications, PositionInformation and PositionReconciliation records to create a NotificationRecords for both type 1 and the rest. With the NotificationRecords generate a notifications file, upload to Azure then save them in the ESR service,

Activity Diagram

Sequence Diagram

20:00 APC Import

This job downloads the APC (Applicant Confirmation) file from Azure, creates ApplicantConfirmation records and saves them in the ESR service. This file contains the results from ESR's processing of the APP file that we upload

Activity Diagram

Sequence Diagram

Browser not supported