9.4.0.0 Release Notes

February 14, 2020

New Features

[ZPD-8334/ZPD-7689/ZPD-7671] - Search Activity Reports

Administration


A new section Search Activity has been added under Search Settings in the Znode admin application.


This section showcases the following types of reports:

  • Top Keywords

  • No Results Found

Top Keywords Report:

This report provides statistical data about the keywords that customers (shoppers) use most frequently to search the web store.


No Results Found Report:

This report provides statistical data about the keywords that customers (shoppers) have searched and have not received any search results.



[ZPD-7813] - Google Analytics Integration with Znode

Administration


Admin users will now have the ability to view Google Analytics reports for every store from the Znode admin application.


This will require admin users to configure their Google Analytics account with the Znode application.



[ZPD-5770] - Recommendation Engine - Manual Recommendation Generation

Administration, Shopper Experience & Commerce


Znode now provides product recommendation capability which will allow admin users to generate product recommendations (manually) and display the new product recommendations on Home Page, Product Page and Cart Page of the web store (based on the setting).


This feature analyses the orders placed by all the customers (shoppers) and provides recommendations for products that the customers will be likely to purchase along with the products which they are currently viewing.

[ZPD-5970] - Date-Time Filter On Orders List Page

Administration


A large number of orders are received and saved in the Znode application on a regular basis. These orders are displayed on the Orders List page. Therefore a date-time filter has been introduced on the Orders List page which will allow admin users to filter the orders using custom or predefined date-time range options.

[ZPD-8291] - Cloudflare Integration With Znode

Commerce


Znode now supports Cloudflare services.


Following are the benefits of using Cloudflare with Znode:


Improved Security

Using Cloudflare with Znode will improve the security of the Znode application as it protects the application from DoS and DDoS attacks and also filters the bad traffic and protects the servers from automated bots and spammers.


Improved Performance

As the site traffic is filtered, only genuine traffic passes, therefore the hosting resources can serve actual users at a better speed.


Saves Hosting Bandwidth

Static content served as cache from Cloudflare saves on the hosting bandwidth



Enhancements

[ZPD-5709/ZPD-8160/ZPD-6965] - Create/Manage Order Changes

Administration


The UI of Create Order and Manage Order screens has been changed completely to make the elements of the screens more easy to understand and also to eliminate/reduce the number of clicks users had to perform to create/manage an order.


Also, the code written for creating the order from the admin application has been modified so that the same implementation can be used by the admin application and web store to create the orders.


These changes will enhance the admin users experience while creating/managing the order.





[ZPD-1615] - Facets Of Variants On Product Listing Page

Shopper Experience


Earlier, the facets of only the parent products (of type configurable or bundle or grouped) used to get displayed on the product listing page of the web store.


With this release, the facets of the child products (of parent type configurable or bundle or grouped) will also get displayed on the product listing page of the web store. 


Important: This change was initially released in Znode v9.2.1 but due to performance impacts it was reverted in the later release.

[ZPD-8286] - New User Registration Confirmation Messages

Shopper Experience


The confirmation messages for new user registrations have been updated so as to provide more information regarding the further steps to the customers (shoppers)


To implement this enhancement, changes were made in AdminApprovalSuccessMessage and EmailVerificationSuccessMessage keys of WebStore_Resources.resx file.

[ZPD-7564] - Webstore Address Fields New Order

Shopper Experience


The sequence of fields on the Edit Address screen on the web store has been updated as per relevance (only for the B2B oriented theme)




[ZPD-2966/ZLMC-53] - Account Name On Order Receipt

Administration & Shopper Experience


With this release, the Account Name will be displayed on the Order Receipts of the orders placed by customers (shoppers) who are associated with any Account.

[ZPD-5325] - Provision To Replace Media

Administration & Shopper Experience


Admin users will now have the ability to replace any existing media file with another media file of the same type so that the replaced media file is available in all the areas where the initial file was available.


Important: When an image file is replaced with another image file, it’s size will be automatically generated (i.e. Generate Image call would be initiated)


[ZPD-6229/ZLMC-622] - New Fields To Store Back Order Information

Administration


Two new static fields Backorder Quantity and Backorder Expected Date has been added on the Add/Edit Inventory pages. Admin users can save Backorder information in these fields against the selected SKU and Warehouse.


Important: These fields are not bound to the Backorder functionality, therefore different project teams can use these fields to customize the existing Backorder functionality.


[ZPD-7550] - Default Products Per Page Option

Administration & Shopper Experience


Admin users will now have the ability to set any predefined Products Per Page option as the default option so that by default certain number of products can be displayed on every product listing page.

[ZPD-7561] - Webstore - Account Navigation

Shopper Experience


The Slide Out Drawer for Account navigation has been replaced with Drop Down menu for a more user-friendly experience.

[ZPD-7748] - Brand Association With Store

Administration & Shopper Experience


Admin users will now have the ability to associate Brands with the Stores so that only the associated Brand(s) will get displayed on the Brands page and PDP page of the respective products.


Also, a provision to filter Brands starting with numeric value has been added on the Brands list page on the web-store.


Note: Sequence in which Brands will be displayed on the web-store will depend on the Display Order set from Manage Store screen. Therefore the Display Order column is removed from the Brands list page and the Display Order field is removed from the Add/Edit Brand screen.


[ZPD-8215] - Associate Users With Account

Administration


A provision to associate customers (shoppers) with the Account is added on the Manage Account screen (Users tab) in the Znode admin application.



[ZPD-7111/ZLMC-770] - Import Cost Price

Administration


With this release, admin users will have the ability to import the Cost Prices of products with the Pricing Import feature.



Issues Resolved

[ZPD-7616] - For CyberSource and PayPal payment methods, the Gateway Mode can be configured from the web.config file of the payment application and therefore the application never used to use the input saved against the Select Gateway Mode field (from Edit Payment Method screen) and therefore this field was removed for the said payment methods.


[ZPD-6859/ZLMC-697] - Web store - An incorrect Wishlist count used to display on the web-store for customers (shoppers) with multi-store access.


[ZPD-8889] - Admin & Web store - Personalized text (if added) did not use to get displayed on the Cart page for Grouped products because the message was not getting saved in the DB.


[ZPD-8065/ZPD-8066] - Admin - Personalized text of one product used to get removed if the same product with another personalization text was added to the cart from the Create Order screen.


[ZPD-9057] - Admin - Search Profile: Try It Yourself Not field did not use to work because of a null reference.


[ZPD-4884] - Admin - While creating an order, when a product with add-on was added to cart and the same product with another add-on was added to the cart, then the add-ons used to get merge with the same product.


[ZPD-6169/ZLMC-508/ZPD-8498/ZLMC-1080] - Web store - In Znode, the way of dealing with a genuine “Page Not Found” use case is to redirect users to a "404" content page. In such scenarios, the web-store used to display the correct web page to users but in the raw HTTP side, the application used to return a "302" or "307" status code.

Because the status code used was not 404, the search engines did not use to remove the non-existent pages from their indices.

Also, when the CMS page which was configured to display on the web-store when the 404 error was encountered, was disabled, the web-store used to display another error page


[ZPD-6518] - Admin- Default address was not getting displayed even when the address was available for admin users while creating the order.


[ZPD-7848] - Web store - Incorrect value for Sales Tax used to get calculated when an add-on was selected with the main product.


[ZPD-7870] - Web store - An incorrect validation message used to get displayed after adding the address from the Checkout page.


[ZPD-7944] - Admin - Whenever any form used to get submitted from the web store the uploaded file did not use to get displayed in the Manage <Form Name> screen in the admin application.


[ZPD-8114/ZLMC-1000] - Web store - Customers (shoppers) were able to view another customer’s (shopper’s) order details simply by changing the Order ID.


[ZPD-8216] - Webstore - After an order gets failed then if customers try to make Billing address same as Shipping address then the Email ID field used to get blank and when customers try to edit the Shipping address from the Checkout page and click on the Back option, the address fields used to get blank and 


[ZPD-8263] - Admin - The PO document did not use to get displayed on the Manage Order screen.


[ZPD-8325/ ZLMC-1036] - Web store - Instead of SEO Friendly Page Name, Product ID was getting displayed in the URL of the products.


[ZPD-8376/ZLMC-1041] - Admin & Web store - Brand images did not use to get generated using the Generate Image option because of which Brand images did not use to get displayed on the web-store.


[ZPD-8566] - Admin - Admin users were not able to create a CMS page because the application used to throw a validation message on Add New Page screen for SEO Friendly URL even when the appropriate input was added in the SEO Friendly URL field.


[ZPD-8701] - Admin - Admin users were unable to search customers (shoppers) associated with the account, using their full names from Manage Account >> Users screen.


[ZPD-8965/ZLMC-1113/ZPD-8969/ZLMC-1119] - A white border used to get attached to the images when they are resized.


Implementation Details

[ZPD-8334/ZPD-7689/ZPD-7671] - Search Activity Reports

Please refer to the following documents for more information on these:

Technical Document for Top Keywords Report

Technical Document for No Results Found Report


[ZPD-7813] - Google Analytics Integration with Znode

Please refer to the Technical Document for more information.


[ZPD-5770] - Recommendation Engine

Please refer to the Technical Document for more information.


[ZPD-5970] - Date-Time Filter On Orders List Page

Please refer to the Technical Document for more information.


[ZPD-8291] - Cloudflare Integration With Znode

Please refer to the Technical Document for more information.


[ZPD-5709/ZPD-8160/ZPD-6965] - Create/Manage Order Changes

Please refer to the following documents for more information on these:

Technical Document for Create Order screen changes

Technical Document for Create Order Code Optimizations

Technical Document for Manage Order screen changes


[ZPD-1615] - Facets Of Variants On Product Listing Page

Please refer to the Technical Document for more information.


Important: This change was initially released in Znode v9.2.1 but due to performance impacts it was reverted in the later release.


[ZPD-8286] - New User Registration Confirmation Messages

To implement this enhancement, changes were made in AdminApprovalSuccessMessage and EmailVerificationSuccessMessage keys of WebStore_Resources.resx file.

[ZPD-7564] - Webstore Address Fields New Order

To implement this enhancement, changes were made in EditAddress.cshtml (only for Maxwell’s Hardware theme)


[ZPD-2966/ZLMC-53] - Account Name On Order Receipt

To implement this enhancement, changes were made in the following:

  • GetOrderReceipt and ShowOrderAdditionalDetails methods of OrderService file

  • SetCustomerDetails method of UserService file

  • AddCustomerSuccessCallback method of Order.ts file

  • CreateCustomer.cshtml


[ZPD-5325] - Provision To Replace Media

Please refer to the Technical Document for more information.


Important: When an image file is replaced with another image file, it’s size will be automatically generated (i.e. Generate Image call would be initiated)


[ZPD-6229/ZLMC-622] - New Fields To Store Back Order Information

Please refer to the Technical Document for more information.


Important: These fields are not bound to the Backorder functionality, therefore different project teams can use these fields to customize the existing Backorder functionality.


[ZPD-7550] - Default Products Per Page Option

Please refer to the Technical Document for more information.


[ZPD-7561] - Webstore - Account Navigation

To implement this enhancement, changes were made in the following files  (only for Maxwell’s Hardware theme):

  • _AccountMenu.cshtml

  • header.scss

  • site.css

  • _Header.cshtml

  • _LoginPartial.cshtml

  • _AccountMenu.cshtml


[ZPD-7748] - Brand Association With Store

Please refer to the Technical Document for more information.


Note: Sequence in which Brands will be displayed on the web-store will depend on the Display Order set from the Manage Store screen. Therefore the Display Order column is removed from the Brands list page and the Display Order field is removed from the Add/Edit Brand screen.


[ZPD-8215] - Associate Users With Account

Please refer to the Technical Document for more information.


[ZPD-7111/ZLMC-770] - Import Cost Price

Please refer to the Technical Document for more information.


[ZPD-7616] - For CyberSource and PayPal payment methods, the Gateway Mode can be configured from the web.config file of the payment application and therefore the application never used to use the input saved against the Select Gateway Mode field (from Edit Payment Method screen) and therefore this field was removed for the said payment methods.

To resolve this issue, changes were made in the following files:

  • Admin_Resources.resx

  • ResourcesConstants.cs

  • Payment.ts

  • Payment.ts


[ZPD-6859/ZLMC-697] - Web store - An incorrect Wishlist count used to display on the web-store for customers (shoppers) with multi-store access.

To resolve this issue, a portalId column was added to the ZnodeUserWishList table.


[ZPD-8889] - Admin & Web store - Personalized text (if added) did not use to get displayed on the Cart page for Grouped products because the message was not getting saved in the DB.

To resolve this issue, a provision to save the message in DB was made.


[ZPD-8065/ZPD-8066] - Admin - Personalized text of one product used to get removed if the same product with another personalization text was added to the cart from the Create Order screen.

This issue got resolved with [ZPD-6965]


[ZPD-9057] - Admin - Search Profile: Try It Yourself Not field did not use to work because of a null reference.

To resolve this issue, BoostAndBuryList was initialized to new.


[ZPD-4884] - Admin - While creating an order, when a product with add-on was added to cart and the same product with another add-on was added to the cart, then the add-ons used to get merge with the same product.

This issue got resolved with [ZPD-6965]


[ZPD-6169/ZLMC-508/ZPD-8498/ZLMC-1080] - Web store - In Znode, the way of dealing with a genuine “Page Not Found” use case is to redirect users to a "404" content page. In such scenarios, the web-store used to display the correct web page to users but in the raw HTTP side, the application used to return a "302" or "307" status code.

Because the status code used was not 404, the search engines did not use to remove the non-existent pages from their indices.

Also, when the CMS page which was configured to display on the web-store when the 404 error was encountered, was disabled, the web-store used to display another error page

Please refer to the Technical Document for more information and solution.


[ZPD-6518] - Admin- Default address was not getting displayed even when the address was available for admin users while creating the order.

This issue got resolved with [ZPD-6965]


[ZPD-7848] - Web store - Incorrect value for Sales Tax used to get calculated when an add-on was selected with the main product.

To resolve this issue, changes were made in the following:

  • GetProductPrice, CalculateTaxForGroupProduct and Calculate methods of ZnodeTaxSalesTax.cs

  • ApplyDiscount method of ZnodeCartPromotionAmountOffOrder.cs file


[ZPD-7870] - Web store - An incorrect validation message used to get displayed after adding the address from the Checkout page.

To resolve this issue, changes were made in the following files:

  • ApplyGiftCard.cshtml

  • Checkout.ts

  • Resource.en.ts


[ZPD-7944] - Admin - Whenever any form used to get submitted from the web store the uploaded file did not use to get displayed in the Manage <Form Name> screen in the admin application.

To resolve this issue,

  • Changes were made in the following:

    • CreateFormTemplate, SendEmailNotification and SendEmailNotificationEmail methods of FormBuilderService.cs file

    • ZnodeConstant.cs file

    • SendCustomEmail method of ZnodeEmail.cs file

  • GetAttributeFiles method was added in FormBuilderService.cs file

  • SendEmail method was removed from FormBuilderService.cs file


[ZPD-8114/ZLMC-1000] - Web store - Customers (shoppers) were able to view another customer’s (shopper’s) order details simply by changing the Order ID.

To resolve this issue, changes were made in the following:

  • GetOrderById and GetOrderByOrderDetails methods of OrderService.cs file

  • GetOrderDetails method of UserAgent.cs file

  • OrderReceipt.cshtml  file

  • Webstore_resource file


[ZPD-8216] - Webstore - After an order gets failed then if customers try to make Billing address same as Shipping address then the Email ID field used to get blank and when customers try to edit the Shipping address from the Checkout page and click on the Back option, the address fields used to get blank and 

To resolve this issue, changes were made in UserAgent.cs file.


[ZPD-8263] - Admin - The PO document did not use to get displayed on the Manage Order screen.

To resolve this issue, changes were made in the following:

  • GetAjaxHeaders method of CheckoutController file

  • GetAuthorizationHeader method of BaseClient.cs file


[ZPD-8325/ ZLMC-1036] - Web store - Instead of SEO Friendly Page Name, Product ID was getting displayed in the URL of the products.

To resolve this issue, changes were made in the following:

  • Znode_GetPublishProductbulk SP

  • Znode_ImportSEODetails SP


[ZPD-8376/ZLMC-1041] - Admin & Web store - Brand images did not use to get generated using the Generate Image option because of which Brand images did not use to get displayed on the web-store.

To resolve this issue, changes were made in the following:

  • InvokeMethod, GenerateBrandImages and GetBrandData methods of ImageHelper file


[ZPD-8566] - Admin - Admin users were not able to create a CMS page because the application used to throw a validation message on Add New Page screen for SEO Friendly URL even when the appropriate input was added in the SEO Friendly URL field.

To resolve this issue, changes were made in the CheckSeoNameExist method of ContentAgent.cs file.


[ZPD-8701] - Admin - Admin users were unable to search customers (shoppers) associated with the account, using their full names from Manage Account >> Users screen.

To resolve this issue, changes were made in Znode_AdminUnassociatedUsers SP


[ZPD-8965/ZLMC-1113/ZPD-8969/ZLMC-1119] - A white border used to get attached to the images when they are resized.

To resolve this issue, changes were made in ImageHelper.cs file.


Breaking Changes

Please refer to the Breaking Changes Document to know more about the breaking changes.

Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.