WO2018214891A1 - 工作流审批节点按部门设置审批角色的方法 - Google Patents
工作流审批节点按部门设置审批角色的方法 Download PDFInfo
- Publication number
- WO2018214891A1 WO2018214891A1 PCT/CN2018/087921 CN2018087921W WO2018214891A1 WO 2018214891 A1 WO2018214891 A1 WO 2018214891A1 CN 2018087921 W CN2018087921 W CN 2018087921W WO 2018214891 A1 WO2018214891 A1 WO 2018214891A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- role
- approval
- department
- workflow
- user
- Prior art date
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
- G06Q10/103—Workflow collaboration or project management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/604—Tools and structures for managing or administering access control systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
- G06F21/6218—Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
- G06F21/629—Protecting access to data via a platform, e.g. using keys or access control rules to features or functions of an application
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06Q10/063—Operations research, analysis or management
- G06Q10/0631—Resource planning, allocation, distributing or scheduling for enterprises or organisations
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06Q10/063—Operations research, analysis or management
- G06Q10/0633—Workflow analysis
Definitions
- the invention relates to a method for setting and managing an approval node approval role in a workflow of a management software system such as ERP, in particular to a method for a workflow approval node to set an approval role according to a department.
- Role-based access control is one of the most researched and matured database rights management mechanisms in recent years. It is considered to be an ideal candidate to replace traditional mandatory access control (MAC) and autonomous access control (DAC). Traditional autonomous access control has high flexibility but low security. Forced access control is highly secure but too restrictive. Role-based access control combines both ease of management and reduces the complexity, cost, and probability of errors. Therefore, it has been greatly developed in recent years.
- the basic idea of role-based access control (RBAC) is to divide different roles according to different functional positions in the enterprise organization view, encapsulate the access rights of database resources in roles, and indirectly access database resources by being assigned different roles.
- the role-based permission control mechanism can manage the access rights of the system simply and efficiently, which greatly reduces the burden and cost of the system rights management, and makes the system rights management more in line with the business management specifications of the application system.
- the traditional role-based user rights management and workflow control methods adopt the "role-to-user one-to-many" association mechanism, and the "role” is group/class nature, that is, one role can simultaneously correspond to/associate multiple users.
- the role is similar to the concept of position/position/work type.
- the authorization of user rights under this association mechanism is basically divided into the following three forms: 1. As shown in Figure 1, the user is authorized directly. The disadvantage is that the workload is large and the operation is frequent. And trouble; the approval operation subject of the approval node in the approval process is the user, and the workflow approval node directly selects the employee/user as the approval subject.
- the role (class/group/post/work type) is authorized (a role can be associated with multiple users), the user obtains the permission through the role, and the approval operation subject is the group/class nature role; As shown in Figure 3, the above two methods are combined.
- both 2 and 3 need to authorize the role of the class/group nature, and the way of authorization and workflow control through the role of class/group/post/work type has the following disadvantages: 1.
- Difficulties in operation In the actual system use process, it is often necessary to adjust the user's authority during the operation process. For example, when dealing with employee permission changes, the employee rights associated with the role change, we cannot because of this Changes in employee permissions change the permissions of the entire role, because the role is also associated with other employees whose permissions have not changed. So in response to this situation, either create a new role to satisfy the employee whose permissions have changed, or directly authorize (disengage the role) from the employee based on the permission requirements.
- the above two processing methods not only require a long time for the role authorization in the case of a large number of role permissions, but also are easy to make mistakes, the user is cumbersome and troublesome to operate, and is also prone to errors resulting in loss to the system user.
- the workflow approval node directly selects the employee/user as the approval subject, or the new role is added to meet the requirements of the approval process.
- employee changes such as transfer, resignation, etc.
- all the processes involved in the employee must be adjusted accordingly, especially for company management personnel, which involves more approval processes and process adjustments. Large amount, complicated, easy to make mistakes or omissions, affecting the normal operation of the company, and even causing unpredictable losses.
- the new role involves the creation, association, and authorization of the role. Especially in the case of a large number of roles and a large number of users associated with the role, it is difficult to remember which users are associated with the role.
- the object of the present invention is to overcome the deficiencies of the prior art, and to provide a method for a workflow approval node to set an approval role according to a department, and only need to select a corresponding department when setting an approval role, and the operation is convenient.
- the object of the present invention is achieved by the following technical solutions:
- the workflow approval node sets the approval role by department, including: creating the department and role included in the system organization structure; setting the department supervisor role of each department;
- the approval node displays the candidate department when setting; when selecting one or more departments from the candidate department, the department supervisor role of the department acts as the approval role of the approval node.
- each role is an independent individual, not a group/class.
- One role can only associate a unique user at a time, and one user associates one or more roles.
- the method for generating the workflow includes: constructing a three-layer mechanism model of user-role-permission, wherein: a role layer: an operation subject of process approval in a workflow is a role, and each role is an independent individual, instead Group/class, a role can only be associated with a unique user in the same period, and a user is associated with one or more roles; privilege layer: consists of the permissions required for workflow execution, permissions are directly delegated to the role; user layer: user The approval task in the workflow is determined by the associated role, and the approval operation is performed with the permission of the associated role; the workflow is controlled by the three-layer structure model, and an approval process includes a start node, at least one approval node, and an end node.
- start node approval process start
- approval node approval authority authorization (or setting) for the corresponding approval role
- end node approval process end
- user determines the approval task to be processed according to its associated role, and according to The permissions of the associated role are approved.
- a role with workflow initiating permissions can initiate/apply/submit a workflow as a submitting role.
- the role belongs to a department, and the role is authorized according to the working content of the role.
- the name of the role is unique under the department, and the number of the role is unique in the system.
- the user when the user moves across the department, the user is associated with the role in the original department, and the user is associated with the role in the new department.
- the user determines the authority by its association with the role, one employee corresponds to one user account, and one user account corresponds to one employee.
- the display form of the candidate department includes a list, an organizational structure tree diagram, and an organizational structure diagram.
- the workflow approval node sets the approval role by department, including: creating the department and role included in the system organization structure; setting the department supervisor role of each department; selecting (or setting) to set the approval role by department;
- the candidate node is displayed when the approval node of the workflow is set; when one or more departments are selected from the candidate department, the department supervisor role of the department serves as the approval role of the approval node.
- the beneficial effects of the present invention are as follows: (1) the system workflow setting personnel only need to select the corresponding department when setting the approval role, and the department supervisor role of the department is the approval role, even if the department supervisor role of the department changes, The current department head role of the department is the approval role, and there is no need to reset the approval role. The operation is convenient and not easy to make mistakes.
- the employee of the company when the employee of the company takes time off, it needs the approval of the administrative department.
- the department supervisor role of the administrative department is the approval role
- the employee corresponding to the department's supervisor role is obtained through the supervisor role of the department. Approve the task and approve it according to the relevant authority of the department's supervisor role. It is not necessary to select a specific employee for approval setting.
- the operation is simple and convenient.
- the department head of the administrative department changes from role A to role B, the role B corresponds.
- the staff approves and does not need to re-set the approval role.
- the main body of the approval operation in the workflow is the role, and the role is an independent individual rather than a traditional group/class role. Even if employee/user changes occur (such as transfer, resignation, etc.), the employee only needs to be re-established. Linked to the new role, or the employee approval authority changes, the role of the role approval authority can be adjusted, no need to reset / adjust the process, easy to set up, no mistakes or omissions, will not affect the normal operation of the enterprise, greatly improved The reliability of the workflow.
- the role of the nature of the post number is the approval authority of the approval link node. The user determines which approval tasks are available through the role. The user can approve the operation by associating the role permissions; the understanding is clear and simple, and the nature of each post number/station number
- the role is the smallest unit of the work subject, and this application can be well satisfied for each role's different requirements for approval.
- the role of the application is a one-to-one relationship to the user.
- a role can only be associated with a unique user at the same time. The advantage of this is that as long as the user is associated with the role, the user can obtain the associated role (ie, the user obtains the associated role). Permissions), and the role's permission changes are much less than the user permissions in the traditional mechanism.
- the number of roles of the nature of the independent body (the nature of the post number/station number) is small. Although the employee turnover is large, the change of the post number/station number is small (even if there is no change in a certain period of time, that is, the role does not change), This will greatly simplify the user's rights management and reduce the overhead of the system.
- the operation of dynamic management, on-the-job adjustment, etc. is simple and convenient, high in efficiency and high in reliability: the application of the entry/departure/admission in the approval process is simple, and the operation subject of the approval of the workflow is the role, when the employee/user There is no need to reset the approval process when the change occurs (the user only needs to cancel or associate the role: the user who is no longer in the role of the job number/station number cancels the role association and takes over the role of the job number/station number. If the user is associated with the role of the job number, the user associated with the role automatically obtains the related tasks and permissions of the role in the approval workflow, without resetting the approval workflow or reauthorizing the roles in the workflow. , greatly improving the efficiency, security and reliability of process settings.
- Zhang San is no longer working as a “buyer 3”, Zhang San cancels the association with the role; Li Si took over as “Purchaser 3”
- Li Si is associated with the role, and Li Si automatically obtains the approval task and approval authority for the role of “Purchase 3” in the approval process.
- the traditional rights management mechanism defines the role as a group, a job type, a class, etc.
- the role is a one-to-many relationship with the user. In the actual system use process, it is often necessary to perform the user's authority during the operation process. Adjustments, for example, when the employee permissions are changed, the permissions of an employee associated with the role change. We cannot change the permissions of the entire role because of the change of the individual employee permissions, because the role is also associated with other permissions. Staff. So in response to this situation, either create a new role to satisfy the employee whose permissions have changed, or directly authorize (disengage the role) from the employee based on the permission requirements.
- the above two processing methods not only require a long time for the role authorization in the case of a large number of role permissions, but also are easy to make mistakes, the user is cumbersome and troublesome to operate, and is also prone to errors resulting in loss to the system user.
- the role since the role is an independent individual, the role permission can be changed to achieve the goal.
- the method of the present application seems to increase the workload when the system is initialized, it can be made by copying and the like to make the role or authorization more efficient than the traditional group-based role, because the role of the group is not considered.
- the application scheme will make the permission setting clear and clear; especially after the system is used for a period of time (the user/role authority changes dynamically), the application scheme can greatly improve the system usage for the system user.
- the efficiency of the rights management makes the dynamic authorization simpler, more convenient, clearer and clearer, and improves the efficiency and reliability of the permission setting.
- the traditional group-based role authorization method is error-prone, and the method of the present application greatly reduces the probability of authorization errors, because the method of the present application only needs to consider the role as an independent individual, without considering the traditional method to associate the role of the group. What are the commonalities of multiple users? Even if the authorization error occurs, it only affects the user associated with the role, while the traditional group-based role affects all users associated with the role. Even if a permission authorization error occurs, the correction method of the present application is simple and short, and the traditional group-type role needs to consider the commonality of all users associated with the role when correcting the error, and not only the modification when there are many function points. Troublesome, complicated, very error-prone, and in many cases only new roles can be created.
- the method of the present application is as follows: the transferred user associates several roles.
- the user When adjusting the post, the user is first unlinked from the role in the original department (the canceled roles can be re-associated to other users), and then Associate users with roles in the new department. The operation is simple and will not go wrong.
- FIG. 1 is a schematic diagram of a manner in which a system directly authorizes a user in the background art
- FIG. 2 is a schematic diagram of a manner in which a system authorizes a group/class role in the background art
- FIG. 3 is a schematic diagram of a manner in which a system directly authorizes a user and authorizes a group/class role role in the background art
- FIG. 4 is a flow chart of a method for setting a approval role by a workflow approval node according to a department in the present invention
- Figure 5 is a schematic view of a workflow in the present invention.
- FIG. 6 is still another flow chart of a method for a workflow approval node to set an approval role according to a department in the present invention.
- the workflow approval node sets the approval role by department, including: creating departments and roles included in the system organization structure.
- Role definition The role does not have the nature of group/class/category/post/job/work, but a non-collection nature, the role is unique, the role is an independent independent entity; in the enterprise application is equivalent Job number (The job number here is not a post, one post may have multiple employees at the same time, and one job number can only correspond to one employee at the same time).
- a company system can create the following roles: general manager, deputy general manager 1, deputy general manager 2, Beijing sales manager, Beijing sales manager, Beijing sales manager, Shanghai sales engineer 1, Shanghai sales Engineer 2, Shanghai Sales Engineer 3, Shanghai Sales Engineer 4, Shanghai Sales Engineer 5...
- general manager deputy general manager 1, deputy general manager 2, Beijing sales manager, Beijing sales manager, Shanghai sales engineer 1, Shanghai sales Engineer 2, Shanghai Sales Engineer 3, Shanghai Sales Engineer 4, Shanghai Sales Engineer 5...
- Zhang San serves as the company's deputy general manager 2, and also serves as a sales manager in Beijing, then Zhang The three roles to be associated are Deputy General Manager 2 and Beijing Sales Manager. Zhang San has the rights to these two roles.
- roles are group/class/post/position/work type, and one role can correspond to multiple users.
- the concept of "role" in this application is equivalent to the post number/station number, and is similar to the role in the film and television drama: a character can only be played by one actor at the same time (childhood, juvenile, middle-aged). And an actor may be decorated with multiple angles.
- Each role is a separate entity, not a group/class.
- a role can only be associated with a unique user at the same time, and a user is associated with one or more roles.
- the role belongs to the department, and the role is authorized according to the work content of the role; the role is composed of a name and a number, the name of the role is unique under the department, and the number of the role is unique in the system.
- the user When the user moves across departments, the user is associated with the role in the original department, and the user is associated with the role in the new department. After the role is created, you can associate the role in the process of creating the user, or you can associate it at any time after the user is created. After the user associates the role, the relationship with the role can be released at any time, and the relationship with other roles can be established at any time.
- the user determines the authority through its association with the role, one employee corresponds to one user account, and one user account corresponds to one employee.
- the candidate department is displayed when the workflow's approval node is set.
- the display form of the candidate department includes a list, an organizational structure tree diagram, and an organizational structure diagram.
- the method for generating the workflow includes: constructing a three-layer mechanism model of user-role-permission, wherein: a role layer: an operation subject of process approval in a workflow is a role, and each role is an independent individual. Instead of a group/class, a role can only be associated with a unique user at the same time, and a user is associated with one or more roles; the privilege layer: consists of the permissions required for workflow execution, and the permissions are directly delegated to the role; the user Layer: The user determines the approval task in the workflow through the associated role, and performs the approval operation with the permission of the associated role.
- the workflow is controlled by the three-layer structure model.
- One approval process includes a start node and at least one approval node.
- start node initiate/subscribe/submit workflow as the start node, or start node as the first approval node
- approve node approve authority (or set) for the corresponding approval role
- end node The approval process flow ends when the approval process flow goes to this node, and the end node does not approve For; or approval to a node as the last end node, the end node requires approval operation; user to determine the required approval tasks associated with processing according to its role and operating under the authority of the role approval associated.
- the department head role of the department serves as the approval role of the approval node.
- a company includes the administrative department and the sales department.
- the sales department has the role A, the role B, and the role C.
- the administrative department has the role D, the role E, and the role F.
- the role A is the department head of the sales department
- the role D is The department head role of the Department of Administration. All the company's leave requests need to be approved by the administrative department.
- the setting of the approval node for the leave workflow includes the following steps: creating the sales department and the administration department.
- the sales department has the role A, the role B and the role C.
- the administrative department has the role D. Role E and role F.
- the role A is set to the department supervisor role of the sales department, and the role D is set to the department supervisor role of the administration department.
- the candidate department includes the sales department and the administration department.
- the administrative department is selected. At this time, the department head of the administrative department acts as the approver of the node, that is, the role D plays the approval role of the approval node.
- the role E is the new departmental supervisor role of the administrative department. At this time, the role E is the approval role of the approval node, and the approval role does not need to be reset.
- the workflow approval node sets the approval role by department, including: creating the department and role included in the system organization structure; setting the department supervisor role of each department; selecting (or setting) The setting of the approval role is performed in a departmental manner; the candidate department is displayed when the workflow approval node is set; and one or more departments are selected from the candidate department, and the department supervisor role of the department serves as the approval role of the approval node. .
Landscapes
- Engineering & Computer Science (AREA)
- Business, Economics & Management (AREA)
- Human Resources & Organizations (AREA)
- Strategic Management (AREA)
- Entrepreneurship & Innovation (AREA)
- Theoretical Computer Science (AREA)
- Economics (AREA)
- General Physics & Mathematics (AREA)
- Physics & Mathematics (AREA)
- Tourism & Hospitality (AREA)
- General Business, Economics & Management (AREA)
- Quality & Reliability (AREA)
- Operations Research (AREA)
- Marketing (AREA)
- Development Economics (AREA)
- Game Theory and Decision Science (AREA)
- Educational Administration (AREA)
- Health & Medical Sciences (AREA)
- Computer Hardware Design (AREA)
- Computer Security & Cryptography (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- General Health & Medical Sciences (AREA)
- Bioethics (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- Automation & Control Theory (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
Description
Claims (10)
- 工作流审批节点按部门设置审批角色的方法,其特征在于,包括:创建系统组织结构中所包含的部门及角色;设置各部门的部门主管角色;对工作流的审批节点进行设置时显示候选部门;从所述候选部门中选择一个或多个部门,则该部门的部门主管角色担任该审批节点的审批角色。
- 根据权利要求1所述的工作流审批节点按部门设置审批角色的方法,其特征在于,每个角色是独立的个体,而非组/类,同一时段一个角色只能关联唯一的用户,而一个用户关联一个或多个角色。
- 根据权利要求2所述的工作流审批节点按部门设置审批角色的方法,其特征在于,所述工作流的生成方法包括:构建用户-角色-权限的三层机构模型,其中:角色层:工作流中流程审批的操作主体为角色,每个角色是独立的个体,而非组/类,同一时段一个角色只能关联唯一的用户,而一个用户关联一个或多个角色;权限层:由工作流执行中所需要使用的权限构成,权限直接授权给角色;用户层:用户通过关联的角色确定工作流中的审批任务,并以关联角色的权限进行审批操作;利用三层结构模型对工作流进行控制,一个审批流程中包括一个开始节点、至少一个审批节点、一个结束节点,其中:开始节点:审批流程开始;审批节点:对相应的审批角色进行审批权限授权;结束节点:审批流程结束;用户根据其关联的角色确定所需处理的审批任务,并根据关联的角色的权限进行审批操作。
- 根据权利要求3所述的工作流审批节点按部门设置审批角色的方法,其特征在于,有工作流发起权限的角色才能作为提交角色发起/申请/提交工作流。
- 根据权利要求2所述的工作流审批节点按部门设置审批角色的方法,其特征在于,所述角色归属于部门,根据角色的工作内容对角色进行授权。
- 根据权利要求5所述的工作流审批节点按部门设置审批角色的方法,其特征在于,所述角色的名称在该部门下唯一,该角色的编号在系统中唯一。
- 根据权利要求5所述的工作流审批节点按部门设置审批角色的方法,其特征在于,所述用户跨部门调岗时,取消用户与原部门内的角色的关联,将用户与新部门内的角色进行关联。
- 根据权利要求2所述的工作流审批节点按部门设置审批角色的方法,其特征在于,所述用户通过其与角色的关联确定权限,一个员工对应一个用户账号,一个用户账号对应一个员工。
- 根据权利要求1所述的工作流审批节点按部门设置审批角色的方法,其特征在于,所述候选部门的显示形式包括列表、组织结构树形图、组织结构架构图。
- 工作流审批节点按部门设置审批角色的方法,其特征在于,包括:创建系统组织结构中所包含的部门及角色;设置各部门的部门主管角色;选择以按部门方式进行审批角色的设置;对工作流的审批节点进行设置时显示候选部门;从所述候选部门中选择一个或多个部门,则该部门的部门主管角色担任该审批节点的审批角色。
Priority Applications (8)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
AU2018274420A AU2018274420A1 (en) | 2017-05-23 | 2018-05-22 | Method for setting up approval role according to department by approval node in workflow |
EA201992753A EA201992753A1 (ru) | 2017-05-23 | 2018-05-22 | Способ настройки роли утверждения в соответствии с отделом в узле утверждения рабочего процесса |
EP18806921.5A EP3633567A4 (en) | 2017-05-23 | 2018-05-22 | PROCEDURE FOR SETTING UP AN APPROVAL ROLE ACCORDING TO DEPARTMENT BY AN APPROVAL NODE IN THE WORKFLOW |
BR112019024633-9A BR112019024633A2 (pt) | 2017-05-23 | 2018-05-22 | O método da função de aprovação do nó de aprovação do fluxo de trabalho por departamento |
CA3067666A CA3067666A1 (en) | 2017-05-23 | 2018-05-22 | Method for setting up approval role according to department by approval node in workflow |
US16/616,421 US20200143328A1 (en) | 2017-05-23 | 2018-05-22 | Method for setting up approval role according to department by approval node in workflow |
PH12019502615A PH12019502615A1 (en) | 2017-05-23 | 2019-11-21 | Method for setting up approval role according to department by approval node in workflow |
ZA2019/08441A ZA201908441B (en) | 2017-05-23 | 2019-12-18 | Method for setting up approval role according to department by approval node in workflow |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201710369528.XA CN107203870A (zh) | 2017-05-23 | 2017-05-23 | 工作流审批节点按部门设置审批角色的方法 |
CN201710369528.X | 2017-05-23 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2018214891A1 true WO2018214891A1 (zh) | 2018-11-29 |
Family
ID=59905409
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2018/087921 WO2018214891A1 (zh) | 2017-05-23 | 2018-05-22 | 工作流审批节点按部门设置审批角色的方法 |
Country Status (10)
Country | Link |
---|---|
US (1) | US20200143328A1 (zh) |
EP (1) | EP3633567A4 (zh) |
CN (2) | CN107203870A (zh) |
AU (1) | AU2018274420A1 (zh) |
BR (1) | BR112019024633A2 (zh) |
CA (1) | CA3067666A1 (zh) |
EA (1) | EA201992753A1 (zh) |
PH (1) | PH12019502615A1 (zh) |
WO (1) | WO2018214891A1 (zh) |
ZA (1) | ZA201908441B (zh) |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN110827002A (zh) * | 2019-11-11 | 2020-02-21 | 北京中电普华信息技术有限公司 | 一种基于工作流的审批方法及工作流引擎 |
CN114912901A (zh) * | 2022-05-31 | 2022-08-16 | 东风商用车有限公司 | 一种审批流程优化方法、装置、设备及存储介质 |
CN115660607A (zh) * | 2022-12-12 | 2023-01-31 | 平安银行股份有限公司 | 一种审批链自动生成方法、装置以及计算机存储介质 |
Families Citing this family (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN107203870A (zh) * | 2017-05-23 | 2017-09-26 | 成都牵牛草信息技术有限公司 | 工作流审批节点按部门设置审批角色的方法 |
CN107358093A (zh) * | 2017-07-11 | 2017-11-17 | 成都牵牛草信息技术有限公司 | 通过第三方字段对表单字段的字段值进行授权的方法 |
CN108428098A (zh) * | 2017-10-12 | 2018-08-21 | 平安科技(深圳)有限公司 | 员工自助离司方法、应用服务器及计算机可读存储介质 |
CN107862473A (zh) * | 2017-12-04 | 2018-03-30 | 山东浪潮通软信息科技有限公司 | 一种工作流的参与用户确定方法及装置 |
CN108833328B (zh) * | 2018-03-27 | 2021-03-02 | 博彦科技(上海)有限公司 | 云管理方法、装置、存储介质及处理器 |
TWI696968B (zh) * | 2018-03-30 | 2020-06-21 | 彰化商業銀行股份有限公司 | 交易授權設定系統 |
CN109308422A (zh) * | 2018-08-29 | 2019-02-05 | 北京航天云路有限公司 | 搭建面向企业的多级子账号系统及方法 |
CN109903016A (zh) * | 2019-02-26 | 2019-06-18 | 广东启动子信息科技有限公司 | 一种结合权限管理的流程引擎的实现方法及流程引擎系统 |
CN110782223A (zh) * | 2019-10-14 | 2020-02-11 | 浙江讯盟科技有限公司 | Oa系统的通用工作流装置及通用工作流实现方法 |
US11381563B1 (en) * | 2020-09-29 | 2022-07-05 | Parallels International Gmbh | Automated methods and systems for granting complex permissions |
CN115578079A (zh) * | 2022-12-07 | 2023-01-06 | 广东信通通信有限公司 | 一种电网领域的线路隐患管控、流程节点管理系统 |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN105094854A (zh) * | 2015-09-30 | 2015-11-25 | 北京恒华伟业科技股份有限公司 | 审批流程的配置方法及装置 |
CN106339850A (zh) * | 2015-07-17 | 2017-01-18 | 北京奇虎科技有限公司 | 一种合同审批流程的自动生成方法和装置 |
CN106600234A (zh) * | 2016-12-21 | 2017-04-26 | 湖南文理学院 | 一种快速流程审批方法 |
CN107203870A (zh) * | 2017-05-23 | 2017-09-26 | 成都牵牛草信息技术有限公司 | 工作流审批节点按部门设置审批角色的方法 |
Family Cites Families (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6088679A (en) * | 1997-12-01 | 2000-07-11 | The United States Of America As Represented By The Secretary Of Commerce | Workflow management employing role-based access control |
US20020026592A1 (en) * | 2000-06-16 | 2002-02-28 | Vdg, Inc. | Method for automatic permission management in role-based access control systems |
US20030220824A1 (en) * | 2002-05-21 | 2003-11-27 | Shou-Min Tseng | Enterprise organization operational flow management system |
US20090157463A1 (en) * | 2007-12-14 | 2009-06-18 | Morinville Paul V | Approver Identification Using Multiple Hierarchical Role Structures |
US20090182570A1 (en) * | 2008-01-16 | 2009-07-16 | Morinville Paul V | Automated Execution of Business Processes Using Two Stage State |
CN102468971A (zh) * | 2010-11-04 | 2012-05-23 | 北京北方微电子基地设备工艺研究中心有限责任公司 | 权限管理方法和装置、权限控制方法和装置 |
CN102708428A (zh) * | 2011-03-28 | 2012-10-03 | 祖东锋 | 一种企业管理系统控制方法 |
CN107103228B (zh) * | 2017-04-22 | 2021-02-02 | 成都牵牛草信息技术有限公司 | 基于角色对用户的一对一的权限授权方法和系统 |
CN107180334A (zh) * | 2017-04-29 | 2017-09-19 | 成都牵牛草信息技术有限公司 | 基于角色对用户一对一的工作流控制方法和系统 |
-
2017
- 2017-05-23 CN CN201710369528.XA patent/CN107203870A/zh active Pending
-
2018
- 2018-05-22 CA CA3067666A patent/CA3067666A1/en not_active Abandoned
- 2018-05-22 BR BR112019024633-9A patent/BR112019024633A2/pt unknown
- 2018-05-22 EP EP18806921.5A patent/EP3633567A4/en active Pending
- 2018-05-22 US US16/616,421 patent/US20200143328A1/en not_active Abandoned
- 2018-05-22 EA EA201992753A patent/EA201992753A1/ru unknown
- 2018-05-22 WO PCT/CN2018/087921 patent/WO2018214891A1/zh active Application Filing
- 2018-05-22 AU AU2018274420A patent/AU2018274420A1/en not_active Abandoned
- 2018-05-22 CN CN201810496006.0A patent/CN108764833B/zh active Active
-
2019
- 2019-11-21 PH PH12019502615A patent/PH12019502615A1/en unknown
- 2019-12-18 ZA ZA2019/08441A patent/ZA201908441B/en unknown
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN106339850A (zh) * | 2015-07-17 | 2017-01-18 | 北京奇虎科技有限公司 | 一种合同审批流程的自动生成方法和装置 |
CN105094854A (zh) * | 2015-09-30 | 2015-11-25 | 北京恒华伟业科技股份有限公司 | 审批流程的配置方法及装置 |
CN106600234A (zh) * | 2016-12-21 | 2017-04-26 | 湖南文理学院 | 一种快速流程审批方法 |
CN107203870A (zh) * | 2017-05-23 | 2017-09-26 | 成都牵牛草信息技术有限公司 | 工作流审批节点按部门设置审批角色的方法 |
Non-Patent Citations (1)
Title |
---|
See also references of EP3633567A4 * |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN110827002A (zh) * | 2019-11-11 | 2020-02-21 | 北京中电普华信息技术有限公司 | 一种基于工作流的审批方法及工作流引擎 |
CN110827002B (zh) * | 2019-11-11 | 2023-09-15 | 北京中电普华信息技术有限公司 | 一种基于工作流的审批方法及工作流引擎 |
CN114912901A (zh) * | 2022-05-31 | 2022-08-16 | 东风商用车有限公司 | 一种审批流程优化方法、装置、设备及存储介质 |
CN115660607A (zh) * | 2022-12-12 | 2023-01-31 | 平安银行股份有限公司 | 一种审批链自动生成方法、装置以及计算机存储介质 |
Also Published As
Publication number | Publication date |
---|---|
CA3067666A1 (en) | 2018-11-29 |
CN108764833A (zh) | 2018-11-06 |
PH12019502615A1 (en) | 2020-06-08 |
BR112019024633A2 (pt) | 2020-06-16 |
CN107203870A (zh) | 2017-09-26 |
ZA201908441B (en) | 2021-01-27 |
EP3633567A4 (en) | 2021-03-31 |
EP3633567A1 (en) | 2020-04-08 |
CN108764833B (zh) | 2023-04-07 |
AU2018274420A1 (en) | 2020-01-02 |
EA201992753A1 (ru) | 2020-07-15 |
US20200143328A1 (en) | 2020-05-07 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2018214891A1 (zh) | 工作流审批节点按部门设置审批角色的方法 | |
WO2018214890A1 (zh) | 工作流审批节点按角色设置审批角色的方法 | |
WO2018196876A1 (zh) | 基于角色对用户一对一的工作流控制方法和系统 | |
US20230419265A1 (en) | Method based on form fields for arranging examination and approval roles at workflow examination and approval nodes | |
WO2019011220A1 (zh) | 基于依据字段设置审批流程的方法 | |
WO2018210245A1 (zh) | 工作流及其审批节点的表单字段操作权限的设定方法 | |
WO2018224024A1 (zh) | 工作流审批节点高效审批方法 | |
WO2019007260A1 (zh) | 表单字段值操作权限授权方法 | |
WO2018205942A1 (zh) | 工作流审批节点按部门级别设置审批角色的方法 | |
WO2019007292A1 (zh) | 基于角色的表单操作权限授权方法 | |
WO2019029650A1 (zh) | 表单数据操作的审核方法 | |
WO2018192557A1 (zh) | 基于角色对用户的一对一的权限授权方法和系统 | |
WO2018219230A1 (zh) | 审批工作流的委托及其再委托方法 | |
WO2019011304A1 (zh) | 基于角色获取的表单数据的授权方法 | |
JP7318894B2 (ja) | 統計列表の操作権限の承認方法 | |
WO2019015656A1 (zh) | 一种系统派工方法 | |
WO2019029648A1 (zh) | 基于改进型rbac权限控制机制的审批任务转交方法 | |
WO2019015539A1 (zh) | 一种表单数据操作权限授权方法 | |
WO2019019981A1 (zh) | 系统中用户在信息交流单元的权限的设置方法 | |
WO2018224023A1 (zh) | 系统中员工登录其账户后的权限显示方法 | |
WO2019011162A1 (zh) | 快捷功能设置方法 | |
WO2019034023A1 (zh) | 审批者针对审批任务征询参考意见的方法 | |
WO2019029649A1 (zh) | 对使用者进行审批流程及其审批节点授权的方法 | |
WO2018205940A1 (zh) | 基于角色对用户的一对一的组织结构图生成及应用方法 | |
WO2019011255A1 (zh) | 通过第三方字段对表单字段的字段值进行授权的方法 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 18806921 Country of ref document: EP Kind code of ref document: A1 |
|
DPE1 | Request for preliminary examination filed after expiration of 19th month from priority date (pct application filed from 20040101) | ||
NENP | Non-entry into the national phase |
Ref country code: DE |
|
REG | Reference to national code |
Ref country code: BR Ref legal event code: B01A Ref document number: 112019024633 Country of ref document: BR |
|
ENP | Entry into the national phase |
Ref document number: 3067666 Country of ref document: CA |
|
ENP | Entry into the national phase |
Ref document number: 2018274420 Country of ref document: AU Date of ref document: 20180522 Kind code of ref document: A |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2018806921 Country of ref document: EP |
|
ENP | Entry into the national phase |
Ref document number: 2018806921 Country of ref document: EP Effective date: 20200102 |
|
ENP | Entry into the national phase |
Ref document number: 112019024633 Country of ref document: BR Kind code of ref document: A2 Effective date: 20191122 |