Banner Student / Release Guide / 7.3.2

Section 4 Problem ResolutionsAdmissions ModuleFormsSAAACKL(#1-X01EY)Description: You could not remove the Received Date value in the ApplicationChecklist window of SAAADMS when the Item value was cross-referenced toSTVTESC. You could do this on SAAACKL.Impact: As a result of this issue, users may be confused by the inconsistent behaviorbetween SAAADMS and SAAACKL with respect to the proper way to blank out theReceived Date field for a checklist item where the value comes from SOAHSCH,SOAPCOL, SOATEST, or GOAINTL.Resolution: These issues have been resolved:1. When the received date for a checklist item defaults from SOAHSCH,SOAPCOL, SOATES, or GOAINTL, and you remove the value from theApplication Checklist window, the value is automatically repopulated when thechanges are saved.The SARCHKL.ON-COMMIT trigger has been modified to update the receiveddate on existing checklist items and update the application status.2. When any checklist item record is updated, that record is the active recordafter the transaction is saved.The SARCHKL.KEY-COMMIT trigger has been updated to scroll to theappropriate checklist item row, as well as to the appropriate SARADAP row.3. When a checklist item is entered manually, you could not use Tab to access theCount field.The property palette for the SARCHKL_REQ_COUNT has been updated.SAAADMS,SAAACKL(#1-12Z6Z8)Description: When you attempted to insert a new checklist item (with a user-definedchecklist source code) in the Application Checklist window on SAAADMS, thesystem-required value of BASELINE was defaulted. You had to save the new item as abaseline value and then update the checklist origin to the desired value fromSTVCKSR. You should have been able to select a value from the List of Values whenthe record was inserted.Impact: Users could not enter a user-defined checklist source code for a checklistitem in SAAADMS or SAAACKL without first saving the record and then updatingit. This caused extra work for users.Resolution: The SARCHKL.PRE-INSERT triggers on SAAADMS and SAAACKL havebeen updated. The SARCHKL_CKSR_CODE will only be changed to BASELEINE if thevalue is NULL. Code was also removed that initiated the SARCHKL_REQ_COUNT to 1.February 2007 Student Release 7.3.2Confidential Release Guide 95