From 6c2439967517796b9f5ff104aca61357b0d4eda1 Mon Sep 17 00:00:00 2001 From: Michael Date: Mon, 19 Dec 2022 21:59:01 +0100 Subject: [PATCH] Fixed misunderstanding of can_complete (#405) * started python API reference guide * Added test to the API reference guide * Added Price break * added context variables to the build section * Cleand up build section and added new example * Fine tuning * fixed picture * removed unfinished python reference guide * Added allocated_stock to the build rreport * Added contect variables for user model * Added link to user in build.md * Fixed misunderstanding of can_complete --- docs/report/build.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/report/build.md b/docs/report/build.md index 7ba819e..4986bf3 100644 --- a/docs/report/build.md +++ b/docs/report/build.md @@ -31,7 +31,8 @@ The following variables are accessed by build.variable | active | Boolean that tells if the build is active | | batch | Batch code transferred to build parts (optional) | | bom_items | A query set with all BOM items for the build | -| can_complete | Boolean that tells if the build can be completed ( all material allocated)| +| can_complete | Boolean that tells if the build can be completed. Means: All material allocated and all parts have been build. | +| are_untracked_parts_allocated | Boolean that tells if all bom_items have allocated stock_items. | | creation_date | Date where the build has been created | | completion_date | Date the build was completed (or, if incomplete, the expected date of completion) | | completed_by | The [User](./context_variables.md#user) that completed the build |