In this release, we've added a screen where you can manage your system's security settings. These settings include:
CORS - Allows cross-origin requests by setting appropriate response headers on the server. You can enable this if you'd like to allow third-party systems to connect to your API. Read more.
CORS Frames - Controls whether or not your website can be embedded into third-party applications. Read more about it here.
Same Site Cookie Setting - Controls whether or not a cookie is sent with cross-site requests, providing some protection against cross-site request forgery attacks. This should always be set to Strict unless you are using the system as a development environment and need to connect to it from local applications. Read more.
Content Security Policy - Controls which resources the user agent is allowed to load for your website. This helps guard against cross-site scripting attacks. Learn more here. If you'd like to embed third-party applications in your website (for example, a chat bot), update the content security policy via this screen to allow it to load.
CMS
Allow your customers to leave comments
You can now allow your customers to leave comments on your marketing and content pages. Comments are a great way to provide a place for conversations about your business, products, or articles. Both guest and logged in users can view comments but only logged in users can leave a comment. Once they've submitted a comment, the comment is flagged for review and will show up under the Customer Comments tab on your page in the operations portal. To approve and display a comment to the public, simply change the comment status to Approved.
If you'd like to have comments added to your website, please reach out to your account manager. It is available to you in the Kodaris platform but needs to be added to your specific implementation.
Operations Portal
Receive notifications when you are assigned to a company
In this release, we've added a new subscription option for your CRM that sends notifications when an employee has been assigned to a company. You can subscribe to these notifications by navigating to Account > Notifications and choosing Send alerts to Employee who was assigned to Company. You can also subscribe other employees to this notification by navigating to Operations > Employees > Notifications.
Tickets
KOD-13189: Add Additional Fields to Registration Form
1. Go to the login /spcu/login url and register /spcu/register screens in different Tabs. On each Tab open the Register Form. Check that there were 2 fields with labels City and State added (select input with displayed State options). Fill in the Form. Submit it.
2. Go to /operations/emails Tab in operations portal. Check Subject column in the Table. Search for the latest "Contact Form Submission" there. Preview the email by clicking the preview button on the right. Check that the content includes City and State and other data you've submitted.
Also test viewing order details in the customer portal. Make sure the invoice view shows fine.
KOD-13941: Update Customer Service
KOD-13953: Update Host Service
The main goal is to check if everything work the same as before:
1. Go to Hosts page on admin portal
The lists of Hosts in the table should contain same hosts as before.
2. Go to any Host page ? Custom fields. It is the place where settings table are shown.
Please make sure it is also showing same settings as before (all settings of chosen Hosts).
KOD-14003: BI - Metric updates
KOD-14167: Add Ability to Update Content Security Policy Items in Operations Portal
KOD-14221: Add Customer Comments
Open any content page.
Scenario for logged in user:
Type any comment and press submit button. If the comment is submitted successfully, the green message will appear with a success message. Otherwise, the red alert will appear with the text "Something went wrong..."
Go to the employee portal, and find your user. Click the CMS -> Pages tab and open this link /pages/search/207/customer-comments
Approve comments. After you approve, they should appear on the Kodaris demo site.
Scenario for not logged-in user:
If you are not logged in user, comment form won't be displayed.
KOD-14356: Check Currency Format on Product and Category Schema
The schema on Product list should be valid and "priceCurrency" should be three-letter ISO 4217 format and "price" should be number instead of text.
KOD-14444: Prepare screenshots for Customer App Listing
KOD-14466: Prepare screenshots for Customer App Listing
KOD-14544: Prepare screenshots for Customer App Listing
KOD-14674: UX for Warehouse Transfer Data
KOD-14740: Update Permissions for Theme Editor
KOD-14794: Improvements to AR Export UI
1. Ensure the UI explains that the export is limited to 1000 records.
2. For Mark as Exported, select no. For IncludeAlready Exported Data select Yes; for Start Date and End Date, leave them blank. Run the export. Ensure that it does not result in an empty file. If there are at least some records, it should mean it’s handling the dates right. Test with selected startDate and blank endDate and vice versa.
KOD-15120: Default P.O. Number Not Showing at Customer Checkout
Case 1:
Login as employee
Check the ARSS (CompanyAddress) defaultPO field is empty
Check ARSC (Company) customerDefaultPONumber field is empty
Open customer side and login
Add any of products to shopping cart
Go to Checkout page
Check that there's no default value in Purchase Order input
Case 2:
Login as employee
Check the ARSS (CompanyAddress) defaultPO field is empty
Check ARSC (Company) customerDefaultPONumber field is not empty or fill it
Open customer side and login
Add any of products to shopping cart
Go to Checkout page
Check that Purchase Order input contains Company.customerDefaultPONumber as default value
Case 3:
Login as employee
Check the ARSS (CompanyAddress) defaultPO field is empty or fill it
Open customer side and login
Add any of products to shopping cart
Go to Checkout page
Check that Purchase Order input contains CompanyAddress.defaultPO as default value
Regression: Test checking out works as usual
KOD-15139: CCPA Form
Go to /spcu/ccpa
Form should work exactly the same as previous
KOD-15154: Shipping Detail Fields are not Populating at checkout
Add the following setting and make it a 1.
dontOverwriteOrderDataWithBlankCompanyData
Create a procedure to using the comments below:
When a user first creates a cart, data is copied from Account Profile ? Cart.
If company has phone, email, it will overwrite those fields. If not, the data above should stay.
If company billing address is chosen and has phone, email those will be used. If not, the above should stay.
Important Notes:
This does not apply to Delivery Address. They can simply click the use billing as shipping to populate.
User information is only populated when the cart is first initialized. This is because it is copied into the cart and stays there unless company or address overwrites it. Changing something in the profile and then going back to an existing cart will have no effect.
The info above also applies to logging out and logging back in. If you had a cart, it will simply pull that cart back up with the original data it had in it.
Even if you clear your cart, it will still be the same as above.
The only time you will “start over” with new profile data is if you complete your order or didn’t have an order in the first place.
KOD-15180: Credit App - Need a default version added that enables customization
KOD-15258: Add Details Link to Vendor Invoice Data Screen
1. Open AR/AP -> Vendor Invoices
2. Open Data Tab in Vendor Invoices
3. Click the Details button
4. Vendor Invoices Details page should be opened
KOD-15262: Company Data Grid - Unable to Update Extra1 Field
Test updating extra1 field on company data grid screen
KOD-15266: Add "Enable Punchout" button in the Employee Portal to the Company Details screen
1. Open CRM -> Companies
2. Choose Company
3. Click ‘Add Punchout Customer’ button
4. Check that “Add Punchout Customer” modal is opened
5. Fill username in the modal
6. Press “Add" button
7. You will be redirected to Customer details screen
8. Check that request was sent successfully
9. Open Network Tab
10. Find request with url:’ /api/system/integration/punchOut/activateCompanyIntegration`,
11. Find “Integrations” section in the Customer details screen
12. Check that “Integrations” section includes PUNCHOUT
Regression tests:
The existing endpoint was changed from `/api/system/customer/${customerID}` to `/api/system/customer/readDetails/${customerID}`
There are two cases where the endpoint should be retested:
Case 1:
1. Open CRM -> Companies
2. Choose Company
3. Click on “Add Customer” button
4. Fill user name
5. Press “Add” button
6. Check that the customer was successfully added
7. You will be redirected to Customer details screen
Case 2:
1. Open CRM -> Companies
2. Choose Company
3. Open Customers Tab
4. Choose Customer and open Customer details page
5. Change any field, for example, First Name field
6. Check that Customer details page was successfully updated
KOD-15269: Add Punchout screen under Development menu
Pre-requirement:
Go to Employee Portal -> Development -> Punchout.
Case 1:
Make sure you see similar UX you can see on the linked screen.
Case 2:
Click on “Select Punchout System” dropdown.
Make sure it contains values stored in Global Setting as described in comment below.
Case 3:
Make sure “Select Company” autocomplete is working as expected and you’re able to select Company.
Case 4:
Select company from suggested in autocomplete.
Once you selected a company we’re fetching value for “Edit XSLT” code-editor value that is stored in Company -> Custom Fields tab under “punchOutOrderRequestXSLT” key.
KOD-15380: Fix or adjust the Owner and Supplier number in the credit app form
KOD-15390: Update categories and products to Include 'In Cart' Indicator
Regression:
1. Add products to the cart
# Make sure subtotal and quantity in the header was updated.
# Test that the checkout works as normal
You have to do all required steps in different tabs but in ONE browser window, as it requires same session.
1) Login as customer and add few products to your cart.
2) Go to swagger in the same instance and make request GET /api/user/cart/currentMiniCart, response should return productID’s from you current cart.
Test B:
1) Go back to your cart and delete one or few products from the cart.
2) Go to swagger in the same instance and make request GET /api/user/cart/currentMiniCart, response should return productID’s from you current cart reflecting recent changes (without deleted productID).
KOD-15394: Add Fields to Operations Portal
KOD-15399: Insulation Calculator not Displaying Expected Quantity of Bags
/api/user/product/{productID}/footageConversionFactor endpoint should return correct value.
Test that the reported issue was resolved and calculator works as expected.
KOD-15469: PIM editor bug issue in operations portal
Please complete next cases for:
1. Product Details Page.
2. Ticket Details Page.
3. Activity Details Page.
*leave the field - means click outside the field in order to blur it.
Case 1:
1. Open the details page.
2. Open Browser dev tools -> Network tab.
3. Focus Description field.
4. Without any changes leave the field.
5. Make sure there was no Patch request sent in Network tab.
Case 2:
1. Without leaving the page, focus the Description field again.
2. Make some changes.
3. Leave the field.
4. Make sure the field was saved (the Patch request was sent with the current field content).
Case 3:
1. Without leaving the page, focus the Description field again.
2. Make some changes and formatting.
3. Leave the field.
4. Make sure the field was saved with formatting.
Regression:
Make sure the Rich Text Editor field on Product Details Page, Ticket Details Page, Activity Details Page works as expected.
KOD-15501: Employee Job Description Field
Need a UX implementation
Regression test, view employees screen and test filtering them
KOD-15504: Add import tickets feature
It's only possible to test on API level until UX changes are done, endpoint for testing:
POST /api/system/mapped/any/file/{mappingCode}/{importType}/{fileType}, where
{mappingCode} - mapping-basicTicketUpload
{importType} - direct
{fileType} - csv
file - CSV file with data to import, you can find example in the attachment, 'code' field is required, all other fields related to Ticket could be added.
KOD-15510: Update fee on last tab of cart
KOD-15514: Punchout - add customerID field to endpoint response
Endpoint mentioned in description should now return customerID
