This commit is contained in:
@@ -1,16 +1,26 @@
|
|||||||
PRIORITY - ALWAYS Lowest level stuff first
|
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
|
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
|
- 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
|
- so all child objects need a typeandid of the immediate parent
|
||||||
- Not sure where to document this so putting it here for reference
|
- 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
|
- 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
|
- 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 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: 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
|
todo: schema, move all initializing stuff to schema update 1
|
||||||
right now it's 11 but that's weird
|
right now it's 11 but that's weird
|
||||||
|
|||||||
Reference in New Issue
Block a user