- Obsolete inventory is now considered
on-hand(reflected on stock counters)
[fix]Unable to adjust or move obsolete inventory
beta channel brings you the most recent features.
Looking for the most stable releases? Check out the main channel instead.
Settings - General - Check updates
Team Workspaces it is recommended for all users to use the same version of the app so everyone has access to the same features.
New feature: Internal Part Number generator. Internal part numbers can now be automatically generated. The part number consists of a simple counter: every time a new part number is generated, the counter is incremented. You can also define multiple Series. Each Series keeps its own counter and add a prefix to the generated part number. If enabled, internal part numbers are generated whenever manually creating parts, bulk importing parts, or creating parts through the API.
New feature: Obsolete Inventory. You can now change the status of available inventory, from available to obsolete (and vice-versa). The status can be changed by simply editing selected inventory (right-click and
Edit inventory...). Obsolete inventory is inventory that's no longer usable but which you still want to keep track of. Obsolete inventory is ignored for all purposes other than tracking it and for calculating a part's
Revcolumn has been added which allows you to list revisioned inventory to be purchased (not necessarily for in-house parts)
When importing a BOM, a
Unit of Measurecolumn might be mapped. If mapped, it is used to determine the unit of measure in case it's not included in the value mapped in
Qty. This should be useful when the software you use to generate a BOM doesn't include the unit of measure along with the quantity.
Defining depth when importing tree-structured data (e.g. Storage and Labels): a setting was added (Settings - General - Import) which allows to define a character that should be used to denote depth. This way you can have names that include a dash
-, the character previously used (and still used by default) to denote depth in tree-structured data.
Barcodes: a setting was added (Settings - Barcodes) which allows the description on a detailed barcode label to wrap either at a character or word.
When adding parts and quantities into a purchase order from a purchase list, the unit of measure used in the purchase order will match the one from the selected quote. For example: if a purchase list indicates 150 screws to be purchased and you selected a quote with pricing for a "Box-of-100", you'd need to buy 2 "Box-of-100", being that quantity and unit of measure to be listed in the purchase order.
Calendar: events can be drag-and-dropped in order to change its date
- Production plans can now be imported through a CSV file
- When "going-to" something (e.g. a part), if filters are active and possibly preventing the item to show up on the table, a popup is displayed informing you of that including a button to quickly close filters so the item would become visible
- API: when creating parts,
categoryfield can be passed
- History: storage events are logged (storage created, moved or removed)
- When importing CSV files, the fields to map are now double-sorted: first by required ones and then alphabetically
- Some minor UI improvements
- Support for Future Electronics API added
- API: history endpoints added
- The app now detects identical parts whenever importing or manually creating parts. Identical parts are parts with the same Part Number but identical Manufacturer (e.g. "Wurth Electronics" vs "Würth Elektronik"). By default, identical parts are considered the same. When importing parts you'll be warned about identical parts, if any, and given an option to manually confirm if those parts are meant to be considered the same or not.
This should prevent having multiple parts listed on the app that actually represent the same one. Before, a different Manufacturer for the same Part Number would always be considered as a different part whenever importing or manually creating a part. Once created, parts are still considered unique / different based on both Part Number and Manufacturer as different manufacturers might use the same part number.
- A search input (Filter...) for basic search was added to the
- This release introduces barcode actions. With barcode actions you can acomplish a task, such as adding, removing or moving inventory by scanning a sequence of barcodes and without keyboard or mouse intervention. To initiate a barcode action all you need to do is to scan the barcode of one of the available actions on this Barcode Actions PDF and then the app will inform you of the next barcodes you should scan in order to finish it.
- The timeout the app uses to process incoming barcodes as been reduced from 200ms to 100ms to make barcode scanning faster. You might want to increase this value though in case you use slower barcode scanners. That can be done from
Settings - Barcodes.
- Requests to third-party APIs run in parallel, resulting in less time waiting for quotes
- Octopart/Nexar API can now be disabled (only used when searching for quotes). This might be useful if you prefer to only use the supported third-party APIs (DigiKey, Mouser, etc), so the app doesn't spend time fetching quotes from Octopart.
- Element14 API can now use a customer ID so you get custom pricing straight from Element14 stores (Farnell, Newark)
- Support for
[fix]View selector: items not draggable
[fix]Chance for error at startup when documents with URL have been created through the API
- You can now use third-party APIs from online suppliers such as Mouser, Digikey and Element14 (Farnell, Newark). These APIs allow you to get pricing information and quotes directly from these suppliers or distributors. You'll have to get your API key from each of these suppliers and each one of these will have different conditions and limits (e.g. maximum number of requests) which you should check. The app takes care of caching and ensures maximum requests per minute is respected for every supported API service. Currently, APIs from Digikey, Mouser and Element14 (Farnell and Newark) are supported but more are expected in the future.
- BOM settings were moved to the
Settingsdialog (instead of being accessible from the Product or Production tabs)
- Company information can be added under
Settings - Workspace. This information is then included on exported PDFs for sales orders and purchase orders
- API: endpoint
- This release introduces BOM Instructions. BOM instructions allow you to create steps that should be followed during assembly. A BOM instruction can reference items in the BOM and documents and notes can be added into it as well.
During production you can then change the status of each step from
- Files can now be drag-and-dropped onto tables. Tables that can import data through a CSV file will accept CSV files (except purchase orders). Files can also be dropped into Document tables, both on the global table as well as on the Documents table that belong to things (i.e. parts, etc). In this case, the file is saved/uploaded to the workspace itself and becomes listed on the thing it refers to.
- Calendar: you have now access to a calendar to better and more easily visualize important dates (deadlines). Just look for the calendar button that, if available, should be right next to the filters button (see below). Right now you have access to a calendar in: sales orders (delivery dates), production plans (dates by which products should be assembled) and production builds (dates by which production should have inventory reserved and has been fully assembled)
/documentsendpoins added so you can get and set documents for things in the app (i.e. for parts, etc)