Bizagi allows you to include custom components into a feature referred to as Component Library.
Through the Component Library, you extend the logic behind business rules in Bizagi, by including invoking methods in your components or bundled third-party APIs.
That is, you may write you own code in order to directly integrate APIs, or especially to perform additional processing aimed at application integration in your business processes, as described at Application integration.
Before you continue
Recall that additional integration approaches allow you to have 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, then the Component Library becomes an effective alternative.
About the Component Library
The Component Library allows you to develop or reuse APIs or your own class libraries, so that you build them by using an IDE (Visual Studio) in your laptop (i.e, acting as a middleware repository of developed components).
Though it allows you to connect to web services, applications in general, legacy systems or databases, you may also extend the logic and processing capabilities of business rules by bundling such libraries inside Bizagi (.DLL assemblies).
Once registered in the Component Library, components’ public methods can be directly invoked 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.