Information Technology Reference
In-Depth Information
Bases, KIE Sessions, and special configurations for each one to work in the way we ex-
pect them.
Keep track of how to get to the knowledge settings of our project for now, because we
will use it later. But first, before we configure how to expose our process definitions, we
need first to learn how to define them. To do so, let's take a look at the jBPM6 Process
Designer.
Process designer
The process designer is started whenever we choose to create a business process (by se-
lecting the
New Item
|
Business Process
option in the project authoring perspective), or
open one that we previously created from the
Project Explorer
view (the one on the left-
hand side of the
Project Authoring
perspective). It should be a tool flexible enough to al-
low users to create their own specific types of extensions to the BPMN2 standard, but
strict enough to allow the generated process definition to still comply with the standard.
That way, the generated process will be able to run the process runtime with jBPM6 the
way the user wants, and at the same time, it will be able to run in any other type of pro-
cess runtime that is compliant with BPMN2.
To achieve this level of flexibility, enough configurations should be allowed so that every
implementation parameterization can be added to the business processes being defined. In
order to keep the structure of the process in a tidy but efficient way, the process designer
provides an attribute panel to define specific parameters for all the components in the dia-
gram, from a specific sequence flow to the process itself.
In the following screenshot, we see a brief glimpse of the process designer UI present in
the Workbench:
