This commit is contained in:
@@ -170,23 +170,20 @@ todo: how to add locale keys in future after release without erasing all data?
|
||||
|
||||
CURRENTLY DOING: PurchaseOrder
|
||||
|
||||
todo: lots of stuff, but next maybe is the most fundamental stuff like child collection error handling, form customization and required rule handling
|
||||
if doing that then see up above the SERVER section has the notes on implementation. Think workorder while coding that as the wo will have *many* child collections
|
||||
|
||||
|
||||
PO UI for items:
|
||||
todo duplicate common rules in UI that are enforced by server if any
|
||||
|
||||
|
||||
|
||||
PO todo
|
||||
todo: test new from scratch po
|
||||
todo: test duplicate route
|
||||
todo: test inventory affecting ops
|
||||
reversals, updates, deletes etc
|
||||
todo: test default tax codes are set
|
||||
todo: test form customization hide child collection items
|
||||
todo: test required rule and server errors display correctly / clear in both poitems table row and in edit form for poitem when opened
|
||||
make up fake rules if necessary just to confirm the new child collection error handling works
|
||||
todo: test new from scratch po
|
||||
|
||||
|
||||
todo: test read only form of PO
|
||||
todo: test reports, tagging etc
|
||||
todo: can edit po number but if I set an existing po number 4 to 23 for example and the last autogenerated is 22 it will happily make another 23 so there are now two
|
||||
|
||||
Reference in New Issue
Block a user