Aspenware presents Aspenware Commerce 2.10.2.
Updates, Features, and Upgrades
Feature 1
Feature 2
Upgrade 1
1Risk Setting for Date Format Configuration
Resolved Issues
...
Resolved Issue 1
Previously when an add-on was present, the core product and the add on product would sell under the add-on product code and pricing. Now these products are sold and priced separately.
Resolved Issue 2
Previously the import process would start by generating a spreadsheet with all dynamical prices set to zero. Now, the prices in the spreadsheet are set using values from the dynamic pricing tool.
Resolved Issue 3
Previously, content associated with rental location language strings was not displaying. Now your customized content displays wherever language strings are in place.
Things to Look Forward to
Kount fraud protection with Authorize.net
Resort Charge (My Account page)
Bulk payment processing (Payment Plans)
Subscriptions
Features
Feature 1
Feature 2
Upgrade 1
1Risk Setting for Date Format Configuration
...
Payment Plan Modal Date Display Problem
Payment Plan Orders Not Displayed in My Account after Failed Payments
...
Features, Updates and Upgrades
1Risk Setting for Date Format Configuration
For customers using 1Risk, you can now use a new Aspenware Commerce setting that will control how 1Risk displays any dates (e.g. DOB). The valid values include: mm/dd/yyyy, dd/mm/yyyy, mm-dd-yyyy, dd-mm-yyyy. For more information and to add or edit this setting see the 1Risk Configuration Guide.
Resolved Issues
Payment Plan Modal Date Display Problem
For resorts in Canada, there was a defect with dates on the payment plan schedule modal displayed to the consumer in the store when payment plan products are added to the cart. This defect was fixed in this release and international dates display as they should.
Payment Plan orders not displayed in My Account after failed payments
Consumers who had a failed payment plan payment were not able to see the payment plan record in My Account, and therefore were unable to update the credit card used for future payment plan payments. This problem has been corrected in this release.
...