I am not very clear about BPMN, and at present it is only because of the unfamiliar components of Modeler query, to learn about this part of the content, do not ask for an understanding, learn to understand it. So the introduction of this chapter will be relatively simple, but also enough.
The list of components in Modeler is slightly different from BPMN, and some of the content doesn't seem to have been ported to your demo, and there are some problems, and if possible, a detailed description of Modeler's composition, It is roughly the seventh section of the Official document overview and tenth process (important) that has been summed up on the web by http://wenku.baidu.com/view/92b1bc06cc17552707220854.html? From=search, you can see the contents of this link directly. I'm following the proofreading of its and official documents, stating that this column is not translated (too time consuming).
BPMN (Business process Modeling Notation), Orchestration Modeling and labeling, can form a business flowchart with a series of symbols (I call components) that define them. These components are then described in categories. Official website: http://www.bpmn.org/There is a BPMN v2.0 introduction and examples, if you do not understand can be viewed. http://www.omg.org/spec/BPMN/2.0/document and XML checksum file XSD. This is the detailed introduction, but are all in English, I am too lazy to read, just a few basic applications, if there is a need to look at the time. Http://www.omg.org/cgi-bin/doc?dtc/10-06-02 Here are some of the official examples that teach you how to use these components.
1 Stream object (flow Objects)
The flow object is the most basic concept, it is very important.
1.1 Event (events) P271
Events are represented by a circle, which affects the flow of the flow, usually with a cause (trigger) or an impact (result). The standard defines three types of events: Start, middle, and end. From the definition and classification names can also guess the role of events, control the beginning of the process, intermediate flow and end, these controls may take a trigger (trigger) to complete, or lead to a result (end or throw).
(1) Start Event
Chinese |
English |
Trigger |
Description |
Marker |
Start Event |
Start Event |
None |
|
|
Conditional Start Event |
Conditional Start Event |
Conditional |
|
|
Message Start Event |
Message Start Event |
Message |
|
|
Multiple boot events |
Multiple Start Event |
Multiple |
|
|
Multiple Parallel start events |
Parallel Multiple Start Event |
Parallel Multiple |
|
|
Signal Start Event |
Signal Start Event |
Signal |
|
|
Timed Start Events |
Timer Start Event |
Timer |
|
|
(2) Intermediate Event Intermediate Event intermediate events are used in two ways: 1. Place intermediate events in a normal workflow for two purposes: intermediate events can be used for "catch" event triggers, or "throw" event departures. 2. An intermediate event is placed in the middle of an activity, and can only be used for "catch" event triggers, that is, capturing an event and handling it accordingly.
Chinese |
English |
Trigger |
Description |
Marker |
Intermediate events |
None Intermediate Event |
None |
|
|
Message Events |
Message Intermediate Event |
Message |
|
|
Timed events |
Timer Intermediate Event |
Timer |
|
|
Upgrade Events |
Escalation Intermediate Event |
Escalation |
|
|
Compensating events |
Compensation Intermediate Event |
Compensation |
|
|
Conditional events |
Conditional Intermediate Event |
Conditional |
|
|
Link Events |
Link Intermediate Event |
Link |
|
|
Signal Events |
Signal Intermediate Event |
Signal |
|
|
Multiple events |
Multiple intermediate Event |
Multiple |
|
|
Parallel Multiple Events |
Parallel Multiple Intermediate Event |
Parallel multiple |
|
|
The intermediate event is not only these, the remaining is related to Activiti boundary, here is not listed, specific view of the official website document P284 page. (3) The End Event End event must be the target of a sequential flow, not a source, and can have multiple sequential flows pointing to the same end stream. A process can have multiple end events or no end events, but if there is a start event, at least one end event must be present. If you do not use an end event, then all stream objects do not have any outgoing sequence (sequential) flow (that is, a different source sequence flow) to flag the process end. The process does not end until all parallel paths are completed.
Chinese |
English |
Trigger |
Description |
Marker |
End Event |
None End Event |
None |
|
|
Message End Event |
Message End Event |
Message |
|
|
Error End Event |
Error End Event |
Error |
|
|
Upgrade End Event |
Escalation End Event |
Escalation |
|
|
Cancel End Event |
Cancel End Event |
Cancel |
|
|
Compensation End Event |
Compensation End Event |
Compensation |
|
|
Signal End Event |
Signal End Event |
Signal |
|
|
Terminating End Event |
Terminate End Event |
Terminate |
|
|
Multiple End Events |
Multiple End Event |
Multiple |
|
|
1.2 Activities (Activities) P181
(1) Tasks P186
A task is an atomic activity in the process flow, and the task is used as a finer level of detail when the job in the process cannot be interrupted. Typically, an end user or an application whose execution behaves as a task form. The Task object has the same shape in the sub-process, all rectangles have rounded corners.
There are three special task icons: loops, multiple instances, and compensation, and one task may have one or two such icons.
Other tasks:
Chinese |
English |
Description |
Icon |
Service tasks |
Service Task |
|
|
Send Task |
Send Task |
|
|
Receiving tasks |
Receive Task |
|
|
User Tasks |
User Task |
|
|
Manual tasks |
Manual Task |
|
|
Business Rule Tasks |
Business Rule Task |
|
|
Script Task |
Script Task |
|
|
In these tasks, people are required to participate in the manual task and user task that they have completed. The Manual task is a task that is not managed by any commercial process engine, and the User task is. Being out of management means that the process engine cannot track the start and finish of its tasks. For example, this could be a paper full of instructions for telephone technicians to help customers install the phone.
(2) Sub-processes sub-process P203
A sub-process is a model of the internal details of an activity, using activities, events, and gateways, and sequence flows. A sub-process is a graphical object within a process, but it can also be opened to show a lower level of flow. A sub-process defines a context scope that can be used for property visibility, scope of transactions, exception handling, events, or compensation.
BPMN defines a five seed flow, where collapsed sub-process can be replaced by four additional combinations. The other four types are loop, multi-instance, compensation, Ad-hoc.
Here are some uses:
(3) Call activity P213
Call activity determines the point in a process that uses a global process or global task. The calling procedure is used as a wrapper to invoke the global process or global task execution. Activating the invoke activity results in a control transfer called a global process or global task.
The invocation activity must satisfy the data requirements while calling Callableelement to return the data. This means that these elements need to be included in the active inputoutputspecification and must be matched exactly to the callableelement element. These elements include: Datainputs, Dataoutputs, Inputsets, Outputsets.
1.3 Gateway (Gateways) P317
Gateways are used to control how sequential flows converge and diverge in a process. If a process does not need to be controlled, then the gateway is non-essential. The term "gateway" means there is a gate mechanism. Allow or disallow through the gateway-that is, when executing to the gateway, when the gateway mechanism is invoked, the input can be merged together, or the output is separated into several parts.
Chinese |
English |
Description |
Icon |
Mutex Gateway |
Exclusive Gateway |
|
|
Event Gateway |
Event-based Gateway |
|
|
Parallel Event Gateways |
Parallel Event-based Gateway |
|
|
Compatible gateways |
Inclusive Gateway |
|
|
Complex gateways |
Complex Gateway |
|
|
Parallel gateways |
Parallel Gateway |
|
|
2 Data (P233)
Traditional process modeling requires the ability to simulate the creation, operation, and execution of items (physical or informational) in a process. The important aspect is the ability to capture the structure of the data and query or manipulate the structure.
BPMN itself does not provide a built-in model to describe a data structure or a language expression of the query. Instead, it regulates hooks to allow the use of externally defined data structures and expression languages. In addition, BPMN allows different data structures and expression languages in the same model. The compatibility and validation of these languages is beyond the scope of the specification and becomes the responsibility of the tool vendor.
BPMN uses XML schema and XPath as its default data structure and expression language, but vendors are free to replace their own language.
Chinese |
English |
Description |
Icon |
Data Objects |
Data Object |
|
|
Aggregate Data Objects |
Collection DataObject |
|
|
Data storage |
Data Store |
|
|
Input data |
Data Input |
|
|
Output |
Data Output |
|
|
There are other uses, depending on the official documentation. 3 Connection object (connecting Objects) P59
4 Lanes (Swimlanes) 4.1 Pool (pools)
A pool is a container that is isolated from other pools. Typically used in an interactive process. The pool acts primarily on the physical division between two independent entities or participants. Activities in each pool usually have their own processes. As a result, sequential flow does not usually cross multiple pools, and message flow is possible (excerpt from: Http://wenku.baidu.com/view/59b540d228ea81c758f5783c.html?from=search)
4.2 Lanes (Lanes)
The sub-division of the pool, which can be vertical or horizontal, is used to organize and classify activities. Lane is closer to the concept of our traditional swimlane. Lane is often used to divide activities into roles, and the process can flow across the lane in a pool, but in a pool it usually does not (the source is the same as above).
5 workpiece (artifacts) 5.1 groups (group)
Grouping a subset of elements for logical or specific purposes for easy viewing and management, for interpretation and description purposes, without affecting the flow of the process (IBID.).
5.2 Text annotations (text Annotation)
Provide some additional textual information to the reader of the flowchart.
Activiti Construction (v) BPMN Introduction