...
Action: The backend sends the retrieved data to the front end.
Outcome: The frontend displays the data, providing users with a comprehensive view of the file queue status and details.
...
Process flow activity:
Source Activity - The source comprises a database. It is necessary to create DbInfo and DbLayout to be invoked in the source activity
...
a. To efficiently retrieve attributes from multiple tables and display relevant information on the user interface, you must utilize the EDIT Query option. Additionally, you implement conditions to filter the data as needed.
...
Table Name: SQL Query
SELECT FQ.ID,FQ.PARTNER_NAME,FQ.TRANSACTION_TYPE,FQ.FILE_REF_ID,FQ.PHASE,FQ.OVERALL_STATUS,FQ.ERROR_CODE,FQ.INCOMING_FILE_DATE,FQ.TOTAL_RECORDS,FQ.DUPLICATE_RECORDS,FQ.UNIQUE_RECORDS,FQ.GROUP_ID,FQ.V3_GROUP_ID,FQ.V3_PHASE,FQ.V3_STATUS,FQ.V3_TOTAL_RECORDS,FQ.V3_GOOD_RECORDS,FQ.V3_ERROR_RECORDS,FQ.V3_PASS_PERCENTAGE,FQ.V3_ERROR_MESSAGE,FQ.CORE_PHASE,FQ.CORE_STATUS,FQ.CORE_TOTAL_RECORDS,FQ.CORE_GOOD_RECORDS,FQ.CORE_ERROR_RECORDS,FQ.CORE_PASS_PERCENTAGE,FQ.CORE_ERROR_MESSAGE,FQ.CREATED_BY,FQ.LAST_MODIFIED_BY,FQ.LAST_MODIFIED_DATE,FND.FILE_NAME,FND.CREATED_DATE,ER.ERROR_MESSAGE,FQ.TRANSACTION_NAME FROM file_queue FQ LEFT JOIN file_name_details FND on FND.FILE_QUEUE_ID=FQ.ID LEFT JOIN error_code ER on FQ.ERROR_CODE=ER.ERROR_CODE
Where Clauses:
WHERE FND.FILE_TYPE='INPUT_FILE' and DATE_SUB(NOW(), INTERVAL 30 DAY) < FND.CREATED_DATE ORDER BY FQ.ID DESC
Target Layout - The JSON schema for the source data (database) will be designed to be utilized in the RESTful API for the user interface. JSON is selected for its compatibility with RESTful APIs.
...
Mapping - You are required to load the database schema and the target schema (JSON) to finalize the mapping process.
...
Context Target -The target will be ContextTarget to store data in the flow for the REST provider.
...
b.Top Flow: Search by Filename & Transaction Id
...
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.
Process Steps
Step 1: User Initiates Search
...
This Process flow is used for advanced search in which a user can filter records based on their start date and end date using the Advanced Search functionality. This includes the interactions between the frontend and backend systems to accomplish this task.
Process Steps
1. Date Range Selection
User Action:
The user selects a date range or enters specific dates to filter records by the created date.
UI Elements:
Date pickers for selecting the start and end dates.
A button to submit the filter request.
...
Select the Response Schema ( ExampleFor example, we are opting for the schema that has been utilized in the process flow as the target schema)
...
Save it.
...