Account Service - September
Date:
Exception when email address is changed before confirmation
(RTL-2402)
Changing the e-mail address for recently created member in ChainWeb before confirming email, no longer results in Account Service 'PUT UserExternal/ForceChangeIdentifier' exception.
Forgot password show sent labels or error messages
(RTL-2440)
MyPage users will get 'resend email' message and feedback message displayed in AccountService UI, when clicking 'send' button in reset password view.
User is Able to Trigger Two Registration Calls Causing Index Collision
(RTL-2497)
Index collision caused by triggering two registration calls is not happening anymore.
That means, when user is trying to register, and click at 'Register' button, it becomes disabled to prevent from triggering the second registration within one process.
What is more, when registration fails, the appropriate error message is being displayed and user is informed about particular obstacle and able to continue or retry the registration process once again (Register button becomes enabled in such situations).
Account Service - July / August
Date:
Create Config UI for Account Service
(RTL-289)
The UI for all configuration fields in Account Service has been created and contains all recently existing fields in a form of checkboxes, drop-down lists or input fields. It can be found under system menu icon -> Account Management -> Concepts.
What is more, the configuration set in UI is correctly saved in dbo.LoyaltyProgram and displayed in Account Service page.
Important:
Loading apropriate configuration in Account Service page can varry between 1-30 min (cash = 30min) - waiting time depends on the moment user submits required changes.
Countdown removed
(RTL-2066)
Removed the countdown when registering by mobile, instead a message will appear stating that the user can send a new registration/login link in 30 seconds. Also did some minor text improvements.
Registration Fails in Account Service if Member has Empty Address Fields
(RTL-2108)
Registration of members that have partial (incorrect) address fields onpremise does not fail.
That means, if member has partial (incorrect) address and address is not configurable in AS, MemberIdentity with partial (incorrect) address is transformed before upserting to MemberInfoservice and invalid address is removed. However, if member has partial (incorrect) addres and address is configurable in AS (user can fill it), MemberIdentity with partial (incorrect) address is validate in UI before upserting to MemberInfoservice.
HEAD Requests
(RTL-2183)
Fixed so that HEAD requests with params now returns 200. If no params are present, 404 will be returned and logged.
Add Support for MemberIdentityOnBoardingReady
(RTL-1553)
It is possible to create account in AccountService for members created in store.
That means, when member is created in store, user receives email or SMS invitation message sent on defined email address or mobile number and is able to finish registration process that leads to creating account in AccountService.
Account Service - June
Date:
Loading of AccountService
(RTL-1974)
While confirming membership via email verification, the "enter SSN to register" field was briefly visible while the page was loading. This has been removed.
Conflict error message
(RTL-2039)
If a mobile number is in use on-premise and is configured to be unique, AccountService will correctly display an error message to the user stating that the number is in use. Previously, there was only an error message stating "something is wrong. Please contact administrator". The user is now able to see why the error occurred.
Countdown removed
(RTL-2066)
Removed the countdown when registering by mobile, instead a message will appear stating that the user can send a new registration/login link in 30 seconds. Also did some minor text improvements.
Fixed an issue with registration if a member had empty adress, name of mobile fields.
(RTL-2159)
AccountService does not reqiure most of this information but it would fail in MemberInfoService. We now ignore this failed validation and the member can be onboarded anyway as none of this information is required for AccountService.
Account Service - May
Date:
Cleanup in AccountService
(RTL-1871)
StagingCleanup job has been added to AccountServiceIntegration. Enable it to clean staging from old or processed items
Registering member with landline phonenumber
(RTL-2054)
Previously, landline numbers would fail validation in MemberInfoService when sending it to AccountService. This correction, nulls out the phonenumber for AccountService to allow the registration to finish.
Account Service - April
Date:
Import of store data
(RTL-48)
Store data is imported to AccountService from StoreService, which will allow members to add home store to the member during registration.
Add social security number in registration process
(RTL-61)
Social security number is implemented in member registration process. In AccountService webapp after confirming an email address, the user have to add social security number, which allow to fetch personal information, such as name and address which will later on be added to the member.
Add support for changing member email
(RTL-1508)
When member's email is changed in Chain Web, then it is properly updated in account service in both MemberOnboard and User tables.
Support for blank emails has been added. When member's email is changed in Chain Web to a blank one, then in account service it is saved as a hash.
LPMembers-Configuration of identifiers.
(RTL-1551)
MemberNumberAsIdentity identifier was added to MemberInfoService and AccountService to map identity and membership from on-premise to cloud correctly.
Now to modes of mapping are possible:
- MemberNumberAsIdentity - Identity number be set to MemberId and Membership number is set to HouseholdId.
- SocialSecurityNumberAsIdentity - Identity number is set to SocialId if it is defined otherwise to MemberId, and Membership number is be set to MemberId.
After creating a certain member through ChainWeb or API, it gets the appropriate identifier, is correctly onboarded in AccountService and loaded as a user after finishing registration in AccountService.
Requirements:
- LpMemberIdentifierMode Parameter in MemberInfoService should be set to MemberNumberAsIdentity (or SocialSecurityNumberAsIdentity for existing customers) on integration package (package config) and service (tenant admin). MemberNumberAsIdentity is default value for new installations so configuration is not required then.
- LpMemberIdentifierMode Parameter in AccountService should be set to MemberNumberAsIdentity (or SocialSecurityNumberAsIdentity for existing customers) on integration package (package config). MemberNumberAsIdentity is default value for new installations so configuration is not required then.
Add home store in registration process
(RTL-1761)
It is possible to register member with the home store - by using new component dropdown list. The dropdown list consists of stores which are presented in the dbo.Store table in AccountService database.
When changing configurationJson in dbo.LoyaltyProgram, it is possible to enable/disable the home store dropdown list or set to mandatory.
Account Service - March
Date:
Added deletion of memberships
(RTL-270)
Added deletion of memberships for AccountService and MemberInfoService. Deleting a member on-premise in Chain Web will export a message and delete the member in the cloud databases of AccountService and MemberInfoService.
Configuration:
The following LIP jobs have been added:
MemberServiceEventHandler - Default configuration
MemberInfoServiceEventHandler - Default configuration
MemberDeactivation - Default configuration, change CRON run times if needed. Every 1 - 5 minutes recommended.
Added support for older hashing algorithms
(RTL-1532)
Added support for the older type of password hashing algorithms used by MyPage. Both Bcrypt and pre-Bcrypt is supported. If a user is migrated to AccountService from MyPage, and has the old hashing algorithm, the "old" password will still work. And upon login or using "Forgot password" the hashing algorithm will be updated to the newer version used by AccountService, while maintaining the same password for the user.
Add Preferred Communication Channel in Registration Process.
(RTL-1537)
When creating a member in AccountService v.2 it is possible to select preferred communication channel in the registration. Whether or not this section is displayed in registration is configurable.
Required configuration:
In Lindbak AccountService db add "communicationTerms" parametr and set its mode to:
mode 0 = mandatory
mode 1 = visible
mode 2 = read only
mode 3 = disabled
in [dbo].[LoyaltyProgram] column [ConfigurationJson]
| Module | Description |
|---|---|
AccountServiceIntegration (RTL-1512) | Improve mass onboarding error handling If there is an already onboarded member in a loyalty program with an email, then another member with the same email will not be onboarded in this loyalty program. |
AccountServiceIntegration (RTL-1629) | Phone number validation error Corrected an issue where a user would register themselves via the forgot password link when they had no previous account. The issue would lead to the account being created, but the phone number being wrong and hence, the user was unable to log in. This only applied to tenants using mobile as primary identifier. |
Account Service - Feb
Date:
URL shortening for SMS links
(RTL-1387)
It is possible to shorten the verification URL sent on SMS to user when registering via AccountService. For this to be useable, AccountService should be configured for mobilenumber registration
Account Service - January
Date:
Birth date as a field in registration process
(RTL-215)
It is possible to add birth date as a field in registration process - it can be typed manually or picked by using calendar. It is configurable whether or not it is mandatory to be of a certain age to be allowed to register.
Improvements
| Module | Description |
|---|---|
Add support for data analysis terms in registration process | Support for data analysis terms in registration process has been implemented. Now by applying proper configuration, it is possible to:
|
| WebApp: Add support for terms approval in registration process | Support for terms approval in registration process has been implemented. It is possible to add member terms checkBox with descriptions and link - which can be customizable by using configurationJson in dbo.loyaltyProgram table. If we don't add the configuration, then user will see member terms checkbox with descriptions and link - and during registration process user must accept member terms to register |