Service Requests

The Service Requests page helps users manage requests created from Data Quality Scheme failures or rule violations. It enables stewards and administrators to track remediation activities, monitor progress, and ensure data quality issues are resolved through defined workflows.

Each request is linked to a scheme rule, associated object, and failed validation outcome. Users can search, filter, sort, and review requests based on priority, status, ownership, or recent activity.

This page is useful for monitoring issue resolution from request creation through final closure.

Request List View

The Request List View displays all service requests associated with the selected Data Quality Scheme.

Field	Text
Request ID	Displays the unique identifier of the service request. Selecting the ID opens the related request details page for full lifecycle review.
Summary	Displays a short description of the issue raised from the failed scheme or rule validation.
Priority	Displays the severity level, such as Low, Medium, High, or Critical, based on business impact.
Scheme Rule Name	Displays the rule that triggered the request, helping users understand which validation failed.
Object Name	Displays the affected table, file, or data object linked to the issue.
Status	Displays the current request state, such as Open, Assigned, In Progress, Resolved, or Closed.
Latest Comment / Remarks	Displays the most recent update, remediation note, or progress comment added to the request.
Requested By	Displays the user or system process that created the request.
Created On	Displays the date and time when the request was created.
Last Updated On	Displays the most recent date and time when the request was modified.

Search, Filter, and Sort

Users can quickly locate requests using search and filtering options.

Search helps users find requests by Request ID, Summary, Scheme Rule Name, Object Name, or comments. Filters can be applied for Priority, Status, Requested By, and created or updated dates. Sorting can be applied to date, priority, identifier, and status fields.

These capabilities help users focus on critical issues, open requests, recently updated items, or requests related to specific rules or objects.

Status Definitions

• Open indicates the request has been created and is awaiting action.

• Assigned indicates the request has been routed to an owner or responsible team.

• In Progress indicates remediation work is currently underway.

• Resolved indicates the issue has been fixed and is pending closure or validation.

• Closed indicates the request lifecycle is complete.

These statuses help users monitor progress and operational accountability.

---

Copyright © 2026, OvalEdge LLC, Peachtree Corners, GA, USA.