Difference between revisions of "Process modelling"
From OpenKM Documentation
(→End node) |
|||
| Line 20: | Line 20: | ||
=== Task node === | === Task node === | ||
| + | [[File:Jbpm node task.png|center]] | ||
=== Node node === | === Node node === | ||
| + | [[File:Jbpm node node.png|center]] | ||
=== State node === | === State node === | ||
| + | [[File:Jbpm node state.png|center]] | ||
=== Decision node === | === Decision node === | ||
| + | [[File:Jbpm node decision.png|center]] | ||
=== Fork node === | === Fork node === | ||
| + | [[File:Jbpm node fork.png|center]] | ||
=== Join node === | === Join node === | ||
| + | [[File:Jbpm node join.png|center]] | ||
Revision as of 10:35, 12 January 2012
We are going to describe the elements which define a jBPM process. A process is composed by:
- Nodes
- Transitions
To create a process definition in a graphical way, you can use jBPM Graphical Process Designer. This tool is packaged as a Eclipse plugin.
Nodes
The define the states of the process definition. They are connected by transitions. Both define the different path which can be followed in a running process definition. A running process definition is called process instance.
There are several types of nodes:
Start node
End node
Task node
Node node
State node
Decision node
Fork node
Join node
