(TFS 173223:)

When a new member is added, the Member Id will be stored as a hashed value. The hashed value can be used as a variable when sending a link to landing page in a SMS (Variable=@HashedMemberId) A 3rd party can use the hashed value to look up the member with the new method GetMemberByHashedId in Member Service.

The hashed value will always represent the member Id, not any other identifiers like MobileNo or e-mail address.

(TFS 171321:)

Database changes and logic to enable automatic import of employees from an external source (eg. customers) to the Loyalty database. Employees will be created as new members flagged as employees. When an employee is inactivated, the employee will be removed from the Loyalty database. If a new employee already exists as a member, the existing member will be flagged as an employee and If the employee is inactivated the employee flag for the member will be removed. The import requires Social security number (eg. Swedish personal number) to be used as identifier. The automatic import will be performed in a LIP job which will be part of version 2.9.240 of Chain web