May 22, 2025 release notes

Tickets

1. KOD-24060: Automate Orders
2. KOD-24486: Dynamic Data-Driven Meta Descriptions
3. KOD-24851: Set up Order Templates
   • Regression Tests
   • Case 1
     • Check that the order details in customer portal, order email and order pdf templates still work as expected.
   • Tests
   • Case 1
     • Go through the three templates above.
     • Make sure they match the invoice pdfs provided in the template description.
     • Both Invoice (status=invoiced or paid) and Acknowledgement versions.
   • Case 2
     • On the order details one, also check mobile responsiveness.
4. KOD-24894: Create App Listing
5. KOD-25139: Allow customers to select Need Lift Gate for LTL shipments and then send in FedEx API request and to CSD
6. KOD-25203: Configure & Display Badges for Order Automation Discrepancies
   • Regression Tests
   • Case 1
     • For this regression test, we will go to Orders screen (/orders/search) - Search tab.
     • Make sure the page loads without any errors.
     • Make sure that the right arrow takes you to the details screen of the selected order.
     • Make sure there are no visual errors on the badge or tooltip when you resize the screen or add and remove columns.
   • Case 2
     • For this regression test, we will go to the orders screen of an order that has no discrepancies.
     • We should test both the Details and the Items tab.
     • Make sure no errors pop up when you enter any of these pages.
     • We will update the fields and Purchase Order on the Details tab, and the item code on the Items tab.
     • Make sure everything works as expected.
   • Tests
     • Go to Orders screen on the search tab. If an order has discrepancyWarningCount or discrepancyExceptionCount values greater than 0, you will see a badge on the row. If any of the discrepancies is of exception type, the badge should be red. Otherwise it should be orange. When you hover the badge, a tooltip with the number of warnings and exceptions should be displayed.
     • Go to an order Details screen. If that order has discrepancyWarningCount or discrepancyExceptionCount values greater than 0, the discrepancies endpoint should be called, if not, it shouldn’t be called. You can check that by opening the Network tab. On the details screen, you should see discrepancy badges on the following places: Fields: Purchase Order # The badges should be displayed if a discrepancy pointing to those fields exist for that order. If the discrepancy is an exception, the badge should be red, otherwise it should be orange. A tooltip with the discrepancy message is also able to be seen if you hover the badge.
     • Move from the Details to the Items tab on the order screen. If there are discrepancies you will see the their count on a badge on the Items tab. If any order items discrepancies is of exception type, the badge should be red, otherwise it should be orange. The total number of item discrepancies should also be recalculated if you make changes on the number of items or the items fields. Similarly to previous test cases, a red or orange badge should be displayed inside the cell that contains the discrepancy. These cells could be: Code or unit price. Updating said cells could remove or create new discrepancies, so make sure you also test that. (discrepancy updates may take a while to process, it is not instantaneous) You should also update the other cells not related to discrepancies to make sure it all works as expected
     • Go to the Order Automation screen. There are two sections, order with the Order Details main page discrepancy configurations (for purchase order number) and Order Items with its respective discrepancy configurations (product code and unit price). The values displayed there should match the ones from the GET /api/system/setting/orderAutomation/discrepancyConfiguration endpoint. Changing one of the values and clicking on save, should call the PUT endpoint of the same name and update the values. Make sure that is the case after you click on Save, reload the page and make sure the new values are displayed. Since this is a PUT endpoint, we are sending the entire object every time we are making a change.
7. KOD-25219: Filter logins
   • Regression Tests
   • Case 1
     • Make sure you can still login as a customer with new setting companyHostRestricted disabled
     • OR if you are not even in a mulithost site.
   • Tests
   • Case 1
     • When logging in as a Customer, if the setting companyHostRestricted is enabled, you are under a particular host and the customer company doesn’t have the same hostCode than the user’s Host,
     • Login should fail.
     • If the company has the same hostCode than the User’s Host, you should be able to log in.
     • For testing you can try to log in with different users that are under the same Host but in different companies and have those companies with different hostCode (One that matches, and one doesn’t)
     • Make sure you still can log in if:
     • Setting companyHostRestricted is enabled but the site is not multi host (setting multiTenantMode is disabled)
     • Setting companyHostRestricted is enabled but the current user doesn’t have a Host assigned.
8. KOD-25239: Rollout Script Revisions
   • Regression Tests
   • Case 1
     • Check revision settings whether are turn on:
       • saveUserScriptRevisionToDataLake
       • saveAPIScriptRevisionToDataLake
       • saveInterceptorRevisionToDataLake
       • saveScriptRevisionToDataLake
9. KOD-25329: Tariff calculation update
10. KOD-25340: Log the full request and response in system events
11. KOD-25348: Scanning Barcodes in the Mobile App
12. KOD-25381: Release Updated Customer App
13. KOD-25433: Include Tracking on Invoices
14. KOD-25497: DDA App - Add tote return feature
    • Tests
    • Case 1
      • Test select feature screen:
      • Test if Trips screen is opened correctly.
      • Test if return totes is opened correctly.
15. KOD-25543: UPC Item and Line Type on the Order templates
16. KOD-25629: Automated Monthly Statements Created From Ticket 15420
17. KOD-25636: Customer Parser Setup Created From Ticket 22129
18. KOD-25641: Delayed order acknowledgement email template
19. KOD-25655: Set Up Test Site w/ Standard DDA Notifications
20. KOD-25663: Add "Shipping date" field in ordering process Created From Ticket 22058
    • Tests
    • Case 1
      • Open the website.
      • Add a few items to the cart.
      • Proceed to checkout.
      • Select any new shipping date.
      • Copy the order ID.
      • Open the operations portal and navigate to the Orders page.
      • Find the corresponding order using the order ID.
      • In the Delivery Methods section, check the delivery date.
      • Verify that the delivery date matches the one selected on the website.
      • Complete the order.
      • Check the delivery date once again using the order ID, it should still match the selected date.
21. KOD-25666: Change portal
22. KOD-25671: Add a setting to send additional tendering information to CSD for payments
    • Regression Tests
    • Case 1
      • When setting inforCSDSendAdditionalTenderingInformationToErp is disabled, we should not send in tender_payment.fieldvalue node the value acct and expdate.
      • After syncing a payment to CSD you should be able to see in the request the Tender_Payment node with the information populated in the ‘fieldvalue’
      • You should be able to see the request in the event CSDOrder_SendOrderChangeRecord.
    • Tests
    • Case 1
      • When setting inforCSDSendAdditionalTenderingInformationToErp is enabled, when sending payment to ERP for InforCSD we willl see in the Tender_Payment.fieldvalue the new fields acct and expdate (See event CSDOrder_SendOrderChangeRecord node Tender_Payment to confirm).
      • For doing that, the Payment record should contain the field creditCardDate and creditCartNumberDisplay populated.
      • For testing we need to create a Payment with any of these providers: Converge/PriorityPayment/ACH and one with cenpos since there are 2 different flows for setting the Tender information.
23. KOD-25713: Test addons for rollout
24. KOD-25718: Ticket #189 - Created From Ticket 23385
25. KOD-25723: Ticket #167 - Created From Ticket 23375
26. KOD-25725: Ticket #143 - Brands page update
27. KOD-25727: Ticket #145 - Career page update
28. KOD-25726: Ticket #144 - Locations page update
29. KOD-25734: Ticket #160 - Policy pages update
30. KOD-25740: Ticket #172
31. KOD-25768: ERP Sync
32. KOD-25773: Ticket #173 - Created From Ticket 23343
33. KOD-25799: Implementation - Countries / States
34. KOD-25797: Implementation - Branding
35. KOD-25801: Implementation - Configure Customer Portal
36. KOD-25802: Implementation - Porting content over
37. KOD-25812: Ticket #175 - Google Tag
38. KOD-25814: Issue with duplicate items being added to the cart
39. KOD-25815: Configure copying products from category to filter category on live
40. KOD-25821: Pass customerCode and email from app server to payments server
41. KOD-25830: Fix Error on Vendor Invoice Screen
42. KOD-25846: Badges for Order Automation Discrepancies - Order Item fix
43. KOD-25848: Update email subject line for web forms
44. KOD-25849: Ticket #192 - Created From Ticket 23957
45. KOD-25851: Implementation - Sync addons
46. KOD-25852: Implementation - Sync addons
47. KOD-25854: Freight Intensive
48. KOD-25856: Ticket #194
49. KOD-25857: Update to automatically sending employee notifications for automated orders sitting in Kodaris
50. KOD-25862: Error page issue
51. KOD-25866: Spin up the system
52. KOD-25868: Install the applications
53. KOD-25871: Notification setting for new account creation
54. KOD-25884: Support more decimal places in the system side prices by codes endpoint
    • Regression Tests
    • Case 1
      • Check endpoint GET: api/system/product/pricesByCodes whether field: wholeUnitPrice, calculatedPrice, unitPrice and altPrice return numbers with 5 decimal places back.
55. KOD-25887: Add require shipto check to system side
    • Tests
    • Case 1
      • Test new endpoint added to system side:
      • GET: /api/system/order/{orderID}/shippingAddressRequired
      • Pass orderID to determine if shipping address is required for order’s company.
56. KOD-25894: Surface on UX setting that is defaulted to off
57. KOD-25903: update message