Release Date: 1/31/24
...
Current Releases (as of 1/2331/24) | ||||||
|---|---|---|---|---|---|---|
Cloud UI | Commerce | Identity (Auth0) | Identity (Legacy) | Unity | Arrival | Resort Tools |
1.5 | 3.44 | |||||
Identity (Auth0) 1.5 Release Notes |
|---|
Enhancements
Social Connections Enhancement
We’ve refactored our social connections to Auth0 to simplify our code and make it easier to scale with additional social connections, i.e. a google sign-in. This only effects Alterra currentlyenhanced our support for 3rd party integrations for future implementations of social platforms such as Google sign-in.
Resolved Issues
Browser Back Button
We fixed 've addressed an issue where if you selected ‘back’ selecting ‘back' on your browser , you’d experience an auth0 led to Auth0’s error page. We’ve adjusted Now, the behavior to go back to the last known browser page.
There was an issue where duplicates guest family records were being created for Alterra resorts. This has been corrected and we are matching family members to existing (if found).
There was an issue when trying to navigate to commerce pages from My Account. We’ve fixed the routing and users will now be able to navigate directly to any commerce page from their Account.
Alterra cannot update unity until we are onto Accounts 1.5 as part of this fix. If we decide this cannot wait that long, we’ll need to rework this ticket and create a hotfix for accounts (1.3.2)has been adjusted to seamlessly return users to their previous browser page, eliminating any disruptions in navigation.
Family Member Match
We’ve corrected an issue with using alternative IDs in RTP that was causing duplicate customers being created. This issue only applies to resorts utilizing alternative IDs to link to their external customer databases. Note that this works in conjunction with the fix noted in the Unity 3.44 notes below.
Multiple ID Support in RTP
We have updated the underlying behavior of supporting multiple IDs in RTP to account for previous changes in Resort Charge. Note that this works in conjunction with the Unity 3.44 fix noted below.
...
Unity 3.44 Release Notes |
|---|
Resolved Issues
...
Family Member Match
Unity now conducts an initial check to determine if a matching alternative ID is present. If a matching alternative ID is found, it will sync with that ID before creating a new customer in RTP. Note that this works in conjunction with the fix noted in the Identity (Auth0) 1.5 notes above.
Multiple ID Support in RTP
We have updated the underlying behavior of supporting multiple IDs in RTP to account for previous changes in Resort Charge. Note that this works in conjunction with the Identity (Auth0) 1.5 fix noted above.