Release Date: 2/XX22/24

...

Resolved Issues

The ecommerce application is supposed to only log error messages to the Log table in the database and all other informational logs go to Application Insights. This happens so that the database Log table doesn’t grow too large. A bug was introduced in 3.0, however, where most logs (even informational logs) are sent to the Log table in the database causing it to grow large and in turn hurting performance. Hotfix/3.3.3 corrects this issue so informational logs are once again only sent to Application Insights.

EDIT:

Previously, our application was designed to log only error messages to the Log table in the database, while all other informational logs were directed to Application Insights. However, a bug surfaced in version 3.0, causing most logs—including informational ones—to inundate the Log table, leading to undesired performance impacts due to database bloating.

...

Enhancements

Payment Plan Schedules

Aspenware has added date-sorting functionality to payment plans. Previously, resort admins could add payment plan dates in non-consecutive order when constructing their payment plans. Now, upon saving a payment plan schedule, Aspenware will automatically sort payment plan scheduled payment dates in consecutive order.

FreedomPay and TransArmor (TA) Tokens

Aspenware has added a new setting that supports resorts that have worked with FreedomPay to use TransArmor tokens. This setting can be found in the payment gateway configuration and is unchecked by default. To learn more about our FreedomPay integration, please see FreedomPay on the Customer Hub.

...

Resolved Issues

Information Logs

We have updated our logging process to ensure no performance impacts are experienced.

...