New Feature

Advanced Coupon Usage Report

Administration

This new advanced report “Coupon Usage Report” shows the details of coupons and promotions used during the specified time period in the stores.

Administrators can view and filter the data shown in this report based on the access levels they have.

To implement this report, 

• Changes were made in:

  • GetDiscountType method of DevExpressReportClient.cs

  • GetDiscountType method of IDevExpressReportClient.cs

  • GetDiscountType method of DevExpressReportEndpoint.cs

  • ReportDiscountTypeListResponse.cs

  • GetDiscountType and GetCouponReport methods of DevExpressReportService.cs

  • GetDiscountType, GetCouponReport methods of IDevExpressReportService.cs

  • GetDiscountTypeList method of DevExpressReportAgent.cs

  • WebApiConfig.cs

  • GetCouponReport method of DevExpressReportCache.cs

  • GetCouponReport method of IDevExpressReportCache.cs

  • GetCouponReport, GetDiscountType methods of DevExpressReportController.cs

  • ReportFilterHelper.cs

  • ValidateParameterValues method of ReportHelper.cs

  • ReportSettingModel.cs

  • Coupons.cs

  • FilterKeys.cs

  • AdminResource files

• Following were added:

  • ReportDiscountTypeModel.cs

  • Coupon Usage Dev Express Report Model properties in CouponUsageInfo.cs

  • Coupons.cshtml

Enhancements

SEO Enhancements

Administration

The following new SEO related enhancements are introduced in this release:

Support for Robot Tag:

Robot tags allow search engines to identify which pages of the web stores to crawl.
Znode now allows admin users to manage Robot tag at Store level and at the Page level (i.e. at the Product level, Category level, and CMS Pagelevel). 

Admin users can also import the value of Page-level Robot Tag field using SEO Import.

Important: The value of Robot Tag saved at Store level will be used on the web-store if and only if the value for Robot Tag is not saved at the Page level.

Support for Page-Level Canonical URL:

Znode now allows admin users to add Canonical URL for products, categories and CMS pages. 
Admin users can also import the value of Canonical URL field using SEO Import.

Get Default SEO values:

A new button Get Defaults is introduced in the SEO section of Edit Product, Edit Category and Edit CMS Page. 

Admin users can use this button to fetch the default values of SEO Title, SEO Description, and SEO Keyword on Edit Product, Edit Category and Edit CMS Page pages. 

Note: The macros for default values are saved in the SEO Setup module.

To implement the above Robot Tag and Canonical URL enhancements,

• Changes were made in

  • ZnodeRobotText table

  • SEODetailsViewModel.cs

  • SEODetailsViewModel

  • EODEtailsModel

  • ContentPageModel

  • PublishProductModel

  • SEOUrlModel

  • ProductViewModel

  • SEOURLViewModel

  • SEOViewModel

  • ProductSEO.cshtml

  • CategorySEO.html

  • CreateEdit.cshtml

  • CreateEditRobotText.cshtml

  • ContentPageForLocale.cshtml

  • SEODetails.cshtml

  • CreateContentPage and UpdateContentPage methods of ContentAgent file

  • UpdateSEODetails, GetSEODetails and GetSEODetailsBySEOCode methods of SEOSettingAgent

  • GetSEOAndLocaleDetailInformation and GetSEODetailsLocaleEntity methods of SEOService file

  • GetCategorySEODetails method of PublishCategoryService file

  • WebStoreGetPortal method of WebstorePortalService.cs file

  • _LayoutHead.cshtml

• Following were added:

  • DefaultRobotTag property in RobotTextModel.cs, RobotTextViewModel.cs and WebstorePortalModel.cs file

  • GetRobotText method in WebStoreGetPortal method of WebstorePortalService.cs file

To implement Get Defaults functionality,

• Following were added:

  • GetDefaultCMSSEODetails and GetDefaultSEODetails methods in SEOSettingAgent file

  • GetDefaultSEODetails method in SEOService.cs

Shipping & Billing Address Enhancement 

Administration, Shopper Experience and Commerce

With this release, when admin user will try to update any address while managing an order, then if Shipping Address is same as Billing Address or Shipping Address and Billing Address are the default addresses then the updated address will be added as a new entry in the database.

Issues Resolved

[ZPD-6251] - Admin - The default profile of user was getting changed when a customer (shopper) account was converted to the admin account.

To resolve this issue, changes were made in ConvertShopperToAdmin method of UserService file.

[ZPD-6660/ZLMC-669] - Admin - In case of large data, after publish action was performed, the application used to show an error message.

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

• SetSchedulerParameters, GetEXEParameterForPublishCatalog and SetProductFeedParameter methods  of ERPTaskSchedulerService.cs

• CallSearchIndexer method of SearchService.cs

• SetSchedulerParameters method of scheduler parameters for ERP

• GenerateImages method of PortalService.cs
  
  

[ZPD-6661/ZLMC-665] - Web store - Some Home page widgets were displaying data of other home page widgets due to home page caching.

To resolve this issue, changes were made in the GetContent method of WidgetDataAgent.cs file.

[ZPD-6675/ZLMC-664] - Web store - Category page used to break (in a scenario when the web store preview was disabled) when publish process progressed to 60% because old publish version SEO details used to get deleted immediately after the new publish version SEO details were inserted in Mongo.

[ZPD-6677/ZLMC-634] - Web store - “Search Results” label had no spacing between them and therefore an appropriate label was added in the resource file.

[ZPD-6776/ZLMC-684] - Application used to throw a NULL error after a coupon was applied for ZnodeCartPromotionAmountOffProduct type promotion.

To resolve this issue, changes were made in ApplyChildItemDiscount and  ApplyLineItemDiscount methods of ZnodeCartPromotionAmountOffProduct.cs