You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 20
Next »
๐ ๏ธ Potential Solutions
Update the exist search input to accept and search by loyalty ID, and communicate with loyalty service to get the consumer information.
โ
Proposed Solution
Updated the exist search bar inside the home screen on to accept the loyalty id.
Add a new line in this message to indicate the new kind of data (loyalty id)
Update the admin app to consume this from loyalty API
Add new graphQl call FE to BE in Admin App.
Add new resolver (getUserByLoyaltyId) in BE to consume the Intl Loyalty Middleware service. This resolver will receive the loyaltyId and will return the user attributes.
ย Detailed solution
Update the Query with the new method customerByLoyaltyId and update graphQl queries
Create a new method customerByLoyaltyId inside the Query resolvers section (with the same signature and name of query above)
and this is the loyalty response
{
"createdAt": "string",
"id": "string",
"name": "string",
"updatedAt": "string",
"clientUserId": "string",
"dateOfBirth": "string",
"email": "string",
"emailVerified": true,
"expirationBuckets": [
{
"expirationDate": "string",
"pointsToExpire": 0
}
],
"loyaltyTier": {
"loyaltyTierExpiryDate": "string",
"loyaltyTierKey": "Tier_1",
"pointsEarnedInTimeConstraint": 0,
"startAt": "string"
},
"metadata": {
"additionalProp1": "string",
"additionalProp2": "string",
"additionalProp3": "string"
},
"offerRedemptionAvailability": {
"availableAfter": "string",
"transactionId": "string"
},
"phoneNumber": "string",
"phoneVerified": true,
"points": 0,
"pointsEarningDisabled": true,
"pointsExpiryDateKey": "string"
}
queries/customers
Create a new query inside the customers queries
hooks/use-universal-search
Create a use query for consume the customerByLoyaltyId
Add on the map section the new query
universal-search/searchInstructions
Add 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.
โ ๏ธPotential Challenges
Was made a POC to map all the challenges and no one appear.
๐ฐ Cost
No additional cost will be necessary.
๐๏ธ Configuration
No configuration will be necessary.
๐ Metrics
๐๏ธ Delivery Plan
๐งโ๐ QA Plan
โ ๏ธ Call-outs
No call-outs
Add Comment