Glossary

A B C F G H I J K L M N O P Q R S T U V W X Y Z

A
 

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)

About

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)

Activity

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)

Actor

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)

Appearance

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

Applications
(See Web Applications)

Application developer

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

ARIS

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

Artifact

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)

Attachment

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)

Attribute

Atributes define additional information about an element.

(See Design a report template)
(See Diagram)
(See Redirect a form page)

B

.bar

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

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)

BPMN

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)

C

Call activity

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

Case

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

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.
(See Case history)

Catch

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)

Category

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)
(See Complex data)

Cool bar

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

Condition

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)

Confirmation

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

(See Confirmation message)

Connector

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)

Context

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.
(See Context palette)

Contiguous

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)

Contingency

Making one element dependant on another element
(See Contingency)

Contributions

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)
 

D

Dashboard

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)

Database

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)

Debug

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

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 on Transitions)

Delegee

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

Dependencies

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

Deployment

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

Description

The tab in the details panel where an element is named.
(See Describe a pool)
(See Define 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)

Diagram

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)

Dynamic

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.

(See Define a dynamic element)

E

Eclipse

BOS is an Eclipse RCP  (Rich Client Platform)
(See Eclipse RCP)

End event

Represents the result of a process; indicated by a circle with single thick line or bold border
(Terminate end event)

Engine

(See Bonita Execution Engine)

Engine log

Includes the log of the application server embedded by Bonita Studio.
(See Engine logs)
(See Configure logging)

Entry pageflow

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

Error events

Errors carry 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)

Event

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

(See Run)
(See Run a simulation)

Execution time
(See Simulation execution time)

Export

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)
(See Export a Connector)
(See Export a repository)

Expression

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

Extensions

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)

F

Field

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)

Filter

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

(See Customize-user-experience-looknfeel-manually)

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

Form

(See Form field design)

Form builder

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

Form template

A model for creating forms.
(See Create a new form template)

G

Gateway

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

Grid

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)

Group

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)

H

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.

(See Case history)
(See Log history)
(See Versioning and history)

Host

IP address or name of an email server
(See Send an email)

(See Connector configuration)

Human task (see task)

A human task is a task that requires intervention bya human (actor). It needs to be assigned anactor.
(See Human task)

I

Inclusive gateway

Inclusive gateways are activitated when the first input transition arrives and fire output transitions simultaneously.

XOR join, AND split; the first input to arrive will allow the process to pass through the Gate if there are multiple outputs, all will fire.
(See Inclusive Gateways)

Initiator

This actor selector will retrieve the user who has initiated the process. It does not require configuration.
However, you can create an actor selector to select the process initiator with a different name.
(See Process initiator)

Instance

A single case of a process.A Start instance connector will start a process instance (ie, instantiate a process) when it is activated.
(See Start an instance)

Instantiator

Allows you to specify values for variables for each instance of a multi-instantiated task. The instantiator will be called to initialize the data for each instance as it is created.
(See Define a new instatiator)

Integer variable

Integer variables in Bonita Open Solution are equal to java.lang.Long and can have a value between -263and 2-63.
(See Define an Integer variable)

Internationalization

Choose the language in which forms are presented in the web application.
This feature uses an internationalization key. Define the default string, then the key to apply to it to change the language that is presented for the form element (e.g. field widget label, field initial value, form name, etc.)
(See Choose languages for forms)

Iterator

An iterator repeats a set of instructions or tasks.
(See Use complex data in multi-instatiated data fields)
(See Multi-instantiation)

J

Jar

Java Archive file (compressed). Used to distribute a Java application or library. Collection of Java class files, text, images.µ
(See Add dependenacies to a process)
(See Define a complex data as a variable)

Java class

(See Java connector)

Jbpm

A workflow engine written in Java
(See Import a diagram)

Join checker

When a multi-instantiator creates multiple parallel tasks, the join checker checks whether a number of a tasks in progress have finished or not.
(See Develop a new join checker)
(See Multi-instantiation)

JRE

Java Runtime Environment
(See Java requirements)

K

Key

Text field variables in the process.
(See Define context keys)

Code generated by Bonita Subscription pack to unlock the features).
(See License key)

KPI

Key Performance Indicators (KPIs) in Bonita Open Solution refer to any data that you want to collect on a process for Business Activity Monitoring (BAM).
(See Configure KPI /BAM

L

Lane

A lane is used to organize tasks in a pool. A lane generally represents a functional or organizational group.
(See Lane)

Language

Choose the language for the Bonita Studio interface or Bonita Use Experience.
(See Choose language for Bonita Studio)
(See Choose language for forms)
(See Choose language for Bonita User Experience)

Library

A collection of jar files that can be installed.
(See Install a BAM report)

Link events

Business process modeling (BPMN) uses link events to allow the process designer to graphically cut up a long and/or complexprocesssequence, and link up parts that are not next to each other on the whiteboard.
(See Link events)
(See Catch or throw links)

List of options

The list of options variable can be used to define a set of items from which a user can choose one or more.
(See Define a list of options as a variable)

Local repository

A workspace situated in the home directory for the Bonita Sudio installation.In Bonita Subscription pack, you can create a local repository in your local workspace, without being connected to SVN.
The repositories are created in the local folder on your computer:BOS SP 5.6 > Studio > Workspace.
(See Create a local repository)

Log files

Files where Bonita Execution Engine data execution is recorded.
(See Access log files)

Look 'n feel

The appearance of web applications generated with BOS; can be modified and customized in several ways.
(See Change the look'nfeel of web forms)

Looping

Looping allows the process to execute a task or a call activity (subprocess) repeatedly, either until a condition (defined as an expression) has been met, or until a specified number of loops has completed.
(See Loop a task or a call activity)

M

Manager

Organizational lead of a team of Users
(See Assign manager)

Menu bar

Bar with roll down menus, located at the top of the Bonita Studio screen, above the Task bar
(See Menu bar)

Message event

Message events are used in a process to carry information from one process (pool) to another.
(See Message events)

Message flow

Message flow is theway messages move around a process diagram.
(See BPMN)

Microsoft Visio

Microsoft visio is one of the diagram formats that can be imported into Bonita Studio.
(See Import a diagram)

Model

A model is a graphic representation of a real-world process; an executable model can emulate the steps in a process.
(See Set Process validation)

Monitor

Process monitoring shows the status of open steps, overdue steps, cases created, and steps created in real time. It is refreshed every 3 seconds.
(See Monitor processes)

Monitor JVM

Shows the resources used in real time by your Java Virtual Machine. It is refreshed every 3 seconds.
(See JVM monitoring)

Multi-instantiation

Multi instantiationinstantiates (initiates) the same task or set of tasks multiple times in parallel. The number of instances (and possibly also the specific actors who will perform each instance), are determined in the process design.The number of iterations of a multi-instantiated task are known in advance and the iterations are performed in parallel.
(See Multi-instantiation)

N

New diagram

New pool and lane

New calendar event

New case 

New form template

New task

New join checker

New instantiator

New look n feel

New filter

New connector

New form from a template

O

Outgoing transitions

When a simulation is run, the multiple iterations may take different paths to completion, simulating various possibilities for a process case.

(See Outgoing transitions)

Overview

The overview panel enables the uqser to quickly get a general view of the process. It is composed of 2 views:aquick overviewand asearchable tree-view.

(See Overview panel)

Overview form (Pageflow)

Use Overview pageflow to define the field content and placementfor forms that are presented in the Administration view of Bonita User Experience.

(See Overview form)

P

Pool

A Pool is equivalent to a stand-alone process and contains all the elements and resources needed to deploy a complete process.It can contain one or more lanes which might represent different organizations participating in the process. A pool constrains sequence flow which means a flow (that is, a transition) cannot cross over to another pool 
(See Pool)

Preferences

Bonita Studio and some Bonita User Experience preferences can be changed or re-set to default configurations.

(See Preferences)

Priviledges

(See Priviledges)

Probability

(See Probability)

Process or Pool

A seance of tasks linked by transitions to create a flow of information.

(See Pool)

Process designer/developer

A process designer uses Bonita Studio to design a process, resulting in a Process Diagram, Connectors, and end user Forms.
(See Process design)

Process Instance

Describes an actual process which includes data, real actions, and specific decisions taken as the process advances

Process Management

Monitoring a process, managing exceptions, measuring results of the process
(See Monitoring)
(See monitor processes)

Profile

(See User Guuidance)

Properties

The parameters of an object which can be modified.

(See Common properties for a task)

Protocol

Protocol a set of rules & regulations that determine how data is transmitted.

For example, the Internet protocol is responsible for addressing hosts and routing datagrams (packets) from a source host to the destination host across one or more IP networks.
(See CMIS)
(See Search in a LDAP directory service)

Q

R

Receive task

A task that is performed only when it receives a Message
(See Receive task)

Repository

A repository can be local or remote on a server. It can be a shared workspace with others, accessed by SVN.
(see Collaboration).

Reporting

Shows an overview of all Process Cases running and archived, incorporating data from all users.
(See Monitoring and reporting)

Resources

A collection of data used in creating process: they can be real, simulated or shared on repositories.

(See Assign simulation resources)
(See Define resources as unlimited)
(See Manage locks on shared resources)

REST

Representational State Transfer. An application is installed on a server and communicates with the Bonita Execution Engine via http protocol.
(See Configure BOS to use REST)

Restore point

A restore point in a process is a marker or flag created in the history of a process, that will allow you to restore a process back to a previous state.
(See Using restore points)

Role

The title/position/job of an individual user in an Actor selector, as defined in User Experience.
(See Define roles)

Rules

(See Drools)

Run or execute a process

Applied to execute a process diagram with the Bonita Execution Engine. What happens, essentially, behind the RUN button:

• The process and resources are packaged in a *.bar file (Bonita ARchive)
• A default Web application specific to this Process is created
• The Bonita Execution Engine and a lightweight relational database (Hibernate) are used by the application
• A web container is started and the *.war file deployed
• A new browser window opens and shows the initial application page

(See Run a process)
(See Run a simulation)

Runtime

Runtime is the environment of the Bonita Execution Engine.

(See Export a process for deployment)

S

Script task

An Automatic Task with a script that executes when the Task is reached in the Process.

(See Script task)

Send task

Sends a message; same as Send Message event.

(See Send task)

Sequence flow

Shows in which order the activities in a process flow will be performed.

(See Transitions)

Service task

Task processed and launched by Bonita Execution Engine without the need for human intervention; automatic task

(See Service task)

Simulation

Use simulation in Bonita Open Solution to evaluate the way a process runs under different resource availabilities and different load profiles.

(See Process simulation)

Signals

Signals broadcast or receive information from anywhere, either within a process or across different processes.Unlikemessages, they do not carry data.

(See Signal events)

Skip

The process instantiation form can bejumped, or missed out, when a process is deployed in Bonita User Experience.
If Skip is checked, the instance is automatically created.
(See Use a process instantiator)

Snap to grid

A grid is magnetized so an element on the whiteboard will attach itself to the nearest grid line whether the grid be in front or behind the diagram.
(See Apply a grid to a process)

Start event

Start events indicate where a process starts.
(See Start events)

Step

A task in a Process designed in Bonita Studio becomes a Step in Bonita User Experience, to be completed by a User.
(See Manage steps)

String

A string is a sequence of characters, either as a literal constant or as some kind of variable.
(See Filter process list).

Subprocess

A parent process can comprise children sub-processes. A subprocess represents a complete process (simple or complex) that can be called by a higher level process

when it reaches a call activity (the design element that represents a subprocess). Its behavior is the same as it would be if the subprocess were represented in-line.

However, it can be modified or replaced without changing the parent process.
(See Subprocess)

Subscription Pack

Adds support and extra features to Bonita Open Source to help collaboration, accelerate processing and increase security.
(See Subscription pack)

Synchronize

(See Synchronize a shared repository)

Synchronizer

The LDAP Synchronizer is a program that will synchronize Bonita Open Solution users and groups with an LDAP directory.
(See Synchronize LDAP)

In shared collaboration, shared process diagrams and workspaces can be synchronized (brought up to date) so everyone will always working on the latest version of a process with the latest dependancies.

(See Design collaboration)

Synchronous process

Activities which proceed in series; each task waits until the task preceeding it has completed before it can execute.

System administrator

The Superuser who has access to the Administration tools and can give rights to users, create new users and passwords etc.

System administrators guide

(See System Administrators guide)

Swimlane

Lane; it used to organize tasks in a pool. Generally represents a functional or organizational group.

(See Lane)

T

Task

An activity; an action in the Process, specific work performed. When a process is deployed and running, a Task in Bonita Studio becomes a Step in Bonita User Experience.

(See Task).

Throwing

Sends a message or a signal that will be received by another task or process.

(See Throw and catch).

Timer events

Timer events are used toStart a process on a predetermined schedule

(See Start timer)

Delay a process for a predetermined amount of time / until a specific date and time

(See Intermediate timer)

Countdown during a task until a predetermined deadline is reached

(See Boundary timer).

Timers

Timer events are used to:

• Start a process on a predetermined schedule (start timer)
• Delay a process for a predetermined amount of time / until a specific date and time (intermediate timer)
• Countdown during a task until a predetermined deadline is reached (boundary timer).

(See Timer events)

Transient data or variable

Define atransientvariable if this variable is meant to be a temporary placeholder, (for example, to treatdata in a formused in a single task, or to definepageflow.

(See Define a transient variable)

U

User Guidance

User Guidance consists of 2 parts:

• User Guidance profiles
• User Guidance checklists

(See User Guidance)

User role

(See Roles)

V

Variables

Data variables can be defined in Bonita Open Solution to accept, manipulate, and manage data for the process.

Variables can be definedglobally (for the entire process), orlocally (accessible only to a single task and its transitions).

(See Variables)

W

WAR

A WAR file (or Web application ARchive) is a JAR file used to distribute a collection of JavaServer Pages, Java Servlets, Javaclasses, XMLfiles, tag libraries and static Web pages (HTMLand related files) that together constitute a Web application.

(See Export a diagram)

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.

Note: In Library Export Mode, there are 3 choices :Embedded : the engine is included in the exported war file,Light : the engine is installed in the application server,Client war : the engine is installed in a remote application server. The bonita-client API is used in this case.

(See Export process for installation/deployment)

Web applications

Features to create forms are provided byForm Builderin Bonita Studio, and the results are visible in the forms presented in the web application(s) specified by the process designer.

(See Web applications)

Whiteboard

The whiteboard is where you draw your process using BPMN elements from thedesignandcontext palettes.

It allows you to draw one or more pools, and multiple lanes within each pool,inside a process diagram.

(See Whiteboard)

Widgets

Drag-n-drop tool in Form Builder used to define the type of field used in a form to accept and treat data.

A set of widgets (or mini applications), is available in theForm Builder paletteto define the characteristics of data fields in a form.

(See Widgets)

Workspace

BOS manages processes, libraries, artifacts, web archives, and more in each individual workspace (workspaces can be shared).

In Bonita Open Solution Open Source, collaborate on process design by exporting and importing a workspace.

(See Design collaboaration) 

XOR Gateway

The first input to arrive will allow the Process to pass through the Gate. If there are multiple outputs, only one will fire.

(See XOR Gateway)

X

XSD

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

(See Define a complex data package)

Y

Z