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-04-13 22:00:19 +00:00
parent 9c2d3ea3e4
commit f85b9cbee3
1 changed files with 12 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
ayanova/devdocs/todo.txt
View File

@@ -240,6 +240,8 @@ OVERALL
- load and stress test on client
todo: introduce menu item for woitem table descendant view (not wired up yet, just there to remind and as placeholder)
todo: status control should require click to open dialog which shows list of all status prior and allows to add then close to view
this way it's clear how to change, less confusing than now and easy to get at the list
@@ -255,16 +257,22 @@ todo: Translations stuff
- clean up translation text, many things are badly worded for wo like all *List could just use plural form and be shorter
as coding it look for areas to be cleaned up
todo: UI wo descendants data table exposure (old v7 wo tree nav pane ui)
people probably want them / it's an easy way to see certain things you can't see any other way
I don't want to put them into the main menu, however I could expose them as menu options from the workorderlist itself
expose them as menu options from the workorderlist itself
so user goes to Main Workorders DataTable and in there with the extensions etc is an option to
select items list from menu -> Workorderitems -> select parts list from menu -> Parts
So at wo list level you can switch to items level
at items level you can select any grandhild level and see a datalist for that level
but only top level exposed in navigation pane menu
WorkOrder is *still* the main key in all these sub tables
Sub tables all rows have column for Workorder itself as main key / openable object for row
You cannot open a workorderItem for example directly, it's an entire workorder
though it may center upon the item as preselected row??
fastest system might be a "focus(atype,id)" property in Router, workorder form opens, tree is walked to find the record and the full path to it is selected at each level
e.g. if it's a sched user id 45 then wo finds it in the tree and then selects it's woitem first then the scheduser next in grid (if more than one of each)
that way it's there to edit / view from one click in the sub table grid
Reports and bulk ops all use full workorder object so it's up to the report maintainer how they show
todo: Should workorderitemloan be included in contract discounting system??[v.Next?]