Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 10 Next »

  1. Design a Solution DB

  2. Design Process flow

  3. Create REST Provider End-point

  4. 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.

image-20240620-115215.png

Once the flow has been designed, it needs to be published for the REST provider.

image-20240621-060942.png

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:

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.

image-20240620-113900.png

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.

image-20240620-115506.png

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.

image-20240620-120055.png

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.

c. Button Process Flow - Advanced Search: Filtering Records by (Start Date & End Date)

image-20240621-055057.png

Overview

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.

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.

2. Request Submission

  • Frontend Action:

    • The frontend constructs a request with the selected date range like Start Date & End Date

image-20240621-060333.png

3. Date Filter

  • Backend Action:

    • The backend processes the request by filtering the file queue data based on the provided date range.

    • Implementation:

      • The backend queries the database to retrieve records where the createdDate falls within the startDate and endDate.

4. Response Handling

  • Backend Action:

    • The backend returns the filtered results to the front end.

5. Display Results

  • Frontend Action:

    • The front end processes the response and displays the filtered results to the user.

  • UI Elements:

    • A table view to present the filtered file records.

    • The results section updates dynamically upon receiving the response.

image-20240621-060201.png

3. Create REST Provider End-point

Overview

A REST (Representational State Transfer) Provider is a service that offers resources and functionalities over HTTP(S) using standard REST principles. It enables clients to interact with the service through predefined APIs, facilitating the integration and communication between different systems.

In this particular use case, the process flow is shared by developing a REST provider that will eventually be integrated with the user interface.image-20240621-061858.png

Follow the steps below to create a REST Provider:

  1. Click Configure > WEB SERVICES > REST Provider.

  2. Click Create REST Provider. 

  3. In Create REST Provider window, type the name and description of the new Web Service Provider service in the Name and Description fields respectively.

image-20240621-062337.png

  1. Type API Version, for example, your API version can be 1

  2. Type the resource end path URL in the Resource End Path field. The URL can be static or dynamic. Static URL example:  /get/FileQueueDetails 

  3. Select the process flow name to trigger with the web service from the Process Flow Name field.

    1. Set parameterName attribute of the context source should be restRequest

      1. searchQuery - To enable the Advanced Search option

      2. start_date - Advanced search criteria

      3. end_date - Advanced search criteria

      4. start - Pagination control in the user interface

Select the process flow name to trigger with the web service from the Process Flow Name field.

image-20240621-064010.png

  1. To add methods to your activity, click Add Method and do the following.

    1. In this use case, you need to select GET as the method type.

image-20240621-063007.png

  • No labels