1. Application Support, System Configuration & Permission Management James Hill Maytas PS Team Leader Enhance your knowledge, improve your organisation

2. Sync / Force Sync Updating and maintaining the report library Basics Individual Maytas Permissions Group Maytas Permissions Web User Editor Permissions Creating new fields & new centres Creating new lookups Creating new tables DB Schema Overview of the new Maytas Config Editor Maytas 5 Config Release management Multiple environments for development and testing Best Practice What will this session cover?

3. Enhance your knowledge, improve your organisation Items that require a Sync (M5$_SYNCTABLES) - New centres, lookups and fields - New tabs & controls - New processes & command mappings - New objectives (TRMODULE) & templates - New vacancy attributes & vacancy matching criteria - New schemes When to Force Sync? A force sync has a network wide effect and will force all users to sync when they log back into Maytas 5. When a force sync is triggered Maytas 5 will collect all changes and update the local configuration data file accordingly. When to Sync and when to Force Sync? Basics

4. Enhance your knowledge, improve your organisation Report Library updates are contained in all major Maytas releases. Users are required to import the relevant report library file and then run the Reports Upgrade SQL. Modular reports (e.g. PFR, QSR, Sales Pipeline etc) are also updated frequently and users should ensure these are imported. Manage and maintain the report library removing any unnecessary reports! http://DFM18W1-LT-LA/reports Updating and maintaining the report library

5. Enhance your knowledge, improve your organisation Individual User Permissions Group User Permissions Web User Permissions Permission Management

6. Enhance your knowledge, improve your organisation

7. DB Schema Creating new fields and new centres New field lookups and indexing User Created Tables

8. Enhance your knowledge, improve your organisation

9. Maytas 5 Config Editor

10. Enhance your knowledge, improve your organisation Multiple Environments -Separate instances for LIVE & TEST (potentially TRAINING & DEV) -For different versions different servers required! Release Testing -With multiple environments across different servers you can implement different Maytas and e-track versions for release testing -Develop an internal testing plan to verify new releases then deploy on LIVE. Environments for User Training & Process, Tab and Reporting Development -Multiple environments ensure training can take place in non-live environment -Allows you to prepare and update internal documentation ahead of deploying release onto LIVE. -Processes, tabs and reports can be created in TEST or DEV and then exported/imported to LIVE Best Practice Recommendations

11. Application Support, System Configuration & Permission Management james.hill@tribalgroup.com james.hill@tribalgroup.com Maytas PS Team Leader Enhance your knowledge, improve your organisation