Java workflow engine node receives 20 kinds of people set a rule to explain

Keywords: ride fast workflow development platform workflow management system workflow engine workflow engine asp.net java workflow engine developers to drag and drop form Form workflow system CCBPM node access rules recipient rules.

Adaptation database: oralce, mysql, sqlserver, Informix, PostgreSQL up to the dream

Recipient rule, the next step is to send people to solve various rules established by the scope. Approval, the production environment has a lot of uncertainty, more often it needs to automatically determine the recipient of the range, in order to meet the needs of different occasions I propose the following rule recipient.

Summary Description

Related Functions: Access rule processing content.

Node attribute configuration: as shown below:

up-92ee9514fea08543c53593f35dd6085e705.png
up-d87269edb09a7a658df0e20ea5009b18712.png

Function entrance

Explanation: is the recipient of the next range of staff processing rules. A motion to B, who deal with how to determine the range B. According to different business scenarios, CCBPM provides the following mode, you can set up your own business rules to automatically according to different business backgrounds.

Description:

1, the following setting type, are provided to act on the next node the current node.

2, each type of path has automatic memory function, said memory function automatically when a node is the next node for the first time delivery, it is to be delivered to the person recorded.

If you execute the assignment of personnel distribution system to put, as to accept staff calculations.

Type of delivery that can be set:

In order to better explain the rules, cc process provides a test case for us, as follows:

up-65a7db6c1b75a7d50338ae6aa75c05c99ba.png

The case set a detailed method for each mode, open the node name associated attributes, the control node, run the process.

Start node access rules

Starting node is a special node, is the entrance to the entire process, a process that only a start node.

Access rules starting node is to identify those who may initiate the process.

Access rules start node with other nodes is not the same, as shown below.

up-8d145f7c1456cd75bf43cf18c9fc49360a3.png

We can easily understand from the literal meaning of the name of the rule, how to bind staff can initiate to start node.

By organizational structure settlement

This section describes in detail each of the access rules in different scenarios of application, users can use a different access rules for different situations.

Intelligent terms of job

设置方法: 在下一个节点上的节点属性里,设置节点岗位。这是默认的投递规则,他是在下一个节点设置岗位时按照岗位计算. 他的计算方式,首先按照当前操作员的部门范围计算。如果该操作员部门下没有这个工作岗位的人员,CCBPM就会把当前操作员的部门级次提高一个级别,在寻找,依次计算。理解了这个算法,您就不难理解为什么,本部分的业务,只能让本部门的经理审批了.
up-276fb3c3bb3619c20bd99800617407659c6.png

举例说明:一个省机关下面有n个县,n个市,n个县. n个所. 一个所员受理人员的业务,只能让自己的所长审批,所长的业务只能投递到本区县的相关业务部分审批,而非其它区县业务部分审批。

这就是岗位的权限与部门权限的交叉形成的被投递的人员集合. 这就是CCBPM经常说的。

岗位:表示能做什么事情。部门: 表示能做那里的事情。岗位+部门: 表示一个操作员能做那里的那些事情。

按节点绑定的部门计算

设置方法:在当前节点上的节点属性里,设置节点岗位.

CCBPM会按照您指定的部门下面的人员,进行投递, 就是这个n个部门下面都可以接受这个工作. 这个类于发送邮件的按照邮件组进行发送。

up-e80d9e2b120e211b16af98dc577cbc72542.png

按节点绑定的人员计算:

节点绑定那些人员,该系统就会发送给这些人,如下图设置。

up-3dcf23b2d34e6331fe87b92be7d7a38ef82.png

按绑定的岗位与部门交集计算

设置方式:在节点岗位,节点部门都设置。

运行方式:CCBPM会取既具备此岗位集合的又具备此部门集合的人员,做为本节点的接受人员。

up-7db12555287bfd6590aa1a21808abbf6630.png

按绑定的岗位计算并且以绑定的部门集合为纬度

按指定节点的工作人员或者指定字段人员的岗位计算

应用场景:为一个单位设置一个设备维修流程,此单位下分好多部门,有一个IT部门负责计算机设备维修。每个部门的成员如果有设备维护的需要,首先填写一个单子向这个IT部门的受理人员发送详细的故障说明。IT受理人员接受到此请求后,根据情况发送到该发起人的部门领导那里去。

This is a simple three-step process, launch - "IT departments Accepted -" initiated by department heads for approval. The first step of junior officers initiated the second step is to accept IT staff Kong accepted. The third step of mid-level leadership for approval. It is calculated according to a specified node positions in the third node access rules. Because if calculated according to the post will be sent to the IT department manager for approval in the second step, rather than the promoters of the department manager for approval. The default is calculated by post by post on a node calculation, the current scenario is Yaoan specified node positions are calculated.

Settings: Set a node number in the receiving object, such as: 101.

Run: CCBPM in dealing with recipients, will be calculated according to their status on the specified node, rather than by the identity of a person on the steps of the calculation.

Other: in this way complement the calculated positions at.

Changelog: 2015/10/8 In order to be able to adapt as specified form field staff, especially support, you can also specify a form field as a process person.

For the original set of nodes is effective manner, if a setting field name, CCBPM form field value as it is received from the man.

Only post bound by computing

According to the binding posts on the compute nodes to the recipient, this removes the filter sector dimension.

Guess you like

Origin blog.51cto.com/14150825/2465920