...
Updated the exist search bar inside the home screen on to accept the loyalty id.
...
Add Adding a new line in this message to indicate the new kind of data (loyalty id) and a new validation to the input that will expect the LoyaltyId(UUID) format.
...
Update the admin app to consume this from loyalty APIthe loyaltyId and communicate to loyalty API. Creating a new method to communicate the AdminApp to Intl Loyalty Middleware service. This method will receive the loyaltyId and will return the specific loyalty user attributes, cognitoID(User ID) and email.
Zenuml sequence macro lite | ||||||
---|---|---|---|---|---|---|
|
Add new graphQl call FE to BE in Admin App.
...
| |
All this idea already validate in a POC.
Country Solution
To the above flow works, a new information is necessary. The Loyalty Service expect in all call, the country in ISO format be specified (ES, PT, UK, …). Current the Admin App doesn’t have a way to delivery this properly. After an AWS analyses, was found that majority of the users are roles admin, and this role follow this format: ISO country + “-admin”. Based on this, is possible ready this information in the search page, split this to get the country code and send with the loyaltyId, making possible all the flow without any other configuration or creation (except the code mentioned in this document).
Expand | ||
---|---|---|
| ||
Schemas/Customer
queries/customersCreate a new query inside the customers queries hooks/use-universal-searchCreate a use query for consume the customerByLoyaltyId Add on the map section the new query universal-search/searchInstructionsAdd new descriptions to this list for loyalty id The text for loyaltyId already exist in Lokalize, avoiding the necessity of create a new string text. |
...