All Releases
February 19, 2026 February 12, 2026 January 22, 2026 February 5, 2026 January 29, 2026 January 15, 2026 January 8, 2026 January 1, 2026 December 25, 2025 December 18, 2025 December 11, 2025 December 4, 2025 November 27, 2025 November 20, 2025 November 13, 2025 November 6, 2025 October 30, 2025 October 23, 2025 October 16, 2025 October 9, 2025 October 2, 2025 September 25, 2025 September 18, 2025 September 11, 2025 September 4, 2025 August 28, 2025 August 21, 2025 August 14, 2025 August 7, 2025 July 31, 2025 July 24, 2025 July 17, 2025 July 10, 2025 July 3, 2025 June 26, 2025 June 19, 2025 June 12, 2025 June 5, 2025 May 29, 2025 May 22, 2025 May 15, 2025 May 8, 2025 May 1, 2025 April 24, 2025 April 17, 2025 April 10, 2025 April 3, 2025 March 27, 2025 March 20, 2025 March 13, 2025 March 6, 2025 February 27, 2025 February 20, 2025 February 13, 2025 February 6, 2025 January 30, 2025 January 23, 2025 January 16, 2025 January 9, 2025 January 2, 2025 December 26, 2024 December 19, 2024 December 12, 2024 November 28, 2024 November 21, 2024 November 14, 2024 November 7, 2024 October 31, 2024 October 24, 2024 October 17, 2024 October 10, 2024 October 3, 2024 September 26, 2024 September 19, 2024 September 12, 2024 September 5, 2024 August 29, 2024 August 22, 2024 August 15, 2024 August 8, 2024 August 1, 2024 July 25, 2024 July 18, 2024 July 11, 2024 June 27, 2024 June 20, 2024 June 13, 2024 June 6, 2024 May 30, 2024 May 23, 2024 May 16, 2024 May 9, 2024 May 2, 2024 April 25, 2024 April 18, 2024 April 11, 2024 April 4, 2024 March 28, 2024 March 21, 2024 March 14, 2024 March 7, 2024 February 29, 2024 February 22, 2024 February 15, 2024 February 8, 2024 February 1, 2024 January 25, 2024 January 18, 2024 January 11, 2024 January 4, 2024 December 21, 2023 December 14, 2023 December 7, 2023 November 30, 2023 November 16, 2023 November 9, 2023 November 2, 2023 October 26, 2023 October 19, 2023 October 12, 2023 October 5, 2023 September 28, 2023 September 21, 2023 September 14, 2023 September 7, 2023 August 31, 2023 August 24, 2023 August 17, 2023 August 10, 2023 August 3, 2023 July 27, 2023 July 20, 2023 July 13, 2023 July 6, 2023 June 29, 2023 June 22, 2023 June 15, 2023 June 8, 2023 June 1, 2023 May 25, 2023 May 18, 2023 May 11, 2023 May 4, 2023 April 27, 2023 April 20, 2023 April 13, 2023 April 6, 2023 March 30, 2023 March 23, 2023 March 16, 2023 March 9, 2023 March 2, 2023 February 23, 2023 February 16, 2023 February 9, 2023 February 2, 2023 January, 2023 December, 2022 November, 2022 October, 2022 September, 2022 August, 2022 July, 2022 June, 2022 May, 2022 April, 2022 March, 2022 February, 2022 January, 2022 December, 2021 November, 2021 October, 2021 September, 2021 August, 2021 July, 2021 June, 2021 May, 2021 April, 2021 March, 2021 February, 2021 January, 2021 December, 2020
View all releases

January 8, 2026 release notes

Tickets

  1. KOD-11715: Kodaris - Digital Payment Application
  2. KOD-23338: Deposits on Wrong Company in Pull Payments to ERP CSV Export
  3. KOD-27722: Switch Vendor/Internal Files screen to editable grid
    • Regression Tests
    • Case 1
      • Go to Account Payable → Vendors → Vendor.
      • Check that the UI looks good, there’s no any errors, broken UI components, responsive looks good.
    • Case 2
      • Go to the Internal Files tab.
      • Check that the new grid view looks ok, everything renders good and there’s no any responsive issues.
    • Tests
    • Case 1
      • Go to Account Payable → Vendors → Vendor → Internal Files.
      • Create an internal file for the test.
      • Try to test features of preview file, download, and delete. Check that everything works correctly.
      • Try to click on the type field of this file row, and then change its content by type the new value and then blur. See that the Type field value changed.
      • Try to reload the page and see that the changes are saved.
    • Case 2
      • Try to make multiple updates of the fields. See that the update successfully applied to multiple file entities.
  4. KOD-27810: Order confirmation Email improvements
    • Tests
    • Case 1
      • The test can be performed either by placing an order on the website or by using an existing order in the Operations Portal.
      • Open Operations Portal.
      • Navigate to Orders.
      • Click on the Email icon for a selected order.
      • Select order email.
      • Verify email template.
      • Send and verify email rendering.
      • Send the email to your own email address.
      • Verify the email in:
      • Gmail (web)
      • Mail app
      • Outlook
      • Ensure the design is consistent across all clients and displayed without visual issues.
      • Verify email interactivity.
      • Test product links by clicking on a product and navigating to its page.
      • Test all buttons present in the email.
      • Verify invoice presence.
      • Ensure the standard invoice is included at the bottom of the email.
      • The unit price was removed, so there are no prices.
    • Case 2
      • Generate email for a Received order.
      • Navigate to a Received order.
      • Generate the order email.
      • Verify that the default email template is displayed.
    • Case 3
      • Generate email for a non-Received order.
      • Navigate to any order with a status other than Received.
      • Generate the order email.
      • Verify that the default email template is displayed.
  5. KOD-28049: Order / Invoice Documents
  6. KOD-28408: Share APIs for POD in Customer Portal
    • Tests
    • Case 1
      • For server-side API copy snippets into UserScripts, turn them and check if the response looks like the one in the example’s file.
    • Case 2
      • For client-side API examples you need to set commerce layout on some site and create triggering objects for that, for example buttons. Then Copy code into script and trigger it. In the console you can see the response, which should look like the one in the example’s file.
  7. KOD-28506: Swap Customer PO for Invoice Number Created From Ticket 39818
    • Tests
    • Case 1
      • Setting that turns on sending PO for Invoice Number to a payment provider - is a Company-level setting (a “Developer Fields“ tab on Company details screen):
      • paymentsLevel3DataSendPurchaseOrderNumberForInvoiceNumber - integerValue - 1
      • Also make sure enableLevel3DataFromOrders global setting is enabled.
      • Pay order in CSD (CSD integrated payments).
      • Pay order in the operations portal.
      • If the order has PO populated it should be sent to the payment provider as invoice number.
      • Check transaction details in Payments portal.
  8. KOD-28532: Employee Portal App
  9. KOD-28600: Price tolerance kickouts
  10. KOD-28615: Update AplusErpLogicIntegrator to handle taxes properly for Avalara based on A+ ERP
    • Regression Tests
    • Case 1
      • Make sure both useAplusPricingEngineV2 and useAplusLogicIntegratorV2 are disabled.
      • Create an order.
      • Change delivery address.
      • Add line items.
      • Expected: The new tax logic should NOT run; items should remain in their default state.
      • No ADDRESS_TAXABLE_TYPE , IS_ORDER_TAXABLE settings created.
      • Test this both creating an order in the operations portal and on the customer side using the cart.
    • Case 2
      • useAplusLogicIntegratorV2 = 1.
      • Company with example warehouseCode = "WH1".
      • Address with example warehouseCode = "WH2".
      • Create order.
      • Change delivery address to address with WH2.
      • Expected:
      • Order items get warehouse = "WH2".
      • Order gets warehouseCode = "WH2".
      • WHSE order setting updated.
      • Can also check that nothing is updated when we do the same thing and the setting is set to 0.
    • Tests
    • Test 1
      • For all tests we need the following settings:
      • useAplusLogicIntegratorV2 = 1 and useAplusPricingEngineV2 = 1
      • Create/find a Company with taxableType = "n"
      • Steps:
      • Create an order for this company.
      • Add items to the order.
      • Change the delivery address.
      • Expected: All order items should have taxed = false.
      • Company with taxableType = "y" or blank.
      • Steps:
      • Create an order for this company.
      • Add items to the order.
      • Change the delivery address.
      • Expected: Order items should have taxed = true.
    • Case 2
      • Company with taxableType = "y" (taxable).
      • CompanyAddress with taxableType = "n" (exempt).
      • Steps:
      • Create an order for this company.
      • Change delivery address to the tax-exempt address.
      • Check order items.
      • Expected: All order items should have taxed = false (address overrides company).
      • Company with taxableType = "n" (exempt).
      • CompanyAddress with taxableType = "y" (taxable).
      • Steps:
      • Create an order for this company.
      • Change delivery address to the taxable address.
      • Check order items.
      • Expected: All order items should have taxed = false.
      • for both of these cases we should have.
      • ADDRESS_TAXABLE_TYPE - should contain the address's taxableType value
      • IS_ORDER_TAXABLE - should be "y" or "n" based on company/address logic
    • Case 3
      • Add a new line item to the order via the admin portal.
      • Check the new item's taxed status (it should match the rest of the order items).
    • Case 4
      • Customer account with multiple addresses.
      • One address tax-exempt (taxableType = "n").
      • One address is taxable (taxableType = "y").
      • Steps:
      • Log in as a customer.
      • Add items to cart.
      • Change delivery address to tax-exempt address.
      • Check cart items' tax status.
      • Change delivery address to taxable address.
      • Check cart items' tax status again.
      • Expected: Items should update their taxed status based on the selected address.
  11. KOD-28715: Rule Engine UX Prototype
    • Regression Tests
    • Case 1
      • Ensure that the system menu appears correctly.
      • Ensure that the Rules grid appears and functions correctly, as well as the detail tab and actions tab.
    • Tests
    • Case 1
      • Ensure that a new section has appeared in the system menu - Rules Engine (Beta).
      • Make sure that the Rules Engine (Beta) grid displays the same items as the Rules grid.
      • Make sure that there is a clickable “Add Rule” button in the toolbar. Also, make sure that clicking it creates an empty rule and redirects you to the detail tab for further editing.
      • Make sure that the “when”, ‘condition’, and “then” sections appear in the detail tab, make sure that the form can be filled out and successfully saved (in the “Save” toolbar).
      • Make sure that after saving, the form redirects to the grid and make sure that the elements from the form have been saved in the rule item.
  12. KOD-28731: Blank frame for a saved payment method after removing
    • Regression Tests
    • Case 1
      • Check that the Payment Methods page appears correctly.
      • Check that Items of the "Credit" type are displayed correctly in the Payment Methods tab.
      • Check that Items of the "Credit" type can be edited and deleted in the Payment Methods tab.
      • Check that there are no errors in the console.
      • Check that if there are no Items in the Payment Methods tab, an image similar to the one in the screenshot is displayed.
    • Tests
    • Case 1
      • Verify that Items with the "Store Credit" type are displayed correctly in the Payment Methods tab and look like this.
      • Verify that Items with the "GiftCard" type are displayed correctly in the Payment Methods tab and look like this.
      • Verify that Items with the "Store Credit" type cannot be edited.
      • Verify that Items with the "GiftCard" type cannot be edited.
      • Verify that the delete function works correctly for Items with the "Store Credit" type.
      • Verify that the delete function works correctly for Items with the "GiftCard" type.
      • Verify that deleting or editing cards with the "Credit" types does not create new "empty" cards.
  13. KOD-28750: Check Standard Parser List
  14. KOD-28791: Block Accounts on Hold
  15. KOD-28814: Assign price type to new accounts
    • Regression Tests
    • Case 1
    • Ensure that the company is successfully created when submitting the registration form. (namely BILLING ADDRESS, SHIPPING ADDRESS, Primary Purchaser, Company Owner, Company Name)
    • Tests
    • Case 1
      • Ensure that the company is set to priceTypeCode
      • Make sure that priceTypeCode is successfully saved to CSD.
  16. KOD-28861: PIM Integration for Commerce/Sync Full Data
  17. KOD-28887: Dynamic ShipVia Selection
    • Tests
    • Case 1
      • For this test, we need to place an order.
      • Make sure you’ve selected “Truck Run” as the shipping option and that the delivery address you’ve selected has a defaultShipViaCode value.
      • Once you release the order, the defaultShipViaCode of the delivery address should be sent as the ship via of the order to CSD.
    • Case 2
      • For this test, we need to place an order.
      • Make sure you’ve selected “Truck Run” as the shipping option and that there’s NOT a defaultShipViaCode on the shipping address of your order.
      • You also need to make sure there is a defaultShipViaCode in the company you placed the order from.
      • Once you release the order, the defaultShipViaCode of the company should be sent as the ship via of the order to CSD.
    • Case 3
      • If none of the conditions above are met, the shippingMethod code should be sent as the ship via of the order to CSD.
  18. KOD-28934: Product Configurator - Maintain Configured Product Options When Navigating Between Cart and Product Detail Views in all repos
  19. KOD-28985: Kodaris Dev Examples: SKU Entity
  20. KOD-29000: Vipar Integration
  21. KOD-29003: Account Automation Customer Form Changes
  22. KOD-29010: Order & AP Automation - Development Environment UX
    • Regression Tests
    • Case 1
      • Go to Account Payable → Vendors.
      • Open a random vendor entity.
      • Check that the header with navigation looks good, responsive works well and there’s no any issues with it.
      • Go to Customers → Companies.
      • Open a random company entity.
      • Check that the header with navigation looks good, responsive works well and there’s no any issues with it.
    • Tests
    • Case 1
      • Go to Account Payable → Vendors.
      • Open a random Vendor entity.
      • In the entity tabs select the “Automation” tab.
      • Check that the layout looks good, responsive works well.
      • Go to Customers → Companies.
      • Open a random Company entity.
      • In the entity tabs select the “Automation” tab.
      • Check that the layout looks good, responsive works well.
    • Case 2
      • Go to the Vendor automation page.
      • Click on “Edit Analysis Script” button in the right top corner and set the next value for script for test to see the results UI:
        • invoice.vendorName = "TEST_VENDOR_NAME" ;
        • invoice.invoiceDate = '2023-01-01' ;
        • invoice.reference = 'PO-998877' ;
        • invoice.totalAmount = 1110;
        • invoice.currency = 'USD' ;
        • invoice.dueDate = '2023-01-02' ;
        • invoiceItems.add({
        • description: 'Software License' ,
        • quantity: 1,
        • rate: 250,
        • total: 250
        • });
        • invoiceItems.add({
        • description: 'Consulting Services' ,
        • quantity: 10,
        • rate: 100,
        • total: 1000
        • });
      • Save it. Go back to the “Vendor Automation” page.
      • Try to upload a new file. Check that after file analysis finishes we have the same values and names of the fields in the UI as we set in the script.
      • Go to the script page and try to update some values and keys, for example vendorName}}field renamed to {{ ['Vendor Name'] and change value of reference field. Go back to “Vendor Automation” page.
      • Try to click on the “Re-analyze” button right under the document preview block.
      • After analysis finish check that the values that you changed in the script, also changed in the result after re-analyzing.
      • Try to click the “Download” button, in the top right corner. You will download the results zip file. Unzip it, check that there’s the same names of files according to “Analysis Methods” selected before analysis started + result analysis file.
      • In the bottom left corner click on “Upload Document”. Try to upload one more document for test. Check that after file analyze, the analyze document in the preview is updated.
    • Case 3
      • On the “Vendor Automation” page, click on the “Edit Analysis Script” button. Then go to Revisions. Try to restore to the first revision of the script. Check that the value of the script changed.
      • Go back to the revisions page and restore to the most recent revision. Check that the script is restored correctly.
      • Go to The revisions tab, open specific revision.
      • Check that the code in the revision is readonly. Go to the Detail tab, check that content there rendered correctly.
      • Try to run “Restore” revision from this point. Check that the script changed correctly after restoring.
    • Case 4
      • On the Company automation page check that in the top right corner is a “Edit Analysis Script” button.
      • Click on it and set the next value for script for test to see the results UI:
        • order.vendorName = "TEST_VENDOR_NAME" ;
        • order.invoiceDate = '2023-01-01' ;
        • order.reference = 'PO-0000 ;
        • order.totalAmount = 1110;
        • order.currency = 'USD' ;
        • order.dueDate = '2023-01-02' ;
        • orderItems.add({
        • description: 'Software License' ,
        • quantity: 1,
        • rate: 250,
        • total: 250
        • });
        • orderItems.add({
        • description: 'Consulting Services' ,
        • quantity: 10,
        • rate: 100,
        • total: 1000
        • });
      • Save it. Go back to the “Company Automation” page.
      • Try to upload a new file. Check that after file analysis finishes we have the same values in the UI as we set in script.
      • Go to the script page and try to update some values, for example vendorName and reference . Go back to the “Company Automation” page.
      • Try to click on the “Re-analyze” button right under the document preview block.
      • After analysis finish check that the values, that you changed in the script, also changed in the result after re-analyzing.
      • Try to click the “Download” button, in the top right corner. You will download the results zip file. Unzip it, check that there’s the same names of files according to “Analysis Methods” selected before analysis started + result analysis file.
      • In the bottom left corner click on “Upload Document”. Check that initial view opened.
    • Case 5
      • On the “Company Automation” page, click on “Edit Analysis Script” button. Then go to Revisions. Try to restore to the first revision of the script. Check that the value of the script changed.
      • Go back to the revisions page and restore to the most recent revision. Check that script is restored correctly.
      • Go to The revisions tab, open specific revision.
      • Check that the code in the revision is readonly. Go to the Detail tab, check that content there rendered correctly.
      • Try to run “Restore” revision from this point. Check that the script changed correctly after restoring.
    • Case 6
      • Go to the Automation page of Vendor/Company.
      • Open the “Network” Tab in the Developer Tools.
      • Try to change the “Enable Analysis” selected value. Check that in the network */setting request appeared.
      • Try to change the value of “Enable Analysis” back to the previous value. Check that at this time /vendorInvoiceDocumentAnalysisEnabled or /customerOrderDocumentAnalysisEnabled request appeared.
      • Try to do the same with “Analysis methods” select. In the first time we will see /setting request. In the second time it should be /vendorInvoicePdfDocumentAnalysisMethods or */customerOrderPdfDocumentAnalysisMethods request.
      • After changing these fields try to reload the page and after reload the values of the selects should be the same as before the page reload.
  23. KOD-29023: Kodaris Dev Examples: Preferences entity
    • Regression Tests
    • Tests
    • Case 1
      • To test rest-api/account/preferences , you must be logged in as a customer.
      • To test rest-api/system/preferences , you must be logged in as an employee.
      • Set commerce layout on any site.
      • Create a triggering object (e.g. button ).
      • Copy the provided code into the script.
      • Trigger the object.
      • Open browser console.
      • Verify the response data in the console matches the example described in the file.
  24. KOD-29028: Phase 3 - Payments Report API Integration
  25. KOD-29083: Quick Order from Import File Placement
  26. KOD-29102: Kodaris ERP-Inventory Conversions Import Feature
    • Tests
    • Case 1
      • Open the Operations Portal.
      • Navigate to Inventory Conversions.
      • Test import modes.
      • Click on Import.
      • Test the following options:
        • Create and Update
        • Create Only
        • Update Only
  27. KOD-29153: Extend the Tag for abandoned cart and browse
  28. KOD-29164: Home Page Secondary Banner
    • Regression Tests
    • Case 1
      • Login to the Operations portal.
      • Navigate to CMS > Menus > Secondary banner .
      • Check the variations to ensure Button text and Button URL are present.
      • Click Publish .
      • The text or link should be displayed in the site preview.
      • The layout and the banner block should be displayed correctly.
    • Tests
    • Case 1
      • Go to the Operations portal.
      • Navigate to CMS > Menus > Secondary banner .
      • Remove the text from Button text and Button URL .
      • Click Publish .
      • The banner should not be clickable, and the button should not be displayed.
      • In the mobile version, nothing should overflow outside the image.
    • Case 2
      • Go to the Operations portal .
      • Navigate to CMS > Menus > Secondary banner .
      • Remove text from Button text.
      • Add text to Button URL .
      • Click Publish .
      • The banner should be clickable and work as a link, the button should not be displayed.
      • In the mobile version, nothing should overflow outside the image.
    • Case 3
      • Go to the Operations portal.
      • Navigate to CMS > Menus > Secondary banner .
      • Add text to Button URL and Button text .
      • Click Publish .
      • The banner should not be clickable, the button should be displayed and work as a link.
      • In the mobile version, nothing should overflow outside the image.
    • Case 4
      • Go to the Operations portal.
      • Navigate to CMS > Menus > Secondary banner .
      • Remove all texts.
      • Click Publish .
      • The banner should be the original image size.
      • In the mobile version, nothing should overflow outside the image.
  29. KOD-29188: Create PDSR mappings
  30. KOD-29189: Sync PDSR Records
  31. KOD-29192: Impl - Order / Invoice Documents
  32. KOD-29207: Questions About Sending Automated Messages (Low Stock Notifications)
    • Regression Tests
    • Case 1
    • Make sure you can still place an order.
    • Tests
    • Case 1
      • Add an item to the cart that has a quantity of less than 5 at the location of the order’s warehouse (usually it is the location on the company) → you can add more items or keep only the one → then place the order → the email that is set in the location’s keywords field should get an email with the subject Low Stock Notification with the order confirmation as the body (if no value is set in the location’s keywords, then no email will be sent)
    • Case 2
      • Now place an order with inventory greater than or equal to 5, a low stock notification email should not be sent
  33. KOD-29223: Product Multilingual Translations
  34. KOD-29228: Add Cookie Banner & Dynamically Comment Out Trackers
    • Regression Tests
    • Case 1
      • Load the homepage without accepting/declining cookies.
      • Navigate through key pages: product pages, cart, checkout, login.
      • Accept cookies and continue browsing.
      • Verify console for errors.
      • Expected Results:
      • Before Cookie Consent Choice:
      • Site loads and functions normally.
      • Navigation works correctly.
      • Banner appears but doesn't block site usage.
      • No JavaScript errors in console (except warnings which are expected).
      • After Accepting Cookies:
      • All site functionality continues to work.
      • Page navigation doesn't trigger banner again.
      • Tracking scripts work.
  35. KOD-29238: Web compliance
  36. KOD-29269: Customer App
  37. KOD-29288: Taxes not picked up
  38. KOD-29295: Create server side import for Shared Drive
    • Regression Tests
    • Case 1
      • For this test, you should go to the Shared Drive screen in the operations portal.
      • Make sure the screen loads properly, that you are able to preview file items, download and delete them.
    • Tests
    • Case 1
      • For this test, we need to go to the Shared Drive screen in the operations portal.
      • You should see an Actions dropdown on the top right and the previous Attach File button should be gone.
      • The dropdown offers two options: Attach File Attach Folder.
      • Clicking on Attach File should open your Finder and you should be able to select multiple files to upload. Make sure that they are uploaded properly.
      • Clicking on Attach Folder should open your Finder and you should be able to select folders only to upload. Make sure that the files inside the folder you select are uploaded properly.
  39. KOD-29312: Add Guest vs Customer Menus
    • Tests
    • Case 1
      • Log in to the operations portal.
      • Go to CMS → Menus.
      • Create a new menu header-authenticated.
      • Build menu.
      • Create a new menu footer-authenticated.
      • Build menu.
      • Click Publish.
      • We should see two different menus when logged in and when not logged in.
  40. KOD-29329: OA: Exceptions Notification Email & Warehouse Update
  41. KOD-29331: -99 Invoices, payment notes are not included in the customer PDF
    • Regression Tests
    • Case 1
      • Ensure that when you run sendPDFAutomatedInvoicesToCustomers.js (User Script), 99-invoices are sent successfully.
    • Tests
    • Case 1
      • Ensure that order notes are successfully added to 99-invoice.
  42. KOD-29332: Implement Product Configurator Fix Cart
    • Regression Tests
    • Case 1
      • Go to the Product Details page and confirm that the product description is displayed correctly.
    • Case 2
      • Add any product to the cart and confirm that the product description in the cart is displayed correctly.
    • Tests
    • Case 1
      • Add the product to the cart , go to the Cart page , and confirm that the product image and part/ref description match the selected product options.
  43. KOD-29347: Implementation - Branding
  44. KOD-29367: Double-Click Button Issue
    • Tests
    • Case 1
      • For this ticket, we will test the Submit button on different forms across the site.
      • The Submit button should display a spinner while the submission is in process.
      • We should also test that double clicking the button doesn’t trigger multiple responses, for this, you can change the Network speed to Fast 4G and try double clicking the Submit button. Only one API call should be made.
      • Also, if the form submission is successful, the Submit button should disappear from the screen.
      • Test the following flows:
      • Clicking on “Forgot Password” which will take you to the account-retrieval page. Test that Submit button.
      • After you click on the email that will take you to the reset-password screen. Test that Submit button.
      • Go to the account-activation screen. Test that Submit button there.
      • After you click on the email that will take you to the account-password screen, test that submit button there.
    • Case 2
      • In this test, we will also test the Submit button. This is a little bit different since we will do it on a CMS page: content/register
      • Make sure the Submit button disappears after submitting the form and it’s successful.
  45. KOD-29372: Page
  46. KOD-29377: Display the confirmation when using keyboard shortcuts to delete rows
    • Regression Tests
    • Case 1
      • Navigate to any data grid where row deletion is enabled (FAQs).
      • Press Ctrl + “-” on the keyboard.
      • Confirm:
      • No rows are deleted.
      • The page view is minimized only.
    • Case 2
      • Navigate to any data grid where row deletion is disabled.
      • Press Ctrl + “-” on the keyboard.
      • Confirm:
      • No rows are deleted.
      • The page view is minimized only.
      • Select any row.
      • Press Ctrl + “-”.
      • Confirm:
      • The selected row is not deleted.
      • Page behavior remains unchanged.
    • Tests
    • Case 1
      • Navigate to a deletable data grid.
      • Select one or more rows.
      • Press Ctrl + “-”
      • Confirm that Popup is displayed.
      • In the confirmation popup, click Cancel.
      • Confirm that:
      • Popup is closed.
      • Selected rows are not deleted.
    • Case 2
      • On the same page select one or more rows.
      • Click Ctrl + “-”.
      • In the popup, click Delete.
      • Confirm that:
      • Selected rows are deleted.
    • Case 3
      • Repeat deletion using shortcut.
      • Confirm that:
      • Popup appears again.
      • In the popup:
      • Select Do not show again.
      • Click Delete.
      • Select another row.
      • Click Ctrl + “-”
      • Confirm that:
      • Popup is not shown.
      • Row is deleted immediately.
  47. KOD-29379: "Log in for Your Custom Price"
    • Regression Tests
    • Case 1
      • Check that the product list looks good for guests and logged in users.
    • Case 2
      • Check that the product details page still looks good for guests and logged in users.
    • Tests
    • Case 1
      • When you a guest and product doesn’t have any price, you can see the label “Login for the Price” on product lists and product details page.
  48. KOD-29382: Chance the Default Fields on the Rules Screen grid
    • Tests
    • Case 1
      • For this test, go to the Rules screen in the operations portal.
      • The default columns should be:
      • Rule ID
      • Name
      • Description
      • Rule Trigger
      • Type
      • Workflow Type
  49. KOD-29390: Hide/Disable Widgets Until Integration Is Ready
    • Regression Tests
    • Case 1
      • For this test, we need to go to a Product details screen that has an AHRI related product.
      • If the AHRI product has more related products, they should appear in the AHRI slider.
    • Tests
    • Case 1
      • For this test, we need to go to a Product details screen that has an AHRI related product, which should also have more related products assigned.
      • We will enable the setting showAHRISlider in the operations portal.
      • We should see the AHRI slider and the AHRI # information on the product details page.
      • Disabling the setting should hide the slider and the AHRI #.
    • Case 2
      • For this test, we need to go to a Product details screen that has an AHRI related product, which should also have more related products assigned.
      • The AHRI slider should only contain the related products of the AHRI product, except for the current product you are on.
    • Case 3
      • For this test, we need to go to a Product details screen that has related products but none are of product type AHRI.
      • The AHRI slider and the AHRI # information should not appear on that product even when the setting is on.
      • The regular Related Products slider should appear.
  50. KOD-29392: Add Host Logic to Widgets
    • Regression Tests
    • Case 1
      • Open the Customizer.
      • Verify that the page displays correctly and all sections are accessible for editing.
    • Tests
    • Case 1
      • Open the Customizer.
      • In the top area of the sidebar, find the Host dropdown.
      • Verify that:
      • “Default” option is displayed first.
      • The dropdown contains all required host options.
      • When another host is selected, the page reloads.
      • The URL contains ?hostCode=SELECTED_CODE.
      • When “Default” is selected, hostCode is removed from the URL.
    • Case 2
      • For the currently selected host, update any data in the following sections:
      • Home slider
      • Home content tiles
      • Top categories
      • Top brands
      • Footer content
      • Verify that the changes are successfully applied for the current host.
      • Select another host.
      • Verify that the same functionality works correctly for this host.
      • Switch back to the previous host.
      • Verify that the previously applied changes are saved.
  51. KOD-29395: Add Question to the Checkout Survey
  52. KOD-29398: Customer cannot pay with PO on Child account
    • Regression Tests
    • Case 1
      • Setup a customer with role companyAdmin or placeOrderWithPurchaseOrder on company, where canUsePOs = true.
      • Go to the customer portal. You should be able to see the PO payment method within checkout.
    • Case 2
      • Setup a customer with role companyAdmin or placeOrderWithPurchaseOrder on company, where canUsePOs = false.
      • Go to the customer portal. You should NOT see the PO payment method within checkout.
    • Tests
    • Case 1
      • Setup a customer with role companyAdmin or placeOrderWithPurchaseOrder on parent company with canUsePOs = false.
      • Create a child company under the mentioned parent company with canUsePOs = true.
      • Go to the customer portal.
      • Switch company to the child company, where canUsePOs = true.
      • Confirm that you see PO payment method on the checkout.
  53. KOD-29400: Configure Customer Portal
  54. KOD-29401: Superseded Product Messaging
  55. KOD-29402: shipTo Default Functionality
  56. KOD-29404: Kodaris - Cross References Fields inconsistent behavior Fix
    • Regression Tests
    • Case 1
      • Navigate to the Cross References page.
      • Confirm that the grid is displayed correctly with all necessary data.
      • Verify that all grid functionalities work properly.
    • Case 2
      • Navigate to Companies > Company Details > Cross References.
      • Confirm that the grid is displayed correctly with all necessary data.
      • Verify that all grid functionalities work properly.
    • Tests
    • Case 1
      • Navigate to the Cross References page.
      • For columns that support sorting/filtering: confirm the sorting arrow and filter icon are visible and functional.
      • For columns that do not support sorting/filtering: confirm the sorting arrow is not displayed and the filter icon is not clickable.
    • Case 2
      • Navigate to Companies > Company Details > Cross References.
      • Repeat the same steps 2 and 3 from the previous test case.
  57. KOD-29410: Add Metric field to the Business Event Types screen
    • Regression Tests
    • Case 1
      • Navigate to the Business Event Types page and confirm that the grid displays correctly and functions as expected.
    • Case 2
      • Navigate to the Business Event Detail page and confirm that all data on the page is displayed correctly.
    • Tests
    • Case 1
      • Navigate to the Business Event Types page.
      • Click Show/Hide New Columns and confirm that a new column Metric appears.
      • Add the Metric column to the grid and confirm that it contains Yes/No values.
    • Case 2
      • Navigate to the Business Event Detail page and confirm that the Metric value is present and matches the value shown in the grid.
  58. KOD-29414: Website Order UOM Issue
  59. KOD-29418: Pricing for configurator products issue
    • Regression Tests
    • Case 1
      • Verify that order creation with the configuratorOption product works correctly.
      • Verify that there are no errors in the console.
    • Tests
    • Case 1
      • Verify that the price appears on the configuration product page when selecting options.
      • Verify that the price matches the configuration product price from the operations portal.
      • Verify that when selecting a configuration variation and adding a product, the product part and its price are correctly displayed in the cart.
      • Verify that creating an order with the configuration product works correctly.
  60. KOD-29424: Delete settings
  61. KOD-29427: Ticket #248 - Dropdown Item Removal
    • Regression Tests
    • Case 1
      • Verify that the footer still looks good and links are working fine.
    • Tests
    • Case 1
      • For the Sign Up for E-News button in the footer check that link is from the ticket description and this link opens in a new tab.
  62. KOD-29429: Customer Confidential Files Flow
    • Tests
    • Case 1
      • Check new swagger endpoints.
      • Before using new endpoints.
      • Turn the new global setting: creditApplicationSavePdfForCustomer
      • Fill the credit form on the page: http://localhost:8080/credit-application (to view the credit form you need to log in as a customer).
      • Click the button “complete“.
      • It will save confidential file on the customer side.
      • Then you can use new swagger endpoints to view uploaded customer confidential file on the customer side and on customer > customer files in the operations portal.
      • New swagger endpoint:
      • api/account/customer/confidential/documents/{customerFileID}/view (customer side)
      • api/system/customer/{customerID}/confidential/customerFile/{customerFileID}/view (system side)
      • before checking the current swagger endpoint on system side need to assign new role: customerConfidentialCustomerFileView to administrator ( employee )
  63. KOD-29433: Email Address Auto-Population at Checkout
  64. KOD-29450: Google Tag Manager not appearing on website
    • Tests
    • Case 1
      • Open the website.
      • Open browser developer tools.
      • Navigate to the Elements (DOM) tab.
      • Verify configuration from the Operations Portal.
      • ( Google Analytics page) has been correctly added and is present in the DOM (Google Tag Manager, Google Tag Manager (noscript)).
  65. KOD-29451: Credit card payment not available when there is a guide in the cart
    • Regression Tests
    • Case 1
      • Test that credit card payment option is still available.
    • Case 2
      • Test that credit card payment option is not available if one of cart items has a total less than or equal to 0 (except guide products).
    • Tests
    • Case 1
      • Test that credit card payment option is available when guide free product added to the card using a coupon code.
  66. KOD-29457: the serverside api forces us to send the requested cod amount on POST: /api/system/order/{orderID}/generateEmail when we are not sending a cod link, we are simply sending an order email
  67. KOD-29463: Temporary verbiage for Hidden Credit Application Page
  68. KOD-29466: UX to View Customer Confidential Files
    • Regression Tests
    • Case 1
      • In the operations portal on the customer > customer files screen, check that you can still view and download files without issues.
    • Case 2
      • In the customer portal > user documents screen, check that you can still view and download files without issues.
    • Tests
    • Case 1
      • In the operations portal > customer > customer files screen, check that you can now view and download confidential customer files.
    • Case 2
      • In the customer portal > user documents screen, check that you can now view and download confidential files.
  69. KOD-29467: Add Chat Widget Code Snippet
  70. KOD-29477: OA - Fix issue with order still being created after failure to process
  71. KOD-29478: Importing postal codes
    • Tests
    • Case 1
      • Ensure that the import on the postal codes screen is functioning correctly and that the fields are matched correctly.
  72. KOD-29483: User Access Issues
    • Regression Tests
    • Case 1
      • Check that you can still view, download, upload, edit, and delete files on the Media screen in the operations portal.
    • Tests
    • Case 1
      • Check that now if you only have admin permissions, you can still view, download, upload, edit and delete files on the Media screen in the operations portal.