| Table of Contents |
|---|
🛠️ Potential Solutions
Enhance existing search input to accept and search by loyalty ID , and communicate with loyalty service to get the consumer information.
...
Enhance the existent search bar inside the home screen to accept the loyalty id.
For that, it can be added a new line to indicate highlight the new type of data (loyalty id) and a new validation to the input that will expect the LoyaltyId(UUID) format.
...
Enhance admin app to consume the loyaltyId and communicate to loyalty API.
For that, it can be created a new method in AdminApp to communicate with Intl Loyalty Middleware service.
This method will receive the loyaltyId and country and will return the specific loyalty user attributes, cognitoID(User ID) and emailcustomerId and email. With the customerId FE is already prepared to fetch customer related data as it does for other input searches.
| Zenuml sequence macro lite | ||||||
|---|---|---|---|---|---|---|
| ||||||
This idea is validated in this POC
How to get the input data?
Since loyaltyId information are stored in distributed tables per country. Loyalty Middleware API requires country as part of the inputs. E.g.: loyalty-es-users-plk-dev
For that, proposed solution intends to pass the operator country using the following logic. :
Go through all operators user groups and check one-by-one the <country>-admin groups.
...
Based on that, admin-app needs to provide this country as part of the inputs.
...