View all releases

October 9, 2025 release notes

Tickets

KOD-24505: Flag a category as a favorite
KOD-25632: Get Configuration & Sample Code for Save to ERP in Cash Quotes Created From Ticket 20049
KOD-25919: Implement AI for Order Automation, Quote Automation, AP Automation, PO Acknowledgment Automation
KOD-26370: Sub-Parent Pricing Hierarchy Not Pulling Correctly
KOD-26372: Would like to be able to update the selling price or adjust markup on a quote to increase sales volume
KOD-26420: Add ability to choose a shipping options when calculate totals
- Regression Tests
- Case 1
  - Navigate to the operations portal, go to Orders/Items screen. Check if everything is displayed as expected.
- Tests
- Case 1
  - Navigate to the operations portal, go to any Order’s Item screen. Here check if there is “Choose Shipping Option”.
  - Check if the shipping fee is changing when you choose another shipping option. Also check if Total got recalculated.
- Case 2
  - Check the Network tab in DevTools if these two endpoints were called.
  - /api/system/order/{orderID}/applyShippingOption
KOD-26794: Refund Issue
KOD-27198: Kit builder - Calculate/Display shipping cost
KOD-27199: Kit builder - Add “PRINT TO PDF” button
KOD-27524: Platform - Create cross references when changing product code and populate supplierCode
KOD-27581: Additional custom blocks
KOD-27590: Add Tickets
KOD-27631: Test on a wired connection
KOD-27650: Add Time to Date picker
- Regression Tests
- Case 1
  - Open the operations portal. Go to any screen with a Data grid and have a date-time filter enabled. Check if the filter works fine.
- Case 2
  - Go to CMS/Pages. Check if the data screen looks as expected.
- Case 3
  - Go to any Page detail screen. Check if it is displayed as expected.
- Tests
- Case 1
  - Go to the data tab for records on CMS/Pages. Find columns for start date and end date. Check if you can enter date and time for them as shown on video.
  - Check if the date was saved.
- Case 2
  - Go to the details screen for any Page. Find fields for start date and end date on the right. Check if you can enter date and time for them as shown on video.
  - Check if the date was saved.
- Case 3
  - Open page editor. Here on the right menu bar you need to find a section for Schedule. Here try to update and set date and time for startDate and endDate.
  - Expected to update data for the page.
KOD-27657: Vendor Import Created From Ticket 34351
KOD-27677: Kodaris - Add all to cart on company/customer catalog tweaks
KOD-27709: Customized Lead Times Configuration
- Regression Tests
- Case 1
  - Check if the lead time message doesn’t appear when there is no skus with inventory level or lead time provided for a product.
- Tests
- Case 1
  - Find a company that has a customer type different from “Consumer“ to be able to get selected company on the customer portal.
  - Assign your account into that company.
  - Make sure the “Location“ field for that company is empty - that would be your warehouse for the company in the next test.
  - Get some product with skus and lead times provided for that product.
  - Check that product on the website - lead times displaying only on the product list.
  - Lead time used to provide range for shipping information value should be taken from the sku with the largest lead time for the product.
  - Once you clarify that it’s displaying the correct value, go ahead and assign some location into the company that you are assigned into.
  - From now on, if there is inventory level for sku and that sku will be the same as company location (warehouse) it will display 2 days lead time message, there would be no inventory level it should display lead time ranges based on lead time for the sku.
  - Once you confirm that flow is working, turn on company addresses for the company that you are assign into and select one.
  - Check if lead times information is displayed with same logic as for the company warehouse.
KOD-27720: Kodaris - Sync Returns as Credits
KOD-27749: Table Insert Border in PIM
- Regression Tests
- Case 1
  - Check that the product details page looks correctly.
  - Check that there are no errors in the console.
  - Check that the product details page layout looks good across different screen widths (mobile devices, tablets).
- Tests
- Case 1
  - Check that the item names in the Resources tab on the product details page are removed and only the links under the image are displayed.
  - Check that the Specs and Description tabs on the product details page are combined and appear correctly.
  - Check that the layout does not break if Specs are missing for a specific product.
  - Check that the product detail page layout looks correct across different platforms (desktop, mobile, laptop).
  - Check that the Featured and Specs sections on the product detail page are the same width.
KOD-27768: Create fraud record for declined attempts flag and fraud hold
KOD-27794: Improve Error Messaging
KOD-27819: Replatform - Customer Mobile App
KOD-27839: Display FAQs on the Website
- Tests
- Case 1
  - Open FAQ Page.
  - Test responsive for the page, that mobile and desktop versions working properly.
- Case 2
  - Open FAQ page in the operation portal here.
  - Create a few more FAQs for the test.
  - Go to the website FAQ page. Reload it and see the new FAQs rendered correctly.
- Case 3
  - On the FAQ page test the functionality of the search input.
  - Use random strings from the questions and answers to test that searching works properly.
- Case 4
  - Go to the FAQ page.
  - Test “Read More” button functionality.
  - Try to search FAQ with the specific string.
  - Reset search input.
  - See that the state Reset to default.
KOD-27848: Contract Pricing-Honor Hierarchy of Pricing not working
KOD-27917: Remove Part Number search
KOD-27925: run connector
KOD-27939: Invoice Missing in Kodaris System Created From Ticket 36222
KOD-27944: Order parser From Ticket 36027
KOD-27959: Remove postProcessOrderUsingRuleUtils setting from fraud flow
- Regression Tests
- Case 1
  - Validate confirmation emails are being sent with the proper shipping method information.
  - Pre-requirements:
  - Setting enableOrderByStore must be enabled.
  - Steps:
  - From the Customer Portal add some items to the cart.
  - Proceed with the purchase (select Customer Pickup as shipping option).
  - Before placing the order, open a logs screen from the Operations Platform.
  - Place the order by any payment method, e.g. Pay with PO.
  - The expected outcome is that the confirmation email Shipping method must be Customer Pickup and a log line like this [JS] RuleUtils: Sending confirmation email for order… must appear.
  - NOTE : to enable Pay With ACH Account , the company setting allowACHCheckoutPayments must be enabled.
- Case 2
  - Validate that order is put on hold in Kodaris with Employee Status set to Fraud Data Hold when autorelease logic runs after purchase and setting fraudDataCheckOnCartCheckout is enabled and the value set in the setting fraudDataKodarisHoldThreshold is smaller than the fraudData risk score calculated.
  - Pre-requirements:
  - Setting fraudDataKodarisHoldThreshold must be set to a value greater than 0.
  - From Customer Portal add some items to the cart.
  - Proceed with the steps filling up the fields.
  - Before placing the order, open a logs screen from the Operations portal.
  - Place the order by any payment method, e.g. Pay with PO.
  - The order must not have been released to the ERP , the Employee Status field must have been set to Fraud Data Hold and the trendHold order setting must have been set to 1 now and a log line like this [JS] RuleUtils: Checking FraudData for Order… must appear.
  - NOTES :
  - To enable Pay With ACH Account , the company setting allowACHCheckoutPayments must be enabled.
  - Repeat the test for the other payment methods Pay with credit card , Pay with ACH Account.
- Case 3
  - Validate that when setting holdWebOrders is enabled and setting holdPickupWebOrders is disabled those web orders whose shipping option is CPU are autorelease to the ERP.
  - Pre-requirements:
  - Setting holdWebOrders must be enabled.
  - Setting holdPickupWebOrders must be disabled.
  - Setting enableOrderByStore must be enabled.
  - Steps:
  - From Customer Portal add some items to the cart.
  - Proceed with the purchase and in step 3 Delivery Payment select Customer Pickup as shipping option and fill the rest of the fields.
  - Before placing the order, open a logs screen from the Operations portal.
  - Place the order by any payment method, e.g. Pay with PO.
  - The order must have been released to the ERP and a log line like this [JS] RuleUtils: holdPickupWebOrder is not 1 must appear.
  - NOTES :
  - To enable Pay With ACH Account , the company setting allowACHCheckoutPayments must be enabled.
  - Repeat the test for the other payment methods Pay with credit card , Pay with ACH Account.
- Case 4
  - Validate that order is auto released when autorelease logic runs after purchase and setting fraudDataCheckOnCartCheckout is enabled and the value set in the setting fraudDataKodarisHoldThreshold is greater than the fraudData risk score calculated for that order.
  - Pre-requirements:
  - Setting fraudDataCheckOnCartCheckout must be enabled.
  - Setting fraudDataKodarisHoldThreshold must be set to a value greater than 0.
  - Steps:
  - From Customer Portal add some items to the cart.
  - Proceed with the steps filling up the fields.
  - Before placing the order, open a logs screen from the Operations portal.
  - Place the order by any payment method, e.g. Pay with PO.
  - The order must have been released to the ERP and a log line like this [JS] RuleUtils: Checking FraudData for Order… must appear.
  - NOTES :
  - To enable Pay With ACH Account , the company setting allowACHCheckoutPayments must be enabled
  - Repeat the test for the other payment methods Pay with credit card , Pay with ACH Account.
- Case 5
  - Validate that when setting holdWebOrders is enabled and setting holdPickupWebOrders is enabled those web orders whose shipping option is CPU are NOT autorelease to the ERP.
  - Pre-requirements:
  - Setting holdWebOrders must be enabled.
  - Setting holdPickupWebOrders must be enabled.
  - Setting enableOrderByStore must be enabled.
  - Steps:
  - From Customer Portal add some items to the cart.
  - Proceed with the purchase and in step 3 Delivery Payment select Customer Pickup as shipping option and fill the rest of the fields.
  - Before placing the order, open a logs screen from the Operations portal.
  - Place the order by any payment method, e.g. Pay with PO.
  - The order must on hold and a log line like this [JS] RuleUtils: holdPickupWebOrder is… must appear
  - NOTES :
  - To enable Pay With ACH Account , the company setting allowACHCheckoutPayments must be enabled.
  - Repeat the test for the other payment methods Pay with credit card , Pay with ACH Account.
KOD-27981: Job Schema Markup for certain CMS Pages
KOD-27980: Model Lookup - Next steps
- Regression Tests
- Case 1
  - Navigate to any page.
  - Verify page loads without JavaScript errors related to variable c.
- Case 2
  - Navigate to model lookup page ( /spcu/lookup ).
  - Verify page loads.
  - Check that integration loads properly.
- Tests
- Case 1
  - Open browser console.
  - Navigate to model lookup page ( /spcu/lookup ).
  - Verify page loads without JavaScript errors related to variable c.
- Case 2
  - Navigate to model lookup page ( /spcu/lookup ).
  - Go to a product.
  - Click View Details.
  - Verify panel opens with product details.
  - Verify product information displays correctly like name , part number , price , image and availability .
- Case 3
  - Open panel with valid product.
  - Verify quantity selector works.
  - Click Add to Cart button.
  - Verify product is added to cart with correct quantity.
  - Verify cart badge updates.
  - Verify panel closes after successful add.
- Case 4
  - Navigate to model lookup page ( /spcu/lookup ).
  - Open browser network tab.
  - Go to a product.
  - Click View Details.
  - Go to the network tab and find /api/user/product/code request.
  - Right click on the request and Block request URL.
  - Close the panel and click View Details for the same product.
  - Verify panel handles errors gracefully.
- Case 5
  - Navigate to model lookup page ( /spcu/lookup ).
  - Open browser network tab.
  - Go to a product.
  - Click View Details.
  - Click Add to Cart.
  - Go to the network tab and find /api/user/cart/item request.
  - Right click on the request and Block request URL.
  - Close the panel and click View Details for the same product.
  - Click Add to Cart again.
  - Verify Add to Cart button handles errors gracefully.
  - Note: Remove all network request blocking patterns after testing.
KOD-27999: parser request
KOD-28015: Customer parser From Ticket 36592
KOD-28016: Add flag on controllers to be able to skip syncing records to ERP
- Regression Tests
- Case 1
  - Validate add/update product price record continues working as the same from Pricing Screen.
  - Pre-requirements:
  - Setting jobSyncProductPriceToErpEnabled must be enabled.
  - Steps:
  - From the operation portal, go to Pricing Screen.
  - Add/update a record.
  - Last Modified Locally must always be set to the current date and time.
  - Wait (or run it manually) until FiveMinuteBulkJobsJob runs.
  - Verify those records' field Last Sync to ERP is updated to the current date and time.
  - To the same from Company > Pricing screen.
- Case 2
  - Validate product price imports continue working as the same from Pricing Screen.
  - Pre-requirements:
  - Setting jobSyncProductPriceToErpEnabled must be enabled.
  - Steps:
  - From the Pricing screen import some CSV file without the new optional column syncToERP.
  - The import must work as always - All the added/updated records must have the field Last Modified Locally set to the current date and time.
- Case 3
  - Validate add/update product price record continues working as the same from Company Pricing Screen.
  - Pre-requirements:
  - Setting jobSyncProductPriceToErpEnabled must be enabled.
  - Steps:
  - From the operation portal, go to Company and then select Pricing tab.
  - Add/update a record.
  - Last Modified Locally must always be set to the current date and time.
  - Wait (or run it manually) until FiveMinuteBulkJobsJob runs.
  - Verify those records' field Last Sync to ERP is updated to the current date and time.
  - To the same from Company > Pricing screen.
KOD-28017: Kit builder - List fixes
KOD-28024: Kit builder - Order Templates
KOD-28026: Payment Methods
KOD-28029: File Upload from Customer Order Screen
- Regression Tests
- Case 1
  - Navigate to an order in the customer portal. You should be able to attach a file regardless of the order status.
KOD-28031: Payment Configuration Credit Card at Checkout
KOD-28039: Parser from Ticket 36677
KOD-28040: Order parser Created From Ticket 36538
KOD-28045: Implementing ACH at Checkout
KOD-28046: Export ticket wishlist products and push to datalake
KOD-28055: AP: Disregard Inactive Lines in PO-Invoice Matching Process
KOD-28056: Investigate pricing tolerance issue
KOD-28071: AP: Unit Conversion UX Fixes
- Regression Tests
- Case 1
  - Check that the layout of the Vendor Invoices page looks good, namely in the items tab.
  - Check that the grid on the Vendor Invoices -> Items page looks correct.
  - Check that there are no errors in the console.
- Tests
- Case 1
  - Check that when opening the Cross Reference modal window, the error shown in the screenshot does not appear (even if you change the code beforehand).
  - Verify that after creating a Cross Reference, the CompanyCode field is filled in on the Cross References page.
- Case 2
  - Open Vendor invoice Items tab.
  - Open network tab.
  - Try to open the “Manage Cross Reference” modal for items that doesn’t exist in products.
  - See that the “Product” field is not pre-populated.
  - In the “Network” tab check /api/system/productCrossReference/list request, see that filterFields contains companyCode filters.
  - Click on “Cancel” and see that there’s no redundant requests after modal close.
KOD-28082: Update Host Code Per Companies
KOD-28080: Set-up & Brand new Host
KOD-28078: Upgrade current system to multi-host
KOD-28084: Pricing Issue
KOD-28085: Align Tags to Bottom
- Regression Tests
- Case 1
  - Please test that the product grid view looks good.
- Tests
- Case 1
  - Please test that tags are aligned to the bottom of the product component (next to the inventory).
KOD-28090: Add ship-to to customer columns Created From Ticket 29244
KOD-28094: Payment Portal Email Addresses
KOD-28097: Not all invoices displaying on Payment History Record Created From Ticket 37290
- Regression Tests
- Case 1
  - You should still be able to access the payments history screen in the customer portal (as long as you have the accountsPayable role) as well as you should still see the applied invoices listed out (if applicable).
- Tests
- Case 1
  - If a payment has over 10 invoices, you should now be able to see all of them listed out on the payments history details screen.
KOD-28095: AP - Exceptions Created From Ticket 37251
KOD-28101: Remove requestedDeliveryDate which is not going to be used.
- Regression Tests
- Case 1
  - When adding/editing a product in the cart you may choose to “Pick up” or “Delivery” it. When “Delivery” you’ll be able to pick a delivery date. The UX will send this date through a field named “deliveredDate” and it will be saved as a Custom Field of the Order Item.
KOD-28105: SFTP file list endpoint and customer file upload
KOD-28104: Add Endpoint to Clone Ticket Templates
- Regression Tests
- Case 1
  - Clone Tickets by Group.
  - Clone Tickets by group. Do not put in a companyID.
  - This should not throw any errors and should just create a clone of each ticket of that type with the title’s, title prefix’s etc. that are given during cloning.
- Tests
- Case 1
  - Clone Tickets by group with a companyID.
  - Do the same thing as in Case 1 of the regression tests but this time also provide a CompanyID.
  - You should expect the same results as in Case 1 of regression tests, but these tickets should also have their CompanyCode and BillableCompanyCode fields populated with the code of the company you gave.
- Case 2
  - Clone TicketTemplates by group.
  - Use the new endpoint I created to clone ticketTemplates by group.
  - This works in the same way as the clone tickets by group endpoint does.
  - Make sure that your resulting tickets have ticketType Ticket and not TicketTemplate.
- Case 3
  - Clone TicketTemplates by group with CompanyID.
  - Clone ticketTemplates by group again but this time provides a companyID.
  - Now you have to check that the resulting tickets have type Ticket and not TicketTemplate, and that the companyCode and billableCompanyCode correspond to the companyID you gave.
KOD-28111: Verbiage added to checkout Created From Ticket 37369
- Regression Tests
- Case 1
  - Check that checkout steps are displayed correctly on different device types.
  - Check that the checkout functionality is working correctly.
  - Check that there are no errors in the console.
- Tests
- Case 1
  - Check that in step 3 of the checkout process, under "All online orders will automatically default to the ' Ship Complete '.” , the following phrase has been added:
  - "Note: Additional freight or delivery surcharges may apply and will be displayed on the order acknowledgement".
KOD-28121: AP: Mapping Update for vendor
KOD-28124: Parser from Ticket 37216
KOD-28123: Parser from Ticket 37217
KOD-28125: Kodaris - Can view AI Chat screen & ops portal in Kodaris
KOD-28128: Event Pages: Fix issues
- Regression Tests
- Case 1
  - Make sure you can still change to the different views as well click into the previous/next events and can still search.
- Tests
- Case 1
  - On the calendar events page, the arrows on the view as and previous/next events should be displayed properly.
  - Note: Can’t test this locally as it was working before and still looks like it is working with the updates, but we are using the html entities in the code now instead of just the characters.
- Case 2
  - When you update the date on the calendar and click find events, it should return you the correct events.
- Case 3
  - Clicking into an event should generate the event post page and you should be able to download the event to iCalendar or Google calendar.
- Case 4
  - In list view, if the event spans more than one day, you should only see the event listed once.
- Case 5
  - In the Gutenberg editor, you should be able to update the event start and end date and time.
KOD-28127: Implement Insert Order V4 for SX
KOD-28130: Implementation - Images
KOD-28131: Investigate issue with tariff order
KOD-28134: H1 Letter Case Update
- Regression Tests
- Case 1
  - Confirm that the text tags on the site page have styles applied - font-size, font-weight, and font-family.
- Tests
- Case 1
  - Confirm that all h1 tags are displayed in normal case (not uppercase), both on the live site and in the Gutenberg editor.
- Case 2
  - Confirm that in Gutenberg we can change this to uppercase if needed.
KOD-28135: Add Retail Pricing
KOD-28140: Translation not saving when clicking a link from French email
KOD-28141: Add to Website Created From Ticket 37525
KOD-28144: Kit Shipping
KOD-28147: Infor SX - Payments Integration Compatibility Updates
KOD-28151: Turn on CC option for all customers at checkout
KOD-28158: Kits showing labor details on invoice
KOD-28157: Order notes section update
- Regression Tests
- Case 1
  - Please verify that the order templates still look good.
  - You can navigate to the customer portal, choose any order and check if everything looks good.
  - Also in this order, you can click on the print button for generating the pdf, then click on the files tab, choose the last pdf file and check if everything is ok.
  - For email, you need to go to the operations portal, order screen, choose any order, then click on the email icon, generate an email and verify if everything looks good.
- Tests
- Case 1
  - Please verify that the order templates have a notes section.
  - You can navigate to the customer portal, choose any order and check if the template contains the notes section.
  - Also in this order, you can click on print button for generating pdf, then click on files tab, choose the last pdf file and check if template contains notes section.
  - For email, you need to go to the operations portal, orders screen, choose any order, then click on email icon, generate email and verify if template contains notes section.
KOD-28160: Core Charge Invoice Display & ERP Integration
- Regression Tests
- Case 1
  - Insert order in CSD (Any environment).
  - Make sure it is working as expected (No errors when going to the ERP). The externalOrderNumber should be populated successfully.
- Case 2
  - Insert an order in SX in Fox (or any environment) without using CoreCharge items.
  - Make sure it is still working as expected.
  - All the items should go to the ERP (unless it is inactive in the order).
- Tests
- Case 1
  - If there are any KCoreCharge products in the order, when releasing to the ERP (SX), those items should NOT be in the order request (You can validate in the SystemEvent - line items).
  - Also, after the process ends the KCoreCharge items in the order should change to INACTIVE.
KOD-28162: A customer submitted a form on the website
KOD-28170: Missing SKU associations for certain products
KOD-28168: Add validation to prevent special characters in Host code field
- Regression Tests
- Case 1
  - Navigate to the Hosts page.
  - Confirm we can see a grid with the created hosts and can add/hide columns.
  - In the code input, enter a string containing only letters and numbers.
  - Create a Host.
  - Verify that the entered text appears in the Code column.
- Case 2
  - Navigate to the Hosts-details page.
  - Confirm, you can see the current host details.
  - In the code input, change some characters using only letters and numbers.
  - Focus on another input and confirm that, code data was changed.
  - Returning to the hosts page, you will see that the code has been changed.
KOD-28172: Order shipment notifications - Define a notification start date
KOD-28173: Allow price check by warehouse code in pricesByCodes
- Regression Tests
- Case 1
  - You should be logged in into the customer account.
  - Disable enablePriceCheckWarehouse setting. If you don't see such setting in the list, please add one
  - Test, these endpoints:
  - /api/user/product/pricesByCodesV2
  - /api/user/product/pricesByCodes
  - Works as intended.
  - Confirm that next logic works correctly:
  - The value priceCheckWarehouse should be ignored when enableShopByStore setting is disabled.
  - If enableShopByStore is enabled, priceCheckWarehouse should not be ignored and return appropriate results.
- Tests
- Case 1
  - You should be logged in into the customer account.
  - Enable enablePriceCheckWarehouse setting. If you don't see such a setting in the list, please add one.
  - The only difference from regression test case:
  - The value of priceCheckWarehouse should not be ignored regardless of enableShopByStore setting.
KOD-28180: Update Fee Created From Ticket 37570
KOD-28188: Modifying default customer order > items view
- Regression Tests
- Case 1
  - Check that the Orders screen in the customer portal works fine without issues.
- Tests
- Case 1
  - Check that the Shipped column has now been added to the Orders screen and data is populated for orders that have a Shipped date.
  - Can check the order shipdt field or setting.
KOD-28185: Display taxCode field on the Discount and OrderDiscount screens
- Regression Tests
- Case 1
  - Verify that layout in grid and detail views displays correctly on Discount and OrderDiscount screens.
- Tests
- Case 1
  - Verify that the taxCode checkbox appears in the modal window for Discount and OrderDiscount.
  - Verify presence of taxCode column in Discount and OrderDiscount grids.
  - Verify presence of taxCode field on Discount and OrderDiscount detail forms.
  - Verify taxCode value change in grid reflects in detail form and new value is properly saved and displayed.
  - Verify that filtering and sorting are disabled (taxCode field) on the Discounts and OrderDiscounts screen.
KOD-28196: Proposition 65
KOD-28198: Create generic customer automated email template
KOD-28197: AP- Data Sync Created From Ticket 37928
KOD-28203: Update filter name and remove from dynamic filters
- Regression Tests
- Case 1
  - Please check that categories and filters are displayed as usual.
- Tests
- Case 1
  - Please test that under categories filters there is no Fall Clearance category.
- Case 2
  - Please test that under shop by category there is no Fall Clearance category.
KOD-28206: Add Fields to Order and OrderItems OS
KOD-28210: Incorrect transaction
KOD-28207: Promo tag filter Categories issues Investigation
KOD-28211: Spin Up System
KOD-28226: Home Slider - Ability to control timing of slider
- Regression Tests
- Case 1
  - Check that the slider still works and looks as usual (after updating from the previous step).
- Case 2
  - Go to the operations portal > Menus screen.
  - In the Home Slider section, you should still be able to add, update, and remove slides.
- Tests
- Case 1
  - Go to the operations portal > Menus screen.
  - In the Home Slider section, there should now be an update to change the slider speed - how long it takes before the next slide appears.
  - Try changing the time and make sure the change is reflected on the website.
KOD-28234: Fix discrepancy handling logic in Orders table
- Tests
- Case 1
  - Go to Orders → Order → Order Items tab.
  - Open Developer Tools, Network tab.
  - Try to edit any cell in the table.
  - See, that when we update the table we don’t have any request duplicates in the network tab.
KOD-28238: Add a setting to enable fraud checks for ERP integrations
- Regression Tests
- Case 1
  - Validate when reach endpoint /api/system/integration/infor/extension/fraudCheck and the new setting fraudDataCheckForERPIntegrationsEnabled is enabled the fraud data checks continue working as always.
- Tests
- Case 1
  - Validate when reach endpoint /api/system/integration/infor/extension/fraudCheck and the new setting fraudDataCheckForERPIntegrationsEnabled is disabled a 200 response is retrieved with a risk score of -1.
KOD-28241: Implementation - Countries / States