Work with Requests

The AVEVA Data Pipeline Admin Dashboard UI consists of a dedicated Requests tab under the existing application area for the selected asset.

This section allows you to monitor register configuration validation requests in a paginated way, download execution output when available, and track request status for supported operations.

For a detailed explanation of each type of validation, you can refer to the Validate section in the View model details page topic.

The Requests section shows the requested information in a paginated table and provides the following features:

• Refreshes the list.

• Filters the results.

• Sorts supported columns.

• Downloads request logs.

Requests dashboard

After the Requests tab is selected, the Requests page is loaded with focus on the existing requests in a paginated manner.

From this list you can perform the following actions:

• refresh the request list by clicking the Refresh button.

• filter requests by opening the Filter pane.

• sort supported table columns such as Request ID, Model ID, Message, Created By, and Last Updated.

• download execution logs or generated EIWM files by selecting the download icon under the Download column when logs are available.

The table includes request details such as Request ID, Model ID, Datasource, Datasets, Message, State, Created By, Last Updated, and Download.

An information banner is displayed at the top of the page to indicate that request data for any operation is maintained for 30 days.

Request table layout

The Requests dashboard shows the following columns:

Filter requests

The Requests page provides a Filter button in the top-right area of the dashboard. After selecting this button, the filter pane appears and you can narrow the request list using one or more criteria.

The filter pane supports the following options:

• Search or query filter: search request by Model ID.

• Date range filter: filter requests using From Date and To Date values.

• Created By filter: filter requests based on the user who initiated them.

• State filter: select one or more request states to display.

When filters are applied, the table refreshes to display only matching requests and pagination resets to the first page.

Sort requests

You can sort requests by selecting a sortable column header. The first selection sorts in ascending order, the second sorts in descending order, and another can return the table to its default sorting behavior.

The following columns can be sorted:

• Request ID

• Model ID

• Message

• Created By

• Last Updated

The default sort shows the most recently updated requests firsts:

Pagination

The Requests dashboard displays pagination controls at the bottom of the table. You can navigate between pages and select how many requests must be displayed per page.

The page size options include:

• 10 items per page

• 20 items per page

• 50 items per page

• 100 items per page

Pagination preserves the current page during sorting and resets to the first page when filters are changed.

Downloading request logs

For requests that have generated logs, the Download column displays an enabled Download icon. Selecting this icon starts the log download process.

The downloaded file includes execution logs or EIWM files that can be used for troubleshooting, audit, and support activities.

Logs are available when the request has progressed beyond the initial state and log files have been generated. For requests still in the Initialized state, the download action is disabled or shown as unavailable.

If log download fails, the user must refresh the page and try again. If the issue continues, you must contact support with the Request ID, state, and timestamp information.

Request states

Each request displays a state that indicates where it is in the processing lifecycle. The state is displayed with a visual indicator for quick identification.

Typical request states include:

• Initialized: the request has been created but processing has not started.

• Completed: the request finished successfully.

• Failed: the request encountered an error and did not complete successfully.

Completed and failed requests generally have logs available, while initialized or queued requests may not have logs yet.

Data retention

The Requests page displays an information message that the requests data for any operation is maintained for 30 days.

This means:

• request records are retained for 30 days from creation.

• older records are automatically removed.

• important logs should be downloaded within the retention window.

Common use cases

Monitor active requests

You can open the Requests tab, open the Filter pane, select states, and review the filtered list to monitor currently running operations.

Troubleshoot failed requests

You can filter by Failed or Error state, sort by Last Updated to see recent failures, and download logs to investigate the error details.

Audit user activity

You can filter by Created By and optionally add a date range to review requests submitted by a specific user during a selected time period.

Track a specific request

You can use the search filter to enter a Request ID and quickly find the request details, current state, timestamps, and logs.