9.7.1 Release Notes

Release Date: January 14, 2022


TABLE OF CONTENTS


Highlights


Release Information

 

Znode 9.7.1 release includes some minor bug fixes, merging of certain changes from Znode versions 9.5.0.5, 9.6.6, 9.6.6.1, 9.3.2.21, 9.6.2.7, and 9.6.2.6 along with the following enhancements,

  • Custom Content Containers

  • Elasticsearch Upgrade

  • Search, Search Suggestion, Search Profile related  Enhancements

  • Captcha Implementation

  • Catalog Publish Enhancement

  • Account Security, Payment API Security Enhancement and Security Enhancements

  • Enhancement in Create Order Submit Workflow and many more

 

System Requirements


The following major updates are released with Znode version 9.7.1, therefore it is mandatory to install the following updates in the required systems before updating the Znode version to 9.7.1:

  • Elasticsearch has been upgraded from version 7.6 to the latest version 7.16.2

  • Java Development Kit (JDK) is upgraded from version 11 to version 17


Software/Framework Upgrades
[ZPD-15798/ZPD-17003] - Elasticsearch Upgrade

Elasticsearch has been upgraded from version 7.6 to 7.16.2


Breaking Changes and Important Points

 

Upgrade Path From Znode 9.6.5 And Znode 9.6.6

There will not be any upgrade path available from Znode 9.6.6 to Znode 9.7. The projects on Znode 9.6.5 can be upgraded to Znode 9.7, and projects on Znode 9.6.6 can only be upgraded to Znode 9.7.1. The below flow diagram explains the upgrade path for projects on Znode 9.6.5 and Znode 9.6.6 versions.

Note: Teams whose projects are on the Znode 9.6.6 version can now upgrade to Znode 9.7.1 to upgrade their projects.


Pending Orders/Pending Payments

  • When a Pending Order or Pending Payment Order is created, all the details which get saved in DB against the Order after Znode v9.7 will also be saved for Pending Orders and Pending Payment Orders.

  • When an Order Discount (promotion only) is applied to an in-progress Pending Order or Pending Payment Order, the Discount Amount will first be distributed among the line item items before a new Discount is applied.  Discount values will be saved along with the orders.

  • Shipping Discount (promotion only) amount will be displayed separately in the Pending Order or Pending Payment Order

  • Shipping Discounts (promotion only) will only be applicable on Shipping and not on Handling Charges.

  • Handling Charges will only be applicable for the entire Pending Order/Payment Order and not for line items.

  • When a voucher or a coupon is applied, an error message will be displayed on the Checkout page since the application of voucher and coupons is not allowed.

  • When a Pending Order/Payment order is created, the following information will also be saved along with the order:

    • Subtotal

    • Shipping (total and line item wise)

    • Handling Charges

    • Tax (total and line item wise)

    • Discount (all applied promotions and the discount value)

    • Shipping Discount (all applied promotions and the discount value)

    • Job/Project Name

    • Shipping Constraints

    • In Hands Date

    • Etc (i.e. other existing details and other similar details that were considered for Orders in 9.7)


Old Pending Orders/Payments

  • Since new columns have been introduced in the database for Pending Order/Payment Order, the information in the new columns will not be available for existing orders after an upgrade from a previous version. In order to migrate old orders, it is necessary for admin users to either reject the Pending Order/Payment Order and create a new one instead


Avalara Integration (VAT and Duty/Import)

The current implementation is done only for the Create/Manage Order and Create/Manage Quote workflows. This implementation will not have any impact on the Create/Manage Pending Order/Pending Payments workflow and it will work as-is for this version of Znode. So, if Avalara VAT and Import/Duty is tried along with the Create/Manage Pending Order/Pending Payments modules it won’t work and will result in miscalculations.

Note: Avalara VAT and Duty/Import integrations are currently not planned to be implemented for Create/Manage Returns modules.


Content Containers

Content Widgets labels, URLs, and file names in code are renamed to include containers instead of widgets and the workflow is changed. The implementation of the variants in the ContentContainers is completely different from how the variants in the widgets were implemented. A new Variant in the Container Widgets was created on the basis of the Locale and User profile whereas a new Variant in the Content Container is created using Store Names and User Profile.


Other Breaking Changes


Please refer to this Breaking Changes Document for more information.


Enhancements

[ZPD-15798] - Elasticsearch Upgrade

Commerce


ElasticSearch has been upgraded from version 7.6 to the latest version 7.16.2


[ZPD-16534/ZPD-16744] - Search Profile Enhancements

Administration / Shopper Experience

  • There are numerous enhancements made on the search profile which can be seen below:

    • Improvement in the basic search 

    • Improvement in the code 

    • Simplified admin

    • Simplified default search profile in Database

    • The search suggestions will work after 3 letters typed in Search

    • Help Text changes are being made in Query Type->Multi-match

  • There are modifications made in Marketing -> Site Search -> Search Profiles -> Add/Edit Search Profile

    • Following settings are now hidden from the Admin Screen:

      • Query Properties-> Query Type -> Match Phrase Prefix

      • Query Properties> Query Type -> Match 

      • Query Properties-> Query Type -> Match Phrase    

      • Minimum Should Match

      • Enable Accurate Scoring

    • Only two options will now be available in the Query Type

      • Multi Match - Cross: Multi Match query type searches text in multiple searchable fields. When Multi Match - Cross is selected text/keywords can be available across multiple searchable fields to bring the search results/suggestions.

      • Multi Match - Best: Multi Match query type searches text in multiple searchable fields. When Multi Match - Best is selected, all the searched text/keywords must be available combined in any one of the searchable fields.

  • One of the point to be noted here is that Elasticsearch does not support Cross with Autocorrect, so  if a user manually selects Multi Match - Cross and Autocorrect = Yes, then the data passed to Elasticsearch  would be “Multi Match - Cross and Autocorrect = No”

  • Default Search Profile is created in the database with some predefined values for all sections. Configurations set by default (i.e values to be stored in the database)

    • Searchable Fields:

      • SKU (no boosting value)

      • Product Name (no boosting value) 

    • Relevance Based Ranking - nothing selected 

    • Query Properties

      • Query Type 

        • Multi Match - Cross 

        • Operator = AND 

        • Autocorrect = No

    • Facet

      • Brand

  • Following are some technical changes done:

    • Ngram Token filter will be used only for SKU, Product Name, and Brand in searchable fields for index time

Note: Ngram will not work on other searchable fields. Project-specific teams will have to customize accordingly

  • While Ngram is used, it is required to set a minimum length=1 (Min gram) and maximum length=40 (Max gram) for token generation

Note: Min/Max gram values will be in code. Project-specific team will have to configure accordingly if lengths of Min/Max gram are to be changed

  • Character filter would be applied to special characters i.e Underscore (_), and Dashes/ Hyphen/Minus (-) along with their mapping in the code to obtain the desired output 

Note: Mapping would be defined in the code. Project-specific teams will have to configure the mapping for other special characters if needed 

  • standard_ngram_analyzer would be used during index time for all fields, token filters will be applied in the following sequence:

    • Lowercase

    • Synonyms

    • Stopwords

    • Ngram (only applicable for SKU, Brand and Product Name)

    • Shingle

  • standard_search_synonym_analyzer Analyzer would be used during search time, token filters will be applied in the following sequence:

    • Lowercase

    • Stopwords

    • Stemming-Porter

    • Shingle

  • didYouMean_analyzer would be used during search time, token filters will be applied in the following sequence:

    • Lowercase

    • Synonyms

    • Stopwords

    • Ngram (only applicable for SKU, Brand and Product Name)

    • Shingle

  • Stemmer-Porter would be used at query time 



[ZPD-16542/ZPD-16541] - Search Suggestion Improvements

Shopper Experience

There are a couple of changes made in the search suggestion feature to further enhance and make it more user-friendly. The changes made here are as follows

  • A product image will now be displayed along with every product suggestion. The image and product name both will be hyperlinked and will take users to the search results page.

  • Category Name (displayed along with the product) will also be hyperlinked and will take users to the respective category page.

  • Product Suggestions for different product types will be as follows:

    • For a simple product, the respective simple product’s image should be displayed.

    • For a bundled product, the respective parent product’s image should be displayed.

    • For a configurable product, the respective parent product’s image should be displayed.

    • For a grouped product, the respective parent product’s image should be displayed.


[ZPD-16394/ZLMC-3049/ZPD-16138/ZLMC-2933] - Search Result Improvements

Shopper Experience

There are numerous enhancements made on the search profile which can be seen below:

  • The hardcode configuration of the GetAutoSuggestions method  is removed to make it flexible

  • Search term present in the prefix will now be displayed on the top of the search. In order to boost the prefix , wildcard queries are used.


[ZPD-14750] - Changes In Pending Order/Payment Calculations

Administration / Shopper Experience

The following new changes are introduced for Discount, Shipping, and Tax calculations for Pending Order/Payment Orders so that they can be managed and processed easily:

  • When a Pending Order or Pending Payment Order is created, all the details which get saved in DB against the Order after Znode v9.7 will also be saved for Pending Orders and Pending Payment Orders.

  • When an Order Discount (promotion only) is applied to an in-progress Pending Order or Pending Payment Order, the Discount Amount will first be distributed among the line item items before a new Discount is applied.  Discount values will be saved along with the orders.

  • Shipping Discount (promotion only) amount will be displayed separately in the Pending Order or Pending Payment Order

  • Shipping Discounts (promotion only) will only be applicable on Shipping and not on Handling Charges.

  • Handling Charges will only be applicable for the entire Pending Order/Payment Order and not for line items.

  • When a voucher or a coupon is applied, an error message will be displayed on the Checkout page since the application of voucher and coupons is not allowed.

  • When Pending Order/Payment Order is created, the following information from the respective product(s) will be saved against the Pending Order/Payment Order and will not changed unless the Pending Order/Payment Order is converted to Order:

  • Subtotal

  • Shipping (total and line item wise)

  • Handling Charges

  • Tax (total and line item wise)

  • Discount (all applied promotions and the discount value)

  • Shipping Discount (all applied promotions and the discount value)

  • Job/Project Name

  • Shipping Constraints

  • In Hands Date

  • Etc (i.e. other existing details and other similar details that were considered for Orders in 9.7)

  • The changes will only reflect in Orders and not in Pending Order/Payment Order


[ZPD-14565] - Avalara Integration (VAT and Duty/Import)

Administration / Shopper Experience

When shipping to a different country, it is necessary to pay import taxes or any related taxes that are applicable when the product reaches the destination country. Using Avalara this can now be accomplished wherein the system will calculate the import taxes and VAT in the destination country which can then be collected through Znode. The current implementation is done only for the create/manage order and create/manage quotes. Pending order/Pending Payments and returns will have no impact with this implementation and they will work as-is for this version of Znode.


[ZPD-15459/ZLMC-2716] - Hangfire Scheduler Configurations

Administration

The fields  to select a date and time and configure a recurring job using a Cron expression is now implemented in the Add/Update Scheduler pop up. The Add/Update Scheduler popup will now have the following options available for defining a schedule for job execution:

  • One Time: The purpose is to configure a job execution scheduler, which will only execute once as per the start date and the time specified. The behavior of the start date and time will be the same as prior and no changes are applied.

  • Recurring: The purpose is to configure a scheduler using a Cron Expression so that the job executes multiple times a day, or runs on specific days and months as per the defined schedule for the job execution

Also, a section to display the Hangfire dashboard is added under Dev Center >> Diagnostics & Maintenance section so that admin users can view the various configured/scheduled/completed jobs.




[ZPD-15097] - Enhancement in Create Order Submit Workflow

Commerce

While submitting the order, the order will now be stored first in the Znode database and after successful storage, it will go for the payment processing. Also for the payment processing, an iframe payment tokenizer is used. Using this iframe payment tokenizer the credit card payments will not be controlled at Znode level which will result in limited calls to payment API. 

Note: This iframe payment tokenizer will be limited to specific payment gateways. For other payment gateways that do not support iframe payment tokenizer, the payment flow will work as it was working previously.


[ZPD-13449] - Content Containers

Administration / Shopper Experience

A provision to create content containers is provided to the admin users who can create/manage structured and personalized content for different user groups and the content can then be displayed on the Web Store based on the user group. A new Variant in the Content Container can be  created using Store Names and User Profile and its data can be configured against different locales. Also, the Publish option is now available on the Container level as well as on the Variant level.

Now, a vital point here is that the, content containers module development is independent thus, when CMS Content/Store Experience is published, the content container and its variants will not get published  like other CMS modules (like pages, content blocks, blog/news, etc)

When a content container is configured on the web store, the application will check the Store, the user profile that is being used on the web store, and the selected locale to identify the published container and published variant whose data will be displayed on the webstore.


[ZPD-15566] - Provision To Publish Draft or All Products With Catalog Publish

Administration

Admin users will now have a provision to decide whether to publish only products which are in “Draft State” or publish all products available in the Catalog. For the same, a new setting is introduced in the Catalog publish popup in the admin application which will indicate whether only the products available in a draft mode need to be published (default option) or all products will be published when the Catalog is set to publish. This setting is added in all the publish popups from where catalog can be published.


 

[ZPD-16160] - Enable/Disable Barcode Scanner

Administration / Shopper Experience

A new setting has been added on the Stores & Reps >> Stores >> Manage Store - General to enable/disable the barcode scanner feature on the Web Store.


 

 

[ZPD-15794/ZLMC-2835] - Captcha For Login Page

Administration / Shopper Experience


To prevent malicious attacks on the log-in page, the captcha feature has been implemented. For the same, an additional setting namely  ‘Is Captcha Required for Login’ is introduced on Stores & Reps >> Stores >> Manage Store - Additional Attributes section to turn the captcha On or Off on the login page for that specific store. One of the important points here is that Captcha will be case insensitive  by default (i.e User can add Captcha with caps on or off, the application will not throw an error)


[ZPD-16349] - Changes In Voucher Email Templates

Administration

Modifications are made to the following email templates:

  • Voucher Expiration Reminder Email (used for notifying customers that their voucher is about to expire.) 

  • New Voucher Issued For Customer (used for notifying customers that a new voucher has been issued for their account).

  • Remaining Voucher Balance (used for notifying customers that the voucher associated with their account has been used for an order). 


[ZPD-14971/ZLMC-2579] - New Filters On Products List Page

Administration

New filters "Status" and "Publish Status" are added to the Admin Products filter section.


[ZPD-15872] - Payment API Security Enhancement

Commerce

The token utilization process for user authentication has been improved. This enhancement has made the Payment API utilization more secure.

Important: The basic authorization is removed and a GUID and private key-based authorization is used.


[ZPD-13573] - Account Security

Shopper Experience

A new feature is introduced for securing a user account wherein if a user tries to create an account on the Web Store by using an already registered email or a username, then an email will be sent through Registration Attempt Using Existing Username email template on the entered email address (or the associated email address in case if the username is entered) notifying that the registration attempt was made along with reset the password link. This notification will be sent only once throughout a day even if the user tries to register multiple times


[ZPD-16027/ZPD-15338/ZPD-15279/ZPD-15251/ZPD-15246/ZPD-15197/ZPD-15182/ZPD-15597/ZPD-15428] - Security Improvements

Commerce

A lot of security enhancements have been made which are as follows:

  • An additional layer of protection is provided to the orderstate parameters by encoding the JS which eliminates its vulnerability to the reflected Cross Site Scripting and will protect the sensitive information

  • An additional layer of protection is provided to the search box by encoding the text value which eliminates its vulnerability to the Cross Site Scripting

  • The applications authorization policy was improved for protecting the complete user information

  • Proper authorization checks have  been implemented to protect the user address information 

  • Validations are made on the product SKU parameter to avoid any malicious injections into the system

  • Once the user logs out of the system, the related cookies data will now be cleared and certain validations are set  to further secure the user account

  • Visa Security enhancements are also been made

[ZPD-13822] - Performance: Web Store

Shopper Experience

The performance of the Web Store has been improved by reducing the number of Ajax calls  and also through the creation JS or CSS bundles

Issues Resolved


[ZPD-16199] - Admin - A Simple Select Type Attribute was created and was enabled to show on the grid. The attribute was then assigned to a few products. But when tried to filter out the products on the product list page in the Admin through the newly created column, the filter was not working

 

[ZPD-16099] - Admin - Reports - In the reports section, navigation was not displaying for the custom reports on the Add New screen

 

[ZPD-16054] - Admin - On the Manage User screen, when the Account lookup button was clicked, the Portal ID was present in the columns which were not required.

 

[ZPD-15947] - Web Store - On the Web Store, when a locale was selected it was not getting highlighted 

 

[ZPD-15825] - Web Store - A news/blog was created and a future date was specified as an activation date. But once it was saved, on the web store, the news/blog was available as the system was considering the creation date and not the activation date.

 

[ZPD-15729] - Admin - In the Advance Report section of the Reports, all the tabs were displayed as selected which should highlight only the one that is currently selected.

 

[ZPD-15706] - Web Store - When a pending order was submitted, the Store Logo was missing in the approval mail.

 

[ZPD-15679] - Admin - Under the Manage Guest User section, unchecking "IS DEFAULT SHIPPING" and "ADDRESS" from columns was not working as expected

 

[ZPD-15645] - Web Store - When a Quote was submitted, the font size of the description in the email templates for the Quote Request Acknowledgement, Quote Converted To Order Acknowledgement, and New Quote Request was not as per the standard size

 

[ZPD-14492] - Commerce - B2B Theme is now ADA Level A Compliant

 

[ZPD-15629] - Web Store - The pending payment order receipt UI was disturbed for the customer when opening the pending payment order through the account navigation

 

[ZPD-15587] - Web Store - The best seller product was configured in the quote receipt but they were missing on the thank you quote receipt page

 

[ZPD-15548] - Admin - A quote was submitted through the web store. After submitting the quote, the price list was deactivated. Then on the manage quote screen when the price of a product was updated, the product quantity was showing  out of stock message

 

[ZPD-15463] - Web Store - A bundled product was created with an inventory added for both the parent as well as the child product and purchasing was disabled. On the quick order page in the multiple tab section added this new product which resulted in taking the page into a loading state

 

[ZPD-15292] - Web Store - A wrong zip code was entered and the system showed a validation message. But the system continued to show the validation message even after removing the zip code

 

[ZPD-15219] - Admin and Web Store - While placing a return for an order,  the loader was missing and the return receipt was generated directly

 

[ZPD-15195] - Web Store - A voucher was applied on the checkout page and when another voucher was applied, the  voucher block size was getting changed

 

[ZPD-15193] - Web Store - Reviews submitted on products were not getting displayed immediately

 

[ZPD-15190] - Web Store - A group product with a personalization text option order was created. After that when the order status was checked, the personalized attribute code was seen against the product which should be the personalized attribute label

 

[ZPD-15092] - Web Store - While managing a pending order from the Web Store, a text line missing above the order total

 

[ZPD-14994] - Web Store - In the case of Address Auto suggestion, upon selection of an address, it was not saving the same against the shipping and billing address

 

[ZPD-14903] - Commerce - The Company name was not seen over the Authorize.net payment gateway transaction details screen for a placed order

 

[ZPD-14447] - Web Store - Add ons associated with a product were removed but the add ons were still visible on the product description page for the product

 

[ZPD-13747] - Web Store - Non refunded amount field was missing on the create return screen

 

[ZPD-13652] - Admin - In the manage store section, in the tax tab, an unnecessary column namely Portalid was displayed in the columns action

 

[ZPD-13552] - Admin - In the promotions and coupon section, while associating a catalog for the amount off catalog discount type, certain filters were applied. But upon clearing those filters   dirty popup was getting displayed

 

[ZPD-13306] - Admin - When a new page was created through the CMS section and a new payment link was added in the payment option of the content tab, the UI was getting disturbed

 

[ZPD-13018]  - Web Store - While creating an order, the handling charges were visible on the checkout page but after submitting the order, the handling charge was not displayed on the thank you page

 

[ZPD-11723] - Web Store - While creating a pending order, a voucher was applied and the order was submitted. Upon submitting the order, the Voucher amount was not getting displayed on the receipt and pending order details page

 

[ZPD-10513] - Web Store - When a very old user who did not access the application for a very long time tried to log in to the application, the application redirected to the reset password page and the UI for the page was disturbed

 

[ZPD-16111/ZLMC-2923] - Admin and Web Store - When a single product publish was carried out, the attributes whose type was simple/multi-select, their values were not getting published for other locales

 

[ZPD-15468] - Commerce - Correction was made in the spelling of the generate token API endpoint

 

[ZPD-11463] - Web Store - An order template was created wherein maximum quantity for a specific product was defined. But more than the maximum quantity defined in the order template was allowed to be added to the cart

 

[ZPD-6816] - Web Store - For one of the payment methods, the hide billing address flag was set ON, but when the same payment method was selected for payment, still the billing address was visible on the check out page

 

[ZPD-15807/ZLMC-2841] - Admin - Expired vouchers were not visible in the Admin

To resolve this issue, changes were made in the List method of GiftCardController.cs file

 

[ZPD-15812] - Admin - While importing Customer Address, the system updated the customer address without looking into the associated username entered in the uploaded import file

 

[ZPD-15221] - Web Store - While creating a return, when the return quantity entered for a line item was greater than the available quantity,  Save As Draft and Submit Return button were displaying

 

[ZPD-12595] - Admin and Web Store -  Broken UI of various print receipts were fixed

 

[ZPD-13606] - Admin - An order was created from the admin end with a product having addon associated with it and then when a grouped product was added in the cart, the quantity box for the previously added product was highlighted in red

 

[ZPD-14780] - Web Store - A bundled product was created with addons and was added to the cart. Same bundled product was added to the cart without addons. The product was observed to be getting merged on the cart page with addon and without addon

 

[ZPD-15734] - Admin - Add button, Back Button, and Save Button UI was inappropriate on the Custom reports list page and add new report page

 

[ZPD-15934/ZLMC-2867] - Admin - Timeout errors were noticed when trying to pull abandoned cart reports from the advance reports section where the date range spanned over a year.

 

[ZPD-13662] - Admin and Web Store - Inconsistency was observed for the Shipping and Tax fields on the create return screen while creating a return from the Admin end in comparison to the Web Store

 

[ZPD-9654/ZLMC-1258] - Admin - When multiple catalogs were available and one catalog was published, the Status of categories of other catalogs changed to "Preview".

 

[ZPD-12693] - Web Store - In the Firefox web browser while creating a return for a specific order, a quantity was defined and the page was refreshed. After doing so the page blanked out and the only information seen on the page was the order number which was displaying 0 .

 

[ZPD-15696] - Web Store - A product was added to the cart, the voucher was applied on the same and the voucher amount was showing equal to the order amount. But when again a product was added to the cart, a voucher with $0.00 was getting applied

 

[ZPD-14716] - Web Store - The configurable PDP page of a web store was opened through the firefox browser. The attributes were configured for that product and the page was refreshed. After the page refresh, the product on the page was different as well the attributes selected were different 

 

[ZPD-15280/ZLMC-2687] - Commerce - A new admin user was created with a prime user role. When tried to reset the password for this user, the reset password link received was with reference to the web store user and not with reference to the admin user

 

[ZPD-15505/ZLMC-2747] - Web Store - When added same product to cart as a guest and logged in user, cart quantity was not getting updated and also any new products added in the cart as guest user were also not present in the cart when logged in. 

 

[ZPD-15870] - Web Store - A product was made unavailable in the catalog that was being used on the web store (Store/Account/User Profile based catalog). When the user opened the SEO URL or the product id URL, it was not redirecting to the 404 page 

 

[ZPD-15901] - Admin - A global store attribute and the group was created.  But when the attribute was associated to the group and the group was associated to the store family there was an error message being displayed by the system

 

[ZPD-15745] - Admin - The product highlight image is now managed with the product attribute swatch but the product highlight image attribute was still present in the product highlight section

 

[ZPD-15009/ZLMC-2599] - Admin and Web Store - Certain City/State/Territories were missing in the address dropdown on the checkout page

 

[ZPD-15705/ZLMC-2793] - Admin and Web Store - The #FirstName# macro in the Reset Password email sent to the user was showing the email address which actually should be the first name of the person.

 

[ZPD-15742] - Admin - When a new product was created, the default value of the attribute was not getting displayed/selected by default. Also, when a new attribute was added to a family and then an existing product was edited, the default value of attribute was not getting displayed/selected by default

 

[ZPD-15123/ZLMC-2636] - Web Store - After logging in on the web store and hovering on the category panel multiple times resulted in showing duplicate categories 

 

[ZPD-15555/ZLMC-2758] - Admin - Some Global Attributes were created and were placed in their own Group.The group was showing in the Stores & Reps >> Stores >> Manage Store - Additional Attributes section, but the attributes were not loading. But when an entry was made manually in the database, those attributes appeared in the same section. 

 

[ZPD-15535/ZLMC-2752] - Admin - When a third party PIM was integrated with Znode and products were getting added through an API, Znode was unable to respond back although the product was added in Znode which lead the third party API to again create the same product using the same API call considering that the product was not added in Znode. Znode was unable to detect that this is the same product that was created that resulted in storing a duplicate product.

 

[ZPD-15203 ZLMC-2658] - Admin - There was a mapping issue in some Email Template Area Names and the associated Template Names.

 

[ZPD-14116] - Admin - File upload popup was not visible clearly when users click on the “Multiple Upload” button and selected the cross-link.

 

[ZPD-12580] - Web Store - When products were added from Quick Order’s Paste Multiple sections, the products were added from the 2nd row, and the 1st row used to display an invalid message.

 

[ZPD-15249/ZLMC-2669] - Admin - New users created as approvers were unable to view their own order history when associated with a new account.

 

[ZPD-15245/ZLMC-2665] - Admin - Robots.txt update was not working for Multiple Stores.

 

[ZPD-14669] - Web Store - All state names were displayed in lower case for Mexico country when an address was selected on the Checkout Page.

 

[ZPD-14069] - Admin - The sequence of product attributes did not reflect on the Web Store even after changing the “Display Order value” setting from PIM >> Product Attributes >> Add/Edit Product Attribute section.

 

[ZPD-14753] - Admin - Changes were not getting saved and an error message was visible on the screen when a user tried editing a downloadable product and deleting the inventory.

 

[ZPD-13244/ZLMC-1900] - Admin - Two error messages used to get displayed on the Login screen at the same time when a user tries to reset and submit a blank username and password. 

 

[ZPD-14880/ZLMC-2541] - Admin - When an existing Voucher’s Remaining Amount was updated and 'Would You Like To Email Customer' setting was enabled, the voucher amount was getting displayed incorrectly on the Web Store.

 

[ZPD-15169/ZLMC-2649] - Admin - While editing the Content Widget, their variants were not getting saved properly for the PromoCardWidgetGroupSection, as the image property was blank upon saving.

 

[ZPD-14739/ZLMC-2296] - Web Store - When a customer (shopper) edits his profile information from a Web Store, the Account that was associated with the customer account used to get removed. 

 

[ZPD-14632/ZLMC-2461] - Web Store - UPS shipping method was not loading on the Checkout page when a specific address was selected.

 

[ZPD-14107] - Admin - When a user selects Users -> Profile Tab after a new user was associated with the account, existing profiles were not removed and the newly created profile was not selected as the default profile.

 

[ZPD-15442] - Web Store - After updating the Billing Address from Address section, it was also getting updated in the Orders as well.

 

[ZPD-15503] - Admin - Tax amount was getting removed from the Order when CSR discount was applied after deleting a line item(s).

 

[ZPD-15564] - GetAspNetUserDetails() and CreateOwnUser() methods were made public and virtual within UserService.cs class  so that custom methods can be implemented when required.

 

[ZPD-15350] - Admin - An order was created with a configurable product which had all the required tax information. But when the return was created for it, the tax was missing on the create return screen

 

[ZPD-15257] - Admin - When the user entered the address, the address was saved even though the phone number was not provided which eventually is a mandatory field. 

 

[ZPD-14984/ZLMC-2591] - Web Store - Barcodes with font code128 were not getting scanned. 

 

[ZPD-14832] - Web Store - UI and text on the Product Details Page, Quick view were not aligned properly with the UI elements.

 

[ZPD-14981] - Web Store - Favorite Icon was getting displayed on top of the overlay when the navigation panel was expanded.

 

[ZPD-14348/ZLMC-2324] - Admin - An error message was visible multiple times in the Application Logs section.

 

[ZPD-14335/ZLMC-2307] - Admin - Product Export feature was not able to download product details file from the Product Page.

 

[ZPD-14729] - Admin and Web Store - The Personalised text for Grouped products was displaying more than once in the cart.

 

[ZPD-13741] - Admin - Content Security Global Attribute, text was not user-friendly to read and the WYSIWYG text editor was missing for text editing and was therefore added.

 

[ZPD-14721/ZLMC-2494] - Admin - For downloadable products, when a return request was initiated from the admin, the downloadable product keys were not getting reset to “Unused”.

 

[ZPD-15351/ZLMC-1773/ZPD-12696/ZLMC-1773] - Web Store - In a specific scenario the performance was enhanced while retrieving the bundle products into the cart 

 

[ZPD-13492] - Admin - When an order was created from the admin application,  the application was taking too much time to create an user.

 

[ZPD-16033/ZLMC-2900] - Admin and Web Store - For a store CMS Based Search was enabled and publish store only with preview was done, the block for CMS results was getting displayed on the production site as well even though it was published to preview only

 

[ZPD-14766] - Web Store - When a user was logging in or out logs into the Web Store, they were redirected to //home/index view instead of the root/

 

[ZPD-15732] - Admin - Reports - In the reports section, when a custom report was viewed the navigation was missing.

 

[ZPD-15452] - Commerce - The Authentication Helper class is used for login related validation purposes. The code for the authentication filter and its method has now been made extensible and overridable.

Did you find it helpful? Yes No

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