diff --git a/docs/assets/images/build/bom_add_item.png b/docs/assets/images/build/bom_add_item.png index a535629..c51310e 100644 Binary files a/docs/assets/images/build/bom_add_item.png and b/docs/assets/images/build/bom_add_item.png differ diff --git a/docs/assets/images/build/bom_invalid.png b/docs/assets/images/build/bom_invalid.png index f6fa0e2..0a74416 100644 Binary files a/docs/assets/images/build/bom_invalid.png and b/docs/assets/images/build/bom_invalid.png differ diff --git a/docs/assets/images/build/bom_select_fields.png b/docs/assets/images/build/bom_select_fields.png index dd46a07..67d8e8a 100644 Binary files a/docs/assets/images/build/bom_select_fields.png and b/docs/assets/images/build/bom_select_fields.png differ diff --git a/docs/assets/images/build/bom_select_parts.png b/docs/assets/images/build/bom_select_parts.png index eaa77a0..447bdfd 100644 Binary files a/docs/assets/images/build/bom_select_parts.png and b/docs/assets/images/build/bom_select_parts.png differ diff --git a/docs/assets/images/build/bom_upload_file.png b/docs/assets/images/build/bom_upload_file.png index a070bd0..c01dcf1 100644 Binary files a/docs/assets/images/build/bom_upload_file.png and b/docs/assets/images/build/bom_upload_file.png differ diff --git a/docs/assets/images/build/bom_valid.png b/docs/assets/images/build/bom_valid.png index dfd6dd3..304a429 100644 Binary files a/docs/assets/images/build/bom_valid.png and b/docs/assets/images/build/bom_valid.png differ diff --git a/docs/assets/images/build/build_list.png b/docs/assets/images/build/build_list.png new file mode 100644 index 0000000..0ee12a7 Binary files /dev/null and b/docs/assets/images/build/build_list.png differ diff --git a/docs/assets/images/build/build_start_new.png b/docs/assets/images/build/build_start_new.png deleted file mode 100644 index 0868f91..0000000 Binary files a/docs/assets/images/build/build_start_new.png and /dev/null differ diff --git a/docs/build/bom.md b/docs/build/bom.md index 73b8c66..c90c9d0 100644 --- a/docs/build/bom.md +++ b/docs/build/bom.md @@ -116,7 +116,7 @@ Once the BOM file is uploaded, the following view will load: {% include 'img.html' %} {% endwith %} -InvenTree will attempt to automatically match the BOM file columns with InvenTree part fields. `Part_Name` is a **required** field for the upload process and moving on to the next step. Sprcifying the `Part_IPN` field matching is very powerful as it allows to create direct pointers to InvenTree parts. +InvenTree will attempt to automatically match the BOM file columns with InvenTree part fields. `Part_Name` is a **required** field for the upload process and moving on to the next step. Specifying the `Part_IPN` field matching is very powerful as it allows to create direct pointers to InvenTree parts. Once you have selected the corresponding InvenTree fields, click on the "Submit Selections" button to move on to the next step. @@ -129,9 +129,6 @@ Once the BOM file columns and InvenTree fields are correctly matched, the follow InvenTree automatically tries to match parts from the BOM file with parts in its database. For parts that are found in InvenTree's database, the `Select Part` field selection will automatically point to the matching database part. -!!! info "Create New Part" - The icon in the `Select Part` column let's you load the `Create New Part` form which allows you to create an InvenTree part during the BOM upload process. - In this view, you can also edit the parts `Reference` and `Quantity` fields. Once you have selected the corresponding InvenTree parts, click on the "Submit BOM" button to complete the BOM upload process. diff --git a/docs/build/build.md b/docs/build/build.md index 4c7d32d..d9dde1f 100644 --- a/docs/build/build.md +++ b/docs/build/build.md @@ -4,7 +4,7 @@ title: Build Orders ## Build Orders -A *Build Order* is used to create new stock by assembling component parts, according to a [Bill of Materials](./bom.md)(BOM). +A *Build Order* is used to create new stock by assembling component parts, according to a [Bill of Materials](./bom.md) (BOM). A BOM can be specified for any [Part](../part/part.md) which is designated as an *Assembly*. The BOM consists of other Parts which are designated as *Components*. @@ -22,6 +22,10 @@ To navigate to the Build Order display, select *Build* from the main navigation *Table View* provides a table of Build Orders, which can be filtered to only show the orders you are interested in. +{% with id="build_list", url="build/build_list.png", description="Build List" %} +{% include "img.html" %} +{% endwith %} + #### Calendar View *Calendar View* shows a calendar display with upcoming build orders, based on the various dates specified for each build. @@ -165,19 +169,11 @@ To create a build order for your part, you have two options: ### Build Order Page - Navigate to the Build Order overview page -- Select *New Build Order* - ------ - -Either of these options will launch the *Start new Build* form: - -{% with id="build_start_new", url="build/build_start_new.png", description="Start New Build Form" %} -{% include 'img.html' %} -{% endwith %} +- Click on *New Build Order* Fill-out the form as required, then click the "Submit" button to create the build. -### Complete Build Order +## Complete Build Order To complete a build, click on icon on the build detail page, the `Complete Build` form will be displayed.