SCT Banner YES Training Team s6

SCT Banner YES Technical Team Meeting Minutes

1 Meeting Logistics Item Description Date October 10, 2005 Time 1:30 p.m. – 3:00 p.m. Location Meshel Hall Large Conference Room

2 Attendees Role Name Facilitator Troy Cross Note Taker Troy Cross Participants Troy Cross, John Dalbec, Marayamah Hassan, Tom Masters, Cleo Nastopoulos and Doug Sewell. Not Present James (J.T.) Holt, Dennis Konik, Mary Noble, Sandy Stanhope, Jeff Trimble and Mark Welton. Guest Ray Hess, Cameron Hughes, Dona Madacsi and Rick Marsico.

3 Minutes Topic Notes Minutes – 10/10/2005 Fourteenth Meeting 1. Minutes from Everyone received minutes from previous meeting. No updates required. 09/26/2005 meeting Old Business 2. Expanded No update. Not a high priority. Check to see if this is still an issue with Banner 7. message screen locks up 3. Oracle Utilities No update. 4. Interface from No update. Low priority. Banner to AccuMail and back needed 5. SCT e~Print Delayed. Rick, Dona and Troy still need to determine staff for this assignment. 6. Legacy and Testing continuing. Results look good. Should be ready by Friday, October 14. Banner Data Synchronization 7. Source Code Doug continues reviewing the documentation and creating some documentation of his Management own. 8. Object Access Rick, Dona and Troy still need to determine staff for this assignment. MS Access Views Support reports on end-user’s workstations do not allow the reports to be shared easily and may not be backed up. 9. Draft policy to Low priority task on DBA list of tasks. ID/install Banner patches 10. IntelleCheck Waiting for Accounts Payable to test. Need to re-implement change in PPR7.

YES Technical Minutes Page 1 of 3 11. TFRBILL Doug restored files for Tom. Bad input and lack of understanding process caused data to be purged. Tom is continuing researching how process works. 12. YSU_DEV1 Role Give developers YSU_DEV1 role in TEST, PPRD and DUP instances. 13. Developer PROD was cloned into TEST last week. Cleo asked when PROD will be cloned into Instance PPRD. 14. Finance Update No update. 15. Advancement No update. Update 16. Luminis Update John attended Content Planning workshop last week. Carol is testing Calendaring functions. Giving user administration rights caused issues with Messenger Express. Modify for YSU look and feel. 17. Banner 7 Update Doug said that Banner 7 upgrade activities are continuing. All modules are upgraded to 7.1 and Financial Aid is upgraded to 7.2 in PPR7. An additional 7 patches were applied with this upgrade. Additional upgrading remains. May be completed before Friday due date. New Business Timeouts Banner 6 INB timeout removed. Banner 7 INB timeout increased from 30 minutes to 180 minutes (3 hours). Banner 6 & 7 SSB timeouts increased from 30 minutes to 180 minutes (3 hours). Oracle timeouts were increased from 65 minutes to 185 minutes. So, the INB timeout should kick in for Banner 7 INB, the Oracle timeout should kick in for Banner 6 and the SSB timeouts should kick in for Banner 6 & 7 SSB. The Oracle timeout seems to be a little more forgiving for INB users than the INB timeout since you seem to be able to click Help/Technical Support/Reconnect to Database and remain on your form. That is, the INB timeout requires you to close your IE session and the Oracle timeout does not. Troy will perform some additional testing. We may want to remove the INB timeout from Banner 7 and rely on the Oracle timeout. If the Oracle timeout is more forgiving, we may be able to decrease the timeout value. MicroFocus COBOL Carol asked me to add an item to the agenda concerning using MicroFocus COBOL for developing standard canned reports in Banner. Tom, Cameron and others discussed the pros and cons of the various products that can be used for Banner and Oracle development. Cameron passed out pages 30 and 31 from Jim Petro’s Performance Assessment. Tom mentioned that he thought that Banner Job Submission should be used for Banner reporting requirements. Doug and Troy agreed. Troy mentioned that Banner Job Submission reports can easily be implemented in AppWorx (our scheduling product). Cameron said that the legacy to Banner synchronization is not using Banner Job Submission. Systems development also expressed concerns over which platform (server or client side) they should use for development and what editors could be used. Most thought that we should not restrict the staff to certain technologies but let them determine the best solution for the task at hand. Rick suggested that systems development schedule weekly one hour meetings for the staff to show what they are doing with newer technologies.

4 Action Items Action Item Owner Due Date Status Action items and issues from 01/28/2005 1. Expanded Troy 11/30/2005 Not a high priority. Check to see if this is still an message screen issue with Banner 7. locks up 2. Oracle Utilities Technical Staff 12/31/2005 Evaluation of PL/SQL Developer and TOAD

YES Technical Minutes Page 2 of 3 continuing. Action items and issues from 02/28/2005 3. Interface from Technical Team Delayed Delayed until needed. Banner to AccuMail and back needed 4. SCT e~Print Rick/Dona/Troy Delayed Determine technical staff for this assignment. Action items and issues from 04/18/2005 5. Legacy and Marayamah, 10/14/2005 Testing continuing. Banner Data Cleo, Cameron, Synchronization Maureen and others Action items and issues from 05/16/2005 6. Source code Doug and 10/31/2005 Develop initial procedures. management Technical Staff Action items and issues from 09/12/2005 7. Object Access Rick/Dona/Troy 10/24/2005 Rick, Dona and Troy need to determine staff for this Views Support assignment. 8. Draft policy to Sandy 12/31/2005 Draft initial policy. ID/install Banner patches Action items and issues from 09/26/2005 9. IntelleCheck Elaine Beatty ? Waiting for Accounts Payable to test. Need to re- implement change in PPR7. 10. TFRBILL Doug Completed Restore TFRBILL list and log files for Tom’s review. 11. YSU_DEV1 Role Kirk/Sandy 10/31/2005 Give developers YSU_DEV1 role in TEST, PPRD and DUP. 12. Developer Dona/Troy 10/24/2005 Create work team to determine both a short and long Instance term solution to systems development’s need. Action items and issues from 10/10/2005 13. Systems Dona/Rick 10/24/2005 Schedule weekly one hour meetings for the systems Development development staff to show what they are doing with Weekly Meetings newer technologies.

YES Technical Minutes Page 3 of 3