Banner Student / Release Guide / 7.3.2

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