Page Comparison

...

This form provides the agent with more detailed information; therefore, we need to modify certain parts of the code.

Acceptance Criteria

1 - Display of Information on Screens

• 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 (displayed as a negative value, e.g., “-60”)

  • Transaction Points (points earned minus points used)

  • User's Final Points in that order.

2 - Display of Orders and Status

• Given that the support user accesses the orders screen and understands the meaning of each status,

• When the screen is loaded,

• Then all orders should be displayed, including all relevant statuses:

  • Claimed: Success status where points are credited or debited.

  • Confirmed: Order completed but not finalized (e.g., delivery not completed), where the points do not impact the user's total.

  • Void: Canceled order where the points do not impact the user's total.

3 - Feature Flag

• Given that there is new data to be displayed,

• When the feature flag is activated,

• Then the new data should be displayed in the user interface.

• And when the feature flag is deactivated, the new data should be hidden.

4 - Points Calculation

• Given that the points received, used, bonus, and final points are derived from the loyalty system,

• When the transactions are processed,

• Then no changes should be made to the existing calculations.

• And we will not be responsible for correcting and/or altering loyalty rules.

Development

Backend:

transactionDetails {
  person {
    currentPoints
  }
}

...