This commit is contained in:
@@ -10,10 +10,18 @@
|
|||||||
Ideally would like to see event of interest check with cached data but need to consider how many different things would be in that, could be huge
|
Ideally would like to see event of interest check with cached data but need to consider how many different things would be in that, could be huge
|
||||||
since I will be adding so many new notification types and they are more complex.
|
since I will be adding so many new notification types and they are more complex.
|
||||||
|
|
||||||
|
client end is a list type form also each object can notify directly on demand and all users have default notification subscription
|
||||||
|
|
||||||
|
No longer templating but rather using short single text string with link back to open instead and optionally send report / attachment or whatever
|
||||||
|
also no delivery days or hours fuckery anymore, all deliveries happen all the time as appropriate to the event deliver date. If user wants that they can configure
|
||||||
|
their device email notification settings, not our concern anymore.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
Important cases:
|
Important cases:
|
||||||
client viewing ui (was popup in v7) https://rockfish.ayanova.com/default.htm#!/rfcaseEdit/3783
|
client viewing ui (was popup in v7) https://rockfish.ayanova.com/default.htm#!/rfcaseEdit/3783
|
||||||
Restrict to involved people only: https://rockfish.ayanova.com/default.htm#!/rfcaseEdit/892
|
|
||||||
|
|
||||||
|
|
||||||
ALL EVENT TYPES INITIAL RELEASE
|
ALL EVENT TYPES INITIAL RELEASE
|
||||||
|
|||||||
@@ -14,9 +14,28 @@ todo: Search get search result for workorder descendents doesn't fit into existi
|
|||||||
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
|
||||||
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: tags - does server ensure only unique tags are saved even if there are dupes in the list?
|
||||||
todo: ability to mass rename a tag to something else in all objects (SERVER AND CLIENT)
|
|
||||||
|
MASS TAG OPS
|
||||||
|
NOTE: separate routes for seperate things just to avoid issues, i.e. dont' conflate two different functions in same route
|
||||||
|
i.e. search and replace, not search and remove
|
||||||
|
NOTE: no mass tag op route will work with every object in order for safety, there arent' *that* many objects so safer to have people pick them from a list and if they want they can manually check all types
|
||||||
|
note: they can use a datalist to select so no need to add any filtering ability here
|
||||||
|
|
||||||
|
todo: SET TAGS ability to mass tag items from list (SERVER AND CLIENT)
|
||||||
|
route: mass tag by type and id collection
|
||||||
|
route: mass tag by type and all objects no id specified
|
||||||
|
|
||||||
|
todo: REPLACE TAGS
|
||||||
|
route: mass replace one tag with another tag by type and id collection
|
||||||
|
route: mass repalce one tag with another tag by type and all objects no collection
|
||||||
|
|
||||||
|
todo: REMOVE TAGS
|
||||||
|
route: mass remove specified tag by type and id collection
|
||||||
|
route: mass remove tag by type and all objects no id specified
|
||||||
|
|
||||||
|
|
||||||
todo: api / server landing page is shitty on a mobile
|
todo: api / server landing page is shitty on a mobile
|
||||||
and really just shitty, add a logo or some shit
|
and really just shitty, add a logo or some shit
|
||||||
todo: Should server show uptime somewhere?
|
todo: Should server show uptime somewhere?
|
||||||
|
|||||||
Reference in New Issue
Block a user