Issue Description:
Andrew Jung’s app in Slate – it does seem we have his LORs and we have one from a PT, but in the “app details (PTCAS)” section, his LOR from the PT is still listed as “requested” when it has been “complete” in PTCAS for about a week now … is there a way to manually update this as well (or would this be a time when we’re waiving it on the checklist…?)?
Troubleshooting/Research
Reviewed the applicant’s record in PTCAS and in Slate. The name of the recommender in Slate doesn’t match in PTCAS; seems like the applicant swapped out one recommender for another, likely after his application was verified (9/20).
We know that updates to recommendation information in the CAS do not trigger an update file via the API, so the change to recommender after verification would not have been picked up by the API file.
The scheduled export in each instance of PTCAS to send a file of updated recommendation data should have caught this, however.
Reviewed the scheduled exports in PTCAS and the WebAdMIT API - PTCAS Evaluation Received source format in Slate. There should be 3 files in the morning and 3 in the afternoon for each day; instead there is only one in the morning and one in the afternoon. Realized this is probably the issue where files with the same name who get dumped into the staging server before being processed by Slate overwrite eachother (same file name is not cool).
Therefore, even if a file had been generated with the updated recommender information out of the DPt-PHX PTCAS, it seems to have been overwritten by one of the other two scheduled files sent from the other PTCAS instances at the same time.
Wanted to see if different name had been included in a file through that source format would’ve added a new row to the Recommender entity, so generated a file out of PTCAS in that same format including the updated information for the sample student and ran it through the Source Format (as if it had come through as scheduled) and it did create a new row for the new recommender:
The issue is now just that because the original process was designed only as an update, not all fields were added to the import, so First Name and Title are not coming through via the update. Can also fix this by adding these fields in the scheduled export out of PTCAS, and updating the source format mapping.
Resolution Steps:
In all three instances of PTCAS, I updated the file name for the scheduled export to append the three letter code for the program to each file, so the would no longer have the same file name and overwrite each other:
I updated the Import Automation settings in the source format to add a wildcard character to the Import Path/Mask so it would still pick up the new files
I ran fresh exports out of each instance, then ran a force process pickup and a force process import in Slate (via the Database tools) to ensure that these new files were picked up and consumed properly, which they were.
Add Comment