The Operations Portal now supports Google Tag Manager integration through two new fields in the Google Analytics screen. Users can add their GTM main script and NoScript snippets directly through the interface, enabling comprehensive web analytics and tracking capabilities.
The integration allows for seamless connection between your Operations Portal and Google Tag Manager, with the main script initializing your GTM container and loading associated tags and triggers. The NoScript component ensures tracking functionality remains available for users with JavaScript disabled, resulting in more complete data collection.
This feature is available now in the current version of the Operations Portal. For a step-by-step demonstration of how to implement Google Tag Manager integration, please refer to our instructional video on YouTube.
https://youtu.be/hNf7jkHTDrk
Tickets
KOD-21764: Update for COD Flow
KOD-21949: Update to Checkout w/ Card
KOD-25115: Link ERP Payments to Order if exists
KOD-25744: Product Configurator Polish
KOD-27213: Showing a percentage value from CSD, not price
KOD-27278: Vendor Invoice Parser Created From Ticket 30314
KOD-27344: Update to the deposit screens when selecting a payment method
KOD-27430: Customer Feedback Form
Regression Tests
Case 1
Check that the header looks correct for both guest and user.
Check that there are no errors in the console.
Check that the product detail page looks good.
Tests
Case 1
Check that there is a “Feedback” button in the header on the right side, both for the guest and for the logged in user.
Check that when you click on the button, the “Your feedback will help us improve” window opens.
Check that all fields except Notes are mandatory and the form will not be sent without filling in the data.
Check that there is a “Feedback” button on the product details page for the user.
Check that when you click on the button, the “Your feedback will help us improve” window opens.
Check that when filling in the fields and clicking Submit, the form is sent, an Email and Ticket are created in the operations portal.
Check that the data in the Email and Ticket match the data entered from the Frontend.
KOD-27451: Prevent return for old orders
Tests
Case 1
Validate when trying to start a return order from the customer side and this was placed before the amount of days specified in the new setting disableReturnOrdersOlderThanDays, this action will not be allowed otherwise yes.
Steps:
Set a value in setting disableReturnOrdersOlderThanDays.
Start a new return order from the customer portal.
If the other order was placed before the current date minus the amount in setting disableReturnOrdersOlderThanDays, the action action will not be allowed otherwise the return order will be started.
NOTE : If the order has the ERP Created date ( extra4 field) set this will be used as the order placement date otherwise it will use the order’s created field.
KOD-27511: Parser request for 2nd layout from Ticket 27562
KOD-27515: Shipping Rules
KOD-27619: CMS Request - Follow-Up: Include Content from One Page in Another Page
KOD-27636: Contact Information Flow to ERP
KOD-27671: Master order/budgets - UX for ability to create budget from quote in customer portal
Regression Tests
Case 1
Go to /locations.
Find any location.
Navigate between the Details , Files , Quote , and Budgets tabs.
Make sure all tabs load properly and there are no navigation issues or broken links.
Case 2
Go to /locations.
Find a location with an existing budget.
Click on the Budgets tab.
Verify the budget data loads properly and shows total spend information.
Test all grid actions like edit budget, add line items, and actions menu.
Case 3
Go to /locations.
Find a location with no existing budget.
Click on the Budgets tab.
Click the Create budget button or option.
Fill in the budget name and amount, then submit.
Verify the budget is created successfully.
Case 4
Go to /locations.
Find a location with no quote.
Verify the Quote tab is not rendered in the navigation.
Tests
Case 1
Go to /locations.
Find a location that has a quote.
Verify the Quote tab appears before the Budget tab in the navigation.
Case 2
Go to /locations.
Find a location that has a quote but no budget.
Click on the Budgets tab.
Verify the Create budget from quote option appears in the dropdown.
Click Create budget from quote and verify it generates the budget successfully.
Case 3
Go to /locations.
Find a location with no quote and no existing budget.
Click on the Budgets tab.
Verify only a simple Create budget button is shown (no dropdown arrow).
Click the button and verify it opens the create budget dialog.
KOD-27716: UX – Financial Accounts Management in the Operations Portal
Regression Tests
Case 1
Check that the companies and company details screens in the operations portal still work as expected without issues.
Also check that you can create a company by going to the companies screen, clicking the Actions button, and choosing Create Company.
Case 2
Check that the Financial Accounts screen in the operations portal still works as expected without issues.
Tests
Case 1
Go to the Companies > Details screen in the operations portal.
There should be a new tab/screen called Financial Accounts.
It should work the same as the global financial accounts screen. Ensure the following works:
Only FI Accounts related to that company are shown.
You can create Fi Accounts.
You can update Fi Accounts.
You can delete Fi Accounts.
Case 2
On the same screen as Case 1, there should be a dropdown option in the header to ' Add Store Credit Account '.
Try creating one, and afterwards, you should be redirected to the Financial Accounts tab on the company with the record created.
Case 3
Go to the financial Accounts screen. There should be a new Actions menu with an option to create a Gift Card Account.
Try it out, enter some information, and check that you can create it successfully without issues and are redirected to the fi account after its created.
Case 4
Go to the global Companies screen. In the actions menu, there should be the option to Create a Consumer Company.
Click the option, fill out the information, and make sure the company is created correctly without issues and you are redirected to it after it was created.
KOD-27729: Add payment ID to system events grid
Regression Tests
Case 1
Navigate to the System Events page.
We can add or hide new columns, view more details, or download the file.
Tests
Case 1
Navigate to the System Events page.
In the top bar, choose Payment ID.
It should be visible in our grid.
We can pin, unpin, or edit this column.
To make sure it works correctly, we can search for the data by the code name 'TerminalTransaction_Failed'.
We can see that the Payment ID is visible.
Clicking the arrow “to top” sorts the data in ascending order, and clicking “to down” sorts it in descending order.
We can also use the filter to search.
We can also view more details, download the file, or go to the details page.
KOD-27728: Add system events to payment details
Regression Tests
Case 1
Navigate to the Accounts Receivable page.
Make sure you can click Search / Data.
Add/hide some new columns to the grid.
Then navigate to the Details screen.
Ensure that everything works correctly.
Tests
Case 1
Navigate to the Accounts Receivable page.
Then navigate to the Details screen.
You should see a System Events option in the Top Menu Bar.
Click on it.
You should see a grid with the System Events.
Make sure you can show/hide the new columns and interact with them.
Case 2
To make sure everything works correctly, we should go to the Data section.
Add the Payment ID column.
Search for the event by ID 1176 (this event has some details).
After that, go to the Detail page.
In the top bar, choose System Events — this will take us to the System Events page.
There, we can see that the grid contains some data from this event. We can add or hide new columns, view more details, or download the file.
KOD-27840: Link in Customer Portal
Regression Tests
Case 1
Check that the HomePage page appears correctly.
Check that there are no errors in the console.
Check that the Customizer page opens correctly in the operations portal.
Check that Customizer functionality is working correctly.
Check that Customize Theme functionality is working correctly.
KOD-27850: Product Exports - Import Category
KOD-27914: Create Kodaris Email Address for Order Automation
KOD-27933: Update buttons on product images slider
Regression Tests
Case 1
Open any product that has more than 3 photos. Page expected to load without any issues.
Tests
Case 1
Check arrows for sliding products. They are bigger, darker and bolder than before.
KOD-27934: Add Customer Part Numbers to Order Templates
Regression Tests
Case 1
Check that the order templates still work as expected.
Order Details (in the customer portal)
Order Email
Order PDF
Tests
Case 1
Check that the Customer Part # is now displayed on all the order templates.
Data comes from the user10 field in the trendCompiledSettings on the order item.
KOD-27948: Order Automation-Ship-To Mapping Enhancement Created From Ticket 35275
KOD-28004: AP-Mapping Issue Created From Ticket 36699
KOD-28021: Create Customer Department Controller
Tests
Case 1
Validate customer side new endpoints are working as expected, see list below:
GET - /api/account/department/{departmentID}
PUT - /api/account/department/{departmentID}
DELETE - /api/account/department/{departmentID}
PATCH - /api/account/department/{departmentID}
POST - /api/account/department
Steps:
From the customer side, go to swagger.
Verify the endpoints under the Customer Department API section are working fine.
KOD-28019: Add parent customer to customer entity
Regression Tests
Case 1
From the Customer Portal side validate that read, add and modify employee operations - from Employees screen - continue working without any error.
Case 2
From the Customer Portal side, validate that read and modify profile data continue working without any error.
Case 3
From the Customer Portal side, validate that read, add and modify customers operations continue working without any error - From customer screen and Companies → Company → Customer screen.
Tests
Case 1
Validate PATCH endpoints /api/account/customer/myAccount and /api/account/customer/{customerID} are properly adding/updating the customer parent parentCustomerID and parentCustomerUserName .
Steps:
From swagger look for the endpoints.
Add the patch payload like the example below.
In the response you must see the new fields parentCustomerID and parentCustomerUserName properly populated
{
"parentCustomerID" : <PARENT_ID>
}
NOTES:
Repeat this exact test for system side PATCH endpoint /api/system/customer/{customerID}
The payload can include either parentCustomerID or parentCustomerUserName (or both, in this case the update will be apply base on parentCustomerUserName )
Case 2
Validate endpoints GETs /api/account/customer/{customerID}, /api/account/customer/myAccount and POST /api/account/customer/search are returning parentCustomerID and parentCustomerUserName
Steps:
From swagger look for the endpoints and execute them.
In the response you must see the new fields parentCustomerID and parentCustomerUserName.
NOTE: Repeat this exact test from system side GET endpoints /api/system/customer/{customerID}, /api/system/customer/search/{customerID}, /api/system/customer/userName/{userName} and POST endpoint /api/system/customer/search.
Case 3
Validate POST endpoint /api/account/customer is creating the customer with parent and populating properly the parentCustomerName field.
Steps:
From swagger look for the endpoint /api/account/customer and execute it including a value for the field parentCustomerID.
In the response you must see the new fields parentCustomerID and parentCustomerUserName properly populated.
NOTE : Repeat this exact test for system side POST endpoints /api/system/customer and /api/system/customer/{companyCode}.
Case 4
Validate PUT endpoints /api/account/customer/{customerID}, /api/account/customer/myAccount are updating properly fields parentCustomerID and parentCustomerUserName .
Steps:
From swagger look for the endpoints and execute them.
Add a PUT payload which includes either parentCustomerID or parentCustomerUserName (or both, in this case the update will be apply based on parentCustomerUserName).
In the response you must see the new fields parentCustomerID and parentCustomerUserName properly populated
NOTE: Repeat this exact test from system side PUT endpoint /api/system/customer/{customerID}
KOD-28036: Getting shipping charges to 'stick' Created From Ticket 36665
KOD-28038: B2B pricing display: show CSD Base Price (ALT PRICE) as strikethrough Created From Ticket 32364
Regression Tests
Case 1
Confirm that the product page loads without any issues, just like the product list page.
Case 2
Confirm that the product page displays the price for guest users if the pricesByCodes endpoint includes calculatedPrice .
Case 3
Confirm that if there’s no price , we show Call for Pricing .
Сase 4
Confirm that prices look correct on mobile devices.
Tests
Case 1
Confirm that for consumer users, we display altPrice, and if it’s not available, then calculatedPrice.
For B2B users, we display calculatedPrice and a strikethrough altPrice (if it exists).
Case 2
Confirm that if productType is R, then + Core Charge is rendered and displayed correctly next to the price.
KOD-28054: COD Payment Form Updates
Tests
Case 1
Check that the address section has been deleted.
Check that the amount field does not contain any special characters or commas, only numbers and a period; two characters can be entered after the period.
KOD-28065: Mapping Products to ICSP
Tests
Case 1
New endpoints available to add products to the ERP or update products in the ERP.
These are:
api/system/product/{productID}/addProductToErp
api/system/product/{productID}/updateProductInErp
Currently, it only works if erpLogicEngine is InforCSD.
KOD-28076: Order Warehouse and Sales Warehouse Created From Ticket 32752
KOD-28081: Update layout to be behind a customer login
KOD-28091: Kodaris - Update Pricing screen
Tests
Case 1
Navigate to the Operations Portal → Pricing screen.
Open pricing detail view.
Verify warehouseApplies autocomplete.
Click into the "warehouseApplies" field.
Start typing characters.
Expected result: Autocomplete shows relevant warehouse options matching the input.
Case 2
Navigate to the Operations Portal → Pricing screen.
Open pricing detail view.
Verify vendorCode field.
Add or change text in the vendorCode field.
Expected result: The field saves the text entered by the user.
Case 3
Navigate to the Operations Portal → Pricing screen.
Open pricing detail view.
Verify Status Synced to ERP field.
Case 4
Navigate to the Operations Portal → Pricing screen.
Open pricing detail view.
Verify Company Applies autocomplete.
Click into the "Company Applies" field.
Start typing characters.
Expected result: Autocomplete shows relevant Company Applies options matching the input.
Verify it on the grid as well.
Case 5
Navigate to the Operations Portal → Pricing screen.
Open pricing detail view.
Verify Product Price ID in summary.
Verify “Need syncing to ERP” field in summary.
Case 6
Navigate to the Operations Portal → Pricing screen.
Open pricing detail view.
Verify behavior when priceLevelCode IS 1
Expected result: The Price Code field becomes a product autocomplete field, suggesting products as the user types.
Verify behavior when priceLevelCode NOT 1
Expected result: The Price Code field allows free text entry without autocomplete.
Case 7
Navigate to the Operations Portal → Pricing screen.
Open pricing detail view.
Compare labels between grid and detail screen.
Case 8
Navigate to the Operations Portal → Pricing screen.
Verify autocomplete for Price Code.
Click into the “Price Code” row in the grid.
Expected result: Autocomplete works with the same logic as on the detailed page.
Verify autocomplete for Company Applies.
Click into the “Company Applies” field in the grid.
Expected result: Autocomplete displays relevant company options matching the input.
Verify autocomplete for Warehouse Applies.
Click into the “Warehouse Applies” field in the grid.
Expected result: Autocomplete displays relevant warehouse options matching the input.
KOD-28096: Add new vendor price record fields to data grid and details tab
Regression Tests
Case 1
Make sure the vendor pricing screen still loads properly.
Tests
Case 1
On the vendor pricing screen, click to add more columns → notice the 4 new options - List Price, Standard Price, Unit Conversion, and UPC Code.
Add all 4 to the grid.
You should not be able to filter or sort on those fields.
KOD-28106: Kodaris - Ability to add google tracking scripts from the operations portal
Tests
Case 1
Open Google Analytics.
Test Google Tag Manager (script and noscript).
Enter any test value in the code editor.
Click the Save button.
Navigate to Settings screen
Verify GTM settings.
Locate the following settings:
Google Tag Manager (script)
Google Tag Manager (noscript)
Expected result: Both settings exist and reflect the updated value saved in the previous step.
KOD-28108: Customer Part # Search Not Working
KOD-28107: Update for Swap PO Number for Invoice Number
KOD-28110: Translation of Catalogs
Regression Tests
Case 1
Open the website.
Log in.
Open Catalogs page.
Verify catalog titles.
Check the displayed catalog names.
Expected result: All catalog titles are displayed correctly in English.
Tests
Case 1
Open the website.
Log in.
Open Catalogs page and change language.
Navigate to the Catalogs page.
Change the site language to French.
Verify catalog titles and descriptions.
Expected result: Catalog titles are correctly translated into French.
Add missing translations.
If any catalog title is not translated, go to the Operations Portal → Messages screen.
Add the missing translation for that catalog name.
Verify updated translation.
Return to the Catalogs page and refresh it.
Expected result: The new translation is displayed correctly.
Verify on the mobile version.
Open the Catalogs page on a mobile device.
Expected result: Translations are displayed correctly in mobile view as well.
Verify translate on the details page.
KOD-28122: Date Not Showing on Invoice Created From Ticket 37404
Regression Tests
Case 1
Confirm that we can open the order detail page in the Customer Portal and confirm that we can view order emails through the Operations Portal.
Tests
Case 1
Confirm that in the templates:
wrappedOrderCSDExtensionCODEmail-EJS
wrappedOrderPickUpEmail-EJS
wrappedOrderHTML-EJS
wrappedOrderEmail-EJS
wrappedOrderPDF-EJS
If we render them in the Send Email modal, they are displayed correctly.
(except for the HTML template, which should be opened in the Customer Portal)
Confirm that if the order status is Invoice or Paid, the invoice date will show the value from the invoicedt setting.
If the status is different, the delivery date will show the value from the reqshipdt setting- and if that setting is missing, it will display the delivery date.
Case 2
Confirm that in this field, the Invoice Date or Delivery Date values are displayed in the MM/DD/YY format.
KOD-28126: Add missing fields to vendor pricing details page
Regression Tests
Case 1
Log in the Operations Portal, and open the Vendor Pricing page.
Open the Details page of an item in the grid.
It should display the following fields:
Sales Markup (string)
Sales Markup Method (string)
Price Level Code (number)
Vendor Price (number)
Each field has a value type (number or string), indicated beside each one on this list.
Edit each one of these fields:
It should only permit values of its corresponding type
It should save the value right after blurring the input
It should keep displaying the value right after its saved
Reload the page:
It should display the saved values in each field.
Tests
Case 1
Log in the Operations Portal, and open the Vendor Pricing page.
Open the Details page of an item in the grid.
It should display these fields under the following sections:
General Info section
Customer Markup (string)
Customer Markup Method (string)
Refer (string)
Cono (number)
Record Type (string)
Status Type (string)
Product Info section
Universal Product Code (string)
Product Code (string)
Product Group (string)
Unit (string)
Units (string)
Unit Conversion (number)
Price Info section
Standard Cost (number)
List Price (number)
Other Info section
User 1 (string)
User 2 (string)
User 3 (string)
User 4 (string)
Each field has a value type (number or string), indicated beside each one on this list.
Edit each one of these fields:
It should only permit values of its corresponding type.
It should save the value right after blurring the input.
It should keep displaying the value right after its saved.
Reload the page:
It should display the saved values in each field.
KOD-28132: Auto-selecting in My Warehouse
KOD-28139: Vendor-PO Matching Error
KOD-28174: "use current location" & display in miles how far a warehouse
Tests
Case 1
Confirm that after clicking “Use current location” , the locations are sorted by proximity, showing the number of miles away.
Confirm that clicking on Current Location adds the ZIP code to the search.
Case 2
Confirm that if we enter a few letters or the full name of a location, the list is sorted by name.
If we enter a location name that doesn’t exist in the list, it will be sorted by distance from the point and show miles away.
Case 3
Confirm that when entering a ZIP code, the locations are sorted by distance, and the number of miles away is displayed next to each location.
Case 4
Confirm that when closing the modal and opening it again, the “miles away” values disappear.
KOD-28178: Return Credit Application on patch endpoint
KOD-28186: Order notes section update - ERP update
KOD-28194: AP Automation - Parser Issues
KOD-28193: Additional changes
Regression Tests
Case 1
Please check that the product details page still looks good.
Case 2
Please check that all three steps of checkout still look good.
Tests
Case 1
For catalog products (which starts with C-) you should see the next text Non Stock - Special Order Please allow extra time for the order to be fulfilled. after pricing.
Case 2
Add some products to the cart, it should be in stock/out of stock products. If the product doesn’t have warehouses or any inventory in these warehouses, that means its out of stock.
If a product has warehouses and inventory levels, that means the product is in stock.
Add a few items to the cart, and Review your products (the first step of checkout) for products you will see in stock/out of stock label.
Case 3
After doing the first step of checkout, move to the next step of checkout. For this test, you should be a guest. Do not fill company field and try to navigate to the next step. Right now, company is not required for guests.
KOD-28201: AP: New Mapping
KOD-28209: Check on 0.00 Line Item in Kodaris
KOD-28212: Install Applications
KOD-28214: Alignment of Spec on Product Page when Spec is too long
Regression Tests
Case 1
Navigate to the platform.
Choose any category in the category navigation.
Select any item and click to open its product page.
Scroll down to the “About this item” section.
Find “Specs” and click on it.
You should see two columns — one for the name and one for the value.
Case 2
Repeat the first step from the previous test case.
Open the Inspect tool (using F12 or go to Settings → More Tools → Developer Tools ).
You should find ‘ Toggle device Toolbar ’
Switch to tablet display,
You should see the same: two columns — one for the name and one for the value.
Case 3
Repeat from the 1st to the 3rd steps from the previous test case.
Switch to mobile display.
In the mobile view, you will see that the information is displayed in a column.
Tests
Case 1
Navigate to the platform.
Using the search, find the 112g item.
Click on it and open its product page.
Scroll to the “About this item” section and click “Specs.”
You should see a long value for “Additional information” and it should be displayed properly in its place and not overlap with its name ( “Additional information” ).
Case 2
Open the Inspect tool (using F12 or go to Settings → More Tools → Developer Tools).
You should find ‘ Toggle device Tollbar ’.
Switch to tablet display.
You should see the same as on the desktop display.
Case 3
Repeat from the 1st and 2nd steps from the previous test case.
Switch to mobile display.
The information should be displayed in a column, in its proper place, with all the correct spacing.
KOD-28216: AP-Establish Dedicated email inbox for AP Created From Ticket 38112
KOD-28217: AP Data Sync Created From Ticket 37928
KOD-28223: AP: Invoice Pull $0 unit price
KOD-28230: Customer System Spin Up
KOD-28229: System Spin Up
KOD-28228: Mark supersede items as Active
KOD-28242: Shipping Methods / Shipvias
KOD-28243: Fix discrepancy handling logic in Orders table
Regression Tests
Case 1
Go to Orders → Orders.
Select order with a few items inside.
Open the “Network” tab in the Developer Tools.
Try to select two items and delete them through the table menu. Delete button located in the header of the table, Edit dropdown.
See that we don’t have any duplicate requests in the network tab.
Case 2
Go to CRM → Cash Quotes → Quote → Items.
Create some new items there.
Open Developer Tools → Network tab.
Select 2 items in one tab and in the Edit dropdown select “Delete Selected Rows”.
See in the Network that we don’t have request duplicates.
KOD-28244: Include Inactive Invoices in Payment History
KOD-28245: Pricing not Matching CSD
KOD-28246: Update Model Search Logic
KOD-28252: Implementation - Addons
KOD-28257: Kodaris - JIRA ticket mapping update
KOD-28259: Add Tracking Numbers to Order Templates
Regression Tests
Case 1
Check that the order details template in the customer portal looks as usual without issues.
Same with the order email and order pdf templates.
Tests
Case 1
Check that if an order has tracking numbers, that the order templates now display them:
Order Details
Order PDF
Order Email
KOD-28260: Default Shipping Same as Billing
Regression Tests
Case 1
Go through the checkout process, everything should work as normal without issues.
Case 2
Check that the Shipping same as billing functionality still works as expected.
Tests
Case 1
On the Addresses checkout tab, the Shipping same as Billing checkbox should be enabled by default and all the info from the billing fields copied over to the delivery fields.
KOD-28262: Follow-up ‘check availability’
Regression Tests
Case 1
Confirm that the product list page and the product detail page load without any issues, and that we can see the price and product information.
Case 2
Confirm that on both the product detail page and the product list page, there should be a “Check Availability” button that opens a modal showing the availability information.
Case 3
Confirm that if you are logged in as a consumer user and have a selected warehouse, there should be no number displayed next to it.
Tests
Case 1
Confirm that if the product appears only in our selected warehouse in the prices by codes endpoint response, the “Check Availability” link for it should still exist.
Case 2
Confirm that when opening the modal by clicking “Check Availability” on the product list page, it displays SKUs specifically for that product.
Case 3
Confirm that if you log in as a customer and open the PDP page of a product, you can see the quantity available in your warehouse.
Confirm that if you are logged in as a customer and your selected warehouse does not have the product in stock, a message should appear saying *“Not available in {name of warehouse} ”*.
Сase 4
Confirm that if you have a selected warehouse, it should also appear in the list of warehouses within the modal.
KOD-28264: Payment Methods Mapping Update
KOD-28266: Remove title in green letters - Duplicates title in green background
KOD-28268: Discontinued Items
Regression Tests
Case 1
Check that category page still looks good both for guest user and logged in users.
Case 2
Check that the product details page still looks good both for guest users and logged in users.
Tests
Case 1
Check that on the categories page if the product is having all sku records with status is X, you will see No Longer Available and no possibility to add to cart, just view the product.
Case 2
Check that on the product details page if the product is having all skus with status X, you will see No Longer Available and won’t see the possibility to add to cart.
KOD-28274: Bring in customer's shipping option from SX.e
Regression Tests
Case 1
Check that cart still working fine, all three steps both for guest and logged in users.
Tests
Case 1
For guest users, no shipping methods should not be preselected.
For logged in users, there are several thing to check.
When a company has defaultShipViaCode populated and shipto under this company has type populated. In this case, the preselected shippind method will be taken from the field type.
When a company has defaultShipViaCode populated OR shipto under this company has type populated. In this case, it will select default from shipto or company.
When a company doesn't have defaultShipViaCode populated and shipto under this company doesn't have type populated. In this case, it won’t have preselected any shipping methods.
KOD-28277: Parser update From Ticket 36677
KOD-28284: New ERPSetting and Product Price Fields
Tests
Case 1
Validate new field priceTypeGroup is now coming in the ERPSettings.
Go to the operations portal.
Go to the ERP Setting screen.
Open the browser dev tools and go to the tab network (and clear it).
Click on the refresh button.
In the response the ERP Settings must have the new field in null (this ticket was just about adding the field).
Case 2
Validate new field priceEngine is now coming in the Pricing records.
Go to the operations portal.
Go to the Pricing screen.
Open the browser dev tools and go to the network tab (and clear it).
Click on the refresh button.
In the response the Pricing records must have the new field in null (this ticket was just about adding the field).
NOTE: repeat this test for both Search and Data tabs.
KOD-28286: Kodaris - Add setting to InforCSD Price Engine screen
Regression Tests
Case 1
Verify that the InforCSD Setup page appears correctly and that the settings can be changed.
When changing a setting, a valid value is set for the setting on the Settings page.
Verify that there are no errors in the console.
Tests
Case 1
Verify that a new setting has been added to the InforCSD Setup page in the Development section:
Enable Initial Price Record Cleanup.
Verify that when changing this setting on the InforCSD Setup page, the setting value changes on the Settings page.
KOD-28287: Implementation - Payment Methods
KOD-28289: Add "/api/system/order/{orderID}/assignOrderToCompany" POST to serverside
KOD-28291: Job Schema Markup for certain CMS Pages
KOD-28299: Implementation - News posts
KOD-28301: Add payments configuration endpoint for CSD payments
KOD-28302: Selected Unit not Sticking & Pricing not Displayed Created From Ticket 38860
KOD-28308: Kodaris.com – Platform Tab Update
KOD-28315: Parser From Ticket 36592
KOD-28317: Technical documents update
KOD-28322: Adjusting h6 margin CSS
Regression Tests
Case 1
Check that the website still loads without issues.
Tests
Case 1
Check that on the page in the ticket description, the padding underneath each brand is less than before, and looks good.
KOD-28325: Content - COD Payment Form Updates
Regression Tests
Case 1
Check that the form layout looks good.
No errors in the console.
Form submission works correctly.
Tests
Case 1
Check that the amount field does not contain any special characters or commas, only numbers and a period; two characters can be entered after the period.
