With great pleasure, Aspenware presents Aspenware Commerce 2.12. This release is compatible and must be deployed jointly with Aspenware Commerce version 2.23 and Aspenware Unity version 3.18.

Features

Opt-In/Out of Marketing Communications when creating an account through Identity

Aspenware now supports optionally enabling customers to opt-in or out of marketing communications when creating an account through Identity. This feature flags the customer’s communication profile in RTP|One, which is used by email marketing providers to decide who is signed up to receive marketing emails. Talk to your Aspenware Representative by emailing support@aspenware.com to set this up for your Identity instance.

Support for Google Analytics Tracking within Identity

Aspenware now supports Google Analytics tracking in Identity. Talk to your Aspenware Representative by emailing support@aspenware.com to set this up for your store as this will require providing your GTM ID to your rep and also will require resorts to follow the configuration guide to set up your Google Tag Manager environment to properly track Identity pageviews.

Support for Forced Lockout After a Configurable Number of Invalid Login Attempts

Aspenware Identity now supports defining the number of failed login attempts a lockout is enforced after and the lockout length. Talk to your Aspenware Representative by emailing support@aspenware.com to set this setting for your Identity instance.

Admin for Adjusting Language Strings and Settings (Presently For Aspenware Internal Use)

Updating identity settings and language strings are now easier and less error prone with the introduction of an admin screen for updating identity settings within Azure. Previously setting and language string changes required config file changes and needed to be done by a developer due to the high risk of creating an error in the config file.

Resolved Issues

• 4 character postal codes, which are common in Australia, were previously not accepted by Identity and would throw an error when a guest tried to create an account with a 4 character postal code.

• Identity previously only worked with Inntopia Marketing Cloud or Sendgrid sending capabilities, it is now supported to work with SMTP, though this is not recommended due to the fragile and unsophisticated nature of many SMTP servers. For optimized deliverability and reliability, Aspenware recommends configuring Identity with Sendgrid or Inntopia Marketing Cloud.

Known Issues

• Aspenware Identity doesn’t automatically redirect the guest back to the PDP they were on prior to selecting to sign in unless they explicitly use a redirect URL where sign-in is required. This is a feature enhancement to Identity.

• Guests who do not have a birth date defined on their profile are not able to log in through Identity.