From eb3be1b3bb0f955b709fd75b9fb4c6aeff44635b Mon Sep 17 00:00:00 2001 From: John Cardinal Date: Fri, 13 Dec 2019 21:32:18 +0000 Subject: [PATCH] --- devdocs/specs/core-ui-design.txt | 55 ++++++++++++++++++++++++++++++++ 1 file changed, 55 insertions(+) diff --git a/devdocs/specs/core-ui-design.txt b/devdocs/specs/core-ui-design.txt index 7beac0d7..f6d58cc0 100644 --- a/devdocs/specs/core-ui-design.txt +++ b/devdocs/specs/core-ui-design.txt @@ -33,6 +33,61 @@ Requirements - or for a Ops person they can plunk down on their dashboard a current server status widget or active jobs widget etc +FOR REFERENCE HERE IS THE v7 NAV panel LAYOUT: +- V7 nav panel is like this: + - DASHBOARD + - SERVICE + - All levels of workorders of this type + - Templates for workorders of this type + - QUOTES + - All levels of workorders of this type + - Templates for workorders of this type + - PREVENTIVE MAINTENANCE + - All levels of workorders of this type + - Templates for workorders of this type + - SCHEDULE + - INVENTORY + - parts + - po's + - po items (weird) + - po receipts + - po receipt items (also weird) + - adjustments + - adjustment items (strange) + - part inventory + - part requests + - CLIENTS (CUSTOMERS) + - clients (customers) + - head offices + - contracts + - projects + - customer service requests + - UNITS + - units + - unit models + - loan items + - VENDORS + - vendors + - CURRENT USER + - memos + - notification subscriptions + - notification deliveries + - wiki page (personal, wtf?) + - SEARCH + - ADMINISTRATION + - global settings + - regions + - security groups + - users + - custom field design + - localized text design + - notification deliveries (last 7 days) + - report templates + - files in database + - schedule markers (wtf forgot about this what's it for again?) + + + =-=-=-=-=-= This is a worked example to determine what UI elements should be where using the Client as the example object type: