MDM First Use Cases 3/8/2018

Emailed to John Julian, Alex Jackl, Robbie, Mark Fitzpatrick, Jane Linder, and Ashwini Nambiar:

Use Case 1: (Note: see the attached image from the white board as reference--everything that’s labeled on the picture as “5” you can just ignore and when you reach step 4, jump to 6).

1. A student clicks Yes on a CCCApply Standard application. (note: this means the SNS topic is triggered but simultaneously that submitted app is saved to the submitted application database, no?)
2. The SNS topic hears that and says, “oh look! Someone just submitted a CCCApply Standard application!" And that then...
3. Triggers a Conductor workflow that then pulls the application data through SQS into Conductor.
4. Conductor then PUTS or POSTS that application data into the Uber Adaptor, and MDM and that then...sends the application data to YOUnite.
5. YOUnite processes the application data and then...does one or more outgoing things to the Uber Adaptor, depending on which things it talks to, which would then...
6. Trigger a Conductor task, which would then mean...
7. Conductor then sends the CCCApply application data to SPS.

Use Case 2: (This is a non-MDM enabled scenario and timeliness matters as this is a front-end user scenario):

1. A student logs into the College Promise app (which they navigated to via MyPath and they have a CCCID).
2. As soon as that student logs in to the College Promise app, that triggers a request from the SPS to downloaded student data to pre-populate the application. (Note that, today, the Unicon team has this pre-populating from CCCApply data).
3. The student finishes the College Promise application and they click Submit.
4. Then we make use of Ben’s already-existing service (see note below) and that triggers a workflow (just like the other use case, above?) and writes the data to:
   • the SPS
   • a temp table in the student's Home College SIS
   • the College Promise database

Essentially, a triple fork. Note: We did not know for sure if Ben is using Conductor for this fork.

Note on Ben's already-existing College Promise (fka the BOG Fee Waiver): right now, Ben has demo'd a student completing the College Promise app and, upon Submit, Conductor recognizes it and routes it to the college adaptor for that student's Home College, which then writes the College Promise data to a temp table in that SIS. Also note that today, Course Exchange can read a student's College Promise financial aid decision data from their Home College's SIS and auto-write that financial aid decision data to the Teaching College's SIS (when that student signs up to take a Course Exchange course).