All Releases
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

July 17, 2025 release notes

Tickets

  1. KOD-20646: Create Expense UX in Operations Portal
    • Tests
    • Case 1
      • Make sure a new Expenses Screen was added.
      • Its link should be located within the System.
      • Make sure you are able to check this screen and expense details screen with following permissions only: administrator, superuser, expenseView, expenseEdit.
    • Case 2
      • Make sure the Expenses Screen has a grid.
      • Make sure using this grid you are able to:
      • Read existing Expenses records.
      • Create a new Expense record.
      • Update existing Expense record.
      • Delete existing expense record.
      • Go to the expense details from the grid.
      • Make sure you are able to add/remove columns from the grid.
    • Case 3
      • Make sure the expense details tab can be opened from the grid.
      • Make sure the Expense details tab contains multiple fields, which are editable with no issues.
  2. KOD-23840: Customer Portal Testing
  3. KOD-24198: Parser only uploading/importing 19 items
  4. KOD-24475: Add email option to standard credit card form
  5. KOD-26133: Missing Zero
  6. KOD-26315: Incorporate quantity requirements into the inventory flow for Build-on-Demand
    • Regression Tests
    • Case 1
      • Setting displayInventoryOnKits enabled.
      • Having a product with setting kittype = ‘B' which has related products associated with the same SKUs that the product has.
      • The related products should have the related type 'KIT’.
      • Those related products are being considered for calculate inventory from the correspondent SKUs.
      • The products for the ‘component’ items should have statusType different than 'L'. It could be null or any value.
      • The lowest value of the inventory will be displayed.
      • Go to the ecommerce site and see the inventory for each warehouse for the parent product.
      • For regression you need to make sure that if the statusType is not L for the component item then it is taken into account for the inventory calculation.
    • Tests
    • Case 1
      • Setting displayInventoryOnKits enabled.
      • Having a product with setting kittype = ‘B' which has related products associated with the same SKUs that the product has.
      • The related products should have the related type 'KIT’.
      • Those related products are being considered for calculate inventory from the correspondent SKUs.
      • At least one of the products for the ‘component’ items should have statusType 'L'. That means it will be skipped for the inventory calculation so the inventory levels for the corresponding SKUs will be ignored.
      • The lowest value of the inventory will be displayed.
      • Go to the ecommerce site and see the inventory for each warehouse for the parent product.
  7. KOD-26351: Promotional Pricing
  8. KOD-26421: Retail Price Import
  9. KOD-26424: Canned Responses & Templates for Ticketing System Created From Ticket 22165
    • Tests
    • Case 1
      • On the comment box notice the button with the 3 vertical dots → click that and you will see a list of responses.
      • Click add a snippet and add in name and content.
      • Click save and new text should be added to the comment box with that canned response.
      • Check from another account if that snippet is available.
    • Case 2
      • Now edit newly created snippet. Check from another account if that snippet was updated.
  10. KOD-26425: Top Categories are not listed
  11. KOD-26448: Master order/budgets - Update to search case insensitive shipto codes
  12. KOD-26458: Automated Monthly Statement
  13. KOD-26477: Address pulling into Website
  14. KOD-26487: Avalara / Taxing Issue
  15. KOD-26497: Populate "Customer" Fields for Guest Pricing
  16. KOD-26505: Ticket #208 - Center the logo and the social icons
  17. KOD-26517: Ticket notification template
  18. KOD-26526: Tag to line items - UX
    • Regression Tests
    • Case 1
      • Check that the cart still works as expected.
    • Case 2
      • Check that you can still place orders without issues.
    • Tests
    • Case 1
      • Try filling out the additional info from the last step of checkout and place an order.
      • Navigate to the order items in the operations portal and make sure the info was saved correctly.
  19. KOD-26527: Pass Ordered By Field & Display on Templates
    • Regression Tests
    • Case 1
      • Check that the Email PDF after placing the order looks correct.
      • Check that the Thank you page after placing the order looks correct.
      • Check that there are no errors in the console.
    • Tests
    • Case 1
      • Verify that the Ordered By field in the Email PDF after placing an order displays the first name, first letter of the last name of the person that is logged in. (If the user's order does not contain the First and Last Name, the user's email will be displayed in the Ordered By field).
      • Verify that the data in the Ordered by field is displayed in uppercase.
  20. KOD-26543: Master order/budgets - Add qty to customer portal view
    • Regression Tests
    • Case 1
      • Please check that the budget page works correctly, there are no errors in the console.
    • Tests
    • Case 1
      • Go to customer portal → Locations → Location item → Budget tab.
      • Make sure that the Product Quantity column is available in the table.
      • Make sure that data in Product Quantity displays correctly.
  21. KOD-26549: Order Automation - Purchase Order parser
  22. KOD-26551: Import Internal Pages
  23. KOD-26580: Send User Email to Agility
  24. KOD-26584: Surface showPublic flag on products to product search or data grid
    • Regression Tests
    • Case 1
      • Please confirm that the Product page loads without any issues and that we can see our list of products there.
    • Tests
    • Case 1
      • Сonfirm that we can add the showPublic field to the Search tab - It can be used for sorting and filtering but it will not be visible on the Data tab.
  25. KOD-26598: Warehouse logic for province separation
    • Regression Tests
    • Case 1
      • Make sure the product detail page still loads properly for a logged in and logged out user.
    • Case 2
      • For non west regions, make sure on the product details page on an item that is in stock, it still shows all the branches in the list for that region.
    • Case 3
      • On the product list page, make sure the items only have your branch, region and network listed (if in stock).
  26. KOD-26616: Spin Up System
  27. KOD-26635: Create server side export for related products screen
  28. KOD-26642: Issue with order acknowledgment delivery date
  29. KOD-26643: Type 5 pricing records Created From Ticket 28212
  30. KOD-26649: Line Items Fields in Ops Portal
  31. KOD-26651: Add Your Description field to PDP
  32. KOD-26657: Configure store email for the three host sites
  33. KOD-26660: Tariff Charges Created From Ticket 28372
  34. KOD-26662: AP (Ignore) Created From Ticket 28379
  35. KOD-26667: Home page image resize Created From Ticket 28393
    • Regression Tests
    • Case 1
      • Check that the layout of the main page looks correct (both on desktop and mobile devices).
      • Check that there are no errors in the console.
    • Tests
    • Case 1
      • Check that the image on the main page under the header adapts correctly to the screen size (changes size).
  36. KOD-26672: Update pdsc mappings
  37. KOD-26673: Ticketing system - Enable to use latest email response as a customer's ticket comment
  38. KOD-26678: Ticket #209 - Created From Ticket 27932
  39. KOD-26680: Update Quote Templates and PDF
  40. KOD-26689: Shop by Store Sort Order
  41. KOD-26693: LTL shipping method name tweak on order confirmation email
    • Regression Tests
    • Case 1
      • Please test that shipping methods still are displayed properly on order templates.
    • Tests
    • Case 1
      • Please check that we have shipping method name on order confirmation email from order custom fields instead of shipping option code if the shipping option is not configured in the shipping methods table.
  42. KOD-26695: Generic Company Table UX
    • Regression Tests
    • Case 1
      • On the operations portal navigate between different pages.
      • Confirm pages are loaded as expected.
    • Case 2
      • On the operations portal navigate to the companies screen.
      • Confirm the screen is loaded properly.
      • Navigate between companies tabs.
      • Confirm each tab is loaded as expected.
    • Tests
    • Case 1
      • On the operations portal as an employee without any of these roles:
      • administrator
      • superuser
      • companyTableRecordView
      • companyTableRecordEdit
      • Enter “Company Tables“ or “Company > {Specific Company}“ > “Tables”
      • Confirm you can not enter the page.
      • Assign companyTableRecordView role.
      • Confirm page could be visited without issues.
      • Try to modify any values and confirm that there is an error.
      • Assign only the companyTableRecordEdit role.
      • Confirm accessing and editing of the records is available.
      • Repeat these steps for detail pages.
    • Case 2
      • On the operations portal navigate to the “Company Tables” screen.
      • Confirm the screen is loaded properly.
      • Confirm the grid is shown as expected.
      • Apply filters and sorts for each column that supports it.
      • Confirm filtering, searching and sorting is applied.
      • Apply global table search.
      • Confirm records were properly displayed on the search query.
    • Case 3
      • On the operations portal navigate to the “Company Tables” screen.
      • Add a new record.
      • Confirm “Code” column is autogenerated if blank.
      • Confirm “Type” field is required.
      • Confirm values from the dropdown are obtained from the setting companyTableRecordAllowedRecordTypeValues.
      • Confirm a new record can be added and saved.
    • Case 4
      • On the operations portal navigate to the “Company Table.
      • Modify some records.
      • Confirm that the code field is required and can not be blanked.
      • Confirm “Type” field could be selected from the options declared from the companyTableRecordAllowedRecordTypeValues setting.
      • Confirm updates work as expected.
      • Update multiple rows at the same time.
      • Confirm multiple records are updated.
    • Case 5
      • On the operations portal navigate to the “Company Tables” screen.
      • Select any row and delete it
      • Confirm the row was deleted.
      • Select multiple rows and delete them in bulk.
      • Confirm deletion is working in bulk.
    • Case 6
      • On the operations portal navigate to the companies screen.
      • Navigate to the “Tables” tab.
      • Confirm on this screen there only those tables that have companyID from the company you have selected.
      • Confirm Addition of the record sets the companyID to the company you have selected.
    • Case 7
      • On the operations portal go to “Company Tables” or “Tables tab” under the company.
      • Navigate to the detail page of the Company Table record.
      • Confirm you can modify some fields.
      • Confirm “code” field is required.
      • Confirm changes are saved after the modification.
      • Confirm “Record Type” field gets values from the setting companyTableRecordAllowedRecordTypeValues.
    • Case 8
      • Navigate to the Company Table screen on the operations portal.
      • Navigate to the detail page.
      • Confirm by clicking on “Company Tables“ you are redirected to the previous page.
      • Navigate to the Companies screen.
      • Select any company.
      • Navigate to the Tables tab and select any record (add if needed).
      • Navigate to its detail page.
      • Confirm:
      • Companies → redirects to Companies screen.
      • Company Code → redirects to Company detail page.
      • Tables → Redirects to the Tables tab of the company.
      • Confirm the final item is Company Table code.
  43. KOD-26696: Add Settings to Company Generic Table
  44. KOD-26697:Add Message at Checkout for Shipping Methods / Shipvias Created From Ticket 14906
  45. KOD-26705: Fix catalog view flipping back to grid view on page switch
    • Regression Tests
    • Case 1
      • On catalog, category and search pages (if there are any products returned) products should be loaded with no issues.
    • Case 2
      • On catalog, category and search pages:
      • If you are switching between grid and list views: make sure your selected view on the last page that you have loaded becomes your “base view“: when you load any other category, catalog or search page - by default they are loaded with the view that was previously selected. (this is only for grid and list views).
    • Case 3
      • Make sure functionality for switching between different views (grid and list on category and search pages and grid, list and catalog views on catalog pages) works with no issues.
      • When you click on any view icon, the correspondent view is loaded for the product selection on the page.
    • Case 4
      • On Catalog pages try resizing the page and check smaller screen width.
      • While resizing from the catalog view, the table should look good. Name should be clickable. You should be able to add product from a table to a cart while resizing. All product info per table row should be available.
      • While resizing from the list view, product list items should look good. The name should be clickable. You should be able to add products to a cart while resizing. All product info per list item should be available.
      • Make sure catalog and list views are available to you on 1201px width and more.
      • Make sure you are switching to the grid view once you have reached 1200px width.
    • Tests
    • Case 1
      • On any catalog page of the catalog which has several products, click on the catalog view icon.
      • Make sure you have switched to the catalog view and the grid view hasn’t loaded before the catalog view loaded.
      • Catalog view should be loaded without flipping.
    • Case 2
      • On catalog, category and search pages: click on any view icon button. Make sure on button click into the URL params view was added. And the view should be equal to the type of view with you have clicked: (grid/list/catalog).
      • Catalog view should be available on catalog pages only.
      • Make sure the page with the correct view was loaded on button click.
      • Remove view URL parameter. Load the same page but without view the URL parameter.
      • Make sure you stay on the page with the same view as before the removal of the view URL parameter.
    • Case 3
      • With the setup from previous case, select grid or list view on any catalog, category or search page.
      • Open any other catalog, category and search page.
      • Make sure on different pages the correct view which you have selected on the 1st step of this case was loaded by default.
    • Case 4
      • On the catalog page select catalog view.
      • Make sure in the URL parameter was added view=catalog.
      • Refresh the same catalog page. Make sure you stay on the catalog page with the catalog view.
      • Remove this URL parameter, reload the page. Make sure even without the URL parameter, you stay on the catalog page with the catalog view.
      • Open other catalog pages. Make sure by default when you open those catalog pages, they are loaded with the catalog view.
      • Open category page of search page.
      • Make sure your default view for those pages now becomes grid view and those category and search pages are loaded with no issues (products are loaded in grid view with no issues).
  46. KOD-26707: AP Automation - miscellaneous charges Created From Ticket 28264
  47. KOD-26710: Statuses Dropdown for page drafts
    • Regression Tests
    • Case 1
      • Confirm that the pages and page-drafts and page-drafts detail pages load without errors and the content is visible.
    • Сase2
      • Confirm that when changing the contentPageStatuses settings, the list of items in the status dropdown updates accordingly.
    • Tests
    • Case 1
      • Confirm that when selecting and editing the status field, a dropdown appears containing the options from contentPageStatuses settings. Confirm that these options match and that you can select one of them, and it gets saved.
    • Case 2
      • Confirm that when opening the page-draft detail page, there is a status select field that retains the same value as shown in the main page-drafts list. Confirm that you can change this select, and the change will be reflected in the main list accordingly.
  48. KOD-26712: Invoice Emails Missing Some Invoices
  49. KOD-26713: Update Hero Image on CSD Payments Page
  50. KOD-26719: Update Shipto Matching Logic
  51. KOD-26726: Create server side APIs for CompanyPage
  52. KOD-26727: Need to set the Print All & Invoice flags
  53. KOD-26728: Commerce Testing
  54. KOD-26730: Change links on career page - Created From Ticket 28650
  55. KOD-26735: Update hero section of homepage
  56. KOD-26736: Update Quote Templates to Reflect 3 Decimal Places
  57. KOD-26737: Kodaris.com – Payments Page Update
  58. KOD-26739: Update Default Product Image
    • Regression Tests
    • Case 1
      • On the commerce site navigate to the product search page.
      • Confirm page is loaded properly.
    • Case 2
      • Select any product on the commerce site.
      • Navigate to the detail page of this product.
      • Confirm page is loaded properly.
    • Case 3
      • On the commerce site add some products to cart.
      • Navigate to the cart.
      • Confirm checkout pages works as expected.
    • Case 4
      • Open 5 products.
      • Confirm Related product slider displayed as expected.
      • Confirm images for products which do not have one are rendered properly.
    • Case 5
      • On the operations portal navigate to the CMS section.
      • Click on Menus.
      • Confirm page is loaded properly.
      • Confirm featured product sliders could be added.
      • Configure slider with products.
      • Confirm slider works as expected on the page.
  59. KOD-26744: Avoid reply loop
  60. KOD-26756: Top Brands & Category Adjustments
    • Regression Tests
    • Case 1
      • On the commerce site navigate to the bottom of the Home Page.
      • Confirm sliders displayed as expected.
    • Case 2
      • On the operations portal navigate to the Menus under CMS.
      • Confirm sliders displayed as expected.
    • Tests
    • Case 1
      • Confirm style for Top Categories slider is the same for the Top Brand one.
  61. KOD-26758: Update to not Sync Invoice & Statement Type Fields Created From Ticket 26888
  62. KOD-26760: Ticketing Template
  63. KOD-26762: Disclaimer Update
  64. KOD-26763: Mapping Specific Date Field on Invoice
  65. KOD-26765: Page Editor View vs Actual Site Look Created From Ticket 28847
  66. KOD-26768: Unable to refund order
  67. KOD-26777: Add Punchout as integration to all sites
    • Regression Tests
    • Case 1
      • Verify if the integration PUNCHOUT already existed in any site, that it continues working as expected and it doesn’t change the ‘status’.
      • For example, you can try to activate it or inactivate it and it should work correctly.
    • Tests
    • Case 1
      • Verify on any site that the integration PUNCHOUT exists.
  68. KOD-26782: Item code issue Created From Ticket 28196
  69. KOD-26789: Parser not picking up lines
  70. KOD-26792: New Product Tag
    • Tests
    • Case 1
      • Please test that we have a new product tag and it has all the same functionality as others. Such as:
      • Is clickable from all pages and redirects to a new page with 3 Points products.
      • Is displayed correctly on pages:
      • Product list
      • Product grid
      • Product details
      • Recently viewed products slider
      • Cart page
      • Related products slider
      • Is not shown in the categories list (dropdown on the header).
      • We have and can check the checkbox under the featured filter category.
  71. KOD-26797: Content5 - Add host and create URL
  72. KOD-26810: Add Flag and Customer Flag columns to tickets screens
    • Regression Tests
    • Case 1
      • Please test that we still can open and see data on all screens below:
      • Activities
      • Activity templates
      • Company → activities
      • Company address → tickets
      • Company → tickets
      • Order → tickets
      • Quote → tickets
      • Ticket detail
      • Ticket search / grid tables
      • Ticket → linked tickets
      • Ticket templates search / grid tables
    • Tests
    • Case 1
      • Please test that on all screens listed above we have flag and customer flag as an available columns, they are editable from grid table, facetable.
    • Case 2
      • On the ticket details page please test that we have 2 new fields with flag and customer flag under status / work status fields and they are editable.
  73. KOD-26813: Kodaris.com – Fraud Detection & Payments page updates
  74. KOD-26819: Look at MID by Host
  75. KOD-26821: Update template for old internal pages
  76. KOD-26823: Investigations on pricing record
  77. KOD-26826: Cross References: add companyCode filter when looking for a cross reference
    • Regression Tests
    • Case 1
      • For all regression and feature cases check Order items and Quote items.
      • If the item is NONSTOCK and has customerProductCode or generatedCrossReference on the note - you should be able to create a new cross reference and specify it’s unit conversion.
    • Case 2
      • If the item is not NONSTOCK but has associated cross reference and has customerProductCode or generatedCrossReference on the note - you should be able to edit Unit conversion on this cross reference.
    • Tests
    • Case 1
      • If the item is NONSTOCK and has customerUnit not empty or null and customerProductCode - while creating cross reference it should be used for creating a new cross reference as altProductCode.
      • If item is NONSTOCK and doesn’t have customerUnit not empty or a customerProductCode and has generatedCrossReference on the note - this generatedCrossReference should be used as altProductCode for creation of the new cross reference.
      • If the above closes are not true and the item has only customerProductCode not empty - it should be used to create Cross Reference as altProductCode.
    • Case 2
      • Manage Cross Reference case.
      • When item is not non NONSTOCK:
      • To search for existent cross reference we should be checking at first customerProductCode (if customerUnit exists) if above clause was false and there is generatedCrossReference - we should use generatedCrossReference to search for existing cross reference, if 2 above clauses are false and customerProductCode exists, we should use it to search for existent cross reference.
      • If on any of those checks we have found an existent Cross reference - it should be displayed in the Update Cross Reference dialog as Alternative Product code. In case we haven’t found any cross references - we display message:
      • This Item doesn't have an associated Cross Reference.
    • Case 3
      • To search for existing cross reference when clicking Manage Cross Reference button this request is already called:
      • api/system/productCrossReference/list
      • make sure in the filter fields there was added 3rd filter:
      • name: "companyCode", operation: "IS", value: "your current company code value"
  78. KOD-26827: Unit Conversion Created From Ticket 28832