Versions Compared

Old Version 46

changes.mady.by.user Erin Hunter

Saved on

compared with

New Version 47

changes.mady.by.user Sarah Holst

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

...

With great pleasure, Aspenware presents Aspenware Commerce 3.0

Note that beta release notes are drafts of what will be included in the upcoming release. They are subject to change and may be altered due to findings during beta testing.

...

Current Versions

(as of 9/14/2023)

Cloud UI

Commerce

Identity

Unity

Arrival

Resort Tools

1.1

3.0

2.32

3.40

1.9

3.7

...

Commerce 3.0 Release Notes

nopCommerce Upgrade

In Commerce 3.0, we upgraded our core application framework to the latest supported versions. These framework upgrades include nopCommerce and .NET - taking us from a 4-year-old version to a current 2023 version. Aspenware has spent several months optimizing our base commerce platform to prepare for this transition and to expedite future upgrades.

Upgrade Benefits

This improvement brings several important significant benefits, including:

  • Platform upgrade from 4.2 (May 2019) to 4.60.3 (May 2023). See the nopCommerce release notes for enhancements made between the two versions. Note that Aspenware does not use all features included in nopCommerce.

  • .NET 2.2 core to .NET 6.0 to unlock new developer efficiencies

  • Security improvements

  • Performance boost through improved memory utilization and page load time

  • Safer and faster future upgrades for our partner resorts

  • Removal of unnecessary plugins, such as the ResortOS plugin

Aspenware rigorously tested Commerce 3.0 has been rigorously tested across all plugins.

UI Changes

As with most software upgrades, you will notice refinements to the UI. These changes are primarily minor and include enhanced features. Many of the enhanced improved features are not currenetly currently used by the Aspenware platform. The minor updates to the user interface include things such as changed formatting, icons, and additional options.

...

  • Improved search functionality, including selection options and enhanced search options across the site

  • Basic and advanced modes were added to store details and discounts pages

  • Additional UI changes with the placement, naming, and rearrangement of fields (. 

These changes do not affect Aspenware store configuration but may vary slightly from what is shown in configuration guides on the Aspenware Hub. Changes to these screenshots will be part of ongoing updates within the Aspenware Commerce Hub documentation.

...

SQL Reporting Tool Replacement

  • Aspenware has replaced the SQL reporting tool, Nop4U SqlReport, with  with Nop-Station Sql Manager, as the former plugin is no longer supported. This tool has a slightly different UI but offers the same reporting tools. All reports used by your resort uses will be ported over to the new system. See See Configuration: Nop-Station Sql Manager for  for more information on this new plugin.

Note

IMPORTANT: The Aspenware Commerce customization of nopCommerce does not support all nopCommerce features. If you have any questions or comments about Admin changes, please get in touch with your Service Agent (support@aspenware.com).

...

Additional Enhancements

...

Calendar Templates (Cloud Only)

Inventory Scarcity Controls per Product on are not enabled at the product level on the Full-Page Pricing Calendar: . Once you take the Commerce 3.0 release, as an Aspenware Cloud customer, Calendar Templates admin can be used to configure inventory urgency indicators on the full-page pricing calendar. This is important because now you can control inventory scarcity thresholds at the product level rather than just the storewide level for the large pricing calendar! . For example, your lift ticket can display low inventory when 20 tickets are left, but your lessons can display as low inventory when 5 are left. To learn more about this feature, see Calendar Templates.

Inline PDP Calendar (Cloud Only)

When showing scarcity on the inline calendar, the threshold used to determine if dates should be colored for inventory scarcity checks if the inventory left on a date is less than or equal to the threshold rather than less-than-only logic. This logic matches how logic works on the large pricing calendar to ensure consistency across the two calendars.

Cookie Consent

Additional validation now happens on the cookie consent JavaScript and CSS. Previously, formatting errors were handled via the frontend. In 3.0, these are now validated during Admin entry, which ensures that newly added values render correctly on the frontend.

App Insights

We improved failed order diagnostics and troubleshooting in App Insights used by our Service Team and DevOps Teamteams. Slight improvements to messaging in the order queue have were also been made.

Product Admin Updates

  • We added a new setting to control which products should use the Cloud UI. This is a foundational change is in preparation for the PDP design refresh, and more information will come soon. Stay tuned!

  • We enhanced some additions to the product editor admin page to support some features that are coming soon, such as:

    • Naming a product variant which Product variants will be able to be named, and that name will be presented to customers for clarity at several points in the customer journey and passed into the Google Analytics 4.

    • Defining max prices Max prices will be able to be defined for a product variant that is not dynamically priced so that you can display savings can be displayed at several points throughout the customer journey.

...