View all releases

September 28, 2023 release notes

Highlights

Operations Portal

Update, filter, and sort customer files by extra field

The Kodaris platform has built-in five additional fields, labeled as "Extra" followed by a 1, 2, 3, 4 or 5, that can store any data you like in them and can be used for configuration or other purposes. As an employee, you can now edit, view, sort and filter customer files by the Extra 1 field on the System > Customer Files screen. Customer files are available on many entities in your Operations Portal including orders, quotes, products, etc.

To view the extra field, navigate to the System section of the platform and select Customer Files. Using the Show/Hide Columns icon, choose the Extra 1 field from the menu.

View customer files by entity

As mentioned in the highlight above, customer files are available on many different entities in your Kodaris system. They are files that your customers and/or public users can access and view when browsing products, viewing order history, etc.

In this release, we've made a second update to display the entity a customer file is attached to on the System > Customer Files screen. You can use this to easily check which entity a customer file is attached to.

Tickets

KOD-13957: FacetGroup Service
KOD-13963: Template Service
- Go to template list page, add few items to list, check sort and search column
- Server Side: check two endpoints:
- {{'POST' => '/api/system/template/list'}}
- {{'POST' => '/api/system/template/{templateID}/settings'}}
KOD-15014: ERP Logic Integration for Products - CSD
KOD-15032: Content - Set Up Home Page Content
KOD-15126: Privacy Policy
KOD-15326: PIM Status Changes for Breadcrumbs
- Case 1:
  - Choose category
  - Open Product Page
  - Make sure that product information displays correctly
  - Warehouse name/number is consistently sorted
KOD-16013: Display "Call for Availability" on OAN Items
- Case 1:
  - Please check if product list and grid view, as well as product pages, are displayed as usual
- Case 2:
  - Check if on product list and product pages inventory block is displayed as usual if product has specialOrder: false
KOD-16184: Updated Product Availability Messaging for Guest Users - Phase 1
KOD-16188: Add serverside API for Syncing Jira to Kodaris
KOD-16193: Choose Infor inforCSDSFOEOrderTotLoadV4.js Interceptor When Pushing Orders to CSD
KOD-16270: Add Details Tab to Global Purchase Order Screen
KOD-16311: Check SEO Schema Markup
- Case 1:
  - Check a website page
  - To update a page’s SEO tags
  - Go to the Operations Portal ? CMS ? Pages
  - Go to the page detail screen
  - Update the following fields (seo tag - corresponding field)
    - Title - Seo Title
    - Description - Seo Meta Description
    - Keywords - Keywords
    - OG Fields:
      - OG title
      - OG Description
      - OG URL
      - OG Type
      - OG Locale
- Case 2:
  - Check a category
  - To update a category’s SEO tags
  - Go to the Operations Portal ? PIM ? Categories
  - Go to the category detail screen
  - Update the following fields (seo tag - corresponding field)
    - Title - Seo title tag
    - Description - Seo Meta Description
    - Keywords - Keywords
    - OG Fields (currently not editable)
- Case 3:
  - Check a product
  - To update a product SEO tags
  - Go to the Operations Portal ? PIM ? Products
  - Go to the product detail screen
  - Update the following fields (seo tag - corresponding field)
    - Title - Name
    - Description - Short Description
    - Keywords - Keywords
- Regression Tests
- Case 1:
  - Check the following pages; these pages should have the following meta title:
  - Homepage - {{storeName}}
  - /spcu/login - {{storeName}} - Login
  - /spcu/cart-login - {{storeName}} - Cart Login
  - /spcu/contact - {{storeName}} - Contact
  - /spcu/quick-order - {{storeName}} - Quick Order
  - /spcu/checkout-thank-you - {{storeName}} - Thank You!
  - /spcu/credit-application-register - {{storeName}} - Credit Application - Sign up
  - /spcu/credit-application-thank-you -{{storeName}} - Credit Application - Thank You
  - /spcu/credit-application-password - {{storeName}} - 'Credit Application - Set Password
  - /spcu/cart - {{storeName}} - Cart
  - /spcu/account-retrieval - {{storeName}} Account Retrieval
  - /spcu/reset-password - {{storeName}} - Reset your Password
  - /spcu/error - {{storeName}} - Error
  - /spcu/registration-successful - {{storeName}} - Registration Successful
  - /spcu/saved-for-later" - {{storeName}} - Cart - Saved for Later
  - /spcu/cod-payment-thank-you - {{storeName}} - Payment Received
  - /spcu/sitemap" - {{storeName}} - Sitemap
  - /spcu/initialize-account - {{storeName}} - Initialize you Account
  - /spcu/sds-list - {{storeName}} - SDS Quick Search
KOD-16336: UX for Making Customer File extra1 Sortable, Filterable, Updateable
- Case 1:
  - Go to System ? Customer Files page, try to add new column to be shown ('Extra 1').
  - Then try to filter, sort and update its content.
- Case 2:
  - Go to System ? Customer Files, click on File ? Export, then click save.
  - You should be able to see exported file.
- Case 3:
  - Go to System ? Customer Files, try to add new column to be shown ('Folder').
  - Then try to filter and update its content.
KOD-16337: Add Ability to Set Store Phone Number in Utility Panel
KOD-16388: Employee Portal - Add Company Budgets Screen to System Cection
- Case 1:
  - Go to System ? Company Budgets page, try to create a new company budget using required fields.
  - Add a new column to a table and try to change its content if the field is editable; refresh the page to see if changes were saved.
- Case 2:
  - Go to the Details page of one of company budgets.
  - Try to change the content of some non readonly fields, then return to company budgets screen.
  - Refresh the page and the freshly added data should be displayed.
KOD-16405: Updates to Required Fields on Credit App
- Case 1:
  - Make sure that we can fill the credit application form, validate it correctly and sendTests
- Case 1:
  - Sign Up for credit with link
  - Login as customer with your new account
  - Read ticket details and please make sure that validation works as described in ticket story
- Case 2:
  - Physical address fields should be prefilled with business details above if all physical fields are empty
- Case 3:
  - If some physical address field is not empty, validation for all physical address fields should be turned on
- Case 4:
  - Check that we should have at least 2 suppliers with required name and email fields
KOD-16410: Send Confirmation Email When Payment Is Scheduled
- Case 1:
  - Paying Open invoice and COD
  - Make sure you get the customer and employee notifications
- Case 1:
  - Create scheduled payment for open invoice
KOD-16442: Add a Full CRUD API to Manage Vendor User Roles
- Case 1:
  - POST /api/system/vendorUserRole
- Case 2:
  - GET /api/system/vendorUserRole/{vendorUserRoleID}
- Case 3:
  - PUT /api/system/vendorUserRole/{vendorUserRoleID}
- Case 4:
  - DELETE /api/system/vendorUserRole/{vendorUserRoleID}
- Case 5:
  - PATCH /api/system/vendorUserRole/{vendorUserRoleID}
- Case 6:
  - POST /api/system/vendorUserRole/{vendorUserRoleID}/vendors
- Case 7:
  - POST /api/system/vendorUserRole/list
KOD-16445: Update Invoice Template to Match CSD Template
KOD-16450: CMS Templates by HostCode
KOD-16457: Logged in Inventory Availability Messaging
KOD-16466: Remove Period from Account Request Form
KOD-16472: Install Templates
KOD-16473: Employee App - Full Product Code Sometimes Required to Display Results
- Case 1:
  - Login to app as employee
  - Search in search bar for some product code
  - Results should display found products while typing
KOD-16484: Setup and Test the Jobs and Configuration for Statement Generation
KOD-16492: Line Item Notes Not Populating on Emails
KOD-16494: Don't Show Language Dropdown if Customer Isn't Multilingual
KOD-16501: Check Why ERP # Are Not Going Through
KOD-16504: Part 2 - Fix Period Buckets Query on Open Invoices Tab
KOD-16614: Payment Portal - Create externalCustomerURL Setting and Update Statement PDF
KOD-16613: Employee App - Double Search Bar and Button
- Case 1:
  - Login to the app
  - Go to the burger menu button
  - Press leads
  - Press search icon
  - There should only be 1 search bar
KOD-16635: When an Order Is Deleted Via the Data Tab Make Sure It Is Also Deleted From Index
KOD-16638: Convert Content to CMS
KOD-16646: Change Sign in Prompt
KOD-16647: Link Payment Portal in the Header to the External Payment Portal
KOD-16649: Remove Request Item From Checkout
- Case 1:
  - Please add some products to the cart, go there and above selected products we don’t have button '{{Request Custom Item}}'
- Case 2:
  - Clear the cart and there should be only one button ‘continue shopping’
KOD-16651: Take Guest Users to the Login Screen if They Try to Add to Cart
- Case 1:
  - Please check if all buttons that are on the screenshots included with this ticket work as usual for logged in user
  - Also on the mobile view, please check if quick order works as usual for logged in users
- Case 1.1
  - Please check if ‘add to cart’ buttons redirect guest user to the login page
- Case 2:
  - Please check if ‘add to quote’ buttons redirect guest user to the login page on mobile view ? quick order
KOD-16661: CMS Templates by HostCode - More Items
KOD-16662: SEO Enhancements
KOD-16673: QA - Commerce as a Logged In User
KOD-16672: QA - Commerce as a Public User
KOD-16670: QA - Company Branding & Auth Flows
KOD-16675: QA - DDA App on Android
KOD-16674: QA - Customer Portal
KOD-16678: Add readDetails Endpoint for Purchase Orders
- Case1
  - Test newly created endpoint GET {{/api/system/purchaseOrder/readDetails/{purchaseOrderID}}
KOD-16679: Custom Order Templates for Customer Specific Properties
- Case 1:
  - Employee Portal.
  - No company custom templates were set up.
  - Expected behavior:
    - Default templates are being used for.
    - Employee portal: email and pdf.
    - Customer Portal: order details.
- Case 2:
  - Guest user checkout.
  - Expected behavior:
    - Checkout works fine.
    - Thank you page looks good and uses the default template.
    - User receives email that uses the default template.
- Tests
- Case 1:
  - Employee Portal.
  - Company custom templates were set up.
  - Expected behavior:
    - Custom templates are being used for.
    - Employee portal: email and pdf.
    - Customer Portal: order details.
- Case 2:
  - Employee Portal
  - Company custom templates were set up.
  - Email template setting value was misspelled.
  - Configure email.
  - Expected behavior:
    - Unhandled error occurred message.
    - Error generating template error in logs.
- Case 3:
  - Employee Portal.
  - Company custom templates were set up.
  - Totals section for email, pdf, order details.
  - Expected behavior:
    - {{Shipping & Handling}} line shows shipping value (was renamed back from Shipping).
    - No extra messages for CHARGES or FREE shipping method.
    - {{Add'l Charges}} shows total charges (was renamed back from Handling).
    - Extra Charge line is always shown.
- Case 4:
  - Employee Portal.
  - No company custom templates were set up.
  - Totals section for email, pdf, order details.
  - Expected behavior:
    - Data presentation was not changed.
- Case 5:
  - Logged in user checkout.
  - Custom templates are not set.
  - Checkout works fine.
  - Thank you page looks good and uses the default template.
  - User receives email that uses the default template.
- Case 6:
  - Logged in user checkout.
  - Custom templates are set.
  - Checkout works fine.
  - Thank you page looks good and uses the custom template.
  - User receives email that uses the custom template.
KOD-16680: Order Template Updates for Web Entered Status
- Case 1:
  - Go to Customer Portal
  - Go to Orders screen
  - Shoose status ‘Saved’
  - Choose any of available orders
  - Check on details page:
    - Should be shown *Quote Date*
    - Should be shown *Quote No.*
- Case 2:
  - Go to Customer Portal
  - Go to Orders screen
  - Choose status ‘Saved’
  - Choose any of available orders
  - Click on button ‘print’
  - After PDF was downloaded, check following:
    - Should be shown *Quote Date*
    - Should be shown *Quote No.*
- Case 3:
  - Go to Customer Portal
  - Go to Orders screen
  - Choose status ‘{{Invoiced}}’ or '{{Paid}}'
  - Choose any of available orders
  - Check on details page:
    - Should be shown *Invoiced Date*
    - Should be shown *Invoiced No.*
- Case 4:
  - Go to Customer Portal
  - Go to Orders screen
  - Choose status ‘{{Invoiced}}’ or '{{Paid}}'
  - Choose any of available orders
  - Click on button ‘print’
  - After PDF was downloaded, check following:
    - Should be shown *Invoiced Date*
    - Should be shown *Invoiced No.*
- Case 5:
  - Go to Customer Portal
  - Go to Orders screen
  - Choose status ‘{{Cancelled}}’
  - Choose any of available orders
  - Check on Details page:
    - Should be shown *Order Date*
    - Should be shown *Order No.*
- Case 6:
  - Go to Customer Portal
  - Go to Orders screen
  - Choose status ‘{{Cancelled}}’
  - Choose any of available orders
  - Click on button ‘print’
  - After PDF was downloaded, check following:
    - Should be shown *Order Date*
    - Should be shown *Order No.*
- Case 7:
  - Go to Operations Portal
  - Go to Orders screen
  - Choose status ‘Received’
  - Choose any of available orders
  - Click on button ‘email order’
  - Click on button ‘configure’
  - DO NOT SEND EMAIL, ONLY CHECK VIEW*
  - Check following:
    - Should be shown *Order Date*
    - Should be shown *Order No.*
    - Subject is *Your Order Details*
    - Should be shown *ORDER* in right top corner
- Case 8:
  - Go to Operations Portal
  - Go to Orders screen
  - Choose status ‘Received’
  - Choose any of available orders
  - Click on button ‘generate pdf’
  - ONLY GENERATE INTERNAL FILE
  - After PDF was generated, check following:
    - Should be shown *Order Date*
    - Should be shown *Order No.*
- Case 9:
  - Go to Operations Portal
  - Go to Orders screen
  - Choose status ‘Paid’
  - Choose any of available orders
  - Click on button ‘email order’
  - Click on button ‘configure’
  - DO NOT SEND EMAIL, ONLY CHECK VIEW
  - Check following:
    - Should be shown *INVOICE Date*
    - Should be shown *INVOICE No.*
    - Subject is *Your Order Details*
    - Should be shown *INVOICE* in right top corner
- Case 10:
  - Go to Operations Portal
  - Go to Orders screen
  - Choose status ‘Paid’
  - Choose any of available orders
  - Click on button ‘generate pdf’
  - ONLY GENERATE INTERNAL FILE
  - After PDF was generated, check following:
    - Should be shown *INVOICE Date*
    - Should be shown *INVOICE No.*
- Tests
- Case 1:
  - Go to Customer Portal
  - Go to Orders screen
  - Choose status ‘web entered’
  - Choose any of available orders
  - Check on Details page:
    - *Order Date* changed to *Quote Date*
    - *Order No*. changed to *Quote No.*
- Case 2:
  - Go to Customer Portal
  - Go to Orders screen
  - Choose status ‘web entered’
  - Choose any of available orders
  - Click on button ‘print’
  - After PDF was downloaded, check following:
    - *Order Date* changed to *Quote Date*
    - *Order No*. changed to *Quote No.*
- Case 3:
  - Go to Operations Portal
  - Go to Orders screen
  - Choose status ‘web entered’
  - Choose any of available orders
  - Click on button ‘generate pdf’
  - ONLY GENERATE INTERNAL FILE
  - After PDF was generated, check following:
    - *Order Date* changed to *Quote Date*
    - *Order No*. changed to *Quote No.*
- Case 4:
  - Go to Operations Portal
  - Go to oOrders screen
  - Choose status ‘web entered’
  - Choose any of available orders
  - Click on button ‘email order’
  - Click on button ‘configure’
  - DO NOT SEND EMAIL, ONLY CHECK VIEW
  - Check following:
    - *Order Date* changed to *Quote Date*
    - Order No. changed to Quote No.
    - Subject is *_Your Quote Details_*
    - *INVOICE* changed to *QUOTE* in right top corner
    - Added missing Colon after Status
KOD-16682: PurchaseOrder Comments API Endpoints
- Case 1:
  - Swagger ? use endpoint:
    - {{/api/system/purchaseOrder/{purchaseOrderID}/customerNote/list}}
  - If {{purchaseOrderID}} find order with type different from {{Purchase Order}} then the exception has to be thrown.
  - If {{purchaseOrderID}} find order with status different from {{Master}} the exception has to be thrown.
  - If {{purchaseOrderID}} doesn’t find order the exception has to be thrown.
  - *Important!!!* Has to be workled only for roles: {{administrator}} {{superuser}} {{purchaseOrderView}} {{purchaseOrderEdit}}
- Case 2:
  - Swagger ? use endpoint:
    - {{/api/system/purchaseOrder/{purchaseOrderID}/customerNote}}
  - If {{purchaseOrderID}} find order with type different from {{Purchase Order}} then the exception has to be thrown.
  - If {{purchaseOrderID}} find order with status different from {{Master}} the exception has to be thrown.
  - If {{purchaseOrderID}} doesn’t find order the exception has to be thrown.
  - *Important!!!* Has to be workled only for roles: {{administrator}} {{superuser}} {{purchaseOrderEdit}}
KOD-16684: PurchaseOrder CustomerFile API Endpoints
- Case 1:
  - Swagger ? use endpoint: {{/api/system/purchaseOrder/{purchaseOrderID}/customerFile/upload}}
  - Check the endpoint for each role separately: {{administrator}}, {{superuser}}, {{purchaseOrderEdit}}.
  - If the {{type}} is empty then it has to set {{Other}} entity type by default.
  - If purchaseOrderID doesn’t have the {{Purchase Order}} order type or status isn’t {{Master}} throw an exception.
- Case 2:
  - Swagger ? use endpoint: {{/api/system/purchaseOrder/{purchaseOrderID}/customerFile/list}}
  - Check the endpoint for each role separately: {{administrator}}, {{superuser}}, {{purchaseOrderView}},{{purchaseOrderEdit}}.
  - If purchaseOrderID doesn’t have the {{Purchase Order}} order type or status isn’t {{Master}} throw an exception.
- Case 3:
  - Swagger ? use *DELETE* endpoint: {{/api/system/purchaseOrder/{purchaseOrderID}/customerFile/{customerFileID}}}
  - Check the endpoint for each role separately: {{administrator}}, {{superuser}}, {{purchaseOrderEdit}}.
  - The json has to have the property {{"deleted": true}} with a status code 200 OK.
  - If purchaseOrderID doesn’t have the {{Purchase Order}} order type or status isn’t {{Master}} throw an exception.
- Case 4:
  - Swagger ? use *GET* endpoint {{/api/system/purchaseOrder/{purchaseOrderID}/customerFile/{customerFileID}/view}}
  - Check the endpoint for each role separately: {{administrator}}, {{superuser}}, {{purchaseOrderEdit}}, {{purchaseOrderView}}.
KOD-16685: PurchaseOrder InternalFile API Endpoints
- Case 1:
  - Swagger ? use endpoint: {{/api/system/purchaseOrder/{purchaseOrderID}/internalFile/list}}
  - Check the endpoint for each role separately: {{administrator}}, {{superuser}}, {{purchaseOrderInternalFileView}}, {{purchaseOrderInternalFileEdit}}.
  - If purchaseOrderID doesn’t has the {{Purchase Order}} order type or status is’t {{Master}} throw an exception.
- Case 2:
  - Swagger ? use endpoint: {{/api/system/purchaseOrder/{purchaseOrderID}/internalFile/upload}}
  - Check the endpoint for each role separately: {{administrator}}, {{superuser}}, {{purchaseOrderInternalFileEdit}}.
  - If the {{type}} is empty then it has to set {{Other}} entity type by default.
  - If purchaseOrderID doesn’t have the {{Purchase Order}} order type or status isn’t {{Master}} throw an exception
- Case 3:
  - Swagger ? use *DELETE* endpoint:
  - {{/api/system/purchaseOrder/{purchaseOrderID}/internalFile/{internalFileID}}}
  - Check the endpoint for each role separately: {{administrator}}, {{superuser}}, {{purchaseOrderInternalFileDelete}}.
  - The json has to have the property {{"deleted": true}} with a status code 200 OK.
  - If purchaseOrderID doesn’t have the {{Purchase Order}} order type or status isn’t {{Master}} throw an exception.
- Case 4:
  - Swagger ? use *GET* endpoint {{/api/system/purchaseOrder/{purchaseOrderID}/internalFile/{internalFileID}/view}}
  - Check the endpoint for each role separately: {{administrator}}, {{superuser}}, {{purchaseOrderInternalFileView}}, {{purchaseOrderInternalFileEdit}}.
KOD-16687: PurchaseOrder Email API Endpoints
- Case 1:
  - Swagger ? use endpoint: {{/api/system/purchaseOrder/{purchaseOrderID}/email/list}}
  - If {{purchaseOrderID}} doesn’t exist then throws an exception that purchase order doesn’t exist.
  - If {{purchaseOrderID}} is exist then the status code has to be {{200 OK}} with some *content*.
  - We can check list of email for these roles: {{administrator}} {{superuser}} {{purchaseOrderView}} {{purchaseOrderEdit}}.
KOD-16690: PurchaseOrder Bulk Items Delete API Endpoint
- Case 1:
  - {{POST /api/system/purchaseOrder/{purchaseOrderID}/deleteItem/bulkItem}}
KOD-16689: PurchaseOrder Settings API Endpoint
- Case 1:
  - {{POST /api/system/purchaseOrder/{purchaseOrderID}/settings}}
KOD-16691: PurchaseOrder Dedicated Search DTO
- Case 1:
  - POST {{/api/system/purchaseOrder/search}}
  - Try this endpoint, should return new DTO
- Case 2:
  - GET {{/api/system/purchaseOrder/search/{purchaseOrderID}}}
  - Try this endpoint, should return new DTO
- Case 3:
  - GET {{/api/system/purchaseOrder/searchDetails/{purchaseOrderID}}}
  - Try this endpoint, should return new DTO
KOD-16697: QA - Website Branding & Auth Flows
KOD-16703: QA - Customer Portal
KOD-16702: QA - Commerce as a Logged in User
KOD-16701: QA - Commerce as a Logged in user
KOD-16700: QA - Commerce as a Public user
KOD-16699: QA - Commerce as a Public user
KOD-16698: QA - Website Branding & Auth Flows
KOD-16709: QA - Customer App on ios
KOD-16708: QA - Customer App on Android
KOD-16707: Customer App on Android
KOD-16706: QA - DDA App on Android
KOD-16705: QA - DDA App on Android
KOD-16704: QA - Customer Portal
KOD-16712: QA - Payments
KOD-16711: QA - Payments
KOD-16710: QA - Customer App on ios
KOD-16713: Unit Price and Total Not Shown in Order Items Grid - Customer Portal
KOD-16719: Your Password Has Been Reset Email goes to Old Admin
- Case 1:
  - Surf through the website and make sure the branding looks right, e.g., buttons, logos, etc.
- Case 2:
  - Go through the customer reset password flow and make sure the branding looks correct.
- Case 3:
  - Go through the employee reset password flow and make sure the branding looks correct, and the link goes to the Operations Portal instead of the administrator portal.
KOD-16720: Platform Infrastructure - Updating Kodaris Data From CSD when ERP settings are updated
KOD-16726: Create Vendor Invoice From Purchase Order File Upload
KOD-16732: Purchase Order and Vendor Invoices API Fixes
- Case 1:
  - Test VendorInvoice
- Case 2:
  - Test PurchaseOrder
KOD-16733: Show Entity Type and Entity ID Field in Products
- Case 1:
  - Go to System ? Customer Files and try to add entityID and entityType columns
KOD-16734: Test Embedded Portal
KOD-16750: Add Content Pages
KOD-16754: Feedback on Datamatx Documents
- Case 1:
  - Check Order Mailer PDF and Order PDF
  - Go to the Operations Portal ? Orders screen
  - Choose a sample order
  - Generate an order PDF; check the layout for the following changes:
    - Invoice numbers should be in the form of 11632502-02
    - Add “Remit To” wording
    - Ship To information should pull from delivery address
    - Price/Price Per/Extended $ values
    - Ship Via field is showing name/description
- Case 2:
  - Check Statement Mailer PDF
  - Go to the Operations Portal ? Companies screen
  - Choose a sample company
  - Generate a StatementPDFMailer and check the cash disc column if showing correctly
- Case 3:
  - Check Order Email, Order PDF and Order layouts and check that the invoice numbers should be in the form of 11632502-02 (2 digits after - )
KOD-16758: Update Statement with Fax Number
- Case 1:
  - Check the Statement PDF
  - Go to the Operations Portal ? Companies screen
  - Choose a sample company and go to the detail screen
  - Click on generate statement PDF icon
  - Check the Statement PDF for the following updates:
    - Replacement of Accounting Fax to Accounting Email
    - Removal of _1 in Customer Number sections
    - Update of the location at the bottom of the PDF to headquarters
KOD-16759: Update to Pull Average Cost instead of Standard
KOD-16764: Make /api/user/product/{code} Return HTML by Default
- Case 1
  - Open product page in browser; should be displayed with no issues
- Case 2:
  - Do the same for categories
- Tests
- Case 1:
  - Test that by default when no special headers are passed in request - {{api/user/product/{code}}} endpoint returns HTML representation (product page) instead of JSON product data.
    - This could not be tested in browser at it usually sends “Accept” header automatically.
    - In Swagger it is also has a selector for response content type.
  - Test with cURL utility:
    - Run command:
      - Without specific header
      - With “Accept“ header
      - In both cases expect to see long *HTML* in response
    - Run command:
      - Expect to see short JSON product data in response
      - With “Accept“ header
KOD-16768: Add Additional Pages for Website
KOD-16774: Missing Pages
KOD-16783: Make /api/user/category/{categoryCode} Return HTML by Default
- Regression Tests
- Case 1:
  - Open category page endpoint in browser - should be displayed with no issues
  - Also check viewing categories in customer mobile app
- Tests
- Case 1:
  - Test that by default when no special headers are passed in request - {{api/user/category/{categoryCode}}} endpoint returns HTML representation (category page) instead of JSON category data.
    - This could not be tested in browser at it usually sends “Accept” header automatically.
    - In Swagger it could not be tested either.
  - Test with cURL utility:
    - Run command:
      - Without specific header
      - With “Accept“ header
      - In both cases expect to see *HTML* in response
    - Run command:
      - Expect to see JSON category data in response
KOD-16786: Datamatx Invoices
KOD-16802: Send Video About CMS Editing
KOD-16850: CMS templates by HostCode - menus
- Regression Tests
- Case 1:
  - Go to Operations Portal ? CMS ? click on Menus.
  - Add and edit the “Menus” and make sure it works properly.
  - Also try editing the slider and make sure that works correctly.
  - Note: when adding an image to the slider, you shouldn't be able to edit the details.
- Case 2:
  - Go to Operations Portal ? CMS ? click on Menus.
  - Go to the French version of the page and make a French menu and slider version.
  - Then make sure it looks good on the actual website.
- Case 3
  - Also on the French version, check multilingual and make sure it is working.
- Tests
- Case 1:
  - Try to add new menus for different host.
  - Check if menus are displayed in the customizer, try to reload the page, and check if menus are displayed.
- Case 2:
  - Check if menus are displayed on website.