Product Comments Fix

1. An issue with product comments in has been resolved. It was found that in older builds (pre-2023), when a formula driven product had comments placed into it and the product was redrawn from the database, the comments would be updated with the product drawing. This was not the case with newer builds, however. With this fix, product comments in the product list should be updated when a product is redrawn from the database. 
   

Nest Tools Order Fix

 

1. An issue reportedly occurred when using multi-tools, wherein 900 tools would be used in an incorrect order during certain operations, with tools order varying back and forth, rather than each tool completing the full sequence it is expected to in a routing operation, unless one manually assigns route priority. For example, during testing, when using tools 911 and 912 assigned to a double line routing operation, the tools would, rather than complete their assigned steps, alternate on a step-by-step basis. This issue has been resolved, and nesting tools should now operate in their proper order (tools completing their intended steps in the operation) without requiring manual assignment.
   

Multipass Rule Fix

1. There was a reported issue that would occur when processing work orders using Biesse Toolfiles with the “Run Face 6 First” option enabled. When processing an order, the parts would have the multipass rule (route using successive depths, such as a depth of 21 for the first pass, then a depth of 25 for the second pass) function correctly, with 2 routes at successive depths, but it was found that the sheet’s trim would not. Rather than following the mutltipass rule, instead immediately creating a single route at the second assigned depth. This issue has been resolved- routing operations using Biesse toolfiles should now properly use successive depths in accordance with the multipass rule.

Horizontal Boring String Fix

 

1. There was an issue that would occur during processing, when a horizontal boring operation had a custom string replacing a string. When processing a part with more than 1 hbore per edge, the generated code from the writer would have the custom string repeating and compounding with each line. This issue has been resolved- custom strings should no longer be compounding in the writer. 
   

Edgebanding Fix

1. An issue would sometimes occur when creating work orders containing edgebanding on multiple parts in a Unified Work Order Database. When examining a work order that had been exported from a Unified Work Order Database, it was expected that each part would have its edgebanding documented, only to instead find that several parts only had a single instance of edgebanding from each part populating the table. This issue has been resolved- edgebanding data should be displayed properly in exported files, regardless of whether they are from a UWOD.