View all releases

March 5, 2026 release notes

Tickets

KOD-23877: Create a mega menu for demo website
- Regression Tests
- Case 1
  - Confirm that the homepage loads without errors.
- Case 2
  - Confirm that clicking on "Warehouse," "Sign In," "Shop by Category," or opening the menu via the burger icon on mobile works without issues and that no content overlaps them.
- Case 3
  - When searching for a product and you hit enter, make sure the og and sg are blank within the url ( og= sg=) and sid is populated.
  - When searching for a product and clicking See all results, you should see og={query search}sg=1
- Case 4
  - When searching for a product and you click a category, make sure you are still being directed to the right category.
- Tests
- Case 1
  - Confirm that search requests are sent only after entering at least two characters and that the dropdown menu with an overlay appears when a response is received.
- Case 2
  - Confirm that the overlay covers the page content except for the header, top bar, and the dropdown menu itself.
- Case 3
  - Confirm that the dropdown menu contains three sections: Categories, Brands, and Products , and that their content is displayed correctly.
- Case 4
  - Confirm that clicking outside the dropdown menu or search input closes both the menu and overlay.
- Case 5
  - Confirm that the dropdown menu displays correctly at all screen widths.
- Case 6
  - Confirm that if an error occurs, the dropdown menu closes.
- Case 7
  - Confirm that clicking on a product, category, or brand within the dropdown redirects to the corresponding page.
- Сase 8
  - Confirm that entering text into the search input and pressing Enter opens the search results page for that query.
- Сase 9
  - Confirm that, with or without the banner, the menu is positioned slightly below the input.
- Case 10
  - Confirm that “See all results >“ link will redirect you to the search page with searchString that entered in input.
KOD-26370: Sub-Parent Pricing Hierarchy Not Pulling Correctly
KOD-28256: system update
KOD-29357: Cash quote flow
KOD-29601: CC/ACH Processing Issues
KOD-29692: Transaction Flow
KOD-29703: Implementation - Statement Templates
KOD-29723: Pre-fix the Ship To Location code for various forms
- Regression Tests
- Case 1
  - Make sure that header still loads fine for guests and logged in as a customer.
  - Run tests that when you are logged in as a customer, you can choose any addresses and it should be applied.
- Case 2
  - Navigate to /spcu/form-special-order page.
  - Verify that this page still looks good.
- Case 3
  - Navigate to /spcu/form-installation-service page.
  - Verify that this page still looks good.
  - Verify that for Ship To # field, dropdown still looks good.
KOD-29743: Implementation - Shipping Methods / Shipvias
KOD-29750: Punchout for main site
KOD-29798: Tax Exempt Customers - Avalara Integration Part Two
KOD-29845: UX update for French AI search
- Regression Tests
- Case 1
  - Navigate to Languages ( /languages ).
  - Add a new language using the spare row (enter a code like pt-br and description "Portuguese (Brazil)").
  - Verify the new language appears in the grid with AI Search showing "Yes" or “No”.
  - Edit the description of an existing language and save.
  - Verify the description updates correctly.
  - Delete the test language created in step 2 and verify it is removed.
- Tests
- Case 1
  - Navigate to Languages ( /languages).
  - Verify the grid can display an AI Search column with "Yes" or "No" for each language (should not be displayed by default).
  - Double-click the AI Search cell for a language (e.g., fr-ca ).
  - Select Yes from the dropdown.
  - Verify the cell updates to "Yes" and the change is saved (row exits edit mode).
  - Refresh the page and verify the value persists as "Yes".
  - Double-click the same cell, select No , and verify it updates back to "Disabled".
KOD-29850: Add UX in operations portal for UPS Code Mapping update
- Regression Tests
- Case 1
  - Navigate to the Shipping Methods screen.
  - Choose any shipping method and navigate to the details page.
  - Check that the details page still loads fine.
- Case 2
  - Navigate to the Shipping Methods screen.
  - Choose any shipping method and navigate to the details page.
  - Check that header still looks good and you can navigate between different tabs.
- Tests
- Case 1
  - Navigate to the Shipping Methods screen.
  - Choose any shipping method and navigate to the details page.
  - Verify that you can see the new tab → Carrier Codes.
  - Verify that you can see data fine, you can create, update or delete records.
KOD-29871: Invoice emails isn't sent under Companies>Open Invoice screen
KOD-29900: Pricing Requirements
- Regression Tests
- Case 1
  - Check that the product list and product detail pages are still working as expected without issues.
  - Product pricing should still appear correctly as well if applicable.
- Tests
- Case 1
  - In this ticket, we made an update to display retail pricing on the product detail and product list pages instead of the normal customer calculated pricing.
  - The logic for price display is as follows:
  - If there is no catalog on the company with code=retailPriceCatalog.
  - The system displays the sku.listPrice if it exists.
  - If it doesn’t exist, it should display Call for Pricing.
  - If the catalog exists, but no products have been added, the same logic as step 1 should happen.
  - If the catalog exists:
  - If the price field is set, that value appears as the product price.
  - If productMarkup is set and the productMarkupType is set to static , the productMarkup value should be displayed as the price.
  - If productMarkup is set and the productMarkupType is percentage , the ( productMarkup times sku.listPrice divided by 100 ) + sku.listPrice should display as the price.
KOD-29907: Bulk Data Load Sync
KOD-29906: Bulk data load sync
KOD-29909: PIM Data Mass Export
KOD-29918: AP - Invoices-Files in Kodaris Changing to Different Format than Original PDF Format
KOD-29922: Map discounts from orders coming from CSD
KOD-29933: Mass Assign Filter Categories to a Category & Mark set Required field
KOD-29953: Parser for Vendor
KOD-29954: Update Mapping for Vendor
KOD-29957: Search Feedback
KOD-29959: Implementation - Invoice Mailer Templates
- Regression Tests
- Case 1
  - Go to the Operations Portal Orders → Orders. Select a random order.
  - Click on the “Generate File” button in the header. Select Wrapped order mailer template and generate it.
  - Open and check that the document generated properly, and we don’t have any broken UI.
KOD-29974: AP - Vendor failing to process in Kodaris system - Entering exception state
KOD-29976: Investigate and Test Automation Endpoint
KOD-29987: Column Dropdown FacetField filtering Solr
KOD-30001: Cookie Banner Update
KOD-30002: AP: New Vendor Invoice Format
KOD-30008: AP: Invoice Parser
KOD-30012: Cache not working for Rule endpoints
- Regression Tests
- Case 1
  - In Automation APP (It only appears with setting: enableOperationsPortalV2 enabled and not all the sites have it), we need to make sure we can do crud operation with any of the available rules (Without modifying the Script content neither the Workflow content).
  - Add a new Rule Interceptor. Be sure it is saved and then delete it.
  - Add a new workflow, make sure it is saved and then delete it.
- Tests
- Case 1
  - Lets make sure that we can update the content (script tab) of the Interceptors or a workflow and it brings the latest content after updating it.
  - Make sure you refresh the screen also to see if the changes are still there.
KOD-30014: Add Ticket Detail page to Services app
- Regression Tests
- Tests
- Case 1
  - Navigate to a ticket page (e.g., /operations/app/services/tickets/36).
  - Verify that the ticket title, status, description, comments, files, linked tickets, and sidebar fields are all populated with correct data.
  - Verify that the breadcrumb shows "Services > Tickets > {ticket code}".
- Case 2
  - Change the title and click outside (blur).
  - Verify that a PATCH request is sent with the updated title.
  - Click on the title again, make no changes, blur.
  - Verify that no PATCH request is sent.
- Case 3
  - Type a comment in the editor and click "Save".
  - Verify that the comment appears in the list.
  - Hover over the comment, click the edit (pencil) button, modify text, click "Save".
  - Verify that the comment is updated.
  - Hover over the comment, click the delete (trash) button.
  - Verify that the comment is removed.
- Case 4
  - Click "Upload" in the Files section, select a file.
  - Verify that the file appears in the list.
  - Click on the file name and verify the preview opens correctly.
  - Hover over the file, click the delete button.
  - Verify that the file is removed.
- Case 5
  - Click "Link" in the Linked Tickets section header.
  - Search for a ticket, select it, optionally choose a link type, click "Link".
  - Verify that the linked ticket appears in the list.
  - Click on the linked ticket code.
  - Verify that the page reloads with the new ticket data (no full page refresh).
  - Navigate back, hover over the linked ticket, click the delete (X) button.
  - Verify that the link is removed.
- Case 6
  - Click "Add assignee", search for an employee, select one.
  - Verify that the assignee appears in the list with correct name and initials.
  - Hover over the assignee, click the delete (X) button.
  - Verify that the assignee is removed.
- Case 7
  - Click "Actions" > "Log Time".
  - Verify that the ticket field is pre-filled and disabled.
  - Enter hours/minutes, a description, and click "Log".
  - Verify that the dialog closes and no error is shown.
- Case 8
  - Hover over a field in the sidebar (e.g., Priority), click the pin icon.
  - Verify that the field moves to the "Pinned" section at the top of the sidebar.
  - Refresh the page.
  - Verify that the field is still pinned (persisted in localStorage).
  - Unpin the field, verify it returns to its original section.
- Case 9
  - Change a select field (e.g., Priority) — verify PATCH is sent immediately.
  - Change a text field (e.g., External ID) and blur — verify PATCH is sent on blur.
  - Change a date field (e.g., Due Date) — verify PATCH is sent immediately.
  - Search and select a Billable Company — verify PATCH is sent with the company code .
KOD-30043: AP - Cut Charges
KOD-30044: Additional Template updates
- Regression Tests
- Case 1
  - Go to Orders → Orders.
  - Select a random order.
  - Try to generate a PDF invoice for this order using template FS - Wrapped Order PDF OLD . Check, that related from what status of the order is, we have a “Remit To” label at the top.
  - Check that in the footer of the invoice we have a “Pay online” table.
  - Check that the size of the table in the header decreased.
  - Try to generate Email Invoice for this order using template FS - Wrapped Order Email OLD . Check that the generated Email invoice has appropriate information on it.
- Case 2
  - Go to the Customers Portal → Orders. Select a random order.
  - Check that the order invoice has a “Remit To” label above the address in the top, the size of the table in the right top corner decreased and check that in the footer of the invoice we have a “Pay online” table.
KOD-30074: Tracking Numbers missing on Kodaris Invoice
KOD-30090: Link Display Issues
- Regression Tests
- Case 1
  - Ensure that buttons on CMS pages display correctly and are not affected by new styles.
  - Ensure there are no errors in the console on CMS pages.
- Tests
- Case 1
  - Ensure that links on CMS pages are displayed in black.
  - Ensure that links on CMS pages are underlined.
  - Ensure that links remain clickable and point to the correct URLs.
KOD-30099: Custom Export App - Export for Quote Non-Stock Items - Next Steps
- Tests
- Case 1
  - Navigation between Export pages works correctly.
  - Navigate to `/operations/app/import-export/`.
  - Verify the Exporters page loads as the default landing page.
  - Click "Export History" in the left navigation drawer.
  - Verify the URL updates to `/operations/app/import-export/export-history` and the Export History table is displayed.
  - Click "Exporters" in the left navigation drawer.
  - Verify the URL updates to `/operations/app/import-export/exporters` and the Exporters table is displayed.
- Case 2
  - Exporters list page loads and display data.
  - Navigate to `/operations/app/import-export/exporters`.
  - Verify the page renders a table with the title "Exporters".
  - Verify the table displays columns: Code, Name, Active, Created, Last Modified, and a Submit action button per row.
  - Verify the breadcrumb bar shows "Import / Export > Exporters".
  - Verify the left navigation drawer shows two groups: "Import" (with Importers, Import History) and "Export" (with Exporters, Export History).
- Case 3
  - Submit a custom export from the Exporters page.
  - Navigate to `/operations/app/import-export/exporters`.
  - Locate a row in the Exporters table and click its "Submit" button.
  - Verify the button shows a loading spinner while the request is in progress.
  - Verify a successful snackbar appears with the title "Export Submitted" and message "Your file will be available shortly in the Export History screen."
  - Verify the button returns to its default state after success.
- Case 4
  - Export History page loads and allows file download.
  - Navigate to `/operations/app/import-export/export-history`.
  - Verify the page renders a table with the title "Export History".
  - Verify the table displays columns: File Name, Created, and a Run action button per row.
  - Verify the breadcrumb bar shows "Import / Export > Export History".
  - Click the "Run" button on a row and verify a file download is triggered.
KOD-30100: Map in CSD Custom Fields
KOD-30106: Sync UPC Codes from CSD for ICSV Records
KOD-30113: Delete and Resync new Business Data
KOD-30123: Add Customer App Flavor
KOD-30124: Import Library Files to Shared Drive
KOD-30131: Shared Drive - Ignore Metadata Files
KOD-30135: Pricing Record Sync
KOD-30138: UX for SSO
KOD-30140: Update Error Page
- Tests
- Case 1
  - Verify Error (Not Found) Page.
  - Steps:
  - Open the website.
  - Open a non-existing page.
  - Manually enter a non-existing URL (/content/random-test-page).
  - Verify Not Found page content.
  - Ensure the Not Found (404) page is displayed.
  - Verify mobile version.
- Case 2
  - Verify Reply-To Email Address.
  - Steps:
  - Open the website.
  - Navigate to the error page.
  - Fill out the form.
  - Complete all required fields.
  - Enter a valid email address in the Email field.
  - Submit the form.
  - Verify reply-to address.
  - Open the email screen in the operations portal or check it in the email.
  - Check the Reply-To field in the email details.
  - Ensure the Reply-To address matches the email entered by the user in the form.
KOD-30148: Unify Price Book Generation Flow (Operations Portal)
- Regression Tests
- Case 1
  - Navigate to a company detail page and click the Catalog tab.
  - Select a category from the catalog tree.
  - Click the Actions dropdown.
  - Verify Download Price List is not present in the menu.
  - Verify Generate Price Book , Edit , and Delete options are still present.
  - Verify that create, edit and delete a catalog is working as before.
- Tests
- Case 1
  - Navigate to a company detail page and click the Catalog tab.
  - Select a category from the catalog tree.
  - Click the Actions dropdown and click Generate Price Book.
  - Verify the dialog opens with a description paragraph: "A price book will be generated and an email will be sent once it is ready. Specify recipients below, or leave blank to send to yourself."
  - Verify a Template dropdown, Email text input, and Attach file to email checkbox (unchecked by default) are present.
  - Verify the Company field is not shown (pre-selected from context).
  - Enter an invalid email (e.g. "abc"), click Generate, and verify a snackbar message: "Please enter a valid email address."
  - Clear the email field or enter a valid email, click Generate , and verify the dialog closes with a success snackbar message.
  - Verify you received an email with the generated price book once processing is complete.
- Case 2
  - Navigate to a customer Company group detail page and click the Catalog tab.
  - Select a category from the catalog tree.
  - Click the Actions dropdown and click Generate Price Book.
  - Verify the dialog opens with the description paragraph, template dropdown, Company autocomplete, email input, and attach checkbox.
  - Click Generate without selecting a company and verify a snackbar message: "Please select a company."
  - Search and select a company in the Company autocomplete.
  - Enter an invalid email (e.g. "abc"), click Generate , and verify a snackbar message: "Please enter a valid email address."
  - Clear the email field or enter a valid email, click Generate , and verify the dialog closes with a success snackbar message.
  - Verify you received an email with the generated price book once processing is complete.
KOD-30149: Text Modal Block Updates
- Regression Tests
- Case 1
  - Verify Text Modal Widget Can Be Created Outside a Form.
  - Steps:
  - Navigate to CMS → Pages.
  - Open any existing page or create a new one.
  - Add Text Modal widget without a form.
  - Add the Text Modal widget directly to the page (not inside a form).
  - Configure widget settings.
  - Set Title.
  - Set Description.
  - Configure color, text alignment, and paddings as needed.
  - Verify functionality.
  - Ensure the modal opens correctly.
  - Verify that all configured settings are applied properly.
  - Confirm there are no layout or functional issues.
- Tests
- Case 1
  - Verify Text Modal Widget in Form.
  - Steps:
  - Navigate to CMS → Pages.
  - Open any existing page for testing or create a new one.
  - Add form and text modal widget.
  - Create or edit a form on the page.
  - Add the Text Modal widget inside the form.
  - Place it in any suitable position.
  - Configure widget settings.
  - Set Title.
  - Set Description.
  - Configure color.
  - Configure text alignment.
  - Adjust paddings as needed.
  - Verify functionality.
  - Ensure the modal opens correctly.
  - Verify that the configured title and description are displayed properly.
  - Verify styles (color, alignment, padding) are applied correctly.
  - Ensure there are no layout or functional issues.
KOD-30152: UX for merging guest cart with user cart previous cart permission fix needed
- Regression Tests
- Case 1
  - Make sure that the page loads without any errors when navigating from the header banner, the previous and saved carts are still displayed.
- Tests
- Case 1
  - When navigating to the previous carts page - open the network tab.
  - Go to the following API call: “/api/account/order/search“.
  - We should now be passing customerID to the payload so that only your saved carts are displayed, not all of the saved carts of the company you are under.
KOD-30154: Kodaris - Add Ability to De-Activate a Default System Rule
- Regression Tests
- Case 1
  - Ensure that all fields are editable (Name, Description, Trigger, Active, Script) for user-created interceptors (editable: true).
  - Ensure that saving works correctly for user-created interceptors.
  - Ensure that for the system interceptor (editable: false), the Name, Description, Trigger, and Script fields remain locked for editing.
- Tests
- Case 1
  - Ensure that for the system interceptor, the “Active” checkbox is available for modification.
  - Verify that when the Active status of the system interceptor is changed.
  - Verify that it is possible to save the change in the Active status for the system interceptor and that the change is applied.
  - Verify that after saving the status of the system interceptor, the page displays the updated value and that after reloading the page, it also displays the updated value.
KOD-30157: YouTube embed widget update
- Regression Tests
- Case 1
  - Ensure that the “CM: YouTube Embed” block correctly embeds videos with URLs in the format
- Tests
- Case 1
  - Make sure that the “CM: YouTube Embed” block correctly embeds videos with share links in the format
  - Make sure that after saving the page, the video from the share link is displayed correctly and can be played.
KOD-30158: Product Configurator Limited Variants
KOD-30165: Make Register Success Text Translatable
KOD-30171: Update on AWS QuickSight
KOD-30173: Stock Wording Change
- Tests
- Case 1
  - Verify Inventory Title Text on Product Detail Page
  - Steps:
  - Log in and open any product from any category.
  - Open Product Detail page.
  - Verify that the inventory title text "Stock Amount" is displayed correctly.
KOD-30177: Location's Developer Fields screen permissions fix
- Tests
- Case 1
  - For this test, create an employee with only wareHouseView and wareHouseSettingView (or wareHouseSettingEdit) roles.
  - Log in with that employee and make sure you can access the Locations - Developer Fields screen.
  - If the edit role was assigned, make sure you can also create, edit and delete items from the grid.
KOD-30182: Add HTTP timeouts
KOD-30186: Shared Drive Updates
- Regression Tests
- Case 1
  - Check that the Shared Drive screen still works as expected without issues.
- Tests
- Case 1
  - Check that now when you upload a folder to the Shared Drive screen, a folder record is created as well as the files.
  - The files in the folder should now have their actual name, e.g. screenshot1 instead of the folder name and file name, e.g. MyFolder_screenshot1.
  - The files in the folder should have the Parent Internal File ID field set to the ID of the folder record.
  - The folder name should be set in the Folder field.
KOD-30189: Pull order images from IDM
KOD-30190: Make tariffs taxable
KOD-30194: Check ContentPageLanguage, erpSetting, Icss, Note server side endpoints which moved
KOD-30196: Check host, escalator, escalatorSchedule server side endpoints which moved
KOD-30200: Check asset, country, state server side endpoints which moved
KOD-30202: Check language, template, setting server side endpoints
KOD-30204: Check category lang, company whish list, role server side endpoints which moved
KOD-30205: Check Subscription, SubscriptionList, CustomerSmsNotif, ShippingMethod server side endpoints which moved
KOD-30207: Check content page server side endpoints which moved
KOD-30211: Chat with us Not Always Working
KOD-30216: Add "Products missing required attributes" Column to Categories > Search View
- Regression Tests
- Case 1
  - Open sidebar > Categories.
  - Verify:
  - The Categories search table is displayed.
  - Data is loaded and displayed in the table.
  - Open column configuration.
  - Add a new column.
  - Verify:
  - The new column is displayed in the table.
  - All data is still displayed correctly.
  - Open column configuration again.
  - Remove the added column.
  - Verify:
  - The column is no longer visible.
  - Table displays correctly with default columns.
- Tests
- Case 1
  - Open sidebar > Categories > Search tab.
  - Open column configuration.
  - Find "Products Missing Required Attributes" in the available columns list.
  - Add the column.
  - Verify on the Categories table:
  - The "Products Missing Required Attributes" column is displayed.
  - Hover over the "Products Missing Required Attributes" column header.
  - Verify:
  - The sort arrow appears on the column header.
  - Click on the sort arrow.
  - Verify:
  - The table sorts by this column.
  - Click on the sort arrow again.
  - Verify:
  - The sort order changed (ascending/descending).
  - Apply a filter on the column (e.g., greater than 0).
  - Verify:
  - Filter was applied successfully.
  - Clear the filter.
  - Verify:
  - All categories are displayed again.
  - Remove the column from displayed columns.
  - Verify:
  - The "Products Missing Required Attributes" column is no longer visible in
  - the table.
KOD-30217: Add Custom Fields Tab & Additional Columns on Products > Data View for CSD Fields
KOD-30219: Language Widget Updates
- Regression Tests
- Case 1
  - Go to Pages > Click "Add Page" button > Select Gutenberg > Close default layout.
  - Add a new block "CM: Language Selector".
  - Verify:
  - The language button appears in the editor.
  - Save the page.
  - Open the page in the frontend view.
  - Verify:
  - The language selector button appeared on this page.
  - Click on the language selector button.
  - Verify:
  - The language dropdown opens.
  - Available languages are displayed.
  - Select a different language.
  - Verify:
  - The page reloads with the selected language.
  - The language selector still works correctly.
- Tests
- Case 1
  - Default alignment of Language Selector block.
  - Go to Pages > Click "Add Page" button > Select Gutenberg > Close default layout.
  - Add a new block "CM: Language Selector".
  - Verify:
  - The language button appears aligned to the right side of the block.
- Case 2
  - Change alignment to left.
  - Go to Pages > Click "Add Page" button > Select Gutenberg > Close default layout.
  - Add a new block "CM: Language Selector".
  - Click on the block to select it.
  - Click on the alignment button in the block toolbar (three horizontal lines icon).
  - Select "Align text left".
  - Verify:
  - The language button moves to the left side of the block.
  - The alignment button now shows left alignment as selected.
  - Save the page.
  - Open the page in the frontend view.
  - Verify:
  - The language selector button is positioned on the left side.
- Case 3
  - Change alignment to center.
  - Go to Pages > Click "Add Page" button > Select Gutenberg > Close default layout.
  - Add a new block "CM: Language Selector".
  - Click on the block to select it.
  - Click on the alignment button in the block toolbar.
  - Select "Align text center".
  - Verify:
  - The language button moves to the center of the block.
  - The alignment button now shows center alignment as selected.
  - Save the page.
  - Open the page in the frontend view.
  - Verify:
  - The language selector button is positioned in the center.
- Case 4
  - Change alignment back to right.
  - Go to Pages > Click "Add Page" button > Select Gutenberg > Close default layout.
  - Add a new block "CM: Language Selector".
  - Click on the block to select it.
  - Click on the alignment button in the block toolbar.
  - Select "Align text right".
  - Verify:
  - The language button moves back to the right side.
  - The alignment button shows right alignment as selected .
KOD-30221: Text, Fuel Charge Updates
- Regression Tests
- Case 1
  - Ensure that the company is successfully created when submitting the spcu/register-new-customer form.
  - Ensure that the company is successfully saved in the ERP without any errors.
- Tests
- Case 1
  - Verify that when saving a company in ERP, all text fields are written in UPPERCASE (name, addr1, addr2, city, countrycd, pricetype, pocontctnm), except for the email field, which should retain its original case.
  - Ensure that the Fuel Charge fields are mapped correctly: taxJurisdiction3 → addonnum4, taxJurisdiction4 → addonnum5 (previously addonnum8).
  - Check the values on the events screen and also check the synchronization status to ensure there are no errors (example: syncCompanies_*.ndjson).
KOD-30222: Add POST: /api/system/category/{categoryID}/categoryFacetGroup to server side for assigning filter categories for categories
KOD-30224: UX for Custom Fields Tab & Additional Columns on Products Data Grid
- Tests
- Case 1
  - Make sure that a new “Custom Fields” tab has appeared on the Product > Detail page between the Details and SKUs tabs.
  - Make sure that the “Custom Fields” tab is only displayed if the integrationIndexedProductFields setting contains value.
  - Make sure that the fields in the Custom Fields form correspond to the setting: settingCode - value, settingName - label.
  - Make sure that the “Custom Fields” tab is not displayed if the integrationIndexedProductFields setting is empty.
  - Ensure that the Custom Fields columns appear on the Products > Data page.
  - Ensure that the Custom Fields columns on Products > Data match the integrationIndexedProductFields setting.
  - Ensure that the Custom Fields columns on Products > Data are read-only.
  - Make sure that when you change the values in the Custom Fields form, the data is saved in Developer Fields.
KOD-30225: Add api/system/pricingType endpoints to server side
KOD-30231: Add showing importers list in the Category -> “Filter Categories” tab
- Regression Tests
- Case 1
  - Go to PIM → Categories → Category → Filter Categories.
  - Open File dropdown, check that everything looks good there and we don’t have any broken UI.
- Tests
- Case 1
  - Go to Development → Importers.
  - Choose a few random importers and change their entity type to CategoryFacetGroup by just pasting this entity name into the cell.
  - Go to PIM → Categories → Category → Filter Categories.
  - Open File → Import. Check that appropriate importers appeared.
KOD-30235: Implementation - Addons