Conditional Applications should have virtual matching similar to Automatches
Currently if a conditional application is open and has qualifications set, the students will match in immediately and be actualized. Often times, Opportunity Admins need to tweak these qualifications as they realize the pool is not matching as expected. Unfortunately, now the pool is left with potential thousands of unqualified students even though the student has never logged in and completed the application. It would be great if the conditional application matched like an automatch being the student would be removed if no longer qualifying and not starting/drafting the application. This happens quite often especially if you miss putting a start and end date in first. Please let me know if you need further clarification. Cammy from Keith Brown
-
Deleted User
- Sep 7 2018
- Shipped
| Employee Name | Cammy Jagielski |
| Client Name "shard name" | southalabama, IU, wisc |
| User | System Admin |
| Functional Unit | Conditional Application |
Related Enhancements
An update was made to prevent Conditional Applications from being created before their start date. This should address the issues described by this request (as long as a start date is set).
And to add to Dana's note, the start date is not required so if left blank it immediately starts matching as it appears to be open at all times. That is easily looked over at first unless the person clicks into the details first which is not always the order. It would be nice if that was required when the template was being created if it will be that they will not start matching until that date has arrived if that helps...
This is an issue for IU and South Alabama too (both CUUI clients). After CM, they have us archive the general and conditional applications and enter a start date. A new import file comes in and creates the general applications, and in turn the conditional applications even though the CAs aren't open yet. This is happening because the qualifications on the conditionals are based off of imported data only.
The only way to prevent this at the moment would be to also remove the qualifications or add a qualification that no one can meet until the start date arrives and they are ready to let students apply.
This could also be an issue for clients without CUUI; if they decide to implement a CA in the middle of an open cycle. If they are playing around with the qualifications in an attempt to find the correct applicants, they could wind up with a lot of applicants who shouldn't be in the grid.
I believe the issue is that fact that the start date doesn't prevent applications from being created.