Acceptance Criteria
1. Access to the Audit Page
Given the operator is on the restaurant selection page on the DOP platform,
When they select one or multiple restaurants and click the “Review Restaurants” button,
Then they should be redirected to the audit page displaying product availability data.
2. Product Availability Filtering & Searching
Given the operator is on the audit page,
When they enter a product name in the search bar or apply filters,
Then the displayed table should update to show only the matching products.
3. Infinite Scroll for Product List
Given the operator is viewing the product table,
When they scroll down,
Then more product data should load dynamically without pagination buttons.
4. Product Audit Report Download
Given the operator has applied filters on the audit page,
When they click the “Download Restaurants Report” button,
Then a report should be generated and downloaded containing only the filtered data.
5. Automated Product Reactivation Reminder
Given a product has been disabled,
When it reaches a predefined reactivation threshold,
Then an automated reminder should be sent to the Store Manager.
6. Real-Time Product Availability Updates
Given a product’s availability status changes,
When the operator accesses the audit page,
Then the updated status should be reflected in real-time.
7. Efficient Backend Data Handling
Given a user requests product data via the audit page,
When the system retrieves data from the backend,
Then it should use AWS Elasticache to ensure fast response times.
8. Error Handling for Data Retrieval
Given the system fails to fetch product availability data,
When a query to DynamoDB or Elasticache fails,
Then the user should see an error message and a retry option.
9. Monitoring & Logging
Given the system is live,
When users interact with the audit page,
Then logs should be recorded in Datadog for monitoring usage and errors.
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
...
Today we already know that the application has performance problems to deal with big content on the table (high loadings, slowness, etc.). To deal with this problem, we have the following proposals:
Infinite Scroll
To-do
✅ Proposed Solution
New page to audit products
Important: TheUX team is defining the experience. This document is already out-dated. The main idea could be reused still.
...
Expand | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
Update the Rematch models index:
|
Front end to-do: Do we need a pagination system? The solutions to deal with performance problems and querie section will answer that.
...
New logic to schedule and automatic reactivation of disabled products
To-do: to confirm if this will be part of this first deliverable or if we’ll only deliver the audit page for now.
Solutions to deal with performance problems and queries
Today the app depends on data from different places to have the products complete data (considering availability, etc). I'll let here just an example of how the data flow is working for the products page/editor flow → This is only intended for the discovery/draft phase. We can delete this text and the image below later.
...
To-do: proposals to solve this data composition/orchestration layer for the new page and products data
# 1 - To-do solution 1
📈 Metrics
Info |
---|
Describe the metrics that will be used to measure the solution’s success, as well as how to measure those KPIs. |
...