December 11, 2025 release notes

Tickets

1. KOD-5465: Updating Triggers
2. KOD-25949: Create and Print Catalog with Pictures
   • Regression Tests
   • Case 1
     • Check button visibility when logged in.
     • Log in to the website.
     • Navigate to the Categories section.
     • Verify that the print button is NOT displayed.
     • Check button visibility when logged out.
     • Log out of the website.
     • Navigate to the Categories section.
     • Verify again that the print button is NOT displayed.
     • Verify direct URL access is restricted.
     • Attempt to open the page /spcu/catalog-print.
     • Confirm that the page does NOT open under any circumstances.
   • Tests
   • Case 1
     • Log in to the website.
     • Navigate to Catalogs.
     • Verify for Customer/Company Catalogs.
     • Test with different product quantities.
     • Verify catalog generation with 1 product.
     • Verify catalog generation with more than 6 products.
     • Validate generated file content.
     • Confirm the file is generated correctly.
     • Ensure the following elements are present:
     • Catalog name
     • Product images
     • Product name (optional for some products)
     • Product ID
     • Product price
     • Page numbering on every page
     • Verify mobile version behavior.
     • Repeat steps on a mobile device or mobile layout.
     • Check button design consistency.
     • Verify that the print button design matches the overall UI.
     • Confirm it aligns visually with similar elements (e.g., list icon).
3. KOD-26332: Payment updates
4. KOD-28282: More payment updates
5. KOD-28335: Fix 'Cono' field accepting negative and exponential numbers
   • Tests
   • Case 1
     • Log in the Operations Portal, and open the Vendor Pricing page.
     • Open the Details page of an item in the grid.
     • Edit the Cono field:
     • It should accept only numbers from 0 to 100.
     • It should accept only numeric digits.
     • It should not accept the minus signal or any letters, like E.
6. KOD-28430: Automated processing of Orders
7. KOD-28688: Library File Management
   • Regression Tests
   • Case 1
     • Sidebar menu.
     • Confirm the sidebar menu looks good and works correctly.
   • Tests
   • Case 1
     • New menu item.
     • Confirm there is a new menu item "Shared drive" with an "Internal Files" item under it.
   • Case 2
     • Open Internal Files page.
     • Confirm there is a grid with internal files list.
     • Open the Show/Hide menu.
     • Confirm there are available columns to show.
     • Show/hide some columns.
     • Confirm it works correctly.
     • Show Entity Type column.
     • Confirm in our list there are only items with the SharedDrive EntityType.
   • Case 3
     • Sort columns where sorting is available.
     • Confirm sort feature works correctly for any columns.
     • Filter columns where filtering is available.
     • Confirm the filter feature works correctly.
     • Find any item using the search field.
     • Confirm the search works correctly and the results match the query parameter with EntityType=SharedDrive.
   • Case 4
     • Change the value of any of the following columns:
     • folder, status, extra1, extra2, extra3, extra4, extra5, parentInternalFileID, isFolder
     • for parentInternalFileID , you can use any existing internal file ID. The value will not change if an invalid ID or any other incorrect value is used.
     • All other columns are not editable.
     • For the next steps, use only the editable cells:
     • Select one or more of them.
     • Go to Edit > Delete the selected values.
     • The selected cells should become empty.
     • Select any row (one or more).
     • Go to Edit > Delete selected rows .
     • The selected internal file(s) should be deleted.
   • Case 5
     • At the top of the page there is an "attach file" icon.
     • Try to attach a new file.
     • Confirm list was updated with the new item.
     • Go to DevTools and set the network speed to 3G.
     • Try to attach a file twice in a row while the previous file is still uploading.
     • Confirm that you cannot attach another file until the previous upload is finished, so in the end, only one new file appears in your grid.
   • Case 6
     • Click the eye icon.
     • Confirm that the file preview works correctly and the file opens.
   • Case 7
     • Click the download icon.
     • Confirm that the file is downloaded successfully.
8. KOD-28694: Parser fix from Ticket 39079
9. KOD-28708: Parser From Ticket 41569
10. KOD-28720: Implementation - Pricing issue
11. KOD-28752: Implementation - PIM Exports
12. KOD-28766: Parser final update from Ticket 27562
13. KOD-28771: Parser from Ticket 41784
14. KOD-28783: Provide Functionality for Direct Orders
15. KOD-28785: "SEO Search" Google Analytics Research
16. KOD-28796: Send certain records from PIM / Cross Reference to data lake
17. KOD-28849: Add Customer Status to Tickets
    • Regression Tests
    • Case 1
      • Make sure that you can create and update a Ticket.
    • Case 2
      • Make sure that existing ticket documents in Solr are still working and that it is still indexing new tickets to Solr.
    • Case 3
      • Make sure that OS documents that have already been indexed are still there and that we can index new Tickets or update tickets in the index and it still works. Here are a couple of queries that you can use to make sure that tickets are still showing up in OS in swagger.
      • (endpoint is POST/api/system/opensearch/ticket/search )
    • Case 4
      • Check setting companyTableRecordAllowedRecordTypeValues.
      • Make sure that it is a list of values separated by commas and that the value ticketCustomerStatus is the last item in the list.
    • Tests
    • Case 1
      • Test new endpoints.
      • Currently these endpoints are only available through swagger. The first endpoint to test is to create a customer status or two using POST/api/account/ticket/customerStatus It prompts you for a code description and companyID. The code and description can be anything but the companyID needs to be a company that the user you are currently signed in with has access to. When you are done with this step you can see the customer statuses you have created using the endpoint
      • GET/api/account/ticket/customerStatus/list
    • Case 2
      • The next endpoints to test all have the form /api/account/ticket/customerStatus/{customerStatusID}
      • There is a GET, PUT, DELETE, and PATCH endpoint. These are all pretty straightforward, you just need to put in new strings for code and description. You can always use the list endpoint from the first test to make sure everything is working properly.
18. KOD-28866: Payment Data
19. KOD-28895: AP - Invoice Parser
20. KOD-28909: AP: Invoices format change- number format change to comma for decimals and space for thousands - Mapping Update
21. KOD-28912: Free shipping discounts
    • Regression Tests
    • Case 1
      • Test getting shipping options in the Cart checkout step and apply those shipping options to your order so the appropriate rate amount is added to the order total.
    • Tests
    • Case 1
      • Pay attention that the new Discount reward type (FreeShipping) requires Applicable Company Values to be populated with company codes, as otherwise it can dismiss any shipping charges in your environment.
      • Test applying FreeShipping discount to order.
22. KOD-28924: Add UX for outside salesreps assignments on shipto creation
    • Regression Tests
    • Case 1
      • Navigate to Quote details page.
      • Add an assignee WITHOUT selecting assignment type (leave dropdown empty).
      • Verify assignee appears in the list.
      • Remove the assignee.
      • Verify assignee is removed.
    • Case 2
      • Navigate to Quote details page.
      • Edit an existing field.
      • Make sure the fields are updated as expected.
    • Tests
    • Case 1
      • Preconditions:
      • Add values to quoteAssignmentTypes setting.
      • Steps:
      • Navigate to Quote details page.
      • In the right sidebar, locate the "Assignees" section.
      • In the "Assignment Type" dropdown, select any value.
      • In the "+ Add assignee" field, start typing the employee name.
      • Select employee.
      • Expected Result:
      • Employee is added to the Assignees list.
      • The Assignment type is displayed below the employee name.
    • Case 2
      • Steps:
      • Navigate to Quote details page.
      • In the right sidebar, locate "Assignees" section.
      • Try to add/remove several employees.
      • Make sure it works well.
      • Make sure that we are using new API endpoints with `employeeAssignment`.
      • Salesreps and quoteAssignees values. employeeAssignment endpoints will be used in the next ticket according to new description.
23. KOD-28948: Kodaris - Internal FAQ
    • Regression Tests
    • Case 1
      • Confirm the sidebar menu looks good, and we are able to open any menu item and see its subitems as well.
    • Tests
    • Case 1
      • Open the Operations menu item.
      • Confirm that there is a new item under it — Internal FAQs.
    • Case 2
      • Go to the Internal FAQs page.
      • Confirm there is a grid with a list of internal FAQs.
      • Click on the Show/Hide menu.
      • Confirm that you can hide or show any of them.
      • Finally, the column list was updated, but the logic remains the same.
      • Open DevTools → Network tab, clear it, refresh the grid, open the request headers.
      • Confirm the list uses the Intranet Page entity.
    • Case 3
      • Sort the columns by clicking the arrow next to the column name.
      • Confirm sorting works correctly.
      • Filter columns using the filter row (where available).
      • Confirm filtering works correctly.
      • Use the search field to test the search feature.
      • Confirm it works correctly.
    • Case 4
      • Choose any editable cell (double-click to verify it switches to input mode) and change its value.
      • Press Enter or click outside the cell.
      • Confirm the value was updated correctly.
    • Case 5
      • Select any editable cell(s) again.
      • Click Edit - Delete selected values.
      • Confirm that the selected data was deleted where allowed.
      • Select any row(s).
      • Click Edit - Delete selected rows.
      • Confirm the selected row(s) were deleted successfully.
      • The same behavior will occur when deleting unselected rows.
    • Case 6
      • Click the Add FAQ button in the top menu.
      • A new page should open.
      • Fill in the fields with any valid information.
      • Go back to the Internal FAQs page.
      • Confirm a new item appeared with the correct data.
    • Case 7
      • Go to the item details page.
      • Confirm the data in the grid matches the data on the current page.
      • Change any values.
      • The values should be saved after pressing Enter or clicking outside the edited field.
      • Go back using the breadcrumbs.
      • Confirm navigation works correctly.
      • Confirm the updated data is also reflected in the grid.
    • Case 8
      • Confirm that you cannot open the Internal FAQ page if you do not have any of the following permissions: 'superuser', 'administrator', 'intranetView', 'intranetEdit'.
24. KOD-28950: Return Contact Details to be sent into CSD
25. KOD-28960: Update OEEL Mappings
26. KOD-28971: Guest Checkout Tax and Credit Card Authorization
27. KOD-28977: AP Update - Invoice Format Changed
28. KOD-28987: Kodaris Dev Examples: Asset entity
29. KOD-28999: Create dropship catalog for public pricing
30. KOD-29001: AP- Updates
31. KOD-29015: Cash / COD version of credit application doesn't submit properly
    • Regression Tests
    • Case 1
      • Create a new credit application.
      • Navigate to the spcu/credit-application-register page.
      • Provide your test email and click the submit button.
      • Confirm you have received email.
      • Click on the button from the email.
      • Confirm navigation to the Set Credit Application Password page.
      • Provide password and log in.
      • Confirm credit application is blank and loads as expected.
    • Case 2
      • Fill in values for Cash/COD application.
      • Confirm required fields needed to submit a credit application.
      • Submit a form.
      • Confirm you were redirected to a “Thank you page”.
    • Case 3
      • Repeat steps from case 1 and 2, but for Credit Account type.
    • Tests
    • Case 1
      • Repeat steps from regression test 1.
      • Select Cash/COD preferred payment method.
      • Select “Credit Account” preferred payment method.
      • Select Cash/COD preferred payment method
      • Repeat steps from regression test case 2.
    • Case 2
      • On the operations portal locate the account from the previous test case.
      • Navigate to its detail page and change “Status” from “Applied for a Credit” to “Applying for a Credit”.
      • From the “Thank You” credit application page, move back to the credit application form.
      • Change Preferred payment method to “Credit Account”.
      • Complete the form filling in all required fields.
      • Confirm the form is properly submitted.
    • Case 3
      • Create a new Account Application (Steps from regression test case 1).
      • Select “Cash/COD” → “Credit Account“ → “Cash/COD” and refresh the page.
      • Confirm all previously required fields are still required.
      • Repeat all this steps for “Credit Account”:
      • Select “Credit Account” → “Cash/COD“ → “Credit Account” and refresh the page.
32. KOD-29031: Issues with returns (check for quantity shipped)
33. KOD-29033: Capture Newsletter Signup Submissions
34. KOD-29053: Form Subject Line Update
    • Regression Tests
    • Case 1
      • Check that both registration forms and the contact form works as expected.
      • The contact form email should have the “ A customer submitted a form on the website ” email subject.
    • Tests
    • Case 1
      • The registration form emails should have the following email subject:
      • A customer submitted a registration form on the website.
35. KOD-29057: Set Up Customer Portal vs Commerce Site
36. KOD-29060: Spin Up System
37. KOD-29065: Implementation - Countries / States
38. KOD-29069: Implementation
39. KOD-29070: Implementation
40. KOD-29078: Implementation - Order Change Interceptor
    • Regression Tests
    • Case 1
      • Confirm that we can save the order in CSD, and in the console we will see that the orderUpdate interceptor is triggered, and we will not see any error snackbar after clicking Save, only if the order passes all validation rules.
    • Tests
    • Case 1
      • Confirm that if our order satisfies all the requirements described below, then:
      • We will not see an error snackbar,
      • The orderUpdate interceptor will be triggered in the console.
      • If the order does not satisfy the conditions, then:
      • We will see an error snackbar,
      • The orderUpdate interceptor will not run.
      • The order is allowed to be saved when all of these are true:
      • extra5 field is a string, and the second part after splitting by "-" is "0" (if yes, then extra5FlagOk would be true)
      • If stagecd exists, then it must be exactly 1, and extra5FlagOk must also be true.
      • If stagecd does not exist, then only extra5FlagOk is required.
      • Every item must have trendCompiledSettings.orderaltno equal to 0 or empty.
      • If any item has a non-zero orderaltno, saving is blocked.
      • The order is blocked and shows a snackbar error when any of the following are true:
      • extra5 second part is not "0",
      • stagecd exists and is not equal to 1,
      • at least one order item has orderaltno not equal to 0.
      • In these cases, a validation error snackbar appears, and the orderUpdate interceptor does not run.
    • Case 2
      • Create a new order and attempt to save it immediately.
      • Saving is blocked because extra5 fields are not populated yet.
      • Confirm that an error snackbar appears, and the orderUpdate interceptor does not run.
      • Release the order to ERP.
      • The developer fields should now include stagecd .
      • Change stagecd to 0 and attempt to save.
      • Expected result: Saving is blocked.
      • An error snackbar appears, mentioning that stage code is 0.
      • The orderUpdate interceptor does not run.
      • Change stagecd back to 1.
      • Go to the items screen and check orderaltno for each item.
      • If orderaltno equals 0, saving is allowed.
      • If orderaltno is changed to 1 (or any non-zero value) and save is clicked,
      • Saving is blocked,
      • An error snackbar appears.
41. KOD-29086: Parser update from Ticket 41703
42. KOD-29087: Parser issue From Ticket 41569
43. KOD-29092: Unable to view some orders in customer portal
44. KOD-29098: Can't translate 'Cookie' popup
    • Regression Tests
    • Case 1
      • Open the website.
      • Switch to the English language (if not the default).
      • Verify that the cookie consent message is displayed in English.
      • Confirm that the message text is correct according to the expected translation.
    • Tests
    • Case 1
      • Open the website.
      • Switch to the French language.
      • Verify that the cookie consent message is displayed in French.
      • Confirm that the message text is correct according to the expected translation.
45. KOD-29104: Add isVoidable and isRefundable fields to regular payments
46. KOD-29105: Delivery Address Endpoint Issue
    • Regression Tests
    • Case 1
      • On the website we need to make sure that on product/ product list pages the prices still load, lead times and stock messages still display. Also we need to check if the users are still able to add items to the cart. This needs to be checked for guests and logged in customers.
    • Case 2
      • We need to make sure that the eco fee display works as it did before the update. For testing - log in as a customer and search for the product that has an eco fee applicable in your user’s selected shipto. The eco fee icon should be displayed on such product. Now change the shipto to one with a different state, the icon should disappear. Eco fees don’t apply to guest users
    • Tests
    • Case 1
      • We should check if the endpoint “ api/user/customer/selectedDeliveryAddress” is not being called repeatedly for each product, it should be one api call per page load to that endpoint.
47. KOD-29106: Add / Update Products, Skus, Pricing To ERP Error
    • Regression Tests
    • Case 1
      • Validate that the setting: enableERPLogicPaymentReceivedOnAccount is turned on (IF it is off, let’s discuss another environment to test).
      • On the customer side we need to make a deposit. After the deposit is successful, the payment should be synced to the ERP asynchronously. So the first step is make sure we have a valid deposit made and then validate from System Events if it was sent or not.
      • A new System Event should be created. It should contain: field endpoint:
      • /web/sxapirestservice/sxapioereceiveonaccount
      • We expect a successful sync without any issue. In the system event you should NOT see the field: responseBody . That is only populated if there is any error at all.
      • This is to sync the payment to the ERP. I am not sure if it is possible to check in InforCSD that the payment was synced successfully.
    • Case 2
      • Sync company to the ERP from the operations portal.
      • In the network console we can see the response (and if there is an error we might see a pop up also).
      • In the system event we should see a payload with the endpoint: sxapiARCustomerMnt where we can get more information.
    • Case 3 Sync Company Address to the ERP
      • Same as the company. There should be a button for saving to ERP.
    • Case 4 - Sync product Price to the ERP
      • Same as the others. There should be a button to sync to the ERP:
      • Validate it works (There should not be any pop up after syncing it and the response in the network console should contain success = true)
    • Tests
    • Case 1
      • With regression test we are already testing the feature in those entities but we can still test:
      • Sku (If there is a button.. I think UX was working on it).
      • Product (Same as the others.. save to ERP button).
48. KOD-29107: Implementation - Kodaris Invoices
49. KOD-29108: Create a video how to use custom blocks for the logged in users
50. KOD-29114: Implementation - Incorrect Price Findings
51. KOD-29120: Requested Pickup/Delivery Date Feature Update
52. KOD-29139: Customer App on android
53. KOD-29140: QA - Customer App on android
54. KOD-29147: Add expireOldQuotes job to scheduler
55. KOD-29149: iOS App Has Different Input for Pickup & Delivery Fields
56. KOD-29152: Check and fix metrics related to group roles
57. KOD-29155: Customer FAQ - Adding header to search endpoint and making searchable
    • Regression Tests
    • Case 1
      • Try to create and update categories in the operations portal and check that list (Data tab) and search (Search tab) endpoints working correctly (categories listed as expected).
    • Case 2
      • Try to create and update CMS pages in the operations portal and check that list( Data tab) and search (Search tab) endpoints working correctly (pages listed as expected).
    • Tests
    • Case 1
      • We probably need to trigger a full reindex of Categories (Content pages) so header/footer fields are indexed (added) to Solr (Search tab).
    • Case 2
      • Open one of your CMS pages, update the footer or header with a very specific phrase like 'customSpecificPhraseElephant123' and save changes.
      • Go back to the search tab and type your phrase in the Search prompt - your content page should be found by the phrase which you added to the footer tab. Also, check that /api/system/contentPage/search endpoint in Network tab returned header/footer fields with values.
58. KOD-29156: Implement account endpoint on the server side
59. KOD-29159: Set up commerce application
60. KOD-29160: Follow-up ticket to move the FreeShipping logic to DiscountService
61. KOD-29163: Integration - Improvements
62. KOD-29170: Show Store Credit is Available & Check Balance
    • Tests
    • Case 1
      • Test new endpoint for listing company FiAccounts through swagger:
      • POST /api/system/company/byCode/{companyCode}/fiAccount/list
63. KOD-29175: API user cannot add product to cart
64. KOD-29176: Collecting customer feedback
    • Regression Tests
    • Case 1
      • Check that you can still checkout without issues and the cart runs smoothly without issues.
    • Case 2
      • Try submitting any form on the website.
      • Make sure that the employee email is sent and a ticket is created for each submission.
    • Tests
    • Case 1
      • After submitting an order, check that you get a survey popup with the following three questions:
      • Was there anything you were looking for today that you couldn’t find on our website?
      • Did anything on the site not work as expected or feel frustrating to use?
      • Did anything on the site not work as expected or feel frustrating to use?
    • Case 2
      • You should be able to close the survey without submitting it.
    • Case 3
      • Check that you have to enter all the info before being able to submit the form.
      • After submitting, make sure that an employee email is sent and that a ticket for the survey is created with the order number.
      • A setting should also be added on the order with the survey data.
    • Case 4
      • If you place another order after submitting the survey, you should not see it appear again after placing it.
65. KOD-29181: Model lookup - Model correction
66. KOD-29191: Add Batch Number to Accounts Receivable screen
    • Regression Tests
    • Case 1
      • Verify that the Accounts Receivable screen still looks good.
    • Tests
    • Case 1
      • Verify that you can see the new field Batch Number on Accounts Receivable.
67. KOD-29200: Customer Portal Questions
    • Regression Tests
    • Case 1
      • Check that the website still loads without issues and looks good, both on mobile and desktop.
    • Tests
    • Case 1
      • Check that a new item has been added in the top right header: Customer Portal. It should also link to the customer portal home page.
68. KOD-29204: Terminal Updates
69. KOD-29208: Add Postal Code Endpoint to Serverside API
70. KOD-29215: Configure Ticket create from Credit Application and COD application submission
    • Regression Tests
    • Case 1
      • Check that there are no errors in the JS logs for the five minute intervals.
      • E.g. watch the JS logs when the current time hits a five minute interval > 1:05, 1:10, etc.
    • Case 2
      • Check that after a five minute interval, there aren’t a bunch of tickets created for normal companies with title Account Application.
    • Tests
    • Case 1
      • Go through the credit application flow on the website.
      • After you submit the account application (might take a few minutes), a ticket should be submitted with a few of the details.
      • Also check that the user10 field on the company has been filled in.
71. KOD-29222: Creating an endpoint to retrieve the list