Other

I am running Bonita in docker containers and using Kubernetes. Using Kubernetes or not it not that relevant but if you are using docker, the following is probably interesting for you. I used to run the migrations manually (ie sopping my container, mounting a volume with the config and migration scripts, restarting the container, running the tool, restarting a new container on the new version). While that works... it is not the simplest...

Ironically, the documentation on the Official Docker hub page mentions some wget, unzip, etc... All kind of stuff no one really want to do :)

Editions: Teamwork, Efficiency, Performance and Enterprise

This project shows some examples on how to use event handlers.

An event handler is a java code that is executed when a certain event is listened.

We can consider to use it when sometimes we need to move from process to platform perspective.

We need to be careful in setting up these events because a wrong implementation can have a strong impact on the platform performance.

The following use cases are covered in the example (at the moment). Handlers that trigger when:

• Any new human task is activated

• Any task is assigned to a new user

• A human task is executed and the handler will get the value of a transient data variable

For sake of simplicity the handler will just log into the filesystem some information.

Bonita Purge tool has been integrated in Bonita and is now part of Bonita 2021.1 Enterprise Edition.

# BonitaCommandDeployment Library to deploy automatically a command, when needed, and organize the communication between the source and the command.

Maven:

org.bonitasoft.command
bonita-commanddeployment
2.1.0

# BonitaCommandDeployment

Library to deploy automaticaly a command, when needed, and organize the communication between the source and the command.

# Implement your command

A command must implement the method org.bonitasoft.engine.command.TenantCommand.TenantComand.execute().

This method has to concern:

Give a description to protect the serverAPI like the Tomcat Valve do.
By default, the servletAPI is open, and any host can connect to a BonitaServer, then use the BONITA JAVA API to do any operation.

This filter is able to protect the servletAPI, to describe which host can access the BONITA JAVA API

Principle
The filter verify that the RemoteAddr match the pattern. This is the same usage as the org.apache.catalina.valves.RequestFilterValve except that a filter can be setup for a specific URL, not all the tomcat

Jaas module to query the Bonita User Database, and return true if the login / password exist. This JAAS module is perfect if you want to use multiple JAAS module, and say "in Bonita OR in my LDAP"

in form V6, you have a "User Anonymous" function. You can setup a process with this properties, and then any person can create a case without a Bonita user/password.

You just need to give to the user an URL like:
http://localhost:8080/bonita/portal/resource/process/mySimpleProcess/1.0...

Actor filter to allow a task to a list of user candidates.
Useful to allow users belonging to a group to be task candidates when the group depends on the process instance.

Bonitasoft is a software to create a BPM application all-in-one, from back-end to front end, all in the same environment. We can drag tasks into diagrams or widgets into web-pages with beautiful rendering. We can add some code (groovy, javascript, css, html) to be closer to our needs.

What's about this specific code insides diagrams and web-pages ? How do I know the level of quality of this code ? How can I detect potential misconception, code smell or bug ?

This is what Bonita Extract Sources provide you : A way to analyse code hidden in diagrams or web-pages