Design a Solution DB
Design Process flow
Create REST Provider End-point
Publish the Provider in WebFrom
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.
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.
1. Default Flow
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:
Upon receiving the request, the backend server queries the database to retrieve all relevant information. The data retrieved includes, but is not limited to, the following:
File Phase, Error Descriptions, Total Record Coun, Unique Record Coun, Duplicate Record Count, File Status
Step 3: Send Data to Frontend:
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.
Top Flow :
This workflow with multiple parallel processes starting from a single start event.
This consists of three flows as per the search criteria. Here's a detailed description:
Top Flow - This flow use to call all
