<< Click to Display Table of Contents >> Data Virtualization |
Overview
Data Virtualization in Bizagi is a data-level integration mechanism that allows the Process data model to connect to external data sources.
With Data Virtualization, Processes in Bizagi can access information stored across multiple data sources (RDBMS, XMLs etc.), and present it as part of the business information.
Integration is done for end users in execution time (information is synchronized in run-time), and the information of a virtual entity is viewed and updated throughout the course of Activities in Processes.
Examples of information handled through Data Virtualization are: customers or vendor details, invoices, purchase orders, amongst others (records from tables which are seen as transactional).
For table data integration where updated information is stored as a predefined set of values (Parameter entities), refer to Data Replication.
How does it work?
To use Data Virtualization in Bizagi, you need to first make sure that your external data source adheres to best practices and requirement guidelines, such as having read and write access permission (a login with granted privileges).
Configuring the Data Virtualization is done by defining the external system and its data provider (connection to the external data source).
Bizagi offers an assisted graphical wizard so that minimum configuration is required.
Once the synchronization occurs, the information will be presented to end users to manage it as part of a business process in Bizagi.
Prerequisites
This mechanism is applicable for customers who have moved from On-premises and whose business case has been reviewed and approved by Bizagi.
In order to use Data Virtualization, the external data source must meet the following conditions:
1. Access to the external information system must be available in real time (for online synchronization); if this is not the case, data Replication in batch mode should be implemented.
Such access involves granting both read and write rights to that data source.
2. When accessing a database, it is recommended that this database has normalization in its design. It is required to clearly identify the keys in each entity (Bizagi supports compound key configuration), so that Bizagi can uniquely identify one instance.
Additionally, the relationships between Bizagi's entities (to virtualize), must exist between the corresponding ones as well in the external source.
Important Characteristics
•Data Virtualization only applies to tables in external data sources which are regarded in Bizagi as Master Entities (those entities which are transactional; and where new rows are created in a new process instance).
To view more information about Master Entities, refer to Entity Types in Bizagi.
If you wish to use this integration feature for tables containing lists of values; that is, Parameter Entities which have records that are not deleted, refer to Data Replication.
The name of entities in Bizagi CANNOT be longer than 22 characters. |
•Configuring Data Virtualization in Bizagi is easily done through a graphical wizard.
The Data Virtualization Wizard assists the definition for the data provider's connection to SQL Server databases (done in few steps and without the need of programming).
Supported database versions by the Data Virtualization Wizard (for native SQL Server connection) are:
Database Engine |
Version |
---|---|
Microsoft SQL Server |
2019 |
2017 |
|
2016 |
|
2014 |
|
2012 |
Supported version by the Virtualization Wizard (native connection).
•For our Automation Service offer, Data Virtualization is supported using SQL Server and SQL Azure databases. •When using data replication or data virtualization against an unicode database, make sure that your Bizagi database supports unicode characters as well. |
•Bizagi supports a comprehensive set of source data types out-of-the-box (SQL Server data source).
To view more information about the supported data types by default, refer to Data type support.
•Deleted values at the source are never deleted in Bizagi.
When synchronizing values for virtual Entities, Bizagi will disable those records which are deleted at the source (will be flagged, using a database logical delete instead of a physical delete).
This is done in order to preserve data integrity for existing cases in Bizagi.
To view more information about guidelines and advanced subjects related to Bizagi Data Virtualization feature and options, refer to Guidelines for Virtualization best practices.
Configuring Virtualization
As mentioned above, configuring Virtualization can be done in two ways.
In most scenarios the assisted graphical wizard will cover all your needs.
To view information about this first method, refer to Using the Virtualization Wizard.
However, for more complex scenarios you may want to use the Advanced Configuration options.
Such scenarios mainly involve the need to manually adjust the configuration. This may happen in sophisticated scenarios where you have a whole set of tables which are related to each other. This may involve relationships with replicated entities, and therefore this configuration requires that all of these tables are replicated and virtualized with some considerations.
To view information about this second method, refer to Using advanced Virtualization configuration.
Last Updated 1/24/2025 4:36:00 PM