Highlights

Release Information

The Znode 10.3.1.0 release introduces new features, enhancements, performance upgrades, and bug fixes.

Disclaimer

Impact of Publish Enhancements

• As part of this enhancement, all storefronts (production and non-production) will experience downtime and the following steps are to be performed to make the storefront functional again:
  • Re-publish all required catalogs once
    • All product catalogs will be republished using the newly created index names. This republishing process ensures that the latest data is fully captured in the new Elasticsearch indexes. It is important to note that all catalog data will be published during this operation—no content will remain in draft status once the reindexing is complete.
    • To support the coexistence of both the newly created and existing indexes during this transition period, the DevOps team will validate and adjust Elasticsearch infrastructure resources, specifically focusing on storage and RAM allocation. This proactive scaling will ensure optimal performance and stability while both sets of indexes are active.
    • Maintaining the old indexes temporarily provides a safe rollback mechanism in case any issues arise post-deployment. These legacy indexes will remain fully accessible until the system has been validated and all stakeholders have confirmed successful adoption of the new indexes.
    • Once confirmation is received from all relevant teams, the DevOps team will proceed to:
      • Permanently delete the old catalog indexes.
    • Note: This activity is limited strictly to catalog/product data. CMS indexes are not included in this process. All CMS pages and related functionality will continue to operate as normal and remain unaffected by the catalog reindexing initiative.
  • Verify the Storefront to ensure it is functioning as expected.
    • Conduct thorough testing of the storefront to confirm that the complete storefront is working as intended, including product displays, search functionality, checkout processes, and any other user-facing features.
    • This step is vital to ensure that there are no disruptions or issues that could negatively affect the customer or shopper experience.
• Downtime Consideration: During the eviction and repopulation process, search functionality may be temporarily unavailable. The length of this downtime will depend on the size of the catalogs being republished.

Custom API (Advice)

• Custom API is to be merged and is to be deployed to overcome API loading issues
  • For Swagger optimization, take changes from Znode v10.3.0.0
  • For Swagger optimization, take changes from Znode v10.3.0.0
• CustomOcelot Merging using API calls, and deprecated the Blob-based Custom Routing Merging.
  • Currently, we are supporting both types of Custom Routing Merging. However, in the upcoming release, we will completely remove the Blob-based routing.

    However, in customer environments, the following cases will apply:

    • For CustomOcelot merging using Blob (Gateway API)

      • "EnableCustomOcelotMerging": true,

      • "UseCliForCustomOcelotMerging": true

      • "EnableBlobConfiguration": true,

    • For CustomOcelot merging using API  (Gateway API)

      • "EnableCustomOcelotMerging": true,

      • "UseCliForCustomOcelotMerging": false

      • "EnableBlobConfiguration": false,

    • Note: By default, all keys are set to false; the above key value will update in the client Custom SDK.

What’s New

Publish Enhancements

• As part of the ongoing efforts to enhance the publishing process, the structure of the Elasticsearch JSON payload has been significantly optimized..
• The main changes and enhancements are applicable for the following publish processes:
  • Catalog Publish
  • Single Product Publish
• Key Changes:
  • Streamlined Payload Structure: In the past, the payload included all product attributes, which resulted in large index sizes, increased memory consumption, and higher network overhead during publishing. This approach posed scalability challenges, especially when handling large catalogs.
  • Optimized Payload Design: Now, Elasticsearch only stores a defined subset of attributes considered essential for search and filtering. Non-essential attributes have been excluded, leading to a reduction in payload size and improved efficiency.
• Functional Changes:
  • The message has been updated to “Product publish is in progress. Please reload the product list page to view the updated status,” when a product publish is initiated.
  • To see the updated status after the catalog is published, a page reload is required.
  • Publish Bar will go from 50% to 100%.
• Additional Information:
  • Improved Performance: Publishing large catalogs, including those with thousands of products, is now considerably faster.
  • Enhanced Throughput: The optimized approach enables the system to handle higher volumes of data without bottlenecks.
  • Smaller Payloads: The reduced size of the payloads minimizes the chances of timeouts or failures during the publish process.
  • Reduced Index Size: Smaller JSON payloads result in lighter Elasticsearch indices, allowing for faster indexing and improved query performance.

Previous Purchases

• "Previous Purchases" feature, designed to enhance the user experience by enabling both admins and customers to easily view and manage past purchases. This feature brings several key improvements to both the admin panel and storefront, offering greater flexibility and control.
• Admin Controls and Configurations:
  • Store Settings:
    • Admins can enable or disable the "Previous Purchases" section on the Webstore via the store-level setting. When enabled, customers will be able to view their past purchases in their account.
  • Global Settings and Configurations:
    • A new settings group called "Previous Purchases Settings" has been created to manage and configure the synchronization settings for previous purchases in the Global Settings.
      • Enable Previous Purchases Data Sync: Admins now have the option to enable or disable the synchronization of previous purchase data. This setting is disabled by default.
      • Scheduler Frequency: Admins can configure how often the system syncs previous purchase data, with the default being a recurring sync.
      • Cron Expression: A default cron expression, 0 3 * * *, ensures that data sync runs once every 24 hours.
        
  • Previous Purchases tab in Manage Users:
    • A new tab has been added under Users to display a customer's previous purchase history. The tab will show the list of line items in the following columns (recent on top):
      • Item Details
        • Product Name: Includes product name, configurable attributes, addons, personalizations, and product image.
        • SKU: The SKU of the item.
        • Order Date: Date the SKU was ordered.
        • Stock:
          • Check Inventory Flag: A flag allows users to check the current availability of each item. Based on the results, items will be marked as In Stock, Out of Stock, or Backordered.
        • Last Quantity Ordered: Displays the last quantity ordered for each SKU.
        • Ordered Price: Shows the price at the time of order.
        • Unit Price: Displays the current price based on existing pricing logic.
      • Actions
        • Text Field: Users can now enter the quantity they wish to purchase directly from the item details page.
        • Clear Option: A button to clear the entered quantity.
        • Add to Cart Button:
          • Adds the specified quantity to the cart after performing necessary validations.
      • Additional Options:
        • Date & Time Filters:
          • The interface includes filters that allow admins to view purchase data for specific date ranges, such as the last 7 days, last 30 days, or a custom range.
        • Search Functionality:
          • Users can search for specific products within previous purchases by product name or SKU, streamlining the process of locating individual items.
            
    • Storefront Changes
      • Previous Purchases" Section in My Account:
        • Customers will see a new section, "Previous Purchases," in the My Account dropdown, located above Order History. Clicking this link will redirect them to the "Previous Purchases" page.
      • Previous Purchases Page:
        • The Previous Purchases page will display the customer's purchase history in a grid format, including:
          • Item Details
            • Product Name: Includes product name, configurable attributes, addons, personalizations, and product image.
            • SKU: The SKU of the item.
            • Order Date: Date the SKU was ordered.
            • Stock:
              • Check Inventory Flag: A flag allows users to check the current availability of each item. Based on the results, items will be marked as In Stock, Out of Stock, or Backordered.
            • Last Quantity Ordered: Displays the last quantity ordered for each SKU.
            • Ordered Price: Shows the price at the time of order.
            • Unit Price: Displays the current price based on existing pricing logic.
          • Actions
            • Text Field: Users can now enter the quantity they wish to purchase directly from the item details page.
            • Clear Option: A button to clear the entered quantity.
            • Add to Cart Button:
              • Adds the specified quantity to the cart after performing necessary validations.
          • Additional Options:
            • Date & Time Filters:
              • The interface includes filters that allow admins to view purchase data for specific date ranges, such as the last 7 days, last 30 days, or a custom range.
            • Search Functionality:
              • Users can search for specific products within previous purchases by product name or SKU only, streamlining the process of locating individual items.
            • Tools for Bulk Actions:
              • Checkbox Selection for Bulk Add to Cart: Customers can select multiple items and use the "Add to Cart" option to bulk add items from their previous purchases.
                
        • Important Notes:
          • Last Synced Data & Time will be displayed in the admin console so that administrators are aware of the last successful sync.
          • The list will contain unique line items, i.e., if 4 orders are placed within the selected filter, each having 4 line items with the same SKUs but different quantities, display the latest order's details for that line item.
          • Profile-based Catalog and Pricing will be respected for the feature.

Centralized User Login (Beta)

• Znode 10 now supports Centralized User Login, enabling shoppers to use a single set of credentials to access multiple stores on the platform—improving user experience and simplifying account management.
• Disclaimer:
  • This feature is intended to be configured once during initial setup. Changing these settings after initial configuration may lead to unexpected behavior or system instability.
• Global Settings and Configurations (Admin Console):
  • New Group is introduced, named as “Centralized Login Settings” with the following attributes:
    • Enable Centralized User Login (Yes/No)
      • New global setting to allow unified/centralized customer login across stores.
    • Centralized Login Exemptions (Stores) (Multi-select)
      • Exclude specific stores from centralized login, if needed.
    • Enable User-Level Restrictions for Centralized Login (Yes/No)
      • Optionally manage store access per individual user for finer control.
        
• Enhancement: Add User Screen (When Centralized Login Settings = Yes)
  • When Centralized User Login is enabled (Global Setting: Enable Centralized User Login = Yes), admin users can now:
    • Create Shoppers with access to:
      • Single Store
      • Multiple Stores
      • All Stores
  • UI Changes and Functional Behaviour:
    • If the “Enable Centralized User Login” is set to NO then the existing behavior i.e. the admin user can only associate a single store with the shopper/user during account creation.
      
    • User Creation with Centralized Login: A new flag named “User Creation with Centralized Login” has been introduced with the following behaviour:
      • This option is shown only if the "Centralized Login Exemptions (Stores)" setting includes one or more stores.
      • When set to Yes (default), the store selection field becomes multi-select and displays only stores that support centralized login i.e. the ones that are not added in exceptions in the Global Setting, Centralized Login Exemptions (Stores).
      • When set to No, the field changes to simple-select and shows only stores that are exempt from centralized login i.e. the stores added in the exceptions in the Global Setting, Centralized Login Exemptions (Stores).
      • Switching between Yes and No clears all previously selected stores and user details.
        
    • Store Selection Enhancements
      • The store selection field is now a multi-select typeahead, allowing admins to associate a user with multiple stores more easily.
      • A new checkbox labeled "All Stores" is introduced. When checked:
        • The store selection dropdown is hidden.
        • The user is automatically associated with all stores except those listed as exempt from centralized login, if any.
    • Default Store Field
      • A new, required field that allows selection of a Default Store for the user.
      • The list of available stores in this dropdown is filtered based on the stores selected above.
      • This field is hidden when centralized login is disabled.
      • All system-generated account emails will use the default store's domain and branding.
    • Username Field Enhancements
      • When centralized login is enabled, the system performs validation on the username as soon as the administrator clicks or tabs away from the input field:
        • If the username already exists for the same store, an error message is displayed.
        • If the username exists in another store:
          • If both stores allow centralized login, the system auto-fills the following fields using data from the user’s default store:
            • Username
            • External ID
            • Default Store
            • First Name
            • Last Name
            • Phone Number
            • Marketing preferences checkboxes
              • Send Periodic Emails and Special Offers
              • Send SMS Notifications
          • If centralized login is not supported across both stores, the admin must manually fill in these fields.
      • New Checkbox: Enable Centralized Login Restriction to Selected Store(s) is added below the Username field.
        • This option is available only if the global setting "Enable User-Level Restrictions for Centralized Login (Stores)" is enabled.
        • When checked:
          • When checked:
            • The user will only be allowed to log in to the selected stores with the centralized/unified credentials. 
            • Centralized login will be disabled for all other stores. And for other stores, the shopper/customer has to create a separate account.
            • The system validates existing usernames and determines if manual entry is required for the following fields, based on login compatibility across stores.
              • Username
              • Email Address
              • External ID
              • Default Store
              • First Name
              • Last Name
              • Phone Number
              • Marketing preferences checkboxes
                • Send Periodic Emails and Special Offers
                • Send SMS Notifications
  • Additional Information:
    • Email Communication
      • Shopper account-related emails are sent using the selected Default Store.
      • All links within these emails point to the default store’s domain.
    • Automatic Association with New Stores
      • Shoppers granted All Stores access will automatically be associated with any newly created stores in the system, ensuring continuous access across the platform.
    • Future Enhancements (Planned)
      • The account field will adapt to show accounts related to the selected or default store(s), supporting improved account association management.
      • In an upcoming release, support will be added to create Shopper accounts directly under a specific Account via the 'Add User' option in Accounts > Manage Account > Users > Add New.
      • Also, the system will support the creation of Shopper accounts with centralized/unified login as part of the Customer Import process, allowing seamless association with specific User Accounts during bulk imports.
• Enhancement: Manage User Screen (When Centralized Login Settings = Yes)
  • The Manage User screen has been significantly updated to support more dynamic user-store relationships, offering administrators increased flexibility and control—especially when Centralized User Login is enabled.
  • UI Changes and Functional Behaviour:
    • Store Field Positioning and Behavior
      • Store field is now placed at the top of the Manage User screen.
      • If the user is associated with only one store, that store is pre-selected and non-editable.
      • If the user is associated with multiple or all stores, the Default Store is pre-selected and the store field remains editable.
      • When Centralized User Login is enabled, an edit icon appears next to the store field, allowing store associations to be updated via a modal.
        
    • Edit Store Associations (Modal)
      • When administrators click the edit icon, a modal appears with:
        • Username (read-only)
        • Restrict Centralized Login to Selected Stores Only (Checkbox)
          • This option is available only if the global setting "Enable User-Level Restrictions for
          • Centralized Login (Stores)" is enabled.
          • Restricts user login to selected stores only.

            Overrides centralized access.

        • (Associated) Store Name Field
          • Multi-select typeahead to add or remove store associations.
          • Error handling for:
            • Attempting to unassociate the selected store:

              “You cannot unassociate the currently selected store. Please switch to a different store before proceeding.”

            • Dependency on other store relationships:

              “Unable to delete this account. Please remove any child relationships associated with this user account.”

          • Hidden when "All Stores" is selected.
        • Default Store Field:
          • Simple select dropdown updated based on store selections.
            
  • Section-Level Behavior (Based on Selected Store)
    • Upon selecting a store from the Store field, the following sections load contextually for that store:
      • General Settings
        • Login Information
          • Enable/Disable Account applies across all stores.
          • Email notifications use the Default Store’s URL.
        • Username
          • Shared across all stores.
          • Email notifications use the Default Store’s URL.
        • Reset Password
          • Triggers store-branded emails based on the Default Store.
        • User Details (Shared Across Stores)
          • Email Address
          • External ID
          • Default Store
          • First Name
          • Last Name
          • Phone Number
          • Marketing preferences checkboxes
            • Send Periodic Emails and Special Offers
            • Send SMS Notifications
      • Addresses
        • The system operates on two different address book models: a centralized model and a store-specific model.
          • Centralized Address Book (the default)
            • By default, each user has a single, unified address book that is consistent across all stores. This means that no matter which store a user is browsing or shopping in, they will see the same list of saved addresses (e.g., home, work, or a relative’s house). Users manage one centralized address list, and any updates or additions are automatically reflected across all stores.
          • Store Specific Address Book (exemption)
            • This is where an exception applies: If a user is associated with an Account for a specific store, that association overrides the centralized address book rule for that store. In this case, the user’s address book becomes unique to that store and is no longer shared across others. For that store, the user will see the address book defined by the Account they are associated with.
              
      • Orders
        • Orders are store-specific.
        • Users must switch stores to view/store historical data.
        • Example: For users, this means their order history is not centralized or shared across stores. To view past orders from Store A, they must log into or access Store A specifically. Likewise, viewing order history from Store B requires accessing that individual store.
          
        • 
      • Vouchers
        • Vouchers are store-specific.
          
      • Notes:
        • Centralized across all stores.
          
      • Additional Attributes
        • Centralized and shared across all stores
          • Budget Management
          • Open Account Billing
          • Address Settings
          • Power BI Settings
          • Global Order Settings
          • Other user-defined fields
            
      • Previous Purchases
        • Filtered by selected store only.
        • Products added from history apply to the current store only.
      • User Cart
        • Store-specific cart.
        • Ensures accurate pricing, inventory, and logistics per store.
          
      • Impersonation
        • Store dropdown removed from UI.
        • Admins impersonate based on currently selected store only.
          
  • Storefront Impact:
    • Shopper Account Creation via Storefront (/SignUp)
      • Unified Account Management Across Storefronts
        • Shoppers can no longer create duplicate accounts across different storefronts using the same username.
        • When a user creates an account for the first time, that storefront is automatically set as the default store.
      • Admin Email Actions Respect Default Store
        • For admin actions such as Account Creation, Account Enable/Disable, and Reset Password, the email links sent to shoppers now always reflect the user’s default store.
      • Improved Sign-Up Validation
        • If a shopper attempts to sign up on another storefront with an existing username, they are prevented from creating a duplicate account.
        • A new error message is displayed:
          • “An account with this username already exists for <Default Store>. Please log in using your existing credentials. If you've forgotten your password, click 'Forgot Password' to reset it.”
      • Single Account, Multiple Storefront Associations
        • When logging in with the same username/email, the system now associates the shopper with their existing account instead of creating a new one.
        • Storefronts maintain their own store-specific details, while the shopper retains a single unified account across all storefronts.
      • Settings Compliance
        • The following settings are fully respected before allowing shoppers to use default store credentials:
          • Enable User-Level Restrictions for Centralized Login (Stores)
          • Centralized Login Exemptions (Stores)
  • Additional Information
    • Currently, the feature is specific to Storefront Users.    
    • The Affiliates section is hidden in this release.
    • Future Enhancements (Planned)
      • User Account (Enable All/Disable All).
        • In an upcoming release, Enable/Disable (All Stores) buttons will be introduced for users with centralized login enabled. These controls will allow immediate status updates across all associated stores—no manual save required.
      • Sales Rep and Account
        • Sales Rep and Account association will respect store-specific behaviour.
      • User Profile
        • User Profile will be store-specific
      • User Groups
        • The data in this section would be shared across all stores. It will be used in the Commerce Portal.
      • Roles
        • Default Role: “Customer” across all stores.
        • Store-Specific Role: Applied when associated with a store account.
        • Admin Role:
          • Becomes global across all stores.
          • Replaces any existing Znode roles.
        • Commerce Portal Role:
          • Centralized and does not override existing roles.
      • Price Lists
        • Centralized Price Lists apply across stores.
      • Approval Management
        • Store-specific approval assignments.

Sort By “Most Popular” Feature

• A new sorting option, "Sort by Most Popular", has been added to the Product Listing Page. This feature allows customers to sort products based on their popularity, using order frequency as the metric.
• Admin Configuration Settings:
  • Manage in Store Settings:
    • Navigate to: Stores >> Manage Store >> Product Listing Options >> Sort By Options
      • Associate the “Most Popular”
    • Default State: Not Associated with Store Settings
      
• Storefront Impact:
  • Visibility: Price (Low to High), Price (High to Low), Newest.
  • Functionality: Sorts products by the number of orders in which they appear, not by total quantity sold.
    
• Additional Information
  • Popularity Matrix:
    • Products are sorted by the number of orders in which each product appears (not total quantity sold).
      • Products without any order data will appear at the bottom of the list when sorted by popularity.
  • Data Synchronization:
    • The "Hyderated Search" scheduler will be used for data syncing.
    • Popularity data is updated periodically to ensure accuracy.
    • Popularity Metrics Window (In Days): Configures how far back the system should consider order data (default is 180 days).
  • Attribute Configurations
    • Attribute Name: Popularity Metrics Window
    • Description: Controls the time period (in days) for calculating product popularity.
    • Default Value: 180 days (can be adjusted).
  • Data Fetching and Sorting:
    • Sort Products by Order Count:
      • The backend sorts products based on the number of orders, not total quantity sold.
    • Example (with a 30-day window):
      • Product A: 10 orders
      • Product B: 5 orders
      • Product C: 0 orders (appears last)

Versioning in CMS Page Builder

Workflow:

• Scenario #1: Creating a New Page
  • First Version Creation:
    • When a page is saved in Preview mode, a draft version is generated (without a version number).
    • When the page is published for the first time, it becomes v1.0.
  • No Version History:
    • The page will have only one version until it is edited again and saved or published.
    • If edited and saved in Preview mode, a new draft version is created.
    • If directly published, the version number is incremented (e.g., v1.1, v1.2, etc.).
• Scenario #2: Editing an Existing Page
  • Version Creation:
    • Any change made to a published page (whether content or layout) will generate a new version.
    • Draft Version: Created when the page is edited and saved in Preview mode.
    • Published Version: Created when the page is published using the Publish button.
  • Version History:
    • Administrators can view the last five published versions plus one draft version for any page.
    • For each version, the following information will be available:
      • Version Number: v1, v2, etc.
      • Version Status: Draft, Published, Published (Live).
      • User: Displays the first and last name (if available) or username of the person who made the change.
      • Date and Time: When the version was created.
      • Restore Button: To restore the page to a previous version.
        • Users can restore a previous version if the current changes are unsatisfactory.
        • Restored versions are available for Preview, but must be saved or published to create a new version.
        • Version Status:
          • Draft, 
          • Published, 
          • Published (Live).
  • Important Points:
    • Up to five published versions will be saved for easy access and reference.
    • Znode Widget Behavior: Once a widget is published, it will update across all versions, including older ones. Version history for widgets is not maintained.
    • If changes to the CMS or Commerce Pages are not saved or published, those changes will be discarded.
    • While reviewing version history, the page will be in view-only mode.
  • Future Scope
    • Tagging Versions: The ability to assign tags to important versions for easy future reference.
    • Deleting Versions: Clean-up of older versions while retaining a history.
    • Approval and Review: Enable collaboration during content review with version tracking.
    • Version Comparison: Enhanced comparison capabilities to review and analyze modifications over time.

Dynamic Account Switching for B2B Storefronts

• This feature, which was previously available as a beta version, is now officially fully available.!
• Here’s a quick link to the feature overview for more details.

Typeahead Search Feature

• This feature, which was previously available as a beta version, is now officially fully available!

• Here’s a quick link to the feature overview for more details.

Tax Exempt Feature (Beta Release)

• The Znode now supports the ability to designate user profiles as Tax Exempt.
  • For domestic orders and quotes, no tax will be applied.
  • For international orders and quotes, only import duty and country tax will be applied; state tax will be excluded.
  • Tax-exempt profiles can be reverted to non-tax-exempt profiles anytime without impacting any previously placed orders or quotes.
• Admin Configuration Settings:
  • New Profiles:
    • Navigate to Accounts and Users> User Profiles> Add New.
    • Mark “Tax Exempt” checkbox.
      
  • Existing Profiles:
    • Accounts and Users > User Profiles > Action (Edit), then set the Tax-Exempt column value to “True”.
      
• Storefront Impact:
  • For tax-exempt profile users, no tax will be applied on domestic orders, while international orders include only import duty and country tax, excluding state tax.
• Important Points:
  • The Tax Exempt flag on the Manage Order and Manage Quote screens has been temporarily disabled.

Media Storage Logic Enhancement

• A new Storage Type flag has been added to the General Settings section (in Global Settings). This flag allows administrators to select the preferred storage medium for file storage operations, offering greater flexibility based on infrastructure requirements.
• The Storage Type flag enables the choice between two primary storage options (currently not editable):
  • Local Storage: Suitable for on-premise or VM-based environments.
  • Cloud Storage: Suitable for cloud-based storage (e.g., Azure Storage Accounts).
    

User-Specific Approval Management

• Approval management now supports user-level approval routing.
  • It allows admins to define approval flows specific to individual users.
  • Multiple approvers can be configured, following the amount brackets.
  • Approval routing applies to all non-digital (PO, COD, and Invoice me) payment methods associated with the store.
• Admin Configuration Settings:
  • A new “Users” option is available under Stores > Manage Stores > Approval Management > Approval Type.
    
  • Select “Users” as the approval type, then go to Accounts and Users > Manage User > Approval Management to configure additional settings.
  • Set the Approval type to “Always required approval”.
  • Admins can configure approvers, approval order (sequence), and amount brackets per user.
• Storefront Impact:
  • If the order amount of a particular user falls within defined brackets, the “Submit for Approval” button is shown at checkout.
  • Orders outside the brackets bypass approval and are placed directly.
  • Orders requiring approval appear in the “Pending Orders” section for both the user and the approver.
  • In the “Pending Orders” section, approvers can approve or reject orders, while users can monitor the status of their pending orders.
  • The approval workflow follows the configured sequence of approvers until final approval is obtained.
• Future Scope: Support for digital payment methods in approval management.

Data-Test-Selector Enhancement for Product Price Element

• Enhanced the data-test-selector attribute used for locating the product price element, which previously returned an undefined value (spnRetailPriceundefined). 
• With this enhancement, the attribute now returns a well-defined and consistent value, enabling seamless test automation and ensuring reliable validation of product prices across environments.

Security Upgrades

• Restricted Role Updates
  • Strengthened security measures to prevent unauthorized role modifications when using the updatecustomeraccount API. Role updates are now strictly
• Protected Order Status Updates Against IDOR
  • Implemented safeguards to prevent Insecure Direct Object Reference (IDOR) vulnerabilities when modifying order statuses using ClassNumber. Order status changes are now strictly validated against user authorization and ownership, ensuring only permitted users can perform such updates.
• Enforced Access Controls on Order Status Updates
  • Introduced strict authentication and authorization checks to prevent unauthenticated users from changing order statuses. All order status modifications now require valid access controls, ensuring only authorized users can perform these actions.

Performance Upgrade

• Improved Static Page Publishing Performance and Stability in Page Builder
  • Optimized the publishing process for static pages within the Page Builder to significantly reduce loading times. 
  • This enhancement minimizes screen freeze duration during publishing, resulting in a smoother user experience. 
  • Additionally, page flickering issues that occurred post-publish have been addressed to ensure stable and seamless content updates.

API Enhancements

• New API – Manage Quote: Update Billing and Shipping Address by Class Number
  • Introduced a new API that allows updating Billing and Shipping Addresses for a Quote based on the provided Class Number. While the QuoteAddress and OrderAddress tables share the same schema, this API is exclusively scoped to Quotes to maintain clear separation from Order-related operations.
  • This enhancement ensures greater flexibility and accuracy in managing Quote address details without affecting Order workflows.
• Enhanced V2 API Support for Additional Attributes in User Profiles
  • Added support in the V2 API to include Additional Attributes in the User Profiles entity responses.
  • This enhancement introduces an optional expand parameter, allowing clients to selectively retrieve extended user profile details when needed, improving API flexibility and data completeness.

Important Updates

• Functional
  • Clear Data: Products and Categories are not moving to draft state when clear data is performed

    When the Clear Data action is executed, products and categories are expected to reset into a draft state. However, they remain unchanged, leading to inconsistencies in the system state after data clearance.

  • Publish: Delay in starting publish and displaying publish progress bar

    During the publishing process, there is a noticeable delay before the publish job actually begins and before the progress bar appears. This creates confusion as the system provides no immediate feedback that the action has been triggered.

  • User Approval Management is not working correctly. After approving the order, the order status is not changing

    When an order is approved through the User Approval Management feature, the approval action is recorded but the order status does not update to reflect the approval, leaving the order stuck in the previous status.

  • Message is not appearing on storefront in case of impersonation user

    When an admin or user logs in through impersonation, the expected Webstore_Message is not displayed. This causes important system messages to be missed during impersonated sessions.

  • Shipping & Tax reset to $0.00 when changing order status to "Shipped" in Admin

    In the Order Management System, when an order’s status is updated to “Shipped” from the admin panel, the system incorrectly resets both the shipping amount and tax amount to $0.00, resulting in inaccurate order details.

  • Showing codes in description, shipping and billing address in order receipt sent via 'Send Cart Line item email'

    Order receipts generated using the Send Cart Line Item Email functionality display product codes within item descriptions, and the shipping and billing address fields are not shown properly, leading to unclear or incomplete order receipts.

  • PIM index/Log is not being created when publishing a catalog with the "Publish Draft Products Only" option checked.

    When attempting to publish a catalog with the "Publish Draft Products Only" option checked with no products in draft, the PIM index/log is not created. This behaviour would be enhanced in the upcoming release.

  • Publish Catalog Scheduler does not execute when products are in the Draft state.

    The scheduler fails to execute when there are no draft products in the catalog. This issue prevents the scheduled publishing process from running if there are no draft products to publish. This behaviour would be enhanced in the upcoming release.

  • Unpublished catalog appears in the Store edit screen catalog dropdown

    Unpublished catalogs are incorrectly appearing in the Catalog dropdown on the Store edit screen. Only published catalogs should be available for store association, and this issue is causing confusion for Admin users. The behaviour would be enhanced in the upcoming release.

• API
  • Payment Manager API
    • orderId is now marked as required in the schema.
    • Endpoint: Capture Payment Operation
  • Publish Enhancement
    • To fetch data through search APIs, it is now required to create an index after catalog publish.
  • Others
    • The PortalId filter is now mandatory for the v2/wish-lists/{userName} API. Any request without this filter will return an error.
    • If the portalId is not included in the request body, the Users/ChangePassword operation may fail or behave unexpectedly.
    • API pattern change: /v2/forms/create-form-template has been updated to /v2/forms/form-template.

Black Box Improvements

Digital Asset Management (DAM)

• Z10-25855 | Missing Help Text for External Base URL
  Resolved an issue where the External Base URL field in the DAM configuration was missing help text. Without guidance, users configuring external integrations lacked clarity on the purpose and expected input for this field, which increased the chances of misconfiguration and errors in media asset management. The fix introduces clear and descriptive help text, ensuring users have the proper context when setting up external base URLs. This enhancement improves usability, reduces onboarding friction, and minimizes configuration errors.
  
  
• Z10-26165 | Incorrect Loading Behavior for Video Attribute
  Resolved an issue where the Video media attribute exhibited incorrect loading behavior. Upon initial load, the system displayed incorrect attribute details, only to replace them after a reload. This inconsistency created confusion and made it difficult for users to trust the data being displayed. With the fix, the system now loads the correct video attribute details consistently from the start, eliminating the need for refreshes and ensuring data accuracy. This improves both the stability of the media attribute framework and the overall user experience when managing video assets.

 

• Z10-26177 | Unable to Create Media Attribute with Type Date
  Resolved a defect that prevented users from creating media attributes of type Date. When attempting to set up such attributes, the system failed to save the configuration, blocking a valid use case for metadata management. With this fix, Date-type attributes are now fully supported for media attributes, enabling users to store and manage date-based metadata such as publishing schedules, license expirations, or archival timelines. This enhancement broadens attribute flexibility and ensures a more complete digital asset management workflow.
• Z10-26499 | Product Gallery Images Not Displaying on Webstore
  Resolved an issue where gallery images associated with products failed to display on the webstore, leading to incomplete product presentation for shoppers. This negatively impacted merchandising, product storytelling, and customer confidence in purchasing decisions. The fix ensures that all gallery images linked to a product are now displayed reliably across the webstore, including on PLPs, PDPs, and quick view modes. This improvement enhances visual consistency, strengthens customer trust, and supports better conversion outcomes through accurate product representation.

Order Management System (OMS)

• Z10-10546 | Order Receipt Showing Codes and Misformatted Address
  Resolved an issue where the Order Receipt generated via the ‘Send Cart Line Item Email’ option displayed internal product codes instead of user-friendly product descriptions. Additionally, shipping and billing addresses were incorrectly formatted, impacting readability and causing confusion for both customers and support teams. The fix ensures that receipts now display descriptive product details and properly formatted addresses, improving clarity, professionalism, and communication quality in transactional emails.

• Z10-21352 | Address Line 2 Missing from Order/Quote Receipts
  Fixed a defect where Address Line 2 was omitted from both Order and Quote receipts, including their email copies. This omission resulted in incomplete billing and shipping details, leading to possible delivery issues and miscommunication with customers. With this fix, all address lines, including Address Line 2, are now consistently displayed across all receipts and email templates, ensuring full visibility of customer address data.

 

• Z10-23453 | Customer Username Missing in Quote Receipt Email
  Addressed an issue where the customer’s username was not included in quote receipt emails. This omission made it difficult for businesses to properly identify or reference users in their transactional communications. The update ensures that the username is now consistently displayed in all quote receipt emails, improving user traceability and strengthening the accuracy of customer communications.
• Z10-24437 | Inconsistent Identifier in Cybersource Capture
  Corrected a payment integration issue where the Spreedly Transaction ID was being passed to Cybersource during capture instead of the Order Number. This mismatch caused inconsistencies in payment reconciliation and tracking between the OMS and payment provider. The system now consistently uses the correct Order Number for Cybersource captures, ensuring accuracy in reporting, reconciliation, and financial audits.

 

• Z10-24681 | Voucher Amount Field Retains Initial Zero
  Fixed a validation issue where the voucher amount field retained leading zeroes during edits, resulting in misleading or invalid display values. This has now been corrected so that voucher amounts are displayed and stored without unnecessary leading zeroes, ensuring clean and accurate financial data entry.

 

• Z10-24853 | Double Colon in Shipping Constraints Field
  Resolved a formatting issue in Quote Receipts and Emails where a double colon appeared for the Shipping Constraints field. The field now displays with correct punctuation.Resolved a formatting issue where the Shipping Constraints field in Quote Receipts and Emails displayed with a double colon (::) instead of the intended single colon. This minor but noticeable UI defect has been corrected, ensuring consistent and professional formatting across all customer-facing receipts and communications.

 

• Z10-24945 | Updated Shipping Method Not Displayed in Order History
  Fixed an issue where updates made to the Shipping Method after saving an order were not reflected in the Order History section. This caused gaps in the historical record and reduced traceability of changes. The system now captures and displays all shipping method updates in Order History, ensuring accurate logging and improving order tracking visibility for customer service teams.

 

• Z10-24982 | Updated Shipping Constraint Not Displayed in Order History
  Corrected an inconsistency where changes to the Shipping Constraint field were not recorded or displayed in Order History. With this fix, the Order History now accurately logs all updates to shipping constraints, ensuring comprehensive change tracking and enhancing transparency for order fulfillment teams.
• Z10-24993 | Updated Tracking Number Not Displayed in Order History
  Resolved an issue where updated tracking numbers were not being captured or shown in Order History after saving changes. This created challenges in shipment tracking and customer service follow-ups. The fix ensures that tracking number updates are consistently logged and displayed in Order History, providing complete shipment visibility.
• Z10-25087 | Incorrect Quantity Format on Quote Edit
  Fixed a defect where changing the shipping method on the Quote Edit screen caused the product quantity format to display incorrectly. This error created confusion in reviewing and updating quotes. The formatting logic has been corrected, ensuring that quantities now remain properly formatted regardless of shipping method changes, improving data consistency.

 

• Z10-25252 | Attribute Codes Displayed Instead of Values in OMS
  Addressed an issue where attribute codes were displayed in OMS views instead of the actual attribute values. This limited readability and comprehension for end users working with product and order data. The update ensures that meaningful attribute values are now shown in the UI, improving usability and data interpretation across OMS screens.

 

• Z10-25308 | Irrelevant Notes in Quote History When Default Status Is Not Submitted
  Resolved a bug where irrelevant notes were added to Quote History and Notes when the default quote status was not set to Submitted. This cluttered the record and created confusion in tracking legitimate actions. The note-saving logic has been refined so that only valid notes are captured, ensuring that Quote History reflects accurate and meaningful activity.
• Z10-25398 | Alignment Issue in Pending Orders Notes UI
  Fixed a UI alignment issue where the “Add Pending Note” text area within Pending Orders appeared misaligned, impacting readability and usability. The field now appears with proper alignment and consistent styling, enhancing the visual clarity of the interface and improving the user experience for order management.
• Z10-26438 | Blank Screen When Managing Orders
  Corrected a stability issue where certain orders, when accessed through Manage Order, resulted in a blank screen and prevented users from performing order management actions. The root cause has been resolved, and orders can now be opened, reviewed, and managed reliably without errors, ensuring smoother operations for customer support and order processing teams.
• Z10-26550 | Payment Method and Status Missing in Billing Section
  Fixed a defect where both the Payment Method and Payment Status fields appeared blank in the Billing section of the Manage Order page. This omission created gaps in financial visibility and hampered support teams from validating payment details. With the fix, the Billing section now accurately displays both payment method and current status, ensuring full transparency in order billing information. 

 

• Z10-23427 | OMS: Order Receipt Not Generated After Converting Quote with Online Payment
  Resolved an issue in the Order Management System (OMS) where the order receipt was not generated after converting a quote into an order when the transaction involved an online payment. This incorrect behavior caused a gap in the order lifecycle, as customers and administrators were unable to access official order receipts for such transactions, leading to confusion in record-keeping, audits, and customer communication.
  The fix ensures that once a quote is successfully converted into an order and payment is captured online, the order receipt is generated automatically and reliably, maintaining consistency with other order workflows. This update improves transactional accuracy, enhances customer trust, and ensures compliance with standard order processing protocols.

Dev Center

• Z10-26096 | Admin User Unable to Update Menu List Field
  Resolved an issue in the Dev Center where admin users were unable to update the Menu List field within the Manage section. Any changes made to the field failed to save, creating unnecessary roadblocks for administrators managing navigation configurations.
  
  This defect not only disrupted menu customization but also limited the flexibility required to maintain up-to-date navigation structures for different environments. With this fix, updates to the Menu List field are now consistently saved and reflected, ensuring that administrators have full control over menu management without encountering workflow interruptions.

Store

• Z10-25124 | Loader Missing on Save and Close in Approval Routing
  Resolved a UI issue in Approval Management where the loader indicator failed to appear after clicking Save and Close during approval routing configuration. This missing visual feedback left users uncertain about whether their changes were being processed or saved, sometimes leading to repeated clicks and potential configuration errors.
  The fix ensures that a loader is consistently displayed during save operations, providing users with clear and immediate confirmation that their action is being processed. This improves usability, prevents duplicate actions, and enhances confidence in the system’s responsiveness.
• Z10-25656 | Decimal Value Length in Order Amount Field Not Aligned
  Corrected a defect in the Order Amount field where users were able to enter decimal values exceeding the maximum precision defined in the global attribute settings. This inconsistency created discrepancies between field validation and global configurations, potentially causing errors in financial calculations and reporting.
  The system has now been updated to enforce consistent validation rules across the platform. Decimal precision in the Order Amount field is properly restricted to the limits set in global attributes, ensuring data integrity, accuracy in calculations, and compliance with standardized configurations.

  

• Z10-25871 | Add New Approval Button Clickable from All Horizontal Areas
  Resolved a UI bug in Approval Management where the “Add New Approval” button was incorrectly clickable across the entire horizontal section of the screen, rather than being restricted to the button’s actual boundary. This created a confusing and inconsistent user experience, as accidental clicks outside the button area could unintentionally trigger the action.
  The clickable area has now been restricted strictly to the button boundaries, ensuring predictable and intentional user interactions. This correction improves overall interface precision, eliminates accidental triggers, and aligns button behavior with standard UI conventions.

Product Information Management (PIM)

• Z10-17578 | Pagination and Filtering Malfunction
  Resolved an issue where product pagination malfunctioned after applying filters on product listing pages. When users attempted to move across pages after setting filter criteria, product data disappeared or failed to load correctly. This disrupted navigation, made it difficult to browse large product catalogs, and created inconsistencies in filtered search results.
  The pagination logic has been corrected and aligned with filter operations, ensuring that filtered product results load seamlessly across multiple pages. This improvement enhances catalog browsing, improves performance stability, and provides a consistent user experience when applying filters in combination with pagination.
  
  
• Z10-26097 | Customized Section Hidden After Product Association
  Fixed a defect where the Customized section on the product details page was removed or hidden after navigating to the Associate Product section. This incorrect behavior caused loss of visibility for key custom configuration fields, leading to confusion for users managing product setups.
  The update ensures that the Customized section now remains persistently visible even after navigating between product association workflows. This correction improves workflow continuity, prevents accidental data oversight, and ensures that customization fields remain accessible throughout the product configuration process.
• Z10-26306 | Error in Frequently Bought Together Product Association
  Addressed a defect in the Frequently Bought Together (FBT) feature where already associated products were still displayed in the association modal. Additionally, attempts to reassociate products triggered a generic error message, preventing users from managing product relationships effectively.
  This issue has been resolved by refining the association validation logic, ensuring that already-associated products are no longer redundantly displayed and reassociation operations are complete without errors. The fix provides a smooth and error-free workflow for managing FBT associations, enhancing both usability and merchandising effectiveness.
  
  
• Z10-26371 | Error on Opening Associated Products Tab in Brand’s Page
  Resolved a problem on the Brand’s management page where opening the Associated Products tab triggered system errors.
  This prevented users from viewing, editing, or managing product associations linked to specific brands, thereby interrupting catalog management operations. The issue has been fixed so that the Associated Products tab now loads reliably without errors, enabling smooth access to product data linked to brands. This update restores full functionality to brand-level product management and ensures a more stable user experience when handling large catalogs.

Marketing

• Z10-18581 | Validation Message Not Clearing on Discount Profile Selection
  Resolved an issue on the Discount Information Page where validation messages persisted even after a user selected a valid discount profile. This misleading behavior gave the impression that the selection was still invalid, creating unnecessary confusion and disrupting the setup of discount rules.
  The system has now been updated to clear validation messages immediately after a valid profile is chosen, ensuring that users receive accurate feedback. This enhancement improves usability, streamlines discount configuration workflows, and reduces the chances of incorrect assumptions about validation failures.
  
  
• Z10-24167 | Tab Focus Shifts During Store–Search Profile Association
  Fixed a usability issue in the Store–Search Profile association workflow where the tab focus shifted unnecessarily between the Store tab and the Search Profile tab after an association was completed. This erratic focus behavior disrupted user flow, requiring additional navigation to return to the intended context.
  The fix ensures that the tab focus remains stable on the current tab after completing store–search profile associations. This provides a smoother user experience, eliminates unnecessary navigation steps, and enhances efficiency when configuring store–search relationships.
  
  
• Z10-24522 | Search Profile Record Not Appearing on List Page
  Corrected a defect where certain search profile records were not being displayed on the search profile list page. This caused inconsistencies in data visibility and limited administrators’ ability to review and manage available search profiles, leading to potential misconfigurations.
  With this fix, the list page now accurately retrieves and displays all existing search profile records, ensuring that administrators have complete visibility. This update strengthens data consistency, prevents oversight, and improves trust in the accuracy of list views.
  
  
• Z10-26596 | Search Not Working After Applying Filter
  Resolved a critical defect in the search functionality where applying filters caused the search feature to stop working entirely. Users were unable to perform searches once a filter was in place, blocking efficient navigation and data retrieval.
  The defect has been addressed so that search operations now function correctly in filtered contexts. Filters and search criteria can be combined seamlessly, ensuring accurate results and restoring confidence in the reliability of the search experience.

 

Users & Roles

• Z10-24110 | Restricted Modules Accessible via Direct URL

  Resolved a critical role-based access control issue where restricted modules, though hidden from the navigation menu, could still be accessed by users through direct URL entry. This loophole created a security and compliance risk, as users without the required permissions were able to view and interact with functionality that should have been inaccessible.

  With this fix, backend-level validation has been enhanced to enforce permissions consistently, ensuring that even when a direct URL is used, access is denied if the user’s role does not authorize it. This update strengthens overall system security, maintains role-based restrictions, and aligns with proper access governance best practices.

Email & Notifications

• Z10-5847 | Retailers Not Receiving Form Submission Mails
  Resolved an issue where form submission emails were not being delivered to retailers, causing them to miss important customer inquiries and notifications. This defect disrupted the expected communication flow between customers and retailers, impacting responsiveness and service quality.
  The email delivery logic has now been corrected and stabilized, ensuring that form submission notifications are sent reliably and consistently to the intended recipients. Retailers will now receive timely updates, improving customer engagement and operational efficiency.
  
  
• Z10-25806 | OverrideEventSubscriberService Not Preventing Default Triggers
  Fixed a defect where the OverrideEventSubscriberService failed to suppress default email triggers. As a result, users were receiving duplicate or unnecessary email notifications, leading to confusion and redundancy in communication.
  The service logic has now been refined to properly intercept and prevent default triggers when overrides are applied, ensuring only the intended notifications are sent. This update improves the reliability of the notification system and eliminates excess noise in user communications.

 

• Z10-25921 | Missing Fields in Sales Rep Creation Email
  Resolved an issue where key details of a newly created Sales Representative were missing in the notification email. This omission reduced the usefulness of the notification and required manual follow-ups to gather the missing details.
  The email template has now been updated to include all relevant sales rep information (such as contact details, identifiers, and role specifications), ensuring that recipients have a complete view of the new user without additional steps.
  
  
• Z10-26235 | Order Email Template Missing Additional Information
  Corrected a template rendering issue where certain additional fields were not appearing in Order Email Templates, leaving recipients without complete order details. This affected transparency in order confirmations and required referencing other systems for missing data.
  The template has now been enhanced to display all expected fields consistently, providing customers, admins, and retailers with full visibility into order details directly from the email. This ensures smoother operations, better communication, and reduced dependency on manual checks.

System Settings

• Z10-24233 | Breadcrumbs Missing on Cache Management Page
  Added missing breadcrumbs to the Cache Management Page within system settings. Previously, users navigating to this page lacked contextual navigation links, making it inconsistent with other settings modules and harder to backtrack.
  With this update, breadcrumbs now appear consistently, improving navigation, usability, and overall user experience across the admin interface.
  
  
• Z10-25243 | Tier Price Import Failing During Product Price Import
  Resolved a defect where tier prices were not being imported during bulk product price imports. While base product prices were processed correctly, tiered pricing data was ignored, resulting in incomplete pricing configurations.
  The import logic has now been corrected to support both base and tier pricing simultaneously, ensuring accurate pricing structures are applied during bulk updates.

 

• Z10-25547 | Unable to Fetch Sitemap for Product Feed
  Fixed an issue where the system failed to fetch the sitemap during product feed generation. This caused interruptions in generating accurate product feeds for external systems and integrations.
  The sitemap fetching process has now been stabilized, ensuring smooth and uninterrupted product feed creation.
  
  
• Z10-25607 | Incorrect Validation During CSV Import
  Corrected a defect where wrong validation messages appeared while importing CSV files. This mismatch between validation rules and actual requirements confused users and slowed down the import process.
  The system’s validation checks are now properly aligned with import rules, ensuring accurate error reporting and smoother CSV imports.
  
  
• Z10-25971 | Issues with Color Shade and Size Import/Update
  Resolved issues where Color Shade and Size attributes were not properly imported or updated during product data imports. This led to incomplete product attribute mapping, causing discrepancies in product variants.
  The import/update logic has been fixed to handle these attributes correctly, ensuring accurate and consistent product attribute management.
  
  
• Z10-26700 | Cybersource Payment Method Configuration – Order Creation Blocker
  Fixed a critical blocker where orders could not be created if Cybersource payment method configurations were misconfigured. This issue prevented order placement, creating a disruption in the checkout and payment process.
  The payment configuration logic has been refined to ensure order creation works reliably with Cybersource, supporting smooth and uninterrupted transactions.
  
  
• Z10-26743 | Available Plugins – Generic Error
  Resolved a stability issue where accessing the Available Plugins page triggered a generic error, preventing users from viewing and managing plugins.
  The underlying defect has been corrected, and the Available Plugins page now loads consistently, allowing administrators to manage extensions without interruption.
  
  
• Z10-22044 | Invalid Media URL in Global Attribute Type – File
  Resolved an issue where the system generated invalid or broken media URLs when global attributes of type File were used. This caused files linked through such attributes to become inaccessible, resulting in missing or unusable assets across different modules that consumed the API.
  The fix ensures that media URLs are now accurately generated and consistently valid, allowing seamless file retrieval, correct linkage across systems, and better stability for integrations that depend on these attributes.

CMS

• Z10-23795 | StoreExperience: Incorrect Validation Message During CMS Publish
  Resolved an issue in the StoreExperience module where an incorrect validation message was displayed during CMS content publishing. The system incorrectly mentioned “Catalog” in the validation prompt instead of “CMS Content,” which confused users attempting to identify and correct publishing errors.

  This update ensures that validation messages now accurately reference CMS Content, providing clear and relevant guidance during the publishing process. By aligning the terminology with the actual module in use, the fix improves usability, reduces misinterpretation, and enhances overall content management workflows.

Other Improvements

• Z10-25719 | Order List API Filtering by ExternalId with Null Values Failing
  Corrected a defect where the Order List API was unable to properly filter orders based on the ExternalId field when null values were present in the dataset. Previously, this issue caused incomplete or inaccurate filtering results, especially when filtering for orders without an ExternalId. The API has now been updated to handle null values explicitly, ensuring that both non-null and null-based filter queries return the expected and accurate results.
  
  
• Z10-26038 | Mismatch Between UI and API Promotion Start Date
  Resolved a data consistency issue where the Promotion Start Date displayed in the UI differed from the value returned by the API. This confused users relying on both systems for accurate promotion scheduling. Additionally, in some instances, the API would return null values for promotions that had valid start dates. The API logic has been aligned with the UI behavior, and now consistently returns accurate start dates across both platforms, including valid defaults where applicable.
  
  
• Z10-26039 | Promotion API Returning Null for PromotionImage Values
  Fixed a bug in the Promotion API where the fields AttributeValue and AttributeDefaultValue related to promotion images were incorrectly returned as null, even though images were visible and correctly configured in the UI. This led to confusion and broken image references in systems depending on API data. The API has been corrected to accurately retrieve and return the appropriate image-related attribute values, reflecting the true state of promotional configurations.
  
  
• Z10-26705 | Cart API Not Retrieving Attribute and Image Details
  Addressed a critical issue in the Cart API where the response payload lacked essential attribute details (e.g., size, color) and product images associated with cart items. This resulted in incomplete data for users reviewing cart contents via API integrations. The issue was traced to a missing linkage in the data retrieval layer. The API logic has been updated to ensure comprehensive inclusion of all associated attributes and imagery, improving downstream display and processing.
  
  
• Z10-25051 | Approval Management Decimal Value Issue
  Fixed a data processing defect in the Approval Management section for Admin Users, where decimal values (e.g., budget limits, thresholds) were not handled properly. This led to incorrect rounding or truncation in workflows relying on precise decimal values. The decimal handling logic has been revised to accurately process, store, and retrieve decimal values as expected, ensuring precision and preventing financial discrepancies or approval miscalculations.

 

• Z10-26408 | Unable to Reset Admin User Password
  Resolved a high-priority issue where Admin Users were unable to reset their passwords due to a failure in the reset logic or email trigger mechanisms. This resulted in administrative lockouts, affecting access to critical system functionalities. The password reset functionality has been thoroughly reviewed and restored, including validation of token generation, expiration handling, and email delivery, ensuring a secure and reliable reset process moving forward.
  
  
• Z10-24478 | Versioning in CMS Page Builder
  The CMS Page Builder now includes versioning support, allowing content creators and administrators to track all changes made to pages, restore previous versions when needed, and maintain a detailed history of all modifications. This feature enhances content management, collaboration, and transparency across the content lifecycle.
  Improved Content Accuracy: By maintaining a full version history, errors or unintended changes can be easily identified and reverted, reducing the risk of publishing incorrect or low-quality content.
  Enhanced Collaboration & Workflow Transparency: Versioning provides visibility into who made changes, when they were made, and what exactly was altered, ensuring better collaboration across teams. 

Open Source Enhancements and Fixes

Saved Cart

• Z10-5988 | Saved Cart Filter Not Working
  Resolved a functionality issue in the Saved Cart module where the applied filters were not working as expected. Both shoppers and administrators faced difficulties narrowing down saved cart results based on common filter criteria such as cart name, creation date, or user. This led to inefficiencies and increased time spent searching for specific carts. The filtering logic has now been corrected, ensuring that the module accurately processes all supported filters and returns the appropriate filtered results. This improves usability and speeds up cart management operations.

 

• Z10-21769 | Failed to Save Cart When Quantity Exceeds Available Stock
  Resolved an issue that prevented users from saving a cart if it contained items with quantities exceeding available stock. Previously, instead of providing a helpful validation message or fallback behavior, the system would abruptly fail the cart save operation, which created a poor user experience. With this fix, the system now gracefully handles over-quantity scenarios by either allowing the cart to be saved with a warning or by notifying the user with a clear validation message, without interrupting the workflow.

 

• Z10-25006 | Saved Cart Created Date Displays Incorrectly on Webstore for Some Time Zones
  Fixed a time zone-related display issue where the "Created Date" of saved carts appeared incorrectly for users in certain regions. This discrepancy led to confusion among shoppers trying to track when carts were created, especially across global storefronts. The issue stemmed from inconsistent handling of time zone offsets in the frontend. The system has been updated to ensure accurate and consistent date-time rendering based on the user’s local time zone, enhancing clarity and trust in the saved cart history.

• Z10-26262 | Saved Carts Delete Button Enabled Without Records
  Addressed a UI/UX defect where the "Delete" button on the Saved Carts screen remained enabled even when no cart records were available. This confused and implied that an action could be taken when none was possible. The UI logic has now been corrected so that the delete button is properly disabled when there are no saved carts, aligning with standard interface behavior and improving overall user experience by removing misleading elements.

Checkout & Orders

• Z10-25002 | Checkout Page: Order Can Be Placed Without Billing Address for New Retail User
  Resolved a critical validation gap in the checkout process where new retail users were able to complete orders without entering a billing address. This allowed orders to bypass required fields, resulting in incomplete or invalid billing information in order records. The fix implements stricter mandatory validation rules, ensuring that a valid billing address must be provided before the order can be placed. This correction brings the checkout process into alignment with expected data integrity and compliance standards.
• Z10-24599 | Shipping Method Not Loading for Guest Users
  Addressed a defect where shipping methods failed to load during checkout for guest users, blocking them from completing purchases. This issue stemmed from a breakdown in eligibility checks or session handling for unauthenticated users. The update ensures that the system accurately identifies and loads applicable shipping methods based on location and cart contents, enabling a seamless and functional guest checkout experience.

 

• Z10-26443 | Checkout: State Field Defaults Incorrectly on Editing Shipping Address
  Resolved a UI logic issue during address editing in checkout, where the State field would incorrectly default to the first option in the dropdown list (index 0) instead of reflecting the previously selected value. This led to incorrect address data and prevented valid shipping method retrieval. The fix ensures that when users edit their shipping address, the State selection now persists properly, maintaining the integrity of the address and allowing accurate shipping calculations.

 

• Z10-26504 | Checkout/Quote: Shipping Methods Not Rendered for Guest Users
  Fixed an issue where guest users were unable to see available shipping methods on both the Checkout and Quote pages. This defect prevented them from finalizing their orders and quotes, resulting in a broken user journey. The resolution ensures that shipping methods are consistently rendered across all user types, regardless of authentication status, facilitating smoother order completion.

 

• Z10-26512 | Tax Field Not Appearing on Checkout Page
  Resolved an issue where the Tax field was missing from the checkout page, leading to incomplete pricing visibility for shoppers. Without this field, users couldn’t see the full cost breakdown, which could lead to confusion or cart abandonment. The fix restores the tax calculation and display logic, ensuring that tax information is always visible and correctly calculated during the checkout process.

 

• Z10-26669 | Tax Fields Missing When Account Associated to User
  Addressed a conditional display issue where tax fields disappeared from the checkout and post-checkout pages when a shopper’s user account was linked to a specific account entity. This led to incomplete or misleading order summaries, especially in B2B scenarios. The fix ensures that tax fields appear reliably across all checkout flows, regardless of the user’s account association, maintaining consistency in pricing transparency.

 

• Z10-26544 | Order Summary Displaying $0 for Configurable Products
  Fixed a pricing issue in the Order Summary section where configurable products (e.g., items with variants like size or color) showed a $0 price, despite having a valid selection and actual price. This miscalculation affected shopper trust and could disrupt conversion rates. The update ensures that accurate pricing is displayed for all configurable products in the order summary, reflecting the selected variant's true cost.
• Z10-24120 | “Checkout As Guest” Button Missing on Login Page
  Resolved a UI flaw where the "Checkout As Guest" option was absent from the login page, limiting the flexibility for users who preferred not to register for an account. This impacted conversion by adding unnecessary friction. The fix reinstates the guest checkout option on the login screen, restoring a critical feature that supports smoother and faster checkouts for non-registered users.

Wishlist

• Z10-23510 | Wishlist: Add to Cart Button Functional for Products Without Price
  Resolved a logic flaw in the Wishlist functionality where the "Add to Cart" button remained visible and functional for products that lacked valid pricing information. This allowed users to add incomplete or invalid items to the cart, potentially causing errors downstream in checkout and order processing. The fix introduces proper validation and UI controls to ensure that the "Add to Cart" button is either hidden or disabled when a product in the wishlist has no associated price, maintaining the integrity of the cart and improving the user experience.

• Z10-26564 | Wishlist Pagination Not Working with Per Page Selection
  Resolved a defect in the Wishlist module where pagination failed to respond correctly to changes in the “per page” dropdown selection. Users attempting to view more or fewer items per page were unable to navigate properly through larger wishlists, leading to usability issues. The fix ensures that pagination now dynamically adapts to the selected per-page value, offering a consistent and intuitive browsing experience across various page configurations.

 

Search & Typeahead

• Z10-25279 | Typeahead Window Remains Open After Clicking Same Suggestion
  Resolved a user interface issue on the product detail page where the typeahead search window (autocomplete suggestions) remained visible after repeatedly clicking the same suggestion. This led to a cluttered and confusing browsing experience, as users expected the suggestion list to close upon selection. The fix enhances user interaction by ensuring that the typeahead properly closes when a suggestion is clicked—regardless of whether it's selected once or multiple times—providing a cleaner and more intuitive experience.

• Z10-26430 | Typeahead Search Not Working in QA Environment
  Addressed a critical issue in the QA build (v10.3.1.0) where the typeahead search functionality was non-operational, blocking testers from performing search validation or navigation tasks. This instability disrupted the quality assurance process and delayed feedback cycles. The fix restores full functionality to the typeahead feature, ensuring it now operates reliably and consistently across all QA environments, allowing thorough and uninterrupted testing.

 

• Z10-26452 | CMS Pages Not Appearing in Webstore Search Results
  Resolved an indexing issue where CMS (Content Management System) pages were not included in the webstore's search results, which reduced the visibility of important informational or marketing content (e.g., FAQs, return policies, promotional pages). The problem was traced to a failure in properly indexing these pages in the search engine. The fix ensures CMS pages are now correctly indexed and returned for relevant queries, enhancing search completeness and discoverability of non-product content.

 

Address Book

• Z10-25594 | Incorrect Success Message on Editing Address
  Resolved a messaging inconsistency in the Address Book module where users received an inaccurate or misleading success message after editing and saving an existing address. This caused confusion about whether the update had been successfully applied. The fix ensures that the system now displays a correct and context-appropriate confirmation message, enhancing user confidence and clarity during address management tasks.
• Z10-25952 | Imported Customer Address Not Appearing During Checkout | Edit Redirects to 404
  Addressed a critical issue where imported customer addresses—typically added through backend systems or third-party integrations—were not visible during the checkout process, preventing users from selecting them for billing or shipping. Additionally, attempts to edit these addresses redirected users to a 404 error page, breaking the navigation flow. The fix ensures that imported addresses are now properly recognized, displayed, and editable in the frontend, delivering a seamless and error-free checkout experience.

UI & Validation

• Z10-18751 | White Background Appears Behind Pop-Up
  Resolved a UI rendering issue where a white background appeared behind modal pop-ups, disrupting the visual hierarchy and aesthetic consistency of the interface. This white overlay could confuse users by obscuring the modal or breaking the immersive design experience. The fix restores the appropriate backdrop styling, ensuring pop-ups now appear with the intended overlay or transparency, delivering a seamless and visually polished user experience.

• Z10-20364 | Missing Full Stop in User Approval Request Validation Message
  Corrected a grammar oversight in the User Approval Request validation message, where a full stop (period) was missing at the end of the sentence. While minor, this impacted the professional tone and readability of system feedback. The fix applies standard punctuation rules, ensuring that all validation messages follow consistent grammar and formatting, contributing to a more polished and user-friendly interface.
• Z10-24584 | Separator Line Missing in Checkout Additional Info Section
  Resolved a UI issue on the checkout page where the separator line meant to visually divide the “Additional Info” section was not rendering, leading to a flat and cluttered layout. The absence of this line affected content structure and made it harder for users to visually distinguish between sections. The fix reinstates the separator line, improving layout clarity and overall page organization.

 

• Z10-24586 | Promotions Title Font Size Inconsistent on Checkout Page
  Resolved a UI inconsistency where the font size of the “PROMOTIONS” title appeared smaller than the “ADDITIONAL INFO” title on the checkout page. The fix aligns typography for a consistent design.Resolved a typographic inconsistency on the checkout page where the “PROMOTIONS” title appeared with a smaller font size than the “ADDITIONAL INFO” title, breaking the visual hierarchy and creating a disjointed look. The fix standardizes the heading styles across sections, ensuring that title fonts are consistent in size and weight, resulting in a cleaner and more cohesive user interface.

 

• Z10-26091 | Incorrect Validation Message on Login for Self Registration with Admin Approval
  Fixed a messaging error in the Self Registration with Admin Approval flow, where users attempting to log in without admin approval received an inaccurate or misleading error message. This led to confusion and unnecessary support requests. The fix ensures that the validation message now clearly explains the status of the account and the need for admin approval, improving user understanding and system transparency during login attempts.

Catalog & Products

• Z10-25310 | Configurable Products Added Without Pricing
  Resolved a critical issue where users were able to add configurable products to the cart without valid pricing, resulting in incomplete or invalid cart entries. This occurred when product variants (e.g., size, color) were selected but had no pricing assigned at the configuration level. The fix introduces a pricing validation mechanism that checks whether all required selections have valid prices before allowing the product to be added to the cart, ensuring data integrity and a smoother purchasing experience.

• Z10-26398 | Associated Products Not Displaying for Bundle and Grouped Products
  Fixed a visibility issue where associated products linked to bundle and grouped product types were not displaying on the webstore, which disrupted the understanding of how these composite products are structured. Shoppers were unable to see or interact with the child products, affecting discoverability and purchase decisions. The fix restores proper front-end rendering of all associated products, ensuring they are now consistently visible across all applicable product detail views.

 

• Z10-26423 | Unwanted Error Displayed on Product Detail Pages (PDPs)
  Addressed a defect where error messages were being shown on Product Detail Pages (PDPs) without any actual issue present—confusing users and undermining trust in the shopping experience. These messages were triggered erroneously due to loose or overly broad error handling in the page logic. The fix tightens error validation conditions so that messages now appear only when a real issue is detected, eliminating unnecessary alerts and preserving a clean, professional UI.

 

• Z10-26594 | Swatch Images Not Displayed on Webstore Quick View, PLP, and PDP
  Resolved a UI rendering issue where swatch images—used to visually represent product variations (e.g., color or style)—were not appearing on Quick View, Product Listing Pages (PLPs), and Product Detail Pages (PDPs). This created gaps in the visual browsing experience and made it harder for shoppers to distinguish between options. The fix ensures swatch images now load and display correctly across all relevant components, delivering a more engaging and intuitive shopping experience.

Other Fixes

• Z10-12472 | Missing Invalid Coupon Code Error Message
  Resolved an issue where no error message was displayed when shoppers attempted to apply an invalid coupon code during checkout. This created confusion, as users were left without feedback about why the discount did not apply. The fix ensures that an accurate and contextual error message is now shown, improving clarity and user trust in the coupon experience.

• Z10-20904 | Shopper Unable to Log In With Valid Email Containing Spaces
  Fixed a login issue where shoppers entering valid email addresses with accidental leading or trailing spaces were blocked from logging into the webstore. The system failed to trim these spaces before validation, incorrectly treating the input as invalid. The fix introduces input sanitization, ensuring the email field is trimmed automatically to support a smoother and more forgiving login experience.

• Z10-24803 | Back Button Missing in Create Order Template
  Resolved a UI inconsistency in the Order Template module where the Back button was present on the Edit Template screen but missing on the Create New Template screen. This disrupted navigation and forced users to rely on browser controls. The fix ensures the Back button is consistently available across both screens, providing intuitive and uniform navigation.
• Z10-25036 | Thank You Page Missing "Give Us Feedback" Button
  Resolved an issue on the Thank You page after order completion, where the “GIVE US FEEDBACK” button was missing. This eliminated a key opportunity for post-purchase engagement and customer input. The fix ensures the button is always rendered as intended, helping businesses collect valuable user feedback at the optimal moment.

 

• Z10-25307 | Shopping Cart Variant Description Disappearing
  Addressed a defect where the variant description (e.g., color, size) of the first product in the shopping cart would disappear after a second product was added. This led to a loss of product context for users reviewing their cart. The fix ensures that variant details are persistently and accurately displayed for all cart items.
• Z10-25509 | Products Page Search & Filter Criteria Not Retained
  Resolved a usability issue on the Products page where search and filter selections were lost upon navigation or refresh, forcing users to reapply filters repeatedly. This caused workflow inefficiencies. The fix introduces state retention, ensuring that filter criteria remain active until users intentionally clear or modify them.

• Z10-25924 | Created Order/Quote Email Showing Zero Shipping and Tax
  Fixed an issue where system-generated order or quote confirmation emails displayed $0 for shipping and tax, even when valid charges existed. This misrepresentation caused confusion among customers and stakeholders. The fix ensures that accurate shipping and tax values are now reflected in all related emails, preserving transactional transparency.
• Z10-25590 | Message Not Displayed for Impersonation Users
  Resolved a functional gap where no indicator message was shown when an admin or user was impersonating another user, leading to uncertainty about session context. The fix introduces a clear system message or banner during impersonation sessions, improving clarity, accountability, and security awareness.
• Z10-25603 | Search and Filter Criteria Not Retained
  Addressed a broader recurrence of the issue affecting multiple modules, where search and filter selections were lost after navigating away or refreshing the page. Users had to reapply filters manually, disrupting efficiency. The fix ensures that search and filter settings are persistently retained across sessions until explicitly reset by the user.
• Z10-26764 | Login Error Preventing User Creation
  Resolved a critical authentication bug where users faced login errors that also blocked the creation of new users, disrupting core workflows and user onboarding. The fix corrects the underlying login issue, fully restoring user creation functionality and ensuring reliable access and setup processes.

• Z10-26895 | Confusing Validation When Adding Same Product to Cart
  Resolved a UX issue where confusing or unclear validation messages were displayed when a shopper attempted to add the same product multiple times to the cart. The error messages did not explain the duplication behavior, leading to frustration. The fix introduces clear, contextual validation messaging, helping users understand the reason and how to proceed.
  
  
• Z10-26906 | Bundle Product Child Items Not Displaying in Cart
  Addressed a cart rendering issue where child items of a bundle product were not displayed once the bundle was added to the cart. This disrupted transparency and made it difficult for shoppers to verify what was included. The fix ensures that all child items now display clearly under their parent bundle, improving cart visibility and trust.
• Z10-26931 | Reorder From Order History Failing
  Fixed a functional defect where shoppers attempting to reorder past purchases from the Order History page were unable to complete the reorder process. This impaired a key convenience feature. The fix restores full reorder functionality, allowing users to quickly repurchase previous orders without disruption.