ayanova/devdocs/todo.txt

@@ -55,8 +55,76 @@ TODO: Time to LOCK IN the layout of main shell as the grids and much other stuff
 			- ? Consider if any can be consolidated, 12 is a lot and many things are the same things, also quote , pm service wo all have many levels but I'm guessing I won't be doing it that way again so maybe all types can go into a single top level service item  and then each one is a single item
 				- i.e. take away the tree for service workorders -> items and only have service workorders?  Is this doable?
 	- NAVIGATION PANEL and ROLES
-		- RAVEN nav panels are supposed to comparmentalize by roles which is a good idea so 
-			- Subitems should go into the appropriate role, not necessarily as it was in v7
+		- RAVEN nav panels have nothing to do with roles, roles only determine what is available to user
+		- Panels and items sb grouped as is business task appropriate or same as v7 if in doubt
+	- 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?)
+	
+	- RAVEN PROPOSED NAV PANEL
+		- HOME (was dashboard)
+			- summary of key info relevant to logged in user?
+			- If they aren't tech related at all then other things besides scheduled workorders?
+			- Do we need this at all?
+			- Useful for a service tech point of view but not really if you're an ops person
+			- A customer had thoughts on the dashboard:
+				- case 1974: shootnsharp@thesoileaus.com "In my opinion, the dashboard would be much more functional and valuable if I could determine how many work orders show on the screen and possibly even what statuses (or be able to sort by status, priority, etc.) The At a Glance stats of Service Rate Quantity is helpful but would be even more relevant if it showed what was approaching due date, overdue, waiting on parts, pending parts requests, items on loan stats, preventative maintenance work orders approaching and overdue. Having the capability to customize the Dashboard is key because each Service business has its own metrics that are most important to its business."
+		- SERVICE
+		- DISPATCH
+		- INVENTORY
+		- ACCOUNTING
+		- ADMINISTRATION
+		- OPERATIONS CONSOLE
+
+
 	- TTM 
 		- This is increasingly becoming the driving force here
 		- Not going with the fancy modular recomposable UI and I know v7 style will work	
@@ -160,7 +228,7 @@ TODO: MAIN GRID LIST ANALYSIS, DESIGN AND COMPLETION KEEPING IN MIND TTM
 		- Needs to remember last settings (stored centrally) like filter used, number of rows etc
 			- When user opens up AyaNova it should always look the same in each area as last time they were there
 
-
+TODO: change LT for OPerations console and remove "console" (main nav panel)
 
 TODO: Make errorBoxError message box on all forms a component instead as it's just boilerplate