Banner Student / Release Guide / 7.3.2

More documents

Recommendations

Info

Section 4 Problem ResolutionsAdmissions Module4. The forms reference documentation/online help for SAAACKL andSAAADMS says Checklist Origin is populated with BASELINE when there arecord is manually inserted. But it seems to be populated with BASELINE for allinserts, whether manual or system performed. There is no discussion of whathappens to pre-existing records. Its seems it is not populated retroactively forexisting records.5. The forms reference documentation/online help for SAAACKL andSAAADMS does not describe the impact of imaging (Banner XtenderSolutions) on checklist fields.6. The purpose of the Date field on SAAACKL and SAAADMS is not clear. Thename could refer to the source date or the activity date. The forms referencedocumentation/online help for SAAACKL does not mention this field, and thetext for SAAADMS says it is used for the source date, which is the date therequirement was added. But the source date could be the date that imagingupdated the checklist.Impact: The documentation was not complete or clear in some cases.Resolution: The documentation for the forms reference and online help has beenupdated as needed to resolve these issues.1. The text has been updated to reflect that the mandatory checklist items mustbe received before the Outstanding Items flag and the Status field are updated.“Selective queries may be performed within this section. If multipleapplications exist, they will be displayed in descending order by term andapplication number. The scroll bar to the right is used to scroll amongmultiple application records. If all mandatory checklist items associated with aspecific application are updated with a received date in the ApplicationChecklist information, the Outstanding Items flag will be updated from Y(es)to blank (no outstanding items), and the Status field will be updated fromI(ncomplete) to C(omplete). Use the Next Block function to display thechecklist items associated with a specific application.”“The Application Checklist information is used to review, and optionallyupdate, checklist items associated with an admissions application. Existingchecklist items may be updated or deleted, and new checklist items may beadded. If all outstanding mandatory checklist items for an application areupdated with a received date in this section, the Outstanding Items flag in theAdmissions Application Summary information will be updated from Y(es) toblank (no outstanding items), and the Status field will be updated fromI(ncomplete) to C(omplete).”2. The field definitions have been added for the Application Checklist block,using the existing information from SAAADMS.3. The Count field description in the Application Checklist block of SAAADMShas been updated to refer to the SARCHKL_REQ_COUNT column.Student Release 7.3.2 February 200792 Release Guide Confidential
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
Page 3 and 4:
Release GuideStudent SystemIntroduc
Page 6 and 7:
Table of ContentsThis page intentio
Page 8 and 9:
IntroductionThis page intentionally
Page 10 and 11:
Section 1 PESC/XML Transcript Phase
Page 12 and 13:
Page 14 and 15:
Page 16 and 17:
Section 1 - PESC/XML Transcript Pha
Page 18 and 19:
Page 20 and 21:
Page 22 and 23:
Page 24 and 25:
Page 26 and 27:
Page 28 and 29:
Page 30 and 31:
Page 32 and 33:
Page 34 and 35:
Page 36 and 37:
Page 38 and 39:
Page 40 and 41:
Page 42 and 43: Section 1 - PESC/XML Transcript Pha
Page 58 and 59: Section 2 PESC/XML Transcript Phase
Page 60 and 61: Section 3 Miscellaneous Enhancement
Page 74 and 75: Section 4 Problem ResolutionsSchedu
Page 76 and 77: Section 4 Problem ResolutionsFacult
Page 79 and 80: Section 4 Problem ResolutionsLocati
Page 81 and 82: Section 4 Problem ResolutionsLocati
Page 83 and 84: Section 4 Problem ResolutionsRecrui
Page 85 and 86: Section 4 Problem ResolutionsRecrui
Page 87 and 88: Section 4 Problem ResolutionsAdmiss
Page 91: Section 4 Problem ResolutionsAdmiss
Page 107 and 108: Section 4 Problem ResolutionsGenera
Page 109 and 110: Section 4 Problem ResolutionsRegist
Page 117 and 118: Section 4 Problem ResolutionsAcadem
Page 119 and 120: Section 4 Problem ResolutionsAcadem
Page 121 and 122: Section 4 Problem ResolutionsCAPP M
Page 123 and 124: Section 4 Problem ResolutionsOveral
Page 129 and 130: Section 4 Problem ResolutionsValida
Page 131 and 132: Section 4 - Problem ResolutionsSamp
Page 143 and 144:
Section 4 - Problem ResolutionsSamp
Page 145 and 146:
Page 147 and 148:
Page 149 and 150:
Page 151 and 152:
Page 153 and 154:
Page 155 and 156:
Page 157 and 158:
Page 159 and 160:
Page 161 and 162:
Page 163 and 164:
Page 165 and 166:
Page 167 and 168:
Page 169 and 170:
Page 171 and 172:
Page 173 and 174:
Page 175 and 176:
Page 177 and 178:
Page 179 and 180:
show all

Banner Student / Release Guide / 7.3.2

Create successful ePaper yourself

Delete template?

Save as template?