11.07.2015 Views

Banner Student / Release Guide / 7.3.2

Banner Student / Release Guide / 7.3.2

Banner Student / Release Guide / 7.3.2

SHOW MORE
SHOW LESS
  • No tags were found...

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Section 4 Problem ResolutionsAdmissions ModuleTherefore, you could not use the Application Summary block to select thecorrect application.2. If you navigated back to the Batch Entry block, the Application Summary blockreverted back to the display of the first application, instead of displaying theapplication that was being viewed.Impact: Users were uncertain that they were entering a decision on the correctapplication for individuals who had multiple applications in the system.Resolution: These issues have been corrected.1. In SAQOLIB, the WHEN-NEW-RECORD-INSTANCE trigger in the SARADAP blockhas been modified to navigate to the HOST_BLOCK in some cases, so theappropriate HOST_BLOCK triggers are fired.2. In SAADCBT, the PRE-TEXT-ITEM trigger in the SARDSCL_TERM_CODE item inthe SARDSCL block has been relocated to the first navigable item in the block(SARDSCL_ID), so the Term Code and Application Number will be populatedwhen the user navigates into the block. This populate will use the SARADAPterm code.The WHEN-VALIDATE-ITEM trigger on the SARDSCL_ID and SARDSCL_APPL_NOitems in the SARDSCL block has been modified to use the SARDSCL termcode, if known, when validation is performed. Otherwise, the Key Block termcode will be used, if it is known.SAQOLIB,SAADCRV(#1-PS5M2)Description: Two issues existed:1. The curriculum data that was displayed was not always the correct data for thedecision and application that were displayed.2. The last application was always displayed when you clicked into the ApplicationSummary block or used the scroll bar in the block.Impact: When an applicant had multiple applications, users were not confident thatthey had entered an admission decision on the correct application. Also, navigatingthrough existing application records was more cumbersome that it should havebeen.Resolution: These issues have been corrected.1. In SAQOLIB, the WHEN-NEW-RECORD-INSTANCE trigger in the SARADAP blockhas been redesigned to not loop through all SARADAP records, and insteadjust query the SORLCUR and SORLFOS records for the current SARADAPrecord. The query is only performed when the SARADAP or SORLCUR recordhas changed.The WHEN-NEW-RECORD-INSTANCE trigger on the SOVLCUR block has alsobeen modified to not query SORLFOS records unless the SORLCUR recordhas changed.February 2007 <strong>Student</strong> <strong>Release</strong> <strong>7.3.2</strong>Confidential <strong>Release</strong> <strong>Guide</strong> 105

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!