Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 15 Next »

🛠️ 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, 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.

image-20240521-182151.png

Add a new line in this message to indicate the new kind of data (loyalty id)

image-20240521-182342.png

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.

 Detailed solution

Schemas/Customer

  • Update the Query with the new method customerByLoyaltyId and update graphQl queries

    image-20240521-201830.png

  • Create a new method customerByLoyaltyId inside the Query resolvers section (with the same signature and name of query above)

    image-20240521-200957.png

    • To get the User from Loyalty serivce, can be used this provider

    image-20240522-191903.png

queries/customers

Create a new query inside the customers queries

image-20240522-195309.png

Create a use query for consume the customerByLoyaltyId

image-20240522-194947.png

Add on the map section the new query

image-20240522-195002.png

universal-search/searchInstructions

Add new descriptions to this list for loyalty id

image-20240522-204049.png

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

  • No labels