Governed Data Quey (GDQ)

Stewards and data users need a method to govern the privacy compliance data. It adapts a standard method by using a Governed Data Query search result to search sensitive Customer data. ach data query is governed across a domain, and privacy terms are created for each domain (such as First Name, Last Name, Mobile Number, and Personal ID). The terms are then associated with the data objects before creating the data query.

Process Flow

Example: Assume that the IT team now wants to search customer data by entering the customer’s First name, Last name, Mobile number, and Personal ID.

Example: Name Smith, Last Name Dsouza, Mobile number 8433776941, Personal ID AZ80918

The IT team will go to the GDQ module and create a Governed Data Query. Then, they will add the privacy terms and configure the term search conditions. (Here, search the data with a combination of different privacy terms and values).

They will then add the configured search term values, execute the GDQ, and view the results to see all the associated data objects for the customer.

Governed Data Query Summary Page

The Governed Data Query (GDQ) summary page displays the predefined Data Query names created under each domain. It contains information such as GDQ name, Steward (approver who can approve the GDQ), Creation Date, and Created By.

Provides the following capabilities within the module:

• Create a new GDQ

• View the list of GDQs

• Configure each GDQ with combinations of privacy terms

• Update the GDQ configuration with more privacy terms

• Add entries based on the configured terms to search the customer information

• Edit the GDQ entries

• Run or execute all or specific GDQ search entries

• View associated data objects for the search result

• Delete a Governed Data Query

Create a Governed Data Query

To create a Governed data Query in the Governed Data Query summary page,

1. Navigate to Governance Catalog > Governed Data Query. Click the plus (+) icon.

   
2. An Add Governed Data Query pop-up window is displayed. Fill in all the required details, such as the Governed Data Query Name (A unique name for the Governed Data Query), Domain (Select the Domain name from the list with the privacy terms), and Governance Roles (Steward, Custodian, Owner, Governance Role 4, Governance Role 5, and Governance Role 6).

3. (Approver for the Governed Data Query).

   

Enter # in the Governance Role dropdown to display and select available teams. Select users or teams as needed for role assignment.

1. This action creates a Governed Data Query.

   

Configure Privacy Terms to Perform a Search

Once the Data Query is created, the privacy terms must be configured. To add the privacy terms and set the term conditions.

1. Go to Governance Catalog > Governed Data Query.

2. Choose and select a Data Query by clicking the radio button of the corresponding query.

3. Select 9 Dots > Configure Terms to add the privacy terms with search conditions to build the Data Query. This provides an option to configure various privacy terms and set multiple search conditions.

4. Add the privacy terms and click Save Terms to store the search criteria for the GDQ.

Multiple AND / OR conditions can be added as needed, based on the use case.

Search Criteria for Privacy Terms

Complex queries can be built using a combination of privacy terms and operators that can later be set to required values. This page provides information about the operators available for building these queries and specific conditions for searching terms.

AND operator: When you enter terms separated by the word "AND," a record will only be found if all the terms you specified are contained somewhere in the associated data objects. For example, if you enter “Gabriel” as your search entry for the term “First name” and “Dizzosa” as your search entry for the term “Last name,” the result will only display if a record matches both of the search conditions.

OR operator: When you enter terms separated by the word "OR," a record will be found if any of the terms you specified is contained somewhere in the associated data objects. For example, if you enter “Gabriel” as your search entry for the term “First name” and “Dizzosa” as your search entry for the term “Last name,” the result will display records that match either the first name or the last name or both the entries.

Configured terms with “AND” conditions execute on all the associated data objects separately, just as configured terms with “OR” conditions execute on all the associated data objects separately.

Match type can be selected as EQUAL for exact matches or LIKE for partial or full matches, based on requirement.

Edit the Terms

Once you configure the Privacy terms and the search conditions, add more privacy terms by editing.

To edit and add more terms to a Governed Data Query:

1. Go to Governance Catalog > Governed Data Query.

2. Select a Governed Data Query by clicking the checkbox for the corresponding query.

3. Select Configure Terms to edit the privacy terms and search conditions of the data Query.

   
4. Add new terms and conditions or edit existing terms and conditions.

5. Click Update Terms to update and save the changes.

   

Delete the Governed Data Query

To delete a GDQ:

1. Go to Governance Catalog > Governed Data Query.

2. Select the Data Query that needs to be deleted by clicking the checkbox for the corresponding query.

3. Click on Delete GDQ to delete the GDQ.

   
4. This action displays a Delete Governed Data Query pop-up window. Click Yes to Delete the GDQ.

   

Search Entries

Once the Privacy terms and conditions are configured, add/edit/delete the entries to search for customer information.

Add New Entries

1. Go to Governance Catalog > Governed Data Query.

2. Click on the GDQ name and click the plus (+) icon.

3. A pop-up window to add new entries is displayed. Add the entries and click Save Entries to save. Note: Custom-defined conditions when adding new entries before running a governed data query, including options such as Custom Value, Is Empty, Is Not Empty, Is Null, or Is Not Null.

4. By default, no term is selected. To add an entry input for a term, select the checkbox and choose the appropriate condition.

   

Conditions

Condition	Definition
Custom Value for Like & Equals	EQUAL: The EQUAL operator is used for exact matching. It checks if a column's value is exactly equal to a specified value. Use Case: You want to find an employee whose name is exactly "John Doe". ✔ You are looking for a specific person in your HR system. ✔ You need an exact match, not similar names. ❌ This won't work for similar names like "John D." or "Johnathon Doe." LIKE: The LIKE operator is used for pattern matching. It is useful when you want to find values that match a certain pattern. Use Case: You want to find all employees whose names start with "John" (e.g., John Doe, Johnny Smith, Johnathan Carter). ✔ You are searching for all employees named "John", but you don’t know their full names. ✔ This is useful when handling customer inquiries where partial information is available. Used to filter data based on a specific, dynamically supplied value.
Is Empty	The 'Is Empty' condition filters records where a specific field has no values. ✔ Applicable to: Fields where empty values are stored explicitly Use Case: The customer database has a column for "Secondary Email", but some customers have left it empty instead of setting it to NULL. You need to find all customers who have an empty email field but not a NULL value. ✔ Finds all customers whose secondary_email field is empty (''). ❌ Does NOT retrieve records where secondary_email is NULL.
Is Not Empty	The 'Is Not Empty' condition filters records where a specific field has values. ✔ Applicable to: Fields that should contain data Use Case: A company wants to find all employees who have provided a secondary email in their HR system. ✔ Finds all customers whose secondary_email field is NOT empty (''). ❌ Does NOT check for NULL values.
Is Null	The 'Is Null' condition filters records where a specific field has null values. ✔ Applicable to: Any field that stores NULL values. Use Case: A financial institution needs to find customers who haven't provided a Tax ID. ✔ Finds all customers whose tax_id is NULL (not recorded in the database).
Is Not Null	The 'Is Not Null' condition filters records where a specific field has no null values. ✔ Applicable to: Any field that should not be left blank for compliance, billing, or operational reasons. Use Case: A hospital needs to retrieve all patient records that contain a recorded phone number (for emergency contact). ✔ Find all patients who have a phone number recorded.

Edit Entries

1. Go to Governance Catalog > Governed Data Query.

2. Select and click a GDQ name.

3. Select the checkbox near the entry to make the changes.

4. Click on 9 Dots > Edit Entry to change the entries for the configured terms.

   
5. A pop-up window to Edit entries is displayed. Make the changes and click Update Entries to save.

   

Delete Entries

1. Go to Governance Catalog > Governed Data Query.

2. Select and click a GDQ name.

3. Navigate to 9 Dots > Delete Entry.

   
4. This action displays the Delete GDQ pop-up window. Click Ok to delete the GDQ.

   

Execute the Governed Data Query

Multiple search entries can be made for a single search criterion. Entries in a single GDQ can be executed in bulk or individually.

Execute each Entry

1. Go to Governance Catalog > Governed Data Query.

2. Click a GDQ name.

3. Navigate to 9 Dots > Run Governed Data Query.

   
4. This action submits a Job as shown below.

   

Execute all the Entries at once

1. Go to Governance Catalog > Governed Data Query.

2. Click the GDQ name. From the 9 Dots, select Run GDQ All.

   
3. This action submits a Job that helps to execute the entry search in the data objects mapped under that domain.

   

View results of the Governed Data Query

Once the entries are executed, the matched results can be viewed using the View Results tab.

To view the results of an entry:

1. Go to Governance Catalog > Governed Data Query.

2. Click the GDQ name.

3. Select an entry and click View Results to see the data objects as a result of the search.

   
4. A new page opens, displaying the list of all the associated data objects with the information entered in the GDQ.

Unmasked data is displayed as is. Masked data shows only the masked version. If data access is not granted, the data is not displayed.

Each search Entry should be selected individually to view results. Each time the GDQ search entry is executed, a data point is created and represented in the line as above. Click on the data point to see the earlier results.

Entries Found

Click the Entries Found search option, then select the six-dot icon to open the advanced search. Use conditions like Equals, Does Not Equal, Contains, Does Not Contain, Starts With, Ends With, Is Empty, and Is Not Empty to refine the search.

The entries found page highlights matching columns and their values in the GDQ results page after execution. This enables quick navigation to relevant data points, enhancing visibility and efficiency when reviewing large datasets.

Create Service Desk Tickets from GDQ Results

Generate service desk tickets in bulk directly from Governed Data Query (GDQ) results to streamline data issue resolution.

In the View Results tab, select one or more entries, click on the nine dots menu and select the option:

• Create one ticket per table.

• Create one ticket per table columns.

The system automatically selects the appropriate template based on the available configuration (Table or Table Column).

---

Copyright © 2025, OvalEdge LLC, Peachtree Corners, GA USA