Business process approval method, computer equipment and readable storage medium

Abstract

The invention discloses a business process examination and approval method, computer equipment and a readable storage medium, and the method comprises the steps: determining first process configuration information of a first examination and approval process instance in response to the detection that an examination and approval process needs to be adjusted; according to first process configuration information of the first process approval instance, calling a configuration interface for the first process configuration information in a visual configuration interface, and changing the first process configuration information into second process configuration information in the configuration interface; generating a second process approval instance according to the second process configuration information; and executing examination and approval of the second process examination and approval instance. In this way, the technical problem that in the prior art, process approval lacks flexibility and dynamic adjustment ability is solved, and efficient adjustment and optimization in the business process approval process are achieved.

Description

Technical Field

[0001] The present invention relates to the technical field of workflow management, and in particular to a business process approval method, computer equipment, and computer-readable storage medium. Background Art

[0002] With the rapid development of enterprise informatization, business process management (BPM) systems are increasingly widely used across various industries. Traditional approval processes are typically statically configured, meaning all steps and conditions are pre-set when the process is created, and these settings are difficult to modify during operation. While this fixed process configuration approach can meet the needs of some standardized businesses, it can encounter the following challenges in actual operations. First, within the business environment, factors such as market fluctuations and internal policy adjustments can lead to frequent changes in the approval process. Traditional static configuration methods cannot quickly respond to these changes, resulting in insufficient process flexibility and impacting work efficiency. Specifically, the personalized needs of different departments or projects often require customized approval processes. However, existing systems often lack the ability to dynamically adjust, making it difficult to support flexible business models or diverse approval scenarios. Therefore, increasing the flexibility of business process approvals to improve work efficiency has become a pressing technical challenge. Summary of the Invention

[0003] The purpose of this application is to provide a business process approval method, computer equipment and computer-readable storage medium, which can solve the problems of insufficient flexibility and poor maintainability in traditional static process configuration methods.

[0004] To achieve the above objectives: In a first aspect, an embodiment of the present application provides a method, the method comprising: In response to detecting that the approval process needs to be adjusted, determining first process configuration information of the first approval process instance; According to the first process configuration information of the first process approval instance, calling a configuration interface for the first process configuration information in a visual configuration interface, and changing the first process configuration information to the second process configuration information in the configuration interface; Generate a second process approval instance according to the second process configuration information; Execute the approval of the second process approval instance.

[0005] In one embodiment, the method further comprises: Define the correspondence between approval items and approval process instances in the approval system; In response to receiving the pending approval item submitted by the first user on the business process interface of the approval system, generating an initial approval process instance corresponding to the pending approval item as the first approval process instance according to the corresponding relationship; or, In response to receiving the pending approval item submitted by the first user on the business process interface of the approval system, generating an initial approval process instance corresponding to the pending approval item as the first approval process instance according to the corresponding relationship; According to the current approval node corresponding to the first approval process instance, a user corresponding to the current approval node is determined as a second user, and the first approval process instance is sent to the second user, and the second user receives the first approval process instance; wherein the second user is a user authorized to approve the first approval process instance. In one embodiment, the approval process instance includes approval content information and approval node information; The method comprises at least one of the following: In response to detecting that the approval content information in the approval process instance does not satisfy the first preset condition, determining that it is detected that the approval process needs to be adjusted; In response to detecting a change in approval node information in the approval process instance, it is determined that a need to adjust the approval process is detected.

[0006] In one embodiment, the method further comprises: If it is detected that the approval item content information has been modified, it is determined that the first preset condition is not met; or, If it is detected that the numerical value information in the approval item content information exceeds the preset numerical value range, it is determined that the first preset condition is not met.

[0007] In one embodiment, the process configuration information includes: approval node information and approval condition information; In response to detecting that the approval process needs to be adjusted, determining first process configuration information of the first approval process instance includes: In response to detecting that the approval process needs to be adjusted, determining current first approval node information and current first approval condition information of the first process approval instance; Based on the current first approval node information and the current first approval condition information of the first process approval instance, second approval node information and second approval condition information subsequent to the node corresponding to the current first approval node information of the first process approval instance are determined; and the second approval node information and the second approval condition information are used as the first process configuration information.

[0008] In one embodiment, calling a configuration interface for the first process configuration information in a visual configuration interface based on the first process configuration information of the first process approval instance, and configuring the first process configuration information as the second process configuration information in the configuration interface includes: According to the first process configuration information of the first process approval instance, calling the visual configuration interface corresponding to the first process configuration information; Displaying the configuration items of the first process configuration information on the visual configuration display page; An input operation for a configuration item of the first process configuration information is received in the visual configuration interface, and the first process configuration information is modified to second process configuration information.

[0009] In one embodiment, the method further comprises: According to the first process configuration information, configuration items of the first process configuration information are automatically generated, and the configuration items are loaded onto the visual configuration interface.

[0010] In one embodiment, the method further comprises: After executing the approval of the item to be approved according to the second process approval instance, saving the second process approval instance; The definition of the correspondence between approval items and approval process instances in the approval system includes: A corresponding relationship between the approval items and the second approval process instance is defined in the approval system. In a second aspect, an embodiment of the present application provides a computer device, comprising: a processor and a memory storing a computer program, wherein when the processor runs the computer program, the steps of the above method are implemented.

[0011] In a third aspect, an embodiment of the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the above method are implemented.

[0012] The business process approval method, computer device and computer-readable storage medium provided in the embodiment of the present application include: receiving a pending approval item submitted by a first user, generating a corresponding first approval process instance based on the pending approval item and sending the first approval process instance to a second user for the second user to approve the process. When it is detected that the approval process needs to be adjusted, the system automatically determines the first process configuration information of the first approval process instance, retrieves the configuration interface for the first process configuration information in the visual configuration interface, so that the second user can modify the first process configuration information to the second process configuration information according to the configuration interface, and generates a new process approval instance based on the second process configuration information, i.e., the second process approval instance, and approves the second process approval instance. In this way, when it is detected that the approval process needs to be adjusted, the system can automatically determine the first process configuration information of the first approval process instance, and retrieves the configuration interface for the configuration information in the visual configuration interface, so that the second user can modify the first process configuration information to the second process configuration information according to the configuration interface. Based on this, the embodiment of the present application solves the technical problem of the lack of flexibility and dynamic adjustment capability of process approval in the prior art, and realizes efficient adjustment and optimization of the business process approval process.

[0013] That is to say, the embodiment of the present application improves the approval efficiency and flexibility by automatically generating new process approval instances and approving them; at the same time, it reduces the complexity of operation and reduces human errors by intuitively displaying and modifying configuration information with the help of a visual interface; in addition, the embodiment of the present application can automatically generate new approval process instances based on the second process configuration information, without the need for system programmers to update background programs, thereby ensuring the dynamic adaptability and efficient execution capabilities of the approval process.

[0014] The embodiments of this application not only solve the problem of existing process approval systems being difficult to adjust to changing requirements, but also significantly improve the system's intelligence level and user experience. Therefore, the embodiments of this application aim to provide a more flexible, efficient, and reliable business process approval method that can quickly respond to and complete approval tasks in complex and changing business environments, thereby providing strong support for improving the operational efficiency of enterprises. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] Figure 1 A flowchart of the approval process in the prior art; Figure 2 A flowchart of a business process approval method provided in an embodiment of the present application; Figure 3 A schematic diagram of a scenario in which multiple process configuration information of an approval process instance provided in an embodiment of the present application is configured; Figure 4A schematic diagram of a specific process flow of the business process approval method provided in an embodiment of the present application; Figure 5 A detailed diagram of the process flow configuration corresponding to the process instance provided in the embodiment of this application; Figure 6 An interaction diagram of the structured service and approval system provided in an embodiment of the present application; Figure 7 A diagram showing the approval details of the structured service and business system process provided in the embodiment of this application; Figure 8 A schematic diagram of the structure of a computer device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0016] Exemplary embodiments will be described in detail herein, with examples illustrated in the accompanying drawings. In the following description, when referring to the drawings, identical numerals in different figures represent identical or similar elements, unless otherwise indicated. The embodiments described in the following exemplary embodiments are not intended to represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.

[0017] It should be noted that, in this document, the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprising a ..." does not exclude the presence of other identical elements in the process, method, article or device comprising the element. In addition, components, features, and elements with the same name in different embodiments of the present application may have the same meaning or different meanings, and their specific meanings need to be determined based on their explanation in the specific embodiment or further combined with the context of the specific embodiment.

[0018] It should be understood that although the terms first, second, third, etc. may be used herein to describe various information, such information should not be limited to these terms. These terms are merely used to distinguish information of the same type from one another. For example, without departing from the scope of this document, first information may also be referred to as second information, and similarly, second information may also be referred to as first information. Depending on the context, the term "if" as used herein may be interpreted as "at the time of," "when," or "in response to a determination." Furthermore, as used herein, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context indicates otherwise. It should be further understood that the terms "comprising" and "including" indicate the presence of the described features, steps, operations, elements, components, items, types, and / or groups, but do not exclude the presence, occurrence, or addition of one or more other features, steps, operations, elements, components, items, types, and / or groups. The terms "or" and "and / or" as used herein are to be interpreted as inclusive, meaning any one or any combination. Thus, “A, B, or C” or “A, B, and / or C” means “any of: A; B; C; A and B; A and C; B and C; A, B, and C.” An exception to this definition occurs only when a combination of elements, functions, steps, or operations are inherently mutually exclusive in some manner.

[0019] It should be understood that, although the various steps in the flowchart in the embodiment of the present application are shown in sequence according to the indication of the arrows, these steps are not necessarily performed in sequence in the order indicated by the arrows. Unless clearly stated herein, the execution of these steps is not strictly limited in order, and they can be performed in other orders. Moreover, at least a portion of the steps in the figure may include multiple sub-steps or multiple stages, and these sub-steps or stages are not necessarily performed at the same time, but can be performed at different times, and their execution order is not necessarily performed in sequence, but can be performed in turn or alternately with at least a portion of other steps or sub-steps or stages of other steps.

[0020] It should be noted that in this article, step codes such as S101 and S102 are used for the purpose of expressing the corresponding content more clearly and concisely, and do not constitute a substantial limitation on the order. When implementing the step, those skilled in the art may execute S102 first and then S101, etc., but these should all be within the scope of protection of this application.

[0021] It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0022] In the subsequent description, the use of suffixes such as "module", "component" or "unit" to represent elements is only for the purpose of facilitating the description of the present application and has no specific meaning. Therefore, "module", "component" or "unit" can be used interchangeably.

[0023] It's important to note that in today's enterprise management, process approval is a critical step in ensuring compliance and efficient execution of business processes. However, existing process approval systems generally have limitations, particularly in terms of the flexibility and adaptability of processing approval information. These systems typically handle approval information independently within each business system. Consequently, when business requirements change, code modifications are required to adapt to these changes, which is not only inefficient but also prone to errors.

[0024] like Figure 1 As shown, the existing approval process usually includes the following steps: Extract data to be approved from the business system, and the system identifies data items to be approved based on specific rules or status tags.

[0025] Process business data according to business needs, including data validation, formatting or calculation to ensure that the data meets approval requirements.

[0026] The data to be approved is presented to the approver through the user interface. The approver can view all relevant information and details and decide whether to submit the approval request or directly approve or save it.

[0027] To process approval information, if it is the first approval, the system will create a new approval process instance, including setting the approval path and rules; if the approval process already exists, the system will continue to process the approval information through this process.

[0028] The system monitors the progress of the approval process and determines whether the current process has been completed; if the process has not ended, the system will push the approval information to the next approval link or approver according to the preset rules; the approval process ends after all necessary approval links are completed, which may be approval, rejection or other decision results.

[0029] However, the limitations of the existing approval system are mainly reflected in the following aspects: Lack of flexibility: Existing process approval systems often lack flexibility and struggle to adapt to the rapidly changing business environment. Each business system has its own approval process, resulting in non-shared approval information and increasing the complexity of development and maintenance.

[0030] Code dependencies: When business requirements change, the current approach is to modify the code to adapt to the new requirements. This approach is inefficient and prone to errors. Any code modification must go through the release, testing, and production process, which is not only time-consuming but also increases the risk of errors.

[0031] Difficulty in unified adjustment and management: Since each system is independent, it is difficult to make unified adjustments and management when the approval process needs to be adjusted.

[0032] Waste of resources: Each business system needs to independently implement the common functions of approving information, resulting in waste of resources.

[0033] Increased development workload: If there is a change in developers, the new developers will need to spend time understanding the original business system, which increases the development workload.

[0034] To address these issues, this paper proposes a new process approval method. By structuring approval information and introducing a visual configuration interface and rule engine, it enables dynamic adjustment of the approval process and efficient management of approval information. This method not only improves the flexibility and responsiveness of the approval process, but also significantly reduces the development workload, providing enterprises with a more efficient and intelligent business process approval solution.

[0035] The following is an explanation of the terms that may be involved in this application, as follows: Indicator: In the approval process of an approval process, an "indicator" can be understood as a minimum approval unit or a specific approval point, which represents the smallest information unit that needs to be evaluated and decided separately.

[0036] Group: A collection of one or more "indicators" that together constitute a larger approval unit. In the approval process, a group may contain multiple related approval indicators, which need to be considered as a whole.

[0037] Process: In the approval process, the term "process" can be understood as a larger approval unit composed of multiple "groups", or a collection of all approval information under a specific approval node.

[0038] Filter rule: It is a logical rule that consists of multiple expressions connected by logical operators (and, or, not) to determine whether all items in a set of data meet specific conditions and ultimately obtain a Boolean value result, that is, TRUE or FALSE.

[0039] Rule Engine: A rule engine is a patented system for executing rules. It processes a set of filter rules and returns the final result based on the logical relationship between these rules.

[0040] See Figure 2 , is a business process approval method provided in an embodiment of the present application. This method can be executed by a business process approval device provided in an embodiment of the present application. The device can be implemented in software and / or hardware. In this embodiment, the execution subject of the method is a computer device as an example. The method provided in this embodiment includes: Step S201: In response to detecting that the approval process needs to be adjusted, first process configuration information of the first approval process instance is determined.

[0041] An approval process instance refers to a specific execution process or running instance generated for a specific item to be approved during actual business processing. It is created from a predefined approval process template and dynamically configured based on the specific request content. For example, when a user submits a leave application, the approval system will generate a corresponding approval process instance based on the specific information requested (such as the number of days, applicant identity, etc.).

[0042] An approval item refers to an entire business request or work item submitted to the approval system for processing. For example, the sales department submits a contract agreement with an external partner. The items pending approval include details such as the contract content, amount, and duration of the agreement. Upon receiving this pending item, the approval system assigns it to an approval process, such as the legal or finance department, for review.

[0043] It's understandable that a pending item can be a single indicator or multiple indicators. A single pending item may contain multiple indicators, each requiring separate approval and decision-making. Each indicator can also serve as a separate pending item, particularly when dealing with small or single-item businesses. For example, in a procurement process, one indicator might be supplier qualification review, while another might be purchasing price reasonableness assessment. Both indicators belong to the same pending item: the purchase order request. Another example: a leave request might have only one indicator: employee request approval.

[0044] It's understood that a pending item can be a single group or multiple groups. For example, in one scenario, a budget adjustment is broken down into a single group containing multiple indicators, and this group can be submitted to the approval system as a single pending item. In another scenario, the budget adjustment is a separate pending item, composed of multiple groups, each handling different indicators. In effect, when a group is requested as a whole, it acts as a single pending item.

[0045] Here, the first process configuration information of the first approval process instance can be understood as information such as the multiple indicators or groups broken down within the approval items corresponding to the first approval process instance, as well as the predefined associations between indicators within the approval items corresponding to the first approval process instance, namely, filtering condition rules. For example, an indicator can be a node, and the first process configuration information of the first process approval instance can be the authorization node information corresponding to that approval process. For example, if the next approval authorization node in the leave request process is Zhang San, then the configuration information here can be Zhang San. For example, a filtering condition rule can be that if a leave request exceeds three days, the leave request process must be reviewed and authorized up to the department's highest supervisor, then the configuration information here can be filtering condition information. In short, process configuration information is the core data that defines, controls, and adjusts the operation of business processes. It not only determines how each step in the process is executed but also influences the flexibility and adaptability of the entire system. Especially when dynamic adjustments are required, effectively managing and utilizing this information is crucial to ensuring system stability and responsiveness.

[0046] Here, in response to detecting that the approval process needs to be adjusted, a change control operation for the approval process may be detected in the business process interface of the approval system, and then it is determined that the approval process needs to be adjusted.

[0047] Step S202: According to the first process configuration information of the first process approval instance, call the configuration interface for the first process configuration information in the visual configuration interface, and change the first process configuration information to the second process configuration information in the configuration interface.

[0048] Here, the visual configuration interface is an interface for viewing and editing process configuration information. The configuration interface supports dynamic updating of the first process configuration information to the second process configuration information, and the changed settings can be correctly identified and applied by the approval system.

[0049] It should be noted that, in the prior art, if the preset configuration information in the business process needs to be changed, it is often necessary to change the program code again and re-update the entire approval system before it can continue to be used.

[0050] Exemplarily, changing the first process configuration information to the second process configuration information in the configuration interface may include: after detecting that the user has completed the modification and clicking the "Save" button, instructing to change the first process configuration information to the second process configuration information in the configuration interface; the method also includes: the system will send the changed configuration information, i.e., the second process configuration information, to the back-end service; the back-end service will verify the data, such as verifying whether the format is legal, checking whether there are conflicting or redundant settings, and after the verification is passed, updating the process configuration of the approval instance in the approval system.

[0051] It should be understood that the second process configuration information is applicable to the subsequent first approval process and is not applicable to the completed first approval process, so as to ensure the validity of the previously completed approval process and improve the system approval efficiency.

[0052] Step S203: Generate a second process approval instance according to the second process configuration information.

[0053] It should be understood that the backend service can create an API interface, where the API interface is used to obtain and update process configuration information; use Resiful API or GraphQL to achieve interaction; at the data layer, a database can be used to store process configuration information, which can be quickly queried based on the instance ID.

[0054] Illustratively, generating the second process approval instance according to the second process configuration information may include: the backend service updates the process configuration information through an API interface according to the second process configuration information and generates the second process approval instance.

[0055] Step S204: Execute the approval of the second process approval instance.

[0056] In some implementations, step S204, i.e., executing the approval of the second process approval instance, includes: Automatically generate approval result information for the second process approval instance based on the first network model; The approval of the second process approval instance is executed according to the approval result information.

[0057] The first network model here can be obtained by collecting relevant data from historical approval processes, such as input information of historical approval instances, approval results, and intermediate states during the approval process. After cleaning and standardizing the collected data, it is trained using a basic model to obtain a network model suitable for the approval system. Approval results here include but are not limited to approval conclusions (i.e., approval or disapproval, pass or fail), as well as approval opinions. Of course, the first network model here can also directly call on existing large models, such as those provided by DeepSeek, Doubao, or Kimi.

[0058] The input information of the historical approval instance here can be the opinion information input in the historical approval instance, as well as the configuration information of the historical approval instance, etc. By learning and training the historical approval process, a first network model that can directly obtain approval result information more accurately is obtained.

[0059] Here, the approval result information may include: consent information and default opinion information. For example, taking the approval process as a leave application process, the opinion information here may be, for example, "Please ask the person applying for leave to arrange urgent matters."

[0060] In some embodiments, executing the approval of the second process approval instance according to the approval result information includes: displaying the approval result information on the approval interface of the second process approval instance according to the approval result information; and completing the approval of the second approval instance in response to determining that the approval result information is correct.

[0061] Exemplarily, if a confirmation operation for the approval result information is received, it is determined that the approval result information is correct.

[0062] It should be noted that the approval result information for the second-process approval instance is automatically displayed on the approval interface. Confirmation can be achieved by clicking the "Submit" control on the approval interface, or any other action that can be used to confirm the approval result information. Therefore, if the current approver has no objection to the approval result automatically generated using the first network model, they can simply click the "Submit" button to complete the approval process for the second-process approval instance.

[0063] In some implementations, if a modification operation on the approval result information is received, the modification result of the approval result is received; and the approval of the second process approval instance is executed according to the modification result information.

[0064] Thus, in this embodiment, the approval of the second process approval instance will automatically present the approval result information by introducing the network model, thereby reducing the manual approval input of the approver and improving the approval efficiency.

[0065] In summary, the configuration based on dynamic adjustment of the approval process provided by the embodiment of the present application can realize efficient management and real-time update of approval process configuration information through a visual configuration interface and dynamic loading function, which has the following significant advantages over the existing technology: First, traditional approval process management requires modification at the code level to realize process changes, which not only increases maintenance costs but also leads to a longer technical intervention cycle. The embodiment of the present application provides a dynamic configuration function of the visual configuration interface, allowing users to flexibly adjust and optimize the approval process without modifying any code. This feature of not requiring code intervention greatly reduces the cost of system maintenance and improves the work efficiency of system administrators. Secondly, the needs of enterprises often need to be constantly adjusted as the market environment changes. The traditional static approval process is difficult to respond to these changes quickly. The embodiment of the present application provides a dynamic adjustment function, which enables the approval process to be optimized in real time according to the actual needs of the enterprise. For example, adding or deleting approval nodes, adjusting the process sequence, and other operations can all be completed on the visual interface. This high flexibility enables the system to adapt to various complex and changing business scenarios. Finally, in traditional approval process management, omissions may occur in code modifications, resulting in process configuration errors, which in turn affect the normal operation of the entire system. The embodiment of the present application provides the function of dynamically loading form fields and performs verification and prompts during the loading process, which can effectively reduce the possibility of human operational errors and reduce the risk of system errors. At the same time, the friendly design of the visual configuration interface also reduces dependence on technical personnel, further reducing overall maintenance costs.

[0066] Therefore, the embodiments of the present application not only solve the problem of the existing process approval system being difficult to adjust to changing needs, but also greatly improve the system's intelligence level and user experience. Therefore, the embodiments of the present application aim to provide a more flexible, efficient, and reliable business process approval method that can quickly respond to and complete approval tasks in a complex and changing business environment, thereby providing strong support for improving the operational efficiency of enterprises.

[0067] Exemplarily, step S201, i.e., in response to detecting that the approval process needs to be adjusted, determining first process configuration information of a first approval process instance, includes: querying instance information of the first approval process instance, such as an identifier, a node status, and a filtering condition mapping set of the first approval process instance, based on the first approval process instance; obtaining first static configuration information related to the first approval process instance based on the identifier and the node status; obtaining dynamic configuration information related to the first approval process instance based on the filtering condition mapping set, the dynamic configuration information including mapping information between the filtering condition and the second static configuration information; and determining the first process configuration information of the first approval process instance based on the first static configuration information and the dynamic configuration information.

[0068] Furthermore, according to the filtering condition mapping set, dynamic configuration information related to the first approval process instance is obtained, including: according to the filtering conditions in the filtering condition mapping set, selecting the process configuration that meets the filtering conditions and is not configured with other filtering conditions as the second static configuration information with mapping information with the filtering conditions; according to the second static configuration information and the true filtering conditions, determining the dynamic configuration information related to the first approval process instance.

[0069] Furthermore, according to the filtering conditions in the process condition mapping set, if there are multiple process configurations that meet the filtering conditions and are not configured with other filtering conditions, the priority of the process configuration is obtained; and the process configuration with the highest priority is selected as the second static configuration information with mapping information with the filtering conditions.

[0070] In other implementations, determining the first process approval information of the first approval process instance may include: querying the process configuration of the first approval process instance, querying the indicators and groups, and thereby determining the first process approval information of the first approval process instance.

[0071] In some embodiments, the method further comprises: Define the correspondence between approval items and approval process instances in the approval system; In response to receiving a pending approval item submitted by a first user on a business process interface of the approval system, generating an initial approval process instance corresponding to the pending approval item as the first approval process instance according to the corresponding relationship; or, In response to receiving the pending approval item submitted by the first user on the business process interface of the approval system, generating an initial approval process instance corresponding to the pending approval item as a first approval process instance according to the corresponding relationship; According to the current approval node corresponding to the first approval process instance, a user corresponding to the current approval node is determined as a second user, and the first approval process instance is sent to the second user, and the second user receives the first approval process instance; wherein the second user is a user authorized to approve the first approval process instance.

[0072] The second user refers to a specific user or role authorized to handle the first approval process instance under pre-defined permissions and responsibilities. The second user here typically refers to the person responsible or approver with review authority for the approval item. For example, the second user can also be the first user. For example, the first user is the initiator of the approval item, and the initiator approves the first node before the process moves to the next node.

[0073] For example, when an employee submits a leave request, a pending approval item, the approval system identifies the specific content and attributes of the request and determines that it must be processed through the approval process. Based on pre-set approval rules, the approval system automatically generates a corresponding first-level approval process instance, which includes information such as specific approval steps, time points, and reference personnel. Based on permission allocation rules, the system determines a second user, the authorized approver for this approval process instance. For example, in the case of a leave request, the second user might be the employee's direct supervisor. After receiving notification, the second user can review the pending approval item within their authority. For example, after reviewing the specific information of the leave request, the second-level approver may approve the employee's request and submit it to the next approver.

[0074] Here, the first user and the second user can be the same user, or different users. The second user can be the first-level reviewer of the first user. In this embodiment, the first approval process instance can be configured directly by the first user, or the second user can configure the first approval process instance when the process is transferred to the second user in the middle. Compared with the prior art, which can only be configured by the process initiator, the embodiment of the present application can be flexibly configured by the second user during the process flow, which can improve the efficiency of the process. For example, when Zhang San initiates a financial review and approval matter as the first user, when the process flows to the third node, it is found that the reviewer corresponding to the fourth node has resigned. Then, the reviewer of the third node can reconfigure the approval matter. By modifying the reviewer of the fourth node, the approval matter can continue to be executed without having to re-initiate the process or wait for the background program personnel to change the information of the fourth node. Therefore, the approval efficiency of the enterprise approval process can be improved.

[0075] It should be noted that manual confirmation is often required to determine whether the approval process needs to be adjusted, but manual confirmation still has some errors. For example, people at the previous process nodes may not know the situation of people at the next process nodes, or in the process of cross-departmental process approval, different departments may have different process approval rules, or there may be differences in screening conditions. For example, the sales department is not clear about the amount limit of financial audits.

[0076] Based on this, in order to improve the efficiency and accuracy of process approval, in some embodiments, the approval process instance includes: approval content information and approval node information. The approval content information here can be, for example, a financial limit, specific approval content, etc., and the approval node information can be the approver, approver attributes, etc.; the method includes at least one of the following: In response to detecting that the approval content information in the approval process instance does not meet the first preset condition, it is determined that the approval process needs to be adjusted; in response to detecting that the approval node information in the approval process instance has changed, it is determined that the approval process needs to be adjusted; the change in the approval node information here may be, for example, the resignation, demotion or promotion of the approver corresponding to the approval node.

[0077] In some embodiments, the method further comprises: If it is detected that the content of the approval item has been modified, it is determined that the first preset condition is not met; or, If it is detected that the numerical value information in the approval item content information exceeds the preset numerical value range, it is determined that the first preset condition is not met.

[0078] The content information here can be, for example, the content of approval process matters, such as changes in the number of leave days or changes in the reason for leave in a leave matter, such as changes in the purchase items in a financial request matter, all of which belong to the content of matters in the approval process; when the content of these approval matters changes, it can be automatically identified as the need to adjust the approval process.

[0079] The numerical information here exceeds the preset numerical range. For example, the number of leave days requested by the employee requesting the item exceeds the preset range, such as 5 days, or the financial amount in the financial request item exceeds the preset amount. It will be automatically identified as an approval process that needs to be adjusted.

[0080] In this way, there is no need for human intervention to determine whether the approval process needs to be adjusted, which can make the configuration of the approval process more intelligent, efficient and flexible.

[0081] In some embodiments, the process configuration includes: approval node information and approval condition information; In response to detecting that the approval process needs to be adjusted, determining first process configuration information of the first approval process instance includes: In response to detecting that the approval process needs to be adjusted, determining current first approval node information and current first approval condition information of the first approval process instance; Based on the current first approval node information and the current first approval condition information of the first process approval instance, determine the second approval node information and the second approval condition information subsequent to the node corresponding to the current first approval node information of the first process approval instance; and use the second approval node information and the second approval condition information as the first process configuration information.

[0082] Thus, in this embodiment, by adjusting only the second approval node information and the second approval condition information, repeated approval of existing approved nodes can be avoided during the adjustment process, thereby ensuring the continuity of the existing approval process, avoiding interruption of matters being processed, and improving process approval efficiency.

[0083] In other words, the technical solution provided by the embodiment of the present application can ensure that existing process instances are not affected by the new configuration, that is, the dynamically adjusted new process only affects the subsequently generated process instances, avoiding the situation where the initiated process is terminated or confused due to configuration changes, thereby improving the stability of the entire system operation and the efficiency of approval processing.

[0084] In some embodiments, based on the first process configuration information of the first process approval instance, calling the configuration interface for the first process configuration information in the visualization configuration interface, calling the configuration interface for the first process configuration information in the visualization configuration interface, and configuring the first process configuration information as the second process configuration information in the configuration interface includes: According to the first process configuration information of the first process approval instance, calling the visual configuration interface corresponding to the first process configuration information; Displaying the configuration items of the first process configuration information on the visual configuration display page; An input operation for a configuration item of the first process configuration information is received in the visual configuration interface, and the first process configuration information is modified to the second process configuration information.

[0085] In some embodiments, the method further comprises: According to the first process configuration information, configuration items of the first process configuration information are automatically generated, and the configuration items are loaded onto the visual configuration interface.

[0086] Here, calling the visual configuration interface requires the front-end to dynamically load the corresponding form or other visual components based on the first process configuration information. For graphical editing tools, process design frameworks (such as draw.io or Activiti Modeler) can be used to implement drag-and-drop editing. For example, the nodes and rules of the current approval process are displayed. Users can modify the node order, add conditions, and so on by clicking or dragging.

[0087] The input operation here may be a selection operation on the visual component of the first process configuration information, or an operation such as clicking or dragging in a graphic editing tool.

[0088] Exemplarily, changing the first process configuration information to the second process configuration information in the configuration interface can be done by submitting an interactive form, allowing the user to modify any field in the first process configuration information, for example, adjusting the review role, such as changing from department head to financial director, dynamically generating form fields, and automatically displaying the editing area if a byte has sub-conditions; if it is graphical editing, the user can directly drag nodes or delete / add new rules.

[0089] In this way, the embodiment of the present application manually configures the configuration items of the first process configuration information displayed on the visual configuration display page, which can significantly lower the technical threshold and eliminate the need for tedious development work. Only simple configuration is required to meet the needs.

[0090] It should be added that the configuration items of the first process configuration information are automatically generated based on the first process configuration information, and the configuration items of the first process configuration information can be automatically generated based on the first process configuration information and the second network model. It should be noted that there are multiple configuration items of the first process configuration information. For example, for process node items, there are many reviewers to choose from, and users are often required to manually find or search. In this embodiment, by introducing the second network model, the configuration items that the user may need can be accurately loaded through learning and training, reducing the loading of unnecessary configuration items.

[0091] The second network model here can be a recurrent neural network (RNN), a long short-term memory network (LSTM) or a graph neural network (GNN). The second network model can be trained in advance and set in the approval system. When the configuration interface displays the first process configuration information that needs to be adjusted, it can intelligently retrieve and load the necessary configuration items of the first process configuration information for the user to select and modify, etc., thereby improving the efficiency of process configuration and thus improving the efficiency of process approval.

[0092] It should be noted that the second network model and the first network model here can be the same network model or different network models, and no limitation is made here.

[0093] In some embodiments, the method further comprises: After executing the approval of the items to be approved according to the second process approval instance, save the second process approval instance; The definition of the correspondence between approval items and approval process instances in the approval system includes: The corresponding relationship between the approval items and the second approval process instance is defined in the approval system.

[0094] In other words, the system will use the new process configuration as the process for the next process approval matter, so there is no need to reconfigure it every time, thereby improving the efficiency of process review.

[0095] Based on the same inventive concept as the above embodiments, the above embodiments are described in detail below through a specific application scenario: It should be noted that the devices involved in this embodiment include but are not limited to: a computer; a Java virtual machine, the computer is used to run the Java virtual machine and configure PC programs; the Java virtual machine is used to compile and run Java programs.

[0096] For example, see Figure 3 , Figure 3 A schematic diagram of a scenario in which multiple process configuration information for an approval process instance is configured; as shown in the figure: Indicators can include approval indicators, such as former employees, suspected agents, domestic middlemen, new industry customers, legal collection, basic information lines, etc., and the smallest unit is defined by pre-defining approval indicators; groups can include approval groups, such as basic information group, blacklisted customer group, contract content clause group, low-risk clause group, payment information, service terms, etc., and group configuration is achieved by configuring approval groups; processes can include approval processes, such as business review process, credit review process, legal review process, credit insurance review process, credit inspection process, fund inspection process, etc., and process configuration is achieved by configuring approval processes; further, processes can also be configured, such as contract process, delivery process, financial process, customer process, and accessories process, and the links in these processes can be configured at the same time, such as business review link, credit review link, legal review link, credit review link, credit insurance review link, fund review link, etc.; in addition, approval results can also be configured, for example, the approval results can be inspection opinions, such as pass, fail, and opinion information, etc.; approval information records can also be included.

[0097] It's important to understand that within the approval process, an "indicator" can be considered the smallest approval unit or a specific approval point. This indicator consists of multiple elements, including display text, inspection results, control requirements, and attachments. If the text contains changes to business data, variable fields are used as placeholders. The variable field values ​​are retrieved through a configured API to replace the original placeholders. For inspection results and control requirements, drop-down boxes, checkboxes, and text box combinations are provided to accommodate diverse information entry needs. If a radio button requires a default option, an expression can be used. To determine whether an indicator is displayed during the approval process, configuration rules are introduced. These rules consist of multiple expressions, both sides of which can contain variables. When querying a specific approval process, simply substitute the variable values ​​in the configured rule into the expression. The resulting "true" or "false" value determines whether the indicator is displayed. Furthermore, the display order of indicators can be configured to display information in a specific order. By configuring the indicator type, information can be divided into different areas for display, such as routine matters, key matters, upgrade matters, etc., and new types can be added as needed. In terms of attachments, the attachment display and mandatory status of indicators can be configured to meet different business needs. At the same time, by configuring the risk level, the mandatory status of information items in the approval process can be controlled to ensure the integrity of key information. Finally, it also supports the configuration of the association between business document numbers and businesses, so that relevant information can be easily processed in special scenarios. This design makes the approval process more flexible and efficient, and can better meet the actual needs of the enterprise.

[0098] Approval Group: An approval information group is a collection of multiple indicators, and can also be flexibly configured to correspond to a single indicator per group. During the display of approval information, the group name is not fixed but can be dynamically changed to the desired group name through the interface, enhancing the flexibility and customizability of approval information.

[0099] Approval process: A larger approval unit composed of multiple "groups." The approval process offers a high degree of flexibility, allowing you to precisely specify a single approval link or incorporate multiple types of approval links, with a separate approval process for each type. For example, you can define three separate approval processes for high-risk, medium-risk, and low-risk approval categories. These approval processes are closely linked to the approval information group to ensure a smooth approval process. This design not only improves approval efficiency but also makes the entire approval system more rigorous and standardized.

[0100] Approval process: When configuring the approval process, in addition to associating the corresponding approval process, you also need to set the approval process number, link number or specific category number to ensure the accuracy and traceability of the process. At the same time, it is necessary to clarify the document type to specify which business system the approval process applies to. The approval type needs to clarify whether the link point is final review, functional node or non-final review, etc., to meet the needs of different approval levels. In addition, the designation of the business type is also crucial. It determines whether the process link belongs to the fields of business, legal affairs, credit insurance, credit, services, etc., or other newly added business types. This setting is intended to enable accurate approval division according to business type during the final approval, to ensure the rationality and effectiveness of the approval results. Through such detailed configuration, the approval process can run more efficiently and in a standardized manner.

[0101] Approval result processing: Approval results are mainly divided into two categories, namely opinion information and approval information records. Opinion information records in detail the approval results, approval opinions, and key information such as return operations, jump approval nodes, and forwarding of the process links. The approval information record archives the configured approval information and the inspection results of each indicator, including a collection of attachments and other information. In the approval process, a high degree of flexibility is provided, and new approval information groups can be added dynamically. This function relies on the original configured approval information group. Users can create a new information group by copying the original group, and the approver will fill in the relevant content. In addition, we also support the dynamic addition of new indicator rows in the approval information group to form a new evaluation dimension. This operation can be easily achieved by simply specifying that these new indicators belong to the same information group when submitting. This design makes the approval process more flexible and efficient, and can better meet diverse approval needs.

[0102] In this embodiment, by structuring the process configuration information, that is, structuring the process configurations in various approval process instances, it is convenient to perform flexible configuration and dynamic adjustment in each process, thereby achieving efficient adjustment and optimization of the business process approval process.

[0103] Specifically, based on the same inventive concept as the above-mentioned embodiment, the above-mentioned embodiment is described in detail below through a specific example. In this example, the purchase order is taken as the item to be approved, and the configuration information of the process instance including the review node, review content and review conditions in the purchase order is used as an example for explanation.

[0104] Please refer to Figure 4 ,like Figure 4 As shown: Step 41: Process instance initialization.

[0105] For example, when a user submits a purchase order for, say, 800,000 yuan, the review system generates an initial approval process instance based on the predefined "Purchase Approval - Standard Process" mapping relationship. This is the first approval process instance described above. Configuration information for this approval process instance can include approval indicator groups, approval nodes, and business types. Approval indicator groups include price verification indicators (with a threshold of 1 million yuan or less) and supplier qualification indicators (including variable placeholders). Indicator nodes can include preliminary procurement review and final financial review. Business types can be associated with standard procurement types. In other words, since the 800,000 yuan here is less than or equal to 1 million yuan, it meets the existing price verification criteria. If it doesn't, such as for purchases exceeding 1 million yuan, an adjustment to the approval process will be triggered.

[0106] Step 42: Dynamically adjust the trigger.

[0107] Assuming the purchase amount is changed to 1.5 million yuan, two conditions will trigger the detection that the approval process needs to be adjusted. One condition is that the purchase amount is changed from 800,000 yuan to 1.5 million yuan, and the other condition is that it exceeds 1 million yuan. At this time, a new process configuration needs to be made for the existing approval process instance.

[0108] Step 43: Visualize configuration changes.

[0109] The specific operation process may include: first call the visual configuration interface, see Figure 5 ,like Figure 5 As shown, the process configuration details diagram corresponding to the current first approval process instance is loaded.

[0110] Specifically, Figure 5 The detailed description of each part is as follows: When configuring indicator information, we introduce the concept of indicator classification. This is primarily to clarify the data sources that placeholder field variables rely on. These data sources may come from various sources, such as API calls, fixed value settings, or dictionary selections. By clearly defining indicator categories, we can clearly define the usage scenarios and rules for each data source, ensuring that the required data source can be accurately selected and referenced during the configuration process.

[0111] Configuring dictionaries involves determining the numbers and corresponding values ​​of all dictionaries required for the entire approval process.

[0112] Configuration rules are composed of multiple expressions, with variables used on both sides of the expressions as placeholders. Variables are defined through configuration dimensions.

[0113] Configuration dimensions are composed of multiple expressions that form a rule, with variables used on both sides of the expressions as placeholders. Variables are defined through configuration dimensions.

[0114] Configure approval indicator information. You need to set a series of display text information, including but not limited to the indicator name, inspection results, control requirements, and attachments. If business data varies, you can use variable field placeholders in the display name text or configure front-end processing logic to enable direct escape processing. For inspection results and control requirements, a wide range of configuration options are available, including drop-down boxes, checkboxes, and combinations with text boxes. In particular, for radio buttons, you can configure expressions to automatically select default options. Furthermore, you can configure rules to filter indicators to meet the needs of different business scenarios. Within the indicator configuration, you can also set display sorting to display information in a specific order within the approval interface. By configuring the indicator type, you can also display information in different areas. You can also configure attachment display and mandatory fields for indicators to meet the needs of different business documents. During configuration, you can also set risk levels and control measures that must be present for information items required by the control rules to ensure the rigor and compliance of the approval process. Finally, you can associate business document numbers with business transactions, allowing you to quickly locate relevant business information and approval processes when handling special scenarios.

[0115] By configuring approval information groups, you can associate one or more approval indicators to meet the needs of different approval processes. In addition, group names can be customized and support the use of placeholder field values, allowing for more flexible adaptation to various business scenarios.

[0116] To configure the approval process, you can associate one or more approval information groups to build an approval process that meets business needs.

[0117] By configuring the approval process, one or more approval processes can be associated to build an approval framework that adapts to various business needs. Among them, the main configuration item represents the number, process node or approval category of the entire process, providing a clear identification for the approval process. In order to clarify the business system to which the current configuration belongs, the document type is also configured to ensure seamless integration of the approval process and the business system. At the same time, by configuring the approval type, you can accurately specify whether each link is a final review, a functional node or a non-final review, etc., to meet the needs of different approval levels and roles. In addition, business types are specially configured to clarify the business areas to which the process links belong, such as commerce, legal affairs, credit insurance, credit, services, accessories, finance, tickets, etc.

[0118] For the above embodiment, during the operation of visual configuration modification, the first process configuration information of the current approval process instance can be loaded by calling the visual configuration interface, for example, the node sequence is from the initial review of procurement to the financial terminal; the effective rule amount is loaded to be less than or equal to 1 million. Furthermore, at least one of the following changes can be performed: inserting a node, that is, adding a node such as the audit department review before the financial final review; modifying the rule: such as adjusting the threshold to 2 million; adding a new indicator, such as adding a large-scale procurement audit indicator group, so as to call the structure corresponding to the audit process of the audit group to directly reuse the audit process of the audit group in the procurement process. This embodiment supports the modification of the entire process information through the configuration interface without the need for code changes, and supports the configuration of indicator default values ​​through expressions, so that the process configuration can be flexibly performed, the efficiency of the process review is improved, and the work efficiency of the enterprise is improved.

[0119] Step 44: Generate and execute a new process instance.

[0120] The approval system generates a second process instance based on the new process configuration information. For example, the updated node path is: procurement initial review to audit department compliance to financial final review; the dynamically loaded audit indicator group can be replaced with quarterly audit through the interface; the rule engine validation includes, for example, applying the new rule 150 less than or equal to 200 at the final review node to determine approval, hiding the small purchase exemption condition in the original process.

[0121] Specifically, see Figure 6 , Figure 6 The interaction diagram of the structured service and approval system provided in the embodiment of this application is as follows: Figure 6 As shown, it can be seen that in the process approval interface of the third-party business system (i.e., the approval system mentioned above), by checking the process to be approved, the process configuration information of the process instance to be approved can be called through the SDK or HTTP interface. Specifically, the new process configuration information to be configured is called through the structured service, so that it can be directly generated and run in the third-party business system to directly perform process approval. Therefore, there is no need for system programmers to update the background program, which can ensure the dynamic adaptability and efficient execution capability of the approval process.

[0122] Step 45: Processing and tracing of approval results.

[0123] Specifically, see Figure 7 , Figure 7 The structured service and business system process approval details diagram provided in the embodiment of this application are as follows: Figure 7 As shown, the business system here is equivalent to the approval system described above. In this embodiment, a structured configuration is performed for process approval, such as whether the approval record needs to be deleted, only the opinions are saved, and the specific background operations for saving opinions and suggestions.

[0124] Specifically, when a third-party system, such as the business approval system, is performing an approval, it needs to query relevant approval information. At this point, it is necessary to enter the process number and node number (or status value). If there are specific filtering conditions, the corresponding business set map must also be entered.

[0125] Common interface implementation: It can be called by referencing the SDK package or HTTP interface.

[0126] The first step is to obtain the corresponding configuration information based on the passed parameters; The second step is to check whether there are any filtering conditions at the process level. If there are no conditions configured, jump directly to the fifth step; In the third step, for processes configured with process-level filtering conditions, the rule engine service is used to process them and determine whether the results are "true" or "false". The process configurations with "true" results and no filtering conditions are retained. Step 4: If there are multiple process layers, the process configuration with the highest priority is selected based on the set priority conditions; Step 5: Then, check whether the indicator reference value rules (i.e., indicator filtering conditions) are configured. For configured indicators, their expression lists and the variable set values ​​involved in the formula are passed to the rule engine service to obtain a set of "true" or "false" results. Indicators with "true" results and no filtering conditions are configured are retained; Step 6: Sort the final data according to the order of the indicators; Step 7: If it is an SDK call and the variable placeholder interface of the indicator name and group name is implemented, the variables and values ​​in the interface are replaced; Step 8. Finally, return the result set to the business system.

[0127] Special pending approval information query function: You can query the process and group information after the filtering conditions set at the process level are processed; you can query the indicator information after filtering according to the process or group and the indicator conditions.

[0128] During process approval, the calling scenarios mainly include: During the withdrawal process, if you only need to save the comments, call the interface for saving only the comments; When withdrawing to the starting node, all withdrawn nodes can be deleted according to the business party's requirements; During the approval process, each node only needs to display the last approval information; when viewing details, all previous approval records need to be queried. According to the specific situation, the corresponding value is passed in and the deletion interface is called; In normal scenarios, save comments and approval information records.

[0129] Data processing mainly includes: deletion, saving only opinions, and approval opinions and approval information record processing.

[0130] Deletion processing, including: The processing of approval records includes two aspects: one is to verify and record its validity, and the other is to execute the operation of deleting the record.

[0131] If approval records need to be processed, the approval opinion information also covers two processing levels: one is to confirm and process the validity only, and the other is to perform the record deletion operation.

[0132] Saving only comments includes: storing only comment information.

[0133] The processing of approval opinions and approval information records includes: Process the approval opinion information. If the approval opinion ID is not passed, the system will add a new approval record. If the approval opinion ID is passed, the system will modify the corresponding approval record based on the ID. Finally, whether adding or modifying, the approval opinion ID will be included in the record queue of pending approval information. Process the approval record information. If the approval record ID is not provided, the current record is considered a new item. If the approval record ID is provided, the current approval record is considered to be updated. Subsequently, for those corresponding records with opinion IDs, all approval records except those marked as modified will be deleted; Determine based on the parameters passed in: whether to dynamically add new groups and related new indicators Attachment information and backup record information are processed asynchronously.

[0134] Query approval records, including: General query, you can query all approval information by process number, document number or single / multiple nodes The last approval information of each node. If a node is approved multiple times during the withdrawal process, only the last approval information will be returned; Comprehensive decision-making: Divide the business types into groups according to the indicators, and return the latest approval opinions and approval record information for each business type.

[0135] Special query interface functions include: No filter condition query: Ignore all configured filter conditions, priorities, sorting, etc., and directly query all pending approval information according to the configuration; Query by indicator number: You can query the information of a single indicator according to the indicator number; Query by process configuration: You can query relevant information of process configuration.

[0136] In this way, by separately storing the approval opinions and approval indicator structures, large-scale procurement business is bound to the new process template, so that when this type of business process is used later, the newly saved process configuration can be quickly called, thereby improving the efficiency of process review.

[0137] In summary, the method provided in the above embodiment, through the three core innovations of structured approval information, dynamic decision-making of rule engine, and zero-code visual configuration, the problem of rigid process in traditional approval system is solved by dynamic expansion through four-level configuration system, and the problem of high maintenance cost in traditional audit system is solved by eliminating hard coding through SDK access and variable replacement. The decision-making blind spots in traditional audit system are solved by covering complex scenarios through multi-rule composite judgment. At the same time, the full-link traceability is achieved through structured storage and version snapshots to solve audit risks and other problems.

[0138] Based on the same inventive concept as the above embodiments, an embodiment of the present invention provides a computer device, such as Figure 8 As shown, the device includes: a processor 310 and a memory 311 storing a computer program; wherein, Figure 4 The processor 310 shown in the figure is not used to indicate that the number of processors 310 is one, but is only used to indicate the positional relationship of the processor 310 relative to other devices. In actual applications, the number of processors 310 may be one or more; similarly, Figure 4 The memory 311 shown in the figure has the same meaning, that is, it is only used to refer to the position relationship of the memory 311 relative to other devices. In actual application, the number of memories 311 can be one or more. When the processor 310 runs the computer program, the method applied to the above device is implemented.

[0139] The device may also include: at least one network interface 312. The various components in the device are coupled together via a bus system 313. It is understood that the bus system 313 is used to achieve connection and communication between these components. In addition to the data bus, the bus system 313 also includes a power bus, a control bus, and a status signal bus. However, for the sake of clarity, Figure 4 Various buses are labeled as bus system 313.

[0140] Memory 311 may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. Non-volatile memory may include read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), ferromagnetic random access memory (FRAM), flash memory, magnetic surface memory, optical disk, or compact disc read-only memory (CD-ROM); magnetic surface memory may include magnetic disk or tape memory. Volatile memory may include random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static random access memory (SRAM), synchronous static random access memory (SSRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct rambus random access memory (DRRAM).The memory 311 described in the embodiments of the present invention is intended to include, but is not limited to, these and any other suitable types of memories.

[0141] The memory 311 in this embodiment of the present invention is used to store various types of data to support the operation of the device. Examples of this data include: any computer programs used to operate on the device, such as the operating system and application programs; contact data; phone book data; messages; images; videos, etc. The operating system includes various system programs, such as the framework layer, core library layer, and driver layer, which implement various basic services and handle hardware-based tasks. Application programs may include various applications, such as media players and browsers, which implement various application services. Here, the program implementing the method of the embodiment of the present invention may be included in the application program.

[0142] Based on the same inventive concept as the above-mentioned embodiment, this embodiment further provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program. The computer-readable storage medium may be a magnetic random access memory (FRAM), a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a flash memory, a magnetic surface memory, an optical disc, or a compact disc read-only memory (CD-ROM); or various devices including one or any combination of the above-mentioned memories, such as a mobile phone, a computer, a tablet device, a personal digital assistant, etc. When the computer program stored in the computer-readable storage medium is executed by a processor, the above-mentioned method is implemented. For the specific steps implemented when the computer program is executed by the processor, please refer to Figure 2 The description of the illustrated embodiment will not be repeated here.

[0143] The technical features of the above-mentioned embodiments can be combined arbitrarily. In order to make the description concise, not all possible combinations of the technical features in the above-mentioned embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0144] As used herein, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion of elements other than the listed elements and may also include additional elements not specifically listed.

[0145] The above description is merely a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any modifications or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in the present invention should be included in the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be based on the scope of protection of the claims.

Claims

1. A business process approval method, characterized in that: include: In response to detecting that the approval process needs to be adjusted, determining first process configuration information of the first approval process instance; According to the first process configuration information of the first process approval instance, calling a configuration interface for the first process configuration information in a visual configuration interface, and changing the first process configuration information to the second process configuration information in the configuration interface; Generate a second process approval instance according to the second process configuration information; Execute the approval of the second process approval instance.

2. The method according to claim 1, characterized in that The method further comprises: Define the correspondence between approval items and approval process instances in the approval system; In response to receiving the pending approval item submitted by the first user on the business process interface of the approval system, generating an initial approval process instance corresponding to the pending approval item as the first approval process instance according to the corresponding relationship; or, In response to receiving the pending approval item submitted by the first user on the business process interface of the approval system, generating an initial approval process instance corresponding to the pending approval item as the first approval process instance according to the corresponding relationship; According to the current approval node corresponding to the first approval process instance, a user corresponding to the current approval node is determined as a second user, and the first approval process instance is sent to the second user, and the second user receives the first approval process instance; wherein the second user is a user authorized to approve the first approval process instance.

3. The approval process instance includes approval content information and approval node information; The method comprises at least one of the following: In response to detecting that the approval content information in the approval process instance does not satisfy the first preset condition, determining that it is detected that the approval process needs to be adjusted; In response to detecting a change in approval node information in the approval process instance, it is determined that a need to adjust the approval process is detected.

4. The method according to claim 3, characterized in that The method further comprises: If it is detected that the approval item content information has been modified, it is determined that the first preset condition is not met; or, If it is detected that the numerical value information in the approval item content information exceeds the preset numerical value range, it is determined that the first preset condition is not met.

5. The method according to claim 1, wherein The process configuration information includes: approval node information and approval condition information; In response to detecting that the approval process needs to be adjusted, determining first process configuration information of the first approval process instance includes: In response to detecting that the approval process needs to be adjusted, determining current first approval node information and current first approval condition information of the first process approval instance; Based on the current first approval node information and the current first approval condition information of the first process approval instance, second approval node information and second approval condition information subsequent to the node corresponding to the current first approval node information of the first process approval instance are determined; and the second approval node information and the second approval condition information are used as the first process configuration information.

6. The method according to claim 1, characterized in that The step of calling a configuration interface for the first process configuration information in a visual configuration interface based on the first process configuration information of the first process approval instance, and configuring the first process configuration information as second process configuration information in the configuration interface includes: According to the first process configuration information of the first process approval instance, calling the visual configuration interface corresponding to the first process configuration information; Displaying the configuration items of the first process configuration information on the visual configuration display page; An input operation for a configuration item of the first process configuration information is received in the visual configuration interface, and the first process configuration information is modified to second process configuration information.

7. The approval method according to claim 1, characterized in that: The step of executing the second process approval instance includes: Automatically generate approval result information for the second process approval instance based on the first network model; Execute the approval of the second process approval instance according to the approval result information.

8. The method according to claim 2, characterized in that The method further comprises: After executing the approval of the item to be approved according to the second process approval instance, saving the second process approval instance; The definition of the correspondence between approval items and approval process instances in the approval system includes: A corresponding relationship between the approval items and the second approval process instance is defined in the approval system.

9. A computer device, characterized in that: include: A processor and a memory storing a computer program, wherein when the processor runs the computer program, the steps of the method according to any one of claims 1 to 8 are implemented.

10. A computer-readable storage medium, characterized in that A computer program is stored, and when the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 8 are implemented.

Images