From 652eacb8877ebc6654cf5564fc95b523e3bba00c Mon Sep 17 00:00:00 2001 From: John Cardinal Date: Fri, 15 May 2020 22:10:30 +0000 Subject: [PATCH] --- devdocs/todo.txt | 20 -------------------- 1 file changed, 20 deletions(-) diff --git a/devdocs/todo.txt b/devdocs/todo.txt index 1df92034..92beaf3a 100644 --- a/devdocs/todo.txt +++ b/devdocs/todo.txt @@ -1,26 +1,6 @@ PRIORITY - ALWAYS Lowest level stuff first =-=-=-=- -todo: Search get search result for workorder descendents doesn't fit into existing system due to it being a biz object wide feature but workorder having sub-get results - - CHILD objects need to point to their parent and be readable in code for searching and for opening objects based on child object - - so all child objects need a typeandid of the immediate parent - - Not sure where to document this so putting it here for reference - - Required for opening a search result of a descendent that is not directly openable an - - Need parent AyaType as an ENUM ATTRIBUTE in the AyaType table for easy traversal - ACTION: - I think simplest and most effective would be a route / public static biz function that will get the openable ancestor of a type and id - Workorder graph are all search indexed by their exact type each - When search comes looking for a result it grabs the exact type - Search result list will have exact type - Only needed to open the parent item - So client sees a type that is not directly openable and queries server for ancestor / principle to open - In Client, navigating to exact item e.g. a workorder item part is a client ui issue really - The only issue related to the server is getting the top most parent openable object, the workorder in this case - the rest can be done at the client easily - Add Search controller route: ancestor(ayatype, ayaid) returns type and id, if no higher ancestor returns what came in - this needs to be a central route, not tied to an object though objects can handle the inner workings maybe i.e. wokorderbiz for workorder tree , pobiz for po tree etc - - todo: search tables in schema, I think there is a missing index here, need to look at the search query section again as it was changed several times from the original schema creation todo: schema, move all initializing stuff to schema update 1 right now it's 11 but that's weird