🛠️ Potential Solutions
Note: this section should be short and sweet, documenting notes about different solutions that were considered during ideation. Can just be a link to a whiteboard for example. Expected outcome: one solution is chosen and documented in more detail under Proposed Solution.
Update the exist search input to accept and search by loyalty ID.
✅ 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
Tech discovery
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
List here potential challenges that have come across the opportunity definition or from the potential solutions so far.
💰 Cost
Describe any additional cost this solution may imply.
🎛️ Configuration
Include here any configuration required (Sanity, LaunchDarkly flags, etc.) required to enable the solution.
📈 Metrics
Describe the metrics that will be used to measure the solution’s success, as well as how to measure those KPIs.
🗓️ Delivery Plan
Link to the task or list of all the tasks required to deliver the solution, along with its progress.
🧑🚒 QA Plan
Testing scenarios. See example /wiki/spaces/EGMT/pages/4080861189.
⚠️ Call-outs
Tip: Document here any improvement or discussion regarding the feature
0 Comments