...
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.
...
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.
...
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
...
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.
...
Process Overview
The search process for file information involves several key steps, starting from user initiation to the final display of search results. The following sections detail each step in the process.
Step 1: User Initiates Search
Action: The user initiates a search for specific file information.
Interface: The search is conducted using a search bar or input field on the file queue page or a dedicated search interface.
...
Step 2: Frontend Sends Request
Action: The frontend application captures the user's search query.
Request: The search query is encapsulated in a request and sent to the backend server for processing.
Data Sent: The request typically includes the search term(s) and any additional filters or parameters specified by the user.
Step 3: Backend Searches File Queue Data
Action: Upon receiving the request, the backend server initiates a search operation.
Database Query: The backend performs a query on the file queue data, searching for records that match the search query.
Search Criteria: The search operation may include matching filenames, dates, statuses, or other relevant metadata associated with the files.
Step 4: Backend Returns Filtered Results
Action: The backend processes the query results and filters out the relevant records.
Response: The filtered search results are then encapsulated in a response.
Data Returned: The response includes all relevant records that match the search criteria, formatted for easy consumption by the front end.
Step 5: Frontend Displays Results
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.
Buttom Flow
User Filters Records by Created Date(Advance Search):
User selects a date range or enters specific dates to filter records by created date.
Frontend sends a request to the backend with the selected daterange.
Backend filters the file queue data based on the specified date range.
Backend returns the filtered results to the frontend.
Frontend displays the filtered results to the user.