Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Release date:

IdentifierUpdate Generated for Deleted Members

(RTL-3032)

MemberInfoService do not generate IdentifierUpdate events for deleted members.  MemberInfoService is not producing 2 events (IdentityDeactivated & IdentifierUpdated) but just correct one (IdentityDeactivated) when member is deactivated/deleted. That means, the 2 events are not triggered at the same time and do not cause problem in AS.

LoyaltyParams fetch fails on cache refresh

(RTL-3033)

MemberInfoService always have loyalty parameters available. Methods using GetLoyaltyParams (GET GetMemberIdentity, POST PostMemberIdentity) do not generate errors for getting loyalty parameters. 

Improve realtime index maintenance

(RTL-3188)

New janitor job's scheduled trigger, which will rebuild most fragmented indexes every 30min according to following logic:

  • if fragmentation >90%, then rebuild
  • if fragmentation between 50% and 90%, then reorganize

Improvement of the MemberInfoService API validation 

(RTL-3209)

PersonalIdentifiers are validated when creating MemberIdentity in MemberInfoService API and an appropriate error is returned.

Exception on Duplicate Identity Delete

(RTL-3354)

The issue with the handling of a batch containing duplicated identity was resolved. That means, now in such cases the MemberIdentityMerger is logged with status 'Completed' and the appropriate message about duplicated identity is logged in the database. 


Release date:

Fill in WebUserId when updating LpMember

(RTL-2004)

WebUserId field is filled when member data is updated in MemberService from MemberInfoService or new member is created

Handling of member deletion

(RTL-1608)

When member is anonymized in 3rd part system, then appropriate member is removed from Account Service and the records in Service Bus Explorer are correctly displayed.


Release date:

Changing Household Issue

(RTL-2332)

Moving members from household A (containing more than 2 members) to separate household B when the MemberIdentifierMode is set to MemberNumberAsIdentityNumber cause LpMemberMerger to successfully update member data in MemberInfoService. What is more, validation for LpMemberMerger and MemberIdentityMerger has been changed and from now on member card number is unique for person, not for personal membership as before.

...