This commit is contained in:
@@ -365,6 +365,15 @@ todo: many biz objects are not using new PUT methodology
|
||||
CURRENTLY DOING: workorder round two electric boogaloo
|
||||
basics first then increasingly esoteric features
|
||||
|
||||
currently: request button implementations
|
||||
make the button actually do the work
|
||||
trigger a route that adds a request and then insert it into the object tree so it appears
|
||||
maybe though it's done from the parts form but signals to the svc-workorder header to do the actual work??
|
||||
or maybe better in the part form as a separation of concerns issue and part does have access to the full object so can
|
||||
easily insert it into the tree!!!!!!
|
||||
handle the case where the inventory changes after error but before click
|
||||
both ways: has enough all of a sudden or has even less all of a sudden
|
||||
|
||||
Biggies
|
||||
todo 3: actual inventory
|
||||
1961 / 3752- auto remove from inventory immediately when wo saved and re-instate if changed
|
||||
@@ -383,8 +392,9 @@ todo: No inventory setting *IMPORTANT* must test with inventory turned off for t
|
||||
so this must be replicated in v8 exactly and dynamically, not from server itself, but server must still check at last moment of save and return error if unavailable
|
||||
See v7 project workorderform.cs line 8878 for the code in question
|
||||
Proper error messages that are localized and must display correctly in UI at the source of the woitempart error
|
||||
|
||||
|
||||
todo: workorder save method is using a shallow clone by reference for each object NOT a copy as intended which is killing the error system as UID is being wiped
|
||||
See Part save for a clone method using json parse and stringify, but maybe that's shit and need something better
|
||||
|
||||
todo 3: service bank
|
||||
todo 3: notification
|
||||
|
||||
Reference in New Issue
Block a user