CN111242567A

CN111242567A - Authority control method of workflow node

Info

Publication number: CN111242567A
Application number: CN201911425990.2A
Authority: CN
Inventors: 周群辉; 刘远荣
Original assignee: Shenzhen Idreamsky Technology Co ltd
Current assignee: Shenzhen Idreamsky Technology Co ltd
Priority date: 2019-12-31
Filing date: 2019-12-31
Publication date: 2020-06-05
Anticipated expiration: 2039-12-31
Also published as: CN111242567B

Abstract

The application provides a method for controlling the authority of a workflow node, which comprises the following steps: receiving task items; the task item corresponds to a plurality of nodes; receiving login information sent by a terminal, and determining a first node corresponding to the login information from the plurality of nodes; acquiring a data field of the first node and an authority rule table of the first node or an authority rule group table of the first node; determining a display field corresponding to the first node from the data field according to the authority rule table of the first node or the authority rule group table of the first node; and sending the display field corresponding to the first node to the terminal. The method can flexibly configure the data authority of each node in the workflow according to the user requirements, improves the process processing efficiency and improves the safety of the process data.

Description

Authority control method of workflow node

Technical Field

The application relates to the technical field of information processing, in particular to a method for controlling authority of workflow nodes.

Background

An office automation system is a system for managing daily office work, such as daily various process approval jobs. The method has the function of improving the overall management operation level in a software mode.

The node data authority in the process approval work is specified by a system, and two setting modes are usually provided, wherein one setting mode is that a processor can only see the current processing node and cannot see the data of other nodes; another way to set up this is that all node data in the process is visible to the handler.

When the setting mode that a processor can only see the current processing node is adopted, the current processor cannot see the data of other nodes, so that the normal approval process cannot be completed; when all node data in the process is visible to a processor, the information propagation range is expanded, and information leakage is easily caused.

Disclosure of Invention

In order to overcome the defects of the prior art, the invention aims to provide the authority control method of the workflow node, which can flexibly configure the data authority of each node in the workflow according to the user requirement, thereby improving the process processing efficiency and the safety of the process data.

In a first aspect, the present application provides a method for controlling authority of a workflow node, including:

receiving task items; the task item corresponds to a plurality of nodes;

receiving login information sent by a terminal, and determining a first node corresponding to the login information from the plurality of nodes;

acquiring a data field of the first node and an authority rule table of the first node or an authority rule group table of the first node;

determining a display field corresponding to the first node from the data field according to the authority rule table of the first node or the authority rule group table of the first node;

sending a display field corresponding to the first node to the terminal

In one possible implementation, before the receiving the task item, the method further includes:

receiving a first operation of a user;

and setting authority rules of a plurality of nodes in the task item in response to a first operation of a user.

In a possible implementation manner, the permission rule table of the first node includes at least one permission rule;

the determining, according to the authority rule table of the first node, a display field corresponding to the first node from the data field specifically includes:

and sequentially judging whether the at least one authority rule is established, and determining the display field according to the first established authority rule in the at least one authority rule.

In a possible implementation manner, the permission group table of the first node includes at least one permission rule group, and the permission rule group includes at least one permission rule;

the determining, according to the permission rule group table of the first node, a display field corresponding to the first node from the data field specifically includes:

sequentially judging whether the at least one authority rule group is established, and determining the display field according to a first established authority rule group in the at least one authority rule group; and when all the authority rules in the authority rule group are established, the authority rule group is established.

In a possible implementation manner, the determining the display field according to a first established authority rule in the at least one authority rule specifically includes:

determining a control field from the data field according to a first established authority rule in the at least one authority rule; wherein the control field is invisible to the first node;

and determining the display field according to the data field and the control field.

In a possible implementation manner, the determining the display field according to a first established permission rule group in the at least one permission rule group specifically includes:

determining a control field from the data field according to a first established authority rule group in the at least one authority rule group; wherein the control field is invisible to the first node;

In a second aspect, the present application provides an apparatus for controlling authority of a workflow node, including:

a receiving unit for receiving task items; the task item corresponds to a plurality of nodes;

a first determining unit, configured to receive login information sent by a terminal, and determine a first node corresponding to the login information from the plurality of nodes;

a first obtaining unit, configured to obtain a data field of the first node and an authority rule table of the first node or an authority rule group table of the first node;

and the second determining unit is used for determining the display field corresponding to the first node from the data field according to the authority rule table of the first node or the authority rule group table of the first node.

And the sending unit is used for sending the display field corresponding to the first node to the terminal.

In one possible implementation, the apparatus further includes:

a receiving unit, configured to receive a first operation of a user;

and the processing unit is used for responding to the first operation of the user and setting authority rules of a plurality of nodes in the task item.

In a third aspect, the present application provides an authority control device, comprising: one or more processors, one or more memories, transceivers; the one or more memories are coupled to the one or more processors and the one or more memories are configured to store computer program code comprising computer instructions which, when executed by the one or more processors, perform a method of controlling authority of a workflow node as in any one of the possible implementations of any of the aspects.

In a fourth aspect, the present application provides a computer storage medium characterized by computer instructions that, when executed, perform a method according to any one of the possible implementation manners of any one of the aspects.

The method can flexibly configure the data authority of each node in the workflow according to the user requirements, improves the process processing efficiency and improves the safety of the process data.

Drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below.

Wherein:

fig. 1 is a schematic network architecture diagram of a method for controlling authority of a workflow node according to an embodiment of the present application;

fig. 2 is a flowchart of an authority control method for a workflow node according to an embodiment of the present application;

FIG. 3 is a flow of sales contract signing provided by an embodiment of the present application;

fig. 4 is an authority setting operation interface provided in the embodiment of the present application;

5-6 are an access control setting interface provided by an embodiment of the present application;

fig. 7 is a diagram of an apparatus for controlling authority of a workflow node according to an embodiment of the present application;

Detailed Description

In order to make the technical solutions of the present invention better understood, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

It should be further understood that the term "and/or" as used in this specification and the appended claims refers to and includes any and all possible combinations of one or more of the associated listed items.

The invention provides a workflow node data authority control method, which comprises the steps of setting data authority of each node in a workflow; receiving task items; acquiring a designated node according to the login information; the login information comprises a login user name and a login password; acquiring the appointed node data field and the appointed node authority rule table or the node authority rule group list; and acquiring a display field in the data field of the designated node according to the data field of the designated node and the authority rule table of the designated node or the authority rule group list of the designated node.

The method can flexibly configure the data authority of each node in the workflow according to the user requirements, improves the process processing efficiency and ensures the information safety.

First, a network architecture diagram of an authority control method of a workflow node provided in an embodiment of the present application is introduced. As shown in fig. 1, the network architecture 100 includes a terminal 101 and a server 102. Wherein:

the terminal 101 may be implemented as a smartphone, a computer, a Personal Digital Assistant (PDA), or the like.

Here, the terminal is installed with a client. The user can view and/or process the node tasks in the workflow through the client.

The workflow is a workflow, and the main problem solved by the workflow is that in order to complete a transaction or task, a group of related subtasks, namely node tasks, need to be completed according to a certain procedure, each node is assigned with at least one handler, and the handler can view and/or process the node tasks through a client in a terminal.

Specifically, the client may include: an application running locally, a function running on a Web browser (also called Web App), an applet embedded in an email, an applet embedded in client software for instant messaging (e.g. WeChat), and a function embedded in another application (e.g. WeChat) (e.g. WeChat public number), etc. For the client, the server 102 needs to run a corresponding server-side program to provide a corresponding service, such as a database service, data calculation, decision execution, and the like.

The server provides computing or application services for other devices in the network.

As shown in fig. 2, the method may include:

s201, setting data authority of each node in the workflow.

In each node of the workflow, a fixed processor is provided, and each node can receive user operation to set the authority of the node, namely, set the authority of the data field of the node, and clearly determine which data fields of each node are visible, which data fields are invisible and which data fields are editable, and can set some data fields as required items, such as non-filing and non-submitting.

Wherein, the data field is the input information attribute in the form. Wherein, the form is an information form that the node handler needs to process.

For example, the form may be as shown in Table 1 below:

TABLE 1

Product name

Reexamination product

Reason for review

The data fields in table 1 include "product name", "review product", and "review reason".

The method for setting the data authority of each node in the workflow comprises the following steps:

1. and designing a workflow template.

The work flow template comprises an approval flow, an reimbursement flow, a leave-asking flow, an article application flow, a sale contract signing flow and the like. Each workflow is comprised of at least one node, each node including at least one handler.

For example, in the flow of sales contract signing, a total of five nodes are included, each node having a fixed processor.

Referring to fig. 3, the flow is entered into for a sales contract, and the form data fields of the order contract include customer name, product model number, quantity, unit price, technical requirements, delivery date, and delivery location.

The processing person of the node 1 is a salesperson, after the server detects that the salesperson submits an order contract, the server control flow moves to the node 2, the processing person of the node 2 is a salesperson, the salesperson checks whether the order contract has a problem, after the server detects that the sales executive checks, the server control flow moves to the node 3, the processing person of the node 3 is a financial staff, the financial staff checks financial related information, after the server detects that the financial staff checks, the server control flow moves to the node 4, the processing person of the node 4 is a technician, the technician confirms technical related information, after the server detects that the technician checks, the server control flow moves to the node 5, the processing person of the node 5 is a general manager, the general manager comprehensively checks the order contract, and after the server detects that the general manager checks, the flow is finished.

2. And setting node data authority.

And setting the authority for the node data, namely setting the authority for the node data field. The rights can be visible, invisible, editable, non-editable, mandatory, and the like.

Here, a permission may be set to each node in the workflow, and a permission may be set to a certain data field or a plurality of data fields in the node.

For example, there is a workflow a including a node X, a node Y, and a node Z, where a form data field of the workflow a includes a field a/B/C/D/E/F// H/I, and a permission is set for the node Z, and fig. 4 is an operation interface for setting the permission for the node Z.

As shown in FIG. 4, the data field 401 is a form data field of workflow a, and includes fields A/B/C/D/E/F/H/I, the fields A/B/C/D/E/F/H/I are preceded by a selection box control 404, the selection box control 404 can receive a click operation, an odd number of click operations are to select the selection box, when the selection box 404 is selected, control over the field is indicated, and the field is referred to as a control field. Wherein the control fields may be set to visible, invisible, editable, non-editable, mandatory, and so on. As shown in fig. 4, i.e., the control of the field B/E/I is shown.

The authority control 402 may include at least one authority control rule, where each rule has four variables: reference objects, reference attributes, control actions, and observation targets.

Wherein the reference object is typically a certain node in the workflow.

The reference attribute is an attribute of the reference object and can be divided into a user class and a state class. The user class is a current login user, namely a current node handler; the state class may refer to before, during, or after processing.

Control actions include visible and invisible.

The observation target is determined with reference to the attribute.

As in fig. 4, the node is set with permissions through permissions control 402, where:

the first selection control 405 may receive a click operation to select a node, for example, node X or node Y or node Z may be selected.

The second selection control 406 can receive a click operation to select a handler.

The third selection control 407 can receive a click action selection control behavior, can select visible or invisible or editable or non-editable or mandatory, and the like.

The fourth selection control 408 can receive a click operation to select a node, e.g., node X or node Y or node Z can be selected

The fifth selection control 409 may receive a click operation selection state, and may select, for example, before, during, or after processing.

The sixth selection control 410 can receive a click action selection control behavior, can select visible or invisible or editable or non-editable or mandatory, and the like.

The newly added control 403 may receive a click operation add permission rule.

In one possible implementation, a permission rule may be set for a node.

Fig. 4 lists two entitlement rules for node Z. Wherein the content of the first and second substances,

the first is that the field B/E/I is invisible to the handler of the node Z, and if the current login user is the handler of the node Z, that is, the handler of the node Z cannot see the field B/E/I, the other field A/C/D/F/G/H can be seen. Here, the authority rule for the handler is referred to as a first type rule.

Second, when node Y is in process, the fields B/E/I are not visible to the handler of node Z.

Here, the authority rule for the state class is referred to as a second type rule.

It should be noted that, in this implementation, there may be a plurality of rules of the first type and a plurality of rules of the second type.

Exemplarily, if the first permission rule is established, the second permission rule is not executed continuously; if the first permission rule is not established, executing a second permission rule; if the second permission rule is not satisfied, the node Z does not set the data permission.

Aiming at the embodiment with a plurality of authority rules, the authority executing rule is that if the first authority rule is established, the second authority rule is not executed continuously; if the first permission rule is not established, executing a second permission rule; if the second authority rule is not established, the rules are traversed in sequence by analogy, if one authority rule is established, corresponding control operation is executed according to the control action and traversal is skipped, and if no established authority rule is found, the designated node is indicated to be not provided with the data authority.

The adding control 403 can receive the authority rule added by the user operation according to the actual requirement.

The above-described embodiment is only one implementation of the present application and should not be construed as limiting.

For a better understanding of the above embodiments, the present application will be explained in conjunction with specific embodiments.

In the process of signing a sales contract, the node 3 is a financial staff, the financial staff only need to check financial information and do not need to display other client information to the financial staff, and the authority of the node 3 can be set to be invisible to a client name, technical requirements, delivery date and a delivery place; the product model, quantity and unit price can be seen.

In particular, see the entitlement control settings interface of FIG. 5. The authority control setting interface is used for setting the authority of the node 3.

Specifically, the first rule of authority is that if the current logged-in user is the processor of node 3, the data fields of client name, technical requirements, delivery date and delivery location are not visible to the processor of node 3.

The second rule of authority is that if node 2 is in the state that the processor of node 2 is processing, then the data fields for client name, specification, delivery date and delivery location are not visible to the processor of node 3.

In another alternative implementation, two or more control actions may be set for a node.

The application provides another permission setting interface of the node Z.

The difference between this embodiment and the above embodiments is that this embodiment adds a group concept, where the authority rules include N groups of authority rules, each group of authority rules further includes m authority rules, and only one or none of the N groups of authority rules are established.

The method and the device can realize the setting of multiple authorities for a certain node.

Illustratively, as shown in FIG. 6, the entitlement control includes two sets of entitlement rules.

Wherein, the first group:

the first is that the field B/E/I is invisible to the handler of the node Z, and if the current login user is the handler of the node Z, that is, the handler of the node Z cannot see the field B/E/I, the other field A/C/D/F/G/H can be seen.

Second group:

Second, when node X is in process, the field B/E/I is not visible to the handler of node Z.

It should be noted that, only if each permission rule in each group is established, the group of permission rules is established, and if one permission rule is not established, the group of permission rules is not established.

In this implementation, if the first set of permission rules is true, the second set of permission rules is not executed continuously; if the first set of authority rules is not established, executing a second set of authority rules; if the second group of authority rules are not established, the node X does not set the data authority.

The newly added permission group control can receive user operation and add permission rule groups according to actual requirements.

According to the two permission rule setting methods, the data permission of each node in the workflow can be flexibly configured according to requirements, the process processing efficiency is improved, and the information safety is ensured.

And S202, receiving task items.

And S203, distributing node tasks and node authority rules.

The task items trigger the server to start the process operation, and the server determines the specific workflow according to the process starting node and distributes the workflow node task and the node data authority.

Each node task in the workflow has a fixed processor, and the server sends each node task to the terminal to prompt the user that a new node task needs to be processed.

And S204, the terminal receives the login operation of the user and acquires the login information of the user.

And S205, the terminal sends the login information of the user to the server.

The client of the terminal receives the login operation of the user and receives the login information of the user, wherein the login information can comprise a login user name and a login password of the user.

And the terminal sends the login information of the user to the server.

And S206, acquiring the designated node according to the login information of the user.

The server receives the login information of the user sent by the terminal, and confirms which specific node task handler of the workflow is according to the login information of the user, so as to determine the designated node.

S207, acquiring the designated node data field of the designated node and the designated node authority rule.

First, the server obtains all data fields of the designated node, and at the same time, the server obtains the authority rules of the designated node, namely, which data fields are visible and which data fields are invisible.

In an alternative embodiment, the rule list of the designated node is obtained according to the authority rule of the designated node, and the rule list includes the authority rule.

It should be noted that, in this implementation manner, if the first permission rule is established, the second permission rule is not continuously executed; if the first permission rule is not established, executing a second permission rule; if the second authority rule is not established, the rules are traversed in sequence by analogy, if one authority rule is established, corresponding control operation is executed according to the control action and traversal is skipped, and if no established authority rule is found, the designated node is indicated to be not provided with the data authority.

Illustratively, in the sales contract signing flow, it is assumed that the server acquires the data fields and rule list of the node 4.

As shown in table 2, which is a list of data fields for node 4:

TABLE 2

Client name
	Technical requirements
Date of delivery
	Delivery location
Product type
	Number of
Unit price of

As shown in table 3, table 3 is a rule list for node 4:

TABLE 3

Table 3 shows that the rule list of node 4 includes two entitlement rules.

Wherein, the first authority rule is that if the current login user is the processor of the node 4, the data fields of client name, technical requirement, delivery date, delivery place, product model number, quantity and unit price are invisible to the processor of the node 4; the second rule of authority is that if the currently logged-on user is the processor of node 4, the data fields of client name, technical requirements, delivery date, delivery location, product model number, quantity and unit price are not visible to the processor of node 4 after the processing of node 3 is completed.

Specifically, the designated node acquired by the server is the node 4, the server first determines whether a first permission rule is satisfied, and if the current login user is the processor of the node 4, the data fields of the client name, the technical requirement, the delivery date, the delivery place, the product model number, the quantity and the unit price are invisible to the processor of the node 2. If the first authority rule is established, the second authority rule is not seen.

The control field of the node 4 is obtained according to the first permission rule, as shown in table 4:

TABLE 4

Client name
	Date of delivery
Delivery location
	Product type
Number of
	Unit price of

The control fields include customer name, technical requirements, delivery date, delivery location, product model number, quantity, and unit price.

The server removes the control field from all data fields of the node 4 to obtain the display field, as shown in table 5:

TABLE 5

Technical requirements

As shown in table 5, the display field includes a specification field.

In another alternative embodiment, a rule group list for a given node is obtained according to the rule of the authority of the node, and the rule group list includes the rule authority.

In this implementation, if the first set of permission rules is true, the second set of permission rules is not executed continuously; if the first set of authority rules is not established, executing a second set of authority rules; and by analogy, if no one group of rule groups is not established, the designated node does not set the data authority.

Illustratively, in the sales contract signing flow, it is assumed that the server acquires the data fields and rule group list of the node 4.

Here, the data field list of the node 4 is the same as table 2, and is not described in detail here.

As shown in table 6, table 6 is a rule group list for node 4:

TABLE 6

Table 6 shows that the rule set list of node 4 includes two sets of permission rule sets.

Wherein group 1 group includes two entitlement rules, as shown in table 7:

TABLE 7

Group 2 includes a permission rule, as shown in Table 8:

TABLE 8

Control field	id	The node to which it belongs	Reference node	Reference attribute	Controlling behavior
						Product type	1	Node 4	Node 1	After treatment	It can be seen that

The first authority rule is that if the current login user is the processor of the node 4, after the node 1 finishes processing, the product type number field is visible to the processor of the node 4.

Since the designated node acquired by the server is the node 4, the currently logged-in user is the handler of the node 4, and it is assumed that the processing state of the node 3 acquired by the node 4 is in process.

The first entitlement rule for group 1 is specified by the fact that if the current logged-in user is the handler of node 4, then the data fields for client name, specification, delivery date, delivery location, product model number, quantity and unit price are not visible to the handler of node 4. The first entitlement rule holds.

The second rule of authority for group 1 is that if the node state of node 3 is processed, then the data fields for client name, specification, delivery date, delivery location, product model number, quantity and unit price are not visible to the processor of node 4. The second rule of authority holds.

The first permission rule and the second permission rule of the group 1 are both established, so that the rule of the group 1 is established, the server executes the permission setting of the group 1, and the permission setting of the group 2 is not checked.

The permission settings for group 1 are to control the data fields of client name, technical requirements, delivery date, delivery location, product model number, quantity and unit price, which are not visible to the processor of node 4, resulting in a control field for node 4.

The control field of the node 4 is consistent with the control field table of table 4, and will not be described herein.

And eliminating the control fields from all the data fields of the node 4 to obtain display fields, wherein the display fields are consistent with the display fields of the table 5, and the description is omitted here.

And S208, the server sends the display data field to the terminal.

The server sends the display field to the terminal, and the terminal displays the display field to the handler of the node 4.

For example, in the sales contract signing process, assuming that the server acquires the display field of the node 4, and the display field table is shown in table 5, the server only sends the technical requirement field to the terminal, and the form displayed by the terminal to the node 4 handler only includes the technical requirement field.

The form displayed by the terminal can receive the approval operation of the handler of the node 4, and when the server detects that the handler of the node 4 has submitted the approval operation, the server controls the flow to the node 5, and so on until the workflow is finished.

As shown in fig. 7, an authority control apparatus diagram of a workflow node provided in an embodiment of the present application includes:

a receiving unit 701 configured to receive task items; the task item corresponds to a plurality of nodes;

a first determining unit 702, configured to receive login information sent by a terminal, and determine, from the multiple nodes, a first node corresponding to the login information;

a first obtaining unit 703, configured to obtain a data field of the first node and an authority rule table of the first node or an authority rule group table of the first node;

a second determining unit 704, configured to determine, according to the authority rule table of the first node or the authority rule group table of the first node, a display field corresponding to the first node from the data field.

A sending unit 705, configured to send the display field corresponding to the first node to the terminal

In one possible implementation, the apparatus further includes:

a receiving unit, configured to receive a first operation of a user;

In one possible implementation, the apparatus further includes:

the authority rule table of the first node comprises at least one authority rule;

the second determining unit specifically includes:

and the third determining unit is used for sequentially judging whether the at least one authority rule is established or not and determining the display field according to the first established authority rule in the at least one authority rule.

In one possible implementation, the apparatus further includes:

the authority group table of the first node comprises at least one authority rule group, and the authority rule group comprises at least one authority rule;

the second determining unit specifically includes:

the fourth determining unit is used for sequentially judging whether the at least one authority rule group is established, and determining the display field according to the first established authority rule group in the at least one authority rule group; and when all the authority rules in the authority rule group are established, the authority rule group is established.

In a possible implementation manner, the third determining unit specifically includes:

In a possible implementation manner, the fourth determining unit specifically includes:

It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by a computer program, which can be stored in a computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. The storage medium may be a usb disk, a magnetic disk, an optical disk, a Read-only Memory (ROM), a Random Access Memory (RAM), or the like.

The present application may be a system, method and/or computer program product. The computer program product may include a computer-readable storage medium having computer-readable program instructions embodied thereon for causing a processor to implement various aspects of the present application.

The computer readable storage medium may be a tangible device that can hold and store the instructions for use by the instruction execution device. The computer readable storage medium may be, for example, but not limited to, an electronic memory device, a magnetic memory device, an optical memory device, an electromagnetic memory device, a semiconductor memory device, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a Static Random Access Memory (SRAM), a portable compact disc read-only memory (CD-ROM), a Digital Versatile Disc (DVD), a memory stick, a floppy disk, a mechanical coding device, such as punch cards or in-groove projection structures having instructions stored thereon, and any suitable combination of the foregoing. Computer-readable storage media as used herein is not to be construed as transitory signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide or other transmission medium (e.g., optical pulses through a fiber optic cable), or electrical signals transmitted through electrical wires.

The computer-readable program instructions described herein may be downloaded to the respective computing/processing apparatus from a computer-readable storage medium, or to an external computer or external storage device via a network, such as the internet, a local area network, a wide area network, and/or a wireless network. The network may include copper transmission cables, fiber optic transmission, wireless transmission, routers, firewalls, switches, gateway computers and/or edge servers. The network adapter card or network interface in each computing/processing device receives computer-readable program instructions from the network and forwards the computer-readable program instructions for storage in a computer-readable storage medium in the respective computing/processing device.

The computer program instructions for carrying out operations of the present application may be assembler instructions, Instruction Set Architecture (ISA) instructions, machine-related instructions, microcode, firmware instructions, state setting data, or source code or object code written in any combination of one or more programming languages, including an object oriented programming language such as Smalltalk, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The computer-readable program instructions may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider). In some embodiments, the electronic circuitry can execute computer-readable program instructions to implement aspects of the present application by utilizing state information of the computer-readable program instructions to personalize the electronic circuitry, such as a programmable logic circuit, a Field Programmable Gate Array (FPGA), or a Programmable Logic Array (PLA).

Various aspects of the present application are described herein with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the application. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer-readable program instructions.

These computer-readable program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. These computer-readable program instructions may also be stored in a computer-readable storage medium that can direct a computer, programmable data processing apparatus, and/or other devices to function in a particular manner, such that the computer-readable medium storing the instructions comprises an article of manufacture including instructions which implement the function/act specified in the flowchart and/or block diagram block or blocks.

The computer readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the instructions which execute on the computer, other programmable apparatus or other devices implement the functions/acts specified in the flowchart and/or block diagram block or blocks.

The description of the present embodiments has been presented for purposes of illustration and description, and is not intended to be exhaustive or limited to the invention in the form disclosed. Many modifications and variations will be apparent to practitioners skilled in this art. The embodiment was chosen and described in order to best explain the principles of the invention and the practical application, and to enable others of ordinary skill in the art to understand the disclosure for preferred embodiments only.

Claims

1. A method for controlling authority of a workflow node is characterized by comprising the following steps:

receiving task items; the task item corresponds to a plurality of nodes;

and sending the display field corresponding to the first node to the terminal.

2. The method of claim 1, wherein prior to said receiving a task item, the method further comprises:

receiving a first operation of a user;

3. The method of claim 1, wherein the permission rule table of the first node comprises at least one permission rule;

4. The method of claim 1, wherein the permission group table of the first node comprises at least one permission rule group, wherein the permission rule group comprises at least one permission rule;

5. The method according to claim 3, wherein the determining the display field according to a first established one of the at least one permission rule specifically comprises:

6. The method according to claim 4, wherein the determining the display field according to a first established permission rule group of the at least one permission rule group specifically includes:

7. An apparatus for controlling authority of a workflow node, the apparatus comprising:

a second determining unit, configured to determine, according to the permission rule table of the first node or the permission rule group table of the first node, a display field corresponding to the first node from the data field;

8. The apparatus of claim 7, further comprising:

a receiving unit, configured to receive a first operation of a user;

9. An authorization control device, comprising: one or more processors, one or more memories, transceivers; the one or more memories coupled to the one or more processors for storing computer program code comprising computer instructions which, when executed by the one or more processors, perform the method of any of claims 1-6.

10. A computer storage medium comprising computer instructions which, when executed, perform the method of any of claims 1-6.