...
The "time period for graphs" section of the Member Statistics Dashboard has been added.
CustomerService API New features and improvements
(RTL-118)
We are excited to announce a new release for our Customer service API. This update includes a number of improvements and new features to enhance your experience with our API.
Changes to the API:
- The following changes was done to the API. Backwards compatibility is kept so that the old API endpoints still work:
- API/Association -> API/Associations
- API/BusinessCustomer -> API/BusinessCustomers
- API/MemberIdentity -> API/Identities
- API/Membership -> API/Memberships
- Added personal customer relationships to identity (import & export) - You can import and export personal customer relationships to the API, making it easier for you to manage your customer data. Details about the changes can be found in Swagger
- Slight refactoring of business customer - We have made some changes to our business customer functionality for consistency. The CustomerNo field has been replaced by CustomerNumber, and the storage for CustomerRemarks has been simplified and is stored as a JSON object in a single field on the customer.
- Identity API improvements - The Identity API provides the same functionality as before, but in a more RESTful manner, also able to return multiple results for email/mobile query, which might be the case when introducing customer relationships.
- Customer groups - import/export and rest API functionalities for customer groups, making it easy for you to manage and organize your customer data.
- Loyalty program sharding - better support for loyalty program sharding for business customers and customer groups.
Configuration:
Tenant config for MemberInfoServer: The IdentityDataProvider parameter determines which provider to use for getting and setting identity/member/customer data in the API. The default provider is "Hybrid," which uses the MemberService as the master for members and stores a copy of members in the database. The provider "Standalone" fetches and stores everything in the database.
Improvements
Header | Description |
|---|---|
Missing association name from MemberService(on-prem)(RTL-5440) | When returning identity from MemberService ExternalNumber is passed as default association name. |
Remove loyaltyprogram from membership (RTL-5320) | LoyaltyProgramNumber was removed from MemberIdentity. |
Icon for Loyalty menu
...
The new Loyalty icon has been implemented and applied for the loyalty main menu entry and the old loyalty icon is applied for the customer main menu entry.
Improvements
Header | Description |
|---|---|
| Remove dependence to Organization number (RTL-5112) | An organization number is not required when creating a member in MemberInfoService. It is possible to have no value in this field: NULL. |
| Member Identities View Missing Members (RTL-5042) | All members are displayed in the member grid, and it is possible to filter on them. |
...
There was added a new view in Chain Web where member identities are listed.
Improvements
Header | Description |
|---|---|
| Fetching LpMember with no existing loyalty program (RTL-4525) | Loyalty program number is validated when calling MIS API GetMemberIdentity.
|
| Timeout do not cause FlatBatchJson to retry (RTL-4851) | Upon page validation exception batch lines are marked as failed (and ready for retry), and not as processed ok. |
...
It is possible to add an association without an uploaded logo.
Thus associations without ImageURL are synchronized correctly to the cloud and are available on the webshop without a logo.
Improvements
Header | Description |
|---|---|
| MemberIdentityMerger aborted as a deadlock victim (RTL-4262) | Deadlock during merging of data does not abort MemberIdentityMerger. Deadlocked merging data is marked as faulted and retried on another run |
...