ESR Full Notification File manual generation process

This page outlines the process to generate a Full Notification File (DNF) for a Deanery/Local Office. This is a manual process and is required on Day 1 of a new Local Office switching on the TIS-ESR interface where they've previously been using the Intrepid-ESR interface.

It may be required to generate a DNF file subsequent to Day 1, but this will have to be made by request from ESR. The circumstance under which one may be required, is where there might have been a possible outage of the interface for a period of time and therefore ESR being made out of sync as a result.

The Full Notification File, if requested with prior notice of X days by ESR, can be manually generated for a Local Office and sent as per the schedules. 

How to run ESR Full Notification:

Full ESR notification file can be generated per deanery at a time.

Follow the below steps in the same order:

1. Take a backup of table EsrNotification in tcs database.
2. Take a backup of table EsrNotificationDetailsRecord in ESR database.
3. The full notification should be triggered after the daily applicant and notification jobs are finished. The last one starts at 5.30PM. Ideally and if time permits it is good to do it over weekend as there is not much of user interactions with the TIS application. 
   1. The implication of running full notification results in duplicate high volume of applicant records generated during applicant export. 
4. Run the job https://build.tis.nhs.uk/jenkins/job/tis-esr-etl-parameterized/ with the below options selected:
   1. LOAD_TYPE: notification-full-load
   2. PLATFORM: prod
      1. (whichever environment you want the full load to run)
   3. PARAMS: --application.notification.fullNotificationDeanery=WMD
      1. WMD is the local office deanery code. This can be replaced with any deanery code you want to run the full load against.

   4. ESR_APP_LOG_LEVEL: Change it to DEBUG if you want to monitor the logs. Otherwise leave it as INFO.

   5. ESR_ROOT_LOG_LEVEL: INFO
   6. DEBUG: no
5. The jenkin job finishes after triggering the esr-etl load. ssh to the environment and grep the esr-etl log to see the progress of the load.
6. Once the job finishes you should see a DNF file generated and uploaded to the corresponding Azure account inside the <currentDate>-outbound folder.