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-01-05 01:05:57 +00:00
parent 37d9a3e9bc
commit 3c3264a123
4 changed files with 17 additions and 32 deletions
Download Patch File Download Diff File Expand all files Collapse all files

21
ayanova/devdocs/todo.txt
View File

@@ -5,20 +5,7 @@
MISC ITEMS THAT CAME UP
todo: idea - move sublists into menu option in grid list and edit form
e.g. Unit Models doesn't really need to sit always in the nav panel to the left and it's getting crowded in the service "pane" anyway so
Move the unitModels into the menu of the Units list and into the menu of the Unit edit form and remove from the Service nav panel
do this with other things as well
This way it's accessible from 4 places:
within the form itself as a quick jump from the picklist (albeit to a single edit form only )
within the units grid menu as unitmodels list
within the units list itself as a item they can click on in the column
and within the edit from menu as it's list form
I think it's intuitive becuase rather than the old v7 subgrids which was a bit of a wet blanket UX wise, at least this way it's where you would expect with the relevant object it applies to
If think of it like that as being with the object you would select it on (and replicated to anywhere you would select it) then it's intuitive for the user to look there and far cleaner for the UI
todo: consider moving service contracts to Accounting area?
todo: Notification at server has NotifyDeliveryLog object unused and no UI at from for it either
it's supposed to keep a set queue of the past 90 days of deliveries for troubleshooting like in v7,
@@ -33,11 +20,9 @@ todo: figure out the datalistview form slowness when typing into the name field,
todo: in many areas I'm potentially using unnecessary v-row elements, only one is necessary
Do a quick search for v-row and see what's what
todo: unitmodel, maybe can make a combo unique constraint for the model number or name by combining with the vendorID
it's doubtful two models from the same vendor would have the same model number so this covers that case or am I wrong on that?
purpose of this is to catch duplicate entries while still supporting duplicate model numbers
todo: rename translation for unitmodel upc to "bar code"
Except it's not a "bar" code necessary, there is probably a better term for a scanable code..."Scan code"?
todo: Smoke test for servicebank
todo: smoke test for opening edit form, missed a bunch see unitmodels for example