You now have the option to split ERP quotes into a different screen in the Customer Portal so that they’re separate from the Orders screen. This is not required, but you have the ability to enable the setting in the Operations Portal.
See how you can turn on this setting by watching the video:
https://youtu.be/3SdND3nIg2g
Mobile App
“My Chats” feature added to the Employee Mobile App
When a customer comment is added to a Ticket, it will create a chat thread under the new “My Chat” section in the Employee Mobile App. By clicking on the chat thread, you’ll be taken to the customer comments under the Ticket where you’ll be able to read all comments and respond directly. This feature will allow you to organize and stay on top of customer comments, ensuring that no comment is left unseen.
Check out the images below, or download the app to see for yourself! 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.
Tickets
KOD-9680: Zip Code Table - Shipping Table Update
Tests
Case 1
Here we are to test basic crud endpoints for create/read/update/delete.
Use following endpoints to create a PostalCodeData and read/edit/delete:
/api/system/postalCodeData/{postalCodeDataID}
And this one to create:
POST -> /api/system/postalCodeData
Example of payload for creation:
{
"code": "KOD-968",
"postalCode": "10001",
"city": "New York",
"stateCode": "NY",
"imprecise": false,
"educationCollegeOrAbove": 65.12345,
"raceWhite": 50.12345,
"taxJurisdiction1": "NYC",
"user1": "test",
"warehouseID": 13,
"countryID": 150
}
Note: Code is unique - if you try to generate an empty code system will autogenerates one.
If you try to create a record with an existing code, you will get 'PostalCodeData code already exists'.
Use /api/system/postalCodeData/list endpoint to get the records.
In here you can just pass size and page and it will find all. If not, you could filter by postalCode / code / warehouseID / postalCodeDataID like this:
{
"page": 0,
"size": 10,
"filterFields": [
{
"name": "postalCodeDataID",
"value": "1",
"operation": "IS"
}
]
}
Case 2
Use following export to get the csv file: /api/system/postalCodeData/export.
That works as any other export in the system where you can filter the records to export or limit it.
For example:
{
"page": 0,
"size": 10,
"filterFields": [
{
"name": "postalCodeDataID",
"value": "1",
"operation": "IS"
}
]
}
Case 3
For import we can use any of these endpoints test until we have the UX screen.
Or also, you could use general import from UX and then wait for the FixeMinuteBulkJob to run:
On Orders, Quotes and Cash Quotes tabs make sure those tabs are not broken.
Case 2
Set enableNewOrderInternalNotes setting value to 0.
On following tabs:
Order Internal Comments
Quote Comments
Cash Quote Internal Comments
Make sure that we’re using old flow for taking order notes.
Order notes should be taken from api/system/order/search/{orderID}.
pi/system/quote/search/{orderID}.
Case 3
With the same setup as for the Case 2 check adding a note. Make sure that on wedding the same PATCH endpoints are used and new note is passed in the payload in quoteNotes field.
Make sure after adding new note appeared within the comments list.
Tests
Case 4
Set enableNewOrderInternalNotes setting value to 1.
On following tabs:
Order Internal Comments
Quote Comments
Cash Quote InternalComments
Make sure we’re using new endpoints to list notes:
On Order Internal Comments we’re using api/system/order/{orderID}/note/list.
On Quote Comments we’re using api/system/quote/{orderID}/note/list.
On Cash Quote Internal Comments we’re using api/system/order/{orderID}/note/list.
Case 5
With the same setup as from the Case 4:
Make sure we’re using new endpoints to add new note.
On Order Internal Comments we’re using POST api/system/order/{orderID}/note.
On Quote Comments we’re using POST api/system/quote/{orderID}/note.
On Cash Quote Internal Comments we’re using POST api/system/order/{orderID}/note.
Case 6
Set enableNewOrderInternalNotes setting value to 1.
On Quote Comments make sure you see actual Comment Count at the top when page is loaded initially.
Add a new comment. Reload page. Make sure Comment Count number is updated at the top nav.
KOD-20612: sync mapping scripts
KOD-21036: Implementation - Taxes
KOD-21340: Parser Requested Enhancements
KOD-21487: Freight / Delivery Fee Assessment on Checkout
KOD-22271: Importing Company Group Catalogs and Products updates - Code supported
Regression Tests
Case 1
Imports by companyProductCategoryID and externalID should still be working.
Make sure you have the lookupFieldName with ‘companyProductCategoryID’ to identify the catalog.
Do an import an update an existing catalog using the ID in the column.
Case 2
Make sure you have the lookupParentFieldName with ‘companyProductCategoryID’ to identify the catalog.
Validate that the product is added under the specific companyProductCAtegory ID specified.
Tests
Case 1
Here you can change mapping to use lookupFieldName = ‘code’ or if not, just don’t send the ‘companyProductCategoryID’ neither ‘externalID’ and it will fallback to do the lookup by code.
Since code is not unique, you need to identify the company catalog by adding the companyCode column as well.
Do an update or create and validate it works fine.
Example of csv File:
"code","companyCode","name"
Case 2
Here you can change mapping to use lookupFieldName = ‘code’ or if not, just don’t send the ‘companyProductCategoryID’ neither ‘externalID’ and it will fallback to do the lookup by code.
Since code is not unique, you need to identify the company Address catalog by adding the companyAddressCode column as well.
Do an update or create and validate it works fine.
Example of csv file:
"code","companyAddressCode","name"
Case 3
Here you can change mapping to use lookupFieldName = ‘code’ or if not, just don’t send the ‘companyProductCategoryID’ neither ‘externalID’ and it will fallback to do the lookup by code.
Since code is not unique, you need to identify the Customer Group catalog by adding the customerGroupCode column as well.
Do an update or create and validate it works fine.
Example of csv file:
"code","customerGroupCode","name"
Case 4
Here you can change mapping to use lookupFieldName = ‘code’ or if not, just don’t send the ‘companyProductCategoryID’ neither ‘externalID’ and it will fallback to do the lookup by code.
You can add products to any catalog (Company catalog, company Address catalog, customer group catalog and customer catalog)
For adding to a NON customer catalog you need code + one of the following columns:
Validate that you can add product to any of these catalogs.
Example of csv file:
"code","companyCode","productCode"
Case 4
Here you can change mapping to use lookupFieldName = ‘code’ or if not, just don’t send the ‘companyProductCategoryID’ neither ‘externalID’ and it will fallback to do the lookup by code.
You can add products to a customerCatalog by specifying code + companyCode + userName (Username of the customer).
Then, validate that the product is being added to the customer catalog and NOT to the company catalog (It can happen there exist 2 catalogs under the same code + companyCode. The difference will be one of them is a customer catalog)
Example of csv File:
"code","companyCode","productCode","userName"
KOD-22273: FTP Rollout
KOD-22377: Add robots directive to test site
KOD-22465: Custom PIM Import
KOD-22497: Create settings table for related products
Tests
Case 1
Test related product setting endpoints on swagger side:
Check endpoint: /api/system/order/list whether the field: orderTypeDetails is filterable.
Example =>
"filterFields": [
{
"name": "orderTypeDetails",
"value": "Cash Quote",
"operation": "IS",
"not": false,
"and": false
}
]
KOD-22658: Business Intelligence
KOD-22677: Implementation - Videos
KOD-22726: Create settings for activity fields - UX
Regression Tests
Case 1
Make sure that the /settings and /activities pages are working as before. All necessary information is displayed without errors.
Tests
Case 1
Add values to the departmentTicketVaues, projectTicketValues, teamTicketValues settings on the `/settings` page.
Go to the activity page.
Make sure that the text input fields have changed to dropdown.
Make sure that the data that we added via the settings page is available in the dropdown.
Make sure that the data is saved without errors.
KOD-22761: integration updates
KOD-22766: Build out blocking and alerts for employees on Fraud
KOD-22780: Add the Ability to Refresh Informational Cards via a refresh button click
Regression Tests
Case 1
The information in the table should also be updated after refresh button click.
Tests
Case 1
Go to the Operations portal -> Events -> Status tab. When clicking the refresh button, in addition to updating the table, the informational cards above the table (records queued, records processed, records failed) should also be updated.
KOD-22819: Create new Setting and add it to employee configuration endpoint
KOD-22838: Add Find a Dealer layout to content site
Regression Tests
Case 1
Check that the saved-for-later, account-retrieval pages open correctly on the website.
Tests
Case 1
Check that the find-a-dealer page opens correctly.
Check that there are no errors in the console related to this page.
Check that the page layout looks correct.
KOD-22869: Kodaris - Update settings type for all types of Jobs
Tests
Case 1
Navigate to the Operations Portal - Scheduler View and make sure that the changes made in txt below show up and that the Scheduler names match up to jobs.
Jobs can be found in Settings → for some of the settings, they should equal a scheduler name EX: FiveMinuteIntervalJob.
KOD-22893: Sync Inventory and pricing to Kodaris
KOD-22894: Sync Inventory for Products
KOD-22902: Generate Tracking Numbers for DQ created order Shipments
Regression Tests
Case 1
With setting enableGeneratedOrderShipmentTrackingNumbers disabled, do not send the trackingNumber in /api/system/orderShipment/addOrUpdateByExternalOrderNumber and make sure the value is not autogenerated.
Tests
Case 1
With setting enableGeneratedOrderShipmentTrackingNumbers enabled, use following endpoint /api/system/orderShipment/addOrUpdateByExternalOrderNumber to create an OrderShipment and make sure the trackingNumber is autogenerated (Do not send the trackingNumber field)
Example of request:
{
"code": "CODE_1000",
"externalOrderNumber": "7878-87",
"status": "ADDED",
"active": true
}
Case 2
With setting enableGeneratedOrderShipmentTrackingNumbers enabled, use following endpoint: /api/system/orderShipment/addOrUpdateByExternalOrderNumber to create an OrderShipment but send a value in the payload.
That value should remain after inserting the record.
Example of payload:
{
"code": "CODE_1000",
"externalOrderNumber": "7878-87",
"status": "ADDED",
"active": true,
"trackingNumber": "ABC1234"
}
Case 3
With setting enableGeneratedOrderShipmentTrackingNumbers enabled, use following endpoint: /api/system/integration/dq/webhook/deliveryEvent to create an Trip/Delivery/OrderShipment and make sure the trackingNumber is generated there as well.
This will create a event and then it will actually be processed in the FiveMinuteIntervalJob.
Example of payload:
{
"deliveryID": "code_9823sd",
"orderNumber": "123123132-1",
"stopNumber": 1
}
The orderNumber should have to be a valid externalOrderNumber.
KOD-22926: Order Detail Updates
Tests
Case 1
Operations portal => Order Details.
Generate email.
Expected result:
There is no Discount column.
Credit terms are pulled from order.company.termstypeDescription.
Case 2
Customer portal => Order Details.
Expected result:
There is no Discount column.
Credit terms are pulled from order.company.termstypeDescription.
KOD-22929: PIM Explore - Managing Product Data via External PIM Integrations
KOD-22941: Update Add Company Flow in Employee App
KOD-22952: Display links to vendor resources
KOD-22994: Update Invoice Total when There's a Downpayment
Check whether current new setting return on employee /config endpoint.
Case 2
Check new quote note swagger endpoints.
Internal Comment endpoints:
POST /api/system/quote/{quoteID}/note
GET /api/system/quote/{quoteID}/note/{noteID}
PUT /api/system/quote/{quoteID}/note/{noteID}
DELETE /api/system/quote/{quoteID}/note/{noteID}
POST /api/system/quote/{quoteID}/note/list
KOD-23007: Implementation
KOD-23016: Fix CMS link on homepage panel moving around the page
KOD-23017: Add ERP Quotes Screen to Customer Portal
Regression Tests
Case 1
Verify the Contract Quotes screen.
Verify the Quotes screen.
Test the functionality of the table on both screens.
Tests
Case 1
Log in to the website.
Click on ‘manage account’.
Verify if the Quote screen is visible in the navigation menu.
If the Quote screen is not visible:
Open the operations portal.
Navigate to the Settings screen.
Update the customerERPQuotesEnabled field to 1.
Verify the Quote screen is now displayed in the navigation menu.
Ensure its functionality is identical to the Order screen.
Validate that the displayed data is filtered correctly, showing only records where extra1 = Quote.
Case 2
Check for the presence of the Contract Quotes screen.
Confirm that the Contract Quotes screen has retained all features and functionality from the previous Quote screen.
Case 3
Check for the presence of the Orders screen.
Verify that the Orders screen does not contain ERP quotes when the customerERPQuotesEnabled setting is set to 1.
KOD-23022: Order Taxes Based on SASST
KOD-23031: Employee App - My Chats feature
Regression Tests
Case 1
Test all screen next screens, they should be working correctly.
Note: for every screen test editing / adding / updating data in all possible fields.
Company data grid
Company details
Assignees
Customers
Orders
Tickets
Activity data grid
Details
Customer comments
Internal comments
Assignees
Ticket details
Details
Customer comments
Internal comments
Assignees
Expenses Reporting
Details
Tests
Case 1
Note: for chats to be found, you should write 1-2 comments under the ticket by yourself.
Go into “My Chats” screen.
If no chats found, you should see message "No chats were found."
If chats are found, you should see them.
Case 2
When clicking on the chat, you should be taken to ticket details → Customer comments section.
Case 3
On comments screen you should see the text "Add a comment..."
KOD-23032: Direct Ship Delivery Fees
KOD-23033: Custom Homepage - Title above Markets update
Regression Tests
Case 1
Check that the header title block is displayed correctly.
Check that the text in the header title can be changed and is displayed correctly.
Tests
Case 1
Check that the information in the header title is located on 1 line.
Check that the blue underline under the header title is the same width as the text.
KOD-23035: Custom homepage - Home Content Tiles update
Regression Tests
Case 1
Check that the Content Tiles layout looks correct.
Check that there are no errors related to Content Tiles in the console.
Check that the Content Tiles functionality works correctly (delete Tile, edit, etc.)
Tests
Case 1
Check that the bottom border of the “Content Tiles” block coincides with the bottom border of the subcategories block (the block on the left).
Check that Content Tiles functionality can be added for Tile Main Text and Additional Text.
Check that the Tile layout with Main Text and Additional Text are displayed correctly.
KOD-23038: Custom homepage - Top Brands image alignment
Regression Tests
Case 1
Check that the layout of the Top Brands block is displayed correctly (on different devices).
Tests
Case 1
Check that each brand image is centered.
KOD-23045: ERP Configuration and release order to the ERP
KOD-23046: Slider - Apply auto loop logic
KOD-23058: Piyovi Shipping Integration
KOD-23059: Get shipping rates from any shipping engine
KOD-23063: Email Sending
KOD-23067: Implementation - Set Card Payment System
KOD-23069: Search Rule Validator
Regression Tests
Case 1
Navigate through SearchRule screens and make sure you can create/edit any SearchRule.
Tests
Case 1
Enable setting jobInactivateSearchRules to be ran during the DailyJob.
New subscriptionList where employees can subscribe: InvalidSearchRulesAlert.
The idea for the testing is generate some wrong redirect URLs for SearchRule and those SearchRules might be updated with status ‘INVALID’ and mark us Inactive.
For testing:
Create a preProcessing SearchRule with action = categoryRedirect and actionData= anyInvalidCode.
Create another preProcessing searchRule with action = categoryRedirect and actionData = validCode but do not set any products on it (Just a category without products).
Create a preProcessing SearchRule with action = urlRedirect and actionData = any invalid URL without the first part (For example, /api/user/product/invalidCode).
(This needs to be created from swagger):
{
"query": "mouse",
"searchType": "product",
"minimumMatch": "1",
"active": true,
"pattern": "matchSearchText",
"action": "urlRedirect",
"actionData": "/api/user/product/invalidCode",
"ruleType": "preProcessing"
}
Wait until job runs and make sure those searchRules were inactivated and status changed as well.
If there were subscriptions to the subscription list, an email with the report should send it to you.
In swagger using /api/system/searchRule/list endpoint you can gett all searchRules that are inactive using this payload:
{
"page": 0,
"size": 10,
"sortBy": "id",
"filterFields": [
{
"name": "active",
"value": false,
"operation": "IS"
}
]
}
For the one SearchRule that changed the status but was not inactivated, you might have to filter by searchRuleID or just get ALL in the list endpoint and find the searchRule (Since you cannot filter by status yet).
KOD-23079: Implementation - Check on Sync Issue
KOD-23105: Issue With Call for Availability
Tests
Case 1
For this test, we will go to the Products screen.
Inside the In Stock section, if the product has no inventory on a certain warehouse, you should see the message “Call for Availability”. If there is stock, you should see the number being displayed correctly with the formatting with a comma every three digits.
KOD-23106: Thumbnail missing from recently viewed Products
KOD-23111: Zip Code Table
Regression Tests
Case 1
Make sure the operations portal works with no issues. You should be able to check different tabs with no issues (if you have permissions for those tabs).
Case 2
Make sure left nav is not broken and works with no issues.
Tests
Case 1
Make sure new Tab Postal Codes is added under System to the left nav.
Case 2
Go to the Postal Codes tab. Make sure in the header you can see Postal Codes header.
Make sure this tab contains the grid.
You should be able to add new postal code, to edit existent postal code record and to delete postal code record.
Case 3
Within the grid make sure you can add/remove columns from the Postal Codes grid.
KOD-23116: Configure email to entire website
KOD-23118: Add button to save pricing record to ERP
Regression Tests
Case 1
Make sure the pricing page still loads correctly.
Tests
Case 1
Go to the Pricing → click into a price → notice up top save to ERPbutton → click the button → upon success you should see a snacker saving ‘Saved to ERP’ → if unsuccessful, you should see an error dialog pop up with the field and value of the errors.
Case 2
After you saved the pricing to the ERP, to test the update part, make sure the pricing record has trendCompiledSettings and then click the save to ERP button again and it should save with that snacker saying ‘Saved to ERP’.
KOD-23121: Update Font Site-wide
Regression Tests
Case 1
Make sure the pages load without errors and the content is visible.
Case 2
Confirm that the font for regular text on the pages is "Inter".
Tests
Case 1
Confirm that the heading tags on the pages use the "Oswald" font.
KOD-23123: Implementation - Remove old gifs
KOD-23132: Create new discount endpoints for the order, purchase order, vendor invoice
KOD-23135: Kodaris.com - Add PIM page to platform tab
KOD-23136: Adding/updating customerTrackingNumber field to the cart
Regression Tests
Case 1
You should continue updating other fields in the cart PATCH endpoint.
