Banner Student / Release Guide / 7.3.2

More documents

Recommendations

Info

Section 4 Problem ResolutionsAdmissions Module2. In SAADCRV, the WHEN_NEW_BLOCK_INSTANCE_TRG trigger has been modifiedto not perform the query at When New Block Instance time. This query is nowperformed at When New Record Instance time.The WHEN-NEW-RECORD-INSTANCE triggers on the SARADAP and SOVLCURblocks have been modified to only requery details when the key data in thechild record does not match the key data in the parent record.SAQOLIB,SAAQUAN,SAADCRV,SAARRATSAQOLIB,SAARRAT,SAAACKL,SAADCBT,SAADCRV,SAAQUAN(#1-PFG5L)Description: Multiple forms may not show the correct application data after anupdate is performed on SOASUPL.Impact: When supplemental information was entered (SOASUPL) for a particularapplication and term and multiple applications existed for that term and ID, itwould cause other application forms to retrieve only the application that wasupdated on SOASUPL. (The other forms were SAAQUAN, SAARRAT, SAADCRV.)The user had to execute a query on SAAADMS for the ID and term and then accessthe forms to correct the situation.Resolution: After a field is updated on SOASUPL, when other Admissions forms areaccessed, the term and application number are being passed, which is restricting therows that are displayed. This has been corrected by adding new triggers andupdating existing triggers and other code.Also, it was possible to use the Search button from the Prior College field inSOASUPL to access SOISBGI while you were still in the Key Block. The button hasbeen disabled while you are in the Key Block. It is not enabled until you are in theSupplemental or Agency Data block.(#1-QGYKR)Description: SAARRAT and SAADCBT allowed you to delete a SARADAP record,which left orphaned SORLCUR and SORLFOS records. When you saved thechanges, the SARADAP record was deleted, unless it had child records. As inSAADCRV, SAAACKL, and SAAQUAN, you should not be able to delete SARADAPrecords using SAARRAT or SAADCBT.Impact: It was possible for a user to delete an application record, perhaps byaccident, in a manner that would not also remove all child records dependent uponthe application record.Resolution: Triggers have been added to the SARADAP block that display an InvalidMessage error. Also, the Insert Allowed and Delete Allowed properties have been setto No. The forms involved have been recompiled.ReportsSARETPG(#1-PE666)Description: When the report is run, the output is not correct. Either no output isproduced, or the report stops before it is finished, and no control report is created.Records are deleted from the database.Student Release 7.3.2 February 2007106 Release Guide Confidential
Section 4 Problem ResolutionsGeneral Student ModuleImpact: The report is not producing correct output for users.Resolution: Process header changes and RELEASE variable changes have beenremoved.SARETPG(#CMS-DFCT97929)Description: The process was not deleting records from the Electronic AdmissionsEmployment Table (SAREMPL).Impact: Not all records were being purged.Resolution: The process has been modified to compare the APPL_SEQNO to theSAREMPL_APPL_SEQNO, instead of to the SAREMPL_AIDM.SARRATE(#1-16DYXY)Description: SARRATE was not considering the rating type code (STVRATP)entered in the Rating Type parameter when the Recalculate Existing Ratingsparameter was set to Y. For example, if an applicant had two ratings on SAARRAT,one with a rating type of ACAD and another with a rating type of GP, and SARRATEwas run with a rating type of GPA, the ACAD and GPA ratings were updated. Also,both ratings appear to have been updated using GPA calculations (SAARRDF).Impact: Inaccurate ratings were being produced.Resolution: The UPDATE SARRRAT has been changed to include andsarrrat_ratp_code = :in_ratp_code in the WHERE clause.General Student ModuleFunctionsSGFCORT(#1-IMT3J)Description: When data was selected using f_concat_sgrchrt, data was incorrectlyreturned for a term when the cohort had already been ended on SGASADD.Impact: Object:Access data from this view would report a student in a cohort thathas been discontinued/stopped for a given term.Resolution: In the f_concat_sgrchrt function, the get_sgrchrt cursor looked atany term code that was less than or equal to the incoming term code. It now looksat only the maximum effective term code to retrieve the current cohort.SGFADVR(#CMS-DFCT102290)Description: The AS_STUDENT_DATA view was incorrectly displaying advisors forstudents that were no longer effective. When an advisor was removed from a studentFebruary 2007 Student Release 7.3.2Confidential Release Guide 107
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: 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 105: Section 4 Problem ResolutionsAdmiss
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 157 and 158:
Section 4 - Problem ResolutionsSamp
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?