SCT Banner Student / Release Guide / 7.0

Section 13 Problem ResolutionsAdmissions ModuleSAAQUIK (#94244)GOPVALT1.sql was causing improper error messages to appear with Value-BasedSecurity. This has been corrected.Previously, the concept for VBS access was that a recruit record, admissions record,or a general student record already existed for the person. The record was one towhich the user did not have access. Consequently, the user could not access thatperson at all, even to add a valid row, (one to which the user did have access). ThePIDM was unavailable for that module. Now, the concept has changed so that thePIDM will always be available for the addition of a valid row, (one to which the userhas access). Banner will no longer check the existing rows for the validity of accessto that person (PIDM). Resolved in Release 7.0.SAAQUIK (#89505)If a ZIP code corresponded to more than one city or state on GTVZIPC, when thatZIP code was entered on SPAIDEN, the form defaulted in the last city listedalphabetically, with the message: "WARNING-Multiple Cities exist for this ZIP/Postalcode; press LIST to select one." However, in the Address Information window onSRAQUIK or SAAQUIK, the form populated the first city alphabetically, and nowarning message was displayed. The correct city will now be populated, and thewarning message will be displayed. Also the warning message has been modified toread the same on SRAQUIK, SAAQUIK, and SPAIDEN. Resolved in Release 6.1.SAAQUIK (#84905)When searching for a ZIP code from the Address Information block, if more thanone city existed for a ZIP code, selecting any of the cities would always return thefirst city alphabetically listed. The correct city is now returned. Resolved in Release6.1.SAAQUIK (#85416)In the situation where, if a student record already existed for a given term and level,and registration existed but for a term other than the one in the Key Block, you weresupposed to receive the following error message: "*ERROR* Student record exists forterm, use a different term." This error will now be displayed correctly. Resolved inRelease 6.1.SAAQUIK (#86779)When adding a second major in the Primary Curriculum window, after you pressedEnter or Tab, the department code for Major 2 was defaulted into the Dept 1 field,which is associated with Major 1. The Dept 2 field was left blank. This caused a fatalcurriculum error. You had to manually enter the Dept 2 value, and then manuallyre-enter the Dept 1 value. Now, when you Tab out of Major 1 or Major 2, theassociated department codes will automatically default in for the correct major.Resolved in Release 6.1.January 2005 Student Release 7.0Confidential Release Guide 339