Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
开发团队
Flowable Engine
提交
9eff1235
F
Flowable Engine
项目概览
开发团队
/
Flowable Engine
通知
9
Star
0
Fork
0
代码
文件
提交
分支
Tags
贡献者
分支图
Diff
Issue
0
列表
看板
标记
里程碑
合并请求
0
DevOps
流水线
流水线任务
计划
Wiki
0
Wiki
分析
仓库
DevOps
项目成员
Pages
F
Flowable Engine
项目概览
项目概览
详情
发布
仓库
仓库
文件
提交
分支
标签
贡献者
分支图
比较
Issue
0
Issue
0
列表
看板
标记
里程碑
合并请求
0
合并请求
0
Pages
DevOps
DevOps
流水线
流水线任务
计划
分析
分析
仓库分析
DevOps
Wiki
0
Wiki
成员
成员
收起侧边栏
关闭侧边栏
动态
分支图
创建新Issue
流水线任务
提交
Issue看板
体验新版 GitCode,发现更多精彩内容 >>
提交
9eff1235
编写于
2月 22, 2012
作者:
M
meyerd
浏览文件
操作
浏览文件
下载
电子邮件补丁
差异文件
ACT-1095 adding documentation on cancel end events and cancel boundary events
上级
4b72e15d
变更
3
隐藏空白更改
内联
并排
Showing
3 changed file
with
108 addition
and
1 deletion
+108
-1
userguide/src/en/chapters/ch07-BPMN.xml
userguide/src/en/chapters/ch07-BPMN.xml
+108
-1
userguide/src/en/images/bpmn.boundary.cancel.event.png
userguide/src/en/images/bpmn.boundary.cancel.event.png
+0
-0
userguide/src/en/images/bpmn.cancel.end.event.png
userguide/src/en/images/bpmn.cancel.end.event.png
+0
-0
未找到文件。
userguide/src/en/chapters/ch07-BPMN.xml
浏览文件 @
9eff1235
...
...
@@ -1447,6 +1447,7 @@ ProcessInstance startProcessInstanceByMessage(String messageName, String busines
</section>
<!-- ////////////////////////////////////// End Events -->
<section
id=
"bpmnEndEvent"
>
...
...
@@ -1462,6 +1463,8 @@ ProcessInstance startProcessInstanceByMessage(String messageName, String busines
</section>
<!-- ////////////////////////////////////// None End Event -->
<section
id=
"bpmnNoneEndEvent"
>
<title>
None end event
</title>
...
...
@@ -1504,6 +1507,8 @@ ProcessInstance startProcessInstanceByMessage(String messageName, String busines
</section>
</section>
<!-- ////////////////////////////////////// Error End Events -->
<section
id=
"bpmnErrorEndEvent"
>
...
...
@@ -1575,8 +1580,49 @@ ProcessInstance startProcessInstanceByMessage(String messageName, String busines
</section>
</section>
<!-- ////////////////////////////////////// Cancel End Event -->
<section
id=
"bpmnCancelEndEvent"
>
<title>
Cancel end event
</title>
<section
id=
"bpmnCancelEndEventDescription"
>
<title>
Description
</title>
<para>
The cancel end event can only be used in combination with a bpmn transaction subprocess.
When the cancel end event is reached, a cancel event is thrown which must be caught by a
cancel boundary event. The cancel boundary event then cancels the transaction and triggers
compensation.
</para>
</section>
<section
id=
"bpmnCancelEndEventGraphicalNotation"
>
<title>
Graphical notation
</title>
<para>
A cancel end event visualized as a typical end event (circle with thick outline), with the
cancel icon inside. The cancel icon is completely black, to indicate the throwing semantics.
<mediaobject><imageobject><imagedata
align=
"center"
fileref=
"images/bpmn.cancel.end.event.png"
/></imageobject></mediaobject>
</para>
</section>
<section
id=
"bpmnCancelEndEventXml"
>
<title>
XML representation
</title>
<para>
A cancel end event is represented as an end event, with a
<emphasis>
cancelEventDefinition
</emphasis>
child element.
<programlisting>
<
endEvent id=
"
myCancelEndEvent
">
<
cancelEventDefinition /
>
<
/endEvent
>
</programlisting>
</para>
</section>
</section>
<!-- ////////////////////////////////////// Boundary Events -->
<section
id=
"bpmnBoundaryEvent"
>
...
...
@@ -1722,6 +1768,9 @@ ProcessInstance startProcessInstanceByMessage(String messageName, String busines
</section>
<!-- ////////////////////// error boundary event -->
<section
id=
"bpmnBoundaryErrorEvent"
>
<title>
Error Boundary event
</title>
...
...
@@ -1825,6 +1874,8 @@ ProcessInstance startProcessInstanceByMessage(String messageName, String busines
</section>
<!-- ////////////////////// signal boundary event -->
<section
id=
"bpmnBoundarySignalEvent"
>
<title>
Signal Boundary event
</title>
...
...
@@ -1880,6 +1931,62 @@ ProcessInstance startProcessInstanceByMessage(String messageName, String busines
</section>
</section>
<!-- ////////////////////// cancel boundary event -->
<section
id=
"bpmnBoundaryCancelEvent"
>
<title>
Cancel Boundary event
</title>
<section
id=
"bpmnBoundaryCancelEventDescription"
>
<title>
Description
</title>
<para>
An attached intermediate
<emphasis>
catching
</emphasis>
cancel on the boundary of a transcation subprocess,
or
<emphasis
role=
"bold"
>
boundary cancel event
</emphasis>
for short, is triggered when a transaction
is cancelled. When the cancel boundary event is triggered, it first interrupts all executions active in the
current scope. Next, it starts compensation of all active compensation boundary events in the scope of the
transaction. Compensation is performed synchounously, i.e. the boundary event waits before compensation is
completed before leaving the transaction. When compensation is completed, the transaction suprocess is left
using the sequence flow(s) running out of the cancel boundary event.
</para>
<para>
<emphasis
role=
"bold"
>
Note:
</emphasis>
Only a single cancel boundary event is allowed for a transaction subprocess.
</para>
<para>
<emphasis
role=
"bold"
>
Note:
</emphasis>
If the transaction subprocess hosts nested subprocesses, compensation is only triggered for subprocesses
that have completed sucessfully.
</para>
</section>
<section
id=
"bpmnBoundaryCancelEventGraphicalNotation"
>
<title>
Graphical notation
</title>
<para>
A cancel boundary event is visualized as a typical intermediate event (Circle with smaller circle inside)
on the boundary, with the cancel icon inside. The cancel icon is white (unfilled), to indicate
the
<emphasis>
catching
</emphasis>
semantics.
<mediaobject><imageobject><imagedata
align=
"center"
fileref=
"images/bpmn.boundary.cancel.event.png"
/></imageobject></mediaobject>
</para>
</section>
<section
id=
"bpmnBoundarySignalEventXml"
>
<title>
Xml representation
</title>
<para>
A cancel boundary event is defined as a typical
<link
linkend=
"bpmnBoundaryEvent"
>
boundary event
</link>
:
<programlisting>
<
boundaryEvent id=
"
boundary
"
attachedToRef=
"
transaction
"
>
<
cancelEventDefinition /
>
<
/boundaryEvent
>
</programlisting>
Since the cancel boundary event is always interrupting, the
<code>
cancelActivity
</code>
attribute
is not required.
</para>
</section>
</section>
<!-- ////////////////////// intermediate catching events -->
<section
id=
"bpmnIntermediateCatchingEvent"
>
...
...
userguide/src/en/images/bpmn.boundary.cancel.event.png
0 → 100644
浏览文件 @
9eff1235
5.3 KB
userguide/src/en/images/bpmn.cancel.end.event.png
0 → 100644
浏览文件 @
9eff1235
1.1 KB
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录