mirror of
https://github.com/inventree/InvenTree.git
synced 2025-10-14 21:22:20 +00:00
Partial build output complete (#10499)
* Handle partial completion of build output * Add 'quantity' field to BuildOutputComplete API endpoint * Allow partial scrapping of build outputs * Adjust column text * Adjust "complete build output" form * Change order of operations when completing build output - Run validation checks *before* potentially splitting stock item * Extract quantity from serializer * Documentation - Update screenshots - Add note on partial completion - Add note on partial scrapping * Update CHANGELOG.md * Update API version * Add unit test for partial scrapping * Tweak text * Unit test for partial output completion * Fix validation check for quantity field * Adjust playwright tests
This commit is contained in:
Binary file not shown.
Before Width: | Height: | Size: 106 KiB After Width: | Height: | Size: 36 KiB |
Binary file not shown.
Before Width: | Height: | Size: 141 KiB After Width: | Height: | Size: 42 KiB |
@@ -70,6 +70,18 @@ The following options are available when completing a build output:
|
||||
| Notes | Any additional notes associated with the completion of these outputs |
|
||||
| Accept Incomplete Allocation | If selected, this option allows [tracked build outputs](./allocate.md#tracked-build-outputs) to be completed in the case where required BOM items have not been fully allocated |
|
||||
|
||||
### Partial Completion
|
||||
|
||||
A build output may be *partially completed* by specifying a quantity less than the total quantity of that build output. In such a case, the following actions are performed:
|
||||
|
||||
- The incomplete build output is "split" into two separate build outputs
|
||||
- The specified quantity is marked as completed, and the completed build quantity is increased accordingly
|
||||
- The remaining quantity is left as an incomplete build output, available for future completion
|
||||
|
||||
!!! note "Serialized Outputs"
|
||||
Serialized build outputs cannot be partially completed.
|
||||
|
||||
|
||||
## Scrap Build Output
|
||||
|
||||
*Scrapping* a build output marks the particular output as rejected, in the context of the given build order.
|
||||
@@ -95,6 +107,17 @@ The following options are available when scrapping a build order:
|
||||
| Notes | Any additional notes associated with the scrapping of these outputs |
|
||||
| Discard Allocations | If selected, any installed BOM items will be removed first, before marking the build output as scrapped. Use this option if the installed items are recoverable and can be used elsewhere |
|
||||
|
||||
### Partial Scrapping
|
||||
|
||||
A build output may be *partially scrapped* by specifying a quantity less than the total quantity of that build output. In such a case, the following actions are performed:
|
||||
|
||||
- The incomplete build output is "split" into two separate build outputs
|
||||
- The specified quantity is marked as scrapped, and the completed build quantity is *not* increased
|
||||
- The remaining quantity is left as an incomplete build output, available for future completion
|
||||
|
||||
!!! note "Serialized Outputs"
|
||||
Serialized build outputs cannot be partially scrapped.
|
||||
|
||||
## Cancel Build Output
|
||||
|
||||
*Cancelling* a build output causes the build output to be deleted, and removed from the database entirely. Use this option when the build output does not physically exist (or was never built) and should not be tracked in the database.
|
||||
|
Reference in New Issue
Block a user