“Source Link” is now clickable to open in a new tab
The “Source Link” located on the Details page of a Job/Lead in the CRM is now clickable and will open in a new tab when clicked. This saves you time by having to manually copy and paste the link into a different tab or window.
See where to locate the “Source Link” field and how this new feature works in the video below.
https://youtu.be/4nmKOU3yuzw
Operations Portal
Attach and play videos within tickets
Recently, we added the ability to attach video files and play them directly within tickets in the Customer Portal. In this release, we’ve added this same ability to the Operations Portal! This addition to the ticketing system will enhance the asynchronous communication between you, your customers, and internal team.
Check out the video below to see this feature in action!
https://youtu.be/kfW5kpgWWKY
Tickets
KOD-14664: Customer Payment Notification
KOD-14775: Phase 1 - Add UX for Supplier Portal
Tests
Case 1
Operations portal:
On the Suppliers screen, you can manage suppliers.
On the Supplier Roles screen, you can manage supplier roles.
KOD-17313: Update Public Files screen on Page Drafts
Regression Tests
Case 1
Ensure the user is created with the specified permissions: 'superuser', or 'administrator'.
Log in to the system using the credentials of the user with the specified permissions.
After logging in, locate and open the Page Drafts screen.
Choose any draft by clicking the arrow on the right side of the draft entry.
Navigate to the Public Files tab within the selected draft.
Ensure that images are displayed correctly.
To confirm that the image is viewable, click on the eye icon to preview the image.
Verify that the user can download the file by clicking on the download icon.
Expected Results:
The user should be able to see the images correctly in the Public Files tab.
The user should be able to preview the image by clicking the eye icon.
The user should be able to download the file by clicking the download icon.
All functionalities should work as they did previously, indicating that the recent changes have not affected the existing system behavior.
Tests
Case 1
A user should have this draft permissions: contentDraftView,contentDraftPublish,contentDraftEdit.
A user should have this CMS permissions: 'cmsView', 'cmsEdit'.
If the user for this test does not already exist, create a new user and assign the specified permissions.
Log in using the credentials of the newly created user.
After logging in, locate and open the Page Drafts screen.
Click on Add Draft.
Add the name and upload the picture to the draft.
Click on Save Draft.
Choose crated draft by clicking the arrow on the right side of the draft entry.
Navigate to the Public Files tab within the selected draft.
Ensure that images are displayed correctly.
To confirm that the image is viewable, click on the eye icon to preview the image.
Verify that the user can download the file by clicking on the download icon.
Attempt to delete the draft and confirm that it is successfully removed from the Page Drafts screen.
Expected Results:
The user should be able to see the images correctly in the Public Files tab.
The user should be able to preview the image by clicking the eye icon.
The user should be able to download the file by clicking the download icon.
The user should be able to delete the draft successfully.
KOD-18537: Implementation - Order templates
Regression Tests
Case 1
Ensure it's possible to generate a PDF and configure & send an email for an order.
Tests
Case 1
Operations portal → Order Details.
Order email looks good and contains all the necessary info.
Case 2
Operations portal → Order Details.
Order PDF looks good and contains all the necessary info.
Case 3
Customer portal → Order Details.
Order details page looks good and contains all the necessary info.
KOD-19054: Unilog Integration info for PIM
Tests
Case 1
Unilog should be configure using unilog settings.
Case 2
You can check the status of the integrator using /api/system/integration/unilog/status.
Case 3
You can use these endpoints to get products from unilog or just fetch an specific product.
Case 4
you can try syncing a single product if you know one partNumber from unilog, in that case you can use this endpoint:
You can look for the synced product in the system under the code unilogV-15072233.
Case 5
You can sync all products with a limit.
Then you can check in the system if we have products synced.
KOD-19241: Issue Creating Account Quote from Quote Request
Regression Tests
Case 1
Check we can still convert Quote Request to Account Quote without any issues.
To enable quote requests in card - turn on setting: enableCustomerQuoteRequestInCart.
Tests
Case 1
Ensure we can create an account quote from the quote request, and that it is NOT automatically assigned a ship-to location code of -9998 or -9999. Instead, it should be set up as a regular account quote, allowing us to set the location manually.
To enable quote requests in card - turn on setting : enableCustomerQuoteRequestInCart.
KOD-19453: Implementation - PIM Integration
Tests
Case 1
You can check vipar integration status using next endpoint:
/api/system/integration/viparpim/status
Case 2
You can sync product from Vipar using next endpoint:
/api/system/integration/viparpim/syncProducts
Where the parameter “limit” is the limit of items that you are going to try to sync.
Where the parameter “remoteFilePath” is the file path of the file that you are going to fetch to sync products from vipar’s sftp server.
KOD-19543: [BE] Able to delete emails on all emails screens
Regression Tests
Case 1
Running the DailyInterval Job with the setting jobPermanentlyDeleteEmails=0 should function as usual.
Case 2
Check emails grid in all screen:
Company Emails
Order Emails
Quote Emails
Vendor Invoice Emails
Emails
Ensure that we can view the emails.
Tests
Case 1
Make sure to test all DELETE method endpoints from Swagger. These endpoints will mark emails as deleted. Even though you will still see the emails in the list screen, you can verify through the GET endpoint that the "deleted" field is set to true.
On Swagger, check the new endpoint that permanently deletes emails. Verify that the email does not appear in any list after running this endpoint.
/api/system/email/deleteForever/{emailID}
Case 4
Check new settings:
jobPermanentlyDeleteEmails: This can be set to 1 or 0. If set to 1, it enables the permanent deletion of emails using the DeleteOldOrdersJob
jobRemoveEmailsForeverOlderThanDaysAgo: Specifies the number of days to retain emails before permanently deleting them. When enabled, the system calculates a cutoff date by subtracting the specified number of days from the current date. Emails older than this cutoff date will be permanently deleted.
KOD-19844: Related products not updating after deleting cross reference sku’s
KOD-19937: Platform for home pages/ widgets custom by company/ company group
Tests
Case 1
We are going to tests the following endpoints:
/api/system/companyPage/company (POST)
/api/system/companyPage/list (POST)
/api/system/companyPage/{companyPageId} (GET / PATCH / PUT / DELETE)
Using Swagger, test the endpoints mentioned above. The functionality should be similar to the CompanyProductCategory API. Specifically:
The code should be unique across companies, customers, and customer groups.
Case 2
We are going to tests the following endpoints:
/api/system/companyPage/customerGroup (POST)
From swagger create a CompanyPage and associate that with a existing CustomerGroup ID.
From swagger create a CompanyPage and associate that with a existing Customer ID.
CompanyID should be associated with the Company from the customer. (This is always true whenever we update the CustomerID. In the case that you try to update the customerID from api/system/companyPage/{CompanyPageID} then the companyID will be associated with the Company from the customer.
KOD-19993: Convert shipto creation to webui / csd flow
Check that the order details show up fine in the customer portal.
Same with order email and pdf.
Tests
Case 1
The order details, email, and pdf should look similar to the mailer pdf version.
Note: the header will appear a bit differently.
Case 2
Check the following information shows up on the invoices:
Discount amt by certain date (if applicable).
Finance information is displayed on the bottom.
KOD-20530: Update primary warehouse message
KOD-20624: Ensure Usage Flag Is Checked
KOD-20684: Customers Can't Access Documents
Regression Tests
Case 1
User should still be able to navigate to the documents page in the embedded customer portal.
Case 2
Go to any standalone payment portal → go to Documents → make sure the view and download buttons still work as before.
Tests
Case 1
Navigate to Documents section in the embedded customer portal → click the view icon → user should be able to view the pdfs (as long as the customer file with id is found → if not it should give a 404 error and nothing will pop up … also if pdf has an error within it, it will pop up with a preview saying error failed to load document → most likely won’t be an issue on a prod envt).
Case 2
Navigate to Documents section in the embedded customer portal → click the download icon → file should have been downloaded and user should be able to open file (also same issue as above if customer file with id isn’t found, it will just show a 404 error and if there is an error within the pdf, it will download, but when opening file it will give same error message as the preview button → once again most likely won’t happen on a prod envt).
KOD-20698: Update UX for unit conversion unitSell
Regression Tests
Case 1
Go to any category view or product description view, and make sure the pricing still shows up as before.
Case 2
For a product that has multiple unit conversions, make sure nothing new has popped up (i.e. new functionality is not shown here).
Tests
Case 1
Find a product that has a unitSell = unitConversions → units (as well as where the calculated price != whole unit price).
Go to both the product list page and product description page and notice the new text next to the price = ([unitSell] of [unitConversion]).
KOD-20714: Link the Source Link on Leads
Regression Tests
Case 1
Open the operations portal.
Log in with valid data - Click on the “Login“ button.
Go to the CRM > Jobs category.
In the grid filter, select Type=Lead.
Go to the page of a specific lead record.
Make sure that when the page loads, all elements are positioned correctly and the layout looks correct.
Click on each page element, make sure it is clickable.
In the Source Link field, change the value and make sure that the save is applied on the lead page.
Check that the save is applied when reopening the lead page.
Go to the specific lead record page.
Checking for changes on the lead page.
Check that the Source Link field has a MattSuffix Button located on the right.
Confirm that there are no additional changes on this page.
Confirm that if in the grid filter on the Jobs page, select Type=Quote and go to the page quotas - Source Link field will not have MattSuffix Button.
Tests
Case 1
Log in with valid data - Click on the “Login“ button.
Go to the lead page.
Go to the CRM > Jobs category.
In the grid filter, select Type=Lead.
Go to the page of the specific lead record.
Checking the new functionality on the lead page.
Check that the Source Link field has a MattSuffix Button located on the right.
Check that when you click on the MattSuffix Button, a link similar to the text in the Source Link field opens.
Check that changing the link in the Source Link field and clicking on the MattSuffix Button opens a link similar to the changed text in the Source Link field.
Check that clicking the MattSuffix Button will not work if the Source Link field is not filled in.
Check that if you clear the field Source Link (pre-filled) - clicking on MattSuffix Button will not work.
KOD-20778: Enable cart indicators
Regression Tests
Case 1
Select any product category and navigate to the category page.
Ensure that the product tile displays correctly with all necessary information.
Add product (+).
Decrease product quantity (-).
Click “Add to cart”.
Verify that the product is correctly added to the cart and the cart indicator updates.
Repeat the verification for the List View.
In Grid View or List View, click on any product to view its detailed information (Detail View).
Ensure that all product information displays correctly.
Test the action buttons in Detail View:
Add product (+).
Decrease product quantity (-).
Click “Add to cart”.
Verify that the product is correctly added to the cart and the cart indicator updates.
Tests
Case 1
Select any product category.
On the category page, choose any product.
Click the “Add to cart” button on the selected product.
Check if the indicator showing the quantity of added products appears in the upper right corner.
Repeat the verification for the List View.
Check if the indicator showing the quantity of added products appears in the left corner (List View).
Check if the products were correctly added to My Cart.
Case 2
Select any product category.
On the category page, choose any product.
Click the “Add to cart” button on the selected product.
Check if the indicator showing the quantity of added products appears in the upper right corner.
Repeat the verification for the List View
Check if the indicator showing the quantity of added products appears in the left corner (List View).
Check if the products were correctly added to My Cart.
Case 3
Select any product category.
On the category page, choose any product.
Click the “Add to cart” button on the selected product.
Check if the indicator showing the correct quantity of added products appears in the upper-right corner.
KOD-20819: Add ability to attach and play videos to customer tickets
Regression Tests
Case 1
For the regression testing we need to make sure that you can still upload files and preview them in the customer files section from a type different than mp4.
Also we can check that the filters and the Show / Hide button still works.
Case 2
We need to make sure that you can still view CSV files under Orders, Companies and Quotes.
Tests
Case 1
For the testing, we need to make sure that we can:
Upload mp4 file.
Make sure it appears on the files table with the video icon.
Click on the preview button (the eye icon) and make sure you can see the spinning loader before the video appears.
See the video playing without any issues and confirm that the mute, volume, full screen, pause, speed, picture in picture mode and download buttons work as they are supposed to.
KOD-20848: LinkedIn Graphics
KOD-20855: Implementation - Breadcrumbs design
Regression Tests
Case 1
Ensure that new features do not impact existing features and that all components with changed code function and display correctly.
Go to specific category page.
Expected result: Make sure that breadcrumbs are displayed on the page and do not contain errors in the structure.
Tests
Case 1
Go to specific category page.
Expected result: Make sure the breadcrumbs are of a design that matches the new design in Figma.
Make sure that when changing the screen width, the breadcrumbs adapt correctly and the layout does not break.
KOD-20858: Implementation - CMS Serverside Blocks
KOD-20881: Generate a new account in real time - UX
Regression Tests
Case 1
Payment portal.
Test that login and register pages works as usual.
Case 2
Full commerce.
Test that login and register pages works as usual.
Header loads and looks without any problems.
Tests
Case 1
Payment portal.
Click on "Go to my account".
Than click on "Initialize an account".
Check that URL has spcu/register.
Try to register yourself with no existing user in system.
You should receive “Please Activate Your Account” email and successfully login as a customer.
Go to companies screen.
Find company using email that was using during register.
Company should be created and check here that there is no flag for pay with credit card.
Company → customers, check that customer was created.
Case 2
Payment portal.
Click on "Go to my account"
Then click on "Initialize an account".
Check that URL has /spcu/register.
Try to register yourself with no existing user in system.
You should receive “Please Activate Your Account” email and successfully login as a customer.
Go to companies screen.
Find company using email that was using during register.
Company should be created and check here that there is flag for pay with credit card.
Company → customers, check that customer was created.
Login in salesforce sandbox.
Using global search find your new created customer
Case 3
Pre-requirements: Turned on this setting customerRegistrationEnabled.
Click on Account in header.
Click on Register for an Account
Try to register yourself with no existing user in system
You should receive “Please Activate Your Account” email and successfully login as a customer.
Go to companies screen.
Find company using email that was using during register.
Company should be created and check here that there is no flag for pay with credit card.
Company → customers, check that customer was created.
Case 4
Pre-requirements: Turned on this setting customerRegistrationEnabled, customerRegistrationCardsEnabled.
Click on Account in header.
Click on Register for an Account.
Try to register yourself with no existing user in system.
You should receive “Please Activate Your Account” email and successfully login as a customer.
Go to companies screen.
Find company using email that was using during register.
Company should be created and check here that there is a flag for paying with credit card.
Company → customers, check that customer was created.
Case 5
Click on Account in header.
Click on Register for an Account.
Try to register yourself with no existing user in system.
You should receive “Please Activate Your Account” email and successfully login as a customer.
Go to companies screen.
Find company using email that was using during register.
Company should be created and check here that there is a flag for paying with credit card.
Company → customers, check that customer was created.
Login in salesforce sandbox.
Using global search find your new created customer.
Case 6
Pre-requirements: Turned on this setting customerRegistrationEnabled.
Use URL with /spcu/register.
Try to register with existing customer in system.
You should receive an error.
You need to trigger an error. company and record in salesforce shouldn’t be created.
Case 7
Pre-requirements: Turned on these settings customerRegistrationEnabled and customerRegistrationCardsEnabled
Use URL with /spcu/register.
Try to register with existing customer in system.
You should receive an error.
You need to trigger an error. company and record in salesforce shouldn’t be created.
KOD-20886: AP Automation Parsers
KOD-20888: Send email to customer when they get locked out and let them reset their password
Regression Tests
Case 1
If setting customerAlertWhenAccountIsLockedOut=0 when a customer account is locked due to multiple fail attempts to login should then the flow should work as always.
Tests
Case 1
Check new setting should be equal to 0 - customerAlertWhenAccountIsLockedOut.
Case 2
If setting customerAlertWhenAccountIsLockedOut=1 when a customer account is locked due to multiple fail. Then an email should be sent.
Note: The template loaded is a temporary template.
Case 3
Check new temporary email template accountLocked-EJS.
KOD-20896: Kodaris - Auto assign assignee to contact form submissions
KOD-20897: Add Attributes to Category Catalog View on Demo & Content Sites
Regression Tests
Case 1
Select any category from the list.
Select Catalog View to view products.
Ensure the product table is functioning correctly.
Confirm that the user can add products to the cart.
Verify that the user can select the quantity of products to add to the cart.
View the cart to confirm that the products have been added.
Go back to the Catalog view.
Ensure that you can access the detailed view of a product.
Expected Results:
The product table should function correctly.
Users should be able to add products to the cart and select the desired quantity.
The cart should reflect the added products accurately.
Users should be able access the detailed product view without any issues.
Tests
Case 1
Select any category from the list.
Select Catalog View to view products.
Ensure that all attributes are displayed correctly for each product in the Catalog view.
Open Operations.
Select "Products".
Click on "Data" and add a new product.
Open the newly created product (click on arrow).
Go to the "Attributes" section.
Add custom attributes to the product.
Go back to the Demo site.
Search for the newly created product.
Ensure that all the added attributes are displayed correctly.
Expected Results:
All product attributes should be displayed correctly in the Catalog view.
Custom attributes for the newly created product should be visible and correctly displayed in the Catalog view.
KOD-20917: Kodaris Support and Account ticket Flows
KOD-20921: Testing Scenarios
KOD-20931: Add bag unit conversion to Work Order PDF
Regression Tests
Case 1
On a Cash Quote generate Internal PDF.
Template code to test: V2-workOrderPDF-EJS.
Check that template was loaded with no issues, any of the template layout was changed.
Tests
Case 1
On a Cash Quote generate Internal PDF.
Template code to test: V2-workOrderPDF-EJS.
KOD-20933: add document type or label to each doc
Regression Tests
Case 1
On a cash quote try generating internal PDF.
Select TEST-workOrderPDF template.
In the generated template check that no template looks, functionality is changes besides feature change.
Case 2
On a cash quote try generating internal PDF.
Select TEST-loadingListPDF template.
In the generated template check that no template looks, functionality is changes besides feature change.
Case 3
On a cash quote try generating internal PDF.
Select TEST-cashQuoteEstimatePDF template
In the generated template check that no template looks, functionality is changes besides feature change.
Tests
Case 1
On a cash quote try generating internal PDF.
Select TEST-workOrderPDF template
Make sure at the top right there is document type label Work Order.
Case 2
On a cash quote try generating internal PDF.
Select TEST-loadingListPDF template.
Make sure at the top right there is document type label Loading List.
Case 3
On a cash quote try generating internal PDF.
Select TEST-cashQuoteEstimatePDF template.
Make sure at the top right there is document type label Cash Quote Estimate.
KOD-20946: Implementation - Inventory
KOD-20960: Operations Portal - some id's are not being exported
KOD-20977: Implementation - UX for Import
Regression Tests
Case 1
For regression testing, ensure the table functionality is intact. Verify that the Show/Hide Columns button works, pagination operates correctly, and that the previous import methods are still available.
KOD-20989: Add captcha to register API endpoint
KOD-20998: Add a new setting for including public price calls in user ERP for pricing flow
KOD-20999: Error Message When Adding Items
KOD-21004: Add new field named workStatus to Ticket table - Account Ticket Emails
KOD-21005: Add debugging output
Regression Tests
Case 1
Make sure that the search still works correctly.
KOD-21007: Cash Quote Template Tweaks
Regression Tests
Case 1
Login into Operations Portal.
Navigate to Orders and go to details for any order.
Try ‘Email Order’ and verify that it generates as expected. No need to send it anywhere.
Case 2
Login into Customer Portal.
Navigate to Orders and go to details for any order that is not Cash Quote.
Check if preview is expected.
Click print and check if created PDF file looks as expected.
Tests
Case 1
Login into Operations Portal.
Navigate to Cash Quotes and go to details for any cash quote.
Try ‘Email Quote’ and verify that it generates as expected. No need to send it anywhere.
Case 2
Create Cash Quote for your customer’s company if there is no such.
Login into Customer Portal.
Navigate to Orders and go to details for any order that is Cash Quote. (the one you created or already existing).
Check if preview is expected.
Click print and check if created PDF file looks as expected.
KOD-21016: DDA update deliver labels screen to display label number
KOD-21017: Implementation - Countries / States
KOD-21018: Search Debugging Output UX - Phase 1
Regression Tests
Case 1
For the regression testing, we need to make sure that the searching and the pagination still works as expected. We can also verify that the Add to cart button also works for the product cards.
Tests
Case 1
To test the new functionality, you need to login as an administrator with the searchDebug role, then we need to search a product.
Two new search parameters will be automatically added to the URL: highlights and debug. Both need to equal true.
After you do that you’ll be able to see the “Search Debugging” section in which three variables will appear with the appropriate information (explainMapParsed.json, debugMap.json and highlights.json).
We need to make sure that this section appears only when are logged into the operations portal and have the searchDebug role.
KOD-21019: Implementation - Warehouses
KOD-21030: Add orderID, customerID, and companyID to events data
Regression Tests
Case 1
Perform an action that you know that should save an event in the event table and check that it is working fine. For example, failed login attempt, place an order, etc.
Also you can try listing events in the event menu and verify that this still working
Tests
Case 1
check that new fields exist in Event entity:
customerID
companyID
orderID
Case 2
Try to add or modify Event using the Event API on swagger to test that new fields could be populated or not.
KOD-21034: Updates to DQ integration - Populate Delivery address, Company Code, and Filter line items
Regression Tests
Case 1
Test submitting delivery event and processing by FiveMinuteIntervalJob.
Setting driverDeliveryUseOrderItemsAsShipmentItems should be ON.
Case 2
/api/system/order/driverDelivery/getSingleTripDetails working as expected.
Setting driverDeliveryUseOrderItemsAsShipmentItems should be ON.
Tests
Case 1
Submit delivery event and process on FiveMinuteIntervalJob and check add ress fields copied from order delivery address to delivery object.
Setting driverDeliveryUseOrderItemsAsShipmentItems should be ON.
Case 2
Check /api/system/order/driverDelivery/getSingleTripDetails endpoint returns related to order company object.
Setting driverDeliveryUseOrderItemsAsShipmentItems should be ON.
KOD-21035: DDA updates - display more fields and bug fixes
KOD-21043: Melting form tweaks
Regression Tests
Case 1
Make sure that the form is working, the emails are being sent, ticket is created. Also check if all of the required fields are marked with an *. Check for guest and logged in customers.
Tests
Case 1
There should be a better looking input visual for the phone number field.
The default selection for Special Delivery Services is “no special delivery required”.
Delivery address, city, province and postal code should be auto populated from the ShipTo address, shipto address should also be auto populated if it is selected.
Case 2
Guest user:
Points 1 and 2 from previous test case.
The delivery week field should be available for all guest customers.
KOD-21044: Add COD card form endpoint
KOD-21046: Add issue credit endpoint for Kodaris payment provider
Check that cart looks good and you can add products to the car.
Case 2
In operations portal add product NONSTOCK.
In front part, check cart if you can see request custom item button.
Tests
Case 1
In operations portal check if product NONSTOCK doesn’t exist.
In front part, check cart if you don’t see request custom item button.
KOD-21058: Implementation - Warehouses
KOD-21059: Implementation - Update notifications
KOD-21061: Pull in Order Notes
KOD-21081: Deleting the validation on product codes for corss references synced from the ERP
Regression Tests
Case 1
Import a Cross Reference records should still working fine.
Tests
Case 1
You should be able to import a cross reference record with a product code that doesn’t exist in the database. Also with a company code that doesn’t exist.
KOD-21083: Implementation - Locations Page Tweaks
Regression Tests
Case 1
Navigate to the "Locations" page.
Verify that the company logo is displayed correctly on the "Locations" page.
Click on the "More information" link or button for a store location.
Verify that the link redirects to a page with more detailed information about the store.
Expected Results:
The company logo should be displayed correctly on the desktop version of the "Locations" page.
Clicking the "More information" link should successfully redirect to the detailed information page for the company.
Tests
Case 1
Open the website.
Navigate to the "Locations" page.
Open Developer Tools (DevTools) in your browser.
Switch to the mobile version of the site by selecting a mobile device from the device toolbar.
Verify that the store addresses are displayed correctly.
Ensure that the addresses are listed in alphabetical order by location.
Confirm that company logos are not displayed on the mobile version of the "Locations" page.
Expected Results:
Store addresses should be listed in alphabetical order by location.
No company logos should be visible on the mobile version of the "Locations" page.
