Oliver
11ab0203b1
* Add builtin plugin for auto-issuing orders * Add plugin to auto-issue orders * Add placeholder documentation * Fix typo * Adds image macro - To replace img.html - includes checking if file exists * Fix tooltips * More docs * Adjust plugin settings filters * docs * More docs * More docs * Updates * Less restrictive URL checking * Refactor build order page * Fix typo * Allow 429 * Debug output * More debug * Construct assets dir * Cleanup * Update docs README * Refactoring more pages * Fix image link * Fix SSO settings * Add hook to check for missing settings - Ensure that all settings are documented! * Add missing user settings * Update docstring * Tweak SSO.md * Image updates * More updates * Tweaks * Exclude orders without a target_date * Fix for issuing build orders * Further refactoring * Fixes * Image refactoring * More refactoring * More refactoring * Refactor app images * Fix pathing issues * Suppress some openapidocs warnings in logs (much easier to debug docs build issues) * Fix image reference * Reduce error messages * Fix image links * Fix image links * Reduce docs log output * Ensure settings are loaded before displaying them * Fix for UI test * Fix unit test * Test tweaks
3.6 KiB
title
| title |
|---|
| Release 0.1.4 |
Release 0.1.4
Release 0.1.4 (November 2020) provides a number of major new features and improvements, as well as some crucial bug fixes:
Build Management System
The build management system has received a major upgrade, bringing the following improvements:
Partial Build Completion
Previously, build orders had to be completed atomically (i.e. if the build order was to create 20x units, then all 20x units had to be created at once).
The new build system allows the user to specify build outputs (of varying quantities) against a given build order. The build order cannot be completed until all build outputs are fulfilled.
A Build Output is simply a StockItem object which is marked as in production. This stock item can be assigned a (unique) serial number which is useful for pre-allocation purposes. It also allows stock to be filtered by production status and determine how many units are being built.
Stock Item Tracking
Parts which are marked as trackable are now treated differently for the purpose of a build order. Stock items must be assigned against each build output (as was the case previously). When a build output is marked as complete, any trackable stock items which are assigned to that build output are installed into the build output (which is simply a StockItem). In this manner, if a trackable stock item is used to build another stock item, it remains tracked via the stock item it is installed into.
Stock items which are not trackable are simply removed from stock when the build output is completed.
Stock Allocation Improvements
A number of UX improvements have been made to simplify the process of allocating stock items against a build output (and thus a build order).
Related Parts
Related Part denotes a relationship between two parts, when users want to show their usage is "related" to another part or simply emphasize a link between two parts.
Implementation
- New PartRelated model/table to store relationships between parts (requires migration)
- New Related tab shown in Part detail page
- Ability to add relationships between parts through both main and admin interfaces
- Can only manage relationship if user has "change" permission on Part ruleset
InvenTree "Global" Settings
Global settings control the default value of fields across the entire web interface, for all-users.
Also, dedicated settings sections were added for:
- Category
- Build
- Purchase Order
- Sales Order
For Category section, read Category Parameter Templates
Other section allows to set the prefix of build, purchase and sales orders.
Category Parameter Templates
Added support for configuring parameter templates defined by categories.
Features
- User can now setup a list of parameter templates for each (or all) part category(ies) in InvenTree settings
- During part creation, part parameters are automatically created using the list of parameter templates from the parent category it belongs to (if option is enabled)
Currency Support
A more comprehensive implementation of Currency support has been implemented.
Using the django-money library enables native support for all currency types, and the (future) possibility of offering real-time currency conversion.
This update is "simply" an architectural change which will allow more comprehensive currency management in a future release.
As part of the new currency library implementation, InvenTree can now track purchase price of stock items (in whichever currency the user chooses).