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...

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

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Section 4 Problem ResolutionsSchedule ModuleImpact: The CRN field Search button not usable, and the user must use a CountQuery Hits function to access the section search.Resolution: Code has been modified to correct this. The Search button is nowavailable.SSAMATXSSAMATXSSAMATX(#CMS-DFCT71410)Description: Previously, the Query Term field was populated with the term fromSSASECT. Now, this no longer happens.Impact: SSAMATX does not default the query term from the last term used onSSASECT, and the user must reenter the data.Resolution: A new trigger has been added, and triggers have been modified to copythe global term correctly.(#CMS-DFCT76076)Description: When you used the scroll bar to access a field for a query, and youclicked into the field, the form scrolled back to its original position.Impact: Users could not see what to enter for the query when this happened.Resolution: Triggers have been modified in the SSRMEET block to scroll farther tothe right when fields are entered. Triggers have also been modified to reset thescrolling canvas position.(#CMS-DFCT94243)Description: When the start date was part of the search criteria for a query, an errorwas received: Unable to resolve reference to item SSRMEET_TBA_DAY, FRM-40505:ORACLE error-Unable to perform QUERY.Impact: Users were unable to perform queries using the start date without receivingan error.Resolution: The SSRMEET_PRE_QUERY program unit has been modified to ensurethat records returned from a query have start and end date and/or start and endtime values that are between any requested date and time values. The query lengthon the SSRMEET_END_DATE has been changed from 11 to 14 to prevent any issues forrecords returned by a query.SSASECT,sokb_section1.sql(#1-STQRZ)Description: Users could not update the integration partner code on SSASECT afterthe 7.3.0.1 version of sokb_section1.sql had been applied, when no registrationrecords existed for the section.Impact: Users were not able to update the Integration Partner field for an existingsection (CRN).Resolution: In sokb_section1.sql, the f_isequal and thep_overlay_validation_rec have been modified to include the integrationpartner code (INTG_CODE).February 2007 <strong>Student</strong> <strong>Release</strong> <strong>7.3.2</strong>Confidential <strong>Release</strong> <strong>Guide</strong> 75

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

Saved successfully!

Ooh no, something went wrong!