Skip to main content

Key Concepts

Organization​

An Organization represents the legal entity that holds a valid iceDQ license. It is the topmost structure in the iceDQ platform's hierarchy. It provides centralized governance over all data testing operations. It allows creation and management of multiple Accounts and manages users, groups, and access control across the entire organization.

Account​

An Account is a logical subdivision within an Organization, used to define permission boundaries, isolate projects, and manage specific operational scopes. This is especially useful in large or multi-departmental setups.

Workspace​

A Workspace is a logical container within an Account in iceDQ, used to organize all the components necessary for data testing and validation activities. It serves as the primary working environment for users to build and manage their projects.

Each Workspace groups together related configurations and artifacts such as:

  • Connections
  • Folders
  • Rules
  • Checks
  • Workflows
  • Parameters
  • Schedules
  • Instances

Connection​

Connection is how iceDQ accesses data from external sources. The external sources includes databases, files, APIs, applications like Salesforce. User defines connection settings and test connectivity through the UI.

Folder​

Folder is a physical grouping mechanism used to organize related components such as rules, parameters, workflows, schedules. Folders help maintain structure and clarity, especially in large projects with numerous rules and configurations.

Rule​

Rule is the smallest executable unit of work in iceDQ. Rule define the logic for validating a single dataset or compare any two datasets. The most common rule templates supported by iceDQ: Checksum (compare 2 numbers), validation (check validity and format of the data) and reconciliation between 2 data sets.

Check​

Check is a test condition that evaluates the quality or validity of data within a dataset. It is applied to specific attributes (columns) and used to ensure that the data meets defined expectations or business rules. iceDQ offers a wide range of predefined (out-of-the-box) checks, along with the flexibility to define custom checks using scripting languages like Groovy.

Parameter​

Parameter is a placeholder for a value that can be used within Rules or Checks to make them dynamic, reusable, and configurable. Parameters allow the same rule logic to be applied across multiple datasets or scenarios by simply passing in different values.

Exception Report​

Exception Report captures and displays all data issues identified during the execution of Rules and Checks. It serves as a centralized, detailed view of data failures, making it easy for users to investigate and resolve issues across multiple records and columns.

Workflow​

Workflow is used to orchestrate and automate the execution of a series of data testing rules, processes, or validation steps in a defined sequence. It enables users to model complex logic, handle conditional execution, and produce a final outcome such as Success, Failure, or Error, based on rule outcomes.

Schedule​

Schedule defines when and how often one or more Workflows should be executed. It allows users to automate data testing operations by triggering workflows at specific times or intervals without manual intervention.

Instance​

Instance represents a single execution record of the executable entities: Rules and Workflows. Everytime these components are executed iceDQ generates an instance to log the execution details, track results, and enable auditing and troubleshooting.

Last updated on