-Challenge:How to manage Applicants in AW who have become inactive in SIS?

Summary:When a student becomes "active" in SIS, i.e. eligible to register, they are extracted and sent to AW in dataload. Only active students are included in dataload. Once student accesses AW, they become an applicant and their information is loaded into AW. Their information is updated in AW with each subsequent dataload from SIS.When student becomes "inactive" in SIS, they are no longer included in dataload. However, they continue to show as "active" in AW because no record exists in dataload from SIS to change their status to "inactive". A process may exist for the new year startup in AW to deactivate applicants prior to the new year startup.

-Problem:Applicants are showing up in Auto-Match Opportunities who are "inactive" in SIS because they are still "active" in AW due to the fact they are no longer included in dataload.I encourage AcademicWorks to consider providing an API allowing schools to export current applicants. This will offer multiple benefits including the automation of applicant inactivation based on information in SIS.This API could function almost identically to the Fund Disbursement API created years ago ... with the exception of pulling users found under the Opportunity / Applicants tab within the web-based UI.