This documentation (Bonita Open Solution V5) is an archive. Please click here for current documentation.
Advanced search


Open Source


Abstract task
A placeholder task with no specific type defined. It is useful for defining a process at an abstract level (that is, not configured as executable), as an abstract task can be changed to any other task type and then configured for process execution
(See Abstract task)

Pop-up message in Bonita Studio > Menu bar, and Bonita User Experience, that shows the current Bonita Studio and Subscription Pack version.
(See Menu bar)

General term in BPMN 2.0 meaning an activity that is represented with a rounded-corner rectangle and describes the type of work to be done in the process.
It can be any task (user, manual, automatic). It is a component of a process or the smallest unit illustrated on a process diagram.
(See Call activity or Tasks)

Used in Bonita Studio process design to refer to the person who performs a task.
An Actor in Bonita Studio becomes a User in Bonita User Experience.
(See Actors)

Actor selectors
Use actor selectors in BOS to assign one or more actors / end users to perform steps in a process.
(See Actor selectors)


Administration View
In Bonita User Experience, 2 interfaces are possible, either the Administration view where the assigned "admin" who has the right to modify, or a simple User View whose users has rights are attributed by the administrator.
(See Bonita User Experience)

Advanced export
Advanced Export offers additional options to the basic export function, for exporting both *.bar files and web applications generated in process design (*.war files).
These extra files will be needed to deploy processes.
(See Advanced export)

And gateway
All inputs must arrive at the gateway before process can continue. If there are multiple outputs, all will fire simultaneously.
(See And gateway)

Annotated text
Text added to a process to provide extra information. It is not executable and adds no functionality to the process.
(See Text Annotation)

You can modify the way elements appear in the Bonita Studio interface by changing color, font, font size, etc.
and in Bonita User Experience.
(See Set Field appearance)


(See Web Applications)

Application developer
The person who develops the user interface in the User Experience.
(See Application developer guide)

A file format that can be imported into Bonita Open Source.
(See Import a diagram)
(See this Aris external source)

Extra information in a process which does not affect the process execution, e.g. text annotation (BPMN)
Methods or processes used by Bonita Open Solution for process modeling and execution that are not part of Bonita Open Solution. These artifacts do affect process execution.
(See Simulation artifacts)

(See Export a repository)

Asynchronous process
A synchronous sequence is a group of activities that must all complete successfully before the process can continue, but that can be completed in parallel to other activities in the process.
(See Define an asynchronous sequence)

Attachments can be uploaded as part of the process design as data. This can be done at the process level only, ie, at the pool or lane level, or with Document Management in Bonita User Experience. It will then be attached to the process during its execution.
(See Define an attachment as a variable)
(see Upload a document with User Forms)

Atributes define additional information about an element.
(See Design a report template)
(See Diagram)
(See Redirect a form page)


Bonita ARchive Package containing all processes in the diagram and all their dependencies. A process is saved in the .bar format as a compressed file. It can be imported into or exported from Bonita Studio.
(See Export process for Installation/Deployment)
(See Add dependencies to a process)

Bonita Studio
The component of Bonita Open Solution where processes are designed, used for modeling, connecting to external systems, designing forms to be deployed in web applications, and more.
(See BOS)

Bonita Execution Engine
Component of Bonita Open Solution that executes processes (runtime); can be integrated into other applications.
(See Bonita Execution Engine)

Bonita User Experience
Sometimes abbreviated as Bonita User XP. Provides a user and administration portal designed for managing and deploying running processes, cases and reports.
(See Bonita User Experience)


Boolean variables in Bonita Open Solution are equal to Java.lang.Boolean and can have a value of "true" or "false."
(See Define a boolean variable)

Business Activity Monitoring (BAM)
Business Activity Monitoring is a means of measuring and/or reporting defined Key Performance Indicators.
(See Configure KPI/BAM)

Business Process Management Notation; standardized graphical representation for specifying and designing business processes based on flowchart modeling techniques.
(See BPMN)

Business Analyst
A profile used in Bonita open Solution.
(See Business Analysts)



Call activity

An element that represents a sub-process in process design.
(See Call activity)

A single instance of a process in Bonita User Experience.
(See Start a new case)



The receiving end of a throw-catch or send-receive set of events, eg a link,a message, an error, etc.
(See Catch link)
(See Catch an error)

Categories are labels that can be applied by the process designer to individual processes. It is applied to a pool, and will be displayed on the tasks (steps) in that process in the User Experience when it is executed.
(See Add a category label)

Collaboration and collaborative modelling
A way of sharing process and other files on a shared repository.
(See Design Collaboration)

Complex data types
Java classes with attributes, as a JAR (Java Archive) or XSD package.

(See Complex data types)
(SeeComplex data)

Cool bar
The Cool bar contains icons representing shortcuts to features and functions available for process design and configuration.
(See Cool bar)

An expression (generally in Groovy script) to define the behavior of a transition at a Gateway.
Transitions can be configured using conditions to determine which path the flow should take.
When a transition has been configured with a condition, the condition can be shown as a label on the whiteboard.
(See Define conditions)

A message displayed on a form when the submit button is clicked. It can be configured.
(See Confirmation message)

Links a process to external applications, such as email functions, databases, etc. Connectors in Bonita Open Solution require inputs from a process and return outputs to a process.
(See Connectors)

Connector repository
When you add or create new connectors or connector configurations in Bonita Studio, you may need to refresh the connector repository to see them.
(See Connector repository)

Connector wizard
An interface containing a step-by-step process to define inputs required to create connections a process and external applications; and to define what to do with the outputs returned
(See Connector output)


Contexts are associated with different environments of a process; for example, to try a Process in a test environment with test data
(such as test email accounts, test databases, etc) before deploying it.
A Context contains a set of key-value pairings. Context keys (which will be replaced by a predefined value) can be used as input in most text variables.
Before deploying or exporting a Process, select which predefined Context to use.
When the Process is Run, the keys are replaced by the appropriate values.
(See Contexts)

Context palette
Whenever you click on an element on the whiteboard, a context palette will appear. Different options will be displayed around the element.
The context palette will be slightly different for each elemnt selected.
(SeeContext palette)

If a task must be done all in one go during its execution - if the step itself must be performed with no interruption for the whole of its duration,
it can be marked ascontiguous.
(See Contiguous tasks)

Contingent field
In Forms, some aspects of a data field can be dependent on another field. The first field is said to be contingent on the second.
For example, whether a field appears in a form or not can be contingent; the information presented in a list of options can be contingent;
when a field refreshes can be contingent, etc.
(See Contingent fields)

Making one element dependant on another element
(See Contingency)

Contributions are uploads to the community websitewhich could be examples of process (.bar files), pdfs etc.
This openexchange of knowledge is designed to make the most out of Bonita Open Solution.
(See Contributions)


Contains graphs, charts, and tables that show data on selected information for a process (ie for Key Performance Indicators, for Process monitoring).
(See Dashboard reports)

Data (see Variable)
Information provided as the process case is run. Data is used to fill variables and in some places is used interchangeably with Variables.
(See Data and variables)

Can refer to users external databases such as MySQL, to the default Hibernate database used by BOS; or to the database tables set up by the user to work with BOS
(See Prepare databases for use with BOS)

Data type
Or variable type. Specify the type of data a variable can be filled with.
(See Data types)

Run a process without connectors. This enables to find out which connectors do not work by excluding them from the execution of a process.

Decision table
A graphic editor used to write groovy expressions using standard operators.

(See Use a decison table to define conditions)

Default flow
The path the process takes, when all other paths have transition conditions that evaluate to false.
(See Define conditions onTransitions)

The user assigned to a Step when the designated User is unavailable.
(See How to assign a manager / delegee of a user)

Java libraries needed for a process to run: connectors, validators, third-party libraries, scripts.
(See Add dependencies to a process)

Ageneral processthat can be customized according to specific requirements or characteristics, to make a software application available for use.
(See Deployment)

The tab in the details panel where an element is named.
(SeeDescribe a pool)
(SeeDefine a dynamic element title, description, or summary)

Details panel
The details panel is a set of 4 tabs panel at the lower right of Bonita Studio. It is used to configure details for design and execution of Process elements.
(See Details panel)

A graphical representation of one or more processes (on the Whiteboard), adiagram is a file that contains the process design, with all its elements, attributes and dependencies, withinBonita Studio.
You can have several process diagrams open at one time in Bonita Studio.
(See Diagram)

Document management
A system for uploading, storing and managing electronic documents, images, and other files.
Bonita Open Solution provides a means to upload and manage documents as processes are running, case by case.
Documents can include files, images, or any file that you can browse to through Bonita User Experience.
(See Document Management)

Not fixed. In the process design, you can use data to customize a title, description, or summary when the element (such as a task) is presented in a case in Bonita User Experience.
The result will change dynamically according to the data input.
(SeeDefine a dynamic element)


Embedded Eclipse options for developer use
(See Preferences)

End event
Represents the result of a process; indicated by a single thick or bold border

(SeeBonita Execution Engine)

Engine log
Includes the log of the application server embedded by Bonita Studio.

Entry pageflow
Used for interactive (entry) Forms. Manages the sequence of pages in a multipage form.
(See use an Entry form)

Error events
Errorscarry information about exceptions. An exception always diverts the normal proess flow to an exception path.
An error signal thrown by an end event is caught by a start or boundary error. This is callederror throw-catch.
(See Error events)

Elements in the Process design that are neither Tasks nor Gateways; e.g. Start, stop, intermediate action.
(See Start events)

Event subprocess
(See Subprocesses)

Exceptions processing
To adjust and repair transactions that could not be completed.
(See Exceptions)

Execute(see Run)
Deploy a process
(SeeRun a process)
(SeeRun a simulation)

Execution time
(See Simulation execution time)

A way of saving elements of a process to be used elsewhere.
It is possible to export a bar file, a connector, a repository, simulation artifacts, a KPI and a process for deployment.
(See Export a diagram)
(See Advanced export)
(SeeExport a Connector)
(See Export a repository)

Script written in code in an expression editor
(See Expression editor)

Externally created artifacts that can be used to extend the capabilities of BOS; e.g. connectors, role resolvers, actor selectors, jar files, etc.
(See Import community contribution)


A field is created on a form using widgets. This form will appear in user XP and the user will enter information in it.
(See Form field design)

A filter selects a subset of data from a given set.
(See Apply a filter)
In Bonita User Experience, the end user canfilteropen and archived cases from the users list of cases.
(See also Filters)

Float and floating

Floatingdecimal variables in Bonita Open Solution are equal to Java.lang.Double.
(See Define a floating decimal variable)

(SeeForm field design)

Form builder
The Form Builder is used to create and customize forms which are deployed via a standalone Web based application.
(SeeForm field design)

Form template
A model for creating forms.
(SeeCreate a new form template)


Branch point in the process flow represented as a diamond shape. A gateway controls the process flow.
(See Gateways)

The grid tool basically enables a grid (a series of lines placed horizontally and vertically) on top of or behind the elements on a whiteboard.
This helps the positioning of elements. A special magnetic positioning tool calledsnap to,pulls the elements to place on the grid.
(See Apply a grid to a process diagram)

Groovy script
An object-oriented programming language for the Java platform. It can be used as a scripting language to write expressions on conditions, on forms etc.
Groovy uses a Java-like bracket syntax.
(See Execute a groovy script)

A set of individual users, defined by the Administrator.
(See Define groups)

Guidance (User Guidance)
A useful tool to adapt Bonita Open Source to the user, with the help ofUser Guidance profilesUser Guidance checklists.
(See User Guidance)


History (Case history)
The (case) history shows a condensed series of steps. The default Step Summary is The Step [Step name] has been completed.
This can be changed to something more descriptive, and can includedynamic content, as configured in Bonita Studio.