Release date:
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.
Merge failure when more than one PersonalAttribute on member
(RTL-204)
It is possible to update members, who have more than one personal attribute.
Fix relate to clients using MemberIdentity format.
Anonymizing members in MemberInfoService
(RTL-1805)
When using MyPage together with AccountService v.2 and MemberInfoService, it is possible for user to deactivate (anonymize) member (identity) from MyPage which results in deactivation of member data in MemberInfoService and MemberService on premise. The member will be deleted in MemberInfoService, but anonymized in MemberService.
Add fallback scenario to GetMemberIdentity request
(RTL-1906)
If looked up member is missing in MemberInfoService database, then service will do additional call to MemberService to search for it there.
Associations in MemberInfoService
(RTL-1951)
LpMemberMerger imports associations (connection to member and association number) to the MemberInfoService database. User can see and check linked association within the MyPage profile in the Member Info tab.
Support for deactivating members
(RTL-1992)
New MemberIdentity status has been introduced - Deleted, which results in hard deletion of identity from MemberInfoService regardless of other settings. Note: Identities are not deleted immediately but within 10 minutes.
It is possible to set the deactivation mode in the LIP configuration - Delete to delete deactivated members and OnlyPublish - deactivated identities are not deleted or modified.
In both modes identities with status deleted are deleted.
Identities with status Deleted are always deleted.
LpMemberMerger member's cards lookup for MemberNumberAsIdentity
(RTL-2043)
It is possible to update members, who have member cards attached.
Improvement related to clients using MemberNumber as identity (all clients using AccountService2)
Fix LpMemberMerger conversion of the member's from the same household, but different stores
(RTL-2044)
Importing multiple members from the same household, with different stores, will be executed correctly into MemberInfoService database.
Release date:
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
Add default store number for LoyaltyProgram
(RTL-1569)
Loyalty program table has been extended by DefaultStoreNumber column. By default the store, from the newest membership in each loyalty program is assigned to the DefaultStoreNumber.
New members created in member info service are assigned to the default store number for the selected loyalty program.
Support in MemberInfoService for updates from Mypage
(RTL-1590)
As a step towards supporting AccountService v.2 together with MyPage, changes made by members in in MyPage are updated in MemberInfoService, which in turn will update MemberService on premise. MyPage can be configured to use MemberInfoService instead of MemberService on premise for handling member data.
Endpoint for fetching membership data was created:
GET api/membership/{number}/identities where number= number on membership
This method fetches Member Identities by Membership number and returns its collections.
Change logging of external requests
(RTL-1670)
Requests returned by Linkmobility as 404/400 (unknown phone number) failure are logged in the same way as success (200) in MemberInfoService's App insights to avoid unnecessary error messages.
Release date:
Republish Member events in cloud
(RTL-1516)
Cloud components cannot depend on on-premise MemberService events. When member updates are published, a new job in MemberInfoService (MemberServiceEventHandler) re-publishes them to cloud service bus using following events:
- IdentityIdentifierChanged
- IdentityProviderOnboardRequested
- IdentityDeactivated
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.
Release date:
GetAssociationInfo Returns 404
(RTL-1440)
An issue was introduced on the 22nd January which causes Get Association Info method to return 404 error when trying to fetch association. This is corrected and using this method in API that exploit customer number as query parameter results in success.
Association import broken due to contract changes
(RTL-1429)
An issue with Associations (Customers) in Cloud [Lindbak Retail] was introduced on the 22nd of January, causing new associations to not be synchronized properly to Cloud, and therefore unavailable in 3rd party API.
Release date:
Map member terms to LpMembers
(RTL-1312)
Mapping of member terms to LpMembers has been implemented. After creating member in AccountService, it is possible to check the approval of the member terms.
Convert to Asp.Net Core 3.1
(RTL-212)
MemberInfoService was converted to target Asp.Net Core 3.1 and use latest version of LRS.MultiTenantService_packages.