Commerce 3.7 / Cloud UI 2.0: Aspenware Admin
- Sarah Holst
- Jenni Buonanni
Several updates have been made to enhance the functionality and usability of the Aspenware Commerce Admin. These improvements address authentication security, optimize performance, fix visual and processing issues, and ensure proper date formatting for specific language cultures. Key updates include:
Multi-Factor Authentication (MFA) Re-authentication
An issue has been resolved where admin users were not prompted to re-authenticate with an MFA code when accessing certain areas of Aspenware Commerce Admin.
Bulk Attribute Combinations
We’ve added safeguards to limit the number of attribute combinations that can be bulk-generated in production environments, ensuring better performance and stability.
The new limits prevent excessively large combinations, such as scenarios with hundreds or thousands of attribute values, which could negatively impact performance.
Example:
If you have 3 required attributes with 4, 3, and 2 possible values respectively, the total number of combinations is:
4×3×2=24
Example Handling Conditional and Non-Required Attributes:
These limits become less straightforward when a product includes conditional or non-required attributes. In these cases, fewer combinations may be generated than suggested by the formula above.
To calculate combinations for optional attributes, consider this example of a meal with 3 optional courses (attributes):
Optional Attribute 1: Appetizers (2 options)
Garlic Bread
Bruschetta
Optional Attribute 2: Main Course (3 options)
Pasta Entree
Fish Entree
Steak Entree
Optional Attribute 3: Dessert (2 options)
Ice Cream
Chocolate Cake
If users can pick any number of courses, you must account for all combinations, from selecting 1 course to all 3 courses.
Calculation:
(2+1)×(3+1)×(2+1)−1=3×4×3−1=36−1=35(2 + 1) \times (3 + 1) \times (2 + 1) - 1 = 3 \times 4 \times 3 - 1 = 36 - 1 = 35(2+1)×(3+1)×(2+1)−1=3×4×3−1=36−1=35
Thus, there are 35 possible meal combinations when considering different options for each course.
Attribute Value Handling
The handling of attribute values containing numbers to ensure correct processing has been improved.
Payment Plans Table Display
A visual issue in the Admin > Payment Plans > Enrollments table has been fixed where the “has failed payments” label and toggle were displayed twice; the duplicate has been removed.
Date Formatting in Waivers
Corrected an issue where resorts using the ENG-AUS language culture were not seeing the proper date formatting in the Admin > Waivers > Edit tool, which could prevent waiver forms from saving unless dates were manually typed. The date-picker tool now displays the correct format for ENG-AUS language culture.