...
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 enhanced our support for 3rd party integrations for future implementations of social platforms such as Google sign-in, ensuring smoother user experiences across various authentication methods.
Resolved Issues
Browser Back Button
We've addressed an issue where selecting ‘back' on your browser led to Auth0’s error page. Now, the behavior has been adjusted to seamlessly return users to their previous browser page, eliminating any disruptions in navigation.
Family Member Match
We've rectified an issue where duplicate family records were created erroneously for a few resorts. Our system now efficiently matches family members to existing records, if found, minimizing redundancy and ensuring data accuracyWe’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
We've rectified an issue where duplicate family records were created erroneously for a few resorts. Our system now efficiently matches family members to existing records (if found), minimizing redundancy and ensuring data accuracyUnity 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.