Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 45 Next »

With great pleasure, Aspenware presents Cloud 3.1, Commerce 2.43, Unity 3.38, Arrival 1.9, and Resort Tools 3.7.

Release Date: 6/21/23

Current Releases

(as of 6/21/23)

Cloud Commerce

Commerce

Identity

Unity

Arrival

Resort Tools

3.1

2.43

2.30

3.38

1.9

3.7

3.1 Cloud Commerce Release Notes

The following enhancements are available for Aspenware Cloud customers.

New Features

Calendar Templates

Scarcity indication is a compelling reason for guests to purchase. Removing friction around date selection by helping users understand that inventory may be low for certain products on certain dates can motivate guests to purchase now. Aspenware is planning to release improved calendar availability urgency capabilities in 2.44 and is making the Calendar Template manager admin available in 2.43 to prepare for this feature release, giving admins time to make product setup adjustments.

To that end, Aspenware Cloud includes a new, global Calendar Template manager. With this manager, admins can view and create multiple Calendar Templates and each template contains a number of settings that control how the calendar will appear for the assigned products (after the 2.44 release) to create urgency for product purchase. Within the Calandar Template Manager, resort users are able to:

  • Determine whether or not assigned products should color code dates with low inventory

  • Add an optional description that will appear above the calendar for specified products.

  • Assign specific low inventory threshold per product type indicating dates for when assigned products should be color coded

Enhancements

GA4

Users of Aspenware Cloud will now see an event trigger when a customer clicks on the cart icon in the Cloud Commerce header. This event is the equivalent of the View_Cart event triggered when a customer clicks on the cart in the standard Aspenware Commerce header.

2.43 Commerce Release Notes

The following enhancements are available to all Aspenware customers.

Enhancements

Checkout Refinements of Assign Product Step

The Assign Products step has been optimized to address user drop-off and frustration when household members do not appear in the assignment dropdown list and the user doesn’t understand why.

To address this challenge, guests are now presented with all members of their household during the Product Assignment step. If a household member is not eligible for assignment (e.g., a child for an adult pass), their name will be disabled for selection and an explanation will be offered as to why they are ineligible for assignment. The explanations for assignment restriction are as follows, and the guest-facing message can be updated via a language string.

The customer-facing messaging for assignment restriction can be updated via a language string and the possible reasons for ineligibility are as follows:

  • Age restriction

  • Fastflow product variant

  • Media is required to assign

  • A birthdate must be defined prior to assignment

  • Product is restricted by a validation prompt

See the Conflguration: Requiring Assignment for a list of the language string resources.

Resolved Issues

GA4

  • An issue was addressed with GA4 in which the product SKU is sometimes reported as NULL in the Purchase event. The SKU is now reporting correctly in the Purchase Event whether it is assigned at the product level or at the variant level (defined in the attribute combination admin).

FreedomPay Payment Gateway

  • In some instances, the SKU that is passed to FreedomPay as part of level 2/3 data was populating as NULL. This issue is resolved, and the SKU passes as correctly.

3.38 Unity Release Notes

This Unity release contains updates that lay the foundation for future feature work. The following changes have been made to existing APIs:

  • You can now get customers, contacts, and family members using external IDs

    • External ID’s could be associated with an external customer database

  • When a new customer, contact, or family member has been created, external IDs can now be based to any profile type. Previously, you could only pass an external ID for a configured type (Commerce Customer ID).

  • When getting a customer or contact all external IDs will be returned.

  • When getting customer and returning a contact list with family members, all contact external IDs will be returned.

Suggested Edits

This Unity release contains updates that lay the foundation for future feature work. Changes have been made to existing APIs to enable future-state functions including:

  • Customer, contact and family member searches using an external ID.

  • External ID basing on any profile type when creating a new customer, contact or family member. Previously, only external IDs for a configured type (Commerce Customer ID) were passed.

  • Customer, contact, or family member searches return all external IDs.

  • All contact external IDs returned in a search for a customer who has a contact list with family members.

Note that these search and account create functions are not currently available for Aspenware customers. These Unity API updates have been made to enable development of them. This Unity release is not required for any resorts at this time.

1.9 Arrival Release Notes

Resolved Issues

The Arrival Admin has been updated to display all Admin users on the page, even if the count exceeds 10.

3.7 Resort Tools Release Notes

Resolved Issues

  • Restrictions were added to the date of birth field to prevent the creation of a birth date in the future.

  • Waiver signature date and time stamp are now populating correctly in the RTP Authorization Profile when a guest signs a waiver.

  • After signing a waiver in Resort Tools/Guest check-in, a new Authorization Profile entry is now created for the customer in RTP.

  • No labels