When you have created a Dataset, you automatically get different instances of it in three default environments (development, testing and production), as described in Creating a dataset.
This section describes how to use and manage different Dataset environments.
Default and custom environments
Set up the data feed so that each Dataset environment is connected solely to the matching Bizagi process environment type.
For instance, have Bizagi processes in the Development environment send data to the Dataset Development environment. Similarly, Bizagi processes in the Testing environment should send data to the Dataset Testing environment.
The three default environments provided for a Dataset cannot be deleted.
If you want to use additional environments, or to experiment with them without mixing up different sets of data of different nature, you can create any number of custom Dataset environments.
To create a custom environment, click the three dots menu of a Dataset, then select New environment:
Once you give it a Name and meaningful Description, click Create Environment.
And that's it.
At this point, your new Dataset environment is available along with the default ones, and you can use it as you would the others and as described in the section below.
To delete a custom environment, click the Delete link next to the custom environment you want to deletes.
Click the link representing the environment you want to use for a given Dataset:
You get information about the environment in the upper part of the screen, and three tabs: General information, Explore Data and Security & Connectivity.
Refer to the information below about each tab.
Presents the columns composing the structure of the Dataset, along with the Data type of each column.
You cannot modify the definition.
To define a new structure, you need to create a new Dataset.
Lets you take a quick look at the data you have stored so far in that Dataset environment.
It also provides an option for you to do an initial data load (from a .csv file) if you will be using the Dataset to obtain reports on data you already have, or if you want to populate the Dataset and then continue to feed it from processes.
For an initial data load, click the Select a .csv button:
Upload a .csv file from its location:
When using collection columns, the main register needs to be repeated as many times as the number of items in the collection.
In the example above, the Dataset has a Numeric type column (CountryCode), a String type column (CountryName) and a Collection type column called City; in this collection column you have two columns (Code and Name). As mentioned before, the collection related to the record Colombia has five items, so this is why the record value 57, Colombia is repeated five times.
Once initial data is loaded, you can take a quick look at it. Use the paging control at the bottom of the display to browse the results across different pages.
•Security & Connectivity:
Provides your access keys and URL endpoints so you can feed this Dataset with data incoming from the execution of cases (per instance of business process) and consume the data stored in this Dataset in another application such as a reporting tool.
To learn more about these options refer to the links below.
oView how to configure your Bizagi processes to send data to the Dataset at Connecting Bizagi processes to feed the dataset.
oView how to consume the Dataset from other applications at Consuming the dataset from external applications.