admin/raven-client
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Browse Source
This commit is contained in:
John Cardinal
2021-06-16 21:59:36 +00:00
parent e144a8fbab
commit e1912d5f14
1 changed files with 6 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
ayanova/devdocs/todo.txt
View File

@@ -370,7 +370,6 @@ TODO: //MIGRATE_OUTSTANDING comment tag
todo: many biz objects are not using new PUT methodology todo: many biz objects are not using new PUT methodology
Might be because new methodology assumes complete PUT object as a entire replacement not a partial update Might be because new methodology assumes complete PUT object as a entire replacement not a partial update
some of these objects (User) do partial updates so.... some of these objects (User) do partial updates so....
also this includes *all* of the initial workorder object so there's that
might be that they don't need it but for consistency should check into it might be that they don't need it but for consistency should check into it
@@ -383,15 +382,7 @@ todo: many biz objects are not using new PUT methodology
CURRENTLY DOING: CURRENTLY DOING: turn off "direct notification" menu options for customer type users
todo 3: workorder notifications to code and test:
todo test this
TODO: Hiding sections not used when empty and now added from the menu to present a cleaner empty work order TODO: Hiding sections not used when empty and now added from the menu to present a cleaner empty work order
@@ -401,6 +392,10 @@ TODO: Hiding sections not used when empty and now added from the menu to present
add from fab floating action button when new? add from fab floating action button when new?
something that stays so users can use either way so no confusion about shifting UI elements that disappear something that stays so users can use either way so no confusion about shifting UI elements that disappear
todo: check Joyce's cases
--------- TEST RELEASE HERE ---------------
todo: notify event list table needs to show status of workorder (all fields) ideally todo: notify event list table needs to show status of workorder (all fields) ideally
otherwise if you have multiple wostatusage notifications they all appear the same otherwise if you have multiple wostatusage notifications they all appear the same