Overview

Nected DataSet helps to unify data across the database, via database query, to attach directly as input to the rule. Using Dataset, you won't have to pass any data to rules, which are already present in your data sources but can be automatically fetched from data source while executing the rule.

You should integrate your database connector before creating the Dataset.

Note: A dataset does not update any table in the database. It just retrieves the data from the database. Only SELECT statement is allowed in the DataSet.

Query in the dataset executes only when the rule (to which the dataset is connected) is triggered and the query retrieves only the data that is required for the rule.

Nected Dataset supports multiple development environments including staging & production:

• Staging – This dataset can retrieve data only from a staging database connector but does not modify the database.

• Production – This dataset can retrieve data only from a production database connector but does not modify the database.

Note: The query is shared across staging and production environments, however, Dataset settings are different for both staging and production environments.

Setting up New DataSet:

When you create a dataset:

• You select a published database connector to establish a connection to the database.

• You provide a name for the dataset and add a database query to retrieve data from the database.

• You execute the query and verify the results. This would mark Dataset as Tested.

• Once you have used it in Rule and Tested Rule, you need to publish the dataset before publishing the Rule

Note: You can't publish / re-publish the Rule until you have published the latest Dataset Version.

DataSet Settings

Dataset settings can help you control query performance as well as amount of data to be fetched. Using Settings, you can configure:

• Row limit – Number of data rows to be fetched to execute the Rule

• Cache – Enable or disable the cache for the dataset results. Cached results provide faster query processing.

• Time to expire – Cache expiration time, after which Nected will execute database query again.

Note: All settings like row limit, cache, and time to expire are applicable in terms of data retrieved for that respective rule on which this dataset is attached.

Demo DataSet

Nected provides a pre-configured read-only dataset, named Demo-Product-DataSet, connected to Demo-Mysql-Connector.

The following figure shows the Datasets page of the Nected platform:

DataSet States

A dataset has the following three states:

States	Desc	Allowed in
Draft	The dataset is created and saved, but it is not yet tested.	Not usable anywhere. Also if this dataset is attached in Rules, those Rules will not work in staging mode until you test the dataset again.
Tested	The dataset is tested, but it is not yet published.	Draft, Tested Rules
Published	The dataset is published, and you can use it to query the in both staging & production env	Draft, Tested, Published Rules

Refer to State Combinations to know more about possible combinations of connectors, datasets, and rules.

Versioning

Every time you edit a published dataset, its version is automatically incremented by .10. For example, if the current version is .30, then after you modify the dataset, its version will be .40.

To check the current version or if you want to revert into any of the previous version here is how you can do that:

1. Click on a data source to open its configuration panel.

2. Click on the 'timer' like button from the right-hand side panel, and it will open the "Version Control" tab where you can check and manage your versions.

Dependency Mapping

Dependency Mapping, also known as Entity Mapping, is a powerful feature in Nected that allows users to visualize, track, and manage the relationships and dependencies between various entities within the platform. These entities include Integrations, Data Sources, Rules, and Workflows. Entity Mapping provides a comprehensive view of how different components interact, ensuring efficient data flow management and system integrity.

To access Dependency Mapping inside Data source, follow these steps:

1. Choose a Data Source: Click on a data source to open its configuration panel.

2. Within the data source settings, find and click the ‘Dependency Map’ tab by clicking the button just below of the button for "Version Control" which will show how this particular data source is utilized across rules and workflows.