Specify a site when downloading ERP payment files in Multi-Site Mode
You can now specify a site/host when downloading ERP payment files in the Operations Portal. The process for pulling web account payments remains the same; however, with this added feature, you can now select a host using the “Host Code” field before downloading. This field is optional/not required, but it is available should you want to use it if you have multiple websites on the same Kodaris system.
Watch this video to see how to select a host before downloading ERP payment files:
https://youtu.be/3DthkE9AHlU
Unlock a customer’s account after too many login attempts
When a customer is locked out of their account after too many login attempts, you have the ability to manually unlock their account in the Operations Portal. Along with this, you can also view the number of failed login attempts and the date of which their lockout expires.
See how in the video below!
https://youtu.be/POKmuJH_Lu0
Search by product code or product name on the price check and price debug screens
A new toggle button has been added to the Price Check screen and the Price Debug screen so that you can search by the product code or by the product name or keyword. This new feature presents multiple ways to search for products, offering your team more flexibility when using the search functions in the Operations Portal.
Learn how to use this feature by watching the video below!
https://youtu.be/mZkXo-oCwbk
Mobile App
Tickets screen added to the Employee Mobile App
The Tickets screen has been added to the Employee Mobile App! Your team members can now leverage the ticketing features while using their mobile devices. You can view the Tickets screen, perform searches, apply filters, add and edit tickets, and more, just as you would on your desktop.
Try it out for yourself by browsing through the Tickets screen. If you haven’t downloaded the mobile app yet, head to the App Store or Google Play, search “Kodaris Employee Portal”, and download the app with the Kodaris logo. To log in, enter your company’s domain/URL, your username, and your password. Your credentials will be the same as what you use to log into the desktop version.
In the meantime, here are previews of a few of the Tickets screens:
Tickets
KOD-19608: Add new field in purchase order and vendor invoice - UX
Regression Tests
Case 1
For the regression testing, we should check if the functionality of adding new items still works as it’s supposed to in the Vendor Invoice page.
Tests
Case 1
In this test, we need to verify that the new Received column exists in both pages and returns the necessary data when it has it.
KOD-19823: Implementation - Start ERP Syncs
KOD-20340: MaxRecall Integration Connection
KOD-20435: Manual file download lockbox for per division/host
Regression Tests
Case 1
Operations portal → Accounts Receivable → you should still be able to pull the data without any problems and without Host Code value.
Tests
Case 1
Operations portal → Accounts Receivable → you should still be able to pull the data without any problems and with Host Code value.
KOD-20448: Demo Site - show and hide custom item button
Regression Tests
Case 1
Navigate to the commerce portal.
Go to the cart (Login if needed).
Confirm “Request Custom Item” button is displayed on the empty cart.
Click on this button and confirm Request Custom Button dialog displayed.
Add custom item.
Confirm cart displayed this item.
Confirm “Request Custom Item” button is visible for cart with items in it.
Tests
Case 1
Log in to the operations portal.
Navigate to the Products screen.
Find NONSTOCK item.
Open it’s detail page.
Change one value at time:
Code
Active
Display
Go back to cart.
Confirm “Request Custom Item” button is not visible on the cart page for both empty cart and cart with items.
Note: After you’ve changed “code” for the product, move back to the search screen and refresh it.
Once data has changed, you can move to the next step.
Request custom item button is displayed in the non empty cart with changed Code.
KOD-20489: Implementation - Warehouses
KOD-20569: UX update for direct ship order tracking notifications
KOD-20585: Lindstrom daily ship log - Update Drop Ship Orders.
Tests
Case 1
Use the Swagger endpoint (/api/system/integration/lindstrom/syncDropShipOrdersFromFile) and upload a CSV file with the modified values for updating the specified fields. You can monitor the process in the Portal Operation log screen to see real-time updates.
The process will update all rows for a specific order sequentially before moving to the next one. For example, if you have the same order number in the Customer PO field in two different rows (e.g., the first and the last), it will process both records consecutively. This allows you to see all the logs for a specific order before it processes the next one.
Additionally, you should see the file being processed in the System Event screen under 'Lindstrom_SyncDropShipOrders'. If the process fails, another event called 'Lindstrom_SyncDropShipOrdersFailed_{orderNumber}' will appear, where {orderNumber} is the specific order number, such as 'Lindstrom_SyncDropShipOrdersFailed_1050'. These events are uploaded asynchronously, so there might be a delay before they appear on the screen.
This process updates the orderItem and creates/updates OrderShipments (only if Order.externalOrderNumber is not empty) and changes the order status to ‘Shipped’.
After the sync completes, verify the following updates:
New/updated OrderShipments for the externalOrderNumber (in the Order Shipment screen).
orderItem quantityShipped for the order (in Order -> Items -> Shipped column).
orderItem externalProductCode for the order (in Order -> Items -> External Product Code column).
Order last modified date should also be updated.
Case 2
Use the swagger endpoint to download the file and see the sync process. It would be the same than Case 1 except for the file needs to be download.
(when we have the SFTP credentials , this can be used to test the feature instead of waiting for the hourly job)
Case 3
Enable the lindstromIsActive setting
Set the lindstromOrderUpdateFilePath to the desired path.
Define the hour for processing with lindstromOrderUpdateHour (in UTC format).
Then run the hourlyJob (or wait for 1h to be run) and see the operation logs to confirm that the orders are being updated.
After the job completes, check the order status. The order status should be ‘Shipped’ at the very least.
Also, verify that the second time the hourlyIntervalJob starts (Or the following times), lindstrom updates are skipped.
In this case, we need to wait for an hour since the logic will pick the current time and validate if it was already process. To validate this we can have a file with new changes ready to be updated and confirm that the file will not being picked up until next day
KOD-20618: Update Surcharge/Fee Language
Regression Tests
Case 1
Turn on dollarCreditCardFee setting.
Make sure percentageCreditCardFee setting value is empty.
In customer portal Open Invoices screen select Invoice and click Pay selected Invoices.
Make sure in the modal window wording under card number says “convenience fee”.
Case 2
Repeat 1 - 3 steps from Case 1.
Make sure the modal window loaded and displayed with no issues.
Case 3
Turn on dollarCreditCardFee setting.
Make sure percentageCreditCardFee setting value is empty.
In the Operations Portal Companies → Company → Open Invoices screen select Invoice and click Make Payment.
Make sure in the modal window wording under card number says “convenience fee”.
Case 4
Repeat 1 - 3 steps from Case 3.
Make sure the modal window loaded and displayed with no issues.
Tests
Case 1
Check percentageCreditCardFee setting value. Set it’s value to some numeric value and Save.
In Customer Portal Open Invoices screen select Invoice and click Pay selected Invoices.
Make sure in the modal window wording under card number says “surcharge”.
Case 2
Check percentageCreditCardFee setting value. Set it’s value to some numeric value and Save.
In the Operations Portal go to Companies → Company → Open Invoices screen. Select Invoice and click Make Payment.
Make sure in the modal window wording under card number says “surcharge”.
KOD-20691: Customer Lockout message
Tests
Case 1
Navigate to “Customers” tab on the Operations Portal.
Check if there are a field under Authorization that is named “Locked Out Until” with date picker.
Case 2
Lock out a customer account and clear the "Lock Out Until" field. Then, verify if the customer’s account is locked out by attempting to log in.
KOD-20731: Add branding for second cono
Regression Tests
Case 1
Log in to the operations portal.
Navigate to the site and open branding editor.
Change svg light logo.
Refresh the page.
Confirm logo was updated.
Navigate to the media screen on the operations portal.
Confirm there are new record.
Navigate to the settings screen.
Confirm setting storeFaviconSVGLight contains reference to your image.
Tests
Case 1
Log in to the operations portal.
On the customer portal open branding tool.
Update svg icon light/dark.
Open page source code and find in the html source “xml+svg”.
Confirm href value is properly set.
KOD-20767: Content - Convert Content to CMS
KOD-20777: Enable filter chips
Regression Tests
Case 1
Navigate to the product categories section.
Choose any product category from the available options.
Interact with the sorting options (e.g., sort by price, popularity, newest items).
Verify that the products are sorted according to the selected criteria without issues.
Switch between different view variants (e.g., grid view, list view).
Ensure that the products are displayed correctly according to the selected view variant.
From the right panel, select any filters.
Confirm that the product list updates to display products that match the selected filter criteria.
Add products to the cart.
Verify that the products are successfully added to the cart without any issues.
Switch to the mobile view (e.g., using browser developer tools).
Ensure that all functionalities (sorting, view variants, filters, and adding to cart) work correctly in the mobile version.
Verify that the filter chips and overall interface display correctly and do not break or the interface.
Expected Results:
Sorting options should work correctly, sorting products as expected without any errors.
View variants should switch correctly, and products should be displayed according to the selected view without any issues.
Products should be successfully added to the cart.
In the mobile version, all functionalities should work correctly, and the interface should not break or distort.
Tests
Case 1
Choose any product category from the available options.
From the right panel, select any filters.
Check that the filter chips are displayed correctly at the top of the product list.
Ensure that the filter chips can be removed by interacting with them.
Confirm that the product list updates to display products that match the selected filter criteria.
Switch to the mobile view (e.g., using browser developer tools).
Ensure that all filter chips are displayed correctly on the mobile version.
Verify that the filter chips do not break the interface.
Expected Results:
Filter chips should be displayed correctly at the top of the product list.
Filter chips should be removable.
The product list should update to display products that match the selected filters.
In the mobile version, all filter chips should be displayed correctly and should not break or distort the interface.
KOD-20780: Enable catalog view
Regression Tests
Case 1
Navigate to the product categories section.
Choose any product category from the available options.
Check that the header is present above the product listings.
Ensure that the header contains sorting options and view variants for the selected category.
Interact with the sorting options (e.g., sort by price).
Verify that the products are sorted according to the selected criteria without issues.
Switch between different view variants (e.g., grid view, list view).
Ensure that the products are displayed correctly according to the selected view variant.
Expected Results:
The header containing sorting options and view variants should be present and correctly displayed for any selected product category.
Sorting options should work correctly, sorting products as expected without any errors.
View variants should switch correctly, and products should be displayed according to the selected view without any issues.
Tests
Case 1
Navigate to the product categories section.
Choose any product category from the available options.
Verify the presence of the header containing sorting options and view variants for the selected category.
Ensure that the sorting options and view variants are displayed correctly.
Click on the 'Catalog' button.
Confirm that the Catalog view is displayed correctly.
Expected Results:
Clicking on the 'Catalog' button should display the Catalog view without any issues.
KOD-20781: Direct Ship Order Status Synced
Regression Tests
Case 1
If an order is not a direct order (check the field order.extra1) and has a status of "Received" or "Web Entered", then the order should be eligible for release to ERP.
Tests
Case 1
If the order is a “Direct Order” (check the field extra1), then regardless of the order.status, the releaseStatus field should be “Awaiting Release”.
KOD-20791: GuestCheckoutEnabled setting
KOD-20792: Kodaris demo site - add redirection to sign in page
Regression Tests
Case 1
Navigate to any product category that displays a list of products (test on list, grid, and catalog views).
Select any product from the category view.
Click on the “Add to cart” button for the selected product.
Ensure the product is added to the cart and the user can proceed to the Cart page.
Select any product to view its details (detail page).
Click on the “Add to cart” button on the detail page.
Ensure the product is added to the cart and the user can proceed to the Cart page.
Click on the “Quick Order” button.
Add any product through the quick order feature.
Click on the “Add to cart” button.
Ensure the product is added to the cart and the user can proceed to the Cart page.
Expected Results for Logged-in User:
Should be able to add products to the cart and proceed to the My Cart page, including through the quick order feature.
Tests
Case 1
Navigate to any product category that displays a list of products (test on list, grid, and catalog views).
Select any product from the category view.
Click on the “Add to cart” button for the selected product.
Check if the user is redirected to the login page.
Select any product to view its details (detail page).
Click on the “Add to cart” button on the detail page.
Ensure the user is redirected to the login page.
Click on the “Quick Order +” button.
Add any product through the quick order feature.
Click on the “Add to cart” button.
Ensure the user is redirected to the login page.
Click on the “Quick Order +” button.
Click on the “Add more rows” link.
Navigate to the Quick Order Page.
Click on the “Add to Quote" button.
Ensure the user is redirected to the login page.
Expected Results for Guest User:
Should be redirected to the login page upon clicking “Add to cart” in both category view, detail page and through the quick order feature.
KOD-20797: Create server side import/export for Search Rule table
Ensure that the addition of data-uw-ignore-translate="true" to the Manufacturer section div does not affect existing features and that all components with code changes are functioning and displaying correctly.
Tests
Case 1
Navigate to the Product Search Page.
Open the product search page where the Manufacturer section is displayed.
Click on the UserWay widget icon with live site translation to open the accessibility menu.
Select the option to change the language from English to French (or another language) using the UserWay widget.
Check the Manufacturer section to ensure that the brand names are not translated.
Expected Results:
The brand names in the Manufacturer section should remain in their original language and not be translated.
KOD-20891: Translator Widget - Home Page Multilingual Support
Regression Tests
Case 1
Log into the operations portal and go to CMS → Menus.
Make sure customizer still loads and everything in the home content tiles section works as before.
Tests
Case 1
Open the Home CSS section of the customizer → in the text box add some classes/css that will overwrite the ones that are currently there → Click Activate and Publish and notice the page is updated with those changes.
Case 2
Open the Home Content Tiles section → on any of the images, add text in the Image Title → click activate and publish → notice the new text is located on the picture it was associated with.
KOD-20898: Configure countries and states
KOD-20904: Fix Saved Lists page mobile responsive
Regression Tests
Case 1
Navigate to the “Saved Lists” page.
Click on “Add saved list”.
Enter a name with more than 100 characters.
Enter a lengthy description.
Add a product to the new Shared List.
Return to the “Saved Lists” page.
Verify the display of this content on a desktop-sized screen.
Tests
Case 1
Navigate to Saved Lists.
Click on the “Saved Lists” link in the navigation menu.
Open the browser’s developer tools.
Switch to mobile view (choose a popular mobile device from the device toolbar).
Refresh the page to ensure the mobile view is properly applied.
On the Saved Lists page, locate the “Shared Lists” table.
Click on “Add saved list”.
Enter a name with more than 100 characters.
Enter a lengthy description.
Add a product to the new Shared List.
Return to the “Saved Lists” page.
Verify the display of this content on a mobile-sized screen.
On the Saved Lists page, locate the “Shared Lists” table.
Ensure that only the “Name” column and “View” button are visible for each entry.
Repeat the verification for the “My Personal Lists” table.
Expected Results:
The Saved Lists page loads correctly.
In mobile view, all content should fit within the screen without requiring horizontal scrolling.
The “Shared Lists” and “My Personal Lists” tables should only display the “Name” column and “View” button for each list entry.
Case 2
Navigate to Saved Lists.
Click on the “Saved Lists” link in the navigation menu.
Click on any catalogue that has more than 50 characters in its name and check the header with the name and breadcrumbs.
Check on different screens from mobile to desktop versions.
Expected Results:
The Catalogue page loads correctly.
In mobile view, all content should fit within the screen without requiring horizontal scrolling.
Three endpoints accept a string as input in the request body and return an encrypted string using the algorithm specified in the endpoint name.
Case 2
Che new server side endpoints:
[POST]:
/api/system/utils/md5Encrypt
/api/system/utils/sha1Encrypt
/api/system/utils/sha256Encrypt
Three endpoints accept a string in the request body and return an encrypted string based on the algorithm specified in the endpoint name.
Script example: var result = scriptServiceUtils.runAPIMethod("post", "/api/system/utils/md5Encrypt", null, //pathParam null, // requestParam "test string" // body app.log(app.toJson(result));
KOD-20915: Customer can't load pricing issue
Tests
Case 1
Log into a customer that doesn’t have a recently ordered catalog → go to any category or search for a product or a catalog (if present)→ notice the page fully loads with the prices.
KOD-20919: Add ticketID to sscEmail to relate emails to Tickets
KOD-20920: Add notificationEmails to sscTicket
Regression Tests
Case 1
Go to Ticket screen in the operations portal and navigate to the main screen/details and update some fields.
Verify no errors appear and the data is saved correctly.
Tests
Case 1
Verify that you can create or update a ticket with the new notificationEmails. This should be tested using Swagger, as there is no UX interface available.
Go to swagger and use the following endpoints to create/update ticket:
Use the POST endpoint (api/system/ticket) to create a ticket.
Use the PUT/PATCH endpoint (api/system/ticket/{ticketID}) to update an existing ticket.
Case 2
Validate you can obtain the new field in the /search endpoint coming from solr. It would be in the Search tab from ‘Ticket’ screen in the operations portal and you can see the request in network tab:
/api/system/ticket/search
KOD-20930: Add and update setting
KOD-20938: Make Shipping Methods Host Compatible
Regression Tests
Case 1
Verify the presence of the new hostCode field when creating or updating a Shipping Method.
Tests
Case 1
Verify the presence of the new hostCode field when creating or updating a Shipping Method.
Use the PATCH endpoint (/api/system/shippingMethod/{shippingMethodID}) to populate the hostCode field.
Use the POST endpoint (/api/system/shippingMethod/list) to check that the hostCode is correctly populated in the list of Shipping Methods.
KOD-20943: Shipping Methods / Shipvias
Regression Tests
Case 1
On the commerce portal add some products to the cart.
Navigate to the cart and move to the delivery and payment tab.
Confirm shipping methods displayed as expected.
Case 2
Log in to the operations portal.
Navigate to the Shipping Methods screen.
Apply changes:
Change method name.
Add new method.
Delete any method.
Confirm these changes were applied on the checkout.
Tests
Case 1
On the operations portal navigate to the Shipping Methods screen.
Change Method Order field.
Navigate to the delivery and payment tab on cart.
Confirm shipping methods' order were updated.
KOD-20945: Add a new field to the payment endpoint
Regression Tests
Case 1
Check api/account/payment/searchTotalAmountToPayForInvoices endpoint working as expected without any errors when applying convenience fee and not.
Tests
Case 1
Check convenienceFeeType field is returned as expected.
KOD-20947: Hide/show catalogs inside header menu via setting
KOD-20954: Price Check / Debug Screen - Search by Code or Not
Regression Tests
Case 1
Ensure that all fields are functioning as expected and verify that the 'Check Prices' button operates correctly on both the Price Check and Price Debug pages. Confirm that it returns the expected data in both scenarios.
Tests
Case 1
To test the new functionality, click on the new toggle button added to the 'Product Code' field. Ensure that the results in the autocomplete field adjust according to the selected status on the button (search by name or by code).
KOD-20959: UX to Add Customer Product Codes Feature
Regression Tests
Case 1
Check product list (both grid and list views) and product detail pages. Make sure they load correctly without errors.
Case 2
As not logged-in user check that you can’t see “Your Part #” on product list (both grid and list views) and detail pages.
Case 3
Add few items with customer product code to cart. Check that cart page loaded with no issues.
Case 4
Place an order with the items from Case 3.
Check this order in the customer portal orders.
Order should be loaded with no issues.
Case 5
Check this order in the Operations Portal.
Generate order email and order pdf.
Both of them should be loaded with no issues
Tests
Case 1
On Product Detail Page:
Check as a logged in customer.
Try adding and editing “Your Part #”.
Case 2
On Product Detail Page check as a logged in customer:
Open the edit dialog for the part number, clicking out, cancel should work fine.
Same with clicking “Save” on the original value.
Case 3
On Category Page check as a logged in customer: both grid and list views.
Try adding and editing “Your Part #”.
It should work correctly.
Case 4
On Category Page check as a logged in customer: both grid and list views.
Open the edit dialog for the part number, clicking out, cancel should work fine.
Same with clicking “Save” on the original value.
Case 5
Customers without ‘companyAdmin’ should not be able to edit ‘Your Part #’.
Case 6
Check the items in the cart to ensure that the customer part number is displayed for items that have it.
Case 7
Place an order with items from case 6.
Check this order in the customer portal. Customer part number should be displayed for items with them.
Case 8
Check this order in the operations portal.
Generate order Email. Customer part number should be displayed for items with them.
Case 14
Check this order in the operations portal.
Generate order PDF. Customer part number should be displayed for items with them.
KOD-20962: Mobile Employee App - Warehouses missing from price check screen
Tests
Case 1
You should be able to search for particular warehouses' name or code.
You should see the same behavior, as currently on the web.
KOD-20974: Implementation - Updates to order templates
Regression Tests
Case 1
Check that the order details, order email, and order pdf still work fine.
Tests
Case 1
On the order details, order email, and order pdf, the top left address should reflect the warehouse address.
KOD-20976: Implementation - 99 Invoice Template
Regression Tests
Case 1
Go to customer portal, open invoices screen.
Open preview of normal invoices, e.g., invoice #'s that end in -00
The preview should appear correctly and look fine.
Try printing as well, this should work fine.
Case 2
Order details in customer portal should still work as well.
Tests
Case 1
Go to customer portal, open invoices screen.
Open preview of 99 invoices, e.g., invoice #'s that end in -99.
The preview should appear correctly.
Try printing as well and this pdf should also look like the mockup.
