You can now send and link emails to individual tickets under the Tickets feature in the Operations Portal. By viewing a ticket’s Details page, you will now see a new tab titled “Emails” where all emails relating to the ticket can be found. On this screen, you will be able to see each email and its corresponding “From”, “To”, “Cc”, “Bcc”, “Subject” fields and more. You can also view a preview of the email or click into an email’s Details page to see all available information.
This feature will ultimately keep ticket communication even more organized for your team, making it simple to find all emails related to specific tickets.
See how this feature work in the video below:
https://youtu.be/10FWceu44Ps
Send emails to Subscription Lists
You can now send emails using Subscription Lists in the Operations Portal! If you have lists set up, a new “Send Email” button will be available under each individual list. Once you select the button, you will be able to choose from email templates before sending.
This feature allows you to easily send emails or mass distribute emails to pre-established lists in the Operations Portal, saving you time that it would previously take to manually set up and send mass emails.
Learn more about this feature and how to use it by watching this video:
https://youtu.be/L51dNjCBODo
Lockbox Configuration Screen and Closing G/L Journals
In this release, we've added a new screen where you can easily configure lockbox for your Kodaris system. In addition to setting the lockbox configuration, you can manually trigger the batch out process, and view batch out history.
Additionally, a Closing Journals option has been added to the Lockbox screen in the Operations Portal. If enabled, this feature will automatically close any open G/L Journals tied to customer payments as a part of the day end routine for payment processing, and it will occur during Lock Box processing. This option only applies to Infor CloudSuite Distribution users.
Check out the video below:
https://youtu.be/KPsEB3C2Ijo?feature=shared
Search for multiple values at one time on Search grids
In this release, we’ve added a new search feature that allows you to search for multiple values at one time instead of a single value. The search filter is titled “In” under each column; multiple values can be added by typing a keyword or number and then pressing a comma, space, semicolon, or enter. This feature applies to all Search grids in the Operations Portal and will soon be added to the Data screens.
Check out the new search feature by watching the video below:
https://youtu.be/VFbOn0Hh43E
Tickets
KOD-18487: Run Kodaris Statements
KOD-18954: Demo Site - Base Install updates
KOD-20349: Display disposition
KOD-20424: MFA
KOD-20461: Disable access
KOD-20970: Add ticketID to Email to relate emails to Tickets - UX
Regression Tests
Case 1
Make sure that the email list is working correctly.
Emails Section > list.
Case 2
Make sure that the ticket section is working correctly.
Ticket Section > Pick a ticket.
Tests
Case 1
Emails tab is loading the list correctly.
Tickets Section > Pick a Ticket > scroll horizontally > Go to “Emails“ tab.
Case 2
Read Email correctly on Modal and loading details correctly.
Tickets Section > Pick a Ticket > scroll horizontally > Go to “Emails“ tab > press Eye Icon or arrow.
Case 3
Checking the validity of sending a mail to a specific ticket.
KOD-21003: Create Category Views Dataset for Analysis
KOD-21065: Kodaris - add ready pages to the site for customer use
Regression Tests
Case 1
Check that searching in the product documentation and developer documentation still works fine.
The resulting search page should work/look fine as well with no errors.
Case 2
Try searching for a page that does not have a status of either ‘Published’ or ‘Approved’.
The page should not appear in the dropdown or the search results page.
Tests
Case 1
Try searching for a page with a status of ‘Published’ or ‘Approved’.
It should appear both in the dropdown and the search results page.
Make sure the dropdown looks good as well as the search results page.
KOD-21095: AI PIM Descriptions - Phase 2
KOD-21277: Import images
KOD-21289: Operations Portal - "In" Operation on the Search Grid
Regression Tests
Case 1
Checking if the other filters are working correctly. We are testing the 'true/false - does not exist' filter as an example, as well as the 'greater than or equal to' filter. Additionally, we ensure everything works properly when applying multiple filters and when switching between them.
Tests
Case 1
A new "In" filter has been created, allowing multiple values to be added for filtering in the form of chips, applicable to all search tables.
Case 2
Testing on the Tickets Orders page.
When the user presses a comma, space, semicolon, or enter, a new value should be added. When the selection window for operators is closed and then reopened, all the values we entered before should be present.
KOD-21439: Implementation - Test MaxRecall
KOD-21492: ERP Integration Updates
KOD-21526: Add payload to the event after batchout triggered manually
Regression Tests
Case 1
Confirm that "Pull Payments to ERP" on the /accounts-receivable/search page in the Operations portal works without any errors, and after clicking Submit in the modal, a non-empty file is downloaded.
Tests
Case 1
Click on the "Trigger Batch Out" button on the lockbox page.
Confirm that the modal opens without any errors. Confirm that the helper text in the modal does not overlap the inputs.
Case 2
Click on the "Trigger Batch Out" button on the lockbox page.
Click on the "Submit" button in the modal and confirm that a new modal opens without any errors.
Confirm that the modal contains the file content and that it is not empty.
Case 3
Click on the "Trigger Batch Out" button on the lockbox page.
Click on the "Submit" button in the modal.
Confirm that clicking on the download icon in the modal starts downloading the same file that we see in the modal.
Case 4
Confirm that the file in the modal has the same content as the last event in the history tab (you can view the file content by clicking on the eye icon).
Case 5
Confirm that only batchout events (events with the code EDIFileUploadToERP or EDIFileUploadToERP-ERROR) are present in the history tab table.
KOD-21543: Send Emails to Subscription List
Regression Tests
Case 1
Go to “Subscription Lists” view and check details if everything is working like updating fields, nav.
Tests
Case 1
Go to the Operations Portal → Marketing → Subscriptions.
Create Subscriptions with customer.
Copy code for Subscription List Code.
Go to Subscription Lists under Marketing.
Create record with your subscription list.
Go into details of this list.
Paste code with your subscriptions into “Code” field.
Go to Marketing → Templates.
Create record with templates. Add some body in details. Example: “subscriptionListTest”.
Copy code of the template and go back to “Subscription Lists”.
Click Send Email icon on top of the navbar and paste your template code.
Send Email.
KOD-21630: Associative Products - Choose warehouse to pickup product at
Regression Tests
Case 1
Product detail, grid, list, cart pages should be loaded with no issues.
All existent functionality should persist and be loaded with no issues.
Case 2
The fulfillment section design should be changed according to the task description.
Tests
Case 1
Click on “Shop By Category“ → Tools.
Find the product that has the ‘Pickup’ option available → And click on the store name in the Pickup option.
Make sure that a sidebar with a list of stores appears on the right.
Case 2
In the sidebar that appears, add an item to the cart in another store.
Go to the shopping cart and make sure that the product is added to the cart with the selected store.
Case 3
Find the product that has the ‘Pickup’ option available → And click on the store name in the Pickup option.
In the sidebar that appears, make sure that only those stores that have this product are displayed.
Case 4
Navigate to the shopping cart.
Click on the store name in the Pickup option.
Make sure that the name of the button in the list of each store has changed to “Change in cart“.
KOD-21645: Configure Quoting Templates
KOD-21709: Implementation - Test Multilingual
Regression Tests
Case 1
In the header section find “Account“ and “Register or Sign In“ text.
Confirm this text is displayed properly.
Log in to the site.
Confirm your account name and “Manage Account“ text are displayed.
Tests
Case 1
Log in to the operations portal.
Navigate to the commerce site and confirm there is Customizer Theme button.
Click on this button and on right-hand side panel find “Translation Mode” toggle.
Enter Translation Mode.
On the header section confirm “Account“ and “Register or Sign” are underlined and there no any additional symbols.
Hold Ctrl or Command and click on this text.
Confirm translation popover is displayed properly.
KOD-21725: Unit of Measurement Updates
KOD-21744: Product display tweaks
Regression Tests
Case 1
For the grid view make sure that tiles are responsive and whole page styling is not broken.
Make sure when you’re resizing screen, tiles updates styles accordingly.
Tests
Case 2
Category Grid.
Make sure by default there are 4 tiles displayed in a row (when screen width is more that 1301 px).
KOD-21777: Location Links Issue
KOD-21781: Add noindex to demo site
KOD-21783: Add Vendor Automation UX Tab
Regression Tests
Case 1
For this regression test we will go to Vendors > Select a Vendor > Details tab.
We will test the fields to make sure everything is being saved correctly.
We don’t have to test the fields inside the Automation section for this test.
Tests
Case 1
For this test, we will go to Vendors > Select a vendor > Details tab > Automation section.
We will test the “AP Automated Email Addresses” field.
First, we will make sure that setting doesn’t exist for that vendor by going to Custom Fields.
We will add a couple of emails to the field and reload. You can add new emails by pressing Enter, Comma or clicking away. Everything should be saved accordingly.
We will also try to delete an email that we added and will make sure it was successfully updated as well by reloading the Details tab and the Custom Fields table.
Case 2
For this test, we will go to Vendors > Select a vendor > Details tab > Automation section.
We will test the “Release Automated Invoices to ERP” and the “Use Custom Analysis Parser” fields.
First, we will make sure those settings don't exist for that vendor by going to Custom Fields.
You will see that when those settings don’t exist the default value is “No” or “0” for those fields.
We will then change the value to Yes for both of them and check the changes were applied by reloading the Details tab and the Custom Fields table.
We will change them to No and verify the changes again the same way.
Case 3
For this test, we will go to Vendors > Select a vendor > Details tab > Automation section.
We will test the “Vendor AP Upload Script” field.
First, we will make sure that setting doesn’t exist for that vendor by going to Custom Fields.
We will introduce a value to the field and reload the Details tab to make sure it was successfully updated. We will also check in the Custom Fields grid that the setting was created.
We can also try erasing the content inside the field and reload the page. Setting shouldn’t disappear in the Custom Fields grid but value should be empty now.
KOD-21811: Vendor Screen Cleanup & Direct Ship Configuration
Regression Tests
Case 1
For this regression test, we are going to Vendors.
We are also going to test the Show / Hide Column button in both Search and Data tabs.
Tests
Case 1
For this test, we are going to Vendors > Search.
We are going to check the following changes:
“ID” was renamed to “Vendor ID”.
“MSF” was removed.
“POs” was renamed to “Can Use POs”.
“Note Count” was removed.
“Updated” was renamed to “Last Modified”.
“Number” was removed.
“Vendor Name” was renamed to “Name”.
“Web Location” was renamed to “Default Web Warehouse”.
Default displayed columns are now:
Code, Name, Active, Country, State and City.
Case 2
For this test, we are going to Vendors > Data.
“Location” was renamed to “Warehouse Code”.
Default displayed columns are now:
Code, Name, Active, Country, State and City.
KOD-21818: Add Closing Journals Option to Lockbox Screen in Operations Portal
Regression Tests
Case 1
Open the lockbox page and make sure it loads without any errors.|
Case 2
Confirm that all inputs and selects on the lockbox page are working without errors.
Tests
Case 1
Open the lockbox page.
Confirm that there is a select labeled "Automatically Close Open Journals".
Confirm that this select has two options: "Yes" and "No".
Case 2
Confirm that if the value of the setting closeJournalsWithOrderInsert === 1, then the select value will be "Yes" and if it's 0, the select value will be "No".
Confirm that changing the value of the select also changes the value of the setting.
Case 3
Confirm that changing "Enable Batch Out" from "No" to "Yes" does not change the value of "Automatically Close Open Journals."
Also, confirm that if the setting value does not exist or is not of type number, then after changing "Enable Batch Out" from "No" to "Yes," the value in our select will be set to "No" (0).
Case 4
Сonfirm that if closeJournalsWithOrderInsert setting does not exist, the select should be empty, and if we try to select any option, we should receive an error stating that closeJournalsWithOrderInsert is not found.
KOD-21824: Location Page Updates
Tests
Case 1
Go to Location Page
In the operations portal:
Add new location with “service description” and “company name” in order to display it on the list of locations.
Check if selecting by state and company name is displaying correctly locations.
KOD-21826: Lock Tools panel
Regression Tests
Case 1
Check that the navigation bar is displayed correctly on the page.
Check that the navigation elements are clickable and work correctly.
Tests
Case 1
Check that the navigation bar remains at the top of the page during navigation, its layout is correct.
Check that when scrolling, the navigation bar is on top of other elements.
Check that the navigation bar looks correct in different browsers (Opera, Google, Safari, etc.).
Check that when opening a pop-up window (like Welcome Back!), the navigation bar is on top of it (not overlapping).
Check that the “Quick order” functionality is displayed on the navigation bar.
Check that the “Quick order” functionality works correctly(and look good for desktop/mobile).
KOD-21827: Home Page slider tweak
KOD-21828: Add password limitations to password reset page
Regression Tests
Case 1
Open the reset-password page and confirm that it loads correctly without any errors.
Confirm the same for the account-password page.
Confirm the same for credit-application-password page.
Tests
Case 1
Make sure minimumPasswordLength setting is set to something greater than 0
Go to the password reset page → when entering your password, you should see a check on if you have a password with X amount of characters as well as if they match.
Go to account password page → when entering your password, you should see a check on if you have a password with X amount of characters as well as if they match.
Go to credit application password page → when entering your password, you should see a check on if you have a password with X amount of characters as well as if they match.
Case 2
Make sure customerPasswordRequiresLetterAndNumber setting is set to 1.
Go to the password reset page → when entering your password, you should see a check on if your password has both letters and numbers as well as if they match.
Go to account password page → when entering your password, you should see a check on if your password has both letters and numbers as well as if they match.
Go to credit application password page → when entering your password, you should see a check on if your password has both letters and numbers as well as if they match.
Case 3
Make sure customerPasswordRequiresSpecialCharacter setting has a list of special characters (ie: !@#$%^)
Go to the password reset page → when entering your password, you should see a check on if your password has one of the required special characters as well as if they match.
Go to account password page → when entering your password, you should see a check on if your password has one of the required special characters as well as if they match.
Go to credit application password page → when entering your password, you should see a check on if your password has one of the required special characters as well as if they match.
KOD-21834: Employee mobile app - fix issues
KOD-21848: Implementation - Import companies
KOD-21851: Sort Product Categories
Regression Tests
Case 1
Go to the Operations Portal → Pages → Data.
Choose page where you’ll add CM: Section: Product Categories block and choose parent category that you want to display.
Check if block is displaying on the real page.
Tests
Case 1
Go to the Operations Portal → Pages → Data.
Choose page where you’ll add CM: Section: Product Categories block and choose parent category that you want to display.
In the Operations Portal go to Categories → Data.
Set filter for your parent category page and set sort by order.
Set some order to 0 and some of them to 1.
Wait for data to be updated and check on the page if it’s displayed: first by order and also if it’s displayed alphabetically.
KOD-21857: Employee app - Add a ticket tab under the company details
KOD-21866: Add signature to PDF also created date and geo-coordinates
Regression Tests
Case 1
In the operations portal, go to orders → click into an order → make sure page still loads properly.
Case 2
Generate an internal pdf on an order and keep showPODFiles = false → make sure the template still looks the same as before.
Tests
Case 1
Find an order that has POD files → generate an internal file → change showPODFiles to yes → if there is a signature present, you should see the signature under the remit to section along with the created date and the geo coordinate.
KOD-21869: Standardize logins for mobile apps
KOD-21875: Add Assigned Employees to Vendor Invoice List
Tests
Case 1
check new ability to filter by field: assigneeNames, assigneeIDs, assigneeEmails, assigneeTypes for endpoint:
For assigning employees to vendor you can use endpoint: POST: /api/system/vendorInvoice/{vendorInvoiceID}/employeeAssignment.
KOD-21880: Preview AP Vendor Invoice file on data screen
Regression Tests
Case 1
For this test, we need to go to AP Vendor Invoices > Select an item > Internal Files tab.
The functionality to preview a file should be working as expected with no changes.
Tests
Case 1
For this test, we need to go to AP Vendor Invoices > Data.
First, we will look for an item that has one Internal File of fileType “pdf” and type “VendorInvoiceFileUpload”.
When we click on the Preview Invoice File button, we should see the Dialog being open and the file being displayed.
Case 2
For this test, we need to go to AP Vendor Invoices > Data.
This case will happen if there’s more than one Internal File with fileType “pdf” and type “VendorInvoiceFileUpload”, or if there are other files with different attributes or if there are no files at all.
You should be redirected to the internal-files screen after you click on the Preview Invoice File button.
KOD-21884: Add Filterable Assignee Name/ID to Data tab on AP Vendor Invoice Screen
Regression Tests
Case 1
Operations Portal → AP Vendor Invoices → Data screen.
Expected result: Screen works without any errors.
Tests
Case 1
Operations Portal → AP Vendor Invoices → Data screen.
Expected result: 2 new Columns were added:
Assignee IDs - non filterable/sortable.
Assignee Names - filterable, non-sortable.
KOD-21892: Assignees field update via API to AP Vendor Invoices page
Regression Tests
Case 1
For this regression test, we will go to AP Vendor Invoices > Select an item > Details tab.
We are going to make some changes to the fields.
Everything should be saved correctly.
Tests
Case 1
For this test, we will go to AP Vendor Invoices > Select an item > Details tab.
We are going to click on the Add assignee field. A list of suggestions should be displayed. We are going to choose a couple of assignees and verify they were added using the API and not the Custom field setting.
We are also going to remove them and make sure everything is working properly and that the correct endpoints are being called.
KOD-21895: Add button on the vendor invoice details screen to change the vendor
Regression Tests
Case 1
Go to the operation portal → AR/AP → Vendor AP Invoices → enter details screen for invoice.
Check if options (top-rightcorner is working correctly).
Check if data in details.
Tests
Case 1
Go to the operation portal → AR/AP → Vendor AP Invoices → enter details screen for invoice.
In top right corner select “Vendor Invoice Settings”
Update vendor for current Invoice.
Check if data is updated after page refresh.
KOD-21933: UX to Update Surcharge/Fee Language in Customer Email
Regression Tests
Case 1
Make a payment on an open invoice in the customer portal and make sure that in the customer email sent out, the convenience fee label and amount still look good.
Tests
Case 1
In customer payment email, convenience fee label should now display whether the fee is a surcharge or credit card fee.
if setting ‘dollarCreditCardFee’ is setup, then it should show ‘convenience fee’ as the label. otherwise if ‘percentageCreditCardFee is setup, it should show as a 'surcharge’
KOD-21935: Shop by Store Feature
Regression Tests
Case 1
For this regression test, we will disable the setting enableShopByStore in the operations portal.
We will go through the entire order placement process.
We will add a product to the cart and.
If you are not logged in, you should be prompted to do so.
Then, we will go to checkout and make the payment.
Everything should work properly.
Case 2
For this test, we need to go to the web repo as a guest.
We are going to test the Shop By Store button.
Change the store selection and click save. You should be send to the store.
Tests
Case 1
For this test, we need to go to the web repo as a guest. Make sure geolocation is enabled.
If you click on Use current location you should see that the text field is filled with your current zip code and that the warehouse selection is rearranged to match that.
Case 2
For this test, we need to go to the web repo. We are going to test this as a guest and then as a logged in user.
We are going to check if an user without geolocation is redirected to very first warehouse from list of available warehouses.
Case 3
For this test, we need to go to the web repo and log in.
You will see the Shop By Store button. We will test the “Set as Default Store” button.
Click on that button. You will be send to that store and also if you look at the customer information, the warehouse data you selected was added to the customer object.
If you change the store selected without changing the default store you will be send to that store but the information in the customer object won’t change.
You can also test that the warehouse selected as default now has a text saying “Your Default Store” instead of the button.
Case 4
For this test, we need to go to the web repo and log in.
Make sure the user previously selected a store as default.
If the account has warehouse information, you should be assigned to that warehouse next time you log in.
It’ll be the same if the user has geolocation on or not.
KOD-21942: Planned Delivery / Future Delivery Date - Website
Regression Tests
Case 1
For this test we should be a guest.
We will add an item to the cart and click on My Cart. Then we will Checkout As Guest. We will click Next and fill the fields on step 2. We will click next again.
We will enter the payment information and then we will place the order.
Case 2
For this test we have to be logged in.
We will add an item to the cart and click on My Cart. Then we will click on Next. We are going to select a Shipping Address and fill the fields accordingly.
We are going to test this first choosing Account as the payment method and then entering the correct information.
We should repeat the same steps but changing to Card payment to test that as well.
When we place the order, we should be redirected to the Thank You page and the order should’ve been created.
Case 3
For this test we have to be logged in as a Punchout user.
We will add an item to the cart and go to My Cart. Then we will click on Next. We are going to select a Shipping Address and fill the fields accordingly.
On step 3, we should only see the checkout with punchout option.
When we place the order, you will be redirected to a blank screen, but that is normal.
Tests
Case 1
For this test. you should be logged in as a normal user.
We need to disable this setting on the company record: checkoutDeliveryDateEnabled.
We will add an item to the cart and click on Next. We are going to select a Shipping Address and fill the fields accordingly.
On step 3, we shouldn’t see the new Delivery Options container because the setting is disabled.
We will now place the order and we should be redirected to the Thank You page accordingly.
Case 2
For this test you should be logged in as a normal user.
We need to enable this setting on the company record: checkoutDeliveryDateEnabled.
We will add a not Direct Shipped item to the cart and click on Next. We are going to select a Shipping Address and fill the fields accordingly.
On step 3, we will see the new Delivery Options container.
Now, we will change the selection to Schedule Your Delivery.
After we do that, a calendar control will appear. You will also see that the “Place Order” buttons are disabled for now.
When we click on the calendar control, you will see that the maximum date you can pick is 60 days from today’s date, and the first future date available will be assessed on the longest lead time (from today's date) for the products in the cart.
If you try to manually enter a date outside of the range you will get a message that says “Selected date is out of range” and the buttons will remain disabled.
We will now select a valid date.
You will see that the number of days that appear in the message will update accordingly.
kd.cartService.update will be called after that to update the deliveryDate.
After we do that, you should see the Place Order buttons being enabled now.
We will now place the order and we should be redirected to the Thank You page accordingly.
Case 3
For this test you should be logged in as a Punchout user.
We will repeat the steps of case 2 but now as a Punchout user.
We will place the order and make sure that works fine.
Case 4
For this test you should be logged in as a normal user.
We need to enable this setting on the company record: checkoutDeliveryDateEnabled.
We will add a Direct Shipped item to the cart and click on Next. We are going to select a Shipping Address and fill the fields accordingly.
On step 3, we will see the new Delivery Options container.
We will see that the option to Schedule Your Delivery is disabled and a new message that says “This order includes Direct Ship products. If you want to schedule your delivery, please place those products in the Save for Later section before proceeding.” appeared.
We will now Save For Later the Direct Shipped item. After we do that, we can now select to schedule our delivery.
We should be able to place the order appropriately now without any issues with either of the Delivery Options.
Case 5
For this test, you should be logged in as a normal user.
We need to enable this setting on the company record: checkoutDeliveryDateEnabled.
We will add an item to the cart and click on Next. We are going to select a Shipping Address and fill the fields accordingly.
On step 3, we will see the new Delivery Options container.
Now, we will change the selection to Schedule Your Delivery.
kd.cartService.update will be called after that to update the deliveryDate to the entered date.
We will now change the delivery option back to Standard Delivery.
kd.cartService.update will be called after that to update the deliveryDate to an empty string.
We should be able to place the order appropriately now without any issues. A deliveryDate shouldn’t be added to this order.
KOD-21941: Customizer issue with multilingual
Regression Tests
Case 1
Make sure that you’re able to use customizer. Welcome page widgets are working properly with no issues.
Make sure you’re able to update widgets in multilingual.
Tests
Case 1
Open api/system/contentPage/site-customizer page.
Check defaultLocale setting in operations portal settings. If it’s en-us ->
Make sure in customizer multilingual dropdown there is no English (default).
And when you update home content tiles for English → it is properly reflected for the English version of the site.
Try updating home content tiles for French (Canada) and French (Standard).
Make sure all updates are reflected properly for each language versions of the site.
KOD-21945: Unit in a Box - Website
Regression Tests
Case 1
Log in to the website.
Add some items to the cart and go to step 3 of checkout.
Confirm that if Unit in a box checkbox is not checked and orderdisp on a selected shipto is not s - user can switch the disposition to ship complete and back. If orderdisp on the shipto is s - disposition change should be disabled
also check if the page does not break after any action with disposition.
Tests
Case 1
Unit in a box checkbox should only be available if user chose “selected delivery date“ as shipping method and orderdisp on the shipto is not set to 's'.
If user checks the checkbox - the itemShipmentPreferance field on the order should be updated to ‘Tag and Hold'. User will not be able to select 'Ship Complete’.
When unchecking the checkox - this field should be set to ‘Ship Partial' and the 'Ship Complete’ toggle will be available to change
The 'order summary' should also be updated when switching this on and off.
KOD-21951: Logging in from Dropdown on Mobile doesn't Log Customer in
Tests
Case 1
Open the website.
Open Developer Tools and switch to the mobile version of the site.
Click on “Sign In or Create an Account”.
Fill in the form with your login and password.
Click the “Sign In” button.
Expected Result: The user is successfully logged in.
KOD-21957: Remove Add to list for unsigned in users.
Regression Tests
Case 1
Navigate to the Customer Portal.
Check if you can see products as list view and grid view. Go to any product and check if detail page is displayed as expected.
Case 2
Navigate to the Customer Portal.
Log in and check if you can add any product to list.
Tests
Case 1
Navigate to the customer portal and do not log in.
Verify that you don’t see ‘Add to List' button on Product list both list view and grid view and also on product’s detail page.
Case 2
Navigate to the customer portal and log in.
Verify that you see and use ‘Add to List' button on Product list both list view and grid view and also on product’s detail page.
KOD-21967: Payment issue with adding new payment method
Regression Tests
Case 1
Open the Operations Portal.
Navigate to Companies screen:
Select any company.
Navigate to detailed page.
Go to Open Invoices:
Select an invoice.
Click on the Make Payment button.
Click on + Add a Payment Method.
Fill out the form using test card details provided by the testing environment.
Open the Browser Console:
Ensure there are no errors displayed in the console.
Click Make Payment.
Verify that the payment is processed successfully without any console errors.
Tests
Case 1
Open the Operations Portal.
Navigate to Companies screen:
Select any company.
Navigate to detailed page.
Go to Open Invoices:
Select an invoice.
Click on the Make Payment button.
Click on + Add a Payment Method.
Fill out the form using test card details provided by the testing environment.
Open the Browser Console.
Ensure there are no errors displayed in the console.
Click Make Payment.
Verify that the payment is processed successfully without any console errors.
KOD-21979: Enable Shop By Location Feature
Regression Tests
Case 1
For mobile & desktop logged in and guest users.
Make sure header and overall pages are loaded with no issues.
Make sure all existent functionality is available.
Case 2
Make sure enableShopByStore setting value is set to 0.
Go to the store site.
Make sure there is no Shop by store functionality available on desktop and mobile.
Tests
Case 3
For mobile & desktop as guest & logged in user.
Open any page. Make sure at the to there is Shop by Store button.
Don’t allow to share your location.
Make sure after some time warehouse will be selected for you from the list. The very first option from the list should be selected as warehouse.
Case 4
As guest & logged in user.
Allow site to know your location.
Make sure there would happen warehouse selection. Selected warehouse should be the one, which is located closest to your shared location.
Case 5
For mobile & desktop as guest & logged in user.
Click warehouse or Shop by Store button.
Make sure menu with options appears on the screen.
Make sure you’re able to select warehouse from the list.
Make sure after selection, page is reloaded and after reload your selected warehouse appears within the button.
Case 6
As logged in user:
Open warehouse selection menu.
If you haven’t selected default warehouse before, below each option you should see “Set default store” link. Click on that link on any warehouse.
Make sure after reload wording is updated to “Your default store“.
Check it wia swagger /api/account/customer/myAccount endpoint response.
Case 7
As a guest user:
Make sure you’re not able to Set default store as in Case 5.
KOD-21982: Selective removal of orders on e hold
KOD-21989: Content Site - Display the product quantity in the 'Usually Ships Next Day' filter
Regression Tests
Case 1
Login to your customer account.
Go to hardware.
Check if “Usually Ships Next Day“ is working correctly and not displaying undefined value.
Tests
Case 1
Login to your customer account.
Go to hardware.
Check if “Usually Ships Next Day“ is working correctly and not displaying undefined value.
KOD-21990: Add all fields to the vendor invoice data grid
Regression Tests
Case 1
In the operations portal → AR/AP → AP Vendor Invoices → Data.
Check if grid is working correctly.
Tests
Case 1
In the operations portal → AR/AP → AP vendor Invoices → Data.
Check if displayed columns is working.
Check if fields to display are the same as the response from.
In order to setup the page to pull info from a filter category, go to settings > add setting 'websiteBrandsPageFilterCategoryCode' with value of filter category name that you want to use.
Check that page works correctly after updating setting and you see the correct info.
Note: page will default to ‘fg_brand’ if setting isn’t created or set.
KOD-21999: DDA - Require certain action items to be completed before Delivery status can be moved to 'Delivered'
Tests
Case 1
Go to trip, open single delivery.
You should not be able to set status to delivered without:
Saving QTY RECV. for all items under “Deliver Items“.
Saving at least one picture.
Collecting at least one signature.
Case 2
The app should follow next logic:
Once items under “Deliver Items” are saved, screen “Take Pictures” should be opened.
After pressing “Next: Collect Signature” under “Take Pictures”, screen “Collect Signature” should be opened.
After Signature successfully added, the screen with Signature should be closed and you should be prompted to change status of delivery to Delivered.
KOD-22008: Overpayment in Operations Portal - Failed to update in CSD
KOD-22009: Careers Page Design
KOD-22012: Salesforce - Create a documentation
KOD-22022: Change error message to dialog when saving company to erp
Regression Tests
Case 1
Make sure you can still push a company to the ERP successfully and the snacker still appears.
Tests
Case 1
On the companies screen, select a company → remove (if present) one of the following fields:
Company Name
Country
Address Line 1
City
State
Zip code
Primary Phone
Click the save to ERP button → notice upon error that a popup appears with the errors received → click the close button and the dialog should close.
KOD-22035: Kodaris site - fixes
Tests
Case 1
On the operations portal navigate to any page.
Open a new tab and make a logout.
Reload the first browser tab and make sure that you have moved to the login page and the URL stores information about the page you were on.
Go through the login procedure via Google authorization.
Make sure that you have moved to the right page after logging in.
Test placing an order both with po required and po not required.
Make sure the checkout process works correctly, e.g., you can checkout without po if its not required vice-versa.
Also make sure that the po number is saved when you go back to the first checkout tab, and is also saved on the order when you place it.
Case 2
Try selecting a different method of placing order, e.g., card order.
There should be no issues + placing order after this should work as well.
Case 3
Test placing an order both with po required and po not required with card payment type (both existing card and new card).
Make sure the checkout process works correctly, e.g., you can checkout without po if its not required vice-versa.
Also make sure that the po number is saved on the order after you place it, regardless if its optional or not.
Case 4
Also test guest card checkout, make sure that is working correctly.
Tests
Case 1
For feature, there should only be one place to enter a purchase order, the purchase order section on the top of the cart-payments screen.
If you select pay with ‘Account' option, there should be no purchase order input there.
Case 2
If a purchase order is not required to checkout, the input placeholder should be ‘Purchase Order - Optional’.
Case 3
If a purchase order is required, it should have the placeholder → ‘Purchase Order’ along with the following text below the input: ‘Your account setup requires you to provide us with a Purchase Order number to process your order.’
KOD-22141: Add importers to the Company Addresses
KOD-22143: Order approval flow error
Tests
Case 1
Check orderApprover customer received order email for approval without any errors.
KOD-22151: Specs tab on the product page - fixes
Regression Tests
Case 1
For this test, we need to select a product without Specs and navigate to the Specs tab.
We should see the message "There are currently no specs for this product." being displayed correctly.
Tests
Case 1
For this test, we need to select a product and navigate to the Specs tab.
You should see that for specs with more than one row, the description is now displayed correctly on both Desktop and Mobile.
Additionally, for specs with names longer than 250px, they are also displayed correctly now.
KOD-22152: Add shippingMethod field to order items
Regression Tests
Case 1
Go to order item screen (Operation portal > Order > Items) and verify you can see everything without errors.
Also go into the orderItem details and check no error appears.
Case 2
Do checkout as a user to make sure it still works.
Tests
Case 1
Go to Orders → Items and add a new Item (Or edit an existing one).
Then, edit the orderItem from development tab and confirm the shippingMethod can be edited.
Also check you can see the new field shippingMethod in the response api/system/order/{orderID}/orderItem/{orderItemID} when clicking on ‘items’ tab.
KOD-22159: Add to cart feature
Regression Tests
Case 1
Please test that we still can see related, complimentary, recently viewed and substitute products sliders.
Case 2
Please test that the product page still works as usual.
Tests
Case 1
Please test that we will see recently viewed products as GUEST user only if there are more than 4 of them.
Case 2
Please test that we will see recently viewed products as CUSTOMER always ( if there were no recent there should be frequently ordered products).
Case 3
Please test that add to cart and quantity buttons work as expected.
