Custom components

<< Click to Display Table of Contents >>

Navigation:  Application integration >

Custom components

Overview

Bizagi lets you include custom components through the Component Library.

Through the Component Library, you can extend the logic behind business rules in Bizagi, by including invoking methods in your components or bundled third-party APIs.

You can write you own code to directly integrate APIs, or especially to perform additional processing aimed at application integration in your business processes, as described at Application integration.

 

ComponentLibraryNET02_102

 

 

Before you continue

Additional integration approaches lets your processes easily use a generic SOAP Web services connector or use Bizagi Connectors, which enable you to invoke web services with no programming needed.

 

In scenarios where these features above are not optimal (e.g., to extend processing capabilities) or whenever the generic SOAP Web services connector is not compatible with a given web service of yours, the Component Library becomes an effective alternative.

 

About the Component Library

The Component Library lets you to develop or reuse APIs or your own class libraries, that you build using an IDE (like Visual Studio) in your laptop. The Component Library acts as a middleware repository of developed components.

Though it allows you to connect to web services, applications in general, legacy systems or databases, you can also extend the logic and processing capabilities of business rules by bundling libraries inside Bizagi (.DLL assemblies).

 

Once components are registered in the Component Library, you can directly invoke their public methods from the Processes’ business rules (from either synchronous or asynchronous tasks).

To view an example, refer to Component library example.

To view recommendations and considerations for its use, refer to Component library guidelines.