This commit is contained in:
@@ -1,10 +1,15 @@
|
||||
PRIORITY - ALWAYS Lowest level stuff first
|
||||
=-=-=-=-
|
||||
|
||||
todo: add long polling notification route (CLIENT AND SERVER)
|
||||
https://rockfish.ayanova.com/default.htm#!/rfcaseEdit/3507
|
||||
- Need way to acknowledge receipt of long poll info from client to server so that it can be removed or something?
|
||||
- maybe successfull sending clears it regardless of client?
|
||||
todo: change trial detection route that client first hits
|
||||
- make it a different controller and renamed to something like server ping or "hello" or something friendly and useful
|
||||
- maybe the route that gets Notifications
|
||||
- because there could be a notificatoin type that doesn't need logged in users for general server down announcements etc
|
||||
- because there could be a notificatoin type that doesn't need logged in users for general server down announcements etc
|
||||
|
||||
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
|
||||
@@ -12,10 +17,8 @@ todo: Search get search result for workorder descendents doesn't fit into existi
|
||||
- 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
|
||||
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: add long polling notification route (CLIENT AND SERVER)
|
||||
https://rockfish.ayanova.com/default.htm#!/rfcaseEdit/3507
|
||||
- Need way to acknowledge receipt of long poll info from client to server so that it can be removed or something?
|
||||
- maybe successfull sending clears it regardless of client?
|
||||
todo: schema, move all initializing stuff to schema update 1
|
||||
right now it's 11 but that's weird
|
||||
todo: ability to mass tag items from list (SERVER AND CLIENT)
|
||||
- also a good way to do an initial implementation of a mass ops UI code
|
||||
todo: ability to mass rename a tag to something else in all objects (SERVER AND CLIENT)
|
||||
|
||||
Reference in New Issue
Block a user