...
Document Status |
| ||||||
---|---|---|---|---|---|---|---|
Document Owner(s) | |||||||
Reviewers |
Table of Contents |
---|
🛠️ Potential Solutions
...
Given that the user accesses the Loyalty Transactions, Orders, and Recent Orders screens,
When the transactions are loaded,
Then the system should display the following information in order:
Initial Points
Points Earned (regular points and bonus points)
Points Used burned (displayed as a negative value, e.g., “-60”)
Transaction Points balance (points earned minus points used)
User's Final Points in that order.
...
Expand | ||
---|---|---|
| ||
File: src/remote/queries/fragments/intl-loyalty-transaction.ts
DOD: Return the |
Frontend:
We can see the discussion about this in this thread: https://rbidigital.slack.com/archives/C067D4XK9D5/p1724350040702039
The labels are:
...
Expand | ||
---|---|---|
| ||
Name suggestion: display-points-balance |
...
Expand | ||
---|---|---|
| ||
File: src/components/intl-loyalty/points-balance.tsx
|
Expand | ||
---|---|---|
| ||
File: src/components/customer-orders/order-timeline-item.tsx
|
Expand | ||
---|---|---|
| ||
File: src/components/points-details-card/index.tsx
|
Expand | ||
---|---|---|
| ||
Local src/utils/…
|
...
Step | Expected Results |
---|---|
If the FF is enable | Show new fields on the screens:
|
Existing orders with the status CLAIMED | Show the order with earned values, used values, transactions, initial points, and final points. In this status, the calculation must change the user's final points. |
Existing orders with the status CONFIRMED | Show the order with earned values, used values, transactions, initial points, and final points. In this status, the calculation must not change the user's final points. After complete delivery this status change to CLAIMED or VOID |
Existing orders with the status VOID | Show the order with earned values, used values, transactions, initial points, and final points. In this status, the calculation must not change the user's final points. |
If the user has 2 or more order with CONFIRMED | Show the order with earned values, used values, transactions, initial points, and final points. In this status, the calculation must not change the user's final points. After complete delivery this status change to CLAIMED or VOID For each order, the initial and final points are the same because confirmed transactions do not accumulate points. |
If the user has 2 or more order with CONFIRMED and change to VOID | Show the order with earned values, used values, transactions, initial points, and final points. In this status, the calculation must not change the user's final points. The order change to VOID and don’t change the final poins |
If the user has 2 or more order with CONFIRMED and change to CLAIMED | Show the order with earned values, used values, transactions, initial points, and final points. In this status, the calculation must not change the user's final points. The order change to CLAIMED and change the final poins |
If the user has 2 or more order with CONFIRMED and change one to CLAIMED and other to VOID | Show the order with earned values, used values, transactions, initial points, and final points. In this status, the calculation should adjust the user's final points solely based on the value of the order that has been marked as claimed. The void should be completely disregarded, as its values are outdated. Attention: If the oldest order is successfully completed (CLAIMED) and the most recent one fails (VOID), the value of the CLAIMED order will impact the final points. However, the VOID order will not impact the points and will retain its initial and final values as outdated, since when an order is marked as VOID, it is not considered. |
...