Platform extensibility

Bonita comes with more than 80 standard connectors to the major information system components: major databases (Oracle, Microsoft, Postgres, etc.), SOAP Webservice, Salesforce, Email, etc.

However, you create your own connectors to have new connectivity capabilities for processes.

Connectors are developed outside the Studio with a dedicated Maven archetype. Consult this page for more information: Create a connector.

Custom connectors are added to a Bonita project from the extension view.

Bonita comes with a set of standard actor filters that can be used to reduce the list of candidates for process tasks.

Actor filters are developed outside the Studio with a dedicated Maven archetype. Consult this page for more information: Create an actor filter.

Custom actor filters are added to a Bonita project from the extension view.

The Bonita Engine APIs enable you to:

ProcessBuilder and Business Objects DAO are examples of APIs that can be leveraged in your development. They will remain stable in time.

The REST APIs enable you to integrate your Bonita processes into your application and execute operations on Bonita objects including business objects. Pages and forms created with the UI designer rely on the REST APIs to manage data.

In addition to the standard APIs and resources, you can define REST API extensions.

REST API Extension can either be created in the Studio or with the dedicated Maven archetype.

Custom REST API extensions developed with the Maven archetype are added to a Bonita project from the extension view.

A custom page is a page that you can add into Bonita Administrator Application to form part of an application or to customize information provided in default Application pages. To implement a page, you need to provide HTML, CSS and Javascript resources respecting some packaging constraints. You can create a page using the UI designer, which automatically creates a well-formed page. Note that although the page framework provided in the product is stable, we cannot guarantee that all custom pages will work with future versions, because this depends on how the page was implemented.

If the standard UI Designer widgets do not meet your needs, you can create a custom widget. You can then use your custom widget in pages, forms, and fragments.

For Subscription editions only

Custom themes are developed outside the Studio with a dedicated Maven archetype. Consult this page for more information: Create an theme.

For Subscription editions only

Included in the Engine APIs are methods to import and export various items. These methods manipulate files with formats that are versioned. Newer versions of the file format are designed to be backward compatible with earlier versions. The following items have import and export API methods:

For Subscription editions only

From Bonita 6.3, the Engine authentication service is considered to be an official extension point of the solution. It is now safe to provide your own implementation of this service to better fit the needs of your projects. Default authentication implementations are provided allow to check user credentials from the Bonita database, LDAP or other using JAAS. To implement an Authentication Service, provide a Java class respecting the Authentication Service interface.

For Subscription editions only

An event handler is an extension to the engine that is configured to run when a specified event occurs. An event is a change to any object in the database. To implement an event handler, you need to provide a Java class respecting the Handler interface.

Bonita Runtime comes with a number of language packs by default. You can also add languages. It is also possible to use this same mechanism to customize the Application terminology to suit your business environment. For example, an e-commerce business could change Cases to Orders.