Banner Student / Release Guide / 7.3.2

More documents

Recommendations

Info

Section 4 Problem ResolutionsAdmissions ModuleResolution: The changes to the saradap.change_fee_ind.POST-CHANGE triggerthat were added for #CMS-DFCT101341 have been removed. The SARADAP.KEY-DUPREC block level trigger has been modified to null out the rate code and waivercode values when an application is copied.SAACHKBSAAEAPSSAAEAPS(#1-STFZS)Description: When the form was in query mode, the Search button did not bring upa List of Values for some fields (Level, College, Degree, and Field of Study Code).The following message was received: FRM-41047: Cannot navigate out of current blockin enter-query mode.Impact: Users had to use a function key or the List menu option to display a List ofValues.Resolution: A trigger has been modified to check for query mode and generate theList of Value windows, instead of Option List windows. Another correction was madeso that you can select a value from the List of Values for the Program field.(#1-12UKKA)Description: If you selected the Verify Application option prior to having completedthe manual verification, the application verification occurred, but with errors. Theverification should not have been permitted until the required manual verificationsteps had been completed.Numerous errors could occur, including but not limited to P120 curriculum errors.The base error that affects many of the routines is in the P010 ID verification. Theverification message is ID has not yet been resolved within the Banner system. Once theerror has been encountered, then the manual verification step must be performed,but you should not be able to proceed this far without having already done that.Impact: Verification errors were caused because manual verification was notcompleted. This caused processing to take longer than usual.Resolution: An additional check is now made in the process to inform users thatmanual verification steps remain, before the verify application process can beexecuted. The Person Status field must be set to Y before verification can take place.(#1-11IX3R)Description: When you navigated through the various windows to view Webapplication information, the values for the Person Status and Application Statusfields would change from N to Y, even if you hadn’t made any changes on the form.In situations where the Application Status should have been updated to Y, it was notbeing updated.Impact: The statuses may not be correct for the application.Resolution: Indicators have been added to the FORM_HEADER block to be updatedwhen a change has been made in the Verification Steps window. TheSARPSTA_RETURN trigger has been changed to update the status codes only ifchanges have been made to any of the fields in the Verification Steps window.Otherwise, all status codes will remain unchanged.Student Release 7.3.2 February 200798 Release Guide Confidential
Section 4 Problem ResolutionsAdmissions ModuleSAAEAPSSAAEAPSSAAERULSAAETBLSAAQUAN(#1-IF6E3)Description: Quick Start applications that were pushed successfully did not haveload dates populated for the procedures. Also, the Completion Indicator was notchecked for the P900 procedure, and the Verified Date, Completed Date, and LoadDate fields were null. This was cosmetic, as the data was pushed correctly intoBanner.Impact: Data that had been pushed was not being displayed.Resolution: The missing data will now be displayed correctly when an application ispushed successfully.(#1-O06KV)Description: A Web application that used “International Access” for the phonenumber received an error message, and the phone number was not pushed.Impact: Web applications set up for international access had incomplete data.Resolution: SAAEAPS has been modified to correctly map data back to theSARPHON row after matching has taken place, so the international access numberis available to be pushed with the application. The error message correction isincluded with problem resolution #1-GLNU7.(#1-OA8IX)Description: Users could uncheck the System Required Indicator and delete thesystem required rules.Impact: With missing rules, processing was incomplete.Resolution: Code has been added to prevent the System Required Indicator frombeing unchecked after a rule has been saved.(#1-H4FON)Description: After entering a Web ID in the Key Block and then using Next Block,data appears in all three blocks, yet the autohint displays the message: Query CausedNo Records to be Retrieved.Impact: An invalid error message was displayed.Resolution: A redundant execute query has been commented out to correct this.(#1-10F7F5)Description: Three issues existed:1. When a question/answer record was manually entered with an admissionsdecision request code, two Save functions were needed to save the changes.The first Save updated the associated checklist received date (SARQUAN,SARCHKL), and the second Save updated the application status (SARADAP).Only one Save function should be needed.2. The Transaction complete: 1 records applied and saved message that was displayedwhen you tried to update or delete a question/answer record from a selfserviceapplication was misleading.February 2007 Student Release 7.3.2Confidential Release Guide 99
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:
Page 44 and 45:
Page 46 and 47:
Page 48 and 49: 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 97: 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 149 and 150:
Section 4 - Problem ResolutionsSamp
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?