Activiti-based enterprise business process configuration method, system, electronic device and medium

Abstract

The present application relates to a method, system, electronic device and medium for configuring business processes of an enterprise based on Activiti, which is applied to the field of process approval technology. The method includes: obtaining historical approval information and employee information; determining the form template of each form type based on the historical approval information; configuring at least one process information of each form type, the process information includes a process number and an approval flowchart, and the approval flowchart includes an approval node; associating the approval node with the employee information through an association relationship; setting the operable information of each approval node in the approval flowchart based on a first preset rule; responding to a process initiation instruction of a user terminal, receiving the process setting information sent by the user terminal; creating an approval task based on the process setting information and the operable information; and pushing the approval task to the user terminal based on the approval flowchart. The present application has the effect of improving the efficiency of business process configuration.

Description

Technical Field

[0001] The present application relates to the technical field of process approval, and in particular to an Activiti-based enterprise business process configuration method, system, electronic device and medium. Background Art

[0002] In the operation of an enterprise, process approval is a key link to ensure the smooth progress of various businesses. It involves many aspects such as project promotion, fund allocation, personnel changes, etc., and is an indispensable part of internal management of an enterprise. With the expansion of enterprise scale and the complexity of business, the efficiency of process configuration becomes increasingly important.

[0003] Currently, when enterprises configure approval processes, they usually configure corresponding forms and processes for different businesses. This approach results in poor versatility of the process, which in turn makes the business process configuration less efficient. Summary of the invention

[0004] In order to improve the efficiency of business process configuration, the present application provides an Activiti-based enterprise business process configuration method, system, electronic device and medium.

[0005] In the first aspect, the present application provides an Activiti-based enterprise business process configuration method, which adopts the following technical solutions:

[0006] A method for configuring enterprise business processes based on Activiti, applied to the server, including:

[0007] Obtain historical approval information and employee information;

[0008] Determine a form template for each form type based on the historical approval information, wherein the form template includes fields;

[0009] Configure at least one process information of each form type, the process information includes a process number and an approval flowchart, the approval flowchart is compiled based on Activiti, includes an approval node and approval logic, and each process information corresponds to at least one form type;

[0010] Associating the approval node with the employee information through an association relationship to obtain approver information of each approval node, wherein the association relationship includes a one-to-one association and a one-to-many association, and the approver information includes a fixed approver or multiple candidate approvers;

[0011] Setting operable information of each approval node in the approval flowchart based on a first preset rule, wherein the operable information includes operable fields and operation rules;

[0012] In response to a process initiation instruction from a user terminal, receiving process setting information sent by the user terminal, the process setting information including a target form type, a target process number, and a target approver;

[0013] Creating an approval task based on the target form type, the target process number, and the actionable information;

[0014] The approval task is pushed to the user end based on the approval flowchart.

[0015] By adopting the above technical solution, the form template of each form type is determined through historical approval information, which reduces unnecessary manual participation in formulating form templates, thereby improving the efficiency of determining form templates; by setting the operational information of the approval node, refined permission control is achieved, and the security of data and the standardization of the process are enhanced; through the many-to-many relationship between form type and process information, and the one-to-one or one-to-many association relationship between approval nodes and employee information, the process configuration can be more flexibly performed, and users can select the target form type, target process number, and target approver according to their needs, without having to pre-configure corresponding forms and processes for various businesses, thereby improving the efficiency of business process configuration.

[0016] Optionally, determining a form template for each form type based on the historical approval information includes:

[0017] Dividing the historical approval information based on the form type to obtain a plurality of approval information combinations, each of which corresponds to one form type;

[0018] Counting the filling rate and viewing rate of each field in each approval information combination, wherein the viewing rate is the viewing probability during or after the process approval;

[0019] If the filling rate exceeds a first preset probability and / or the viewing rate exceeds a second preset probability, determining the field as a first field;

[0020] The form template is determined based on the first field and required fields.

[0021] By adopting the above technical solution, the filling rate and viewing rate of each field are obtained by analyzing the historical approval information, and the fields in the form template are determined according to the filling rate and viewing rate of each field, thereby reducing unnecessary fields in the form template and improving the form filling efficiency of the process initiator and the approval efficiency of the process approver.

[0022] Optionally, before pushing the approval task to the user terminal based on the approval flowchart, the method further includes:

[0023] Configure fixed CC recipients for each of the form types;

[0024] The pushing the approval task to the user terminal based on the approval flowchart includes:

[0025] Pushing the approval task to the process approver based on the approval flowchart, the process approver includes the target approver and the fixed approver;

[0026] Receiving a to-be-added cc person sent by the user terminal;

[0027] The approval task is pushed to the fixed CC recipients and the CC recipients to be added.

[0028] By adopting the above technical solution and configuring fixed CC recipients for each form type, supervisors can view approval tasks more conveniently and flexibly adjust CC recipients by receiving CC recipients to be added sent by the user end.

[0029] Optionally, the step of pushing the approval task to a process approver based on the approval flowchart includes:

[0030] Get the approval task whose status is pending approval,

[0031] Dividing the approval tasks based on the process approvers to obtain a plurality of first approval task combinations, each of which corresponds to one of the process approvers;

[0032] Divide the approval tasks in each of the first approval task combinations based on a second preset rule to obtain pending approval tasks and non-approved tasks, wherein the pending approval tasks are the approval tasks that require further approval by the process approver, and the non-approved tasks are the approval tasks that do not meet the second preset rule;

[0033] Dividing the tasks to be approved in each of the first approval task combinations based on the form type to obtain a plurality of second approval task combinations, wherein the tasks to be approved in each of the second approval task combinations correspond to the same form type;

[0034] Verifying whether the tasks to be approved in each of the second approval task combinations conflict with each other based on a third preset rule, and marking the tasks to be approved that conflict with each other;

[0035] Each second approval task combination is pushed to the process approver based on the approval flowchart.

[0036] By adopting the above technical solution, the second preset rule can be used to more timely and accurately discover the tasks that are not approved, thereby reducing the approval workload of the process approver. The third preset rule is used to verify in advance whether the pending approval tasks in each second approval task combination conflict with each other, mark the conflicting pending approval tasks, and push the approval tasks to the process approver in units of the second approval task combination, so that the process approver can comprehensively consider the conflicting pending approval tasks to determine the approval result, thereby improving the accuracy of the approval.

[0037] In the second aspect, this application provides an Activiti-based enterprise business process configuration method, which adopts the following technical solutions:

[0038] An Activiti-based enterprise business process configuration method, applied to the user side, including:

[0039] Get the target form type;

[0040] Acquire a candidate process number based on the target form type, where the candidate process number is a process number corresponding to the target form type;

[0041] Get historical approval information;

[0042] Analyze the historical approval information to obtain a recommended process number;

[0043] Obtaining a target process number, where the target process number is determined by the initiator based on the candidate process number and the recommended process number;

[0044] Obtaining a target approver based on the target process number;

[0045] Determine process setting information based on the target form type, the target process number, and the target approver;

[0046] Generate a process initiation instruction and send the process setting information to the server.

[0047] By adopting the above technical solution, the recommended process number is obtained by analyzing the historical approval information, so that a more suitable process can be recommended to the initiator. The initiator of the process can flexibly select the target form type, target process number and target approver as needed, which improves the flexibility of the approval process configuration. The process setting information is sent to the server for process configuration, which improves the process configuration efficiency and reduces the processing work on the user side.

[0048] Optionally, analyzing the historical approval information to obtain a recommended process number includes:

[0049] Analyze the historical approval information to obtain the approval cycle of each candidate process number, wherein the approval cycle includes the longest approval cycle, the shortest approval cycle and the average approval cycle;

[0050] Determine a process approval cycle based on the longest approval cycle, the shortest approval cycle, the average approval cycle, and corresponding weights;

[0051] Determining a first recommendation degree based on the process approval cycle;

[0052] Determine the historical approval information corresponding to the current initiator as the historical approval information of interest;

[0053] Analyze the concerned historical approval information to obtain a usage rate of each candidate process number, wherein the usage rate includes a first usage rate and a second usage rate, wherein the first usage rate is a usage rate of the candidate process number by the current initiator under the target form type, and the second usage rate is a usage rate of the candidate process number by the current initiator under all the form types;

[0054] determining a second recommendation degree based on the first usage rate and the second usage rate;

[0055] Determining a final recommendation degree for each of the candidate process numbers based on the first recommendation degree and the second recommendation degree;

[0056] The recommendation process number is determined based on the final recommendation degree.

[0057] By adopting the above technical solution, when determining the recommended process number, not only the longest approval cycle, the shortest approval cycle and the average approval cycle of each candidate process number are taken into consideration, but also the usage rate of the candidate process number by the current initiator under the target form type and the usage rate of the candidate process number by the current initiator under all form types are taken into consideration, thereby improving the reliability of the recommended process number.

[0058] Optionally, the method further includes:

[0059] Receiving the approval task sent by the server;

[0060] Obtaining the waiting time and urgency level of each approval task;

[0061] determining a first reminder frequency based on the urgency level;

[0062] determining a frequency coefficient based on the waiting time;

[0063] determining a second reminder frequency based on the frequency coefficient and the first reminder frequency;

[0064] The user is reminded based on the second reminder frequency.

[0065] By adopting the above technical solution, the second reminder frequency is determined according to the waiting time and the urgency level of the approval task, so that the user (process approver) is reminded according to the second reminder frequency, thereby improving the process approval efficiency.

[0066] Optionally, after receiving the approval task sent by the server, the method further includes:

[0067] In response to a cc add instruction, obtaining a cc to be added;

[0068] The cc recipients to be added are sent to the server.

[0069] In the third aspect, the present application provides an Activiti-based enterprise business process configuration system, which adopts the following technical solutions:

[0070] An Activiti-based enterprise business process configuration system, applied to the server, including:

[0071] Information acquisition module, used to obtain historical approval information and employee information;

[0072] A template determination module, used to determine a form template for each form type based on the historical approval information, wherein the form template includes fields;

[0073] A process configuration module, used to configure at least one process information of each form type, wherein the process information includes a process number and an approval flowchart, wherein the approval flowchart is compiled based on Activiti and includes an approval node and approval logic, and each process information corresponds to at least one form type;

[0074] A node configuration module, used to associate the approval node with the employee information through an association relationship to obtain the approver information of each approval node, wherein the association relationship includes a one-to-one association and a one-to-many association, and the approver information includes a fixed approver or multiple candidate approvers;

[0075] An operation setting module, used to set operable information of each approval node in the approval flowchart based on a first preset rule, wherein the operable information includes operable fields and operation rules;

[0076] An information receiving module, configured to respond to a process initiation instruction from a user terminal and receive process setting information sent by the user terminal, wherein the process setting information includes a target form type, a target process number, and a target approver;

[0077] A task creation module, used to create an approval task based on the target form type, the target process number and the operable information;

[0078] The task push module is used to push the approval task to the user end based on the approval flowchart.

[0079] By adopting the above technical solution, the form template of each form type is determined through historical approval information, which reduces unnecessary manual participation in formulating form templates, thereby improving the efficiency of determining form templates; by setting the operational information of the approval node, refined permission control is achieved, and the security of data and the standardization of the process are enhanced; through the many-to-many relationship between form type and process information, and the one-to-one or one-to-many association relationship between approval nodes and employee information, the process configuration can be more flexibly performed, and users can select the target form type, target process number, and target approver according to their needs, without having to pre-configure corresponding forms and processes for various businesses, thereby improving the efficiency of business process configuration.

[0080] In the fourth aspect, the present application provides an Activiti-based enterprise business process configuration system, which adopts the following technical solutions:

[0081] An Activiti-based enterprise business process configuration system, applied to the user side, including:

[0082] The first acquisition module is used to acquire the target form type;

[0083] A second acquisition module is used to acquire a candidate process number based on the target form type, where the candidate process number is a process number corresponding to the target form type;

[0084] The third acquisition module is used to obtain historical approval information;

[0085] A recommendation determination module is used to analyze the historical approval information to obtain a recommended process number;

[0086] A fourth acquisition module, configured to acquire a target process number, where the target process number is determined by the initiator based on the candidate process number and the recommended process number;

[0087] A fifth acquisition module, used for acquiring a target approver based on the target process number;

[0088] An information determination module, used to determine process setting information based on the target form type, the target process number and the target approver;

[0089] The information sending module is used to generate a process initiation instruction and send the process setting information to the server.

[0090] By adopting the above technical solution, the recommended process number is obtained by analyzing the historical approval information, so that a more suitable process can be recommended to the initiator. The initiator of the process can flexibly select the target form type, target process number and target approver as needed, which improves the flexibility of the approval process configuration. The process setting information is sent to the server for process configuration, which improves the process configuration efficiency and reduces the processing work on the user side.

[0091] In a fifth aspect, the present application provides an electronic device, which adopts the following technical solution:

[0092] An electronic device comprises a processor, wherein the processor is coupled to a memory;

[0093] The memory stores a computer program that can be loaded by a processor and executes the Activiti-based enterprise business process configuration method described in any one of the first aspect or the second aspect.

[0094] In a sixth aspect, the present application provides a computer-readable storage medium, which adopts the following technical solution:

[0095] A computer-readable storage medium stores a computer program that can be loaded by a processor and executes the Activiti-based enterprise business process configuration method described in any one of the first aspect or the second aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0096] Figure 1 It is a flowchart of an Activiti-based enterprise business process configuration method applied to a server in an embodiment of the present application.

[0097] Figure 2 It is a flowchart of an Activiti-based enterprise business process configuration method applied to a user side in an embodiment of the present application.

[0098] Figure 3 It is a structural block diagram of an Activiti-based enterprise business process configuration system applied to the server in an embodiment of the present application.

[0099] Figure 4 It is a structural block diagram of an Activiti-based enterprise business process configuration system applied to the user side in an embodiment of the present application.

[0100] Figure 5 It is a structural block diagram of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0101] The present application is further described in detail below in conjunction with the accompanying drawings.

[0102] The embodiment of the present application provides an Activiti-based enterprise business process configuration method, which can be executed by an electronic device, which can be a server or a terminal device, wherein the server can be an independent physical server, a server cluster or a distributed system composed of multiple physical servers, or a cloud server providing cloud computing services. The terminal device can be a smart phone, a tablet computer, a desktop computer, etc., but is not limited thereto.

[0103] In order to make the purpose, technical solution and advantages of the embodiments of the present application clearer, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0104] In addition, the term "and / or" in this article is only a description of the association relationship of associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article, unless otherwise specified, generally means that the associated objects before and after are in an "or" relationship.

[0105] The embodiment of the present application provides an Activiti-based enterprise business process configuration method, including a server and a user side. The server side pre-configures forms and processes, and generates approval tasks according to the process initiation instructions of the user side. The user side includes a user side corresponding to the initiator and a user side corresponding to the process approver. The initiator triggers the process initiation instruction through the user side, and the user side sends the process initiation instruction to the server side. The process approver receives the approval task sent by the server through the user side and performs process approval, thereby completing the entire process of process configuration, initiation and approval. It is worth noting that the initiator of a process initiation instruction can also be the process approver of the approval task corresponding to other process initiation instructions.

[0106] like Figure 1 As shown, a method for configuring an Activiti-based enterprise business process is applied to the server. The main process of the method is described as follows (steps S101 to S108):

[0107] Step S101: Obtain historical approval information and employee information.

[0108] Obtain historical approval information and employee information from the database. The historical approval information includes but is not limited to the form type, the filling status of each field in the form, the approval record, and the viewing status of the form or approval record after the approval is completed. The employee information includes but is not limited to the employee's name, work number, and position.

[0109] Step S102: Determine a form template for each form type based on historical approval information.

[0110] The form template includes fields, the layout of fields, and the logic between fields. By analyzing the historical approval information, the field settings in the form template corresponding to each form type are obtained. The layout of fields and the logic between fields are pre-set by the staff and are not specifically limited here.

[0111] Specifically, determining a form template for each form type based on historical approval information includes: dividing the historical approval information based on the form type to obtain multiple approval information combinations, each approval information combination corresponding to a form type; counting the filling rate and viewing rate of each field in each approval information combination, the viewing rate being the probability of viewing during process approval or after the process approval is completed; if the filling rate exceeds a first preset probability and / or the viewing rate exceeds a second preset probability, determining the field as a first field; and determining a form template based on the first field and the required fields.

[0112] In this embodiment, the historical approval information corresponding to the same form type is divided into an approval information combination to obtain multiple approval information combinations. The filling rate and viewing rate of each field in each approval information combination are counted through a data analysis tool. If the filling rate exceeds the first preset probability and / or the viewing rate exceeds the second preset probability, the field is determined as the first field, and the required fields of each form type are obtained from the database. The first field and the required field are jointly determined as fields in the form template, wherein the data analysis tool can be Excel, Python, or SQL, and the first preset probability and the second preset probability are both pre-set, and are not specifically limited here.

[0113] Step S103: configure at least one process information of each form type.

[0114] Among them, the process information includes the process number and the approval flowchart. The approval flowchart corresponds to the process number one by one. The approval flowchart is compiled based on Activiti, including approval nodes and approval logic. Each process information corresponds to at least one form type. Activiti is an open source workflow engine used to support enterprise business process management and automation, which will not be repeated here.

[0115] Obtain the correspondence between form type and process information from the administrator, and configure the form type and process information based on the correspondence, that is, establish an association between form type and process information. One form type can correspond to multiple process information, and one process information can also correspond to multiple form types. Through the many-to-many relationship between form type and process information, more business needs can be met, eliminating the need to compile the same form multiple times and create the same process information multiple times, thereby simplifying the process configuration process.

[0116] Step S104: associate the approval node with the employee information through an association relationship to obtain the approver information of each approval node.

[0117] Among them, the association relationship includes one-to-one association and one-to-many association. The approver information includes fixed approvers or multiple candidate approvers. The association relationship between the approval node and the employee information is obtained from the administrator. If the approval node corresponds to a fixed approver, the approval node is associated with the employee information one-to-one, and the approver information of the approval node is a fixed approver; if the approver corresponding to the approval node is not fixed and the user needs to select, the approval node is associated with the employee information one-to-many, and the approver information of the approval node is multiple candidate approvers.

[0118] Step S105: setting operable information of each approval node in the approval flowchart based on the first preset rule.

[0119] Actionable information includes actionable fields and actionable rules. Actionable rules include but are not limited to hiding, displaying, disabling, enabling, editing, validating, and calculating.

[0120] In this embodiment, different approval nodes have different operable form fields (that is, different operable fields) and different operation rules. The first preset rule is obtained from the database or the administrator. The first preset rule is the correspondence between each approval node and the operable information, so that the operable information of each approval node in the approval flowchart can be set according to the first preset rule. At this time, the server has completed the pre-configuration process of the form and the process, and can subsequently generate an approval task according to the process initiation instruction of the user end.

[0121] Step S106: In response to the process initiation instruction from the user terminal, receive the process setting information sent by the user terminal.

[0122] The process setting information includes the target form type, target process number, and target approver. The target form type is the form type selected by the initiator when initiating the process. The target process number is the process number selected by the initiator when initiating the process. The target approver is the approver selected from multiple candidate approvers when the initiator initiates the process.

[0123] When the initiator initiates a process initiation instruction through the user end, the user end sends the initiator's process setting information to the server end, so that the server end can receive the process setting information.

[0124] Step S107: Create an approval task based on the target form type, target process number, and actionable information.

[0125] The server creates an approval task based on the target form type, target process number, and actionable information.

[0126] Step S108: Push the approval task to the user end based on the approval flowchart.

[0127] Specifically, before pushing the approval task to the user end based on the approval flowchart, the method also includes: configuring fixed CC recipients for each form type; pushing the approval task to the user end based on the approval flowchart, including: pushing the approval task to the process approvers based on the approval flowchart, the process approvers include target approvers and fixed approvers; receiving CC recipients to be added sent by the user end; pushing the approval task to the fixed CC recipients and the CC recipients to be added.

[0128] In this embodiment, the server's pre-configuration process for forms and processes also includes configuring fixed CCs for each form type, obtaining and configuring the fixed CCs corresponding to each form type from the administrator, so that when the approval task is pushed to the user end, not only the process approver can view the approval task, but the fixed CCs corresponding to the form type in the approval task can also view the approval task.

[0129] The approval task is pushed to the process approver corresponding to each approval node in the approval flowchart (that is, the user end corresponding to the process approver). After receiving the approval task, the process approver can add the CC recipient. At this time, the user end will send the CC recipient to be added to the server end. The server end receives the CC recipient to be added sent by the user end, and pushes the approval task to the fixed CC recipient initially configured on the server end and the user end corresponding to the CC recipient to be added.

[0130] Specifically, the approval tasks are pushed to the process approvers based on the approval flowchart, including: obtaining the approval tasks with a status of pending approval, dividing the approval tasks based on the process approvers, and obtaining multiple first approval task combinations, each of which corresponds to a process approver; dividing the approval tasks in each first approval task combination based on the second preset rule, and obtaining pending approval tasks and non-approved tasks, the pending approval tasks are approval tasks that require further approval by the process approver, and the non-approved tasks are approval tasks that do not meet the second preset rule; dividing the pending approval tasks in each first approval task combination based on the form type, and obtaining multiple second approval task combinations, the pending approval tasks in each second approval task combination correspond to the same form type; verifying whether the pending approval tasks in each second approval task combination conflict with each other based on the third preset rule, and marking the conflicting pending approval tasks; pushing each second approval task combination to the process approver based on the approval flowchart.

[0131] In this embodiment, the status of the approval task includes approval completed and pending approval. All approval tasks with a status of pending approval are obtained from the database, and the approval tasks corresponding to the same process approvers are divided into a first approval task combination to obtain multiple first approval task combinations. The second preset rule is obtained from the database. The second preset rule is a rule for verifying whether the content of each field in the form is reasonable and complete. The approval tasks in each first approval task combination are divided according to the second preset rule to obtain pending approval tasks and non-approved tasks. For example, if the second preset rule includes that the amount in the financial approval form cannot exceed the preset amount, then when the amount in a financial approval form exceeds the preset amount, the approval task corresponding to the financial approval form is a non-approved task.

[0132] The pending approval tasks in each first approval task combination are divided based on the form type to obtain multiple second approval task combinations, and a third preset rule is obtained from the database. The third preset rule is a rule for verifying whether the pending approval tasks in each second approval task combination conflict with each other. The pending approval tasks in each second approval task combination are verified according to the third preset rule, and the conflicting pending approval tasks are marked. For example: if the third preset rule includes that the total amount in all financial approval forms cannot exceed the preset amount, then when the total amount of all pending approval tasks in the second approval task combination corresponding to the financial approval form exceeds the preset amount, the pending approval tasks in the second approval task combination conflict with each other and need to be marked. When pushing the pending approval tasks to the process approver, they are pushed according to the second approval task combination, so that the process approver can process the pending approval tasks in batches.

[0133] like Figure 2As shown, a method for configuring an Activiti-based enterprise business process is applied to the user side. The main process of the method is described as follows (steps S201 to S208):

[0134] Step S201: Get the target form type.

[0135] When the initiator needs to initiate a process approval, the target form type will be selected and obtained from the initiator.

[0136] Step S202: Obtain candidate process numbers based on the target form type.

[0137] According to the target form type, a candidate process number associated with the target form type is obtained from the database, that is, the process number corresponding to the target form type.

[0138] Step S203: Obtain historical approval information.

[0139] Obtain historical approval information from the database. The historical approval information includes but is not limited to the form type, the filling status of each field in the form, the approval record, the approval cycle, and the viewing status of the form or approval record after the approval is completed.

[0140] Step S204: Analyze the historical approval information to obtain the recommended process number.

[0141] Specifically, historical approval information is analyzed to obtain a recommended process number, including: analyzing historical approval information to obtain the approval cycle of each candidate process number, the approval cycle includes the longest approval cycle, the shortest approval cycle and the average approval cycle; determining the process approval cycle based on the longest approval cycle, the shortest approval cycle, the average approval cycle and the corresponding weights; determining a first recommendation degree based on the process approval cycle; determining the historical approval information corresponding to the current initiator as the historical approval information of interest; analyzing the historical approval information of interest to obtain a usage rate of each candidate process number, the usage rate includes a first usage rate and a second usage rate, the first usage rate is the usage rate of the candidate process number under the target form type by the current initiator, and the second usage rate is the usage rate of the candidate process number under all form types by the current initiator; determining a second recommendation degree based on the first usage rate and the second usage rate; determining a final recommendation degree for each candidate process number based on the first recommendation degree and the second recommendation degree; determining the recommended process number based on the final recommendation degree.

[0142] In this embodiment, historical approval information is analyzed by a data analysis tool to obtain the longest approval cycle, the shortest approval cycle and the average approval cycle of each candidate process number, and the first weight, the second weight and the third weight corresponding to the longest approval cycle, the shortest approval cycle and the average approval cycle are obtained from the database. The process approval cycle = the longest approval cycle × the first weight + the shortest approval cycle × the second weight + the average approval cycle × the third weight. The database stores the correspondence between the process approval cycle and the first recommendation degree. The first recommendation degree of each candidate process number is searched from the database according to the process approval cycle.

[0143] The historical approval information corresponding to the current initiator is determined as the historical approval information of concern, and the historical approval information of concern is analyzed through a data analysis tool to obtain the first usage rate of the current initiator for the candidate process number under the target form type, and the second usage rate of the current initiator for the candidate process number under all form types. The database stores the correspondence between the first usage rate, the second usage rate and the second recommendation degree. The second recommendation degree is searched from the database according to the first usage rate and the second usage rate, and the first recommendation weight corresponding to the first recommendation degree and the second recommendation weight corresponding to the second recommendation degree are obtained from the database. The final recommendation degree = first recommendation degree × first recommendation weight + second recommendation degree × second recommendation weight. All candidate process numbers are sorted from high to low according to the final recommendation degree, and the candidate process numbers with a preset number of numbers in the front are determined as recommended process numbers.

[0144] Step S205: Get the target process number.

[0145] The recommended process number and the candidate process number are displayed to the initiator, so that the initiator selects a target process number therefrom, that is, the target process number is obtained from the initiator, and the target process number is determined by the initiator based on the candidate process number and the recommended process number.

[0146] Step S206: Obtain the target approver based on the target process number.

[0147] After the initiator selects the target process number, he / she also needs to select the target approver corresponding to the target process number, that is, obtain the target approver from the initiator.

[0148] Step S207: Determine process setting information based on the target form type, target process number, and target approver.

[0149] The target form type, target process number, and target approver are collectively determined as process setting information.

[0150] Step S208: Generate a process initiation instruction and send process setting information to the server.

[0151] When the initiator completes the selection of the target form type, target process number, and target approver, a process initiation instruction is generated and the process setting information is sent to the server.

[0152] Furthermore, the method also includes: receiving the approval task sent by the server; obtaining the waiting time and urgency level of each approval task; determining a first reminder frequency based on the urgency level; determining a frequency coefficient based on the waiting time; determining a second reminder frequency based on the frequency coefficient and the first reminder frequency; and reminding the user based on the second reminder frequency.

[0153] In this embodiment, in order to improve the approval efficiency of the process and reduce the approval cycle, it is necessary to provide approval reminders to the process approvers. After the user end corresponding to the process approver receives the approval task sent by the server end, the urgency level of each approval task is obtained from the database according to the form type corresponding to the approval task, and the waiting time of each approval task is calculated in real time. The waiting time = the current time - the time when the process approver of the first approval node in the approval task receives the approval task. The database stores the corresponding relationship between the urgency level and the first reminder frequency and the corresponding relationship between the waiting time and the frequency coefficient. The first reminder frequency is obtained from the database according to the urgency level, and the frequency coefficient is obtained from the database according to the waiting time. The second reminder frequency = the frequency coefficient × the first reminder frequency. The process approver corresponding to the current approval node is reminded according to the second reminder frequency.

[0154] Furthermore, after receiving the approval task sent by the server, the method further includes: in response to a cc add instruction, obtaining the cc to be added; and sending the cc to be added to the server.

[0155] In this embodiment, after receiving the approval task sent by the server, each process approver can add CC recipients as needed. The user end responds to the process approver's CC recipient addition instruction, obtains the CC recipients to be added from the process approver, and sends the CC recipients to be added to the server, so that the server can push the approval task to the CC recipients to be added.

[0156] Figure 3 This is a structural block diagram of an Activiti-based enterprise business process configuration system 300 applied to the server side in an embodiment of the present application.

[0157] like Figure 3 As shown, the Activiti-based enterprise business process configuration system 300 applied to the server mainly includes:

[0158] Information acquisition module 301, used to acquire historical approval information and employee information;

[0159] A template determination module 302, used to determine a form template for each form type based on historical approval information, where the form template includes fields;

[0160] The process configuration module 303 is used to configure at least one process information of each form type. The process information includes a process number and an approval flowchart. The approval flowchart is compiled based on Activiti and includes approval nodes and approval logic. Each process information corresponds to at least one form type.

[0161] The node configuration module 304 is used to associate the approval node with the employee information through an association relationship to obtain the approver information of each approval node. The association relationship includes a one-to-one association and a one-to-many association. The approver information includes a fixed approver or multiple candidate approvers.

[0162] An operation setting module 305 is used to set operable information of each approval node in the approval flow chart based on a first preset rule, where the operable information includes operable fields and operation rules;

[0163] The information receiving module 306 is used to respond to the process initiation instruction of the user end and receive the process setting information sent by the user end, where the process setting information includes the target form type, the target process number, and the target approver;

[0164] A task creation module 307, used to create an approval task based on a target form type, a target process number, and actionable information;

[0165] The task push module 308 is used to push the approval task to the user end based on the approval flowchart.

[0166] As an optional implementation of this embodiment, the template determination module 302 is also specifically used to determine the form template of each form type based on historical approval information, including: dividing the historical approval information based on the form type to obtain multiple approval information combinations, each approval information combination corresponds to a form type; counting the filling rate and viewing rate of each field in each approval information combination, the viewing rate is the probability of viewing during the process approval or after the process approval is completed; if the filling rate exceeds the first preset probability and / or the viewing rate exceeds the second preset probability, the field is determined as the first field; and the form template is determined based on the first field and the required field.

[0167] As an optional implementation of this embodiment, the task push module 308 is also specifically used to, before pushing the approval task to the user end based on the approval flowchart, also include: configuring fixed CCs for each form type; pushing the approval task to the user end based on the approval flowchart, including: pushing the approval task to the process approvers based on the approval flowchart, the process approvers include target approvers and fixed approvers; receiving CCs to be added sent by the user end; pushing the approval task to the fixed CCs and CCs to be added.

[0168] As an optional implementation of this embodiment, the task push module 308 is also specifically used to push approval tasks to process approvers based on the approval flowchart, including: obtaining approval tasks with a status of pending approval, dividing the approval tasks based on the process approvers, and obtaining multiple first approval task combinations, each of which corresponds to a process approver; dividing the approval tasks in each first approval task combination based on the second preset rule to obtain pending approval tasks and non-approved tasks, the pending approval tasks are approval tasks that require further approval by the process approver, and the non-approved tasks are approval tasks that do not meet the second preset rule; dividing the pending approval tasks in each first approval task combination based on the form type to obtain multiple second approval task combinations, and the pending approval tasks in each second approval task combination correspond to the same form type; verifying whether the pending approval tasks in each second approval task combination conflict with each other based on the third preset rule, and marking the conflicting pending approval tasks; pushing each second approval task combination to the process approver based on the approval flowchart.

[0169] Figure 4 This is a structural block diagram of an Activiti-based enterprise business process configuration system 400 applied to the user side in an embodiment of the present application.

[0170] like Figure 4 As shown, the Activiti-based enterprise business process configuration system 400 applied to the user side mainly includes:

[0171] The first acquisition module 401 is used to acquire the target form type;

[0172] The second acquisition module 402 is used to acquire a candidate process number based on the target form type, where the candidate process number is the process number corresponding to the target form type;

[0173] The third acquisition module 403 is used to obtain historical approval information;

[0174] The recommendation determination module 404 is used to analyze the historical approval information and obtain the recommended process number;

[0175] The fourth acquisition module 405 is used to acquire a target process number, where the target process number is determined by the initiator based on the candidate process number and the recommended process number;

[0176] A fifth acquisition module 406 is used to acquire a target approver based on the target process number;

[0177] An information determination module 407 is used to determine process setting information based on a target form type, a target process number, and a target approver;

[0178] The information sending module 408 is used to generate a process initiation instruction and send process setting information to the server.

[0179] As an optional implementation of this embodiment, the recommendation determination module 404 is also specifically used to analyze the historical approval information to obtain the recommended process number, including: analyzing the historical approval information to obtain the approval cycle of each candidate process number, the approval cycle includes the longest approval cycle, the shortest approval cycle and the average approval cycle; determining the process approval cycle based on the longest approval cycle, the shortest approval cycle, the average approval cycle and the corresponding weights; determining the first recommendation degree based on the process approval cycle; determining the historical approval information corresponding to the current initiator as the historical approval information of concern; analyzing the historical approval information of concern to obtain the usage rate of each candidate process number, the usage rate includes a first usage rate and a second usage rate, the first usage rate is the usage rate of the candidate process number under the target form type by the current initiator, and the second usage rate is the usage rate of the candidate process number under all form types by the current initiator; determining the second recommendation degree based on the first usage rate and the second usage rate; determining the final recommendation degree of each candidate process number based on the first recommendation degree and the second recommendation degree; determining the recommended process number based on the final recommendation degree.

[0180] As an optional implementation of this embodiment, the Activiti-based enterprise business process configuration system 400 applied to the user side is also specifically used to: receive approval tasks sent by the server; obtain the waiting time and urgency level of each approval task; determine a first reminder frequency based on the urgency level; determine a frequency coefficient based on the waiting time; determine a second reminder frequency based on the frequency coefficient and the first reminder frequency; and remind the user based on the second reminder frequency.

[0181] As an optional implementation of this embodiment, the Activiti-based enterprise business process configuration system 400 applied to the user side is also specifically used to, after receiving the approval task sent by the server side, also include: responding to the cc add instruction, obtaining the cc to be added; sending the cc to be added to the server side.

[0182] In one example, the module in any of the above devices can be one or more integrated circuits configured to implement the above methods, such as: one or more application specific integrated circuits (ASICs), or, one or more digital signal processors (DSPs), or, one or more field programmable gate arrays (FPGAs), or a combination of at least two of these integrated circuit forms.

[0183] For another example, when the modules in the device can be implemented in the form of a processing element scheduling program, the processing element can be a general-purpose processor, such as a central processing unit (CPU) or other processor that can call a program. For another example, these modules can be integrated together and implemented in the form of a system-on-a-chip (SOC).

[0184] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the above-described devices and modules can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0185] Figure 5 A structural block diagram of an electronic device 500 provided in an embodiment of the present application.

[0186] like Figure 5 As shown, the electronic device 500 includes a processor 501 and a memory 502 , and may further include an information input / information output (I / O) interface 503 , one or more of communication components 504 , and a communication bus 505 .

[0187] Among them, the processor 501 is used to control the overall operation of the electronic device 500 to complete all or part of the steps of the above-mentioned Activiti-based enterprise business process configuration method; the memory 502 is used to store various types of data to support the operation of the electronic device 500, and these data may include, for example, instructions for any application or method used to operate on the electronic device 500, and application-related data. The memory 502 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (Static Random Access Memory, SRAM), electrically erasable programmable read-only memory (Electrically Erasable Programmable Read-Only Memory, EEPROM), erasable programmable read-only memory (Erasable Programmable Read-Only Memory, EPROM), programmable read-only memory (Programmable Read-Only Memory, PROM), read-only memory (Read-Only Memory, ROM), magnetic memory, flash memory, disk or optical disk. One or more.

[0188] The I / O interface 503 provides an interface between the processor 501 and other interface modules, and the above-mentioned other interface modules can be keyboards, mice, buttons, etc. These buttons can be virtual buttons or physical buttons. The communication component 504 is used for wired or wireless communication between the electronic device 500 and other devices. Wireless communication, such as Wi-Fi, Bluetooth, Near Field Communication (NFC), 2G, 3G or 4G, or a combination of one or more of them, so the corresponding communication component 504 can include: Wi-Fi components, Bluetooth components, NFC components.

[0189] The electronic device 500 can be implemented by one or more application specific integrated circuits (ASIC), digital signal processors (DSP), digital signal processing devices (DSPD), programmable logic devices (PLD), field programmable gate arrays (FPGA), controllers, microcontrollers, microprocessors or other electronic components to execute the Activiti-based enterprise business process configuration method given in the above embodiment.

[0190] The communication bus 505 may include a path to transmit information between the above components. The communication bus 505 may be a PCI (Peripheral Component Interconnect) bus or an EISA (Extended Industry Standard Architecture) bus, etc. The communication bus 505 may be divided into an address bus, a data bus, a control bus, etc.

[0191] The electronic device 500 may include, but is not limited to, mobile terminals such as mobile phones, laptop computers, digital broadcast receivers, PDAs (personal digital assistants), PADs (tablet computers), PMPs (portable multimedia players), vehicle-mounted terminals (such as vehicle-mounted navigation terminals), etc., and fixed terminals such as digital TVs, desktop computers, etc., and may also be servers, etc.

[0192] The present application also provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the steps of the above-mentioned Activiti-based enterprise business process configuration method are implemented.

[0193] The computer-readable storage medium may include: a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and other media that can store program codes.

[0194] The terms "comprises," "comprising," or any other variations thereof are intended to cover non-exclusive inclusion such that a process, method, article, or apparatus that includes a list of elements includes not only those elements but also other elements not expressly listed, or also includes elements inherent to such process, method, article, or apparatus.

[0195] The above description is only a preferred embodiment of the present application and an explanation of the technical principles used. Those skilled in the art should understand that the scope of application involved in the present application is not limited to the technical solution formed by a specific combination of the above technical features, but should also cover other technical solutions formed by any combination of the above technical features or their equivalent features without departing from the aforementioned application concept. For example, the above features are replaced with (but not limited to) technical features with similar functions applied in the present application.

Claims

1. A method for configuring an enterprise business process based on Activiti, applied to the server, characterized in that: include: Obtain historical approval information and employee information; Determine a form template for each form type based on the historical approval information, wherein the form template includes fields; Configure at least one process information of each form type, the process information includes a process number and an approval flowchart, the approval flowchart is compiled based on Activiti, includes an approval node and approval logic, and each process information corresponds to at least one form type; Associating the approval node with the employee information through an association relationship to obtain approver information of each approval node, wherein the association relationship includes a one-to-one association and a one-to-many association, and the approver information includes a fixed approver or multiple candidate approvers; Setting operable information of each approval node in the approval flowchart based on a first preset rule, wherein the operable information includes operable fields and operation rules; In response to a process initiation instruction from a user terminal, receiving process setting information sent by the user terminal, the process setting information including a target form type, a target process number, and a target approver; Creating an approval task based on the target form type, the target process number, and the actionable information; Pushing the approval task to the user terminal based on the approval flowchart; The determining of the form template of each form type based on the historical approval information includes: Dividing the historical approval information based on the form type to obtain a plurality of approval information combinations, each of which corresponds to one form type; Counting the filling rate and viewing rate of each field in each approval information combination, wherein the viewing rate is the viewing probability during or after the process approval; If the filling rate exceeds a first preset probability and / or the viewing rate exceeds a second preset probability, determining the field as a first field; Determine the form template based on the first field and the required fields; Before pushing the approval task to the user terminal based on the approval flowchart, the method further includes: Configure fixed CC recipients for each of the form types; The pushing the approval task to the user terminal based on the approval flowchart includes: Pushing the approval task to the process approver based on the approval flowchart, the process approver includes the target approver and the fixed approver; Receiving a to-be-added cc person sent by the user terminal; Pushing the approval task to the fixed CC recipients and the CC recipients to be added; The step of pushing the approval task to the process approver based on the approval flowchart includes: Get the approval task whose status is pending approval, Dividing the approval tasks based on the process approvers to obtain a plurality of first approval task combinations, each of which corresponds to one of the process approvers; Divide the approval tasks in each of the first approval task combinations based on a second preset rule to obtain pending approval tasks and non-approved tasks, wherein the pending approval tasks are the approval tasks that require further approval by the process approver, and the non-approved tasks are the approval tasks that do not meet the second preset rule; Dividing the tasks to be approved in each of the first approval task combinations based on the form type to obtain a plurality of second approval task combinations, wherein the tasks to be approved in each of the second approval task combinations correspond to the same form type; Verifying whether the tasks to be approved in each of the second approval task combinations conflict with each other based on a third preset rule, and marking the tasks to be approved that conflict with each other; Each second approval task combination is pushed to the process approver based on the approval flowchart.

2. A method for configuring enterprise business processes based on Activiti, applied to the user side, characterized in that: include: Get the target form type; Acquire a candidate process number based on the target form type, where the candidate process number is a process number corresponding to the target form type; Get historical approval information; Analyze the historical approval information to obtain a recommended process number; Obtaining a target process number, where the target process number is determined by the initiator based on the candidate process number and the recommended process number; Obtaining a target approver based on the target process number; Determine process setting information based on the target form type, the target process number, and the target approver; Generate a process initiation instruction and send the process setting information to the server; The analyzing of the historical approval information to obtain the recommended process number includes: Analyze the historical approval information to obtain the approval cycle of each candidate process number, wherein the approval cycle includes the longest approval cycle, the shortest approval cycle and the average approval cycle; Determine a process approval cycle based on the longest approval cycle, the shortest approval cycle, the average approval cycle, and corresponding weights; Determining a first recommendation degree based on the process approval cycle; Determine the historical approval information corresponding to the current initiator as the historical approval information of interest; Analyze the concerned historical approval information to obtain a usage rate of each candidate process number, wherein the usage rate includes a first usage rate and a second usage rate, wherein the first usage rate is a usage rate of the candidate process number by the current initiator under the target form type, and the second usage rate is a usage rate of the candidate process number by the current initiator under all the form types; determining a second recommendation degree based on the first usage rate and the second usage rate; Determining a final recommendation degree for each of the candidate process numbers based on the first recommendation degree and the second recommendation degree; Determining the recommendation process number based on the final recommendation degree; The method further comprises: Receiving the approval task sent by the server; Obtaining the waiting time and urgency level of each approval task; determining a first reminder frequency based on the urgency level; determining a frequency coefficient based on the waiting time; determining a second reminder frequency based on the frequency coefficient and the first reminder frequency; Reminding the user based on the second reminder frequency; After receiving the approval task sent by the server, the method further includes: In response to a cc add instruction, obtaining a cc to be added; The cc recipients to be added are sent to the server.

3. An electronic device, characterized in that: comprising a processor coupled to a memory; The processor is configured to execute a computer program stored in the memory, so that the electronic device executes the method according to any one of claims 1 to 2.

4. A computer-readable storage medium, characterized in that: The method comprises a computer program or an instruction, and when the computer program or the instruction is executed on a computer, the computer is caused to execute the method according to any one of claims 1 to 2.

Images