This commit is contained in:
@@ -175,7 +175,8 @@ todo: lots of stuff, but next maybe is the most fundamental stuff like child col
|
||||
|
||||
|
||||
PO UI for items:
|
||||
|
||||
NEW ITEM button in po list header
|
||||
NEW ITEM button in po item edit form (so can just keep entering)
|
||||
|
||||
Edit mode ideally will not navigate but will open an edit dialog in place which will act on things from within the same form
|
||||
Receive all PO form menu item if applicable that just receives the entire PO as is for a shortcut
|
||||
@@ -191,11 +192,14 @@ 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
|
||||
what I want to happen is it skips existing numbers
|
||||
not many serialized objects, maybe a utility to do wahtever, renumbering with them could be done for just that purpose entirely
|
||||
(along with resetting the autoid number)
|
||||
Does this require a special role?
|
||||
|
||||
|
||||
|
||||
|
||||
Reference in New Issue
Block a user