Banner Student / Release Guide / 7.3.2

More documents

Recommendations

Info

Section 4 Problem ResolutionsLocation Management ModuleFormsSLASGNQSLASGNQ(#CMS-DFCT81099)Description: When a query included an end date, but not a start date, or the queryused only an end date, and no results were returned. Also a duplicate Options Menuitem existed for Available Rooms.Impact: Incorrect query results implied that a room was not available when it shouldhave been.Resolution: A trigger has been modified so that correct results will be returned. Theextra entry on GUROPTM for Available Rooms (sequence number 1.03) has beenremoved.(#CMS-DFCT106016)Description: The system displayed #### in the Capacity and Maximum fields whenthe value was five (5) characters in length.Impact: The fields could not accommodate values that were five characters long, sowhen the query was executed, the incorrect value #### was displayed.Resolution: The field size and query size for the SLBRDEF_CAPACITY andSLBRDEF_MAXIMUM_CAPACITY fields have been changed to five (5).SLQMEETSLQROOM(#CMS-DFCT77932)Description: SLQMEET was not evaluating the term-based room attributes properly.This was verified by removing attributes for terms other than the current term.SLIAEVN does appear to be functioning properly.Impact: Rooms would not appear to be available when they should have been.Resolution: The SELECT_DUAL_1 function, which checks attributes, has beencorrected to select the proper effective term. Searches for an attribute that matchesthe room record should check for the highest term code, which is less than or equalto the term code on the room record being used.(#CMS-DFCT92892)Description: The Term field in the Key Block did not always reflect thecorresponding Term field value entered on SLARDEF. This occurred when thevalue was changed on SLARDEF and the query was performed on SLQROOM.Impact: When rooms are queried by term, the results will not represent the correctterm code.Resolution: The SAVE_KEYS and GLOBAL_COPY triggers have been modified to usethe global.term_code, not the global.key_term.Student Release 7.3.2 February 200780 Release Guide Confidential
Section 4 Problem ResolutionsLocation Management ModuleObject:Access ViewsAS_RESIDENTIAL_LIFE,slfmasg.sql,slfpasg.sql,slfrasg.sql,slfrdef.sql,slfbldg.sqlAS_RESIDENTIAL_LIFE,slfmasg.sql,slfpasg.sql,slfrasg.sql,slfrdef.sql,slfbldg.sqlAS_RESIDENTIAL_LIFE_CHANGES,slfmbld.sql,slfmmas.sql,slfmpas.sql,slfmras.sql,slfmrde.sql(#CMS-DFCT89498)Description: The view returned incorrect results where more than one roomassignment existed with the same start dates.Impact: The view was not retrieving correct information when multiple roomassignments existed with same start and end dates.Resolution: The ORDER BY clauses in the cursors in the packages called byslvres2.sql have been changed to use the status date and the activity date todetermine the most current data row. If the status date is the same for more thanone row, the activity date will determine the last row that was updated.(#CMS-DFCT79507)Description: The view should reflect the current room, phone, and mealassignments.Impact: The view was not retrieving the current information when multipleassignments existed with the same start and end dates for room, meal, and phone.Resolution: This was corrected with changes made for problem resolution #CMS-DFCT89498. The ORDER BY clauses in the cursors in the packages called byslvres2.sql have been changed to use the status date and the activity date todetermine the most current data row. If the status date is the same for more thanone row, the activity date will determine the last row that was updated.(#CMS-DFCT78593)Description: If multiple assignments existed for a term (i.e., the room had beenchanged) the view returned the first assignment, even though this may not havebeen the current room for the student. The view should return the most current,active assignments or all assignments for a term.Impact: The view may retrieve data that is not the most current for records in thephone, meal, and room assignment tables. Users need to see the most recentassignment information for a student.Resolution: The ORDER BY clauses in the cursors in the packages called byslvrsm2.sql have been changed to use the status date and the activity date, inconjunction with the term code, to determine the most current data row.Also, the SLFMRDE function has been modified to retrieve the correct prior roomnumber.APIgokb_room_assign_r1.sql(#1-4OSMC)Description: SLRROLL was not rolling a room when a restriction override existedfor the room from term on SLARASG. When SLRROLL was run in Audit Mode, thereport indicated that the room assignment would be rolled successfully. However,February 2007 Student Release 7.3.2Confidential Release Guide 81
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: 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: 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 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 133 and 134:
Page 135 and 136:
Page 137 and 138:
Page 139 and 140:
Page 141 and 142:
Page 143 and 144:
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?