ver 12.1.14 (2025-SP23)

Changes: Add currency to the pricing information.

ver 12.1.13 (2025-SP23)

Changes: Fix typo error in 12.1.12

ver 12.1.12 (2025-SP23) (SKIP)

Changes: Enhanced logging. log files per request combined into a single request. logging when disabled for production use (recommended) will still log errors.

ver 12.1.11 (2025-SP23)

Changes: Compensation for v6 bug setting an attribute of number type to "" causes error.

ver 12.1.10 (2025-SP23)

Changes: Logical separation for extended options broken down into global supplier vs dealer configurable.

Dealer bindings

CONFIGURATION

'This is settings added which are global to all dealers, from the supplier system

'only add properties on advice from Support Team

Public Function  GetSupplierExtendedSettings As JSONObject

    Return Nothing

End Function

ver 12.1.9 (2025-SP21, 2025-SP20)

Changes: added a property to fully disabled 3D generation from saving content. we recommend disabling this until sprint 22 with performance optimizations on storage is released.

Minimum version v2.1.30

v2.1.30 (2025-SP23 RELEASE VERSION)

• Macro API 12.1.10+
• V6 3.80.73.1004+
• 2026-01-30
• Min Dealer Build: 2025-S23

Changes

• Fix for Combo Boxes not updating when dynamic data changes

v2.1.29 (SP23)

• Macro API 12.1.10+
• V6 3.80.73.1004+
• 2025-12-18
• Min Dealer Build: 2025-S23

Changes

• Rebuild for compatility with SP23 currency

v2.1.28 (SP23)

• Macro API 12.1.10+
• V6 3.80.73.1004+
• 2025-12-18
• Min Dealer Build: 2025-S23

Changes

• Same as v2.1.23c, long term bug, when a light related attribute is in a frame with a nested frame of the same name and same attribute, it collects the meta data from the child by accident and can result in wrong picker info. this was not discovered for such a long time as often the nested content is identical.

v2.1.27 (SP23)

• Macro API 12.1.10+
• V6 3.80.73.1004+
• 2025-12-17
• Min Dealer Build: 2025-S23

Changes

• Same as v2.1.23b, fix an error on setting a global attribute on the defaults page causing it to prevent updates

v2.1.26 (SP23)

• Macro API 12.1.10+
• V6 3.80.73.1004+
• 2025-12-17
• Min Dealer Build: 2025-S23

Changes

• An update to ensure that if a Quote IGU is used in a frame, but then that quote igu is modified, then we must force validation to occur incase the case will have an impact on pricing.

v2.1.25 (SP23)

• Macro API 12.1.10+
• V6 3.80.73.1004+
• 2025-12-16
• Min Dealer Build: 2025-S23

Changes

• Same as hotifix 2.1.23a, fix a filtering bug on frame selectors where if a L1 light has another L1 light (same name) then it accidentally filters out the L1 (Frame) etc attributes for the first nested frame.

v2.1.24 (SP23)

• Macro API 12.1.10
• V6 3.80.73.1004+ or V6Adv Equivalent
• 2025-Dec-8
• Min Dealer Build: 2025-S23 (NOT BACK COMPATIBLE)

v2.1.23c (SP23)

• Macro API 12.1.10+
• V6 3.80.73.1004+
• 2025-12-18
• Min Dealer Build: 2025-S20

Changes

• Long term bug, when a light related attribute is in a frame with a nested frame of the same name and same attribute, it collects the meta data from the child by accident and can result in wrong picker info. this was not discovered for such a long time as often the nested content is identical.

v2.1.23b (SP20/21)

• Macro API 12.1.7+
• V6 3.80.73.1004+
• 2025-12-17
• Min Dealer Build: 2025-S20

Changes

• Fix an error on setting a global attribute on the defaults page causing it to prevent updates

v2.1.23a (SP20/21)

• Macro API 12.1.7+
• V6 3.80.73.1004+
• 2025-12-16
• Min Dealer Build: 2025-S20

Changes

• Fix a filtering bug on frame selectors where if a L1 light has another L1 light (same name) then it accidentally filters out the L1 (Frame) etc attributes for the first nested frame.

v2.1.23 (SP20/21)

• Macro API 12.1.7+
• V6 3.80.73.1004+
• 2025-11-27
• Min Dealer Build: 2025-S20

Changes

• Fix an edge case for new frame initialization where the scope is reduced to initialization only codes. this remains hidden if all existing attributes in the details group are hidden, height/width etc. the fix forces visibility checking on merged attribute list.

v2.1.22 (SP20/21)

• Macro API 12.1.7+
• V6 3.80.73.1004+
• 2025-11-25
• Min Dealer Build: 2025-S20

Changes

• v2.1.8 introduced a bug in its merging feature where some group look ups are broken by invalid reference pointers and this has broken features like v6Attr_InitializationApproved.

v2.1.21 (SP20/SP21)

• Macro API 12.1.7+
• V6 3.80.73.1004+
• 2025-11-7
• Min Dealer Build: 2025-S20

Changes

• Attribute Group was not correctly looking at poweruser property, and hiding all poweruser settings in some screens.

v2.1.20 (SP20/SP21)

• Macro API 12.1.7+
• V6 3.80.73.1004+
• 2025-11-3
• Min Dealer Build: 2025-S20

Changes

• Frame Compare Was not localized

Release Notes will be appended to the top.

v2.1.19 (SP20/SP21)

• Macro API 12.1.7+
• V6 3.80.73.1004+
• 2025-10-29
• Min Dealer Build: 2025-S20

Changes

• Frame Comparison Content for rendering to support tickets hides attributes that are not Report Visible and also hides Supplier Only Attributes.

Limit Access to Settings and Territories Tabs for Supplier Users

Overview

A new permissions enhancement has been introduced to give suppliers greater control over what their staff users can access within the Web Module. This update allows suppliers to independently manage access to the Settings tab and the Territories tab for their supplier users.

Previously, supplier users automatically inherited access to these areas. With this update, suppliers can now explicitly grant or restrict access based on their operational needs.

What’s New

Independent Permissions for Supplier Users

Supplier staff users now have two new permission options available when managing supplier users:

• Allow Edit Settings
  When enabled, the supplier user can view and edit the Settings tab.
• Assign Territories
  When enabled, the supplier user can view and edit the Territories tab.

These permissions can be managed from the Supplier Staff Edit User dialog

and will be visible on the main staff page as permissions.

 

How It Works

Settings Tab Access

• If Allow Edit Settings is checked for a supplier user:
  • The user can see the Settings tab.
  • The user can edit settings as needed.
• If unchecked:
  • The Settings tab is hidden from the user.
  • No access to configuration options is available.

Territories Tab Access

• If Assign Territories is checked for a supplier user:
  • The user can see and manage the Territories tab.
• If unchecked:
  • The Territories tab is hidden from view.
  • The user cannot assign or modify territories.

Benefits

• Improved control over supplier staff roles and responsibilities.
• Reduced risk of unauthorized configuration changes.
• Streamlined workflows, ensuring users only see what they need.
• Greater flexibility for suppliers to manage access based on business processes.

Notes

• Changes take effect at the next session refresh (within 72 hours), or

• Immediately after the staff member logs out and logs back in.

• Instant permission updates without re-login are planned for a future release.

Add property to disable VRML viewer

Feature: 3D Model Viewer Toggle (quote.3d.model.enabled)

Overview

A new configuration flag has been introduced to control visibility of the 3D Model Viewer within Dealer.
This flag is read from the backend API macro GetExtendedCustomOptions and allows selective hiding of the 3D viewer based on customer, environment, or business rules.

Behavior

This behavior applies from Dealer SP20 onward, including SP21.

Macro Example

Public Function GetExtendedCustomOptions(customerRef As String) As JSONObject
    Dim opts As JSONObject = ObjectFactory.CreateJSONObject

    ' Example: disable the 3D viewer for selected customers
    If customerRef = "DEMO-CUST" Then
        opts.Field("quote.3d.model.enabled") = False
    End If

    Return opts
End Function

Developer Notes

• No client-side or configuration change is required — the flag is read automatically.
• Intended for conditional use where 3D visualization is not supported or required.
• If omitted, systems continue to show the model viewer by default for backward compatibility.

Release Impact

Currency Handling Enhancement

Requirement:

Client needs to define the currency that they use, this is an urgent problem for the client as their default currency is Euro and we need to display this currency symbol through the application and on reports.

Secondly, we need to blow away the Settings Currency feature as this is no longer utilized.

Implementation:

Supplier Currency Settings Integration

Overview
This release introduces comprehensive multi-currency support across the dealer platform, enabling proper handling of supplier-specific currencies in quotes, purchase orders, and dashboard widgets. The currency displayed in the dealer portal is now determined by the supplier's configuration.

Currency Configuration

Supplier-Driven Currency
The dealer portal currency is now determined by the supplier. Suppliers can configure their currency code through their V6 configuration macro in the `GetSupplierExtendedSettings` function.

Example: Setting Currency to Euro (EUR)

Public Function GetSupplierExtendedSettings() As JSONObject
   Dim customOptions As JSONObject = ObjectFactory.CreateJSONObject

   Dim globali As JSONObject = customOptions.NewObj("globalization")
   Dim currenc As JSONObject = globali.NewObj("currency")
   currenc.Field("code") = "EUR"

   Return customOptions
End Function
 

Supported Currency Codes

Standard ISO 4217 currency codes are supported, including:

• USD - US Dollar
• EUR - Euro
• GBP - British Pound
• AUD - Australian Dollar
• CAD - Canadian Dollar
• And other ISO currency codes.

Note: If no currency is configured in the supplier's V6 macro, the system defaults to USD.

UI Changes

Dashboard Widgets

Generated Purchase Orders Widget

• Multi-currency chart display: Purchase order revenue charts now display separate charts for each currency, grouped by currency code (e.g., USD, EUR, GBP)
• Improved chart captions: Changed from generic "Currency: USD" labels to more descriptive format: `"{Widget Title} ({Currency Code})"`
• Consistent styling: Caption styling updated to match the Issued Quotes widget (font-weight: 600, margin: 8px)
• Standardized chart height: Chart height normalized for visual consistency across dashboard widgets
• Currency code display: Now correctly converts currency enum values to ISO currency code strings (e.g., `CurrencyCode.USD` → "USD")

 Issued Quotes Widget

• CSS class refactoring: Container class renamed from `quote-issued-revenue` to `quote-issued-revenue-currency` for better semantic clarity
• Selector updates: Internal selectors updated from `.quote-issued-revenue-all` to `.quote-issued-revenue`

Backend/Data Changes

Quote Creation

• Quotes now inherit the supplier's configured currency when created

Data Model Updates

• Added `currency` fields to Quote and PurchaseOrder entitied
• Implemented currency handling in quotes and purchase orders
• Added currency handling to report generation for quotes and purchase orders
• Extended revenue and quote data structures to support currency information

Technical Details

 Currency Resolution Flow

1.  Dealer creates a quote or purchase order
2. System reads the supplier's V6 configuration (`GetSupplierExtendedSettings`)
3. Currency code is extracted from `globalization.currency.code`
4. Quote/PO is created with the supplier's currency
5. Dashboard widgets group and display revenue data by currency

New Dependencies

• `currencyCodeToString` function imported from `currency-formatter` module for proper currency code display

Migration Notes

• No manual migration required
• Currency fields will default to USD for existing records without explicit currency values
• Dashboard widgets will automatically group and display data by currency
• Suppliers should update their V6 macro with `GetSupplierExtendedSettings` to configure their preferred currency

Known Considerations

• Suppliers without configured currency settings will default to USD
• Historical data defaults to USD grouping

PBI: 227738

SP23

Support Ticket Inbox

Real-Time Synchronization & Notifications

Overview

Support ticket handling between the Dealer Portal and Supplier Portal has been significantly optimized to improve responsiveness, visibility, and collaboration. All ticket updates now propagate in near real time, removing previous delays and ensuring both sides always see the latest information.

🔄 Real-Time Ticket Synchronization

• No more update delays between Dealer and Supplier portals.
• Changes made to a support ticket in the Dealer Portal are now immediately synchronized to the Supplier Portal as part of the save operation.
• This ensures suppliers always see the most current ticket state without waiting for background processing.

👤 Instant Assignment Updates

• When a user is assigned to a ticket in the Supplier Portal, the assignment is immediately reflected in the Dealer Portal, even before the ticket is explicitly saved.
• This provides instant visibility of ownership and responsibility across both portals.

🔔 Event Notifications Enabled

• Event notifications are now fully enabled on:
  • Dealer Portal – Support Tickets
  • Supplier Portal – Support Tickets
• Both parties are notified of ticket updates, assignments, and changes as they occur.

🔄 Auto-Refresh & Visual Indicators (Supplier Portal)

• The Supplier Portal Support Tickets page will now automatically refresh when changes occur if the page is left open.
• Refresh checks run on a 20-second interval.
• A flashing notification indicator highlights when new or updated ticket data is available, ensuring changes are never missed.

✅ Benefits

• Faster collaboration between Dealers and Suppliers
• Immediate visibility of ticket changes and ownership
• Reduced confusion caused by stale ticket data
• Improved support response times.

PBI: 227904

SP23

Add a delete button for 'Draft' Management

Requirement:

Added ability to explicitly save or delete draft support tickets to prevent unused drafts blocking downstream processes such as quote issuance. This enhancement improves user control and ticket hygiene following recent support ticket refactoring.

Implementation:

Draft Management

Step 1: User Creates or Edits a Support Ticket Draft

• User starts composing a support ticket but does not finalize it immediately.
• The ticket is saved as a draft automatically or manually.

Step 2: User Explicitly Saves the Draft

• User chooses to save the draft explicitly (e.g., clicks a “Save Draft” button).
• The draft is stored clearly as a separate entity in the system, marked as an active draft.
• This prevents losing changes while allowing the user to come back later.

Step 3: User Reviews Drafts List

• User can view all saved drafts in a dedicated drafts section or list.
• Drafts can be identified easily and opened for editing.

Step 4: User Deletes Unwanted Drafts

• User can explicitly delete drafts they no longer need.
• Deleting removes the draft completely from the system.
• This prevents unused drafts from cluttering the system or blocking processes downstream.

Step 5: Finalizing a Ticket from Draft

• When ready, user finalizes the ticket by submitting or issuing it.
• The draft is automatically removed or marked as completed.
• This ensures no draft remains to block subsequent actions like quote issuance.

Benefits Recap:

• Explicit save/delete gives user control over drafts.
• Prevents unused drafts from causing blockages in workflows such as quote issuance.
• Improves overall ticket hygiene after support ticket system refactoring.
• Simplifies management of in-progress tickets.

There is also a delete draft button added to the support request which will delete the draft when pressed

PBI: 227601

SP22

Client Q - set up Automated Data Export facility

Requirement:

Client requested the automated DataExport solution, this is beneficial to our team so we don't have to manually process this weekly.

Implementation:

• Prepared instruction material explaining the new DataExport solution integrated into the software.

• Shared step-by-step guidance with the client on how to use the new functionality.

• Walked through the workflow and key usage scenarios to clarify the process.

• Provided live assistance and answered questions during the rollout.

• Ensured the team is comfortable and ready to adopt the new DataExport solution.

PBI: 227583

Add a list of active users to Data Export facility for Client A

Manually provide user data to Awake while waiting to configure the dataexport.

Wrought Iron - Overlay POC

Requirement:

SVG assets to be used to prototype filigree as a layered light element within dynamic frame configuration, demonstrating stretch/distortion behavior for client validation. Aim is to confirm suitability as a representative visual element vs dimensionally accurate CAD output. Follow-up client session scheduled to review POC and clarify fabrication approach and scaling expectations.

Implementation:

Overview

We developed a visual prototype of the wrought iron filigree design using scalable SVG artwork. This will allow us to place the filigree within a flexible frame layout and simulate how it behaves when the frame size changes.

This POC is intended for visual validation purposes only.

Purpose

The goal of this exercise is to:

• Demonstrate how the filigree will look as a layered light element within different frame sizes.
• Show how the design responds when stretched or resized.
• Confirm that the pattern remains visually appealing and proportionate.
• Validate that this approach is suitable for early-stage design representation.

What this POC includes

• A scalable filigree design placed within an adjustable frame.
• Visual examples showing how the pattern behaves when resized.
• Demonstration of stretch and distortion effects under different dimensions.
• A layered light effect to simulate intended aesthetic appearance.

What this POC does not include

• Detailed engineering drawings.
• Fabrication-ready CAD files.
• Final production measurements.
• Structural or material validation.

This stage focuses purely on visual alignment and design direction.

Review & Next Steps

A follow-up session is scheduled to:

• Review the visual prototype together.
• Confirm acceptance of the filigree as a representative design element.
• Discuss fabrication considerations.
• Align on scaling expectations for production.

Based on client feedback, we will define the next phase toward engineering and manufacturing documentation.

PBI: 227850

Support Request & Custom Item Request – Major Refactor

Step 1: Internal Refactor Completed

• A major internal refactor was completed for the Support Ticket Request System and Custom Item Request feature.
• Old technical debt from previous rapid design changes has been cleaned up.
• This creates a stronger, more stable foundation.

Step 2: Unified Save Process Implemented

All actions now use a single optimized save pipeline, including:

• Adding conversation notes
• Updating issue details
• Cancelling requests
• Changing ticket states

What changed?

• Instead of multiple API calls, all edits are bundled into one server commit.

Benefits:

• Faster save times
• Reduced server load
• No partial updates
• No lost drafts
• Draft notes are automatically preserved

Step 3: Smarter Refresh & Loading Added

• The system now reloads only changed data instead of the full conversation history.

Benefits:

• Faster refresh after saving
• Smoother performance for long threads
• Better scalability for accounts with large conversation histories.

Step 4: Report Enhancements

• Custom Items without thumbnails now show a default “Freehand” SVG placeholder.
• SSI items now display correct thumbnail images.
• A new Cyncly staff-only control allows safe deletion of rare stuck/pending reports caused by system errors.

Step 5: Overall Impact

This release improves:

• Stability
• Data integrity
• System performance
• Reliability of conversations and reports

User Impact:

Users will experience faster saves, smoother refreshes, and improved reliability immediately.

V6AAS Hardware / Software Configuration

Requirement:

BBG Hyline V6AAS machine is set up and ready for install. Johan will coordinate with Marco (Hyline BSI) in SP12 to confirm access and configuration. Targeting a Dealer demo for BBG Hyline leadership at the end of July, contingent on PS preparing initial frames. Infrastructure and Azure resources to be provisioned by June 30 (or earlier) to enable onboarding, training, and Phase 1 testing. Effort to be allocated to the Dealer system cost center, potentially via Customer Services.

Implementation:

V6AAS – Implementation Steps

1. Machine Setup Completed
   • BBG Hyline V6AAS machine is set up and ready for installation.
2. Access & Configuration (SP12)
   • Johan to coordinate with Marco (Hyline BSI).
   • Confirm system access.
   • Validate and finalize configuration requirements.
3. Infrastructure Provisioning (By June 30 or Earlier)
   • Provision required Azure resources.
   • Ensure environment readiness for onboarding and testing.
4. Onboarding & Training
   • Enable user onboarding.
   • Conduct initial training sessions.
5. Phase 1 Testing
   • Execute initial validation and system testing.
   • Address any configuration gaps.
6. Initial Frame Preparation (Dependency)
   • PS to prepare initial frames required for demo.
7. Dealer Demo (End of July – Target)
   • Conduct demo for BBG Hyline leadership.
   • Contingent on completion of frame preparation and environment readiness.
8. Cost Allocation
   • Allocate effort to Dealer system cost center.
   • Route via Customer Services if required.

PBI: 225331

Resolution times for support tickets in Dealer portal needs to show how long ticket took to resolve

Requirement:

In the Dealer portal | support tickets | archived tab, the resolution field shows how long ago in relation to now a support ticket was resolved IE the last modified date time

 The same ticket in the supplier portal |  support tickets | archived tab, shows how long the ticket took to resolve. In this case it was about 6 minutes
 

Implementation:

⏱️ Resolution Time Display Aligned Across Portals

The Resolution Time shown on support tickets in the Dealer Portal has been updated for consistency.
Previously, it displayed how long it had been since the ticket was resolved, while the Supplier Portal showed how long the ticket took to resolve.

Both portals now consistently display the total time taken from creation to resolution, ensuring clear and comparable resolution metrics across systems.

Resolution Time Display Alignment

1. Identified inconsistency between Dealer Portal and Supplier Portal resolution time display.
2. Observed that:
   • Dealer Portal showed time elapsed since ticket was resolved.
   • Supplier Portal showed total time taken to resolve the ticket (creation to resolution).
3. Aligned the logic across both portals.
4. Updated Dealer Portal to display total resolution time (Created → Resolved).
5. Verified calculation consistency in both portals.
6. Confirmed resolution metrics are now clear, accurate, and comparable across systems.

PBI: 227487

SP21

Upgrade V6 3D Modelling to X3D

Requirement:

Build a new version of vrml and x3d output with enhanced resolution, quality and bug fixes, and support for wood paneling

Implementation:

V6 – VRML & X3D Output Enhancements

Overview

The VRML output functionality in V6 has undergone its first major upgrade in over a decade. The previous export process had numerous limitations in visual accuracy and geometric representation. This update delivers a modernized export engine that significantly improves output quality, visual fidelity, and compatibility with newer visualization tools.

Key Improvements

1. Enhanced Geometry and Joint Rendering

• Overlapping joints now correctly support mitre cuts and other advanced jointing operations.
• Extrusions are now generated with higher precision, eliminating visible artefacts and alignment issues.

2. Curved Extrusion Support

• The system now supports curved and swept extrusions, allowing for accurate 3D representation of complex frame profiles and custom shapes.

3. Improved Material and Fill Representation

• Fills representing plastics, panels, and composite materials now render with accurate solidity and color.
• Material transparency and shading have been updated for improved realism.

4. Modern File Format and Command-line Options

• A new X3D-compatible output format has been introduced alongside VRML.
• V6 command-line and COM interface now support the -x3d switch, enabling integration with modern 3D viewers and downstream systems.
• The new X3D output supports advanced features such as cut-planes, enabling sectioned views in compatible visualization software.

Usage

• The legacy VRML output remains available via the menu and COM interfaces.
• To produce X3D output, use: v6.exe -x3d 
• This option is designed for V6 as a service or automated export workflows.

Summary

This release brings the V6 3D export subsystem up to modern standards, ensuring higher quality geometry, accurate material representation, and compatibility with today’s visualization ecosystems.
Users can expect smoother exports, improved performance in viewers, and better fidelity when presenting or processing 3D frame assemblies.
 

PBI: 227563

V6

Performance Optimization – V6 Content & Large Quote Handling

Requirement:

Over the past few months, new features extending V6 content (BOM, VRML, etc.) have significantly increased the amount of data stored in DB blobs. This is causing degraded load/save performance and Azure SQL timeouts that were not observed in local SQL Server testing.

Azure recommends keeping blob sizes under 256 KB (with 1 MB considered extreme). However, in complex quotes (e.g., 20 items), even base blob data without BOM or VRML can reach ~100 KB per item, making the total blob size difficult to control and potentially very large on some systems.

We need to review and define a strategy to manage or reduce blob data size to align with Azure SQL recommendations and maintain acceptable system performance.

Implementation:

Overview

Network Based Optimization

Requirement:

We need to deal with a number of network related issues in regards to system thrashing of Azure Database causing timeouts.

Implementation:

Platform Resilience & Stability Improvements

Release Focus: Service reliability, database protection, and safe recovery from interruptions
Impact: Zero-downtime restarts, smoother user experience, stronger data integrity

✨ Key Improvements

Seamless Service Restarts (No Lost Work)

• The platform can now restart gracefully during configuration updates or maintenance.
• In-flight requests complete normally, while new requests are temporarily paused.
• Users automatically reconnect once the service is available — no manual refresh required.

Result: Configuration updates no longer disrupt active users.

Smarter Database Protection Under Load

• Introduced global and per-tenant transaction limits to prevent overload.
• Ensures no single tenant or spike in activity can exhaust database capacity.
• Requests queue safely rather than failing unpredictably.

Result: Improved stability during peak usage and background processing.

Automatic Recovery After Connectivity Loss

• If a browser sleeps, loses network, or goes offline temporarily, the system now:
  • Detects reconnection
  • Automatically recovers editing locks
  • Verifies the underlying data has not changed

Result: Users can resume work safely without silent data corruption.

Built-In Data Concurrency Validation

• When reconnecting after being offline, the system checks whether:
  • The data was modified by another user
• If changes are detected:
  • The user is notified clearly
  • The resource is safely closed to prevent overwriting newer data

Result: Stronger guarantees against conflicting edits and lost updates.

Improved User Feedback During Maintenance

• Clear “Service updating…” messaging during planned restarts
• Visual progress indicators with automatic retry
• Manual retry option if a restart takes longer than expected

Result: Transparent, predictable behaviour instead of confusing errors.

Faster, Safer Configuration Updates

• Deployment configuration and secrets can now be updated centrally.
• The system detects changes and restarts safely only when required.
• No need for manual restarts or downtime coordination.

Result: Operational changes are faster, safer, and less disruptive.

🧠 Under the Hood (High-Level)

• New health-check endpoint improves reconnection reliability
• Unified startup and shutdown flow across services
• Improved lock handling logic for offline and recovery scenarios
• Expanded localization for new user-facing messages

⚠️ Notable Developer Change

• Service configuration initialization has been standardized
  (existing service configuration implementations may require a small signature update)

✅ Summary

This release significantly improves platform resilience, user trust, and operational safety:

• No dropped requests during restarts
• Stronger protection against database overload
• Automatic and safe recovery from offline scenarios
• Clear user messaging instead of silent failures

These changes lay the foundation for safer live updates, better scalability, and a smoother day-to-day experience for both users and operators.

Platform Resilience & Stability Release

This release delivers significant improvements to service reliability, database protection, and interruption recovery.

Key outcomes:

• Zero-downtime service restarts with automatic user reconnection
• Enhanced database safeguards to prevent overload during peak usage
• Automatic recovery from temporary connectivity loss
• Built-in concurrency validation to prevent conflicting edits
• Improved user transparency during maintenance events

Impact:

• Reduced operational risk
• Stronger data integrity controls
• Improved user trust and experience
• Foundation for safer live updates and future scalability.

PBI: 227971

Infrastructure

New License Server to handle SAS Tokens

Overview

This release introduces a transition to dynamic SAS token generation to improve security and eliminate the need for annual token renewals.

What’s Changing

• Moving from long-lived SAS tokens to short-lived, dynamically generated tokens.
• Reduces exposure risk associated with static credentials.
• Eliminates the operational overhead of annual manual renewals.

Rollout Approach

• Initial implementation maintains longer-lived tokens for backward compatibility.
• Upcoming sprints will introduce short-lived dynamic tokens.
• Dealer Link will adopt dynamic token handling in subsequent releases.

Benefits

• Improved security posture
• Reduced credential exposure window
• Lower operational maintenance
• Future-ready token management strategy.

PBI: 227965

System

Client A - set up Automated DataExport facility

Requirement:

Client requested the automated DataExport solution, this is beneficial to our team so we don't have to manually process this weekly.

Implementation:

• Prepared instruction material explaining the new DataExport solution integrated into the software.

• Shared step-by-step guidance with the client on how to use the new functionality.

• Walked through the workflow and key usage scenarios to clarify the process.

• Provided live assistance and answered questions during the rollout.

• Ensured the team is comfortable and ready to adopt the new DataExport solution.

PBI: 227582

System