With this release, Kodaris now supports automatic redirects from discontinued product pages to their replacement products. This feature utilizes "supersede" cross references (Type P), which indicates when an old product code has been deactivated and replaced with a new version.
The implementation is straightforward through the Search Tuning page. Simply navigate to the Product Redirect tab and add a new entry with the pattern "supercedesOrReplacement" and the Action Data value "P". Once configured, customers searching for discontinued product codes will automatically land on the replacement product's detail page, eliminating confusion and ensuring a seamless shopping experience.
The product redirect feature is available now in the latest system update. For a visual walkthrough of the configuration process, please refer to our implementation video.
https://youtu.be/d1j4c2ggvPQ
Tickets
KOD-20802: Quotes Template for Kodaris
KOD-24524: Cache User Preferences
KOD-24759: PIM - Missing host code restrictions on new products
KOD-26407: Setup lockbox EDI 820 file
KOD-26628: Model Lookup API
KOD-26674: Create product redirect for discontinued products with supercede cross reference
Regression Tests
Case 1
Go to the operations portal → /operations/search-tuning/product-redirect.
Add some rules for the product.
Go to the operations portal again → /operations/cross-references.
Add some cross references for testing product redirects.
Go to Kodaris website, and use the search field to search your product. Ensure product redirect function is working.
KOD-26764: Request Quote Button #2
KOD-26914: Kodaris - Scope creating a FAQ page and interface for creation
Regression Tests
Case 1
Go to CMS → FAQs and create a FAQ item.
Go to CMS → Pages. Try to find a FAQ entity in the table by using a search field. Input The question text in it.
See that there’s no FAQ item in the table.
Case 2
Go to CMS → FAQs and create a FAQ item.
Go to CMS → Pages → Data tab.
Turn on the Subtype column.
Type “FAQ” in the column search input.
See that there’s no entity with type “FAQ”.
Tests
Case 1
Open CMS -> FAQs page.
Try to create a new FAQ item, set random data to it.
Go back to the FAQs search page, see that the new item was created.
Go to the Data tab. Try to change data of any FAQ item.
Go back to the Search tab, reload content and see the updates.
Case 2
Open CMS -> FAQs page.
Try to use filters/sorting functionality for all cells and check the result.
KOD-26934: Kodaris - Add Active field to Commissions screen - UX
Tests
Case 1
Navigate to the Commissions page in the operations portal.
Verify that the "Active" column is displayed in the data grid.
Locate any commission record in the list.
Click on the Active field value (Yes/No) for that record.
Verify that a dropdown appears with "Yes" and "No" options.
Select the opposite value (if it was "Yes", select "No" and vice versa).
Verify that the value updates in the grid and the change is persisted.
Case 2
Navigate to the Commissions page.
Locate the Active column header.
Click on the filter icon.
In the filter panel, select the "Equals" option and test it with “Yes” and “No”.
Verify the filter works.
For filters different from “Yes” or “No” the filter should be ignored.
In the filter panel, select the "Doesn’t equal" option and test it with “Yes”, “No” and any other value.
Verify the filter works.
Clear the filter by clicking on “Clear”.
Verify all records appear.
Case 3
Navigate to the Commissions page.
Click on any commission record to open the details screen.
Locate the "Active" field.
Note the current value of the Active field.
Click on the Active dropdown and select the opposite value.
Verify that the Active value was changed.
KOD-26962: Integration
KOD-26989: No Inventory Online but inventory in CSD
KOD-27053: Banner Content on SERP pages
Regression Tests
Case 1
Check if the search page is working correctly.
Case 2
Check if other pages like the category page are working correctly.
Case 3
Check if regular customers and not logged in employees without ‘superuser’ roles are not able to see “Manage Slider“ button.
KOD-27100: Update to product images on details page
Tests
Case 1
Open test product (desktop).
Navigate to a product page with more than 4 images.
Verify swiper functionality.
View the images using the swiper.
Verify single-image product (desktop).
Verify zoom functionality (desktop).
Repeat checks on mobile.
Open the same products on a mobile device.
Expected result: Images are displayed correctly, swiper works for multiple images, and zoom functionality is available.
KOD-27163: Payment type issue
KOD-27201: Don't send retail price if logged out user
Regression Tests
Case 1
When you click into a product, make sure when you log out, you see no prices and when you log in, you see the cost as well as the retail price.
Case 2
When you are logged in and on a product details page, right click on the page to view the source, then search on data-retail-price and notice that the retail price is still being passed through.
Tests
Case 1
When you are logged out and on a product details page, right click on the page to view the source, then search on data-retail-price and notice that there is no value in there.
KOD-27248: Automation From Ticket 31541
KOD-27289: Customization for Level 3 Data
KOD-27355: Managed retails not displaying when in customer view Created From Ticket 31990
Regression Tests
Case 1
Make sure when you are on store view, and viewing a product, nothing has changed.
If the product is part of the retail price catalog, you should see the cost, retail price and your retail price.
If the product is not part of the retail price catalog, you should see cost and retail price.
And in both options, you can update the retail pricing.
Case 2
Make sure for a product that does not have a price, in store view you still see a call for pricing.
For customer view, you shouldn’t see any info about pricing.
Tests
Case 1
When you are viewing a product on customer view, if the product is part of the retail price catalog, you should see “Retail Price:” displaying the price of what your retail price is on the store view.
Case 2
If the product is not part of the retail price catalog, on customer view, you should see the retail price with the retail price on the store view.
Case 3
Updating the retail price on both the store and customer view should update the retail price you see when on customer view.
KOD-27382: Sync Shipping Methods and Instructions Field
KOD-27396: Prevent parent companies from placing orders
KOD-27435: Units of Measure "Stock Price" is displayed
Regression Tests
Case 1
Open the website.
Log in.
Verify unit display for logged-in users.
Open a product configured with both unit sell and unit stock.
Expected result: Only unit sell values are displayed; unit stock is not shown.
Verify dropdown for single unit sell
Open a product that has only one unit sell available.
Expected result: Dropdown is not displayed;
Verify product without units
Expected result: No unit selector is displayed on the product page.
Tests
Case 1
Open the website.
Open a product with unit sell and unit stock.
Verify unit display.
Expected result: Only unit sell values are displayed; unit stock is not shown.
Verify dropdown for single unit sell.
Check a product that has only one unit sell available.
Expected result: Dropdown is not displayed.
KOD-27452: Online Order update, re-authorized amount not show in CSD
KOD-27461: ERP User Credentials
KOD-27470: Invoice Parser
KOD-27472: Parser
KOD-27480: API Connector - PIM Connector
KOD-27484: Payment Methods
KOD-27506: Department not filled in on ticket screen
KOD-27508: Kitbuilder - Project
KOD-27519: Approval Process
Regression Tests
Case 1
Validate that when releasing a Cash Quote this is marked as WON.
Case 2
Validate that when changing Quote status details to Quote Lost, Quote Expired or Quote Won from operations platform screen settings quoteLost, quoteExpired or quoteWon are properly added and the value must be the current date.
Tests
Case 1
When a customer accepts a quote via the new endpoint /api/account/order/{orderID}/acceptQuote and the order is Cash Quote which is Pending and new setting enableCustomerToAcceptCashQuote is enabled, then:
This Cash Quote’s statusDetails and employee status must be set to Status Quote Won.
Cash Quote’s setting quoteWon must appear and its value must be the current date.
The Cash Quote’s status must be Initialized and this must have been added to the customer cart so they can complete the purchase by any payment method.
Case 2
When a customer accepts a quote via the new endpoint /api/account/order/{orderID}/acceptQuote and the order is Cash Quote which is not Pending and new setting enableCustomerToAcceptCashQuote is enabled, then a 400 response is returned with an error message indicating invalid status.
Case 3
When a customer accepts a quote via the new endpoint /api/account/order/{orderID}/acceptQuote and the order is not Cash Quote and new setting enableCustomerToAcceptCashQuote is enabled, then a 400 response is returned with an error message indicating invalid type.
Case 4
When a customer accepts a quote via the new endpoint /api/account/order/{orderID}/acceptQuote and the order is not Cash Quote and new setting enableCustomerToAcceptCashQuote is disabled, then a 401 response is returned with an error message indicating an unauthorized error.
Case 5
When a customer accepts a quote via the new endpoint /api/account/order/orderID}/acceptQuote and the order is Cash Quote and customer does not have access to the order, then a 404 response is returned with an error message indicating that the order was not found .
KOD-27586: Rollout upgraded flow
KOD-27600: Return statuses
KOD-27616: Add purchase history tab to product detail page Created From Ticket 33499
Regression Tests
Case 1
Go to any product page and check that existing tabs Product Details and Resources still work. Click between them to make sure nothing is broken.
Case 2
Test the page on all breakpoints (on different screen sizes). Make sure the layout looks good and nothing is broken on different screen sizes.
Case 3
Try the product page without logging in. The Purchase History tab shouldn't be rendered, everything else should work normally.
Tests
Case 1
Log in and go to a product you've bought before. Click the Purchase History tab and verify it shows your past orders in a table with correct dates , quantities , and prices .
Case 2
Log in and go to a product you've never bought before. Click the Purchase History tab and check it says "You have no purchase history for this product yet. "
KOD-27629: Page URLs and items opening in new window
KOD-27647: Add system events to the cash quotes & contract quotes screen for troubleshooting
Tests
Case 1
For this case, we will navigate to the Cash Quotes screen - Select a Cash Quote.
Now, you should see a System Events option in the Top Menu Bar. We will click on it.
You should see a grid with the System Events related to that Cash Quote (by orderID). You can see that the list endpoint is pointing to api/system/event/list and the orderID in the payload to filter by it.
Make sure you are able to Preview, Download and go to the Details of every item.
When you go to the Details screen, make sure you are able to edit the available fields and that the changes are reflected correctly.
While in the System Event Details screen, test the breadcrumbs and make sure they redirect you to the correct screens.
Let’s also test the Custom Fields and Development tabs.
Make sure they load correctly and that you can edit/add items correctly.
Case 2
For this test, we will repeat the steps of case 1 but for Contract Quotes.
KOD-27648: Overdue Report Created From Ticket 34088
KOD-27672: Display Tariffs on product details page
Regression Tests
Case 1
Open the website.
Open product without discount.
Expected result: The product detail page is displayed, and no “+ Tariff” text is shown.
Tests
Case 1
Log in to the website.
Open product with “-tariff” discount code.
Verify text on product detail page (desktop).
Check the product detail page.
Expected result: The “+ Tariff” text is near the price displayed correctly.
Verify mobile version.
KOD-27684: Auto generate OpenSearch Mappings and updates
KOD-27683: Invoice Email Sending configuration for company addresses- Platform
KOD-27687: Zooming on product images, it's using medium-sized images which appear fuzzy
KOD-27688: Review URLs
KOD-27691: Mapping Freight Lines
KOD-27692: Substitute parts/supersedes parts
KOD-27694: Update username to email on login screen
KOD-27699: Indicator and Error Messaging for Mandatory Fields
KOD-27710: Remove "Subscribe to Updates" form on blog post layout
Tests
Case 1
Check if pages that use blog-post layout don't contain “Subscribe to Updates" form.
Check if the layout is responsive.
KOD-27713: Kitbuilder mobile responsiveness
KOD-27719: KITS Serial Numbers
KOD-27725: Add entityType and entityID fields to Tickets Search tab in the Operations Portal
Regression Tests
Case 1
Open the tickets page. Ensure that there are “Entity Type” and “Entity ID” fields in the fields select box.
Try to select these fields and do search/sorting.
KOD-27731: Import Gift Cards
KOD-27733: Flat rate shipping
KOD-27738: Unhandled error page when accessing credit application as a not logged in customer
Regression Tests
Case 1
Validate when trying to access credit-application screen from the customer portal while logged in and the company status is “Applying For Credit”, the credit-application screen must be rendered.
Tests
Case 1
Validate when trying to access /credit-application screen from the customer portal while logged out , error screen must be rendered with the message “Unauthorized”.
Case 2
Validate when trying to access credit-application screen from the customer portal while logged in and the company status is not “Applying For Credit”, error page with message “Access allowed only for companies that are applying for credit“.
KOD-27747: Ensure we are syncing the "Quantity Break Type" Field to the ERP
Regression Tests
Case 1
Make sure you can still add/change a product price.
Tests
Case 1
On the pricing page in the operations portal, click into a price.
Make sure the quantity break type is filled in.
Click save to the ERP button.
Go to the events or system events screen and look for CSDProductPrice_ResponseProductPrice (will either have Add or Change after Price) → click to preview and notice the qtybreakty is now being sent.
KOD-27750: Updates to rules
KOD-27762: Fix issues with shipping option selection
Regression Tests
Case 1
Confirm that the checkout page loads without issues, we can switch between the tabs, and we see the shipping options and totals.
Case 2
Confirm that we cannot place an order until a shipping option is selected.
Tests
Case 1
Once a shipping option is selected, the totals are updated. If we go back to the first tab, change the item quantity, then move to the third tab, the shipping option price is different. When clicking on the same shipping option again, the totals update accordingly, and we are then able to place the order.
KOD-27764: parser line number fix for Ticket 34997
KOD-27763: Sales Territory Assignment - UX to Mass Manage Sales Rep Assignment
Regression Tests
Case 1
Open the operations portal → Employees page.
Scroll to the right to see that the “Sales Territory” column does exist.
Go to the Data tab.
Scroll the table to the right, find the same “Sales Territory” column.
Try to edit fields in some employee rows.
Reload the page to see if the data was saved.
KOD-27767: System
KOD-27769: Install Applications
KOD-27776: Invoice PO Number Not Read Created From Ticket 35050
KOD-27781: Contact page showing wrong page on customer site
KOD-27782: Order Items screen Product Line filter update
Regression Tests
Case 1
Check that the grids on the Cash Quotes, Quotes, Orders, Purchase Orders pages look correct, the filters work.
Check that there are no errors in the console.
Check that the layout of the Cash Quotes, Quotes, Orders, Purchase Orders pages looks good, namely in the items tab.
Tests
Case 1
Make sure the new Product Line filter is clickable and the filter text appears correctly on the page.
KOD-27783: Update the behavior of Add Item Suggester in Purchase Orders
Regression Tests
Case 1
Check that the filter button is working.
Check that the console displays no errors when interacting with the items grid on the purchase order items pages.
Check that the layout on the Purchase Order > Items pages is intact.
Tests
Case 1
Check that the filter button on the page - purchase order items - works correctly and is similar to, for example, cash quotes items.
Check that the correct endpoint is called - the elements in the tooltip are displayed correctly.
KOD-27785: Custom Home Page
KOD-27788: Fix overlapping text in alert component
KOD-27795: Product Display - Part Numbers in Description
Regression Tests
Case 1
Check that category screen still looks good (list/grid/catalog).
Case 2
Check that the product details page still looks good.
Case 3
Check that the first step of checkout still looks good.
Tests
Case 1
Navigate to the product details page.
If a product contains ‘C-’ at the begging of product code, you will still see part on page and no part under name.
If product doesn’t contain at the beginning of product code, you will still see part label and code will be with name but without the first three symbols of code.
KOD-27796: Returns Functionality
KOD-27801: Minimum Match Option Breaks AI Search
KOD-27806: Auto-Assign Order Type (Counter Sale vs Stock Order) Based on Pickup/Delivery
KOD-27807: parser from Ticket 35132
KOD-27812: Parser From Ticket 35244
KOD-27826: 401 error when installing Application via bitbucket repository using Atlassian API token
Regression Tests
Case 1
Go to the applications screen in the operations portal.
Click the Install > V2 option.
Everything should load fine without issues.
Case 2
Go to the Hosts screen and click Add Host.
Everything should load fine without issues.
Tests
Case 1
In both previous modals, there should be a new dropdown ‘authentication type’
It should contain two options, Repository Access Token and User API Key.
If you select the repo access token, it should display a single field below the dropdown for the API key.
If you select the User API Key, it should display two different inputs.
One for User Email and one for User API Token
KOD-27808: Migrate to new Jira APIs
KOD-27837: 500 Status Error happens when user tries to add a second kit to the cart
KOD-27851: OA: Incorrect Subtotal and Missing "Placed By" on Email-Generated Order Confirmations
