WO2018214890A1 - Procédé à base de rôle pour configuration de rôle d'approbation pour nœud d'approbation de flux de travail - Google Patents

Procédé à base de rôle pour configuration de rôle d'approbation pour nœud d'approbation de flux de travail Download PDF

Info

Publication number
WO2018214890A1
WO2018214890A1 PCT/CN2018/087920 CN2018087920W WO2018214890A1 WO 2018214890 A1 WO2018214890 A1 WO 2018214890A1 CN 2018087920 W CN2018087920 W CN 2018087920W WO 2018214890 A1 WO2018214890 A1 WO 2018214890A1
Authority
WO
WIPO (PCT)
Prior art keywords
role
approval
workflow
user
roles
Prior art date
Application number
PCT/CN2018/087920
Other languages
English (en)
Chinese (zh)
Inventor
陈达志
Original Assignee
成都牵牛草信息技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 成都牵牛草信息技术有限公司 filed Critical 成都牵牛草信息技术有限公司
Publication of WO2018214890A1 publication Critical patent/WO2018214890A1/fr

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/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
    • 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

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 an ERP, in particular to a method for setting an approval role by a workflow approval node according to a role.
  • 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 purpose of the present invention is to overcome the deficiencies of the prior art, and to provide a method for setting an approval role by a workflow approval node according to a role, and only need to select a corresponding role when setting an approval role, and the operation is convenient.
  • the workflow approval node sets the role of the approval role by role, including: creating a role included in the system organization structure; displaying the candidate role when setting the workflow approval node; One or more roles are selected from the candidate roles as an approval role for the 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 character includes one or more of a list, an organizational structure tree diagram, and an organizational structure diagram.
  • the workflow approval node sets the role of the approval role by role, including: creating the role contained in the system organization structure; selecting (or setting) to set the approval role by role; displaying candidates when setting the workflow approval node Role; select one or more roles from the candidate roles as the approval role for the node.
  • the beneficial effects of the present invention are as follows: (1) The system workflow setting personnel only need to select the corresponding role as the approval role when setting the approval role, and it is not necessary to select a specific user, even if the user associated with the role changes, it is not required. Resetting the approval role is easy and error-free.
  • the administrative department of the company has role A and role B. If role A is the department supervisor role of the administrative department, when performing the workflow approval setting for leave, simply select role A as the approval role instead of selecting role A. The user, even if the user associated with role A is changed from Zhang San to Li Si, does not need to re-approve the role setting.
  • 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, separation, etc.), only new employees are required. Re-associate to the role in the approval process; or change the employee approval authority, adjust the role approval authority in a targeted manner, no need to reset/adjust the process, easy to set up, no mistakes or omissions, no impact on the enterprise Normal operation greatly improves 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 an approval role by a workflow approval node according to a role 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 setting an approval role by a workflow approval node according to a role in the present invention.
  • the workflow approval node sets the role of the approval role by role, including: creating a role included in the system organization structure. For example, create role a, role b, role c, and role d.
  • 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 role is displayed when the workflow's approval node is set.
  • the display form of the candidate character includes one or more of a list, an organizational structure tree diagram, and an organizational structure diagram. For example, when selecting an approval node, role a, role b, role c, and role d are displayed for selection.
  • 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.
  • One or more roles are selected from the candidate roles as approval roles. For example, if you select role a as the approval role, you can directly select role a as the approval role.
  • the administrative department of a company has role A, role B, role C, role D, role E, and role F. All company leave requires role A to approve.
  • the setting of the approval node of the leave workflow includes the following steps: creating a role A, role B, role C, role D, role E, and role F.
  • the candidate roles include role A, role B, role C, role D, role E, and role F (if there are other roles in the system organization structure, Show these roles).
  • Zhang San obtains the approval task and approves it.
  • the workflow approval node sets the role of the approval role by role, including: creating a role included in the system organization structure; selecting (or setting) to perform the role setting by the role mode; The candidate role is displayed when the approval node of the workflow is set; one or more roles are selected from the candidate roles as the approval role of the node.

Landscapes

  • Business, Economics & Management (AREA)
  • Human Resources & Organizations (AREA)
  • Engineering & Computer Science (AREA)
  • Strategic Management (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Economics (AREA)
  • General Business, Economics & Management (AREA)
  • Marketing (AREA)
  • Operations Research (AREA)
  • Quality & Reliability (AREA)
  • Tourism & Hospitality (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Data Mining & Analysis (AREA)
  • Development Economics (AREA)
  • Educational Administration (AREA)
  • Game Theory and Decision Science (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

L'invention concerne un procédé à base de rôle pour configurer un rôle d'approbation pour un nœud d'approbation de flux de travail. Le procédé consiste à : créer des rôles présents dans une structure d'organisation de système ; afficher des rôles candidats lors de la configuration d'un nœud d'approbation de flux de travail ; et sélectionner un ou plusieurs rôles parmi les rôles candidats en tant que rôle d'approbation du nœud. Selon la présente invention, un personnel de configuration de flux de travail de système a seulement besoin de sélectionner un rôle particulier lors de la configuration d'un rôle d'approbation, sans faire attention aux utilisateurs concrets ; il n'est pas nécessaire d'établir de nouveau un rôle d'approbation même si l'utilisateur associé au rôle est changé, l'exploitation est pratique, et il est peu probable de faire des erreurs. Les rôles qui sont des individus indépendants servent de corps principal d'une opération d'approbation de flux de travail ; un nouvel employé est associé à un rôle dans le flux d'approbation s'il y a un changement d'employé/utilisateur ; ou si l'autorité d'approbation d'un certain employé est modifiée, il est juste nécessaire d'ajuster l'autorité d'approbation du rôle de façon ciblée au lieu de réinitialiser/d'ajuster le flux ; et la configuration est pratique, et la fiabilité de flux de travail est améliorée considérablement.
PCT/CN2018/087920 2017-05-23 2018-05-22 Procédé à base de rôle pour configuration de rôle d'approbation pour nœud d'approbation de flux de travail WO2018214890A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710369876.7A CN107045675A (zh) 2017-05-23 2017-05-23 工作流审批节点按角色设置审批角色的方法
CN201710369876.7 2017-05-23

Publications (1)

Publication Number Publication Date
WO2018214890A1 true WO2018214890A1 (fr) 2018-11-29

Family

ID=59546636

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/087920 WO2018214890A1 (fr) 2017-05-23 2018-05-22 Procédé à base de rôle pour configuration de rôle d'approbation pour nœud d'approbation de flux de travail

Country Status (2)

Country Link
CN (2) CN107045675A (fr)
WO (1) WO2018214890A1 (fr)

Families Citing this family (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107045675A (zh) * 2017-05-23 2017-08-15 成都牵牛草信息技术有限公司 工作流审批节点按角色设置审批角色的方法
CN107665421A (zh) * 2017-09-08 2018-02-06 金蝶软件（中国）有限公司 单据审批方法、装置、存储介质和计算机设备
CN107493304B (zh) * 2017-09-30 2020-06-30 新奥（中国）燃气投资有限公司 一种授权管理平台及方法
CN109492989A (zh) * 2018-10-11 2019-03-19 平安科技（深圳）有限公司 审批流程构建方法、装置、计算机设备以及存储介质
CN109523444A (zh) * 2018-10-11 2019-03-26 昆山信高圣信息科技有限公司 一种组合大学生创业的信息处理方法和装置
CN109740834A (zh) * 2018-11-13 2019-05-10 平安科技（深圳）有限公司 工作流引擎控制方法、装置、计算机设备及存储介质
CN109615333A (zh) * 2018-12-13 2019-04-12 普元信息技术股份有限公司 云平台中基于抽屉模型实现流程逐级审批的系统及方法
CN109829700A (zh) * 2019-02-26 2019-05-31 广东启动子信息科技有限公司 一种权限管理方法及系统
CN109903016A (zh) * 2019-02-26 2019-06-18 广东启动子信息科技有限公司 一种结合权限管理的流程引擎的实现方法及流程引擎系统
CN109995768A (zh) * 2019-03-18 2019-07-09 网宿科技股份有限公司 一种服务器权限管理的方法及装置
CN110110976A (zh) * 2019-04-19 2019-08-09 一起住好房(北京)网络科技有限公司 一种提高流程审批系统角色管理效率的方法
CN110648111A (zh) * 2019-09-09 2020-01-03 杭州博联智能科技股份有限公司 基于工作流的审批任务处理方法、装置、电子设备、介质
CN110782224A (zh) * 2019-10-18 2020-02-11 杭州施强教育科技有限公司 工作流建立及审批节点自适配的方法和系统
CN112907013A (zh) * 2019-12-04 2021-06-04 广州凡科互联网科技股份有限公司 一种基于自定义流转的执行人选择方法
CN110990856A (zh) * 2019-12-06 2020-04-10 广东联晟通信科技有限公司 一种权限审核方法及系统
CN113128942A (zh) * 2019-12-30 2021-07-16 北京国双科技有限公司 可视化的工作流程处理方法及装置
CN111414591B (zh) * 2020-03-02 2024-02-20 中国建设银行股份有限公司 工作流管理的方法和装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140180754A1 (en) * 2005-07-12 2014-06-26 Open Text S.A. Workflow System and Method for Single Call Batch Processing of Collections of Database Records
CN105096030A (zh) * 2015-06-16 2015-11-25 阿里巴巴集团控股有限公司 企业审批事件的处理方法及装置
CN106485389A (zh) * 2015-09-01 2017-03-08 北京奇虎科技有限公司 审批流的动态更新方法和装置
CN107045675A (zh) * 2017-05-23 2017-08-15 成都牵牛草信息技术有限公司 工作流审批节点按角色设置审批角色的方法

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
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 成都牵牛草信息技术有限公司 基于角色对用户一对一的工作流控制方法和系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140180754A1 (en) * 2005-07-12 2014-06-26 Open Text S.A. Workflow System and Method for Single Call Batch Processing of Collections of Database Records
CN105096030A (zh) * 2015-06-16 2015-11-25 阿里巴巴集团控股有限公司 企业审批事件的处理方法及装置
CN106485389A (zh) * 2015-09-01 2017-03-08 北京奇虎科技有限公司 审批流的动态更新方法和装置
CN107045675A (zh) * 2017-05-23 2017-08-15 成都牵牛草信息技术有限公司 工作流审批节点按角色设置审批角色的方法

Also Published As

Publication number Publication date
CN108734400A (zh) 2018-11-02
CN107045675A (zh) 2017-08-15

Similar Documents

Publication Publication Date Title
WO2018214890A1 (fr) Procédé à base de rôle pour configuration de rôle d'approbation pour nœud d'approbation de flux de travail
WO2018214891A1 (fr) Procédé de configuration d'un rôle d'approbation en fonction d'un service au moyen d'un nœud d'approbation dans un flux de travail
WO2018196876A1 (fr) Système et procédé de commande de flux de travaux basés sur une correspondance biunivoque entre des rôles et des utilisateurs
WO2018210248A1 (fr) Procédé basé sur des champs de formulaire permettant d'organiser des rôles d'examen et d'approbation sur des nœuds d'examen et d'approbation de flux de travail
WO2019011220A1 (fr) Procédé d'établissement d'une procédure d'approbation basée sur des champs de base
WO2018210245A1 (fr) Procédé de réglage d'autorité d'opération de champ de formulaire d'un flux de travail, et procédé de réglage d'autorité d'opération de champ de formulaire d'un nœud d'approbation
WO2018224024A1 (fr) Procédé d'approbation efficace pour noeud d'approbation de flux de travail
WO2018205942A1 (fr) Procédé de configuration de rôles d'approbation en fonction de niveaux de services sur des nœuds d'approbation de flux de travail
WO2018214889A1 (fr) Procédé basé sur une contresignature permettant de configurer un nœud d'approbation dans un processus d'approbation
WO2019029650A1 (fr) Procédé de vérification d'opération de données de formulaire
WO2019007260A1 (fr) Procédé d'autorisation de permissions d'exploitation de valeurs de champ de formulaire
WO2019007292A1 (fr) Procédé d'octroi d'autorisation d'opération de formulaire à base de rôle
WO2018219230A1 (fr) Attribution de confiance de flux de travail d'approbation et procédé de ré-attribution de confiance
WO2019011304A1 (fr) Procédé basé sur l'acquisition de rôles pour autoriser des données de formulaire
WO2018192557A1 (fr) Procédé et système d'octroi d'autorisation basés sur une correspondance biunivoque entre des rôles et des utilisateurs
WO2018224023A1 (fr) Procédé permettant d'afficher une autorisation après qu'un employé se connecte à un compte de ce dernier dans un système
WO2019029648A1 (fr) Procédé de transfert de tâche d'approbation basé sur un mécanisme de droit rbac amélioré
WO2019015539A1 (fr) Procédé d'autorisation d'une autorité d'exploitation de données de formulaire
WO2019029649A1 (fr) Procédé d'autorisation de processus d'approbation et de nœuds d'approbation associés pour un utilisateur
WO2019034022A1 (fr) Procédé de réglage de droit de visualisation de registre d'exploitation sur la base d'une période de temps
WO2019011162A1 (fr) Procédé de définition de fonction de raccourci
WO2018205940A1 (fr) Procédé de génération de diagramme de structure organisationnelle basé sur une correspondance bi-univoque entre des rôles et des utilisateurs, et procédé d'application
WO2019029502A1 (fr) Procédé d'autorisation d'opérateur d'autorisation dans un système
WO2019001322A1 (fr) Procédé d'autorisation de menu basé sur un rôle
WO2019007261A1 (fr) Procédé d'obtention d'une valeur de champ d'un champ de propriété de personnage dans un formulaire

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: 18806321

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

122 Ep: pct application non-entry in european phase

Ref document number: 18806321

Country of ref document: EP

Kind code of ref document: A1