1 / 11

Application Support, System Configuration & Permission Management

Application Support, System Configuration & Permission Management. James Hill Maytas PS Team Leader. Enhance your knowledge, improve your organisation. What will this session cover?. Enhance your knowledge, improve your organisation. Basics. When to Sync and when to Force Sync ?.

wood
Télécharger la présentation

Application Support, System Configuration & Permission Management

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

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

  2. What will this session cover? Enhance your knowledge, improve your organisation

  3. Basics When to Sync and when to Force Sync? 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. Enhance your knowledge, improve your organisation

  4. Updating and maintaining the report library 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 Enhance your knowledge, improve your organisation

  5. Permission Management Enhance your knowledge, improve your organisation

  6. Enhance your knowledge, improve your organisation

  7. DB Schema Enhance your knowledge, improve your organisation

  8. Enhance your knowledge, improve your organisation

  9. Maytas 5 Config Editor Enhance your knowledge, improve your organisation

  10. Best Practice Recommendations • 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 Enhance your knowledge, improve your organisation

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

More Related