Ready to deploy to Client Environments

Before deployment, clients are responsible for testing all new functionality and features outlined in the Release Notes within their DEV and TEST environments. 
Once testing is complete and approval is provided, deployment to Production can proceed. Please note that Production deployments cannot be rolled back, so it is essential that clients conduct thorough testing prior to approval.

ver 13.1.7 (2026-SP06)

Changes: Added full IGU attribute pipeline to mirror frame attribute behaviour.

• New IGU binding hooks: EventIsIGUAttributeCustomLookup, GetCustomIGUAttributeLookupItems, IsQuoteIGUAttributeReadonly, IsQuoteIGUAttributePowerUser, IsQuoteIGUAttributeVisibleToSupplierUserOnly
• QuoteIGUProcessor.ReadV6QuoteIGU now respects these events, allowing IGU options to be marked readonly, power-user-only, supplier-only, or backed by dynamic custom lookup lists.
• Updated DEALER BINDINGS HEALTHCHECK to validate all new IGU binding functions.
• Bumped API code minor version to 7.

ver 13.1.6 (2026-SP06)

Changes:

• Added run-optimizer macro command (CmdRunOptimizer in CMD OPTIMIZER.vb) that wraps the V6 Optimizer COM object and returns structured cut plans with total bar length and scrap metrics.
• Registered CMD OPTIMIZER in DEALER.ini and DealerMacros/DEALER.ini, and wired the run-optimizer route into V6L COMMAND API V12.
• Added parse-measurement macro (CmdParseMeasurement in CMD MISC.vb) and corresponding command route.
• Extended localization with messages for invalid measurements and optimizer failures.
• Updated CMD CONFIGURE QUOTE to support per-item BOM JSON through GetBOMAsJson().
• Bumped API_CODE_MINOR_VERSION to 6.

ver 13.1.5 (2026-SP05)

Changes: Bug fixes to 13.1.4 that should not have been released.

ver 13.1.3 (2026-SP04)

Changes: Fix broken version chain for multiface V2.

ver 13.1.2 (2026-SP04)

Changes:

• Added ReadExistingQuote command to CMD CONFIGURE QUOTE. Loads an existing quote from the database or active server memory and returns its full state in the same JSON format as inline frame configuration.
• Added read-existing-quote case to V6L COMMAND API V12 command router.
• Added api/v6/configitem/readexistingquote route to V6 COMMAND CONTROLLER with mock support.
• Added quoteNum, quoteNumPref, quoteNumSuff fields to the ReadExistingQuote quote-level response.
• DB-loaded quotes bypass ServerApi.SetQuoteContext / ClearQuoteContext / ReleaseQuote.
• Filters ItemList to top-level items only (QuoteLevel = 0).
• Strips RTF from item comments.
• Created Quote30-Format-Guide.md documenting the full JSON output schema.

v3.0.3 (2026-SP04)

• Macro API 13.1.5+ (13.1.1 was never released; 13.1.4 must not be used)
• V6ADV 1.10.83.1003
• 2026-May-11
• Min Dealer Build: 2026-SP04

changes

• a patch to fix light attribute handling

v3.0.2 (2026-SP04)

• Macro API 13.1.3+
• V6ADV 1.10.83.1003
• 2026-May-06
• Min Dealer Build: 2026-SP04

changes

• Correct the conversion handlers for upgrading to the new V2 Data format, which was incomplete

v3.0.1 (2026-SP04)

• Macro API 13.1.2+ (13.1.1 was never released)
• V6ADV 1.10.83.1003
• 2026-Apr-30
• Min Dealer Build: 2026-SP04

changes

• Incorrect Version Markers caused by update to multiface was reverted.

v3.0.0 (2026-SP04)

• Macro API 13.1.2+ (13.1.1 introduced the V2 multi-face macros but was never released)
• V6ADV 1.10.83.1003
• 2026-Apr-23
• Min Dealer Build: 2026-SP04

Multi-Faced Frames & 90° Corner Frames (POC)

Summary

Dealers can now configure frames that have more than one face, such as 90° corner frames, which previously could only be built in V6. A multi-faced frame opens in the frame configurator with each face shown as its own section, with its own picture, its own lights, and its own nested frames. It can be priced, saved, reported, and ordered like any other quote item.

To make this possible, the frame data was rebuilt to match the way V6 itself describes a frame. Where the old structure merged an opening (light) and the frame filling it into a single record, a frame is now described as faces, each face holding its lights, and each light holding the frames placed in it. Single-faced frames continue to behave exactly as before; they are simply frames with one face.

What changed

• Multi-faced frames now load, display, and can be edited in the frame configurator. Each face has its own heading and rendered image, and you can move between faces to work on the lights and sashes each one contains.
• A light can now hold more than one nested frame. Previously, only one could be represented, and any others were invisible to Dealer.
• Empty openings are now recorded as a light containing no frames rather than as a blank frame reference, so they display consistently as empty
• Frame comparison (the deep analysis shown when an item is re-validated) now matches face to face, light to light, and frame to frame, and shows face headings in the comparison.
• Dimensions and other attributes that belong to an opening are now held and edited against that light rather than against the frame as a whole. This allows two faces to carry their own sizes without their attribute names colliding.
• Quote reports and purchase order reports now print a face heading for each face of a multi-faced frame. Single-faced frames appear exactly as before, with no additional heading.
• Existing quotes upgrade themselves. A quote item held in the older format is converted the first time it is opened or re-validated, then saved in the new format (storage version 5). Attributes, pricing, buy-in items, validation messages, glass and IGU data, and light boundaries are all carried across. There is no migration step to run and no action required from dealers.
• Fixed: Conversion no longer overwrites the version recorded against a quote and against its items with the format marker "2". Quote and item versions are now left as the supplier or dealer set them, and only the frame data carries the format marker.

For data consumers (Data pump and direct API users)

The exported frame data has changed shape. Anyone reading it directly should note:

• Storage Version is now 5 rather than 2.
• Frame Data now contains faces, each face containing lights, each light containing nested Frames. The old flat nested Frames list is no longer present.
• Multi-faced items no longer expose a separate Faces array on the quote item; faces live inside Frame Data.
• An empty opening is now an empty nested Frames list rather than an empty object Reference.
• Dimension attributes now sit on the light, in faces[].lights[].attribute Groups, rather than at the root of the frame.
• Nested frames carry a new frame Code field. This is an addition and does not break existing readers.

Versions required

The frame configurator and the supplier macros must be upgraded together. The configurator now declares an API compatibility version of 13.1, raised from 12.1, so a supplier left on 12.1 macros will report a version mismatch.

• V6 Frame Configurator (v6config) v3.0.3 or later. The multi-face work spans four builds: v3.0.0 (2026-Apr-23, the V2 data format and face aware editing), v3.0.1 (2026-Apr-30, corrected version markers), v3.0.2 (2026-May-06, completed the storage upgrade handlers) and v3.0.3 (2026-May-11, light attribute handling). Earlier 2.x builds cannot read the new frame data.
• Dealer V6 macros 13.1.5 or later. Take care with the intermediate builds. 13.1.1 introduced the V2 multi-face reader and writer but was never released; 13.1.3 repaired the version chain; and 13.1.4 must not be used, having been replaced the same day by 13.1.5. 13.1.5 is the lowest release that carries the complete and correct multi-face macro set, and it is the build that pairs with frame configurator v3.0.3.
• V6ADV 1.10.83.1003 or later.
• Minimum dealer build 2026-SP04.

Availability

Multi-faced frames only appear where the supplier product database provides them, so each supplier requires the corresponding V6 database work before their dealers see corner frames in the catalogue. Where the supplier assigns frames to openings by tag, the UseLightTagsForFrames binding also needs to be enabled.

Once a quote item has been opened in this release, it is stored in the new format, and there is no path back to the old format, so the upgrade should be treated as one way.

Call Size feature for US customers

A new Call Size feature has been introduced for US customers to simplify frame configuration and improve order accuracy. Call Size uses standard US fenestration size codes to automatically determine product dimensions, reducing manual data entry and the risk of errors.
 

What’s new?

• Added a Call Size field to the top of the Frame Configuration options list in Dealer.
• Supports standard US Call Size formats, including:
  • 3650 → 3'6" × 5'0"
  • 310-50 → 3'10" × 5'0"
  • 3/10-50 → 3'10" × 5'0"
  • 10/4-50 → 10'4" × 5'0"
  • 10/10-50 → 10'10" × 5'0"
  • 10/10-10/10 → 10'10" × 10'10"
• Automatically converts Call Size codes into the corresponding Width and Height values.
• Changes made directly to Width and Height dimensions automatically update the Call Size code.
• Call Size functionality is only displayed for customers using US imperial units of measure.
• Added the Call Size code to Quote and Purchase Order reports.

Validation and error handling

• Call Size entries are validated against supported formats.
• Invalid or unsupported Call Size values display an informative error message to guide users.

Edit Nested Frame Descriptions on Frame Configurator

On the Frame Configurator, you can now edit and save descriptions for nested frames.

Macro: Expose lookup name attributes to IGUs

If an attribute is a list attribute, then the list options will come from a custom lookup attribute function done specifically for Dealer Module. This function has been expanded to now include IGU attributes

Editing Currency defaults getting numbers mixed up

Improved the display of currency type defaults when editing.

License Server Deployment invalid on empty tenant list

New supplier deployments with no tenants can now complete onboarding. 

• Fixed an issue where `GetTenantsNetwork` in the license server incorrectly filtered by tenant, returning an empty result set and causing deployments to be skipped. 
• Fixed an issue where an onboarding tenant could not sign in until the service was restarted. The security graph now falls back to the database on a miss.

SP23 - Triage

Corrections identified in production and ported to the release/2025-SP23 branch as an SP23 amendment. They also carry forward into the current release.

• Custom items – Fixed image asset resolution for original (non-frame) custom items, which failed on quote issue and in reports. Added defensive protection so an incomplete client payload cannot overwrite good frame data, plus handling for already-corrupt data. The initial aggressive block on empty data was reverted in favour of closing the server-side path that reset stored data when the client sent none. For example, when only a description or note was edited.
• Large quote copy – Fixed a failure where the blob copy queue message exceeded the hard size limit,and a Base64 invalid-offset error.
• Transaction handling – Post-commit work is now staged and executed after commit (RunAfterCommit), with staged blob deletes and rollback actions, so a failure no longer leaves partial side effects behind.
• Support requests – Fixed an error when changing or closing a draft support request, and an invalid using clause that was not saved correctly.

QA Regression Testing Summary

Completed manual regression testing on the sprint cut to validate core functionality and identify any potential regressions prior to release.

Areas covered:

• Clients – Creation, editing, management workflows, and data validation.
• Settings – Review and verification of configuration options and administrative settings.
• Dashboard – Validation of dashboard functionality, navigation, and data presentation.
• Support Tickets – Testing of ticket creation, updates, status changes, and related workflows.
• Custom Items – Verification of custom item functionality, configuration, and associated processes.

The regression suite focused on confirming existing functionality remained stable following sprint changes, with results documented and defects raised where required.