Banner Student / Release Guide / 7.3.2

More documents

Recommendations

Info

Section 4 Problem ResolutionsOverallcounter. The SORLFOS and SORLFOS_LITE post query has been changed to selectthe maximum SORLFOS_SEQNO, and to not use the maximum function from the APIwhich adds one (1) to it.SOQOLIBSOQILIBSOQOLIBSOQOLIB,SRAQUIK,SRARECR,SAAQUIK,SAAADMS,SGASTDN,SFAREGS,SHADEGR(#1-1ADX6J)Description: When start and end dates were entered in the Field of Study windowon SRARECR using the Calendar button, the dates were reversed. They wereinserted into the opposite fields.Impact: Dates had to be entered manually.Resolution: The Calendar buttons have been switched so they are next to the correctfields for Start Date and End Date.(#1-18IT85)Description: An error was displayed when a new application was entered, and a Savefunction was performed after the Program value had been entered. The *Error*Enter required level code message was displayed at the same time as the Level, College,and Degree fields were automatically populated. If a second Save function wasperformed without any additional data entry, the Save was successful.Impact: Users had to navigate (Tab) out of the curriculum element before savingtheir changes.Resolution: This has been corrected. The KEY-COMMIT trigger on the SORLCURand SORLCUR_LITE blocks has been modified to force validation to occur at the fieldlevel.(1-1FYJ4Q)Description: When you duplicated a curriculum record and saved the recordwithout changing the field of study, you could save an invalid field of study.Impact: Users could duplicate a curriculum record and select a program where themajor on the old program was no longer valid for the new program.Resolution: This was resolved with the corrections made for problem resolution #1-18IT85.(#1-1A1XOL)Description: Previously, if a student had only one curriculum, and a Remove Recordwas performed, the Priority field was not automatically populated. Now, the Priorityvalue defaults to 2. This also occurred when an Insert Record was performed on anexisting SORLCUR record.Impact: Users must manually change the priority to the initial value on the newcurriculum record after all curriculum rows are deleted.Resolution: The NEW_SORLCUR form level trigger (referenced by SRAQUIK,SRARECR, SAAQUIK, SAAADMS, SGASTDN, SFAREGS, and SHADEGR) has beenmodified. This trigger is executed when a new curriculum record is inserted in thekey for the following instances: create record, next record and a new record isinserted, clear record and only one curriculum exists, delete record when only oneStudent Release 7.3.2 February 2007126 Release Guide Confidential
Section 4 Problem ResolutionsOverallcurriculum existed. The trigger calculates the new priority and fills in default valuesfrom SORLCDF.The source of the maximum priority has been changed and now comes fromSOTLCUR instead of SORLCUR. The issue is that SORLCUR is only updated aftera commit, because the actual database delete occurs in the ON-INSERT trigger, whichis executed at commit. The SOTLCUR temporary table provides a pre-commit lookat current and active curriculum rows.SOQOLIB,SRAQUIK,SRARECR,SAAQUIK,SAAADMS,SGASTDN,SFAREGS,SHADEGR(#1-10EC07)Description: If a student had an existing curriculum on a current SGASTDN record,and SAAQUIK was used to change the curriculum, using the Clear Record functionin the Curriculum block removed the existing SGATSDN curriculum, leaving onlythe curriculum that had been entered on SAAQUIK.Impact: Users had to use the Insert Record function to create a new record and notthe Clear Record function.Resolution: Triggers have been modified in the SORLCUR and SORLCUR_LITEblocks to correct this.APIssokb%, sokd%(#1-QA6PU)Description: The dynamic update statements executed by the DML packages do notfully use bind variables for all runtime values. This causes extra hard parsing of newcursors at runtime and affects system performance by increasing parsing overhead,cached cursors, and latch contention. This level of latch contention was notanticipated when the DML update architecture was first designed, and the bestmethod to correct the situation is being researched. It is not recommended thatinstitutions use the session setting CURSOR_SHARING= FORCE in the meantime, asthis appears to create other performance behavior that is difficult to diagnose. Thisissue occurs across Banner products, including Self-Service products.Impact: Processes that use the APIs may experience slow performance.Resolution: The affected objects were passed through a conversion process tochange the DML p_update procedure to use an explicit update rather than adynamic update. The objects are:• sokb_admissions1.sql• sokb_app_decision1.sql• sokb_catlg_intpart1.sql• sokb_course_reg1.sql• sokb_enr_ver_pay1.sql• sokb_enr_ver_serve1.sql• sokb_enrollment1.sql• sokb_faculty1.sql• sokb_filedelimiter1.sql• sokb_filetestscore1.sqlFebruary 2007 Student Release 7.3.2Confidential Release Guide 127
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:
Page 50 and 51:
Page 52 and 53:
Page 54 and 55:
Page 56 and 57:
Page 58 and 59:
Page 60 and 61:
Section 3 Miscellaneous Enhancement
Page 62 and 63:
Page 64 and 65:
Page 66 and 67:
Page 68 and 69:
Page 70 and 71:
Page 72 and 73:
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 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 125: Section 4 Problem ResolutionsOveral
Page 129 and 130: Section 4 Problem ResolutionsValida
Page 131 and 132: Section 4 - Problem ResolutionsSamp
Page 177 and 178:
Section 4 - Problem ResolutionsSamp
Page 179 and 180:
Section 4 - Problem ResolutionsSamp
show all

Banner Student / Release Guide / 7.3.2

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?