🛠️ 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 to accept the loyalty id. 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 the 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.

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).

 Detailed solution

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)

  

  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"
  }

  • To get the User from Loyalty service, 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

🗓️ Delivery Plan

🧑‍🚒 QA Plan

⚠️ Call-outs

No call-outs