Allow to search resources in quote's BOM 

Requirement:

As a DB developer I would like to use the search resources functionality to search in the quote's BOM as well. This will allow us to identify in which quotes specific resources are used.

Implementation:

• Added a new “Include BOM” checkbox (visible only when Include Quotes is enabled) to allow searching resources used in the Quote BOM.

• Selecting the Include Quotes checkbox should automatically reveal the Include BOM option. Once both are enabled, and the user applies the relevant filters in Find, Resource Library, and Resource Codes, clicking Find should return accurate and expected search results.

228255

Set default colours for X3D exported files 

Requirement:

As a V6 user I want the background colours for the X3D image export to be changed so that the exported images look a lot better than when the current default colours are used.

Implementation:

Two enhancements have been added to the VRML/X3D export pipeline to improve default visual presentation of generated 3D models without requiring client-side post-processing.

1. Automatic Pastel Background Selection

The exporter now automatically selects a contrasting pastel background based on the average diffuse color of model geometry.

• Diffuse colors are tracked during geometry generation.
• Average luminance is calculated at export finalization.
• A light or dark pastel sky/ground combination is applied to improve model visibility.
• This removes the need for client-side background replacement or styling.

2. Automatic Viewpoint Centering

The exporter now computes and applies an optimal camera viewpoint so the full model is centered and visible on load.

• Geometry bounds are tracked during generation.
• A centered camera position and distance are calculated based on model size.
• Default orientation and field-of-view are applied for consistent framing.
• Eliminates the need for client-side bounding box parsing or viewpoint adjustment.

Important Usage Note

Both enhancements are applied during finalization. FinalizeOutput must be called before saving the file to ensure background and viewpoint values are correctly generated. If omitted, default placeholder values will be used.

228203

Error Reporting Framework Update and Enhanced Usability 

Requirement:

As a user, I want a simplified and consistent error reporting experience with the ability to easily share error details, so that I can efficiently document and communicate issues without managing additional configuration settings.

Implementation:

The error reporting system has been migrated to a unified framework, simplifying how errors are captured and managed across the application. As part of this update, the Advanced Error Reporting section in Options → Warnings and Messages has been streamlined.

• The previous toggle for enabling or disabling advanced error reporting has been removed, as the application now uses a single standardized error reporting mechanism. The “Test Error Reporting” option remains available for generating a test exception.
• A new option has been introduced in the error dialog to restart V6 with the same command line parameters, providing a quick and efficient way to relaunch the application after an error.
• Users can now copy the full error report to the clipboard using multiple convenient methods:
• Ctrl + C keyboard shortcut
• Right-click anywhere in the error dialog and select “Copy to clipboard”
• Click the “Copy error information to the clipboard” hyperlink at the bottom of the dialog

228306

Custom Gasket Finish Colour IDs Now Persisted and Remapped Correctly

Symptom:

A gasket on an assembly allows the operator to choose a finish colour (Fincol1, Fincol2, etc.) or select a Custom finish colour from the colour list.
The issue occurred specifically with these Custom‑selected colours.
When a library export/import resulted in different finish colour IDs in the target database, V6 was not remapping the Custom colour IDs correctly, causing mismatches during validation.

This incorrect mapping caused validation errors when attempting to add a frame to a quote. As a result, users could not proceed with quoting operations due to mismatched or missing Gasket Finish Colour references after the library import.

Resolution:

V6 will now store both the ID and LIB_ID for Custom-selected gasket colours in the ASSY_HOOK_GASKET table.
This is applied when saving an Assembly.
During a library import, V6 will now correctly remap the Custom colours using these stored values.

Note: Existing assemblies that contain Custom gasket colours will need to be resaved, so the required data is written into the table. This ensures correct remapping for future exports.

3.80.64.1038

226596
Help Desk Ticket 1116487

Editing template frame in copied quote, changes template frame in source quote

Symptom:

Editing a template frame in a copied quote updated the template in the original/source quote.

When users copied a quote and modified a nested frame within the template in the copy, those changes were unintentionally applied back to the original quote’s template.

Resolution:

The code has been amended to ensure template frames are safely duplicated for copied quotes, preventing changes in the copy from affecting the source quote.

3.80.62.1016

227858
Help Desk Ticket 1289029

Text edit shortcuts disabled while drawing board open

Symptom:

A user was unable to perform standard text actions paste (Ctrl+V), copy (Ctrl+C), and delete (Delete key) within the editor and picker search boxes.

This issue occurred only when the Assembly Drawing board was open in a separate window.

Resolution:

The code has been amended to fix the issue. The solution introduces an additional layer on top of the existing code to properly capture keystrokes, ensuring that all actions (copy, paste, and delete) are now working as expected.

3.80.0.14143, 1.10.0.14153

227305
Help Desk Ticket 1227035

CTE query failing on report printing

Symptom:

Reports containing CTE (Common Table Expression) SQL queries failed to generate when previewed from the Report Designer or run via the User Reports menu, even though the same queries executed successfully through Manage Queries in the SQL Editor.

Resolution:

Updated the report execution pipeline to correctly handle CTE-based SQL queries during report preview and runtime.
The SQL engine now ensures that CTE statements are processed consistently across all report execution paths, preventing syntax errors and allowing CTE queries to run successfully from both Report Designer and User Reports.

1.10.80.1014

228304

Quote IGU Structure tab Does Not Report Correct Total Thickness

Symptom:

Previously, the “Total Thickness” field in Quote IGU → Structure displayed the calculated IGU thickness but excluded any thickness contributed by layers configured using a substitution formula.

Because formula‑driven layer thicknesses are only evaluated when the IGU is placed into a frame and may differ across instances showing a single total thickness at the Quote IGU level was misleading.

Resolution:

The system now hides the “Total Thickness” field whenever any IGU layer is defined as a formula type, preventing incorrect or incomplete thickness values from appearing.

1.10.77.1013

228045
Help Desk Ticket 1391924