November 27, 2025 release notes

Tickets

1. KOD-24408: Templated orders
   • Regression Tests
   • Case 1
     • For the regression test, we will navigate to the following pages. Make sure they load properly:
     • Home Page (or any page where the header is included).
     • Cart page, on all three tabs.
     • Catalogs screen.
     • Company Catalogs details screen.
     • Customer Catalogs details screen.
     • Product List screen.
     • Product details screen.
   • Tests
   • Case 1
     • For this test, we need to check that the “Catalog” text has been replaced with “Order Templates” in the following places:
     • Header.
     • Left to Order History Status.
     • Logged-In: Next to Shop By Category.
     • Logged-In: Mobile menu, next to Order History Status.
     • Cart.
     • Actions dropdown.
     • Both modals.
     • /catalogs route
     • h1 h2 titles and paragraphs in both General and “My” section.
     • Add buttons.
     • Inside both “Add” modals.
     • /company-catalog details screen.
     • Breadcrumb.
     • Edit modal title.
     • Delete modal title and in the paragraph in 3 places.
     • /customer-catalog details screen.
     • Breadcrumb.
     • Edit modal title.
     • Delete modal title and in the paragraph in 3 places.
     • Product.
     • Details page productList “Add to Order Template” button in both grid and list views.
     • Make sure that when you click the button to Add, after the spinner disappears the text shows “Add to Order Template” again.
2. KOD-25067: Integration
   • Regression Tests
   • Case 1
     • You need to perform a regression on the pricing screen in the operations portal.
   • Case 2
     • You need to perform a regression by releasing any order.
3. KOD-26489: Payments - Canadian EFT
4. KOD-26664: Business Central Integration
5. KOD-28331: Customer Group Roles Issues
   • Regression Tests
   • Case 1
     • Check permission of page: http://localhost:8080/spcu/catalogs , try to check whether the button “add catalog“ appears when you have the right permission.
     • When we are assigning the “ companyAdmin “ role directly to the customer, the button “add catalog“ should appear.
     • When we are assigning a customer permission group which includes the role: “ companyAdmin “.
     • Go to page: http://localhost:8080/operations/customers/1024/group-roles and assign group: “ testCatalogGroup “ which has role: companyAdmin.
     • After assigning testCatalogGroup will automatically assign the companyAdmin role.
     • Then again check page: http://localhost:8080/spcu/catalogs whether button is appears on the current page.
6. KOD-28457: CC payment type for web customer order
7. KOD-28522: B2B tax validation with multiple customers (SASGE rules) Created From Ticket 32296
   • Regression Tests
   • Case 1
     • Have the new setting avataxRecalculateTaxabilityOnItemsForSpecialAddressCode disabled and taxEngine = Avalara.
     • Create an order and make sure you receive taxes from Avalara during checkout at this step:
     • Validate that no error appears on the screen or in the logs.
   • Tests
   • Case 1
     • Enable the new setting avataxRecalculateTaxabilityOnItemsForSpecialAddressCode.
     • Make sure also that the taxEngine setting is Avalara.
     • Follow the example on the video and validate the tax now is correct. In the logs you should be able to see the SASGE lines checked by the state used during the checkout process.
     • Do not create an order. We only need to validate taxes during checkout at step 3.
     • Steps:
     • Use credentials provided and add items to the order.
     • Use one single order address.
     • Select the corresponding state
     • Make sure that when moving from step2 to step3 we are taking that state into account when calculating taxes (In the logs we should see something like:
     • [JS] SASGE not found with shipto and state. Looking in SASGE table without shipto for code .. )
     • Also, based on the customer, one specific item is marked as non taxable using the SASGE records so we should not take that item into account during tax calculation on Avalara (Compare the cases that customer shows in the video).
8. KOD-28585: Store Credit Batch Out Enhancement
9. KOD-28623: Maintain the currency field on the payment records
10. KOD-28781: Limit Characters in PO field on checkout
    • Regression Tests
    • Case 1
      • Please check if all 3 checkout pages look as usual.
    • Case 2
      • Please test that the PO input field works as usual and we can place the order.
      • Please check if the PO value is correct.
11. KOD-28811: ERP User Credentials
12. KOD-28822: Active field Integration with ICSP
13. KOD-28828: PO field limit Created From Ticket 41730
    • Tests
    • Case 1
      • Enable inforEnablePurchaseOrderCharacterLimitExceptionOnOrders setting.
      • Open any order.
      • Put more than 22 chars on the Purchase Order field.
      • Go to /api/system/order/{orderID}/discrepancies endpoint.
      • Execute it.
      • You should see EXCEPTION in the result.
      • Also, do next:
      • Test exactly 22 chars. You should not see EXCEPTION.
      • Test 23 chars, You should see EXCEPTION.
      • Exception:
      • {
      • "success": true,
      • "code": 200,
      • "messages": [],
      • "errors": [],
      • "data": {
      • "exceptionCount": 1,
      • "warningCount": 0,
      • "order": [
      • {
      • "code": null,
      • "entityType": null,
      • "entityID": null,
      • "field": "purchaseOrder",
      • "type": "EXCEPTION",
      • "message": "Value exceeds the maximum ERP length"
      • }
      • ],
      • "orderItems": [],
      • "orderDiscounts": []
      • },
      • "requestId": "7OAYUZ-20251124225736"
      • }
    • Case 2
      • Disable inforEnablePurchaseOrderCharacterLimitExceptionOnOrders setting.
      • Open any order.
      • Put more than 22 chars on the Purchase Order field.
      • Go to /api/system/order/{orderID}/discrepancies endpoint.
      • Execute it.
      • You should not see any errors.
14. KOD-28829: Add campaign UX update to web repo
    • Regression Tests
    • Case 1
      • Log out of the operations portal.
      • Go to any category page on the commerce site.
      • Verify that the Actions dropdown button does not render.
      • Log in to the operations portal.
      • Go to any category page on the commerce site.
      • Verify that the Actions dropdown button now renders.
      • Click Manage Category.
      • Verify that a dialog opens.
      • Make changes and save.
      • Verify that the changes are applied successfully.
    • Tests
    • Case 1
      • Log in to the operations portal.
      • Go to any category page on the commerce site.
      • Verify that the Actions dropdown button renders.
      • Verify that it contains two options: Manage Category and Create Campaign.
      • Click Create Campaign.
      • Verify that a dialog opens.
      • Enter a name and description, then save.
      • Verify that it successfully creates a public campaign using the correct endpoint.
      • Verify that the success dialog renders with the correct information.
15. KOD-28840: Update product attribute cache when user updates order fields in the operations portal
    • Regression Tests
    • Case 1
      • Select or create some filter category on page: http://localhost:8080/operations/filter-categories.
      • Go to the selected filter category → go to the attribute tab → create an attribute record and assign some products.
      • Then change one of the current fields: code, name. order.
      • Go to the event list page: http://localhost:8080/operations/events/all , try to find the last new event with type: EventQueue-CategoryProductsReindexEvent.
      • The event contains categoryID of changed filter category attribute.
      • Go to Scheduler page: http://localhost:8080/operations/scheduler and run SolrReindexJob
      • On all products which are assigned to the filter category attribute will update the field: lastModified and the event mark as completed.
      • To check result please go to page: http://localhost:8080/operations/products/data/9904/custom-records , select updated attribute and go to terminal section of browser to find response of GET endpoint: http://localhost:8080/api/system/productDocument/9904/list to check whether updated the fields: code, name or categoryOrder.
    • Case 2
      • Try to update field: position for selected filter category, on page: http://localhost:8080/operations/filter-categories
      • Select some product which is assigned to the filter category and check whether it is updated on product.
16. KOD-28847: Credit App - Add additional company fields to credit app dto
    • Tests
    • Case 1
      • Check whether it populates the new field: website on company side after populating it on credit application page.
      • Use swagger PATCH endpoint: api/account/creditApplication.
      • Check whether it populated on the company side on the operations portal.
17. KOD-28881: Implementation Created From Ticket 42094
18. KOD-28889: Add social link options for Instagram
    • Regression Tests
    • Case 1
      • For the regression test, make sure opening the Themer and changing the value of the storeInstagramURL setting doesn’t break the page.
    • Tests
    • Case 1
      • To test this ticket, you need to log into the operations portal.
      • Go to settings and make sure there is a storeInstagramURL setting created.
      • Still logged in, we will now go to the commerce site. Open the Themer component and scroll down to “Socials”. You should now see a field to enter an Instagram link.
      • Its value should always match the value of the setting after updating and reloading.
      • Now, if we scroll down to our page footer, you should see an Instagram icon next to the YouTube icon. Clicking it should redirect you to the link in the setting value.
      • When there’s no value in the setting, the Instagram icon should remain hidden.
    • Case 2
      • We will repeat the test cases of the previous test but now on a Blog Post page.
19. KOD-28897: Events with Active set to "No" are still showing on website
    • Regression Tests
    • Case 1
      • For this test, we need to make sure that the events page in the commerce sites loads properly and that each event redirects you to its respective page.
    • Tests
    • Case 1
      • For this test, we need to go to the commerce site - Events screen.
      • You should only see events for Child pages from the Events Calendar page that are set to Active=Yes in the operations portal.
      • Child pages from the Events Calendar page that are set no Active = No should not be displayed.
20. KOD-28898: Order Checkout Flow - Pickup/Contact Person
    • Tests
    • Case 1
      • For this test, we will go to the cart screen in the commerce site after we’ve added an item.
      • Above the Order Notes field, the new legend should say “Please list the name and phone number of the person we can call to ask any questions related to this order. You may also use this space to add notes or questions for our team.”
      • This should ideally fit in one line on regular desktops and break to two lines on tablets to lower width devices.
21. KOD-28910: Pricing Discrepancies
22. KOD-28914: Update to Customer Guide UX to hide the box if only one option is available
    • Regression Tests
    • Case 1
      • Make sure that the first step of checkout works without any bugs and errors for logged in users.
    • Tests
    • Case 1
      • Log in as a customer to the commerce site, add some items to the cart and proceed to checkout. The guide box behavior has been updated to follow these 3 cases:
      • If there already is a guide in the cart - show the “Remove option“.
      • If the user has already acquired one guide - hide the guide box, even if the other guide is available.
      • If the user can select both guides - show both options.
23. KOD-28918: Have Storeroom Fields Selected on Cash Quote Persist
    • Regression Tests
    • Case 1
      • Go through the checkout flow and make sure everything works correctly both for spot buys and normal orders.
      • You should be able to add/edit information on the final checkout tab without issues along with placing the order.
    • Tests
    • Case 1
      • Create a spot buy order, add information to the following fields on the item in the operations portal:
      • Department
      • Gl Account
      • Customer Asset
      • Work Order Number
      • Then put the order in your cart as a customer, and then on the final checkout tab, check that you can see this information.
    • Case 2
      • After the previous step, continue to place the order. Check that everything works correctly without issues.
24. KOD-28919: Update Terms on Credit App
    • Regression Tests
    • Case 1
      • Apply for a credit or use an existing account.
      • Confirm credit application loaded properly.
    • Tests
    • Case 1
      • On a credit application, clear out preferred payment method options.
      • Scroll to the signature section.
      • Confirm COD terms are displayed.
      • Select Credit Account option from the dropdown.
      • Scroll to the signatures section.
      • Confirm Credit Account terms are displayed.
      • Select COD/CASH option and scroll to the Signature section.
      • Confirm COD terms are displayed.
25. KOD-28921: Limit PO characters at checkout
    • Regression Tests
    • Case 1
      • Make sure the PO input on the third step of checkout works fine and you can still checkout with a PO that is less than 21 characters.
    • Tests
    • Case 1
      • On the third page of checkout, type a PO that is more than 21 characters → try to checkout → you should not be able to checkout and get a message saying that the PO needs to be less than 21 characters.
    • Case 2
      • On an order, enter a PO longer than 21 characters. Reload the page and notice the PO has been trimmed to 21 characters.
26. KOD-28942: Parser from ticket 42685
27. KOD-28943: Parser request
28. KOD-28946: Parser request
29. KOD-28956: Parser update
30. KOD-28978: Parser from Ticket 32140
31. KOD-28983: Implementation
32. KOD-29016: Payments update