Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
开发团队
Flowable Engine
提交
7bb19406
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,发现更多精彩内容 >>
提交
7bb19406
编写于
12月 03, 2013
作者:
J
Joram Barrez
浏览文件
操作
浏览文件
下载
电子邮件补丁
差异文件
ACT-1869: Document signal event scope
上级
05b20715
变更
1
隐藏空白更改
内联
并排
Showing
1 changed file
with
24 addition
and
1 deletion
+24
-1
userguide/src/en/chapters/ch07b-BPMN-Constructs.xml
userguide/src/en/chapters/ch07b-BPMN-Constructs.xml
+24
-1
未找到文件。
userguide/src/en/chapters/ch07b-BPMN-Constructs.xml
浏览文件 @
7bb19406
...
...
@@ -291,6 +291,7 @@ RuntimeService.signalEventReceived(String signalName, String executionId);
</section>
<section
id=
"bpmnSignalEventDefinitionQuery"
>
<title>
Querying for Signal Event subscriptions
</title>
<para>
It is possible to query for all executions which have subscribed to a specific signal event:
<programlisting>
List
<
Execution
>
executions = runtimeService.createExecutionQuery()
...
...
@@ -298,9 +299,31 @@ RuntimeService.signalEventReceived(String signalName, String executionId);
.list();
</programlisting>
We could then use the
<code>
signalEventReceived(String signalName, String executionId)
</code>
method
to deliver the signal to these executions.
to deliver the signal to these executions.
</para>
</section>
<section
id=
"bpmnSignalEventDefinitionScope"
>
<title>
Signal event scope
</title>
<para>
By default, signals are
<emphasis>
broadcasted process engine wide
</emphasis>
. This means that you
can throw a signal event in a process instance, and other process instances with different process definitions
can react on the occurence of this event.
</para>
<para>
However, sometimes it is wanted to react to a signal event only within the
<emphasis>
same process instance
</emphasis>
.
A use case for example is a synchronization mechanism in the process instance, if two or more activities are
mutually exclusive.
</para>
<para>
To restrict the
<emphasis>
scope
</emphasis>
of the signal event, add the (non-BPMN 2.0 standard!)
<emphasis>
scope attribute
</emphasis>
to the signal event definition:
<programlisting>
<
signal id=
"
alertSignal
"
name=
"
alert
"
activiti:scope
"
processInstance
"
/
>
</programlisting>
The default value for this is attribute is
<emphasis>
"
global
"
</emphasis>
.
</para>
</section>
<section
id=
"bpmnSignalEventDefinitionExample"
>
<title>
Signal Event example(s)
</title>
...
...
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录