View all releases

November 21, 2024 release notes

Tickets

KOD-20135: Exclude Inactive Customers When Copying Quotes
- Regression Tests
- Case 1
  - Quotes → Quote.
  - Open modal for copying quote.
  - Check if autocomplete is still working.
- Tests
- Case 1
  - Quotes → Quote → copy quote.
  - Try to search for some inactive company.
  - Set some active company to inactive.
  - Try to search for that company.
KOD-20591: Add dev doc on how to call API on product category fetch
KOD-20593: Add dev doc on how to call API on listing linked orders
KOD-20592: Add dev doc on how to call API on product search
KOD-20594: Add dev doc on how to call API on creating customer API user
KOD-21388: Redirect/Resolve URLs ending in slash
KOD-21674: Email template and Plugin Testing
- Tests
- Case 1
  - Go to an order in the operations portal, and generate an email with template → directPurchaseOrder-EJS.
  - Make sure it generates correctly and everything looks good.
KOD-21984: Create a documentation
KOD-21986: Add to demo site missing items
- Regression Tests
- Case 1
  - Check that product details page still looks good.
- Case 2
  - Check that category view still looks good (for list/grid/catalog view).
- Case 3
  - Check that FAQs still looks good.
- Case 4
  - Check paying with credit card using Android phone.
- Case 5
  - Check paying with credit card using IOS phone.
- Tests
- Case 1
  - Should be tested on product details page.
  - If product have manufacturerProductCode and manufacturerCode, you should see SUPPLIER and SUPPLIER PART #.
- Case 2
  - Should be tested on product details page.
  - If product has weight, you should see weight.
  - If not, you should not see this.
- Case 3
  - Should be tested on product details page.
  - If product has unitSell, you should see unit sell near price.
- Case 4
  - Should be tested on product details page.
  - You should see “sign in to see your price” if you are not log in as a customer.
- Case 5
  - Should be tested on category view (for list/grid/catalog view).
  - You should see “sign in to see your price” if you are not log in as a customer.
- Case 6
  - Log in as an employee.
  - Check that you can add the fourth FAQs and it’s shown on third step of checkout.
- Case 7
  - Featured product images should load without any problems.
KOD-22051: Move order templates to the operations portal
KOD-22053: Customer balance off between CSD and Kodaris
KOD-22104: Update Surcharging Note on Invoice templates
- Regression Tests
- Case 1
  - Check if you can generate email template and internal PDF file in Orders.
- Case 2
  - Check if orders in customer account are displaying correctly.
- Tests
- Case 1
  - Check if message in generated email and within internal pdf file is correct.
- Case 2
  - Check if message is correct on Orders within customer account.
KOD-22253: Search and Data tabs - Create a documentation
KOD-22331: Order As Needed Products - Presentation
KOD-22356: Update pricing engine logic
- Regression Tests
- Case 1
  - Make sure that pricing still shows up fine.
KOD-22392: Finalize AI Feature
KOD-22395: SASGE record when shipTo is blank, but state has data
- Regression Tests
- Case 1
  - When order is created and we calculate totals for magentoOrder (with taxEngine = Avalara), it should continue working as expected calculating taxes correctly and, if it checks the SASGE table, it should use the state from 'region_code' sent in the request.
  - Check if endpoint called is: /api/system/integration/magento/webhook/order/taxCalculationByID or /api/system/integration/magento/webhook/order/taxCalculation
- Tests
- Case 1
  - We need to corroborate that if the companyAddress used in the site has a ‘state’, that will be used to find the SASGE record.
  - We can confirm that it is being used by checking the logs and see something like:
  - [JS] Looking in SASGE table for code
  - or:
  - [JS] SASGE not found with shipto and state. Looking in SASGE table without shipto for code:
  - So, if there is a record in the SASGE table with state, it should find it and then use it for calculating if product is taxable or not.
  - Add an item in the cart controller with the operation logs open and confirm it.
  - Also, if there is another companyAddres, you could change it and it should re calculate again all the products in the cart. Check operation logs for this as well.
KOD-22408: BI for reporting orders put on e hold through Kodaris
KOD-22413: Open New ERP OE Journal Through API Call - Reconcile (Part 2)
KOD-22450: Order Automation
KOD-22472: Registration form updates
- Regression Tests
- Case 1
  - Go to Customer portal. Check if you can navigate to the Register page.
- Tests
- Case 1
  - Check if all input’s labels are in uppercase. All values entered in inputs are also in uppercase.
- Case 2
  - For FIRST NAME and LAST NAME there are limitation for 2+ characters and no special symbols.
  - When these restrictions are violated, the input will be red, near label will appear red and under input there will be information about violation.
- Case 3
  - For TYPE/DEPARTMENT there is dropdown with values from requirements, they supposed to be in uppercase.
- Case 4
  - For EMAIL it expects some input that is like email. There is some beginning, expect @ some text, then . and some text.
  - When it’s violated, the input will be red, near label will appear red and under input there will be information about violation.
- Case 5
  - For PHONE it expects 10 digit value. Also it automatically formats to (XXX) XXX-XXXX for better user experience.
  - When it’s violated, the input will be red, near label will appear red and under input there will be information about violation.
- Case 6
  - For ACCOUNT ID it expects 5 digit value. Also there is an '_?_' section, that can be clicked. After click, there will appear info box with 2 links, that leads to PDFs with explanations.
  - When it’s violated, the input will be red, near label will appear red and under input there will be information about violation.
- Case 7
  - For SHIP-TO SEQUENCE it expects 1-3 digit value.
  - When it’s violated, the input will be red, near label will appear red and under input there will be information about violation.
- Case 8
  - When you finish form correctly, there will be launched recaptcha (Dev Tools → Network, or check icon on right bottom corner) and form will be proceeded (Dev Tools → Network, enpoint response code 200).
  - Also, on place of Submit button there will be ‘Thank you' message from this ticket’s description.
  - If some required fields are empty, you will be scrolled to these fields with message to fill them for proceeding.
KOD-22487: Error on deleting payment methods investigation
KOD-22492: Kodaris - Support links on customer tickets
- Tests
- Case 1
  - Find a ticket with a hyperlink in its description.
  - Open the page with this ticket and confirm that the text with the hyperlink is displayed as a clickable link, and clicking on it opens the correct URL.
  - Confirm that we can edit the text containing the hyperlink, and step 1 still works as expected after the changes.
- Case 2
  - Confirm that the panel does not get overlapped by the table when changing the text type.
KOD-22494: Automatically Tag Customer Accounts to the Right Host/Site
KOD-22502: Saving the Sign Supply Wizard PDF File
KOD-22560: Roll out Updated Surcharge/Fee Language in Customer Payment Made Email
KOD-22564: Shop By Store Selection Updates
- Regression Tests
- Case 1
  - Make sure for guest and logged in users pages are working with no issues.
  - User should still be able to select different available warehouses from by selecting them on a panel with no issues. Selection result should be saved.
- Tests
- Case 1
  - As a logged in user make sure by default warehouse which is assigned to your customer is selected by default, not the one which is located nearby.
KOD-22598: Add Punchout to checkout
- Regression Tests
- Case 1
  - As punchout user go to the cart page and checkout.
  - Make sure cart page is loaded with no issues.
  - Make sure you’re able to see order items, use Next, Previous buttons.
  - On the last payment tab make sure it is loaded with no issues. You should be able to use functionality on this tab.
- Case 2
  - As a regular user (non-punchout user) make sure cart pages are loaded with no issues.
  - 3 top navigations tab should be available to you and work with no issues.
  - All 3 tabs should be available to you, check their functionality - it should remain the same.
- Tests
- Case 1
  - As punchout user go to cart page.
  - Make sure on the last tab.
  - You see Pay with Punchout tab with the button Place Order. By clicking this button you should be redirected automatically to the api/user/punchOut/cart URL and punch out order should be placed and cart should be cleared.
KOD-22600: Home page display
KOD-22604: Implementation - Warehouses
KOD-22616: Stock Quantity Formatting
- Regression Tests
- Case 1
  - For this regression test, we will look for a product with no inventory information and go to the product’s details page.
  - In this case, the “In Stock” section shouldn’t be displayed.
- Tests
- Case 1
  - For this test, we will look for a product with inventory quantity being greater than a thousand units and go to the product’s detail page.
  - In this case, you should see the stock quantity being formatted with a comma every three digits.
  - For quantities lower than a thousand, format should remain the same.
KOD-22617: Adding Request Quote Form to Product Page
- Regression Tests
- Case 1
  - For product detail pages which don’t have extra2 field:
  - Make sure those pages are loaded with no issues. All functionality should remain the same.
- Case 2
  - Product list/grid/catalog view for the products which don’t have extra2 field:
  - Make sure functionality remain the same. list/grid/catalog loaded with no issues.
  - You should be able to add product to a cart.
- Tests
- Case 1
  - For products with extra2 field on product detail page:
  - Make sure there is no such functionality on the page:
  - Pricing, skus, add to cart button.
  - Make sure you can see product name, code, supplier and form.
  - Request a Quote form should be added with such fields:
  - Name, Phone, Email and _Request a Quote_ Button.
- Case 2
  - Form functionality:
  - Make sure you can see recaptcha button at the bottom of the screen.
  - Fill out all form fields. Click Request a Quote button.
  - On successful submission make sure you can see Success message at the bottom of the form.
  - In the Operations Portal check tickets. Make sure new ticket was added.
  - Make sure ticket’s title is:
  - Form Submission - User Quote Request for Product product code.
  - In Ticket description you should see all submitted data and product code.
KOD-22620: Button Consistency Updates
KOD-22627: Accounts Receivable - Make all fields available on Search and Data tabs
- Tests
- Case 1
  - For this test we will go to the Accounts Receivable screen - Search tab.
  - We will use the Show / Hide Columns to display the recently added columns:
  - Autotimestamp,
  - Code,
  - CC Number,
  - Discount Amount,
  - Doc ID,
  - Doc Type,
  - Extra 1,
  - Extra 2,
  - Extra 3,
  - Journal Number,
  - Note Count,
  - Customer Note Count,
  - Processor Class Name,
  - Sequence Number,
  - Set Number,
  - Source Modified Time,
  - State,
  - Value 1,
  - Value 2,
  - Value 3,
  - Value 4,
  - Value 5,
  - Value 6,
  - Value 7,
  - Value 8,
  - Value Field Labels,
  - Payment Code,
  - Payment Profile ID,
  - Source Code,
  - Company Address Name,
  - Payment Order IDs,
  - Misc 5,
  - Company Address 1
- |Case 2
  - For this test we will go to the Accounts Receivable screen - Data tab.
  - We will use the Show / Hide Columns to display the recently added columns:
  - Company Code,
  - Company Name,
  - Web Payment ID,
  - Amount To Pay.
  - Apart from displaying them, you should be able to edit some of the fields.
  - Fields that accept editing are:
  - Web Payment ID and Amount To Pay.
  - We can verify that the information was saved successfully by reloading the grid.
KOD-22635: Indexing parent order number to find associated orders
- Tests
- Case 1
  - For this test, we will go to Companies - Select a Company - Orders tab.
  - We will use the Show / Hide Columns button to display the two recently added columns:
  - Parent Order ID and Parent Order Number.
  - The correct information should be display for those columns, you can check that using the Network tab.
  - You should be able to use the searching functionality as well on that column and it should work properly.
KOD-22637: Tests passing non tax type to CSD
KOD-22643: Add interceptor for ticket assignment and user creation
KOD-22654: Direct Ship Demo
KOD-22659: Updates not Showing for Additional Items to Translate
- Regression Tests
- Case 1
- Check session expired modal and message if it’s working correctly and display message in default English language.
- Tests
- Case 1
  - In the operations portal set message in other language for each value from the list below.
  - In the customer portal check:
  - Session expired message.
KOD-22668: Employee App - Quick Order - Add company code to the Select Company dropdown
- Regression Tests
- Case 1
  - Go to Quick Order in the company search input verify:
  - Search results are displayed with company code first in bold then the company name.
KOD-22670: Fix close icon
- Regression Tests
- Case 1
  - Check that we still can open and close the register popup on desktop and mobile view.
- Case 2
  - Check that you can still login on desktop and mobile view.
- Tests
- Case 1
  - Check that the close icon looks properly on desktop and mobile view.
KOD-22671: Fix History tab under Lockbox screen
- Regression Tests
- Case 1
  - Open the lockbox page and confirm that it loads without errors.
  - Go to the history tab and confirm that it loads without errors.
- Case 2
  - Open the lockbox page and click the "Trigger Batch Out" button.
  - Confirm that a modal appears with fields and a submit button, then click the submit button.
  - Confirm that another modal appears with the content of our batch out.
  - Close the modal, go to the history tab, and confirm that the first record there has the same content as the batch out in the modal.
- Tests
- Case 1
  - Open the history tab and confirm that it only contains records with entityAction values of 'EDIFileUploadToERP', 'EDIFileUploadToERP-ERROR', and 'CSD_API_response_onApplyAccountPaymentInERP'.
  - Confirm that we can filter or search within the table.
KOD-22690: Implementation - Branding 2 hosts
KOD-22691: Add comment count to AR search screen
- Tests
- Case 1
  - New fields added in the entity and solr (This mean you can see them in development tab and also in the /search response):
  - customerNoteCount, noteCount, customerFileCount, internalFileCount
  - After deploying the ticket, we should see in the development tab that those fields will have values (If there is any comment/file in the payment).
  - If there is any, test that the counters are correct.
  - Then, test uploading a new InternalComment (noteCount).
  - Customer comment (customerNoteCount).
  - Internal File (InternalFileCount).
  - CustomerFile (customerFileCount) and make sure that the counts are updated fine.
KOD-22698: Import General Contractors on Companies
- Tests
- Case 1
  - Select import under Company → data.
  - Import a file with just ‘companyName’ (If we want those to be active as well, we need to add column ‘active').
  - Verify that companies are created with a code and customerType = ‘GeneralContractor’.
KOD-22700: Filter out Inactive Companies on Subcontractor Fields
- Regression Tests
- Case 1
  - Go to Jobs → open some Lead.
  - Check if autocomplete in subcontractors still working.
- Tests
- Case 1
  - Check for some inactive company.
  - Try to search it in Jobs → Lead → subcontractors.
  - Try to search for some active company, then set this company as inactive and try to search it again. (don’t forget refresh pages).
KOD-22706: Cache issue with cmsMenus
- Tests
- Case 1
  - Test cmsMenus multilingual cache issue was fixed and changes made for default CMS doesn’t override other cached CMS languages.
KOD-22720: Date not Showing in Invoiced Column on Order History
KOD-22724: AP Automation - Add tolerance when matching line items by total
KOD-22725: Branding + shipping methods
KOD-22729: Update skuNumber autocreation to include vendorCode if desired
KOD-22733: Update editor used for txt file preview
- Regression Tests
- Case 1
  - Check that previews of files with extensions like .csv, .pdf look good.
- Tests
- Case 1
  - Check that previews of files with a .txt extension look good.
KOD-22734: AI Search - Index all product vector lengths for testing purposes
KOD-22738: Display date with time for Completed column on Orders Search
- Regression Tests
- Case 1
  - Make sure Order Search loaded with no issues.
  - You should be able to filter/sort.
- Tests
- Case 1
  - On Orders Search make sure that in column Completed date is displayed with time.
KOD-22739: Ticket Templates - Investigating the issues
- Regression Tests
- Case 1
  - For this regression test, we will go to the Tickets screen.
  - We will click on Add ticket button.
  - We will fill the Title field, filling the Description field is optional. Then we will select a Template and click on Add.
  - You should be redirected to the ticket details page.
  - Make sure fields were prefilled in according to the selected template.
  - If you filled the description field you should see that value inside the Description input, if not you should see the Ticket template description value in that field.
  - We will go back to the tickets screen and reload to make sure our ticket was created successfully.
- Case 2
  - For this test we will go to Tickets - Select a ticket - Details tab.
  - We will go to the Ticket Type dropdown on the Misc section.
  - We should check that changing that option calls the correct Patch endpoint and modifies that property successfully.
- Tests
- Case 1
  - For this test we will go to Tickets - Create Ticket button.
  - We will try to create a ticket from a template that has an externalID declared.
  - You can verify that the template you will use has an externalID declared, if not you should add one for this test.
  - We should not see any errors this time and the ticket should be created successfully without inheriting the External ID property.
- Case 2
  - For this test we will go to Tickets - Select a ticket - Details tab.
  - We will go to the Ticket Type dropdown on the Misc section.
  - Now we should see the TicketTemplate option there. We will select it.
  - After waiting a little while, you should see that ticket on the Ticket Templates grid.
KOD-22742: Automatically assign tickets
KOD-22743: Updates to continuously sync documents
- Tests
- Case 1 - Paid date
  - Orders that have setting ‘paiddt’ will be considered for syncing documents. the setting paiddt might be in 2 different formats:
  - 1 - mm/dd/yy -> ex: 11/15/24
  - 2 - yyyy-mm-dd → ex: 2024-11-15
  - After reindexing all orders in solr, new field ‘paiddt’ will be available to search by.
  - The same endpoints will be available where you can specify the paid date as parameter.
  - Those are:
  - /api/system/integration/maxrecall/syncCustomerFilesAsync
  - and /api/system/integration/maxrecall/syncInternalFilesAsync
  - Open operation logs to see the orderIDs that are being processed.
  - Execute endpoint populating the paid date and then verify the following:
  - Go to system event and find the report: MAXRECALL_SyncOrderCustomerFiles where you can see the how many order where processed successfully and the ones with errors.
  - If there are orders with the field ‘companyCode’ which is in the setting: maxRecallExcludeCompanyCodes, those should be excluded from the sync.
  - Only orders that have the setting paiddt with a value should be synced. All those that don’t have the setting or it is null should be excluded.
  - If paidDateBefore was populated, only orders in that specific range will be synced. (For instance, If I have a paiddt setting in a order with date 2021-01-02 and I select paidDateSince = 2021-01-01 and paidDateBefore = 2021-01-03 then that order should be selected and any other with paiddt > 2021-01-03.
  - Finally, if there is any new document that should be synced, those should appear in the CustomerFile on the Order.
- Case 2 - paid date from DailyIntervalJob
  - The process will run daily but using the paidDate with 30d ago.
  - Here we can test new documents will be synced for each day using the paiddate < 30d ago.
  - Currently, if we want to test that the date is correct, we need to run the dailyIntervalJob (Or wait until next day) and verify in the logs which was the paid date used.
  - We will see a log similar like this:
  - Using the following dates - invoiceDateSince=null, invoiceDateBefore=null, paidDateSince=2024-10-20 09:31:04:000
KOD-22750: "Not Found" error when trying to price debug
KOD-22751: No emails when submitting forms
KOD-22752: UX for public tracking via URL (DQ)
KOD-22754: Add customerPaymentTemplateEnabled to employee config
KOD-22759: Implementation - Install applications
KOD-22760: Implementation - Branding
KOD-22767: Remove ability to facet on the Company Code field on Orders screen
- Tests
- Case 1
  - For this test, we will go to the Orders screen - Search tab.
  - We will use the Show / Hide Columns button to display the Company Code column.
  - The column should not be facetable now. You should be able to search using the input field.
KOD-22771: Custom Parser
KOD-22772: Custom Parser
KOD-22773: Custom Parser
KOD-22776: Add confirmation popup to confirm email resend
- Regression Tests
- Case 1
  - Make sure Emails grid is loaded with no issues.
- Case 2
  - Make sure action buttons on each row on the Emails grid are loaded with no issues and work as expected (except Resend Email button).
- Tests
- Case 1
  - Make sure spacing around each action button on each row on the Emails grid was increased.
- Case 2
  - Click Resend Email button.
  - Make sure you see popup window after click.
  - Make sure body contains all toEmails, all bccEmails (if available) and all ccEmails (if available) listed in the popup body.
  - Click resend.
  - Make sure you see success Snacker.
  - Make sure your email has been resent successfully.
- Case 3
  - Check the case when you have really long list of email recipients (toEmails), bccEmails and ccEmails.
  - No horizontal scroll should be added.
  - Email addresses should be displayed one per line.
KOD-22783: Custom homepage - Edit text on page
- Regression Tests
- Case 1
  - Check that on the main page the banner text under the navigation bar is displayed correctly.
  - Check that variable addresses work correctly in Customizer Theme (change text in footer blocks).
- Tests
- Case 1
  - Check that the Customizer Theme contains the Header Title and Header Text variables.
  - Check that when the variable value changes, the text and banner title data under the navigation bar also changes.
KOD-22784: Implementation - Update template
KOD-22785: Custom homepage - 3X3 image grid
- Regression Tests
- Case 1
  - Check that Home Content Tiles are displayed correctly on the website.
  - Check that the Home Content Tiles functionality (adding a tile, deleting, assigning a link to a tile) works fine.
  - Check that the Main text field is present in the customizer of the Top Brands section, the field is edited, and the text is added correctly.
- Tests
- Case 1
  - Check that in the Home Content Tiles customizer, Tile has the ability to add only a URL, but there is no option to add Main or Additional text.
KOD-22786: Custom Parser
KOD-22789: Payload mapping locations
KOD-22790: Kodaris - Fix Outlook Ticket Emails
KOD-22796: Update ERP Integration to Sync Weight on Products
KOD-22797: Update ERP Integration to not Display New Products on the Website
KOD-22800: Refresh taxes on cart and quote
KOD-22801: Customer part # added - updates
- Regression Tests
- Case 1
  - Check that all three templates are look good (in customer portal, email and pdf).
- Tests
- Case 1
  - If order has customer product code, you should see:
  - Customer Product: customer product code value for all three templates (in customer portal, email and pdf).
KOD-22803: Fix Escalation Units
KOD-22808: Custom homepage - Update shop by category color
- Regression Tests
- Case 1
  - Check that the “Shop by Category” block and the layout in general looks correct.
- Tests
- Case 1
  - Check that the dropdown block “Shop by Category” has the correct background color, as well as the correct background color when clicked (the color should be the same as in the subsection of other elements of the navigation bar, for example Shop by Market).
KOD-22809: Custom parser
KOD-22810: Ability to create host widgets
- Regression Tests
- Case 1
  - Make sure menus and widgets are still loading fine on the website.
- Case 2
  - Make sure menus are still loading/working fine in customizer.
- Tests
- Case 1
  - In customizer, you should be able to select host in dropdown and create/update menus with no issues.
  - The host menus should appear on the host website fine.
KOD-22834: Allow editing status on InternalFile
KOD-22837: Convert the table with support for editing, filtering, and sorting