Engine-based process approval method, device, computer equipment and storage medium

Abstract

This application belongs to the fields of data processing and financial technology, and relates to an engine-based process approval method, apparatus, computer equipment, and storage medium, including: extracting process codes and user information from a process start request triggered by a user, and performing identity authentication and permission verification on the user based on the user information; if the user passes the verification, displaying the process processing page, and receiving the process code and business data entered by the user in the process processing page; starting a process instance corresponding to the process code and business data in the process engine; determining the target approver corresponding to the process instance, and generating a target approval task based on the process instance; sending the target approval task to the target approver based on the process engine; receiving the approval operation performed by the target approver on the target approval task in the approval page, and generating a target approval result for the process instance based on the approval operation. This application improves the processing efficiency of process approval based on the use of a process engine.

Description

Technical Field

[0001] This application relates to the fields of data processing technology and financial technology, and in particular to engine-based process approval methods, devices, computer equipment and storage media. Background Art

[0002] To adapt to the internet era's demand for high-efficiency, low-cost workflows, more and more financial institutions are transitioning to information-based work models. Against this backdrop, driven by business control and risk mitigation needs, financial institutions generally require process management software. Consequently, systems with process approval capabilities have emerged.

[0003] However, the process approval systems currently used by financial institutions often rely on fixed processes, implemented by developers through coding tailored to specific business needs. Each business process has unique requirements, requiring developers to write specific code to match the approval requirements. This results in low process approval efficiency and high maintenance costs. Summary of the Invention

[0004] The purpose of the embodiments of the present application is to propose an engine-based process approval method, device, computer equipment and storage medium to solve the technical problems of low processing efficiency and high maintenance cost of business process approval in the process approval system based on fixed processes adopted by existing financial enterprises.

[0005] In order to solve the above technical problems, the present application provides an engine-based process approval method, which adopts the following technical solutions:

[0006] If a process start request triggered by a user is received, extract the process code and user information from the process start request, and authenticate the user based on the user information; wherein the process start request carries the process code and the user information of the user;

[0007] If the user passes the identity verification, the user's authority is verified based on the user information and the preset authority identification model;

[0008] If the user passes the authority verification, the preset process processing page is displayed, and the process code and business data entered by the user in the process processing page are received;

[0009] Starting a process instance corresponding to the process code and the business data in a preset process engine;

[0010] Determine a target approver corresponding to the process instance, and generate a target approval task corresponding to the target approver based on the process instance;

[0011] Sending the target approval task to the target approval personnel based on the process engine;

[0012] An approval operation performed by the target approver on the target approval task in a preset approval page is received, and a target approval result corresponding to the process instance is generated based on the approval operation.

[0013] Furthermore, the step of authenticating the user based on the user information specifically includes:

[0014] Collecting target biometric information corresponding to the user based on a preset biometric type; wherein the number of the biometric types includes multiple;

[0015] Call the preset feature information library;

[0016] Based on the user information, obtaining standard biometric feature information corresponding to the biometric feature type from the feature information database;

[0017] Performing verification processing on the target biometric characteristic information based on the standard biometric characteristic information;

[0018] If all the target biometric information passes the verification, it is determined that the user has passed the identity authentication;

[0019] If all the target biometric information fails to pass the verification, it is determined that the user has failed the identity verification.

[0020] Furthermore, the step of verifying the user's authority based on the user information and the preset authority identification model specifically includes:

[0021] Calling the permission identification model, and obtaining a target permission level corresponding to the user information based on the permission identification model;

[0022] Determining a target business operation corresponding to the process code;

[0023] Calling a preset business operation permission table, and querying the specified permission level range corresponding to the target business operation from the business operation permission table;

[0024] Determining whether the target permission level is within the specified permission level range;

[0025] If so, it is determined that the user has passed the authority verification; otherwise, it is determined that the user has not passed the authority verification.

[0026] Furthermore, before the step of starting the process instance corresponding to the process code and the business data in the preset process engine, the method further includes:

[0027] Acquire approval process configuration information corresponding to a designated process input by a target user; wherein the designated process is a process corresponding to the process code;

[0028] Call the preset original process engine;

[0029] Performing configuration processing on the approval process configuration information in the original process engine to obtain a configured original process engine;

[0030] The configured original process engine is used as the process engine.

[0031] Furthermore, after the step of generating a target approval result corresponding to the process instance based on the approval operation, the method further includes:

[0032] Based on the process engine, updating the status of the process instance according to the approval result;

[0033] Performing content analysis on the target approval result to obtain corresponding analysis results;

[0034] Acquire a target processing strategy corresponding to the process instance based on the analysis result;

[0035] The process instance is processed accordingly based on the target processing strategy.

[0036] Furthermore, after the step of generating a target approval result corresponding to the process instance based on the approval operation, the method further includes:

[0037] Based on the preset exception capture statement, the exception capture process is performed at the key operation point of the process engine to obtain the corresponding exception information;

[0038] Classify the abnormal information to obtain corresponding target abnormal information;

[0039] Call the preset log storage system;

[0040] The target exception information is stored in the log storage system.

[0041] Furthermore, after the step of generating a target approval result corresponding to the process instance based on the approval operation, the method further includes:

[0042] Obtaining a performance indicator category corresponding to the process engine;

[0043] Collecting target performance indicators corresponding to the performance indicator categories in the process engine based on a preset monitoring agent;

[0044] Performing data analysis on the target performance indicators based on a preset monitoring and analysis tool to determine whether there are any abnormal indicators in the target performance indicators;

[0045] If so, screening out the abnormal indicator from the target performance indicator, and generating corresponding abnormal warning information based on the abnormal indicator;

[0046] The abnormal warning information is sent to the corresponding processing personnel.

[0047] In order to solve the above technical problems, the embodiment of the present application further provides an engine-based process approval device, which adopts the following technical solution:

[0048] A first processing module is configured to, upon receiving a process start request triggered by a user, extract a process code and user information from the process start request, and authenticate the user based on the user information; wherein the process start request carries the process code and the user information;

[0049] A verification module, configured to verify the user's authority based on the user information and a preset authority identification model if the user passes identity authentication;

[0050] A second processing module is configured to display a preset process processing page if the user passes the authority verification, and receive the process code and business data entered by the user on the process processing page;

[0051] A startup module, configured to start a process instance corresponding to the process code and the business data in a preset process engine;

[0052] A first generating module is configured to determine a target approver corresponding to the process instance, and generate a target approval task corresponding to the target approver based on the process instance;

[0053] A first sending module, configured to send the target approval task to the target approval person based on the process engine;

[0054] The second generating module is configured to receive the approval operation performed by the target approver on the target approval task in a preset approval page, and generate a target approval result corresponding to the process instance based on the approval operation.

[0055] In order to solve the above technical problems, the embodiment of the present application further provides a computer device, which adopts the following technical solution:

[0056] If a process start request triggered by a user is received, extract the process code and user information from the process start request, and authenticate the user based on the user information; wherein the process start request carries the process code and the user information of the user;

[0057] If the user passes the identity verification, the user's authority is verified based on the user information and the preset authority identification model;

[0058] If the user passes the authority verification, the preset process processing page is displayed, and the process code and business data entered by the user in the process processing page are received;

[0059] Starting a process instance corresponding to the process code and the business data in a preset process engine;

[0060] Determine a target approver corresponding to the process instance, and generate a target approval task corresponding to the target approver based on the process instance;

[0061] Sending the target approval task to the target approval personnel based on the process engine;

[0062] An approval operation performed by the target approver on the target approval task in a preset approval page is received, and a target approval result corresponding to the process instance is generated based on the approval operation.

[0063] In order to solve the above technical problems, the embodiment of the present application further provides a computer-readable storage medium, which adopts the following technical solution:

[0064] If a process start request triggered by a user is received, extract the process code and user information from the process start request, and authenticate the user based on the user information; wherein the process start request carries the process code and the user information of the user;

[0065] If the user passes the identity verification, the user's authority is verified based on the user information and the preset authority identification model;

[0066] If the user passes the authority verification, the preset process processing page is displayed, and the process code and business data entered by the user in the process processing page are received;

[0067] Starting a process instance corresponding to the process code and the business data in a preset process engine;

[0068] Determine a target approver corresponding to the process instance, and generate a target approval task corresponding to the target approver based on the process instance;

[0069] Sending the target approval task to the target approval personnel based on the process engine;

[0070] An approval operation performed by the target approver on the target approval task in a preset approval page is received, and a target approval result corresponding to the process instance is generated based on the approval operation.

[0071] Compared with the prior art, the embodiments of the present application have the following beneficial effects:

[0072] After receiving a process start request triggered by a user and passing the identity authentication and permission verification of the user based on the user information, this application will intelligently receive the process code and business data input by the user based on the use of the process processing page, and start the process instance corresponding to the process code and the business data based on the use of the process engine, and then generate a target approval task corresponding to the matched target approver based on the process instance, and receive the approval operation performed by the target approver on the target approval task in the preset approval page, so as to generate a target approval result corresponding to the process instance based on the approval operation, thereby realizing the rapid and intelligent completion of the process approval processing based on the use of the process engine, effectively improving the processing efficiency of the process approval and improving the processing intelligence of the process approval. In addition, the process approval method of this application based on the process engine no longer requires R&D personnel to perform specific writing to match the approval of relevant business processes, effectively reducing the maintenance cost of process approval processing. BRIEF DESCRIPTION OF THE DRAWINGS

[0073] In order to more clearly illustrate the solutions in this application, a brief introduction will be given below to the drawings required for use in the description of the embodiments of this application. Obviously, the drawings described below are some embodiments of this application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0074] Figure 1 is an exemplary system architecture diagram to which the present application may be applied;

[0075] Figure 2 A flowchart of an embodiment of an engine-based process approval method according to the present application;

[0076] Figure 3 This is a structural diagram of an embodiment of an engine-based process approval device according to the present application;

[0077] Figure 4 It is a structural diagram of an embodiment of a computer device according to the present application. DETAILED DESCRIPTION

[0078] Unless otherwise defined, all technical and scientific terms used herein have the same meanings as commonly understood by those skilled in the art to which this application belongs. The terms used in the specification of the application are for the purpose of describing specific embodiments only and are not intended to limit this application. The terms "including" and "having" and any variations thereof in the specification and claims of this application and the above-mentioned drawings are intended to cover non-exclusive inclusions. The terms "first", "second", etc. in the specification and claims of this application or the above-mentioned drawings are used to distinguish different objects, not to describe a specific order.

[0079] References herein to "embodiments" mean that a particular feature, structure, or characteristic described in connection with the embodiments may be included in at least one embodiment of the present application. The appearance of this phrase in various places in the specification does not necessarily refer to the same embodiment, nor does it constitute an independent or alternative embodiment that is mutually exclusive of other embodiments. It is understood, both explicitly and implicitly, by those skilled in the art that the embodiments described herein may be combined with other embodiments.

[0080] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the accompanying drawings.

[0081] like Figure 1 As shown, system architecture 100 may include a terminal device 101, a network 102, and a server 103. Terminal device 101 may be a laptop computer 1011, a tablet computer 1012, or a mobile phone 1013. Network 102 is a medium for providing a communication link between terminal device 101 and server 103. Network 102 may include various connection types, such as wired or wireless communication links or fiber optic cables.

[0082] The user can use the terminal device 101 to interact with the server 103 via the network 102 to receive or send messages, etc. Various communication client applications can be installed on the terminal device 101, such as web browser applications, shopping applications, search applications, instant messaging tools, email clients, social platform software, etc.

[0083] The terminal device 101 can be various electronic devices with a display screen and supporting web browsing. In addition to the laptop computer 1011, the tablet computer 1012 or the mobile phone 1013, the terminal device 101 can also be an e-book reader, an MP3 player (Moving Picture Experts Group Audio Layer III), an MP4 (Moving Picture Experts Group Audio Layer IV) player, a laptop computer, a desktop computer, etc.

[0084] The server 103 may be a server that provides various services, such as a background server that provides support for web pages displayed on the terminal device 101 .

[0085] It should be noted that the engine-based process approval method provided in the embodiment of the present application is generally executed by a server / terminal device, and accordingly, the engine-based process approval device is generally set in the server / terminal device.

[0086] It should be understood that Figure 1 The number of terminal devices, networks and servers in the embodiment is merely illustrative. Any number of terminal devices, networks and servers may be provided as required.

[0087] Continue to refer Figure 2 , shows a flowchart of an embodiment of the engine-based process approval method according to the present application. According to different needs, the order of the steps in the flowchart can be changed, and some steps can be omitted. The engine-based process approval method provided in the embodiment of the present application can be applied to scenarios where process approval is required, and the engine-based process approval method can be applied to products in these scenarios, for example, process approval in the financial and insurance fields. The engine-based process approval method includes the following steps:

[0088] Step S201: If a process start request triggered by a user is received, the process code and user information are extracted from the process start request, and the user is authenticated based on the user information; wherein the process start request carries the process code and the user information of the user.

[0089] In this embodiment, the engine-based process approval method runs on the electronic device (eg Figure 1The server / terminal device shown in the figure) can obtain the process start request through a wired connection or a wireless connection. It should be noted that the above-mentioned wireless connection methods may include but are not limited to 3G / 4G / 5G connection, Wi-Fi connection, Bluetooth connection, WiMAX connection, Zigbee connection, UWB (Ultra Wi-Fi Broadband) connection, and other wireless connection methods currently known or to be developed in the future. The execution entity of this application may specifically be a process approval system. The process initiated by user demand may be a common process in financial affairs. For example, this application can be applied to a business scenario in which employees of an insurance company submit a claim expense reimbursement. The above-mentioned user may be an employee of an insurance company. The above-mentioned process start request is a processing request for submitting a claim expense reimbursement process. The above-mentioned process code is the code corresponding to the claim expense reimbursement process, and the above-mentioned user information may include the user's name or employee code. Among them, the process start request triggered by the user can be parsed to extract the process code and user information carried in the process start request. In addition, the specific implementation process of the above-mentioned user identity authentication based on the user information will be further described in detail in subsequent specific embodiments of this application, and will not be elaborated on here.

[0090] Step S202: If the user passes identity authentication, the user's authority is verified based on the user information and a preset authority identification model.

[0091] In this embodiment, the specific implementation process of the above-mentioned user authority verification based on the user information and the preset authority identification model will be further described in detail in subsequent specific embodiments of this application and will not be elaborated on here.

[0092] Step S203: If the user passes the authority verification, a preset process processing page is displayed, and the process code and business data entered by the user in the process processing page are received.

[0093] In this embodiment, the process processing page is a pre-built page that allows users to enter information related to the process they wish to initiate. The process code is the code for the process that the user wishes to initiate. Based on actual process processing requirements, a unique process code is pre-assigned to each process. Furthermore, the business data may include business description data required for process approval.

[0094] Step S204: Start a process instance corresponding to the process code and the business data in a preset process engine.

[0095] In this embodiment, after receiving the process code and business data input by the user, the process engine can be used to start the corresponding process instance. Specifically, the implementation process of the process engine includes: 1. Process definition and design. Define the process business logic. a. Understand business requirements: First, you need to have a deep understanding of the business requirements and clarify the purpose, input, output, and key nodes of the process. Design the process framework: Based on business requirements, design the overall framework of the process, including the main process branches and node types (such as task nodes, decision nodes, event nodes, etc.). Configure nodes: In the process engine, configure detailed properties for each node, such as node type, executor, execution conditions, timeout settings, etc. Use BPM2.0 specifications. b. Follow BPM2.0 elements: In process design, strictly follow the BPM2.0 specifications and use standard elements such as activities (Activity), events (Event), and gateways (Gateway). Graphical representation: Utilize the graphical representation method of BPMN 2.0 to describe the process through intuitive graphical symbols, which facilitates communication and understanding between business analysts and technical personnel. Execution semantics: Ensure that the process design conforms to the execution semantics of BPMN 2.0, enabling the model to be transformed into an actual business process during execution. c. Visual design. Tool selection: Utilize visual design tools supported by the process engine, such as web interfaces provided by Flowable and Activiti. Draw a flowchart: Draw a flowchart online and quickly build a process model by dragging elements and connecting lines. Configure properties: Configure detailed properties for each element in the flowchart, such as name, description, input and output variables, etc. 2. Process classification and business model. d. Process classification. Classification criteria: Develop process classification criteria based on business process similarity, business scenarios, departments or functions, and other factors. Establish a classification system: Establish a process classification system in the process engine, assigning independent classification identifiers and attributes to each process type. Conditional initiation: Supports process initiation based on specific conditions, such as time conditions and external event triggers. e. Business model. Abstraction and generalization: Abstract and generalize process categories to extract common business attributes, such as user roles, approval levels, and business rules. Conditional judgment: Use the attributes in the business model to provide a basis for judgment of process branches and start-up conditions. Dynamic adjustment: Dynamically adjust the attributes and logic of the business model according to changes in business needs to adapt to new business processes. 3. Permission configuration. F. Unified permissions. Role division: Define entities such as organizations, users, and roles in the process engine, and clarify the responsibilities and permissions of each role in the process. Permission allocation: Based on the responsibilities and permissions of the role, assign corresponding executors, approvers, etc. to each node in the process. Permission management: Provides permission management functions, supports advanced features such as permission addition, deletion, modification, and query, role inheritance, and permission inheritance.

[0096] Step S205 : determining a target approver corresponding to the process instance, and generating a target approval task corresponding to the target approver based on the process instance.

[0097] In this embodiment, the unified authority service can be called to obtain the approver list and authority list through the flowchart design or business logic corresponding to the process instance, and the target approver corresponding to the process instance can be determined based on the approver list and authority list. The target approval task is a task generated to remind the target approver to approve the process instance.

[0098] Step S206: Send the target approval task to the target approval person based on the process engine.

[0099] In this embodiment, the approval task is associated with the target approver by using the API or management tool of the process engine, so as to automatically assign the target approval task to the designated target approver.

[0100] Step S207: receiving the approval operation performed by the target approver on the target approval task in the preset approval page, and generating a target approval result corresponding to the process instance based on the approval operation.

[0101] In this embodiment, the approval page displays detailed information about the target approval task. This page includes at least detailed information about the process instance (e.g., process name, current node location, historical records, etc.), a description of the current approval node, and business data. On this page, the target approver can perform approval actions, such as selecting "Agree," "Reject," or "Transfer," and enter their approval comments. Based on these approval comments, a target approval result corresponding to the process instance can be generated.

[0102] After receiving a process start request triggered by a user and passing the identity authentication and permission verification of the user based on the user information, this application will intelligently receive the process code and business data input by the user based on the use of the process processing page, and start the process instance corresponding to the process code and the business data based on the use of the process engine, and then generate a target approval task corresponding to the matched target approver based on the process instance, and receive the approval operation performed by the target approver on the target approval task in the preset approval page, so as to generate a target approval result corresponding to the process instance based on the approval operation, thereby realizing the rapid and intelligent completion of the process approval processing based on the use of the process engine, effectively improving the processing efficiency of the process approval and improving the processing intelligence of the process approval. In addition, the process approval method of this application based on the process engine no longer requires R&D personnel to perform specific writing to match the approval of relevant business processes, effectively reducing the maintenance cost of process approval processing.

[0103] In some optional implementations, the authenticating the user based on the user information in step S201 includes the following steps:

[0104] Target biometric information corresponding to the user is collected based on a preset biometric type; wherein the number of the biometric types includes multiple.

[0105] In this embodiment, there is no specific limit on the number of biometric feature types, and they can be randomly set according to actual business needs. For example, the biometric feature types may include multiple types such as iris, nose, eyebrow, fingerprint, and lip.

[0106] Call the preset feature information library.

[0107] In this embodiment, the feature database is specifically an authenticated authentication database, for example, a database designated by a company that stores biometric feature information of credible company employees.

[0108] Based on the user information, standard biometric feature information corresponding to the biometric feature type is acquired from the feature information database.

[0109] In this embodiment, all designated biometric information corresponding to the user information can be obtained from the feature information library first, and then based on the biometric type, the biometric information matching the generated feature type can be filtered out from the designated biometric information and used as the above-mentioned standard biometric information.

[0110] The target biometric information is verified based on the standard biometric information.

[0111] In this embodiment, the target biometric information can be verified by using the standard biometric information respectively. Specifically, if the target biometric information includes iris feature information and lip feature information, the standard biometric information includes standard iris feature information and standard lip feature information. Then, the iris feature information is used to perform a similarity comparison with the corresponding standard iris feature information, and the lip feature information is used to perform a similarity comparison with the corresponding standard lip feature information. If all the calculated similarities are greater than the preset similarity threshold, it is determined that the target biometric information has passed the verification, and if there is a case where any of the calculated similarities is less than the similarity threshold, it is determined that the target biometric information has not passed the verification. Among them, there is no specific limitation on the value of the above-mentioned similarity threshold, and it can be set according to actual business usage requirements, for example, it can be set to 0.95.

[0112] If all the target biometric information passes the verification, it is determined that the user has passed the identity authentication.

[0113] In this embodiment, if all the target biometric feature information passes verification, it is determined that the user is a legitimate user and that the user has passed identity authentication.

[0114] If all the target biometric information fails to pass the verification, it is determined that the user has failed the identity verification.

[0115] In this embodiment, if all the target biometric feature information fails to pass the verification, it is determined that the user is not a legitimate user and that the user has failed the identity verification.

[0116] This application collects target biometric information corresponding to the user based on a preset biometric type; then calls a preset feature information library, and based on the user information, obtains standard biometric information corresponding to the biometric type from the feature information library; subsequently verifies the target biometric information based on the standard biometric information; if all of the target biometric information pass the verification, it is determined that the user has passed the identity authentication; and if all of the target biometric information do not pass the verification, it is determined that the user has not passed the identity authentication. After receiving a process start request triggered by the user, this application will intelligently authenticate the user based on the user information and the collected multiple biometric information of the user. Only when it is detected that the user has passed the multiple identity authentication based on multiple biometric information, will the subsequent processing of the process start request triggered by the user be executed, which effectively improves the standardized processing and security processing of the process start request, and ensures the security of the response to the process start request.

[0117] In some optional implementations of this embodiment, step S202 includes the following steps:

[0118] The permission identification model is called, and a target permission level corresponding to the user information is obtained based on the permission identification model.

[0119] In this embodiment, the permission identification model is a pre-built big data model that stores a one-to-one mapping relationship between the name information of each company employee and the permission level. The permission identification model can be queried using the user information to obtain the target permission level corresponding to the user information.

[0120] Determine a target business operation corresponding to the process code.

[0121] In this embodiment, different process codes correspond to different business operations. A mapping relationship between process codes and business operations is pre-established based on actual business needs. Furthermore, a business operation identifier that matches each business operation is pre-set. The business operation identifier is unique, with each business operation corresponding to one business operation identifier.

[0122] A preset business operation authority table is called, and a designated authority level interval corresponding to the target business operation is searched from the business operation authority table.

[0123] In this embodiment, the business operation permission table is a pre-built data table that stores multiple business operation identifiers and the permission level ranges corresponding to each business operation identifier. Specifically, the target business operation identifier corresponding to the target business operation can be obtained, and then the target business operation identifier can be used to query the business operation permission table to obtain the specified permission level range corresponding to the target business operation.

[0124] Determine whether the target permission level is within the specified permission level range.

[0125] In this embodiment, the target permission level can be compared with the two endpoint values ​​included in the above-mentioned specified permission level range to obtain a corresponding numerical comparison result, and based on the numerical comparison result, it can be identified whether the target permission level is within the specified permission level range.

[0126] If so, it is determined that the user has passed the authority verification; otherwise, it is determined that the user has not passed the authority verification.

[0127] In this embodiment, if the target permission level is within the specified permission level range, it indicates that the user has the operation permission to perform the target business operation corresponding to the process code, and the user is determined to have passed the permission verification. If the target permission level is not within the specified permission level range, it indicates that the user does not have the operation permission to perform the target business operation corresponding to the process code, and the user is determined to have failed the permission verification.

[0128] This application calls the permission identification model and obtains the target permission level corresponding to the user information based on the permission identification model; then determines the target business operation corresponding to the process code; then calls the preset business operation permission table, and queries the specified permission level interval corresponding to the target business operation from the business operation permission table; then determines whether the target permission level is within the specified permission level interval; only when it is detected that the target permission level is within the specified permission level interval, it indicates that the user has the operation permission to perform the target business operation corresponding to the above process code, thereby determining that the user has passed the permission verification, effectively improving the processing intelligence and processing accuracy of the user's permission verification, and ensuring the accuracy of the obtained user's permission verification result. In addition, only after it is determined that the user has passed the permission verification, will the response processing for the process start request triggered by the user be executed subsequently, effectively improving the standardized processing and security processing of the process start request, and ensuring the security of the response to the process start request.

[0129] In some optional implementations, before step S204, the electronic device may further perform the following steps:

[0130] Acquire approval process configuration information corresponding to a designated process input by a target user; wherein the designated process is a process corresponding to the process code.

[0131] In this embodiment, the target user may be an administrator of the process approval system. The approval process configuration information may be pre-built approval process information based on the actual process approval requirements that match the process corresponding to the process code. For example, it may include information such as which nodes are automatically approved and which are manually approved, the approval conditions and rules for each node, and an approval flow chart.

[0132] Call the preset original process engine.

[0133] In this embodiment, there is no specific limitation on the selection of the above-mentioned original process engine, which can be determined according to actual business usage requirements. Specifically, a workflow engine implemented based on Flowabl e6.5.0 can be used.

[0134] The approval process configuration information is configured in the original process engine to obtain a configured original process engine.

[0135] In this embodiment, the approval process is defined in the original process engine, including the start and end nodes of the process, as well as the order and conditions of each approval node. Specifically, a new process template is created according to the approval flow chart. The properties of each node are configured, such as node name, node type (automatic / manual), preconditions, post-actions, etc., and the flow logic between nodes is set to ensure that the process can be executed in the predetermined order, thereby obtaining the configured original process engine.

[0136] The configured original process engine is used as the process engine.

[0137] This application configures the original process engine using the approval process configuration information corresponding to the specified process input by the target user, and can intelligently and accurately build a process engine that meets user needs based on the configuration information input by the target user, thereby improving the construction efficiency and intelligence of the process engine and improving the user experience of the target user.

[0138] In some optional implementations, after step S207, the electronic device may further perform the following steps:

[0139] Based on the process engine, the state of the process instance is updated according to the approval result.

[0140] In this embodiment, after the target approver performs an approval operation on the target approval task in the approval page and generates a corresponding approval result, the process engine can automatically update the status of the process instance according to the approval result.

[0141] Perform content analysis on the target approval result to obtain corresponding analysis results.

[0142] In this embodiment, the content of the target approval result can be obtained by performing content analysis on the target approval result. The content of the target approval result includes approval approval or approval failure. Approval failure includes rejection or transfer.

[0143] A target processing strategy corresponding to the process instance is obtained based on the analysis result.

[0144] In this embodiment, for an approval result indicating approval, the corresponding processing strategy is for the process engine to advance the process to the next node. For an approval result indicating rejection, the corresponding processing strategy is to perform corresponding processing according to the business logic.

[0145] The process instance is processed accordingly based on the target processing strategy.

[0146] In this embodiment, the process instance may be processed accordingly according to the policy content of the target processing policy, thereby completing the process advancement of the process instance.

[0147] After generating a target approval result corresponding to the process instance based on the target reviewer's approval operation, this application intelligently updates the status of the process instance based on the approval result, achieving automatic and intelligent updates to the process instance's status. Furthermore, the application further analyzes the content of the target approval result and, based on the analysis results, obtains the target processing strategy corresponding to the process instance. The application then processes the process instance accordingly based on the target processing strategy, thereby accurately completing the process advancement of the process instance and ensuring the accuracy of the process advancement processing.

[0148] In some optional implementations of this embodiment, after step S207, the electronic device may further perform the following steps:

[0149] Based on the preset exception capture statement, the exception capture process is performed at the key operation point of the process engine to obtain the corresponding exception information.

[0150] In this embodiment, the exception catching statement may specifically employ a try-catch block. The key operation points may specifically include permission verification, data validation, and process execution within the process engine. The exception information may include an error code, error message, exception stack trace, occurrence time, and related context.

[0151] The abnormal information is classified and processed to obtain corresponding target abnormal information.

[0152] In this embodiment, exception information can be classified into different categories (such as insufficient user permissions, business data errors, process definition errors, etc.) based on the type and context of the exception information. Unique error codes and error messages are further designed for each type of exception to facilitate identification and processing, thereby obtaining the corresponding target exception information.

[0153] Call the preset log storage system.

[0154] In this embodiment, the log storage system is a pre-built system for storing captured exception information. The log storage system can specifically adopt ElasticSearch.

[0155] The target exception information is stored in the log storage system.

[0156] In this embodiment, a target folder named after the process instance is created in the log storage system, and the target exception information is stored in the target folder in the log storage system to complete the corresponding storage process. A user interface or API corresponding to the log storage system is provided to allow users to query the process log and monitor the status of the process instance.

[0157] During the operation of the process engine, the present application will also intelligently perform exception capture processing at the key operation points of the process engine based on the preset exception capture statements to obtain corresponding exception information, and classify the exception information to obtain corresponding target exception information, and then store the target exception information in the preset log storage system, thereby ensuring the data security of the exception information and facilitating subsequent auditing and monitoring.

[0158] In some optional implementations of this embodiment, after step S207, the electronic device may further perform the following steps:

[0159] Obtain the performance indicator category corresponding to the process engine.

[0160] In this embodiment, there is no specific limitation on the selection of the above monitoring indicator types, which can be set according to actual system monitoring requirements, for example, response time, throughput, memory usage, CPU usage, etc.

[0161] The target performance indicators corresponding to the performance indicator categories in the process engine are collected based on a preset monitoring agent.

[0162] In this embodiment, the monitoring agent is deployed in the process engine to collect monitoring indicators in the process engine. Specifically, the monitoring agent collects target performance indicators corresponding to the performance indicator categories in the process engine and sends the corresponding target performance indicators to the backend service of the monitoring tool corresponding to the monitoring agent.

[0163] Perform data analysis on the target performance indicators based on a preset monitoring and analysis tool to determine whether there are abnormal indicators in the target performance indicators.

[0164] In this embodiment, a monitoring tool is pre-deployed in the process approval system, and monitoring rules are configured in the monitoring tool. The monitoring rules are used to define which indicators corresponding to the above-mentioned process engine should trigger an alarm when they exceed or fall below a certain threshold. Monitoring rules can be set based on various conditions such as time, frequency, and threshold. The selection of the above-mentioned monitoring tool is not specifically limited and can be determined based on actual business usage requirements. For example, tools such as Prometheus and Grafana can be used. Specifically, the monitoring rules configured in the monitoring tool are used to analyze the target performance indicators and detect whether there are specified indicators in the target performance indicators that meet the requirements for triggering an alarm. If there are specified indicators in the target performance indicators that meet the requirements for triggering an alarm, the specified indicators are treated as the above-mentioned abnormal indicators. In addition, by regularly reviewing the monitoring strategy and monitoring rules, the monitoring indicators and thresholds can be adjusted according to changes and requirements of the process engine to ensure that the monitoring strategy is consistent with the actual operation of the process engine.

[0165] If so, the abnormal indicator is screened out from the target performance indicator, and corresponding abnormal warning information is generated based on the abnormal indicator.

[0166] In this embodiment, the abnormal indicators can be filled into a preset abnormal warning information template to generate corresponding abnormal warning information. The above abnormal warning information template is an information template constructed based on the actual process engine's warning notification requirements when abnormal indicators exist. The content of the information template can be written according to actual needs.

[0167] The abnormal warning information is sent to the corresponding processing personnel.

[0168] In this embodiment, the processing personnel may be the operation and maintenance personnel in the process approval system. The abnormality warning information may be sent to the operation and maintenance personnel via an alert notification method such as email or text message, so that the operation and maintenance personnel can be notified in a timely manner when an abnormality alarm of a designated engine is triggered.

[0169] This application obtains the performance indicator category corresponding to the process engine; then collects the target performance indicators corresponding to the performance indicator category in the process engine based on a preset monitoring agent; then performs data analysis on the target performance indicators based on a preset monitoring and analysis tool to determine whether there are abnormal indicators in the target performance indicators; if so, filters out the abnormal indicators from the target performance indicators, and generates corresponding abnormal warning information based on the abnormal indicators; and subsequently sends the abnormal warning information to the corresponding processing personnel. During the operation of the process engine, this application will also intelligently monitor the performance of the process engine based on the use of monitoring agents and monitoring tools, and when abnormal indicators are detected in the process engine, it will promptly and intelligently generate corresponding abnormal warning information based on the abnormal indicators and send it to the corresponding processing personnel, so that the processing personnel can promptly handle the current problems of the process engine by checking the abnormal warning information, which is conducive to ensuring the stable operation of the process engine.

[0170] In some optional implementations of this embodiment, the process approval system of this application also includes the functions of process control, notification callback, and process end processing, as follows:

[0171] Process control. Intelligent control: Use a rule engine (such as Gauss Lab's rule engine) to automatically trigger execution rules at process nodes and respond to results.

[0172] Notification callback. 1. Business data update: Before process approval, the latest business data is obtained through the get method and used as process business data. 2. Status change notification: When the process status changes (such as return, rejection, termination, etc.), the business system is notified of the updated status through the post method. 3. Approval notification: When the process is approved or reaches a specific node, the business system is notified to execute the corresponding logic.

[0173] 1. Notification Service: After the process ends, the business system is notified through the notification service to process the corresponding logic, such as updating the database or sending an email. 2. Failure Retry Mechanism: Ensures that the notification service can retry in the event of failure to ensure the correct execution of business logic.

[0174] It should be understood that the size of the serial numbers of the steps in the above embodiments does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present invention.

[0175] It should be emphasized that in order to further ensure the privacy and security of the above-mentioned target approval results, the above-mentioned target approval results can also be stored in a node of a blockchain.

[0176] The blockchain referred to in this application is a new application model of computer technologies such as distributed data storage, peer-to-peer transmission, consensus mechanisms, and encryption algorithms. Blockchain is essentially a decentralized database, a series of data blocks generated using cryptographic methods. Each data block contains information about a batch of network transactions, which is used to verify the validity of the information (anti-counterfeiting) and generate the next block. Blockchain can include the blockchain underlying platform, the platform product service layer, and the application service layer.

[0177] Those skilled in the art will appreciate that all or part of the processes in the above-described method embodiments can be implemented by instructing related hardware via computer-readable instructions. The computer-readable instructions can be stored in a computer-readable storage medium, and when the program is executed, it can include the processes in the above-described method embodiments. The aforementioned storage medium can be a non-volatile storage medium such as a magnetic disk, an optical disk, a read-only memory (ROM), or a random access memory (RAM).

[0178] It should be understood that although the steps in the flowcharts of the accompanying drawings are shown in sequence as indicated by the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless otherwise specified herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some of the steps in the flowcharts of the accompanying drawings may include multiple sub-steps or multiple stages, and these sub-steps or stages are not necessarily executed at the same time, but can be executed at different times, and their execution order is not necessarily sequential, but can be executed in turn or alternately with other steps or at least a portion of the sub-steps or stages of other steps.

[0179] Further references Figure 3 , as a response to the above Figure 2 The present application provides an embodiment of an engine-based process approval device, which is similar to Figure 2 Corresponding to the method embodiment shown, the device can be specifically applied to various electronic devices.

[0180] like Figure 3 As shown, the engine-based process approval device 300 of this embodiment includes: a first processing module 301, a verification module 302, a second processing module 303, a startup module 304, a first generation module 305, a first sending module 306 and a second generation module 307.

[0181] The first processing module 301 is configured to, upon receiving a process start request triggered by a user, extract a process code and user information from the process start request, and authenticate the user based on the user information; wherein the process start request carries the process code and the user information;

[0182] Verification module 302, configured to verify the user's authority based on the user information and a preset authority identification model if the user passes identity authentication;

[0183] The second processing module 303 is configured to display a preset process processing page if the user passes the authority verification, and receive the process code and business data entered by the user on the process processing page;

[0184] A starting module 304 is used to start a process instance corresponding to the process code and the business data in a preset process engine;

[0185] The first generating module 305 is used to determine the target approver corresponding to the process instance, and generate a target approval task corresponding to the target approver based on the process instance;

[0186] A first sending module 306 is configured to send the target approval task to the target approver based on the process engine;

[0187] The second generating module 307 is configured to receive the approval operation performed by the target approver on the target approval task in the preset approval page, and generate a target approval result corresponding to the process instance based on the approval operation.

[0188] In some optional implementations of this embodiment, the first processing module 301 includes:

[0189] a collection submodule, configured to collect target biometric information corresponding to the user based on a preset biometric type; wherein the number of the biometric types includes a plurality;

[0190] The calling submodule is used to call the preset feature information library;

[0191] A first acquisition submodule is configured to acquire, based on the user information, standard biometric feature information corresponding to the biometric feature type from the feature information database;

[0192] A verification submodule, configured to verify the target biometric information based on the standard biometric information;

[0193] A first determination submodule is configured to determine that the user has passed identity authentication if all target biometric feature information passes verification;

[0194] The second determination submodule is configured to determine that the user has failed identity authentication if all target biometric feature information fails to pass verification.

[0195] In some optional implementations of this embodiment, the verification module 302 includes:

[0196] a second acquisition submodule, configured to call the permission identification model and acquire a target permission level corresponding to the user information based on the permission identification model;

[0197] A determination submodule, configured to determine a target business operation corresponding to the process code;

[0198] A query submodule is used to call a preset business operation permission table and query the specified permission level interval corresponding to the target business operation from the business operation permission table;

[0199] A judgment submodule, configured to judge whether the target permission level is within the specified permission level range;

[0200] The third determination submodule is configured to determine that if yes, the user has passed the authority verification; otherwise, determine that the user has not passed the authority verification.

[0201] In some optional implementations of this embodiment, the engine-based process approval device further includes:

[0202] A first acquisition module is configured to acquire approval process configuration information corresponding to a designated process input by a target user; wherein the designated process is a process corresponding to the process code;

[0203] The first calling module is used to call the preset original process engine;

[0204] A configuration module, configured to perform configuration processing on the approval process configuration information in the original process engine to obtain a configured original process engine;

[0205] A determination module is configured to use the configured original process engine as the process engine.

[0206] In some optional implementations of this embodiment, the engine-based process approval device further includes:

[0207] An updating module, configured to update the status of the process instance based on the approval result based on the process engine;

[0208] An analysis module, configured to perform content analysis on the target approval result to obtain a corresponding analysis result;

[0209] A second acquisition module is used to acquire a target processing strategy corresponding to the process instance based on the analysis result;

[0210] The third processing module is used to perform corresponding processing on the process instance based on the target processing strategy.

[0211] In some optional implementations of this embodiment, the engine-based process approval device further includes:

[0212] A capture module is used to perform exception capture processing at key operation points of the process engine based on preset exception capture statements to obtain corresponding exception information;

[0213] A classification module is used to classify the abnormal information and obtain corresponding target abnormal information;

[0214] The second calling module is used to call the preset log storage system;

[0215] The storage module is used to store the target abnormality information in the log storage system.

[0216] In some optional implementations of this embodiment, the engine-based process approval device further includes:

[0217] A third acquisition module is used to obtain a performance indicator category corresponding to the process engine;

[0218] A collection module, configured to collect target performance indicators corresponding to the performance indicator categories in the process engine based on a preset monitoring agent;

[0219] A judgment module is used to perform data analysis on the target performance indicators based on a preset monitoring and analysis tool to determine whether there are any abnormal indicators in the target performance indicators;

[0220] a screening module, configured to, if yes, screen out the abnormal indicators from the target performance indicators and generate corresponding abnormal warning information based on the abnormal indicators;

[0221] The second sending module is used to send the abnormal warning information to corresponding processing personnel.

[0222] To solve the above technical problems, the present application also provides a computer device. Figure 4 , Figure 4 This is a basic structural block diagram of the computer device in this embodiment.

[0223] The computer device 4 includes a memory 41, a processor 42, and a network interface 43 that are interconnected through a system bus. It should be noted that the figure only shows a computer device 4 having components 41-43, but it should be understood that it is not required to implement all the components shown, and more or fewer components can be implemented instead. Among them, those skilled in the art will understand that the computer device here is a device that can automatically perform numerical calculations and / or information processing according to pre-set or stored instructions, and its hardware includes but is not limited to microprocessors, application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), digital signal processors (DSPs), embedded devices, etc.

[0224] The computer device may be a desktop computer, notebook computer, PDA, cloud server, etc. The computer device may interact with the user via a keyboard, mouse, remote control, touchpad, or voice control device.

[0225] The memory 41 includes at least one type of readable storage medium, including flash memory, hard disk, multimedia card, card-type memory (e.g., SD or DX memory), random access memory (RAM), static random access memory (SRAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), programmable read-only memory (PROM), magnetic memory, magnetic disk, optical disk, etc. In some embodiments, the memory 41 can be an internal storage unit of the computer device 4, such as the hard disk or memory of the computer device 4. In other embodiments, the memory 41 can also be an external storage device of the computer device 4, such as a plug-in hard disk equipped on the computer device 4, a smart memory card (SMC), a secure digital (SD) card, a flash memory card, etc. Of course, the memory 41 can also include both the internal storage unit of the computer device 4 and its external storage device. In this embodiment, the memory 41 is generally used to store the operating system and various application software installed on the computer device 4, such as computer-readable instructions of the engine-based process approval method. In addition, the memory 41 can also be used to temporarily store various types of data that have been output or are to be output.

[0226] In some embodiments, the processor 42 may be a central processing unit (CPU), a controller, a microcontroller, a microprocessor, or other data processing chip. The processor 42 is generally used to control the overall operation of the computer device 4. In this embodiment, the processor 42 is used to execute computer-readable instructions stored in the memory 41 or process data, such as computer-readable instructions for executing the engine-based process approval method.

[0227] The network interface 43 may include a wireless network interface or a wired network interface. The network interface 43 is generally used to establish a communication connection between the computer device 4 and other electronic devices.

[0228] The present application also provides another embodiment, namely, providing a computer-readable storage medium, which stores computer-readable instructions, and the computer-readable instructions can be executed by at least one processor to enable the at least one processor to perform the steps of the engine-based process approval method as described above.

[0229] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus the necessary general hardware platform, and of course can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), and includes a number of instructions for enabling a terminal device (which can be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in each embodiment of the present application.

[0230] Obviously, the embodiments described above are only some of the embodiments of the present application, rather than all of the embodiments. The preferred embodiments of the present application are given in the accompanying drawings, but they do not limit the patent scope of the present application. The present application can be implemented in many different forms. On the contrary, the purpose of providing these embodiments is to make the understanding of the disclosure of the present application more thorough and comprehensive. Although the present application has been described in detail with reference to the aforementioned embodiments, for those skilled in the art, it is still possible to modify the technical solutions described in the aforementioned specific embodiments, or to make equivalent replacements for some of the technical features therein. Any equivalent structure made using the contents of the present application specification and the accompanying drawings, directly or indirectly used in other related technical fields, is also within the scope of patent protection of the present application.

Claims

1. An engine-based process approval method, characterized in that: The steps include: If a process start request triggered by a user is received, extract the process code and user information from the process start request, and authenticate the user based on the user information; wherein the process start request carries the process code and the user information of the user; If the user passes the identity verification, the user's authority is verified based on the user information and the preset authority identification model; If the user passes the authority verification, the preset process processing page is displayed, and the process code and business data entered by the user in the process processing page are received; Starting a process instance corresponding to the process code and the business data in a preset process engine; Determine a target approver corresponding to the process instance, and generate a target approval task corresponding to the target approver based on the process instance; Sending the target approval task to the target approval personnel based on the process engine; receiving an approval operation performed by the target approver on the target approval task in a preset approval page, and generating a target approval result corresponding to the process instance based on the approval operation; Before the step of starting the process instance corresponding to the process code and the business data in the preset process engine, the method further includes: Acquire approval process configuration information corresponding to a designated process input by a target user; wherein the designated process is a process corresponding to the process code; Call the preset original process engine; Performing configuration processing on the approval process configuration information in the original process engine to obtain a configured original process engine; The configured original process engine is used as the process engine.

2. The engine-based process approval method according to claim 1, characterized in that: The step of authenticating the user based on the user information specifically includes: Collecting target biometric information corresponding to the user based on a preset biometric type; wherein the number of the biometric types includes multiple; Call the preset feature information library; Based on the user information, obtaining standard biometric feature information corresponding to the biometric feature type from the feature information database; Performing verification processing on the target biometric characteristic information based on the standard biometric characteristic information; If all the target biometric information passes the verification, it is determined that the user has passed the identity authentication; If all the target biometric information fails to pass the verification, it is determined that the user has failed the identity verification.

3. The engine-based process approval method according to claim 1, characterized in that: The step of verifying the user's authority based on the user information and the preset authority identification model specifically includes: Calling the permission identification model, and obtaining a target permission level corresponding to the user information based on the permission identification model; Determining a target business operation corresponding to the process code; Calling a preset business operation permission table, and querying the specified permission level range corresponding to the target business operation from the business operation permission table; Determining whether the target permission level is within the specified permission level range; If so, it is determined that the user has passed the authority verification; otherwise, it is determined that the user has not passed the authority verification.

4. The engine-based process approval method according to claim 1, characterized in that: After the step of generating a target approval result corresponding to the process instance based on the approval operation, the method further includes: Based on the process engine, updating the status of the process instance according to the approval result; Performing content analysis on the target approval result to obtain corresponding analysis results; Acquire a target processing strategy corresponding to the process instance based on the analysis result; The process instance is processed accordingly based on the target processing strategy.

5. The engine-based process approval method according to claim 1, characterized in that: After the step of generating a target approval result corresponding to the process instance based on the approval operation, the method further includes: Based on the preset exception capture statement, the exception capture process is performed at the key operation point of the process engine to obtain the corresponding exception information; Classify the abnormal information to obtain corresponding target abnormal information; Call the preset log storage system; The target exception information is stored in the log storage system.

6. The engine-based process approval method according to claim 1, characterized in that: After the step of generating a target approval result corresponding to the process instance based on the approval operation, the method further includes: Obtaining a performance indicator category corresponding to the process engine; Collecting target performance indicators corresponding to the performance indicator categories in the process engine based on a preset monitoring agent; Performing data analysis on the target performance indicators based on a preset monitoring and analysis tool to determine whether there are any abnormal indicators in the target performance indicators; If so, screening out the abnormal indicator from the target performance indicator, and generating corresponding abnormal warning information based on the abnormal indicator; The abnormal warning information is sent to the corresponding processing personnel.

7. An engine-based process approval device, characterized in that: include: A first processing module is configured to, upon receiving a process start request triggered by a user, extract a process code and user information from the process start request, and authenticate the user based on the user information; wherein the process start request carries the process code and the user information; A verification module, configured to verify the user's authority based on the user information and a preset authority identification model if the user passes identity authentication; A second processing module is configured to display a preset process processing page if the user passes the authority verification, and receive the process code and business data entered by the user on the process processing page; A startup module, configured to start a process instance corresponding to the process code and the business data in a preset process engine; A first generating module is configured to determine a target approver corresponding to the process instance, and generate a target approval task corresponding to the target approver based on the process instance; A first sending module, configured to send the target approval task to the target approval person based on the process engine; A second generating module is configured to receive an approval operation performed by the target approver on the target approval task in a preset approval page, and generate a target approval result corresponding to the process instance based on the approval operation; Among them, the engine-based process approval device also includes: A first acquisition module is configured to acquire approval process configuration information corresponding to a designated process input by a target user; wherein the designated process is a process corresponding to the process code; The first calling module is used to call the preset original process engine; A configuration module, configured to perform configuration processing on the approval process configuration information in the original process engine to obtain a configured original process engine; A determination module is configured to use the configured original process engine as the process engine.

8. A computer device, characterized in that: The process approval method comprises a memory and a processor, wherein the memory stores computer-readable instructions, and when the processor executes the computer-readable instructions, the steps of the engine-based process approval method as described in any one of claims 1 to 6 are implemented.

9. A computer-readable storage medium, characterized in that The computer-readable storage medium stores computer-readable instructions, which, when executed by a processor, implement the steps of the engine-based process approval method according to any one of claims 1 to 6.

Images