Bizagi provides a powerful integration layer that supports the different integration possibilities involved in a complete digital platform solution.
In such enterprise projects, where there is the need to integrate existing services and applications, Bizagi's Integration layer presents diverse options which you may approach as data-level integration or as process-level (services integration).
When the length of string-type attributes returned by a service exceeds the size of the Bizagi attribute where the data is to be stored, Bizagi will truncate the result in order to fit the length.
1. Application integration features
The following sections describe the approach offered by each of these features.
Invoking external services from Bizagi
For modern and service oriented applications, Bizagi features a Web service connector which is easily configured to consume SOAP Web services or REST services (i.e, WCF services, RESTful APIs, any SOAP service available through the ESB, on-premise, or available at the cloud), in an asynchronous or synchronous fashion.
This is all done through assisted steps, by means of graphical mapping and configuration (without the need of programming).
Within Bizagi connector's approach, you may rely on the built-in SAP connector to easily integrate your corporate SAP systems into the solution.
This connector is officially certified by SAP.
Similarly to how it is done with the above Web service connector, invoke SAP BAPI wrappers through assisted steps, by means of graphical mapping and configuration (without the need of programming).
For more information about this option, refer to SAP connector.
Additionally, you may use other connectors so that these rely on Bizagi graphical input/output mapping features.
Bizagi connectors allow you for powerful extensibility options regarding integration with other systems and applications, especially those using modern architectures (cloud-based, RESTful).
You may install ready-to-use connectors from Bizagi Connectors Xchange, or choose to create your own connectors.
For more information about this option, refer to Connectors.
Integrating APIs or custom code in Bizagi
You may also extend the logic behind business rules in Bizagi, by including your own components or bundling third-party APIs.
You may write you own code to directly integrate APIs, or to customize how you
By means of your own code, you may reuse libraries (EJB Classes, JMS, etc) to namely connect to legacy databases/systems where there is no service-oriented architecture, or to carry out additional specialized processing.
The concept behind this feature, is to be able to rely on proprietary components in .NET or Java technologies, as class libraries (.dll assemblies or .jar files).
For more information about this feature called Component library, refer to Integrating APIs or custom code in Bizagi.
2. Connecting external data sources (data-level integration)
Bizagi presents a powerful technology for a data-level integration approach.
Through this approach, existing data structures (tables) from an external data source can be seamlessly synchronized with the data model in Bizagi.
This powerful technology is called in Bizagi Data Replication and Virtualization, and strongly promotes reusability (e.g reusing data structures and information in legacy systems), so that you avoid having islands of information or the administration overhead implied when keeping information updated, while having Bizagi manage transactions automatically (e.g rollbacks when necessary).
Data Replication is aimed for read-only purposes, where you need to import and keep synchronized in Bizagi, the information stored in the external source periodically through a scheduled job.
Data Virtualization on the other side, is meant to synchronize in both ways, so that you can also update in the external source what you input in Bizagi on real-time.
For more information about integration with external data sources through Data Replication and Virtualization, refer to Integrating data.
3. Additional integration of services and systems
Bizagi offers other integration features for the corporate Bizagi Solution. These features involve options such as the possibility to store documents in an ECM repository, and LDAP integration, amongst others.
Using an ECM as the documents repository
Bizagi supports integration with Enterprise Content Management systems that complies with the CMIS standard, such as SharePoint, Alfresco and Documentum, amongst others. Documents uploaded in Bizagi Processes can be configured to be stored in a central repository.
For further information about ECM integration, refer to ECM Integration.
Bizagi Processes can send automatic e-mail notifications by using an email server which is SMTP compliant, such as Lotus Notes and Exchange, amongst others.
For further information about e-mail server configuration, refer to Defining notifications.
Once a connection to your corporate e-mail notifications is setup, you may also use an additional feature which allows your end users to complete their tasks via e-mail.
For more information about this option, refer to E-mail integration.
Using SSO and integrated authentication
For authentication in Bizagi's Work Portal, a project may use any of the various advanced options: Windows, Custom, Federated services, LDAP, or Mixed authentications.
When using Windows authentication, it is possible to hide the Bizagi's login page and instead use an integrated sign-on mechanism, allowing Bizagi to automatically validate the Windows session credentials.
Custom authentication allows authenticating against any other data source not covered by the common methods (a file, a specific database, or any custom development).
For LDAP integration, end users authenticate against an LDAP server. Importing (periodically synchronizing) users from an LDAP server is also supported.
Similarly and with Federated authentication, you may achieve a full Single Sign-On experience by delegating authentication to your corporate Identity provider system (compliant to renown standards such as SAML).
For more information about the features and options, refer to Login into the Work Portal.
Triggering of Business Events by Bizagi
Bizagi supports the different possibilities for BPMN Collaboration BPMN Collaboration (choreography) in its Processes.
This refers to the possibility to react to business Events which are triggered by another Process in Bizagi, or to react to asynchronous-type Events, such as Timer Events.
This feature allows the modeling of Processes which are started or flagged by messages, signals, timers, or any other asynchronous triggers.
Although this is a concept involving collaboration between Processes, business Events are also supported through custom jobs.
You may rely on custom jobs to specify certain scheduled tasks that are triggered as an agent, separate from Bizagi processes.
You may accomplish batch processing or other specific tasks, which are executed through Bizagi rules or components (programming may be required).
Custom jobs are useful for example, when searching in a physical path for new files and creating any number of cases in Bizagi with these files as uploads.
View more information about Custom jobs in Bizagi
4. Extending functionality from the user interfaces
Bizagi offers a comprehensive set of controls to add onto Activities forms (user interfaces).
These set of controls are available out-of-the-box in the Controls tab of the Forms Designer and these are the most commonly required in any form, such as an file upload inputs for attachments, drop-down lists, and radio buttons amongst others.
For more sophisticated scenarios in which you require to customize the user interfaces and use extended functionality (i.e., display a statistics chart, use a Google map, integrate webcams, scanners or other peripheral devices, or connect to a storage/documents repository), you have the possibility to include Widgets in your Bizagi Forms.
For more information about this possibility, refer to Bizagi Widgets.
5. Invoking Bizagi from external applications
It is also possible for external applications to easily integrate Bizagi processes by means of Bizagi API.
Bizagi API follows a service oriented architecture (for best practices towards integration capabilities and design), and it is made available through Bizagi SOA layer as built-in SOAP Web services.
Every project in Bizagi has such Web services already available and published, to provide the Workflows' functionality and further possibilities to query or update information in the data model.
This means that you can easily raise a business event in Bizagi that is controlled by another system, and you may start new processes, perform an activity, update or get updated information of processes, or abort Process instances, amongst others.
For more information, refer to Bizagi API for external applications.
If you wish to embed Bizagi with user interfaces, within your corporate portal, you may rely on Bizagi Web parts for SharePoint or other type of portals.
For more information about Web parts, refer to Portal integration in Bizagi.