> For the complete documentation index, see [llms.txt](https://docs.ovaledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ovaledge.com/release8.2/data-quality/data-quality-rules/rule-executions.md). # Rule Executions The Rule Executions tab provides a complete history of Data Quality Rule (DQR) executions. It offers a high-level summary of execution outcomes, object-level performance, execution timings, and user-related information. This tab helps users track how often a rule has been executed, analyze its results, review logs, and understand the behavior of associated objects during each execution. Users can view details such as execution logs, counts of passed and failed objects, counts of undetermined or execution-failed objects, Rule Execution ID, overall result, total object count, execution duration, and the user who initiated the execution. The Rule Executions tab displays the following columns: * **Logs:** Click the eye icon in the Logs column to open the job logs for the selected Rule Execution ID. This provides a consolidated view of all DQR-level execution details without requiring users to navigate to the Jobs module. ![](/files/qsJjtGAXbFzZ7P3BhtOw) * **Log Options** * **Select Date:** Filters job logs based on the selected date and timestamp range. * **Search Job Logs:** Searches log content using a keyword. * **Filter Options:** Filters log entries by type—Info, Warning, or Error. * **Refresh:** Clears applied filters and displays the complete job log. * **Download:** Downloads the full job log file. * **Rule Execution ID:** Each execution of a Data Quality Rule generates a unique Rule Execution ID. This ID helps users differentiate between multiple executions and review execution-specific statistics. It supports tracking rule performance, understanding failures, and viewing detailed outcomes for each associated object. * Clicking the Rule Execution ID opens the DQ Rule Report for that execution.
* The DQ Rule Report provides a detailed view of a Data Quality Rule (DQR) execution. Each execution is uniquely identified by a Rule Execution ID, which helps users track, audit, and analyze the results of every run. The report consolidates summary information, execution statistics, object-level outcomes, and failed value details, enabling users to evaluate rule behavior and data quality performance. * The DQ Rule Report is divided into two core sections: * Rule Summary * DQ Rule Execution Details **Rule Summary** The Rule Summary section provides the high-level execution details for a specific rule run. It helps users understand when the rule was executed, who executed it, how long it took, and what the overall outcome was. **Rule Summary Field Descriptions:** * **Rule Name:** Displays the name of the Data Quality Rule executed. * **Purpose:** Shows the purpose or intent of the rule as configured by the user. * **Rule ID:** Unique identifier assigned to the Data Quality Rule. * **Rule Execution ID:** Unique identifier assigned to each execution of the rule. Used to track the execution instance. * **Job ID:** Background job identifier triggered during rule execution. * **Start Time:** Timestamp when the rule execution started. * **End Time:** Timestamp when the rule execution completed. * **Run By:** Username of the user who initiated the execution. * **Duration:** Total time taken to complete the rule execution. * **Result:** Displays the final execution result for the rule. Available statuses include: * **Passed** – The rule met its success criteria. * **Failed** – The rule did not meet its success criteria. * **Execution Failed** – Errors occurred due to connector issues or query failures. * **Undetermined** – Result could not be evaluated (e.g., table contains zero rows). * **Passed Objects:** Number of objects that passed the rule execution. * **Failed Objects:** Number of objects that did not meet the rule criteria. * **Execution Failed Objects:** Number of objects that encountered execution errors. * **Undetermined Objects:** Number of objects where results could not be evaluated. * **Total Objects:** Total number of objects included in the rule during execution. **DQ Rule Execution Details** The DQ Rule Execution Details section displays execution results for all Associated Objects included in the Data Quality Rule. Associated Objects can be table columns, file columns, tables, or files—depending on how the rule is configured. Each object in the rule is evaluated independently during execution, and the information shown in this section updates dynamically based on the object selected by the user. When a user selects an object from the list of Associated Objects, the following fields update to reflect the execution details for that specific object: * **Object Execution ID:** A unique identifier generated for the selected object during the rule execution. Each execution produces a new Object Execution ID for every associated object. * **Object Name:** Displays the name of the table, file, or column being evaluated. * **Database:** Updates to show the database for the selected object. * **Schema:** Displays the schema where the object resides. * **Table/File:** Shows the corresponding table or file name for the selected object. * **Column:** Shows the specific table or file column associated with the selected object. * **Result:** Displays whether the selected object Passed, Failed, was Undetermined, or had Execution Failed. * **Result Value:** Updates based on the calculation performed for that object (count or percentage, depending on success criteria). * **Passed Row Count:** Number (and percentage) of rows that met the function criteria. If the function does not support passed counts, N/A is displayed. * **Failed Row Count:** Number (and percentage) of rows that did not meet the criteria. If the function does not support passed counts, N/A is displayed. * **Failed Values (Eye Icon):** Displays failed values for the selected object (up to the configured limit), when supported. * **Total Row Count:** Total number of rows present in the object during execution. Each time a user switches to a different associated object in the list, the entire set of fields refreshes to display the execution results relevant to that specific object. This allows users to compare performance across objects and analyze how each one contributed to the overall rule result. * **Result:** The Result column displays the overall execution outcome for the rule. Available result types include: * **Failed:** The rule did not meet the configured success criteria. * **Passed:** The rule met all success criteria and completed successfully. * **Execution Failed:** The execution did not complete due to issues such as connection failures or DQ Function query errors. * **Undetermined:** The system could not determine the outcome. **Example:** If the associated table contains 0 rows, the result becomes Undetermined. * **Result Logic** * The execution result is determined based on the Success Criteria and the corresponding result value generated during execution: * If the result value meets the configured success criteria → Passed * If the result value does not meet the success criteria, → Failed * If the execution cannot be completed due to technical issues → Execution Failed * If the system cannot evaluate the rule (e.g., no rows, missing data) → Undetermined * An eye icon beside the Result field provides a detailed summary, including:
* **Result Value:** Displays the value calculated by the rule function during execution. This value may be a count or a percentage depending on the configured success criteria. * **Input:** Shows the input condition or comparison value that the rule used during execution, based on the function’s configuration and user-defined settings. * **Success Criteria:** Indicates the condition that determines whether the rule execution is considered successful (for example, “Result Value should be greater than 95%”). * **Passed Objects:** Displays the number of associated objects that met the rule's success criteria during execution. * **Failed Objects:** Shows the number of associated objects that did not meet the configured success criteria. * **Number of Service Requests Created:** Indicates how many service requests were generated as part of this execution when the Create Service Request on Failure setting is enabled. * **Number of Failed Values Sent to the Remediation Center:** Displays the count of failed values forwarded to the Data Quality Remediation Center, based on the configured maximum failed values limit. * **Downstream Objects Cautioned:** Shows whether caution was applied to downstream assets due to rule failure when the Apply Caution to Downstream Objects option is enabled. * **Passed Objects Count:** Displays the number of objects that passed the rule execution. * **Failed Objects Count:** Displays the number of objects that did not meet the rule criteria. * **Undetermined Objects Count:** Displays the number of objects with results that could not be evaluated. * **Execution Failed Objects Count:** Displays the number of objects where execution could not be completed due to technical issues. * **Total Objects Count:** Displays the total number of associated objects included in the rule. * **Start Time:** Displays the timestamp when the rule execution began. * **End Time:** Displays the timestamp when the rule execution completed. * **Duration:** Displays the total time taken to complete the rule execution. * **Run By:** Displays the username of the individual who initiated the rule execution. ### **Nine Dots Options (Rule Executions)** The Nine Dots menu provides several actions that users can perform within a Data Quality Rule. However, on the Rule Executions tab, only a limited set of options is available. The following actions appear in the menu, but some are disabled based on the nature of the References tab. * **Change Rule Status:** Allows users to change the Data Quality Rule status between Active and Draft. * **Run Now:** Executes the Data Quality Rule. The rule must be in the Active state. * **Activate Objects:** Marks selected associated objects as Active so they are included in rule execution. This option is disabled on the Rule Executions tab. * **Inactivate Objects:** Marks selected associated objects as Inactive, excluding them from rule execution. This option is disabled on the Rule Executions tab. * **Update Steward:** Allows users to update the steward of the Data Quality Rule. Available only when the rule is in the Draft state. This option is disabled on the Rule Executions tab. * **Regenerate Object Queries:** Regenerates Data Quality Function object queries when updates are made to the Functions Template. A background job performs the regeneration. This option is enabled only for objects of type Code. * **Remove Associated Objects:** Removes selected associated objects from the Data Quality Rule. Available only when the rule is in the Draft state. This option is disabled on the Rule Executions tab. * **Delete Contacts:** Removes added contacts from the Data Quality Rule. Available only when the rule is in the Draft state. This option is disabled on the Rule Executions tab. * **Delete Rule:** Deletes the Data Quality Rule. ## Object Execution Results The Object Execution Results tab provides detailed execution information for each object associated with a Data Quality Rule (DQR). It provides users with a complete view of how each object performed during each rule execution, enabling them to track outcomes at the object level.
The Object Execution Results tab displays the following columns: * **Rule Execution ID:** Each DQR execution is assigned a unique Rule Execution ID. This identifier helps distinguish one execution instance from another. When users click the Rule Execution ID, the DQ Rule Report is displayed.
![](/files/C8J6phYTfWyEc6Yyy1tc) * **Object Execution ID:** Each object associated with a data quality rule is allocated a unique Object ID for every execution. * To understand the relationship between Object Execution ID and Rule Execution ID, consider the following example:
Data Quality Rule NameEmail Validation
No. of Associated Objects3
Name of Associated ObjectsColumn 1, Column 2, Column 3
No. of Rule Executions4
Rule Execution IdObject Execution IdObject Name
201Column 1
201Column 2
201Column 3
212Column 1
212Column 2
212Column 3
223Column 1
223Column 2
223Column 3
234Column 1
234Column 2
234Column 3
In this example, each Rule Execution ID (20, 21, 22, 23) has one Object Execution ID shared across all three associated columns. This establishes a clear relationship between the rule execution and its associated objects. * The following columns offer contextual information about the associated data objects when a Data Quality Rule is created for table columns. These columns are listed on the Object Execution Results tab. * **Database:** Displays the database name. Users can filter to focus on specific databases. * **Schema:** Displays the schema name. Filtering helps narrow down results for easier analysis. * **Table:** Shows the table name associated with the object. Users can apply filters to locate specific tables. * **File:** Displays the file name associated with the object (where applicable). Filtering helps refine file-level results. * **Column:** Shows the table or file column name. Filters help refine the view to focus on specific attributes. * **Failed Values:** Displays the failed values identified after execution. Supported for Table Column and File Column functions. Clicking the eye icon shows the complete list of failed values for that column. * **Passed Row Count:** Indicates the number of rows that met the rule criteria. Values are retrieved from the source system and displayed as both count and percentage. If the function does not support passed counts, N/A is displayed. * **Failed Row Count:** Shows the total number of rows that did not meet the rule criteria. Displayed as both count and percentage, based on values retrieved from the source system. * **Total Row Count:** Displays the total number of rows in the associated object. Shown as both count and percentage, based on source system values. * **Result Value:** Displays the calculated result value after rule execution. This may represent a count or percentage, depending on how success criteria are configured. * **For example:** * Data Quality Rule Name: Checking Valid Email Format * **Purpose:** To evaluate the count of valid email values within a specified column. The rule checks whether the email values conform to the standard pattern of “” * After the rule execution, the following statistics have been generated:
Total Row CountPassed Row CountFailed Row CountSuccess CriteriaResult Value
5019 (38%)31 (62%)Result value count should be equal to 10019
In the example, out of a total of 50 rows in a table column, if 19 rows meet the criteria for records in the desired email format, then the Result Value will be 19. * **Result:** Shows the execution outcome of the DQR for each object. Possible values include: * **Failed:** The rule execution failed based on the configured criteria. * **Passed:** The rule execution completed successfully. * **Execution Failed:** The rule could not execute due to issues such as connector failures or query errors. * **Undetermined:** The system could not determine the execution outcome. * Clicking the eye icon provides a summary that may include: * Result Value * Input * Success Criteria * Maximum Failed Values for Remediation * Service Request ID * Failed Values sent to Remediation Center * Downstream Objects Cautioned * **Run On:** Displays the timestamp of when the associated object was last executed. Users can sort by this column to view rule executions in chronological order. ### **Nine Dots Options (Object Execution Results)** The Nine Dots menu provides several actions that users can perform within a Data Quality Rule. However, on the Object Execution Results tab, only a limited set of options is available. The following actions appear in the menu, but some are disabled based on the nature of the References tab. * **Change Rule Status:** Allows users to change the Data Quality Rule status between Active and Draft. * **Run Now:** Executes the Data Quality Rule. The rule must be in the Active state. * **Activate Objects:** Marks selected associated objects as Active so they are included in rule execution. This option is disabled on the Object Execution Results tab. * **Inactivate Objects:** Marks selected associated objects as Inactive, excluding them from rule execution. This option is disabled on the Object Execution Results tab. * **Update Steward:** Allows users to update the steward of the Data Quality Rule. Available only when the rule is in the Draft state. This option is disabled on the Object Execution Results tab. * **Regenerate Object Queries:** Regenerates Data Quality Function object queries when updates are made to the Functions Template. A background job performs the regeneration. This option is enabled only for objects of type Code. * **Remove Associated Objects:** Removes selected associated objects from the Data Quality Rule. Available only when the rule is in the Draft state. This option is disabled on the Object Execution Results tab. * **Delete Contacts:** Removes added contacts from the Data Quality Rule. Available only when the rule is in the Draft state. This option is disabled on the Object Execution Results tab. * **Delete Rule:** Deletes the Data Quality Rule. ## Service Requests The Service Requests tab lists all service requests generated for a Data Quality Rule. These requests are created when the Create Service Request on Failure toggle is enabled. Service Requests also contribute to the overall Data Quality Score, as the Service Request Score forms an important component of the DQ assessment.
The Service Requests tab displays the following columns: * **Request ID:** Each Service Request is assigned a unique Request ID upon creation. This identifier helps users locate, track, and manage individual service requests, ensuring complete traceability. * **Summary:** Displays an auto-generated description of the Service Request. The summary is constructed using the Data Quality Rule name, the associated object, and the success criteria used during rule execution. * **Template:**\ **Failure Data Quality Rule:** (Data Quality Rule Name) for (Associated Object) (Success Criteria during rule execution)
\ Clicking Summary opens the Service Request Details page, where users can view and manage the service request configuration.\ On this page, users can: * Update the Service Request Priority (Highest, High, Medium, Low, Lowest) * Change the Service Request Status (Pending Approval, Review, Approve, Reject) This interface provides a complete workspace for reviewing and updating Service Request details. * **Priority:** Displays the priority assigned to the Service Request. By default, new requests are created with Medium priority. Users can adjust the priority to one of the following: Highest, High, Medium, Low, or Lowest. Filtering options allow users to group Service Requests by priority for better organization. * **Object Name:** Displays the object for which the Service Request was generated. Users can search by object name to quickly locate and track requests related to specific objects. * **Status:** Displays the current workflow status of the Service Request. A request may move through several statuses, including: * Draft * Pending Approval * Reviewed * Rejected * Expired * Resolved * Request Closed These statuses provide transparency into progress and ensure structured collaboration. * **Latest Comments/Remarks:** Displays the most recent comments or notes added to the Service Request. * **Requested By:** Displays the username of the user who initiated the Service Request. By default, this is typically the Data Quality Rule Steward. * **Created On:** Shows the date the Service Request was created. Users can sort by this column to quickly view requests created or older. ### **Nine Dots Options (Service Requests)** The Nine Dots menu provides several actions that users can perform within a Data Quality Rule. However, on the Service Requests tab, only a limited set of options is available. The following actions appear in the menu, but some are disabled based on the nature of the References tab. * **Change Rule Status:** Allows users to change the Data Quality Rule status between Active and Draft. * **Run Now:** Executes the Data Quality Rule. The rule must be in the Active state. * **Activate Objects:** Marks selected associated objects as Active so they are included in rule execution. This option is disabled on the Service Requests tab. * **Inactivate Objects:** Marks selected associated objects as Inactive, excluding them from rule execution. This option is disabled on the Service Requests tab. * **Update Steward:** Allows users to update the steward of the Data Quality Rule. Available only when the rule is in the Draft state. This option is disabled on the Service Requests tab. * **Regenerate Object Queries:** Regenerates Data Quality Function object queries when updates are made to the Functions Template. A background job performs the regeneration. This option is enabled only for objects of type Code. * **Remove Associated Objects:** Removes selected associated objects from the Data Quality Rule. Available only when the rule is in the Draft state. This option is disabled on the Service Requests tab. * **Delete Contacts:** Removes added contacts from the Data Quality Rule. Available only when the rule is in the Draft state. This option is disabled on the Service Requests tab. * **Delete Rule:** Deletes the Data Quality Rule. ## References The References tab displays all links or mentions made to the selected Data Quality Rule from other modules within OvalEdge, such as Data Catalog, Business Glossary, Projects, Data Stories, and Service Desk Tickets. References are created when users mention a Data Quality Rule using the “@” notation in various text fields across these modules. Mentions can be added from areas such as: * Business Description * Technical Description * Endorsements * Collaboration comments * Project Notes * Data Stories * Service Desk Notes This provides traceability and helps users see where the Data Quality Rule is referenced across the platform.
The References tab displays the following columns: * **Reference Category:** Indicates the type of object or document that contains the reference (e.g., Document, Code, Table, Table Column, File, etc). * **Reference From:** Shows the specific field where the mention was added (e.g., Business Description, Technical Description, Notes, Comments). * **Reference Object Type:** Indicates the type of object from which the reference originated (e.g., Table, Table Column, File, Business Glossary Term). * **Reference Object:** Displays the name of the object that contains the reference, presented as a hyperlink for direct navigation. ### **Nine Dots Options (References)** The Nine Dots menu provides several actions that users can perform within a Data Quality Rule. However, on the References tab, only a limited set of options is available. The following actions appear in the menu, but some are disabled based on the nature of the References tab. * **Change Rule Status:** Allows users to change the Data Quality Rule status between Active and Draft. * **Run Now:** Executes the Data Quality Rule. The rule must be in the Active state. * **Activate Objects:** Marks selected associated objects as Active so they are included in rule execution. This option is disabled on the References tab. * **Inactivate Objects:** Marks selected associated objects as Inactive, excluding them from rule execution. This option is disabled on the References tab. * **Update Steward:** Allows users to update the steward of the Data Quality Rule. Available only when the rule is in the Draft state. * **Regenerate Object Queries:** Regenerates Data Quality Function object queries when updates are made to the Functions Template. A background job performs the regeneration. This option is enabled only for objects of type Code. * **Remove Associated Objects:** Removes selected associated objects from the Data Quality Rule. Available only when the rule is in the Draft state. This option is disabled on the References tab. * **Delete Contacts:** Removes added contacts from the Data Quality Rule. Available only when the rule is in the Draft state. This option is disabled on the References tab. * **Delete Rule:** Deletes the Data Quality Rule. ## Contacts The Contacts tab stores the details of users who should receive email notifications related to the Data Quality Rule. It supports both OvalEdge users and external contacts, helping teams collaborate by keeping all relevant contact information in one centralized location. Email alerts are enabled when administrators configure SMTP settings in System Settings > Notifications.
The Contacts tab displays the following columns: * **Contact Name:** Displays the name of the contact added to receive email notifications for the Data Quality Rule. * **User Type:** Indicates whether the contact is an OvalEdge User, Existing External User, or New External User. * **First Name:** Displays the contact's first name used for notifications. * **Last Name:** Shows the last name of the contact added for notifications. * **Email ID:** Displays the email address where notifications related to the Data Quality Rule will be sent. * **Address:** Captures the address details of the external contact, if provided. * **Phone No:** Displays the contact's phone number and provides additional contact information. * **Notify on Edit:** Sends an email notification when the Data Quality Rule configuration is modified. * **Notify on Failure:** Sends an email notification when the rule execution fails. * **Notify on Pass:** Sends an email notification when the rule execution completes successfully. ### **Add Contacts** The Add Contacts option allows users to add email notification recipients for a Data Quality Rule. To add contacts: 1. Click the **Add Contacts** button. 2. The Add Contact for Email Notifications pop-up is displayed.
3. Select the required user type by choosing the appropriate radio button: 1. **OvalEdge User:** Select an existing OvalEdge user from the list to add them as a rule contact. 2. **Existing External User:** Choose an external user already configured in OvalEdge to add them as a contact. 3. **New External User:** Add a new external contact by entering their details so they receive email notifications for the rule. 4. Select the user from the dropdown list. 5. Select the Notification Types using the checkboxes. 1. **Notify on Edit:** Sends an email when the Data Quality Rule is modified. 2. **Notify on Failure:** Sends an email when the rule execution fails. 3. **Notify on Pass:** Sends an email when the rule execution completes successfully. Contacts added through this pop-up will receive email notifications based on the selected notification types, ensuring that the right stakeholders are informed about Data Quality Rule updates and outcomes. ### **Nine Dots Options (Contacts)** The Nine Dots menu provides several actions that users can perform within the Data Quality Rule. The available options include: * **Change Rule Status:** Allows users to update the status of the Data Quality Rule. The rule can be switched between Active and Draft. * **Run Now:** Executes the Data Quality Rule. The rule must be in the Active state to run. * **Activate Objects:** Marks selected associated objects as Active, allowing them to be included during rule execution. This option is disabled on the Contacts tab. * **Inactivate Objects:** Marks selected associated objects as Inactive, preventing them from being included in rule execution. This option is disabled on the Contacts tab. * **Update Steward:** Allows users to update the steward of the Data Quality Rule. This option is available only when the rule is in the Draft state. * **Regenerate Object Queries:** Regenerates Data Quality Function object queries when changes are made to the Functions Template. A background job updates all associated object queries. This option is enabled only for objects of type Code. * **Remove Associated Objects:** Removes selected objects from the Data Quality Rule. This option is available only when the rule is in the Draft state, and objects are selected from the Associated Objects tab. This option is disabled on the Contacts tab. * **Delete Contacts:** Removes added contacts from the Data Quality Rule. This option is available only when the rule is in the Draft state. * **Delete Rule:** Deletes the selected Data Quality Rule. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.ovaledge.com/release8.2/data-quality/data-quality-rules/rule-executions.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.