Key Concepts
This article provides a brief overview of the different concepts and entities available in iceDQ.
Organization
An Organization is the legal entity which has acquired a license of iceDQ. It lets you create multiple accounts and manage users, groups and their access.
Account
An Account enables an organization to set boundaries for permissions, projects and other entities. An enterprise can use multi-account environment on a large cluster deployment.
Workspace
A Workspace is a collection of Folders, Connections, Rules, Functions, Workflows and various other entities available in iceDQ.
Connection
A Connection (JDBC) provides the ability to read data from any data source, including databases, files, APIs, and applications like Salesforce.
Folder
A Folder is a physical grouping of Rules, Parameters and Schedules.
Rule
A Rule is the smallest executable unit of work in iceDQ. It can be used to validate a dataset or compare two datasets. iceDQ supports four types of rules: checksum, validation, pushdown, and recon.
Check
A Check is a test condition that can be applied to any attribute in a dataset. iceDQ supports a variety of out-of-the-box checks, such as completeness, range, pattern, and contains. Users can also write custom checks using Groovy or Java.
Parameter
A Parameter is a placeholder for a value that can be used to customize a Rule or Check. Parameters can be used to provide different data values, test different scenarios, or to make Rules more reusable.
Exception Report
An exception report captures all the data issues identified by the engine based on the Rule and Checks. It helps users quickly view and filter the data failures for multiple records and columns in a single report.
Workflow
Workflows can orchestrate the execution of a series of rules and generate a final outcome of success, failure, or error based on the results. Regression testing is one example of how workflows can be used.
Schedule
A Schedule is a plan for when to run one or multiple Workflows. It ensures that Workflows are triggered on time.
Instance
An instance is an execution record of a Rule, Workflow, Schedule or any other executable entity supported by iceDQ.
Engine
An engine is a service in iceDQ which reads data, identifies and captures issues based on the defined rules. There are currently two types of engines available: Standard and High Throughput.