Versions Compared

Version Old Version 11 New Version Current
Changes made by

Helen Williams

Helen Williams

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Page Properties
idbug-details

Slate Instance

TUP

Requestor/Reporter

Sam Rhuda

Date

10/1/2023

Status

Status
colourRedGreen
titleIn ProgressComplete

Bug Description

In Progress data file is not sending from CAS for some applicants causing application data to be overridden, including the unique for mapping application ID and program choice.

...

Program

IP File Name

App File Name

BOS

PTCAS-app-started-adhoc-6861_12748_349019_<applicationID><CASapplicantid>.csv

PTCAS-app-s-adhoc-6861_12748_349019_<applicationID><CASapplicantid>.csv

PHX

PTCAS-app-started-adhoc-6861_14347_349027_<applicationID><CASapplicantid>.csv

PTCAS-app-s-adhoc-6861_14347_349027_<applicationID><CASapplicantid>.csv

SEA

PTCAS-app-started-adhoc-6861_1274815423_349022_<applicationID><CASapplicantid>.csv

PTCAS-app-s-adhoc-6861_1274815423_349022_<applicationID><CASapplicantid>.csv

...

  1. Change the settings to the source format to add Round: DPT and Round Always Create: Yes.

  2. Generate an application data file and put it through the import process. (Do not retro refresh original file, as retro refresh does not attempt to re-match).

  3. Confirm that new application created.

  4. All testing scenarios ran 3/1 and 3/4, confirmed no issues on 3/4 and will update in production.

Scenarios:

  1. Student has no history of an in-progress data file because they did not indicate they wanted to share this information. They submit their application and an application data file is sent to us, but does not match because of current settings and does not create an application.

    1. Find a student who has no application. Create an application file to import via the app source format as submitted.

    2. Luis Carrillo had file sent to app source format but no history of file sent to in progress source format. Original file created a person record but did not create an application record. In Test I uploaded a new file through the app source format and confirmed that it did create the application correctly.

    3. Just in case, tested the scenario where no person record existed at all by modifying an existing data file to change all the data used for matching (CAS ID, first name, last name, email) to make it look brand new and confirmed that Slate did create a new person record as well as the applciation record as expected.

  2. Student has an in-progress application for more than one program, and submits the application for one of those two programs. Slate should match on the existing application ID and update only the app for one program and not the other.

    1. Kaiden Andersen had an IP app for PHX and SEA. Uploaded an app file for PHX through the app source format and confirmed that PHX app was updated (PHX changed to submitted, SEA still unsubmitted). Source file didn’t change the CAS status (wasn’t changed in file itself), so was still In Progress. This prevented the checklist from being added, and screwed up the status rules, so going to try again with another file and change status so that it will function.

    2. Phillip VanWanzeele had an IP app for PHX and SEA. Changed csv file progMate.progSele0.submissionStatus from IP to Received before uploading; this time the checklist was added and the status updated to Awaiting Materials appropriately.

  3. Student has an in-progress application for one program, but then submits an application for a different program. Slate will not match on app-data, but will match on person data, and so will match the app data in the source to the application record in the same round on the person record.

    1. Find a student who has an IP app and no other apps. Create an application file, modify so the program data is different, import via the app source format as submitted.

    2. Jade McIntyre had an IP PHX app and no other apps. Modified the csv file to change the Program ID to -022 instead of -027 (SEA instead of PHX) and the status to Complete. Uploaded through the app source format and it did create a SEA ap, change the status to complete (which triggered checklist and status update).

  4. Student has an existing applciation for one program and an update file for the same application is sent later, Slate should match and not create a new application.

    1. Find a student who has an application and do a second import of the application data file after changing the app source format to ensure a second app is not created.

    2. Andrew Rattray had an IP PHX application. Changed source file to update the status to Verified and then imported through the application source format. Confirmed that no new app was created but existing app was updated correctly.

...