CN109087054B - Collaborative office data stream processing method, device, computer equipment and storage medium - Google Patents
Collaborative office data stream processing method, device, computer equipment and storage medium Download PDFInfo
- Publication number
- CN109087054B CN109087054B CN201810556667.8A CN201810556667A CN109087054B CN 109087054 B CN109087054 B CN 109087054B CN 201810556667 A CN201810556667 A CN 201810556667A CN 109087054 B CN109087054 B CN 109087054B
- Authority
- CN
- China
- Prior art keywords
- linked list
- workflow
- workflow linked
- target
- user
- Prior art date
- Legal status (The legal status 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 status listed.)
- Active
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
- 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
Landscapes
- Business, Economics & Management (AREA)
- Human Resources & Organizations (AREA)
- Engineering & Computer Science (AREA)
- Strategic Management (AREA)
- Entrepreneurship & Innovation (AREA)
- Economics (AREA)
- Tourism & Hospitality (AREA)
- Marketing (AREA)
- Operations Research (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Game Theory and Decision Science (AREA)
- Development Economics (AREA)
- Educational Administration (AREA)
- Data Mining & Analysis (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The invention discloses a collaborative office data stream processing method, a collaborative office data stream processing device, computer equipment and a storage medium, which comprise the steps of acquiring a workflow linked list matched with task flow information started by a user in a flow database according to task flow attributes, acquiring a target number of a target working node contained in a jump instruction when the jump instruction is received, updating the workflow linked list if the target number is smaller than or equal to a preset maximum threshold value, enabling a current working node on the workflow linked list to jump to the target working node, calling a preset workflow design template when an editing instruction is received, enabling the user to edit the workflow linked list by using the workflow design template, checking the acquired target workflow linked list when the submitting instruction is received, and performing node circulation according to the target workflow linked list if the check is successful. The invention not only ensures that the operation of the user is convenient, improves the flexibility of configuration, but also improves the collaborative office efficiency and meets the requirement of actual office.
Description
Technical Field
The present invention relates to the field of computer technologies, and in particular, to a method and apparatus for processing a collaborative office data stream, a computer device, and a storage medium.
Background
The existing collaborative office system, especially the application related to business forms, generally defines a workflow linked list template for each business form separately, and mixes the business form processing logic with the workflow linked list processing logic, namely the business logic of each business form is tightly coupled with the workflow linked list engine, but for today with continuously abundant personalized requirements, more and more forms are required by one electronic form system, the workflow linked list which needs to be defined during development is increased, so that the development workload of the electronic form system is continuously increased, the maintenance cost is relatively high, and the default preset workflow linked list can not meet the actual collaborative office operation.
In addition, if the user does not adopt the workflow linked list set by default by the system, but edits the workflow linked list by self definition, the operation method is flexible, but the operation is complex, and the workload of the user is increased.
Therefore, whether the default preset workflow linked list or the custom edited workflow linked list is not beneficial to the actual requirement of the user for office work, and the workload of the user is increased, so that the maintenance of the workflow linked list is not beneficial.
Disclosure of Invention
In view of the foregoing, it is desirable to provide a method, an apparatus, a computer device, and a storage medium for collaborative office data stream processing that improve the flexibility of configuration of a workflow linked list and improve collaborative office efficiency.
A collaborative office data flow processing method, comprising:
acquiring task flow information started by a user, wherein the task flow information comprises task flow attributes;
acquiring a workflow linked list matched with the task flow attribute from a flow database according to the task flow attribute, and sending the workflow linked list to a front-end interface, wherein the workflow linked list comprises a numbered work node, and the flow database comprises the task flow attribute, the workflow linked list and a corresponding relation between the task flow attribute and the workflow linked list;
when a jump instruction submitted by the user at a current working node is received, acquiring a target number of a target working node contained in the jump instruction;
if the target number is smaller than or equal to a preset maximum threshold value, updating the workflow linked list so that the current working node jumps to the target working node;
When receiving an editing instruction of the user for the workflow linked list, calling a preset workflow design template to enable the user to edit the workflow linked list by using the workflow design template to obtain a target workflow linked list;
when a submitting instruction of the user is received, acquiring the target workflow linked list, and checking the target workflow linked list to obtain a checking result;
and if the verification result is that the verification is successful, node circulation is carried out according to the target workflow linked list.
A collaborative office data flow processing device, comprising:
the system comprises an acquisition module, a processing module and a processing module, wherein the acquisition module is used for acquiring task flow information started by a user, and the task flow information comprises task flow attributes;
the matching module is used for acquiring a workflow linked list matched with the task flow attribute from a flow database according to the task flow attribute and sending the workflow linked list to a front-end interface, wherein the workflow linked list comprises a numbered work node, and the flow database comprises the task flow attribute, the workflow linked list and a corresponding relation between the task flow attribute and the workflow linked list;
The jump module is used for acquiring a target number of a target working node contained in a jump instruction when the jump instruction submitted by the user at the current working node is received;
the jump module is used for updating the workflow linked list if the target number is smaller than or equal to a preset maximum threshold value, so that the current working node jumps to the target working node;
the editing module is used for calling a preset workflow design template when receiving an editing instruction of the user on the workflow linked list, so that the user uses the workflow design template to edit the workflow linked list to obtain a target workflow linked list;
the verification module is used for acquiring the target workflow linked list when receiving a submitting instruction of the user, and verifying the target workflow linked list to obtain a verification result;
and the verification success module is used for carrying out node circulation according to the target workflow linked list if the verification result is that the verification is successful.
A computer device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, the processor implementing the steps of the collaborative office data flow processing method described above when the computer program is executed.
A computer readable storage medium storing a computer program which when executed by a processor performs the steps of the collaborative office data flow processing method described above.
According to the collaborative office data flow processing method, the collaborative office data flow processing device, the computer equipment and the storage medium, the workflow linked list which is matched with the task flow information and contains the working nodes is obtained according to the task flow information started by the user, and the working nodes of the workflow linked list are processed according to the operation instruction submitted by the user, so that the user can flexibly configure the workflow linked list according to actual conditions, the workflow linked list comprises the working nodes and the length which can be determined by jumping operation according to the preset workflow linked list, the workflow linked list can also be edited according to the workflow design template, the maintainability of the preset workflow link and the flexibility of the custom workflow linked list are perfectly combined, the characteristic of configuration flexibility is improved, the user operation is convenient, the maintenance workload of developers on the workflow linked list is greatly reduced, the collaborative office efficiency is improved, and the requirements of actual office are met.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings that are needed in the description of the embodiments of the present invention will be briefly described below, it being obvious that the drawings in the following description are only some embodiments of the present invention, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a schematic diagram of an application environment of a collaborative office data flow processing method according to an embodiment of the present invention;
FIG. 2 is a flow chart of a method for collaborative office data flow processing in accordance with an embodiment of the present invention;
FIG. 3 is a flowchart of an implementation of constructing a workflow linked list in a collaborative office data flow processing method according to an embodiment of the present invention;
FIG. 4 is a flowchart showing an implementation of step S6 of the collaborative office data flow processing method according to an embodiment of the present invention;
FIG. 5 is a flowchart of an implementation of pushing a workflow linked list to a user in a collaborative office data flow processing method according to an embodiment of the present invention;
FIG. 6 is a schematic diagram of a collaborative office data flow processing device according to an embodiment of the present invention;
FIG. 7 is a schematic diagram of a computer device in accordance with an embodiment of the invention.
Detailed Description
The following description of the embodiments of the present invention will be made clearly and fully with reference to the accompanying drawings, in which it is evident that the embodiments described are some, but not all embodiments of the invention. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
The collaborative office data stream processing method provided by the application environment comprises a server and a client, wherein the server and the client are connected through a network, the server acquires a workflow linked list which is matched with task flow information and contains a working node according to task flow information started by a user, the working node of the workflow linked list is processed according to an operation instruction submitted by the user, the user can flexibly configure the workflow linked list through the client, the client can be particularly but not limited to various personal computers, notebook computers, smart phones, tablet computers and portable wearable devices, and the server can be particularly realized by an independent server or a server cluster formed by a plurality of servers.
In one embodiment, as shown in fig. 2, a collaborative office data flow processing method is provided, and the method is applied to the server in fig. 1 for illustration, and includes the following steps:
s1: and acquiring task flow information started by the user, wherein the task flow information comprises task flow attributes.
Specifically, when the client detects that the user starts the task flow, that is, detects that the user completes information filling according to the task flow template, the information on the acquired task flow template is sent to the server as task flow information, so that the server acquires the task flow information.
The task flow templates used by each department are different due to different task flow conditions executed by each department. The task flow attributes consist of template categories and department categories of the task flow templates, wherein the template categories comprise purchasing, asking for leave, reimbursement and the like. In addition, the template categories are further subdivided into template categories of all departments according to different departments, and different task flow templates are designed according to the template categories of all departments, namely according to task flow attributes. For example, the task flow attributes are reimbursement and sales departments, the corresponding task flow templates are sales reimbursement templates, and reimbursement templates used by financial departments are financial reimbursement templates.
S2: and acquiring a workflow linked list matched with the task flow attribute from a flow database according to the task flow attribute, and transmitting the workflow linked list to a front-end interface, wherein the workflow linked list comprises a numbered work node, and the flow database comprises the task flow attribute, the workflow linked list and the corresponding relation between the task flow attribute and the workflow linked list.
Specifically, each task flow template stored in the flow database is provided with a corresponding preset workflow linked list, and due to the corresponding relation between the task flow attributes and the workflow linked list, the workflow linked list corresponding to the task flow attributes can be matched in the flow database according to the task flow attributes in the acquired task flow information, and the workflow linked list is sent to the front end interface of the client for display.
The flow database stores all task flow attributes in advance and workflow linked lists corresponding to the task flow attributes. In addition, each workflow linked list consists of the numbered work nodes.
S3: and when a jump instruction submitted by a user at the current working node is received, acquiring a target number of a target working node contained in the jump instruction.
Specifically, when the client detects that the user performs the jump operation on the target working node on the workflow linked list at the current working node, the target number of the target working node is obtained, and a jump instruction containing the target number is sent to the server.
When the server receives a jump instruction submitted by a user at a current working node, a target number contained in the jump instruction is acquired, each working node on the workflow linked list is in a movable state, and the current working node of the workflow linked list is adjusted by judging whether the target number meets a preset condition, so that a new connection relation between the working nodes of the workflow linked list is established.
For example, the process from the beginning to the end of a workflow linked list of a reimbursement task flow is a drafter, a department principal, a secondary leader, and a primary leader, when the drafter jumps the current drafter node to the working node of the secondary leader, i.e., when the original workflow linked list needs to establish a new connection between the working nodes, the workflow linked list becomes a drafter, a department principal, a secondary leader, and a primary leader.
S4: if the target number is smaller than or equal to the preset maximum threshold value, updating the workflow linked list so that the current working node jumps to the target working node.
Specifically, the target number acquired in the step S3 is substituted into a preset condition, and when the target number is smaller than or equal to a preset maximum threshold value, the workflow linked list is updated, so that the current working node jumps to the target working node. The preset conditions comprise the maximum working node number and the minimum working node number of the workflow linked list corresponding to each task flow.
It should be noted that, because some of the working nodes on the workflow linked list cannot be subjected to the skip operation, for example, it is assumed that the workflow linked list of the sales reimbursement task flow includes a sketcher→a department responsible person→a second level leader→a first level leader, and a total of four working nodes, the numbers of the working nodes from the sketcher to the first level leader are 1, 2, 3 and 4, respectively, and the workflow linked list is required to pass through the working node where the second level leader is located, that is, the preset maximum threshold is 3, and only when the obtained target number is less than or equal to 3, that is, the target working node where the user skips cannot reach the working node where the first level leader, for example, the target number is 3, at this time, the server updates the current workflow linked list, establishes a connection relationship of new working nodes, and obtains a new workflow linked list, that is, the sketcher→the second level leader→the first level leader.
S5: when receiving an editing instruction of a user on the workflow linked list, calling a preset workflow design template to enable the user to edit the workflow linked list by using the workflow design template to obtain a target workflow linked list.
Specifically, when the client detects that the user clicks the editing button, an editing instruction is sent to the server, and when the server receives the editing instruction of the user on the workflow linked list, a preset workflow design template is called, so that the user edits the workflow linked list by using the workflow design template.
Further, the editing workflow linked list can specifically delete, add, modify the working node on the current workflow linked list of the front-end interface, or newly build a new workflow linked list.
It should be noted that, when the client detects that the user creates the workflow linked list through the workflow design template, the current workflow linked list of the front-end interface is automatically deleted.
S6: when a submitting instruction of a user is received, a target workflow linked list is obtained, and the target workflow linked list is checked to obtain a checking result.
Specifically, when the user submits the target workflow linked list obtained by editing using the workflow design template according to step S5, the client sends the submitting instruction containing the target workflow linked list to the server. When the server receives a submitting instruction of a user, a target workflow linked list is obtained, and the target workflow linked list is checked to obtain a checking result.
Further, verifying the target workflow linked list specifically includes verifying the number of the working nodes of the target workflow linked list, and only when the number of the working nodes is within a preset working node number range and the executor information on the working nodes is valid, the target workflow linked list can normally circulate, otherwise, the server side sends verification failure prompt information to the front-end interface.
S7: and if the verification result is that the verification is successful, node circulation is carried out according to the target workflow linked list.
Specifically, if the verification result obtained in step S6 is that the verification is successful, that is, the connection relationship between the work nodes newly established by the edited workflow linked list is valid, the connection relationship is circulated according to the order of the work nodes of the target workflow linked list, and the connection relationship is sent to the executor corresponding to the work node according to the executor information on the work node, so that the executor completes the execution operation on the work node.
In the embodiment corresponding to fig. 2, task flow information including task flow attributes started by a user is acquired, a workflow linked list matched with the task flow attributes is acquired in a flow database according to the task flow attributes, the workflow linked list is sent to a front-end interface, when a jump instruction of a target number of a target working node included in the current working node submitted by the user is received, if the target number is smaller than or equal to a preset maximum threshold value, the workflow linked list is updated, so that the current working node jumps to the target working node, when an edit instruction of the workflow linked list by the user is received, a preset workflow design template is called, so that the user edits the workflow linked list by using the workflow design template, the target workflow linked list is obtained, when a submit instruction of the user is received, the target workflow linked list is checked, and if the check result is successful, the node is checked according to the target workflow linked list, the user can flexibly configure the workflow linked list according to actual conditions, the workflow node and the length of the preset workflow linked list can be determined by the transfer operation, the workflow can be edited by the preset workflow design template, the flexibility is improved, the work efficiency of the workflow linked list is improved, the work flow is improved, the work efficiency is improved, and the user can not be well-defined, and the user can conveniently maintain the workflow is better.
In one embodiment, as shown in fig. 3, before step S1, the collaborative office data flow processing method further includes the following steps:
s8: and generating a workflow linked list corresponding to each preset task flow attribute according to the number of the working nodes contained in the task flow attribute and the executor information of each working node, wherein the workflow linked list contains the working nodes and the interconnection relation between the working nodes.
Specifically, task flow attributes input by a user, the number of working nodes and executor information corresponding to each node in a workflow linked list are acquired, a corresponding task flow template is acquired according to the task flow attributes, the working nodes with the same number are generated according to the number of the working nodes, the working nodes are built in a mutual connection relation, corresponding executor information is given to each working node according to the input executor information on each working node, and finally the workflow linked list is formed.
S9: and numbering each working node on the workflow linked list according to the interconnection relation, and storing the workflow linked list containing the numbers in a flow database.
Specifically, according to the workflow linked list formed in step S8, numbering is performed sequentially from the start working node to the end working node according to the interconnection relationship, and meanwhile, the workflow linked list containing the numbering and the corresponding task flow template are established with a corresponding connection relationship and stored in the flow database.
Further, continuing to refer to the example of step S4, when the server obtains that the task flow attribute input by the user is reimbursement and sales departments, the number of working nodes is 4, and the executor information corresponding to each working node is respectively a drafter, a department responsible person, a secondary leader and a primary leader, a sales reimbursement template is obtained according to the task flow attribute, a workflow linked list formed by connecting 4 working nodes is generated according to the number of working nodes, and executor information is given to each working node, so that the drafter, the department responsible person, the secondary leader and the primary leader are obtained, the working nodes from the drafter to the primary leader are numbered as 1, 2, 3 and 4, so that the workflow linked list drafter (1), the department responsible person (2), the secondary leader (3) and the primary leader (4) containing the numbers are obtained, and a corresponding connection relation is established with the sales reimbursement template, and finally the workflow linked list is stored in a flow database.
In the embodiment corresponding to fig. 3, the corresponding workflow linked list containing the number is generated in the flow database in advance according to the task flow attribute, so that the server side can acquire the corresponding preset workflow linked list according to the task flow attribute in the task flow started by the user, thereby improving the office efficiency and the accuracy of acquiring the workflow linked list. In addition, the numbering on the working nodes is convenient for the server to check the workflow linked list which is configured freely, so that the server forms a new connection relation of the working nodes according to the checking result.
In one embodiment, as shown in fig. 4, in step S6, verifying the target workflow linked list specifically includes the following steps:
s61: if the number of the working nodes on the target workflow linked list is larger than the preset maximum number of the working nodes or smaller than the preset minimum number of the working nodes, confirming that the verification result is that verification fails.
Specifically, when the server receives the submitting instruction of the user according to step S6, the edited target workflow linked list is obtained, each working node of the target workflow linked list is read, and the number of working nodes of the target workflow linked list is calculated, because in each workflow linked list with matched preset task flow attributes, the number of working nodes required by each workflow linked list is different, the success of the verification result can be confirmed only when the number of working nodes of the target workflow linked list meets the preset verification condition, namely, if the number of working nodes on the target workflow linked list is smaller than or equal to the preset maximum number of working nodes or larger than the preset minimum number of working nodes, the success of the verification result is confirmed, otherwise, if the number of working nodes on the target workflow linked list is larger than the preset maximum number of working nodes or smaller than the preset minimum number of working nodes, the verification result is confirmed to be failed.
For example, when the preset check condition requires that the number of the working nodes of the workflow linked list of the sales reimbursement task flow cannot be less than 3 or exceeds 6, if the number of the working nodes of the edited workflow linked list is 2 or includes a value above 7, the workflow linked list is confirmed to be not in accordance with the check condition, and the check result is confirmed to be a check failure.
S62: if the number of the working nodes on the target workflow linked list is smaller than or equal to the preset maximum number of the working nodes or larger than or equal to the preset minimum number of the working nodes, the operator information of the working nodes on the target workflow linked list is inquired in a personnel organization table in the flow database.
Specifically, if the target workflow linked list is checked according to step S6, and when the number of working nodes on the target workflow linked list is less than or equal to the preset maximum number of working nodes or greater than or equal to the preset minimum number of working nodes, the operator information corresponding to each working node on the target workflow linked list is further queried in the personnel organization table in the flow database, and whether the operator information corresponding to each working node is recorded in the personnel organization table is determined. If the information of the executor is not inquired, the working node is invalid, and the verification result is confirmed to be verification failure.
The reason why the operator information is not searched includes that the operator information input by the user is wrong or that the operator information is not input into the personnel organization table.
S63: if the information of the executor is inquired, the verification result is confirmed to be successful, otherwise, the verification result is confirmed to be failed.
Specifically, according to step S62, the operator information of the working node on the target workflow linked list is queried in the personnel organization table in the flow database, if the operator information is queried, the verification result is confirmed to be successful, otherwise, the operator information is not queried, the working node is invalid, and if the working node is invalid, the verification result is confirmed to be failed.
In the embodiment corresponding to fig. 4, if the number of the working nodes on the target workflow linked list is greater than the preset maximum number of the working nodes or less than the preset minimum number of the working nodes, confirming that the verification result is failed, otherwise, further querying the executor information of the working nodes on the target workflow linked list in the personnel organization table in the flow database, if the executor information is queried, confirming that the verification result is successful, otherwise, confirming that the verification result is failed, and by verifying the edited target workflow linked list, the working nodes of the target workflow linked list which are successful in verification can be normally circulated, thereby improving the office execution efficiency while meeting the office practical office requirements.
In an embodiment, as shown in fig. 5, after step S1, the collaborative office data flow processing method further includes the following steps:
s10: when a push instruction submitted by a user at a current working node is received, the identity information of the user contained in the push instruction is acquired.
Specifically, when the client detects that the user clicks a push button at the current working node, a push command is sent to the server, wherein the push command comprises the identity information of the user, and when the server receives the push command, the identity information of the user is obtained.
S11: and acquiring a historical workflow linked list of the user from the flow database according to the identity identification information.
Specifically, the workflow log in the flow database records and stores the used history workflow linked list for each user as history information, wherein the history information comprises the identity information of the user, the department to which the identity information corresponds, the history workflow linked list and the time of using the history workflow linked list.
Specifically, according to the identification information, a history workflow linked list matched with the identification information of the user is queried in a workflow log in a flow database, the history workflow linked list is ordered in a descending order according to the recorded time of using the history workflow linked list, and n history workflow linked lists before the ordering are obtained, wherein n can be specifically 1 or other positive integers without limitation.
S12: and determining the department to which the user belongs according to the identity information.
Specifically, according to the identification information, the affiliated department matched with the identification information of the user is queried in a workflow log in a flow database.
S13: and searching task flow attributes corresponding to the departments in the flow database according to the departments, and acquiring a department workflow linked list corresponding to the task flow attributes.
Specifically, according to the department to which the user belongs, which is determined in step S12, the task flow attribute corresponding to the department is searched in the flow database according to the department, and the department workflow linked list corresponding to the task flow attribute is obtained.
It should be noted that, the department workflow linked list corresponding to the task flow attribute collects the historical workflow linked list corresponding to the task flow attribute used by the user of the department through the workflow log, orders the historical workflow linked list according to the number of times of use from more to less, and uses the historical workflow linked list m before the order is obtained as the department workflow linked list corresponding to the task attribute, where m may be specifically 1 or other positive integers, and the invention is not limited herein.
S14: and sending the historical workflow linked list and the department workflow linked list to a front-end interface so that a user can select a target workflow linked list from the historical workflow linked list and the department workflow linked list.
Specifically, the historical workflow linked list and the department workflow linked list obtained in the step S11 may be sent to the front end interface of the client for display according to the sequence from the historical workflow linked list to the department workflow linked list or according to the sequence with the highest using times, so that the user selects the target workflow linked list from the historical workflow linked list and the department workflow linked list.
When the server detects that the historical workflow chain table and the department workflow chain table are the same, one historical workflow chain table or one department workflow chain table is sent to the front-end interface.
In the embodiment corresponding to fig. 5, when a push instruction submitted by a user at a current working node is received, the identity information of the user included in the push instruction is acquired, a historical workflow linked list of the user is acquired in a flow database, a department to which the user belongs is determined according to the identity information, a task flow attribute corresponding to the department is searched in the flow database, a department workflow linked list corresponding to the task flow attribute is acquired, and the historical workflow linked list and the department workflow linked list are sent to a front end interface, so that the user selects a target workflow linked list in the historical workflow linked list and the department workflow linked list, more workflow linked list references are provided for the user, and therefore office execution efficiency is improved.
In an embodiment, after step S3, the collaborative office data flow processing method further includes:
if the target number is smaller than the preset minimum threshold value or larger than the preset maximum threshold value, sending prompt information of jump failure to the front-end interface.
Specifically, when a jump instruction submitted by a user at a current working node is received according to step S3, after a target number of a target working node included in the jump instruction is obtained, if the target number is smaller than a preset minimum threshold or larger than a preset maximum threshold, prompt information of jump failure is sent to a front end interface of the client.
Continuing to refer to the step S4, assuming that a workflow chain table of the sales reimbursement task flow comprises a drafting person, a department responsible person, a second-level leader and a first-level leader, wherein the number of the working nodes from the drafting person to the first-level leader is 1, 2, 3 and 4 respectively, the workflow chain table is required to pass through the working node where the second-level leader is located, namely, the preset maximum threshold value is 4, and the workflow chain table cannot jump back to the working node of the drafting person, namely, the preset minimum threshold value is 2, when the acquired target number is 4 or 1, prompt information of jump failure is sent to a front-end interface, so that a user can perform legal jump operation again.
It should be understood that the sequence number of each step in the foregoing embodiment does not mean that the execution sequence of each process should be determined by the function and the internal logic, and should not limit the implementation process of the embodiment of the present invention.
In an embodiment, a cooperative office data stream processing device is provided, where the cooperative office data stream processing device corresponds to the cooperative office data stream processing method in the above embodiment one by one. As shown in fig. 6, the collaborative office data flow processing apparatus includes an acquisition module 601, a matching module 602, an acquisition skip module 603, a skip module 604, an editing module 605, a verification module 606, and a verification success module 607. The functional modules are described in detail as follows:
the acquiring module 601 is configured to acquire task flow information initiated by a user, where the task flow information includes task flow attributes;
the matching module 602 is configured to obtain a workflow linked list matched with the task flow attribute from a flow database according to the task flow attribute, and send the workflow linked list to the front-end interface, where the workflow linked list includes a numbered work node, and the flow database includes the task flow attribute, the workflow linked list, and a correspondence between the task flow attribute and the workflow linked list;
The obtaining jump module 603 is configured to obtain, when a jump instruction submitted by a user at a current working node is received, a target number of a target working node included in the jump instruction;
a skip module 604, configured to update the workflow linked list if the target number is less than or equal to a preset maximum threshold, so that the current working node skips to the target working node;
the editing module 605 is configured to call a preset workflow design template when receiving an editing instruction of a user on the workflow linked list, so that the user uses the workflow design template to edit the workflow linked list to obtain a target workflow linked list;
the verification module 606 is configured to obtain a target workflow linked list when receiving a commit instruction of a user, and verify the target workflow linked list to obtain a verification result;
and the verification success module 607 is configured to perform node circulation according to the target workflow linked list if the verification result is that the verification is successful.
Further, the cooperative office data stream processing apparatus further includes:
the generation linked list module 608 is configured to generate, for each preset task flow attribute, a workflow linked list corresponding to the task flow attribute according to the number of working nodes included in the task flow attribute and executor information of each working node, where the workflow linked list includes the working nodes and an interconnection relationship between the working nodes;
And the numbering module 609 is configured to number each working node on the workflow linked list according to the interconnection relationship, and store the workflow linked list containing the number in the flow database.
Further, the verification module 606 includes:
a first checking unit 6061, configured to confirm that the checking result is a check failure if the number of working nodes on the target workflow linked list is greater than the preset maximum number of working nodes or less than the preset minimum number of working nodes;
a query unit 6062, configured to query the operator information of the working nodes on the target workflow linked list in the personnel organization table in the flow database if the number of the working nodes on the target workflow linked list is less than or equal to the preset maximum number of the working nodes or greater than or equal to the preset minimum number of the working nodes;
and the second checking unit 6063 is configured to confirm that the checking result is successful if the information of the executor is queried, or confirm that the checking result is failed.
Further, the cooperative office data stream processing apparatus further includes:
the information acquisition module 610 is configured to acquire, when a push instruction submitted by a user at a current working node is received, identity information of the user included in the push instruction;
A first obtaining module 611, configured to obtain, according to the identity information, a historical workflow linked list of the user in the flow database;
a determining department module 612, configured to determine, according to the identity information, a department to which the user belongs;
a second obtaining module 613, configured to find a task flow attribute corresponding to a department in the flow database according to the department, and obtain a department workflow linked list corresponding to the task flow attribute;
and a send list module 614, configured to send the historical workflow list and the department workflow list to the front-end interface, so that the user selects the target workflow list from the historical workflow list and the department workflow list.
Further, the cooperative office data stream processing apparatus further includes:
the prompt module 615 is configured to send prompt information of failure in jumping to the front-end interface if the target number is smaller than a preset minimum threshold or larger than a preset maximum threshold.
For specific limitations of the cooperative office data stream processing apparatus, reference may be made to the above limitation of the cooperative office data stream processing method, and no further description is given here. The above-described respective modules in the cooperative office data stream processing apparatus may be implemented in whole or in part by software, hardware, or a combination thereof. The above modules may be embedded in hardware or may be independent of a processor in the computer device, or may be stored in software in a memory in the computer device, so that the processor may call and execute operations corresponding to the above modules.
In one embodiment, a computer device is provided, which may be a server, the internal structure of which may be as shown in fig. 7. The computer device includes a processor, a memory, a network interface, and a database connected by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, computer programs, and a database. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage media. The database of the computer device is used for storing and inquiring task flow information, workflow linked lists and the like. The network interface of the computer device is used for communicating with an external terminal through a network connection. The computer program when executed by a processor implements a collaborative office data flow processing method.
In one embodiment, a computer device is provided, including a memory, a processor, and a computer program stored on the memory and executable on the processor, where the processor executes the computer program to implement the steps of the collaborative office data flow processing method of the above embodiment, such as steps S1 to S7 shown in fig. 2. Alternatively, the processor may implement the functions of the modules/units of the cooperative office data stream processing apparatus in the above embodiment when executing a computer program, for example, the functions of the modules 601 to 607 shown in fig. 6. In order to avoid repetition, a description thereof is omitted.
In one embodiment, a computer readable storage medium is provided, on which a computer program is stored, where the computer program when executed by a processor implements the method for processing a collaboration office data stream in the foregoing method embodiment, or where the computer program when executed by a processor implements the functions of each module/unit in the collaboration office data stream processing apparatus in the foregoing apparatus embodiment. In order to avoid repetition, a description thereof is omitted.
Those skilled in the art will appreciate that implementing all or part of the above described methods may be accomplished by way of a computer program stored on a non-transitory computer readable storage medium, which when executed, may comprise the steps of the embodiments of the methods described above. Any reference to memory, storage, database, or other medium used in the various embodiments provided herein may include non-volatile and/or volatile memory. The nonvolatile memory can include Read Only Memory (ROM), programmable ROM (PROM), electrically Programmable ROM (EPROM), electrically Erasable Programmable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms such as Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double Data Rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous Link DRAM (SLDRAM), memory bus direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM), among others.
It will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-described division of the functional units and modules is illustrated, and in practical application, the above-described functional distribution may be performed by different functional units and modules according to needs, i.e. the internal structure of the apparatus is divided into different functional units or modules to perform all or part of the above-described functions.
The above embodiments are only for illustrating the technical solution of the present invention, and not for limiting the same; although the invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit and scope of the technical solutions of the embodiments of the present invention, and are intended to be included in the scope of the present invention.
Claims (9)
1. The method for processing the collaborative office data stream is characterized by comprising the following steps of:
acquiring task flow information started by a user, wherein the task flow information comprises task flow attributes;
Acquiring a workflow linked list matched with the task flow attribute from a flow database according to the task flow attribute, and sending the workflow linked list to a front-end interface, wherein the workflow linked list comprises a numbered work node, and the flow database comprises the task flow attribute, the workflow linked list and a corresponding relation between the task flow attribute and the workflow linked list;
when a jump instruction submitted by the user at a current working node is received, acquiring a target number of a target working node contained in the jump instruction;
if the target number is smaller than or equal to a preset maximum threshold value, updating the workflow linked list so that the current working node jumps to the target working node;
when receiving an editing instruction of the user for the workflow linked list, calling a preset workflow design template to enable the user to edit the workflow linked list by using the workflow design template to obtain a target workflow linked list;
when a submitting instruction of the user is received, acquiring the target workflow linked list, and checking the target workflow linked list to obtain a checking result;
If the verification result is that the verification is successful, node circulation is carried out according to the target workflow linked list;
when a push instruction submitted by the user at a current working node is received, acquiring the identity information of the user contained in the push instruction;
acquiring a historical workflow linked list of the user from the flow database according to the identity information;
determining a department to which the user belongs according to the identity information;
searching the task flow attribute corresponding to the department in the flow database according to the department, and acquiring a department workflow linked list corresponding to the task flow attribute;
and sending the historical workflow linked list and the department workflow linked list to the front-end interface so that the user selects the target workflow linked list from the historical workflow linked list and the department workflow linked list.
2. The method for processing a collaboration office data stream as claimed in claim 1 wherein prior to the obtaining of the user initiated task flow information, the method for processing a collaboration office data stream further comprises:
generating a workflow linked list corresponding to each preset task flow attribute according to the number of the working nodes contained in the task flow attribute and the executor information of each working node, wherein the workflow linked list contains the working nodes and the interconnection relation between the working nodes;
Numbering each working node on the workflow linked list according to the interconnection relation, and storing the workflow linked list containing the numbers in the flow database.
3. The collaborative office data flow processing method of claim 2, wherein the verifying the target workflow linked list comprises:
if the number of the working nodes on the target workflow linked list is larger than the preset maximum number of the working nodes or smaller than the preset minimum number of the working nodes, confirming that the verification result is verification failure;
if the number of the working nodes on the target workflow linked list is smaller than or equal to the preset maximum number of the working nodes or larger than or equal to the preset minimum number of the working nodes, inquiring executor information of the working nodes on the target workflow linked list in a personnel organization table in the flow database;
and if the executor information is inquired, confirming that the verification result is successful, otherwise, confirming that the verification result is failed.
4. The method for processing a collaborative office data flow according to claim 1, wherein when receiving a jump instruction submitted by the user at a current working node, the method for processing a collaborative office data flow further comprises, after obtaining a target number of a target working node included in the jump instruction:
And if the target number is smaller than a preset minimum threshold or larger than the preset maximum threshold, sending prompt information of failure in jumping to the front-end interface.
5. A collaborative office data flow processing device, the collaborative office data flow processing device comprising:
the system comprises an acquisition module, a processing module and a processing module, wherein the acquisition module is used for acquiring task flow information started by a user, and the task flow information comprises task flow attributes;
the matching module is used for acquiring a workflow linked list matched with the task flow attribute from a flow database according to the task flow attribute and sending the workflow linked list to a front-end interface, wherein the workflow linked list comprises a numbered work node, and the flow database comprises the task flow attribute, the workflow linked list and a corresponding relation between the task flow attribute and the workflow linked list;
the jump module is used for acquiring a target number of a target working node contained in a jump instruction when the jump instruction submitted by the user at the current working node is received;
the jump module is used for updating the workflow linked list if the target number is smaller than or equal to a preset maximum threshold value, so that the current working node jumps to the target working node;
The editing module is used for calling a preset workflow design template when receiving an editing instruction of the user on the workflow linked list, so that the user uses the workflow design template to edit the workflow linked list to obtain a target workflow linked list;
the verification module is used for acquiring the target workflow linked list when receiving a submitting instruction of the user, and verifying the target workflow linked list to obtain a verification result;
the verification success module is used for carrying out node circulation according to the target workflow linked list if the verification result is that the verification is successful;
the pushing module is used for acquiring the identity information of the user contained in the pushing instruction when receiving the pushing instruction submitted by the user at the current working node;
acquiring a historical workflow linked list of the user from the flow database according to the identity information;
determining a department to which the user belongs according to the identity information;
searching the task flow attribute corresponding to the department in the flow database according to the department, and acquiring a department workflow linked list corresponding to the task flow attribute;
And sending the historical workflow linked list and the department workflow linked list to the front-end interface so that the user selects the target workflow linked list from the historical workflow linked list and the department workflow linked list.
6. The collaborative office data flow processing apparatus as in claim 5, wherein the collaborative office data flow processing apparatus further comprises:
the generation linked list module is used for generating a workflow linked list corresponding to each preset task flow attribute according to the number of the working nodes contained in the task flow attribute and the executor information of each working node, wherein the workflow linked list contains the working nodes and the interconnection relation between the working nodes;
and the numbering module is used for numbering each working node on the workflow linked list according to the interconnection relation and storing the workflow linked list containing the numbers in the flow database.
7. The collaborative office data flow processing apparatus as in claim 6, wherein the verification module comprises:
the first verification unit is used for confirming that the verification result is failed in verification if the number of the working nodes on the target workflow linked list is larger than the preset maximum number of the working nodes or smaller than the preset minimum number of the working nodes;
The inquiring unit is used for inquiring the executor information of the working nodes on the target workflow linked list in a personnel organization mechanism table in the flow database if the number of the working nodes on the target workflow linked list is smaller than or equal to the preset maximum number of the working nodes or larger than or equal to the preset minimum number of the working nodes;
and the second verification unit is used for confirming that the verification result is successful if the information of the executor is inquired, and confirming that the verification result is failed if the information of the executor is not inquired.
8. A computer device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, characterized in that the processor implements the steps of the collaborative office data flow processing method of any of claims 1-4 when the computer program is executed.
9. A computer readable storage medium storing a computer program, wherein the computer program when executed by a processor implements the steps of the collaborative office data flow processing method of any of claims 1-4.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810556667.8A CN109087054B (en) | 2018-06-01 | 2018-06-01 | Collaborative office data stream processing method, device, computer equipment and storage medium |
| PCT/CN2018/094347 WO2019227573A1 (en) | 2018-06-01 | 2018-07-03 | Collaborative office data stream processing method and apparatus, computer device, and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810556667.8A CN109087054B (en) | 2018-06-01 | 2018-06-01 | Collaborative office data stream processing method, device, computer equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109087054A CN109087054A (en) | 2018-12-25 |
| CN109087054B true CN109087054B (en) | 2023-08-04 |
Family
ID=64839288
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810556667.8A Active CN109087054B (en) | 2018-06-01 | 2018-06-01 | Collaborative office data stream processing method, device, computer equipment and storage medium |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN109087054B (en) |
| WO (1) | WO2019227573A1 (en) |
Families Citing this family (23)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109977036B (en) * | 2019-02-19 | 2021-10-29 | 东软集团股份有限公司 | Method and device for caching process template, storage medium and electronic equipment |
| CN109634766B (en) * | 2019-02-20 | 2020-02-18 | 深圳大学 | Method, device, equipment and storage medium for improving operation efficiency of data flow machine |
| CN110018860B (en) * | 2019-04-04 | 2022-11-08 | 深圳市永兴元科技股份有限公司 | Workflow management method, device, equipment and computer storage medium |
| CN110071841B (en) * | 2019-04-30 | 2022-04-26 | 杭州迪普科技股份有限公司 | Method and device for checking configuration information of flow definition |
| CN110147986A (en) * | 2019-05-21 | 2019-08-20 | 天津卡达克数据有限公司 | Flow node jump method, device, server and storage medium |
| CN110310080B (en) * | 2019-05-22 | 2023-10-17 | 平安科技（深圳）有限公司 | Data streaming method, device, computer equipment and storage medium |
| CN110727969B (en) * | 2019-10-22 | 2021-10-15 | 深圳前海微众银行股份有限公司 | Method, device and equipment for automatically adjusting workflow and storage medium |
| CN111222845A (en) * | 2019-12-27 | 2020-06-02 | 北京健康之家科技有限公司 | Resource transfer method, device, equipment and readable storage medium |
| CN111506359B (en) * | 2020-03-26 | 2024-03-01 | 深圳市兴海物联科技有限公司 | Visual service configuration method, device, equipment and storage medium |
| CN112036823A (en) * | 2020-08-25 | 2020-12-04 | 上海中通吉网络技术有限公司 | Workflow-based work order transfer method, device and equipment |
| CN112235396B (en) * | 2020-10-13 | 2022-03-01 | 腾讯科技（深圳）有限公司 | Content processing link adjustment method, content processing link adjustment device, computer equipment and storage medium |
| CN112308440B (en) * | 2020-11-06 | 2024-06-25 | 平安证券股份有限公司 | Work order processing method, device, computer equipment and computer readable storage medium |
| CN112416476B (en) * | 2020-11-25 | 2023-03-24 | 武汉联影医疗科技有限公司 | Workflow execution method and device, computer equipment and storage medium |
| CN112685107A (en) * | 2020-12-15 | 2021-04-20 | 建信金融科技有限责任公司 | Workflow engine-based operation processing method, engine, electronic device and medium |
| CN112766885A (en) * | 2021-01-07 | 2021-05-07 | 多点(深圳)数字科技有限公司 | Work order transfer method and device, electronic equipment and storage medium |
| CN112819429B (en) * | 2021-01-29 | 2024-06-07 | 贵州惠智电子技术有限责任公司 | Flow management system and method based on big data autonomous learning function |
| CN113312409B (en) * | 2021-06-07 | 2024-06-28 | 平安证券股份有限公司 | Task monitoring method and device, electronic equipment and computer readable storage medium |
| CN113487294B (en) * | 2021-07-23 | 2023-06-09 | 重庆富民银行股份有限公司 | On-line business noninductive verification method based on list mechanism |
| CN113609831A (en) * | 2021-08-05 | 2021-11-05 | 北京金堤科技有限公司 | Method and device for generating product delivery flow template |
| CN113610504A (en) * | 2021-08-17 | 2021-11-05 | 平安资产管理有限责任公司 | Data processing method and device, computer equipment and storage medium |
| CN113706111B (en) * | 2021-08-30 | 2024-09-17 | 深圳平安智慧医健科技有限公司 | Medical institution flow data processing method, device, equipment and medium |
| CN115150474A (en) * | 2022-06-15 | 2022-10-04 | 阿里巴巴（中国）有限公司 | Information processing method, device, equipment and storage medium |
| CN115509696A (en) * | 2022-10-25 | 2022-12-23 | 中粮信托有限责任公司 | Method, device and equipment for constructing process engine and storage medium |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106910045A (en) * | 2017-03-02 | 2017-06-30 | 重庆砖家宝网络科技发展有限公司 | Design of Workflow method and system |
| CN107578217A (en) * | 2017-09-13 | 2018-01-12 | 深圳市沃易科技有限公司 | A kind of working electronic stream is autonomously generated method, apparatus and office management system |
| CN107944773A (en) * | 2017-12-29 | 2018-04-20 | 咪咕文化科技有限公司 | Business process control method, device and storage medium |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US11487716B2 (en) * | 2016-09-17 | 2022-11-01 | Oracle International Corporation | Application materialization in hierarchical systems |
| CN106651095A (en) * | 2016-09-28 | 2017-05-10 | 北京赢点科技有限公司 | Work flow configuring and jumping method and the configuring and jumping device |
-
2018
- 2018-06-01 CN CN201810556667.8A patent/CN109087054B/en active Active
- 2018-07-03 WO PCT/CN2018/094347 patent/WO2019227573A1/en active Application Filing
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106910045A (en) * | 2017-03-02 | 2017-06-30 | 重庆砖家宝网络科技发展有限公司 | Design of Workflow method and system |
| CN107578217A (en) * | 2017-09-13 | 2018-01-12 | 深圳市沃易科技有限公司 | A kind of working electronic stream is autonomously generated method, apparatus and office management system |
| CN107944773A (en) * | 2017-12-29 | 2018-04-20 | 咪咕文化科技有限公司 | Business process control method, device and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2019227573A1 (en) | 2019-12-05 |
| CN109087054A (en) | 2018-12-25 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109087054B (en) | Collaborative office data stream processing method, device, computer equipment and storage medium | |
| CN108573371B (en) | Data approval method, device, computer equipment and storage medium | |
| CN108874926B (en) | Mass data query method, device, computer equipment and storage medium | |
| CN109062883B (en) | Data table dynamic derivation method and device, computer equipment and storage medium | |
| CN109474578B (en) | Message checking method, device, computer equipment and storage medium | |
| WO2020186786A1 (en) | File processing method and apparatus, computer device and storage medium | |
| CN109189799B (en) | Service data query method, device, computer equipment and storage medium | |
| CN109032662B (en) | Code file generation method and device, computer equipment and storage medium | |
| CN106844307B (en) | System and method for converting Excel into Word based on mark | |
| CN111309991B (en) | Query statement generation method and device and data query method and system | |
| CN109062925A (en) | Automatically generate the method, apparatus, computer equipment and storage medium of insert sentence | |
| CN110609954A (en) | Data acquisition method and device, computer equipment and storage medium | |
| CN108415998B (en) | Application dependency relationship updating method, terminal, device and storage medium | |
| CN111309593A (en) | JSON interface verification method, device and equipment and computer readable storage medium | |
| CN111177121A (en) | Order data feedback method and device, computer equipment and storage medium | |
| CN112685091A (en) | Service request processing method, device, equipment and medium based on big data | |
| CN112905323A (en) | Data processing method and device, electronic equipment and storage medium | |
| CN110795171A (en) | Service data processing method and device, computer equipment and storage medium | |
| CN108334452B (en) | Rule data transfer test method, apparatus, computer device and storage medium | |
| CN112215015B (en) | Translation text revision method, device, computer equipment and storage medium | |
| CN112101848B (en) | Nuclear power station strategic material collecting method, device, equipment and medium for combined reserve | |
| CN113064917A (en) | Data query method and device, computer equipment and storage medium | |
| CN113761858B (en) | Form data processing method, device, computer equipment and storage medium | |
| CN112966974A (en) | Project configuration method, device, equipment and medium | |
| CN111597240A (en) | Data export method, data export device, computer equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |