CBORD User Group Conference 2018

1. CBORD User Group Conference 2018 Odyssey – Converting from PCS UI to Adminweb

2. Converting from Odyssey PCS UI to Adminweb Tuesday 10/10/2018 11:00pm – 12:00pm Presented by: Michael J Schutte

3. Converting from Odyssey PCS UI to Adminweb Transitioning from UI (User Interface) to Adminweb

4. Converting from Odyssey PCS UI to Adminweb • For many sites this will be a stopping point in the upgrade process. Along with the UI being eliminated many parts of the software have to be manually moved from client to client. • When a site is wanting to upgrade to the newest versions of Odyssey 18.2.6597 the server will have new requirements. Odyssey will only install on Windows Server 2012 and Windows Server 2016. • Last version of Odyssey to have UI is 8.0.6441 • Transitioning from UI (User Interface) to Adminweb

5. Converting from Odyssey PCS UI to Adminweb Transitioning from UI (User Interface) to Adminweb Reporting in Odyssey UI Reporting in Adminweb Printing of End of Day reports Printing of Queued reports Placing reports in files Emailed Reports Odyssey has to have access to an email server. Access and reporting require email delivery Reports have to be converted to web client so data has to be updated Reports at minimum will need to email Placing reports in a File requires SMB protocol. Folder has to be shared with a user stored in software

6. Converting from Odyssey PCS UI to Adminweb Transitioning from UI (User Interface) to Adminweb Webadmin Requires Email Host name or IP is requires SMTP Port is require if not port 25(default) User Name / Password only if required Encryption if necessary This requires it to be saved, Parameters being reloaded and Event Service on the Odyssey server being restarted

7. Converting from Odyssey PCS UI to Adminweb Transitioning from UI (User Interface) to Adminweb Converting Legacy Reports Login to Odyssey (Webadmin) Select Reports and in the Dropdown Select Legacy Reports

8. Converting from Odyssey PCS UI to Adminweb Transitioning from UI (User Interface) to Adminweb Converting Legacy Reports In Legacy Reports make sure to check box to Hide Converted – this will eliminate duplicates User the convert button to proceed in moving the Legacy Report into the Saved Reports area

9. Converting from Odyssey PCS UI to Adminweb Transitioning from UI (User Interface) to Adminweb Converting Legacy Reports In Legacy Reports make sure to check box to Hide Converted – this will eliminate duplicates User the convert button to proceed in moving the Legacy Report into the Saved Reports area

10. Converting from Odyssey PCS UI to Adminweb Transitioning from UI (User Interface) to Adminweb Converting Legacy Reports In the Converting process Odyssey automatically changes to new tables for Transaction and Patron information 1st stop is the Filtering area for the report It should not require any changes Use the next button to shift to the Sort Order Page then Next again for the Destination Page

11. Converting from Odyssey PCS UI to Adminweb Transitioning from UI (User Interface) to Adminweb Converting Legacy Reports • The Report Description will transfer but changing this Description will allow you to organize reports by location, user, timing • Café, Gift Shop, Coffee shop • John’s, Bill’s, Sally’s • Daily, Weekly, Monthly • File Format (PDF or Excel data only) • Place it in a Queue • This Queue needs to be schedule to run in the Adminweb • Save Report – will add to list of saved reports • Public vs Private Report • Public – any user can see or edit • Private – (unchecked) converting you are the owner and will be the only user that can see the report in saved reports • Run Report Now – This will allow the process run immediately

12. Converting from Odyssey PCS UI to Adminweb Transitioning from UI (User Interface) to Adminweb Converting Legacy Reports • Send the report via email • To as may recipients as needed • Separate accounts with Semi-Colon or Comma depending on email server rules • Send to a remote SFTP server • This requires credentials and paths to be set up • Send to a shared folder • Requires true SMB protocol • Only works on site owned servers • Must be local folder or true UNC path • Finish completes the process

13. Converting from Odyssey PCS UI to Adminweb Transitioning from UI (User Interface) to Adminweb Exporting in Odyssey UI Exporting in Adminweb • Delivery of Exports • Email • SFTP • Local Folder on site owned servers • Filtering process has changed to new tables • No Conversion tool • All exports have to be hand moved • Exports have to have an extension • .txt • .cvs • Delivery of Exports • Local folders • UNC mapped folders • Tables have changed • No conversion tool

14. Converting from Odyssey PCS UI to Adminweb Transitioning from UI (User Interface) to Adminweb Exports • Re-Creating Exports • Export Types • Data • Photos • Filename • File Format • Delimited (Comma) • Delimited (Tab) • Fix Width • MS Excel 2007 (.xlsx) • Destination Method • Send the export via email • Add timestamp to filename • Send to a remote SFTP server • Credentials need to be setup to use • Send to a shared folder • Credentials/Path need to be setup to use

15. Converting from Odyssey PCS UI to Adminweb Transitioning from UI (User Interface) to Adminweb Exports • Export Fields • Fields have changed and you have to be very cautious • For example Card Number Field is in lots of categories depending on export criteria • Activity Transaction • Patron • Student Advantage Member info • Student Advantage Transactions • Transactions • Filters are available based on Fields selected • Sorting is available based on Field selected • Header and Footer (no requirement) • Summary • Export description – How it shows in save exports • Make Public – who can see and edit • Run Now or not ** Reports are placed in Queues only under settings in Queues

16. Converting from Odyssey PCS UI to Adminweb Transitioning from UI (User Interface) to Adminweb Scheduler • All scheduled tasks in the Task Handler need to be manually moved to Scheduler in Adminweb • Support or an Engineer will need to assist in moving Database backup • Once task is moved and operational in Adminweb deactivate it in the UI • EOD (End of Day) needs to have email addresses added • This will ensure the End of Day File Verification Report and the End of Day Logged Transaction Summary Report • Daily Database Purge should be scheduled

17. Questions?

18. Last Helpful Trick of the AdminwebOne of the biggest issues I have had and had comments about Adminweb is that if you are working on something in Odyssey and need to check data in an other module but if you navigate away from your current page you have to start over. If you open Odyssey in another webpage and complete the other task it overrides your original page and you still have to start over. This is caused because the 2 pages use the same cache from the browser. **Resolved open Adminweb in different browser and you can completed different tasks in different modules at the same time with the same user.

19. Michael J SchutteSr. System EngineerCBORD 950 Danby Road, Suite 100CIthaca, NY 14850Tel: 844.GO.CBORD (844.462.2673)| Cell:  402.707.0368 mjs2@cbord.comwww.cbord.com

20. We want your feedback! Please evaluate this session in the ERMobile app. Your feedback helps usimprove future sessions. Find this session in the app,and touch COMPLETE SESSION SURVEY. Thank you!