Aspenware Commerce 3.0 introduces a new SQL reporting plugin called Nop-Station Sql Manager.
Due to the expiration of the previous SQL reporting plugin, Nop4U SqlReport, Aspenware has replaced it with Nop-Station Sql Manager. This tool has a slightly different UI but offers the same reporting tools. All reports your resort uses will be ported to the new system.
| Note |
|---|
IMPORTANT: Any resort taking Commerce 3.0 or later for the first time will need to install and enable the Nop-Station Sql Manager plugin with the license provided by Aspenware. |
Detailed Setup Guide
If you currently use SQL reporting, your Aspenware Service Agent will install your new Nop-Station Sql Manager plugin and add your license key. At this point, you can use and see all of your existing reports.
If you don’t currently use SQL reports, talk with your Service Agent to learn more about implementing them.
To install the Nop-Station Sql Manager plugin:
Go to Configuration > Local Plugins > Find and install Nop-Station Sql Manager.
...
Go to Nop Station > Core Settings > License.
Enter the license key given to you by your Aspenware Service Agent.
...
Cloud UI 1.2 introduces a separate UI that can be used for most product detail pages, building on the 1.0 release, which enabled a separate UI for the Pricing Calendar and moving toward additional redesigns of the shopping pages.
| Note |
|---|
IMPORTANT: While Cloud UI is supported for most product detail pages, some features and configuration options are not yet supported in Cloud UI. These configurations will continue to work as usual if loaded on the Legacy pages. |
This guide explains the following:
Which product detail pages should NOT be moved over to Cloud UI, and how to ensure that these products continue to load and work on the non-Cloud UI (see the list below)
Which products are now supported and will load in the separate Cloud UI.
Initially, the user experience and UI will be identical between legacy and Cloud UI pages. With the upcoming PDP refresh release, the Cloud UI product detail pages will have a refreshed look and feel and theme application according to our design system, while legacy product detail pages will remain unchanged.
Which products are currently incompatible with the Cloud UI PDP?
Most products are Cloud UI compatible, but there are some exceptions. If a product has any of the following features/configurations enabled on the PDP it should NOT load on the Cloud UI and should be flagged to continue to display legacy PDP. These products will continue to work if they retain their Legacy configuration and are flagged as noted below in the Setup Guide.
Radio button date products (section 2 of this guide) (expected to be Cloud UI compatible in 1.5)
Time-based activity products (expected to be Cloud UI compatible in 1.5)
Assigned to attribute with Assignment on the PDP
Fenced products that can only be accessed using a valid voucher
Detailed Setup Guide
For these listed exception products, there is a new product-level setting that enables some products to continue to load for users in the legacy UI, and for the majority of products to load in the new Cloud UI. Respecting this routing will work whether a PDP is accessed via the category page, related product link, or cross-sell link. To flag a product so that it continues to load in the legacy UI:
Find the product from Catalog > Products >Edit
Scroll to the Aspenware Commerce section of the edit page
Locate the new product-level setting called Use Legacy Product Page.
Check the box
Click SAVE ALL SETTINGS
| Info |
|---|
NOTE: This setting should ONLY be turned on if a product is incompatibale with Cloud UI. |
...