# Admin Tool Discussion ## Admin stuffs: In the Appointment Service Domain: * **Things we probably should be able to do:** * Resource: * Edit Resource data * integrations (email, SYCLE/TCM id) ## Discuss Task Name vs Entity Name based navigational approach: * Below is a few ideas for scenarios I could come up with * Both approaches require a process * Both approaches require communicating said process * In either case, we can use 'smart' UI to help guide the user: * Flavor Text * Gated actions * **Scenarios:** * **Add an integration for "Peter Parker":** * What does this mean? * I need to know what type of integration to add * In the case of TCM or Sycle * I need to link Peter Parker's shop to the corresponding TCM/Sycle Shop Id * I need to link Peter Parker's Resource to the corresponding TCM/Sycle Resource Id * In the case of Outlook * I need to set up the user's Integration configuration (e.g. write policy) * **Once Peter Parker has both a shop and resource integration configured** * Safe way to test Peter Parker? * Communicate Peter Parker is set up? * Set up Peter Parker's availability * Set Peter Parker to 'active' * **Set Peter Parker to inactive:** * Find resource * Click Active Toggle to 'off' position (change background from green to grey) * **Perform a manual action on an Appointment:** * **Scenario A** - Someone deleted an appointment directly from external calendar: * What is the best way to react to this? * One possible solution: * Find Appointment: * Search by resource, appointment, or shop * Display manual actions to cancel or delete depending on best practice * Display (clickable and copy-able) links to reschedule/cancel via appointment UI? * **Scenario B** - Appointment is created in SF but not in resource's calendar: * Assuming appointment appears in appointment service * What is the best way to react to this? * Will this be an ongoing issue? * Is this an issue or a side-effect of the process? * What unintended side-effects may happen if this is automated? * **Scenario C** - Resource becomes unavailable unexpectedly: * What is the best way to react to this? * What is the impact on data AND human resources? * How will appointments and orders etc. be reconciled? * How will customers be notified? * Is this a problem worth solving with code or just process? * What if anything can we do to lessen impact or automate aspects of this scenario? ## Future/Scope Creep but relevant ideas: * Republish things * Administratively edit appointments * IT side of things, is there any quick links or shortcuts which can be made? * quick links to viewing queues * quick links to viewing pods * quick links to viewing New Relic Logs * etc. * Resource * Active status (toggle switch simplicity) * Appointment: * Edit Appointment data * status * reschedule/cancel - link to app * republish? * Appointment Type Configurations: * Edit? * Create? * Other things?: