Banner Student / Release Guide / 7.3.2

Section 4 Problem ResolutionsAdmissions ModuleThe Deadline field description in the Application Checklist block of SAAADMShas been updated to refer to the SARCHKL_DEADLINE_DATE column.The Generated by System field description in the Application Checklist blockof SAAADMS has been updated to refer to the SARCHKL_SOURCE column.4. The impact of new functionality on existing records would have been discussedin a release guide. It is not appropriate for the user guide.5. Imaging is discussed in the documentation for BXS (Banner XtenderSolutions). As not all institutions license this product, it is not appropriate todiscuss it in the Banner Student documentation.6. The Date field reflects the date the checklist item was added manually or wasautomatically generated. The documentation does not need to be changed.SAASUMISAADCSN(#1-13Q0XK)Description: The Status Date field description did not reflect a change infunctionality regarding when the application status changed from I to C, after thelast checklist item had been received. This caused the date for the checklist item thatwas received to populate the application status date with the received date.Impact: Users were confused and thought the processing was not working properly.Resolution: The field description for the Status Date field now reads:“Date of the status associated with the admissions application. If no date is entered,the system date is the default. This value comes from the Application Status Datefield in the main window on the Admissions Application Form (SAAADMS).If the application status changes because checklist items have been received, thenthe item received date for the checklist item will be defaulted into the status date forthe application.”(#1-5CU5K)Description: The Admission Decision Criteria Report (SARBDSN) may not calculateresults properly if all the priority values (as set up on SAADCSN) are not the samelength.For example, priority 101 will be selected before priority 95, because the Priorityfield is defined as a three-character field, not a numeric field.Impact: You always have to use three digit numbers in the Priority field.Resolution: The field definition for the Priority field on SAADCSN has beenupdated to clarify how priorities are used. The user guide now reads:“Alphanumeric code used to determine which decision is selected in the batchprocess when multiple decisions qualify. The lowest priority value will be chosenfirst. For example, priority 001 will be selected first.Since the code is alphanumeric, all values should be entered with the same numberof digits and the same case to ensure expected sorting. For example, 99 will besorted after 101, but 099 will be sorted before 101.February 2007 Student Release 7.3.2Confidential Release Guide 93