本文探讨了jBPM工作流中业务流程的实现方式，包括任务的多种实施手段如网页、业务组件等，并通过结构化的工作流串联起来。在Seam框架下，jBPM页面流作为单一会话内的对话的一部分。业务流程由一系列节点或状态构成，通过不同的过渡相连。文章还介绍了八种流程节点，包括起始和结束状态、多个任务节点以及分叉和合并节点。
Practical JBoss Seam Projects
Page 159 to 161
1) jBPM Supporting tasks implemented in variety of ways (web pages, business components, business rules, etc.), connected together with a structured workflow that can span multiple users across potentially long periods of time.
2) And in the case of Seam, a jbpm pageflow is actually part of a single Seam conversation within a single session.
3) A business process consists of a set of [b]nodes[/b] or [b]states[/b], linked by various possible [b]transitions[/b].
4) [b]Events[/b] in the business process cause various [b]actions[/b] to be executed.
5) There are eight nodes in this workflow. Six of them are named states in the process:
the starting state ("start-state'),
a "write article" task,
a "tech edit" task,
a "copy edit" task,
a "revise article" task,
the end state ("end')
The other two, unnamed nodes are a fork, between the article submission and the two parallel editing tasks, and a join, where the two parallel editing tasks transition to the article revision task.
Various transitions exist between these nodes. Some of these are named, indicating specific actions that have to take place in order for the transition to take place. Others are not named, either because there is only one transition out of a given node, or the nature of the transition is obvious from the start and end nodes.
jBPM maintains the process model in terms of the allowed states, the various transitions between states, and actions and events that can trigger these transitions.
BPM also includes the concept of actors, allowing you to specify what type of user can and should perform specific tasks in the process.
Page 159 to 161
1) jBPM Supporting tasks implemented in variety of ways (web pages, business components, business rules, etc.), connected together with a structured workflow that can span multiple users across potentially long periods of time.
2) And in the case of Seam, a jbpm pageflow is actually part of a single Seam conversation within a single session.
3) A business process consists of a set of [b]nodes[/b] or [b]states[/b], linked by various possible [b]transitions[/b].
4) [b]Events[/b] in the business process cause various [b]actions[/b] to be executed.
5) There are eight nodes in this workflow. Six of them are named states in the process:
the starting state ("start-state'),
a "write article" task,
a "tech edit" task,
a "copy edit" task,
a "revise article" task,
the end state ("end')
The other two, unnamed nodes are a fork, between the article submission and the two parallel editing tasks, and a join, where the two parallel editing tasks transition to the article revision task.
Various transitions exist between these nodes. Some of these are named, indicating specific actions that have to take place in order for the transition to take place. Others are not named, either because there is only one transition out of a given node, or the nature of the transition is obvious from the start and end nodes.
jBPM maintains the process model in terms of the allowed states, the various transitions between states, and actions and events that can trigger these transitions.
BPM also includes the concept of actors, allowing you to specify what type of user can and should perform specific tasks in the process.
扫一扫
1047
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
