This commit is contained in:
@@ -175,13 +175,10 @@ CURRENTLY DOING: PurchaseOrder
|
|||||||
|
|
||||||
PO todo
|
PO todo
|
||||||
|
|
||||||
todo: button to set part price from received cost
|
|
||||||
todo: restock required feature
|
todo: restock required feature
|
||||||
dialog? See notes case 3849
|
dialog? See notes case 3849
|
||||||
todo: MIGRATE_OUTSTANDING note for part requests feature
|
todo: MIGRATE_OUTSTANDING note for part requests feature
|
||||||
maybe add UI button etc for it even with no actual list / form or whatever
|
maybe add UI button etc for it even with no actual list / form or whatever
|
||||||
todo: test add / remove serials via any and all updates changes to po items
|
|
||||||
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
|
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
|
what I want to happen is it skips existing numbers
|
||||||
Research this method and how we can work with it and give it a good think because it maybe a dangerous thing to expose or just fuckery
|
Research this method and how we can work with it and give it a good think because it maybe a dangerous thing to expose or just fuckery
|
||||||
@@ -189,10 +186,29 @@ todo: can edit po number but if I set an existing po number 4 to 23 for example
|
|||||||
not many serialized objects, maybe a utility to do wahtever, renumbering with them could be done for just that purpose entirely
|
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)
|
(along with resetting the autoid number)
|
||||||
Should this operation require a special role?
|
Should this operation require a special role?
|
||||||
i.e. if logged in as a bizadmin full then can edit serials
|
i.e. if logged in as a bizadmin full then can edit serials
|
||||||
|
|
||||||
|
|
||||||
|
todo: test add / remove serials via any and all updates changes to po items
|
||||||
|
todo: test reports, tagging etc
|
||||||
todo: review PO cases and see what I missed
|
todo: review PO cases and see what I missed
|
||||||
todo: if joyce testing PO try to test concurrency issues around quantities and serials etc
|
|
||||||
it shouldn't get out of whack no matter what is thrown at it
|
todo: Post update for testing
|
||||||
|
todo: Joyce testing PO / inventory / inventory adjustments
|
||||||
|
part cost update feature works properly
|
||||||
|
two concurrent edits same object doesn't fuck up inventory (last loses)
|
||||||
|
inventory is always adjusted properly with correct balance when
|
||||||
|
po deleted
|
||||||
|
po items received after created and saved without receipt
|
||||||
|
po item receive qty adjusted
|
||||||
|
po item created with received qty in one save
|
||||||
|
po item part changed
|
||||||
|
po item warehouse changed
|
||||||
|
po item vendor change should update vendor part number if there is one for that vendor
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user