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.9 (2026-SP07)

Changes:

• Added an Import-DealerMacros helper script for importing the dealer macro set.
• Added inline help/reminders to the DEALER BINDINGS HEALTHCHECK output that point at the release notes when a binding is missing or renamed, making load-time failures easier to diagnose.
• Bumped API_CODE_MINOR_VERSION to 8 in API VERSION.vb (tooling / diagnostics only — no JSON contract change).

ver 13.1.9 (2026-SP08)

Changes:

• Added get-finishes-by-resource macro command (CmdGetFinishesByResource in CMD PO PICKERS.vb) returning available finish/colour options for a resource (extrusion / component / gasket).
• Added get-extrusion-lengths macro command (CmdGetExtrusionLengths in CMD PO PICKERS.vb) returning standard/special supplied-length options for an extrusion + finish.
• Registered CMD PO PICKERS in DEALER.ini and wired the get-finishes-by-resource / get-extrusion-lengths routes into V6L COMMAND API V12.
• Added get-resource-descriptions batch command (CmdGetResourceDescriptions in CMD MISC.vb) to resolve V6 descriptions for resource object-references.
• Added format-measurements batch command (CmdFormatMeasurements in CMD MISC.vb) to format internal measurement values into supplier-unit display strings.
• CMD OPTIMIZER cut plans now emit an extrusionLibrary field.
• Bumped API_CODE_MINOR_VERSION to 9.

ver 13.1.11 (2026-SP09)

Changes:

• Added partial (delta) config writes to quote-and-frame-builder.
• Added isPartialUpdate: true support for sending only changed attributes and their parent chain instead of the full quote/frame entity.
• Frame-config responses now advertise supportsPartialConfigWrites: true.
• Partial writes require the quote to be resident in memory from a prior full create/open on the same session.
• Added guards to prevent partial payloads from overwriting omitted data.
• IGU rebuild is skipped for partial writes.
• Quote-level property writes such as DeliverDate are skipped for partial writes.
• Item Qty is only written when included in the delta.

Experimental / preview — UseNativeDealerAttributes

• Native attribute processing can be enabled through the Dealer binding.
• It currently applies to frame attributes and quote attributes only.
• Quote item options and quote option properties are not nativized.
• The native path is off by default and requires the matching V6 core build.

Dealer bindings — CONFIGURATION

Public Function UseNativeDealerAttributes() As Boolean
    Return False
End Function

v3.0.4 (2026-SP08)

• Macro API 13.1.9+
• V6ADV 1.10.89
• 2026-Jun-26
• Min Dealer Build: 2026-SP08

changes

• Added getFinishesByResource and getExtrusionLengths to the V6 data-utilities surface (V6ConfigWrapper), backed by the persistent-api cache (supplier-version-keyed, flushed on supplier change). These expose the macro 13.1.9 get-finishes-by-resource / get-extrusion-lengths picker commands to the dealer ad-hoc Purchase Order flow, replacing the previous direct dealer-app calls.
• Added v6VersionMap entry hasFabricationResourceFinishes (keyed to v3.0.4) and gated the ad-hoc PO finish/length pickers behind v6SupportsVersion(...), so dealers pointed at an older supplier (without the macro 13.1.9 COM surface) degrade gracefully with a friendly message instead of empty/failing pickers.

Default change notification

Applying quote defaults across line items no longer silently discards Supplier Price Adjustments during V6 frame recalculation. 

• Before defaults are applied, a Continue/Cancel dialog lists every frame with an active supplier price adjustment and explains that the adjustment is removed only where recalculation changes the frame price.
• Where an adjustment is removed, the discarded value is retained in the adjustment note, using the same convention already used when editing an item directly from the quote items page. 
• After defaults are applied, an information dialog lists the frames whose adjustment was removed.

Enhanced Quote and Purchase Order Reports

Quote and Purchase Order reports now include additional author information for greater detail and clarity.

What's changed?

• The author's role is now displayed on Quote and Purchase Order reports.
• The author's phone number is now included on Quote and Purchase Order reports.

Improved Ticket Notification Emails with Record Details and Supplier Links

Support Ticket and Custom Item Ticket notification emails now identify the dealership, branch, and quote that each ticket relates to, so recipients can see at a glance which record is affected. 

Supplier recipients also receive secure bridging links that open the referenced content directly in the supplier portal.

Markdown rendering for Terms & Conditions in reports

Summary

Terms & Conditions now render with proper formatting in generated reports. Previously, when the Terms & Conditions text contained markdown (for example bold, # headings, bullet lists), the report displayed the raw markdown characters instead of formatted text.
 

What changed

• Terms & Conditions text stored as markdown is now converted to formatted output in the report (headings, bold/italic, bullet/numbered lists, line breaks, and links).
• Applies to both the Dealership and Supplier Terms & Conditions sections.
• Plain text (no markdown) continues to display exactly as before.

Technical detail

• Reports are generated with DevExpress XtraReports. The Terms & Conditions field was rendered with an XRLabel (plain text). It now uses an XRRichText control, which can display formatted content.
• Markdown is converted to HTML using the Markdig library (already referenced by the reporting project) and handed to the XRRichText control. Single newlines are treated as line breaks so text typed into a plain textarea keeps its layout.

Scope / limitations

• Only the Terms & Conditions field is affected in this change. Other large text fields (Notes/Annotations, Description, Delivery Instructions) are unchanged.
• XRRichText supports a subset of HTML/CSS. Common markdown renders correctly; very complex constructs (for example markdown pipe-tables, nested raw HTML) may render imperfectly.

User impact

• No action required. Existing Terms & Conditions content will automatically render with formatting on the next report generation.

Updated Draft Report Notification Message

Updated the draft report notification message by removing the reference to the watermark. This change provides more consistent wording, as users have the option to disable the display of the draft watermark on reports.

Dealer Link Reverse Proxy Model

Dealer Link 3.0.0.1 introduces a reverse-connection model. Dealer Link now connects outbound to Dealer over gRPC, instead of hosting a server that Dealer connects into.

• Removed the need for inbound firewall rules and a permanent VPN between Dealer and the customer network. Dealer Link now initiates the connection.
• Updated request and state handling so they are no longer bound to a specific client id. Work started against a quote can now be picked up by any available channel, improving scalability and resilience.
• Added a Windows service host with a single named-instance install model and a self-installer. Added support for multi-instance services with a poolSize-driven V6 pool argument.
• Improved admission resilience and clean shutdown handling, resolving SCM 1067 and 7034 errors when stopping the service.
• Added support for gRPC hosting on Linux App Service, with TLS 1.2 pinned.

V6 Server Rewrite

This release re-platforms the V6 service that the Dealer platform depends on by moving from per-worker isolated sandboxes to a shared resource pool with load-balanced worker threads, and extends the Dealer-facing COM surface. It builds on the V6 Team's shared resource-pool refactor.
Detailed engineering work is tracked in three PBIs; this is the consolidated service release:

• Refactor V6 Service Threads (#229531)
• [DEALER] Expose Batch Item to COM (#229699)
• [DEALER] Optimized loading of attributes (#229746).

1. Load-balanced threaded service (#229531)

• Replaced session-to-worker thread affinity with a single shared FIFO work queue served by a fixed, pre-spawned worker pool driven by a counting semaphore. One slow request no longer blocks others, and every CPU thread is fully utilised.
• Rewrote the quote pool as a single shared, thread-safe pool with per-thread leasing (bounded wait-then-throw on contention) and a global purge that skips leased quotes.
• Added new service parameters: -V6API_SERVER_POOL: (worker count, default = CPU count) and V6QuoteContentionTimeoutMs (default 30s).
• Result: Near-cluster throughput in a single process: ~1.29 GB peak RAM versus ~7.7 GB for the 12-process cluster (~1/6 the memory), ~10% higher throughput, and ~4.8× faster than the old single-process model. Endurance: 8,400 calls, zero failures, flat memory.

2. Concurrency hardening (#229531)

• Fixed 11 latent thread-safety races exposed (not introduced) by moving to the shared pool, covering the friend graph, per-thread bag scratch state, frame type copy-on-write, macro-event execution stacks, formula body loading, frame-cache deserialization, the Teigha vectorizer singleton, and the VCL window-thunk freelist.
• Documented each fix with an in-code failure-and-solution comment; the full record is in Documents\Server Refactor\ (CONCURRENCY-HARDENING-CONSOLIDATED.md plus companion docs).

3. Dealer COM surface (#229699, #229746)

• Batch Item over COM: Added the Iv6ComQuoteBatchItem interface and QuoteBatchItem coclass. Batches can be appended via ItemList.Append(rcBatch) and moved with Quote.MoveItemToBatch, with RetainNettSellingPrice / NettSellingPriceAdjustment price control. Added rcBatch (CID_BATCH_QUOTE_ITEM) as a macro constant with editor keyword highlighting. Regenerated the type library.
• Attribute-loading optimization: Updated hot Dealer attribute-read paths that previously used per-attribute macro recursion (AddQuoteAttributes/ProcessQuoteAttributeGroup, CreateStandardAttribute1/V6Attribute, V6AttributeMeta1/PopulateMetaList1, ListOptionDisplayValue1) to build natively in single COM calls, eliminating per-item macro/COM round-trips. This addresses the performance degradation seen as Dealer DB designs grow. Review (#229798) is in progress.

Status

Throughput and memory gains are proven and tested. Concurrency hardening is ongoing; one rare, timing-dependent fault remains under active investigation. Repeated full-saturation stress testing continues before production sign-off.

PBI 229503

PBI 229531

PBI 229699

PBI 229746

Dealer Link now compatible with Azure-hosted APIs (Linux App Service)

Dealer Link connects to the cloud dealer and supplier API over gRPC (HTTP/2) to dispatch V6 work to the on-prem engine. Azure Windows App Service cannot proxy inbound HTTP/2, so it downgraded the gRPC stream to HTTP/1.1 and rejected Dealer Link’s reverse-worker connection (502), preventing work from reaching V6.

Resolved by hosting the dealer and supplier APIs on Azure Linux App Service (three platform settings: http20Enabled, HTTP20_ONLY_PORT, and the “HTTP 2.0 Proxy = gRPC Only” flag). The API is now published as a single portable artifact that runs on both Windows and Linux. Dealer Link’s reverse-worker now connects reliably and all slots dispatch to V6.

Rolled out per environment as each customer’s APIs move to Linux (dev/Kuaka first). Windows hosting remains available for rollback.

TypeScript 7 conversion — DealerUI frontend

Migrated the Dealer UI frontend from the rollup bundler (which embedded the TypeScript compiler and blocked TypeScript 7) to Vite, with type-checking split into a fast standalone TypeScript 7 (native/tsgo) gate. Updated the codebase to be fully clean under TS7 semantics (201 errors → 0), and ensured all build targets now build and type-check from a single command.

Impact: Reduced full build time (all 5 targets) from ~70s (rollup) to ~11.6s (about 6× faster), tightening the developer edit → rebuild → verify loop while unblocking the TypeScript 7 upgrade. Test suite is green (86/0) and runtime-verified in-browser.

KuakaTest migrated to Linux App Service

Migrated the KuakaTest (kuaka-testing) dev environment’s dealer and supplier APIs from Azure Windows App Service to Azure Linux App Service to support Dealer Link 3.0. This enables HTTP/2 end-to-end for the reverse-worker gRPC endpoint, which Azure Windows App Service cannot support for inbound gRPC (it returns a 502 connection).

The migration was completed side-by-side with a live cutover. New Linux apps were provisioned with the required HTTP/2 and gRPC-proxy settings, deployed via the pipeline as a portable artifact, and then hostnames, managed certificates, and DNS were flipped over. The Dealer Link reverse worker now connects (V6 health green), and both API hostnames serve HTTPS. The Windows apps were left stopped but intact for rollback.

Produced a repeatable, scripted Windows to Linux migration procedure to roll the remaining customer environments onto Linux.

Vite 8 build-performance upgrade — DealerUI frontend

Upgraded the DealerUI frontend build from Vite 6 to Vite 8 (Rolldown/Oxc). Fully removed Rollup (including DealerConnect), collapsed the SCSS pipeline to a single compile, and moved the development workflow to native Vite dev:all and preview. Production CSS is now minified and content-hashed.

Impact: 

Full build (all 5 targets) improved from ~70s (Rollup) → ~11.6s (Vite 6 + TS7) → ~5.4s (Vite 8), which is about 13× faster than the original Rollup build. Test suite is green (86/0).
Developer action required: Minimum Node.js is now ^20.19.0 || >=22.12.0 (CI pinned to 22.23.1 via .node-version). The previous default local Node.js 20.15.0 is no longer supported—upgrade your local Node.js version or use fnm or nvm.

License Server - Feature Flag for Fabricator

Fabricator workflow onboarding is now gated per supplier. The Enable Fabricator Workflow option is available only to suppliers entitled to the feature. Other suppliers continue to onboard tenants with the Standard workflow and do not see the fabricator option. This keeps the fabricator workflow hidden until it is released and available only to suppliers licensed for it.

Improved Dealer Network Page Loading

The Dealer Network page in the Supplier portal now loads smoothly. A loading indicator is shown while your dealership network is retrieved, the page stays responsive while loading, and large dealer networks load noticeably faster.

Purchase orders with delivery dates not showing on delivery pipeline (Dealer Dashboard)

A tooltip has been added to the delivery pipeline to clarify when upcoming purchase orders are expected to be displayed. 

Fixed Incorrect License Counts in Supplier Portal Dashboard and Dealer Network

Summary

The supplier Active Licenses dashboard widget displayed NaN of NaN Granted, and the Dealer Network tab summary showed NaN for both Licenses Allocated and Licenses Used. These values now render correct, meaningful numbers, and the UI degrades gracefully (clear, highlighted messaging) when a value genuinely cannot be calculated.
 

Root cause

The license figures are aggregated from the cached franchisee/tenant payload. Two classes of missing data were silently producing NaN:

1. Active Licenses widget (getLicenseDataByBranch) summed each tenant’s licensePoolAllocations. The guard excluded only the -1 sentinel ("license pool not owned by this supplier"); it did not handle tenants whose allocation fields were absent. For such a tenant, undefined !== -1 passed the guard and total += undefined turned the entire running sum into NaN. In the reported customer deployment, two franchisees had no allocation data, poisoning the whole widget.

2. Dealer Network summary (getLicenseData) computed Allocated and Used from the license pool’s availableAllocations and availableUsers fields. Those fields were absent from the pool object, so concurrentUsers - undefined = NaN. License Bundle (concurrentUsers) was present, which is why only Allocated and Used showed NaN.
Both cases stemmed from the display layer using ?? fallback, which catches only null and undefined, not NaN, so the raw NaN leaked into the UI.
 

What changed

• Added a shared tenantHasAllocation() guard that counts a tenant’s allocation only when the data is a finite, non-sentinel value. This prevents a single tenant with missing data from poisoning an aggregate.
• Active Licenses widget now sums only valid tenants, so it shows the correct X of N Granted. As a safety net, any non-finite value renders as N/A instead of NaN.
• Dealer Network summary no longer relies on the pool’s frequently missing available* fields:
  • Licenses Allocated = sum of each franchisee’s licensePoolAllocations (reflects the real, potentially over-subscribed allocation).
  • Licenses Used = count of active users across allocated franchisees.
  • License Bundle is unchanged (pool concurrentUsers).
• The summary highlights two problem states in red with an explanatory tooltip:
  • Over-subscription — Allocated or Used exceeds the License Bundle.
  • Missing allocation — the value still cannot be calculated.

User-facing impact

• The supplier dashboard and Dealer Network tab now show accurate license figures for the affected deployments instead of NaN.
• Where data is genuinely incomplete, the user sees a clear highlighted indicator rather than a broken value, and over-allocation is now visibly flagged.

Risk / scope

• Front-end only (DealerUI supplier scripts). No API, schema, V6, or environment changes.
• No breaking changes. Per-row Dealer Network table values were already guarded and are unaffected.

Inactive users visible on assignee dropdown for support tickets

The Assigned To dropdown on the Supplier Support page previously listed all users, including inactive users, allowing support tickets to be assigned to users who were no longer active. This has been corrected so that new assignments can only be made to active users.

What's changed?

• The Assigned To dropdown now displays only active users for new assignments.
• New tickets can only be assigned to active users.
• Existing tickets assigned to an inactive user continue to display the current assignee.
• For existing tickets, the inactive assignee remains visible in the dropdown but is disabled, preventing the inactive user from being selected for new assignments.

Improved Cancel Project Dialog

Updated the button labels in the Cancel Project dialog with clearer and more intuitive wording, making the available actions easier for users to understand when cancelling a project.

Add Client dialog improvement

Updated the validation message in the Add Client dialog to ensure terminology is consistent with the associated field names.

SP06-2026 QA Regression Testing Summary

Completed manual regression testing on the sprint cut to validate core functionality and identify 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.
• Projects and Quotes – Validation of creation, editing, status management, workflows, and related data integrity.
• Purchase Orders – Testing of purchase order creation, editing, processing workflows, status updates, and associated business rules.

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

SP07-2026 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:

• Projects – Creation, editing, management workflows, status updates, and data validation.
• Quotes – Quote creation, editing, pricing validation, workflow processing, and associated functionality.
• Purchase Orders – Testing of purchase order creation, editing, processing workflows, status updates, and related business rules.
• 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.

SP08-2026 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:

• Projects – Creation, editing, management workflows, status updates, and data validation.
• Quotes – Quote creation, editing, pricing validation, workflow processing, and associated functionality.
• Purchase Orders – Testing of purchase order creation, editing, processing workflows, status updates, and related business rules.
• 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.
• Dealer Settings – Review and verification of dealer configuration options, preferences, and administrative settings.
• Supplier Settings – Validation of supplier configuration, management options, and associated administrative functionality.

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

PBI 229338

PBI 229340

PBI 229461

PBI 229622

PBI 229623

PBI 229624