This commit is contained in:
@@ -198,7 +198,16 @@ todo: in UI the workorder state should show current state but be expandable to v
|
||||
Also, this will be best for sites that don't really use the state fully and just want to ignore it or set it once to completed, that kind of thing
|
||||
so maybe it's a single / collection depending on if there are more than one but collapsable??
|
||||
|
||||
todo: Workorder -> WorkorderService now can combine tables all together under workorder
|
||||
todo: workorderitemstatus was shared with workorder status, but now workorder status is a big independant thing
|
||||
could make them tags, but then people lose the color flag which they might depend on and is technically useful I guess
|
||||
could make a new separate workorderitemstatus collection
|
||||
I want people to move away from using items like individual workorders in favor of just making more workorders so I wouldn't want to expose it like before, but they could just hide it or it's hidden by default
|
||||
Is a separate item status useful? I guess if it can be hidden then it's a moot point, people that need it will expose it, people that don't can hide it
|
||||
|
||||
todo: UI big unresolved question: am I going to expose the workorder children as separate lists in the 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
|
||||
so user goes to workorders select items list from menu -> Workorderitems -> select parts list from menu -> Parts
|
||||
|
||||
todo: WorkorderBiz "modernize" follow the norms of other objects
|
||||
explicitly decouple the graph from each other, currently I think it's set to force transaction for all graph but in reality it should just be separate objects loosely coupled
|
||||
|
||||
Reference in New Issue
Block a user