Allow to force light content to be painted "DrawOnTop" 

Requirement:

A V6 user is using doors with metal panels, which have a "floating light" containing a vision light.

The panel is simulated by a variable profile on the left jamb, which spans from the left to the right side.

When using the solid display, the fill of the vision light is not displayed, as it is draw over by the panel profile.

We need a way to display the fill of the vision light in this configuration.

Implementation:

Added a “DrawOnTop” rendering option for vision lights, allowing their content to be drawn above panel profiles, ensuring correct visual representation without impacting existing configurations.

228682

Avoid loading price per quantity if no such prices are defined 

Requirement:

Avoid loading Price Per Quantity data for components when no such pricing is defined or when the feature is not used, in order to reduce unnecessary database queries and improve system performance

.

Implementation:

Improved pricing performance by eliminating unnecessary Price Per Quantity queries for unused functionality. Previously, queries were executed multiple times for component finish link records even when the feature was not required, resulting in a high volume of database calls. The enhancement reduces redundant query execution and improves overall system efficiency.

228724

Add formula exposure to IncludeInBOM property for extrusions 

Requirement:

As a database developer I want to access the IncludeInBOM property (True/False) of extrusions via formula in quantity formulas of reference points, placement agent selection criteria/rules or bag items.

Implementation:

A new EVA property "IncludeInBOM?" for design extrusions, gaskets, fills/IGUs and assemblies has been added. This property returns either True or False.

228809
Help Desk Ticket 1927083

BOM Export for Dealer Fabricator 

Requirement:

Enable dealers/fabricators to export the Bill of Materials (BOM) for a frame item via macro in a structured JSON format.

Implementation:

A new function GetBOMAsJson() has been introduced under the FrameItem object, enabling direct retrieval of the Bill of Materials (BOM) in JSON format.

The screenshot confirms the availability of the GetBOMAsJson function within the FrameItem API and its successful usage in the below macro.

#Language "WWB.NET"
SubMain()
Dim q As V6.Quote = New V6.Quote
q.GetActive()
Dim frameItem As V6.FrameItem = q.ItemList().Item(0)
Dim json As String = frameItem.GetBOMAsJson()
Dim fso As Object = CreateObject("Scripting.FileSystemObject")
Dim f As Object = fso.CreateTextFile("C:\Temp\bom.json", True)
f.Write(json)
f.Close()
End Sub

228830

Allow creating COM cutplan without quote 

Requirement:

Enable creation of cut plans directly via COM optimizer without requiring a quote or BOM Piece ID.

System should support:
Generating cut plans using macros without dependency on a pre-generated quote/BOM
Ability to specify custom kerf (angled & straight) and end trim
Exporting necessary BOM extrusion properties for optimization

Implementation:

Enhanced optimizer COM API to allow cut plan generation using BOM Piece ID values (-1, -2, 0), eliminating quote dependency

• Introduced support for direct piece addition via macros (AddPiece2 / AddPieceFromID2)
• Added configuration for custom kerf angles, straight kerf, and end trim
• Ensured relevant extrusion properties are available for optimization processing

These uses (AddPieceFromID2):

'#Language "WWB.NET"
Sub Main
Debug.Clear
Dim varOptimizer As V6.Optimizer = ObjectFactory.CreateOptimizer
varOptimizer.ClearDatabase
varOptimizer.CutPlanType = 2
varOptimizer.CustomKerfAngle = 15 / 25.4
varOptimizer.CustomKerfStraight = 5 / 25.4
varOptimizer.CustomEndTrim = 350 / 25.4
Dim iBOMPieceId As Long
Dim iLength As Double
Dim iQty As Double
iBOMPieceId = 0
iLength = 101
iQty = 2
varOptimizer.AddPiece2("[EXT:ALUMINIUM:TESTING]", "[COL:ALUMINIUM:MER (MERANTI)]", iBOMPieceId, iLength, iQty, "0,0.0,0.0", "0,0.0,0.0")
varOptimizer.AddPiece2("[EXT:ALUMINIUM:TESTING]", "[COL:ALUMINIUM:MER (MERANTI)]", iBOMPieceId, 202, 2, "0,0.0,0.0", "0,0.0,0.0")
varOptimizer.AddPiece2("[EXT:ALUMINIUM:TESTING]", "[COL:ALUMINIUM:MER (MERANTI)]", iBOMPieceId, 333, 33, "0,45.0,0.0", "0,45.0,0.0")
varOptimizer.AddPieceFromID2(7, 3001, 7, 3243, 0, 83.622047244094489, 1, "0,45.0,0.0", "0,45.0,0.0")
varOptimizer.Run
For iCutPlan As Integer = 0 To varOptimizer.CutPlanList.Count -1
Dim varCutPlan As V6.CutPlanExtn = varOptimizer.CutPlanList.Item(iCutPlan)
Debug.WriteLine $"CutPlan: {varCutPlan.CutPlanIDStr}"
For iBar As Integer = 0 To varCutPlan.BarList.Count -1
Dim varBar As V6.Bar = varCutPlan.BarList.Item(iBar)
Debug.WriteLine $"Bar: {varBar.Id}, {varBar.CutString}, {varBar.Length}, {varBar.OffCut}"
Next
For iCut As Integer = 0 To varCutPlan.PieceList.Count -1
Dim varPiece As V6.Piece = varCutPlan.PieceList.Item(iCut)
Debug.WriteLine $"{varPiece.BOMPieceID}, {varPiece.ExtnRef}, {varPiece.FinColRef}, {varPiece.Length}, {varPiece.Qty}"
Next
Next
Stop
End Sub.

228867

Frame validation resolver should not be displayed, if UserNotifier is disabled 

Requirement:

When using the Quote.SaveWithoutWarnings macro, the Frame Validation Resolver dialog should not be displayed if UserNotifier is disabled and no blocking validation errors are present.

Implementation:

Updated the validation flow to suppress the Frame Validation Resolver dialog during SaveWithoutWarnings execution when UserNotifier is disabled and no blocking validation errors are detected, ensuring a smoother, non-interruptive save experience.

228137

Crosstalk error when starting V6

Symptom:

V6 Advantage encountered an error despite valid licensing due to a faulty third-party DLL file.

Resolution:

A patch was implemented in Atozed.CrossTalk.Right.dll to disable the erroneous license expiration message. Updating the DLL across affected builds resolves the issue, and enhancements were made to prevent startup failures by handling Crosstalk initialization more gracefully.

3.80.84.1003

229045
Help Desk Ticket 1962065

Using QTY on ad hoc formula causing errors

Symptom:

Using QTY in the quantity formula on an ad hoc item caused formula evaluation errors and crashes when saving or reopening quotes, due to unintended circular references.

Resolution:

Resolved an issue where referencing QTY in ad hoc quantity formulas triggered circular dependencies. The system now handles the linkage correctly, preventing formula errors and application crashes.

1.10.83

228575

Grid resources not matching after import

Symptom:

After importing libraries (LEF) into a target database, grid resources on certain glass door frames were linked to an incorrect grid assembly, causing the wrong grid type to appear (e.g., “Wood Door SDL” instead of “Grid”) when editing frames.

Tv6GridAssyEditor.GetDisplayValue

Resolution:

The grid assembly mapping was corrected during library import so that grid resources now retain the correct grid type and assembly, matching the source database for all affected frames.

3.80.64

225498
Help Desk Ticket 1133032

IGU size constraints are unclear - need improvement

Symptom:

Validation messages for IGU size constraints are unclear because they reference the overall IGU size instead of the specific fill layer dimensions, leading to confusion in interpreting fill size validation errors.

Resolution:

Enhanced IGU validation messages by capturing and displaying the actual failing fill layer details, including layer name, width, and height, ensuring errors reflect the specific layer dimensions instead of the overall IGU size.

3.80.64.1038

227468
Help Desk Ticket 1188621

Extend check for Duplicate published code

Symptom:

Users could add an attribute to an Attribute Group even when both had the same Published Code, leading to duplicate published codes and reference conflicts when used in frames.

Resolution:

Validation has been added to prevent adding an attribute whose Published Code matches the Attribute Group’s Published Code. A warning message is now displayed, and the attribute is not added to avoid conflicts in references.

1.10

228790
Help Desk Ticket 1651465

Alternative Quote Asking for Suffix When Already Entered

Symptom:

• When creating an Alternative Quote, the system repeatedly prompts for a suffix/prefix even when it has already been entered.
• The validation window shows incomplete error text.
• Cancelling the dialog and attempting to save again can cause V6 to crash with a nested database transaction error.

Resolution:

Fixed issues with Alternative Quote suffix/prefix handling by ensuring correct value retrieval and eliminating unnecessary re‑prompts. Also resolved truncated error message display in the suffix selection validation window.

3.80.80

228412
Help Desk Ticket 1812795

Error using incorrect DB version with exe

Symptom:

When users run the application with an incorrect database version, the application crashes with an access violation (AV) instead of showing a clear, user-friendly error message.

Resolution:

Improved validation to detect DB and executable version mismatch and display a clear, user-friendly message indicating the correct DB version required, preventing application crashes.

3.80.84.1003, 1.10

228813