🛠️ 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 a new backend structure to connect the admin app search user to the loyalty service, using loyalty middleware as a bridge to get the user information from loyalty users table.
Schemas/Customer
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)
To get the User from Loyalty serivce, can be used this provider
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
To be defined by Design/Data Team.
🗓️ Delivery Plan
Link to the task or list of all the tasks required to deliver the solution, along with its progress.
🧑🚒 QA Plan
To be defined by QA Team.
⚠️ Call-outs
No call-outs
0 Comments