Company Code Field Now Filterable and Sortable in Locations Screen
The Company Code field in the Locations screen has been enhanced to support sorting and filtering operations. Users can now access this functionality by making the Company Code column visible through the "Show/Hide Columns" button, then utilizing the sort arrows to arrange locations in ascending or descending order based on company codes.
The new filtering capability offers multiple options to refine location data. Users can filter by exact matches using "equals," identify records with or without company codes via "empty" and "not empty" filters, or use partial matching with options like "starts with." These tools streamline the management of location data, allowing users to quickly isolate and analyze locations associated with specific companies without extensive manual searching.
This enhancement is available now in the current release. For a step-by-step demonstration of how to use these new capabilities, please refer to our tutorial video on the feature.
https://youtu.be/JsVBe77OieI
Customer Flag and Flag fields now available in the Tickets screen
The Operations Portal has been enhanced with two new customizable flag fields that help teams track ticket status and important customer notes. Both fields appear as configurable dropdown menus in the Tickets grid and on the Ticket Details page, allowing users to quickly categorize and prioritize work.
To use these fields, simply enable them through the Show/Hide Columns button on the Tickets screen. Values for both dropdown menus can be customized in the Settings area by editing the customerTicketFlags and ticketFlags settings with comma-separated options like "Follow-up Required," "High Priority," or "Ready for QA." Once configured, users can assign values by double-clicking cells in either column.
These new flag fields provide teams with visual indicators for tracking ticket status and highlighting customer-specific requirements without requiring additional notes fields or custom workflows.
The Customer Flag and Flag fields are now available in the Operations Portal. For a visual walkthrough of how to configure and use these new fields, please refer to our demonstration video.
https://youtu.be/hLv8N1-59BQ
New Ticket Grouping Feature
The Ticket Details screen now includes a customizable "Ticket Group" field to help categorize tickets. This addition allows teams to organize tickets based on specific types - for example Commerce, Customer Portal, Operations Portal, or any custom categories relevant to your organization's workflow.
Setting up the feature is straightforward—administrators can define available grouping options through the "ticketGroups" setting, where comma-separated values establish the dropdown choices. Once configured, users can assign a group to any ticket and filter the ticket grid by these categories.
This feature is available now in the latest release. For a visual walkthrough of the setup and usage process, please refer to our instructional video demonstrating the feature in action.
https://youtu.be/GaP2deSF2Qs
Sidebar Feature for Quote Items Screen
The Quotes module has been enhanced with a new sidebar for the Items screen, allowing users to view totals and analysis information without navigating away from the items view. This feature mirrors functionality already available in Cash Quotes.
The sidebar displays key data including subtotal, shipping, extra charges, and total amounts in the Totals section. Users can make changes to any values and instantly recalculate all figures using the "Calculate All" button. Additionally, the Analysis section shows cost, total, and margin metrics with a visual color-coded chart for quick assessment.
For a detailed walkthrough of this feature, please refer to our demonstration video showing how to access and use the sidebar from the Quotes > Items screen.
https://youtu.be/63mSKpQgTvo
Tickets
KOD-25046: Create Application based on customer form - Platform
KOD-25531: Customer Account Activation from New Account in CSD
KOD-25930: Prioritize drop ship items if the entire shipped part of the order can be delivered from there
KOD-26060: Update Sales Rep Filter on Opportunities Screen
Tests
Case 1
Navigate to the Opportunities screen.
Locate the Sales Reps column.
Apply a filter to the Sales Reps column. The list of opportunities should be filtered correctly based on the selected Sales Rep.
KOD-26088: Implementation - Revisions
KOD-26087: Bulk order entry for multiple locations
Regression Tests
Case 1
Make sure that the website loads without any errors. Please also check if the Contact Us form works without any errors and the email is being sent , because updates were made to the API script that handles forms.
KOD-26137: Move "Shipping date" field to Separate Header Created From Ticket 22058
Regression Tests
Case 1
For this regression test, you need to log in the commerce site, add an item to the cart and follow the checkout process until you get to the Delivery & Payment tab.
Make sure that changing the shipping date updates the cart successfully and that you are able to place an order.
The shipping date you select should be reflected and should appear in the operations portal as well.
Tests
Case 1
For this test, you need to log in the commerce site, add an item to the cart and follow the checkout process until you get to the Delivery & Payment tab.
The “Select a shipping option” field should be inside its own accordion now.
Make sure the title is translated to French properly.
KOD-26138: Make $0/OAN Items only Available via Request a Quote Created From Ticket 24426
KOD-26321: Kodaris.com – Podcast Marketing Page
Regression Tests
Case 1
Open a page where this section is used with Gutenberg.
Verify that the styles are not broken and everything is displayed correctly.
Tests
Case 1
Open the mockup
Verify that the page matches the design in the mockup.
Verify that all Listen & Follow Now links are clickable.
Check the Recent Episodes section:
All cards should be expandable/collapsible on (+)(-).
The user should be able to navigate to the episode detail page by clicking on the image or the Open Episode button.
Check the Meet the Hosts section:
Design should match the mockup.
The LinkedIn link should be active.
Check the Subscribe for Updates section:
The user should be able to successfully subscribe.
Ensure that a network request is triggered on button click.
Click on any episode card and navigate to the detailed view.
Verify the Episode Detail Page:
It should match the mockup.
Check the Breadcrumbs:
Ensure correct structure and navigation.
Verify again that all Listen links are clickable.
The detail page should contain:
A video,
Description,
Transcript.
Re-check the Subscribe for Updates section on the detail page.
Case 2
Navigate to the Operations Portal → Pages → Add Page → Gutenberg.
Locate and select the CM: Parse Transcript file.
Upload a valid .txt file containing transcript text (use a sample from the comments section).
Verify the following:
The transcript text is correctly displayed.
The structure matches the uploaded .txt file.
Apply custom styles to the transcript.
Confirm that styles are rendered properly in the editor.
Verify that the transcript appears on the page as expected and matches the original .txt file content.
Invalid File Type Handling.
Attempt to upload a file with an unsupported format.
An appropriate error message is shown (“An error occurred while processing the file: ${error}. Please check the format.t”).
Incorrect .txt File Format Handling.
Upload a .txt file with incorrect or malformed formatting.
Should be added as plain text without structured formatting.
KOD-26337: Custom columns in Customer Portal Error & How to Delete Created From Ticket 25987
Regression Tests
Case 1
Log in to the customer portal.
Confirm pages are loaded properly.
Add some columns to the views.
Apply filters.
Create a new product for the view.
Confirm the new column is displayed only on the specific grid.
Tests
Case 1
Confirm you can add and remove custom columns.
KOD-26359: Auto sourcing shipping fees by rules and line item
KOD-26387: Implementation - Demo Prep
KOD-26421: Retail Price Import
KOD-26447: ERP to Short Description Update
KOD-26453: Document the procedure
KOD-26467: Fix display of pricing in cart for request quote items
KOD-26468: Image size (lg) when clicking into product on mobile app
KOD-26491: Add prompts to encourage users to register
Regression Tests
Case 1
For this regression test, we will go to the commerce site as a guest user.
With an empty cart, we will click on the Cart icon.
We should be redirected to spcu/cart-login, which should be the regular “Your shopping cart is currently empty” page.
We should repeat the steps as a logged in user.
We should be redirected to spcu/cart where we should see the same page as before.
Tests
Case 1
For this test, we will go to the commerce site as a guest user.
We will add an item to the cart and then we will click on the Cart icon.
Make sure the following setting is enabled: enableGuestCheckout.
We should be redirected to spcu/cart-login.
This time, we should see a page that prompts us to log in.
Test the functionality of this page:
Signing In.
Checkout as Guest should take you to spcu/cart, where you should see your cart items.
Register should take you to /content/register.
Forgot Password? Should take you to account-retrieval.
Case 2
For this test, we will go to the commerce site as a guest user.
We will go to a Product List page and add an item to the cart.
We should see a toast with a message and two buttons:
Got it: closes the toast.
Login: redirects you to spcu/login.
If you have already seen the toast once in that session, adding more items to the cart won’t show it again.
Also, adding an item to the cart as a logged in user won’t ever display the toast.
KOD-26507: Ticket #204 - Reduce font weight
KOD-26513: Master order/budgets - UX to enable customer adding line items
Regression Tests
Case 1
Check if you can still edit labels for a budget.
Tests
Case 1
In the customer portal go to Location → pick Location → go to budget tab → in the right corner press “Add Item“.
Select product from autocomplete list, fill quantity (required) and other information (not required). Add product.
Check if you are available to add the same product twice. (Not possible based on API call).
KOD-26522: New Query Script Architecture
KOD-26579: Support data From Kodaris Orders
KOD-26582: Technical documents update
Regression Tests
Case 1
Confirm that the product page loads without errors and that you can open the Resources section.
Tests
Case 1
Confirm that if a product has a file and its extra5 == null, then the file will be shown for all languages on the site.
If extra5 == [some language], then the file will only be shown for that specific language.
KOD-26592: Operations Portal - Fix sorts on screens 2
KOD-26615: Add Ticket Group field to Tickets - UX
KOD-26621: Automated order identification and placed from and by settings
KOD-26641: Setting home content tiles to a max of 4 per row
KOD-26644: Option to Move Attributes to Center of Screen Created From Ticket 28294
Regression Tests
Case 1
Make sure that filters are applied and search results are updated.
Make sure that the functionality related to filters also works in the mobile version.
Tests
Case 1
Open the website.
Navigate to any category.
Click on “Switch to horizontal layout”.
Verify that filtering functions correctly.
Verify that scrolling works as expected.
Click on “Switch to vertical layout”.
Make sure that the switch icon turns green when in vertical mode.
Verify that filtering functions correctly.
Test the behavior across different screen sizes.
Case 2
Open the website.
Navigate to any category.
Click on “Switch to horizontal layout”.
Verify that 4 products are displayed per row.
Check different screen sizes.
Click on “Switch to vertical layout”.
Verify that 3 products are displayed per row.
Check different screen sizes.
Case 3
You also need to make sure the Switch Layout functionality looks okay on different screen views (grid, list and catalog).
KOD-26646: Lead times update
Regression Tests
Case 1
Make sure on following pages:
category grid/list view
product detail
checkout tab 1 and 3
For products which leadTimeInDays + 2 is ≤ 5 Days .
Usually ships within 5 days are displayed.
leadTimeInDays + 2is > 5 Days & ≤ 7 Days .
Usually ships within 7 days are displayed.
leadTimeInDays + 2 is > 7 Days & ≤ 10 Days -
Usually ships within 10 days are displayed.
Tests
Case 1
In the same places as from the regression Case 1:
Make sure if leadTimeInDays + 2is more than 10.
Anticipated shipping time 10+ days is not displayed.
Case 2
Find product which leadTimeInDays is > 10 Days & ≤ 21 Days.
Make sure in all places this product is displayed.
Usually ships in 2 - 3 weeks.
Case 3
Find product which leadTimeInDays is > 21 Days & ≤ 42 Days.
Make sure in all places this product is displayed.
Usually ships in 4 - 6 weeks.
Case 4
Find product which leadTimeInDays is > 42 Days.
Make sure in all places this product is displayed:
Ships in 6+ weeks.
KOD-26659: Order Automation Order Confirmation Email Template
Tests
Case 1
Go to Orders.
Select any Order.
Click on the Email Order icon.
Choose the wrappedAutomatedOrderCustomerEmail-EJS template.
Send it to your own email address and verify that:
All buttons and links work correctly.
The design matches the one attached to the ticket.
KOD-26677: Populate Address Line 2 upon order submission
KOD-26682: Look at the Sidebar on Contract Quotes.
Regression Tests
Case 1
Verify that the Discount Sidebar is displayed.
Check that the styles and appearance of the Discount Sidebar have not changed.
Tests
Case 1
Open the Operations Portal.
Navigate to the Quotes screen.
Open any quote.
Go to the Items tab.
Check that the Show Sidebar button is visible.
Click the button and make sure the sidebar appears and looks the same as on the Cash Quotes screen.
Change any amount.
Click Calculate All.
Verify that the calculation works correctly.
Verify that the sidebar remains open when switching between tabs, as long as the user hasn’t closed it.
Verify that the sidebar remains closed when switching between tabs, if the user closed it earlier.
KOD-26688: Interceptor For Customer Side Tickets Created From Ticket 28391
KOD-26700: Parser request From Ticket 28481
KOD-26716: Auto-set shipping method based on the ship-to information
Tests
Case 1
For this case, we will place an order (commerce site or operations portal is fine).
Make sure you select a valid Ship To option as One Time Only and Add New Ship To Address won’t work for this test case (will test on Case 2).
The companyAddress (ship-to) selected for this order should have a type.
When we push the order to the ERP, we should see that type passed as the shipVia of that order.
Case 2
For this case, we will place another order.
The companyAddress selected for this order should NOT have a type OR it should be “-9997” or “-9999” (for One Time Only and Add New Ship To).
The company selected for this order should have a defaultShipViaCode.
When we push the order to the ERP, we should see that defaultShipViaCode passed as the shipVia of that order.
Case 3
For this case, we will place another order.
The companyAddress should not have a type and the company should not have a defaultShipViaCode selected.
When we push the order to the ERP, we should see that the value passed as the shipVia of that order should have been defaulted to “UPS”.
KOD-26721: Order / Invoice Documents Tweak Created From Ticket 14911
KOD-26724: Add Company Level Pages UX
Regression Tests
Case 1
Check if the left-side navbar is displayed right.
Tests
Case 1
On the operations portal find the new page Company Pages. Check if the table is displayed right.
Case 2
Try To add new record entering values on the bottom grid (Company ID is required), press Enter to submit. Expected new record to appear.
Case 3
On the top right corner press Add Page->Generic and enter values for name, code and choose company. Press Start. Expected new record to appear.
Case 4
On the top right corner press Add Page->Generic and only choose the company. Press Start. Expected new record to appear, where code is generated automatically and Name==”Untitled”.
Case 5
On the top right corner press Add Page->Generic and enter only name or code and choose company. Press Start. Expected new record to appear, where missing code is generated automatically and missing Name==”Untitled”.
Try both cases.
Case 6
After a few records are created Try filtering for code, name, company ID. Expected table to be filtered.
Case 7
Try to delete some records.
KOD-26732: Shipping Dates on Order and Per line item
KOD-26741: Create layout and record video
KOD-26746: Implementation - In Stock Filter
Regression Tests
Case 1
Confirm that the search page and the product page load without any issues, and that we can see our product information on them.
Tests
Case 1
On the search page or the product page, the "Availability" block is displayed, where:
For each SKU with inStock === true, the line "in Stock" is shown.
If inStock === false, the line "Available" is shown, and when hovered over, a tooltip appears with the message "Available to order".
Confirm that this looks correct:
For both logged-in and logged-out users.
For all views on the search page.
Across different screen widths in the various views.
Case 2
Confirm that on the search page or the product page, if an item is out of stock, we will display the lead time.
KOD-26747: Product ID and product code the same for different part numbers
Regression Tests
Case 1
Confirm the following:
The product list page is available at:
company/productlists/items
customer/productlist/items
ticket/productlist/items
We can see the list of products on that screen, and the page loads without errors.
At the bottom of the page, there is:
An input field where the user can add products.
A select dropdown to choose the filter type for the input.
Tests
Case 1
This logic works identically to the logic on the order items page (but without the quantity field).
We can filter the list of products, and by clicking on a product, it gets added to the list.
If a product in the list has no image, a placeholder is shown (same as in order details > items).
The dropdown options function identically to the ones on the order items page.
KOD-26749: New Customer Parser To Set Up - Created From Ticket 28788
KOD-26750: Add Download Option for Company Catalogs
Regression Tests
Case 1
Store Front
Expected:
The product List page works fine for Categories, Catalogs, and Search.
Case 2
Logged out user.
URL contains confirmEmailToke path param.
Expected:
The user was redirected to the login page.
Case 3
The user tries to reach a page that does not exist/not allowed.
Expected:
An error page is shown.
Case 4
Open any empty company catalog.
Verify that the “Actions” button is not displayed.
Also, verify that if the user lacks at least one of the following permissions: customerCanModify, "companyAdmin" role, allowCustomerPriceBookDownload, the “Actions” button should not be visible.
Tests
Case 1
Open the website.
Open any available Company Catalog page.
Locate the Actions dropdown menu.
Click on the “Export price list” button.
After clicking the button:
A popup appears with the message:
“Exporting the price list is currently in progress. We'll send you an email once it is ready to download.”
Once the export is finished:
The user receives an email containing a link to the exported catalog.
Clicking the “Download” button in the email:
Automatically triggers a popup confirming the file is being prepared or downloaded.
Case 2
Attempt to access the price list via a direct download link. The user is redirected to the login page when trying to download the price list.
Attempt to access the catalog page from which the price list can be downloaded. The user is redirected to the login page when trying to access the catalog page.
KOD-26753: Customer Parser Created From Ticket 28584
KOD-26761: Ship-To Address Line 2 not being sent
KOD-26767: Guest Checkout Updates
KOD-26771: Remove all ecommerce elements from the header
Regression Tests
Case 1
Check that header still looks good.
Tests
Case 1
Check that on header there are no ecommerce elements.
KOD-26772: Bring in other companies of other conos to the system
KOD-26774: Confirm front end UX has punchout updated layout
Regression Tests
Case 1
Сheck that the order is created successfully (by guest | user).
Сheck that the checkout page layout looks correct.
Сheck that there are no errors in the console while on the checkout page.
Tests
Case 1
Check that when a guest logs in, the “Pay with Punchout” section is not displayed on the checkout page.
Check that when a user logs in and cartService.isPunchOut() is enabled, the “Pay with Punchout” section appears on the checkout page.
Check that when clicking on “Place Order” in the “Pay with Punchout” section, a request is sent to /api/account/punchOut/cart.
Check that there are no errors in the console when clicking on “Place Order” in the “Pay with Punchout” section.
KOD-26776: Confirm front end UX has punchout updated layout
Regression Tests
Case 1
Сheck that the order is created successfully (by guest | user).
Сheck that the checkout page layout looks correct.
Сheck that there are no errors in the console while on the checkout page.
Tests
Case 1
Check that when a guest logs in, the “Pay with Punchout” section is not displayed on the checkout page.
Check that when a user logs in and cartService.isPunchOut() is enabled, the “Pay with Punchout” section appears on the checkout page.
Check that when clicking on “Place Order” in the “Pay with Punchout” section, a request is sent to /api/account/punchOut/cart.
Check that there are no errors in the console when clicking on “Place Order” in the “Pay with Punchout” section.
KOD-26780: Implementation - Spin Up System
KOD-26783: Update base templates with punchout default setup and function
Regression Tests
Case 1
Сheck that the order is created successfully (by guest | user).
Сheck that the checkout page layout looks correct.
Сheck that there are no errors in the console while on the checkout page.
Tests
Case 1
Check that when a guest logs in, the “Pay with Punchout” section is not displayed on the checkout page.
Check that when a user logs in and cartService.isPunchOut() is enabled, the “Pay with Punchout” section appears on the checkout page.
Check that when clicking on “Place Order” in the “Pay with Punchout” section, a request is sent to /api/account/punchOut/cart.
Check that there are no errors in the console when clicking on “Place Order” in the “Pay with Punchout” section.
KOD-26787: ACH Return Indicators Not Shown in Accounts Receivable
Regression Tests
Case 1
ACH Returns sync.
Processed by the daily job. Returns should be synced and appear at the Accounts Receivable screen.
Tests
Case 1
ACH Returns sync.
The daily job should sync returns going forward.
By default - it looks for transactions for the last 7 days.
To sync older returns - do it manually:
In swagger “Payment Processing API“ - use POST
/api/system/paymentProcessing/syncPaymentsAndReturns endpoint and pass a period in days, e.g. to sync for last 30 days:
{
"startDaysAgo": 30
}
Open the Operations Portal > Development > Logs to see more details of the sync process.
Check if Return records appeared on the Accounts Receivable screen.
KOD-26799: Order parser issue From Ticket 27883
KOD-26804: Customer parser issue From Ticket 27667
KOD-26808: Customer parser issue From Ticket 26093
KOD-26809: Order not Picked Notification
KOD-26811: Update Price Cost Percent Label to Price Cost Unit
Regression Tests
Case 1
Make sure the Inventory Conversions page still loads as well as the details page.
Tests
Case 1
On the inventory conversions screen, the field that used to say Price Cost Percent now should say Price Cost Unit.
Click to add more columns and see in that dropdown that it now says Price Cost Unit and Price Cost Unit 2 instead of Price Cost Percent and Price Cost Percent 2.
Add Price Cost Unit 2 to the grid and notice the column header is correct.
Case 2
Go into the details of one of the conversions and notice the field for Price Cost Percent and Price Cost Percent 2 now say Price Cost Unit and Price Cost Unit 2.
KOD-26812: Install Applications
KOD-26814: Returns not working when pushed to ERP
KOD-26815: Order Automation Created From Ticket 29092
KOD-26822: Gutenberg keyword field erasing data
Regression Tests
Case 1
Check that saving/deleting/editing fields in the Gutenberg editor on the Pages page works correctly.
Tests
Case 1
Check that when filling in the SEO Keywords field in the Gutenberg editor on the Pages page and changing the language from English to French, the field becomes empty.
Check that when filling in the SEO Keywords field in the Gutenberg editor on the Pages page and changing the language from English to French, and then back - the previously specified value remains in the field.
KOD-26823: Investigations on pricing record
KOD-26825: Order - Created From Ticket 25930
KOD-26829: Implementation
KOD-26828: Implementation
KOD-26830: Issue Created From Ticket 27797
KOD-26832: Deleted Line item in CSD on Invoice
KOD-26837: Parser From Ticket 29173
KOD-26839: Make a separate setting for ticket flags
Tests
Case 1
This ticket just involves the creation of the setting: ticketFlags.
Access settings screen and you should find the setting ticketFlags. Update the value with comma-separated values like "abc, def". Save and verify the setting was saved successfully.
KOD-26840: Separate flag and customer flag data for dropdown
Regression Tests
Case 1
Please test that we still can open and see data on all screens below:
Company address → tickets
Order → tickets
Quote → tickets
Ticket detail
Ticket grid tables
Ticket templates grid tables
Case 2
Please test on all screens listed above we have customer flag as an available column, and it gets data from customerTicketFlags setting.
KOD-26852: Update Kodaris Base inforCSDSFOEOrderTotLoadV4 interceptors
KOD-26857: Content changes - French version
KOD-26872: Add UX for Query Scripts
Tests
Case 1
Make sure you can see the new tab Query Scripts.
Make sure it contains the grid with the column which displays the name of the Query Script.
Make sure it is not editable and you are not able to add or delete Query Script.
Click the details button.
Make sure under the Query Script there are 3 buttons: Reset, Save, Run.
Make sure each of them works with no issues.
Make sure on the Editor tab the editor you can see Query Script Content and can edit it.
Make sure you can see Original tab.
On the Original tab should be displayed content of the standard version of the Query Script provided by Kodaris.
Make sure content of the Original Query Script is not editable in the editor.
Make sure you can see the revisions tab between Editor and Original.
Open this tab
Make sure it contains the grid with all Revisions for this particular Query Script.
Revision Date and Source columns should be displayed. Per each revision row 2 buttons should be displayed: restore revision and details button.
By clicking on the details button you should go to the Revision Content Tab, where content of that Query Script Revision version is displayed.
On the near tab Detail you should be able to check Revision Date in readable format and in row format.
Test Restore Revision button by clicking from the Revision content / detail page and from the grid. Make sure each time that you click any of those buttons, you are redirected to the Editor tab of the Query Script you were on and the Query Script content is updated to the revision version that you’ve used to restore.
Case 2
Make sure you can see the new tab Customer Query Scripts.
Make sure it contains the grid with several columns.
Make sure you are able to create new a Customer Query Script by typing file name at the bottom of the grid.
Make sure you are able to delete Customer Query Script records from the grid.
Make sure Customer Query Script records are not editable from the grid.
Click the details button.
Make sure under the Customer Query Script there are 3 buttons: Clear, Save, Run.
Make sure each of them works with no issues.
Make sure on the Editor tab the editor you can see Customer Query Script Content and can edit it.
Make sure you can see the Revisions tab.
Open Revisions tab.
Make sure it contains the grid with all Revisions for this particular Customer Query Script.
Last Modified, Revision Date and Path columns should be displayed. Per each revision row 2 buttons should be displayed: restore revision and details button.
By clicking on the details button you should go to the Revision Content Tab, where content of that Query Script Revision version is displayed.
On the near tab Detail you should be able to check *Revision Date* in readable format and in row format.
Test Restore Revision button by clicking from the Revision content / detail page and from the grid. Make sure each time that you click any of those buttons, you are redirected to the Editor tab of the Query Script you were on and the Query Script content is updated to the revision version that you’ve used to restore.
KOD-26878: Reimport images for internal pages
KOD-26883: Parser request From Ticket 29536
KOD-26884: Spin up system
KOD-26887: Install Applications
KOD-26896: Invoice Item NaN values
KOD-26897: $0 Total Amount - No Items Found Created From Ticket 26810
KOD-26898: QST tax not picked up Created From Ticket 29539
KOD-26899: Tabs Created From Ticket 29458
KOD-26900: Kodaris.com – Update Customers Section
KOD-26909: Spin Up System
KOD-26911: AP: Inv Not Found Created From Ticket 28593
KOD-26912: Remove vertical line from pages
Regression Tests
Case 1
Confirm the navbar is displayed correctly.
Tests
Case 1
For both logged-in and non-logged-in users, there is no horizontal scroll on any screen size (tablet, mobile, desktop).
Case 2
Logged-in users do not see the "My Lists" link in the navbar.
Case 3
Confirm that on the search page in catalog view, there is no 'Units' column displayed.
KOD-26928: Make Company Code field on warehouses filterable
KOD-26933: Kodaris - Add Currency field to the Terminal screen
Regression Tests
Case 1
Make sure the terminals grid displayed with no issues.
You should be able to update different fields from the grid (fields that are not readonly)
You should be able to create new terminal records with no issues.
Case 2
Make sure terminal details screen works with no issues.
You should be able to update multiple fields with no issues.
Tests
Case 1
On the terminals grid make sure there is new column added to the column list: Currency
This column is editable and accepts text values.
This column is not filterable and not sortable.
Make sure you are able to create a new terminal record with currency value.
Make sure you can update existing terminal records with currency value.
Case 2
On the terminal details screen make sure in the Other section you can see Currency field.
Make sure you can update value in this field with no issues from the details screen.
KOD-26943: Banner Slides Reordering in CMS
Regression Tests
Case 1
Сonfirm that you can insert Section 15 into the Gutenberg editor, and a slider with three slides will appear by default.
You can:
Add new slides.
Delete existing slides.
Change the image.
Edit the link (href).
Everything works smoothly and updates in real-time.
Tests
Case 1
When you open a slide’s accordion panel, you’ll also see arrow buttons that allow you to move the slide up or down. When you move a slide:
It swaps places with the slide above or below.
The images and text update correctly for both slides after the move.
