From 6b3f0432e93080fd84f1bba1a7c68df6e659cce1 Mon Sep 17 00:00:00 2001 From: John Cardinal Date: Wed, 6 May 2020 14:07:11 +0000 Subject: [PATCH] --- ayanova/devdocs/todo.txt | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/ayanova/devdocs/todo.txt b/ayanova/devdocs/todo.txt index 9953b70b..80e0ff59 100644 --- a/ayanova/devdocs/todo.txt +++ b/ayanova/devdocs/todo.txt @@ -88,6 +88,7 @@ todo: PLANNING workorder data and class and route structure: likely follows biz object decision Use foreign keys!! Consider UI in this as well, will need to decide at least what is visible when + Workorder UI good ideas here: https://rockfish.ayanova.com/default.htm#!/rfcaseEdit/3475 How to add items, like new woitem? send to server get back new object? lots of biz rules and stuff need to happen, want to minimize load at client @@ -104,6 +105,8 @@ todo: PLANNING workorder data and class and route structure: Just make them Units with extra properties exposed if type of loaner? This seems simplest, but what will it effect? Hard to make them serviceable if they are an alternate table of source for what's being repaired as that breaks a lot of other code or adds exceptions + Customer is then who exactly because it's fundamental to a lot of wo functionality? + from a biz perspective isn't it like you are your own customer when you service your own equipment that you loan out? @@ -725,6 +728,9 @@ todo: workorder UI layout stuff (TTM!! Don't re-invent the wheel!) There's been a lot of ideas about wo floating around and considered, but at the end of the day what we have works so maybe try to meld into what we have the new concepts and see what comes out. Support a rich wo UI on big screens and scroll around UI on phone maybe. some notes: + Workorder UI good ideas here: https://rockfish.ayanova.com/default.htm#!/rfcaseEdit/3475 + Basically (based on RI) it boils down to don't make the user go up to the workorder item level when they can go sideways directly to an alternate child of woitem + i.e. going from parts to labor shouldn't require going up a level All workorder in one document and just really really tall? (people bitch about RI requiring too many navigation steps to get to shit) Header and items in one document then bottom in seperate pages? Is it going to be far easier to code this bitch if I have all the workorder data at hand or..?