Design a Solution DB
Design Process flow
Create REST Provider End-point
Publish the Provider in WebFrom
1. Design Solution DB
In this use case data is stored in Solution DB and from there you need to write a joining query to fetch the data from the backend.
This joining query will be based on what attribute you need to fetch in UI, like here we are fetching File Phase, Error Description, Total Record Count, Unique Record Count, Duplicate Record Count, File Status, etc.
Here is the structure of the tables which are their DB.
2. Design Process flow
Process Overview
When the file queue page is accessed, the backend server performs the following steps to ensure that all relevant file queue data is accurately retrieved and displayed on the front end. Here are three flows working and each flow has a purpose.
...
a. Default Flow: To retrieve all file information
Step 1: Receive Request:
The backend server receives a request from the frontend to access the file queue page. This request initiates the process of retrieving the necessary file queue data.
Step 2: Query the Database:
...
After successfully querying the database and retrieving the necessary data, the backend server sends the retrieved data to the front end. This data is then displayed on the file queue page, providing users with a comprehensive view of the file queue status and details.
...
b.Top Flow: Search by Filename & Transaction Id
This flow process is for searching specific file information within the system. It enables how the user initiates the search, the interactions between the front end and back end, and the final display of the filtered results to the user.
...
Action: The front end receives the response from the backend.
Display: The filtered search results are displayed to the user clearly and organized.
User Interface: The results can be displayed in a list, table, or any other suitable format, allowing the user to browse and analyze the information easily.
c. Buttom Flow - Advanced Search Option
User Filters Records by Created Date(Advance Search):
User The user selects a date range or enters specific dates to filter records by the created date.
Frontend sends a request to the backend with the selected daterange.
Backend The backend filters the file queue data based on the specified date range.
Backend The backend returns the filtered results to the frontendfront end.
Frontend displays the filtered results to the user.
...