CN114723391A

CN114723391A - Method and device for generating user-defined business process approval flow

Info

Publication number: CN114723391A
Application number: CN202210270265.8A
Authority: CN
Inventors: 何亚东
Original assignee: Shenzhen Xiaoman Technology Co ltd
Current assignee: Shenzhen Xiaoman Technology Co ltd
Priority date: 2022-03-18
Filing date: 2022-03-18
Publication date: 2022-07-08

Abstract

The invention relates to the technical field of Internet, in particular to a method and a device for generating a custom business process approval flow; the method comprises the following steps: receiving an event trigger request sent by a requester, determining whether an event is performed or not based on a trigger rule and feeding back the event to the requester; receiving an approval rule newly-built request sent by a requester, and preparing an approval rule form; determining an approval node based on the approval rule form; generating an approval flow corresponding to an approval rule based on the approval nodes; detecting an approval process formed based on the approval flow, and determining the approval progress; based on the approval progress, the change of the service state is completed and fed back to the requesting party; the definition of the approval flow logic is greatly improved, the code repetition rate is reduced, and the development efficiency is improved.

Description

Method and device for generating user-defined business process approval flow

Technical Field

The invention relates to the technical field of internet, in particular to a method and a device for generating a custom business process approval flow.

Background

The Workflow "refers to the automation of part or the whole of the business process in the computer application environment, and is an abstract and general description of the business rules between the Workflow and each operation step thereof. An approval flow is an application of a workflow.

The document with the defined approval process will be delivered and approved according to the defined approval process. This complete process is called an approval flow. The realization of the approval flow can comprehensively improve the office efficiency of the enterprise and realize the high efficiency, transparency and timeliness of the enterprise in the whole approval process.

The existing approval function is usually embedded into a single module or the realization logic of the function, a single system is composed of a plurality of different modules, each module may be composed of different functions, and the embedded approval function not only can bring a large amount of repeated coding work, but also can increase the complexity of the system logic and make the system maintenance difficult. And the approval rules are scattered at different positions of the system, so that the approval logic is difficult to be visually shown. Meanwhile, because the logic is embedded in the code, non-programmers are difficult to edit and modify the logic, and the change of the approval rule can be modified only after a maker communicates with developers for requirements. Meanwhile, due to the dispersity of the approval logic, centralized statistics of approval data is difficult to perform.

Disclosure of Invention

The embodiment of the application provides a method for generating an approval flow of a user-defined business process, which is used for reducing the difficulty of generating the approval flow and determining a proper approval flow based on a specific business scene, and the technical scheme adopted by the embodiment of the application is as follows:

in a first aspect, this embodiment provides a method for generating an approval flow of a custom business process, including:

receiving an event trigger request sent by a requester, determining whether an event is performed or not based on a trigger rule and feeding back the event to the requester;

receiving an approval rule newly-built request sent by a requester, and preparing an approval rule form;

determining an approval node based on the approval rule form;

generating an approval flow corresponding to an approval rule based on the approval nodes;

detecting an approval process formed based on the approval flow, and determining the approval progress;

and finishing the change of the service state and feeding back the service state to the requester based on the approval progress.

With respect to the second implementation possibility, in combination with the first aspect, the accepting an event trigger request sent by a requester, and determining whether an event is performed and fed back to the requester based on a trigger rule includes:

and matching the fields carried in the event request with preset trigger fields, determining whether behaviors are performed or not according to matching results, and feeding back the behaviors to a requester.

With respect to the third implementation possibility, in combination with the first aspect, the accepting a new request for an approval rule sent by a requester and configuring an approval rule form includes:

presetting the examination and approval rule form template, sending the examination and approval rule form template to the requester end, and triggering the requester to fill in the examination and approval rule form on an information input interface.

For the fourth implementation possibility, in combination with the third implementation possibility, the method receives a new approval rule request sent by a requester, and configures an approval rule form, further including:

and receiving the information input on the information input interface and sent by the requester, and generating an approval rule form based on the information.

For a fifth implementation possibility, in combination with the fourth implementation possibility, the determining an approval node based on the approval rule form includes:

and determining the information of the examination and approval personnel and examination and approval triggering conditions of each stage based on the examination and approval rule form.

For the sixth implementation possibility, in combination with the fifth possibility, the approval rule form includes a judgment type, a judgment parameter corresponding to the judgment type, and approval staff information corresponding to the judgment parameter.

With respect to the seventh implementation possibility, in combination with the sixth implementation possibility, the determining, based on the approval rule form, approval person information and approval triggering conditions at each stage includes:

receiving a list of the examination and approval personnel, a plurality of judgment parameters and a plurality of judgment types which are input in an information input interface; receiving the information of the examination and approval personnel of each stage selected from the list of examination and approval personnel sent by the requesting party, and a designated judgment parameter selected from the multiple judgment parameters and a designated judgment type selected from the multiple judgment types; and acquiring the trigger condition of each stage according to the specified judgment parameter and the specified judgment type of each stage and the trigger value of the stage sent by the requester.

With respect to the eighth implementation possibility, in combination with the seventh possibility, the generating an approval flow corresponding to an approval rule based on the approval node includes:

and generating the approval flow according to the approval personnel information, the approval triggering conditions and the state value of completion of the applicant in each stage.

With respect to the ninth implementation possibility, in combination with the eighth possibility, the detecting determines an approval progress based on an approval process formed by the approval flow, and includes:

and receiving the approval completion notification, and modifying the current approval state.

For the second aspect, this embodiment further provides a device for generating a custom business process approval flow, including:

the event determining module is used for receiving an event triggering request sent by a requesting party, determining whether an event is performed or not based on a triggering rule and feeding back the event to the requesting party;

the examination and approval rule form preparation module is used for receiving an examination and approval rule newly-built request sent by a requester and preparing an examination and approval rule form;

the approval node determination module is used for determining approval nodes based on the approval rule form;

the approval flow generation module is used for generating an approval flow corresponding to the approval rule based on the approval nodes;

the approval progress generating module is used for detecting an approval process formed based on the approval flow and determining the approval progress;

and the result feedback module is used for finishing the change of the service state and feeding back the change to the requester based on the approval progress.

According to the device and the method for generating the approval flow of the user-defined business process, the approval flow can be generated and the approval process can be processed on line according to different business types and different business processes in a user-defined mode by formulating the approval rule. The definition of the approval flow logic is greatly improved, the code repetition rate is reduced, and the development efficiency is improved.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.

The methods, systems, and/or processes of the figures are further described in accordance with the exemplary embodiments. These exemplary embodiments will be described in detail with reference to the drawings. These exemplary embodiments are non-limiting exemplary embodiments in which example numbers represent similar mechanisms throughout the various views of the drawings.

FIG. 1 is a schematic diagram of an application scenario of a method of generating an approval stream according to some embodiments of the present application;

FIG. 2 is a schematic structural diagram of an electronic device according to some embodiments of the present application;

FIG. 3 is a flow diagram illustrating a method for generating an approval flow according to an embodiment of the present application;

FIG. 4 is a detailed flow diagram of an approval flow generation method according to some embodiments of the present application;

FIG. 5 is a block diagram of an approval flow generation apparatus according to some embodiments of the present application.

Detailed Description

In order to better understand the technical solutions, the technical solutions of the present application are described in detail below with reference to the drawings and specific embodiments, and it should be understood that the specific features in the embodiments and examples of the present application are detailed descriptions of the technical solutions of the present application, and are not limitations of the technical solutions of the present application, and the technical features in the embodiments and examples of the present application may be combined with each other without conflict.

In the following detailed description, numerous specific details are set forth by way of examples in order to provide a thorough understanding of the relevant guidance. It will be apparent, however, to one skilled in the art that the present application may be practiced without these specific details. In other instances, well-known methods, procedures, systems, compositions, and/or circuits have been described at a relatively high-level, without detail, in order to avoid unnecessarily obscuring aspects of the present application.

The present application uses flowcharts to illustrate the implementations performed by a system according to embodiments of the present application. It should be expressly understood that the processes performed by the flowcharts may be performed out of order. Rather, these implementations may be performed in the reverse order or simultaneously. In addition, at least one other implementation may be added to the flowchart. One or more implementations may be deleted from the flowchart.

Like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, it need not be further defined and explained in subsequent figures. Meanwhile, in the description of the present application, the terms "first", "second", and the like are used only for distinguishing the description, and are not to be construed as indicating or implying relative importance.

In order to better understand the method for generating the custom business process approval flow provided by this embodiment, a certain description needs to be made on a usage scenario of the method.

The method for generating the approval flow of the user-defined business process implemented by the implementation of the stereoscopic work is mainly applied to a CRM (customer relationship management) system. CRM systems are primarily provided for modules such as customers, mail, customer orders, quotations, purchase orders, etc., where many model objects are involved. Such as mail, orders, customers. The business change is actually the attribute change of the corresponding model and the associated model, for example, the order is modified from draft state to placed order, and the process of the attribute of the order is 1 → 2. There are many model objects in the system and the push-to-map of business to an object is a change in the object's properties.

The following is a definite explanation of the terms involved in the present embodiment:

the application form, in this embodiment, refers to a form submitted when a user business action is triggered.

And the examination and approval bill is generated according to the triggering condition and is sent to the approver.

Approval nodes: each approval phase is an approval node.

And the approval process is started, and the approval rule is met and triggered.

And finishing the approval flow, finishing the execution of all the set approval processes, and keeping the application form in a final state.

A final state comprising any one of the following states: refusal, consent, revocation.

Fig. 1 is a schematic application scenario diagram of a method for generating an approval flow according to an embodiment of the present application. The method comprises the following steps: the server 110 and the client 120 communicate with each other through a wireless network. Client 120 may be a smartphone, tablet, desktop computer. The server 110 may be a server or a cluster of servers. The server 110 may execute the method for generating the approval flow provided in the embodiment of the present application.

Fig. 2 is a schematic structural diagram of an electronic device provided in an embodiment of the present application. The electronic device may serve as the server, and the electronic device 200 may be configured to execute the method for generating the custom business process approval flow provided in the embodiment of the present application. As shown in fig. 2, the electronic device 200 includes: one or more processors 210, and one or more memories 220 storing processor-executable instructions. The processor 210 is configured to execute the method for generating the custom business process approval flow provided in the following embodiments of the present application.

The processor 210 may be a device containing a Central Processing Unit (CPU), a Graphics Processing Unit (GPU) or other form of processing unit having data processing and/or instruction execution capabilities, may process data for other components in the electronic device 200, and may control other components in the electronic device 200 to perform desired functions.

The memory 220 may include one or more computer program products that may include various forms of computer-readable storage media, such as volatile memory and/or non-volatile memory. The volatile memory may include, for example, Random Access Memory (RAM), cache memory (cache), and/or the like. The non-volatile memory may include, for example, Read Only Memory (ROM), hard disk, flash memory, etc. One or more computer program instructions may be stored on the computer-readable storage medium and executed by processor 210 to implement the method of generating an approval flow described below. Various applications and various data, such as various data used and/or generated by the applications, may also be stored in the computer-readable storage medium.

In one embodiment, the electronic device 200 shown in FIG. 2 may further include an input device 230, an output device 240, and a data acquisition device 250, which may be interconnected via a bus system 260 and/or other form of connection mechanism (not shown). It should be noted that the components and configuration of the electronic device 200 shown in FIG. 2 are exemplary only, and not limiting, and the electronic device 200 may have other components and configurations as desired.

The input device 230 may be a device used by a user to input instructions, and may include one or more of a keyboard, a mouse, a microphone, a touch screen, and the like. The output device 240 may output various information (e.g., images or sounds) to the outside (e.g., a user), and may include one or more of a display, a speaker, and the like. The data acquisition device 250 may acquire an image of a subject and store the acquired image in the memory 220 for use by other components. Illustratively, the data acquisition device 250 may be a camera.

In an embodiment, the devices in the example electronic device for implementing the method for generating an approval flow according to the embodiment of the present application may be integrally disposed, or may be disposed in a decentralized manner, such as integrally disposing the processor 210, the memory 220, the input device 230, and the output device 240, and disposing the data acquisition device 250 separately.

In an embodiment, the example electronic device 200 for implementing the method for generating an approval flow of an embodiment of the present application may be implemented as an intelligent device such as a computer, a server, or the like.

Fig. 3 is a flowchart illustrating a method for generating an approval flow of a custom business process according to an embodiment of the present application. The method may be performed by the server, as shown in fig. 3, and may include the following S310-S360.

S310: and receiving an event trigger request sent by the requester, determining whether the event is performed or not based on a trigger rule, and feeding back the event to the requester.

Specifically, matching is performed according to fields carried in the event request and preset trigger fields, and whether behaviors are performed or not is determined according to matching results and fed back to a requester.

In the present embodiment, the event is an order state change performed by the requester, i.e. the user policy, for a specific service scenario, including but not limited to editing of an order, saving after the order is edited, modifying after the order is edited and the like.

In this embodiment, when the user changes the order state, an event with the modified order state is generated, and whether the current object and the event trigger the approval is determined by the change of the order state. The determination of each order is performed based on its independent order id, and a value can be assigned to the id, and the range of assignment can be performed according to order assignment rules. For example, an order id of 100 represents an independent order with id of 100.

Based on the process, the order id is 100, and the order is modified from the draft state to the placed order by the user, namely the order state is changed. When the order state changes, an event of a corresponding type is generated, after a user configures a triggering rule of the order in the background and starts a current rule, whether the configuration of the approval flow engine can be matched or not is judged, and the triggering condition of the configuration of the approval flow engine with a specific number is determined to be that the object is the order and the order is changed from a draft to a placed order.

In this embodiment, the field carried in the event request is any one of target fields formulated based on the trigger rule, and may be a name, a number, and the like. And determining whether the field is contained under the trigger condition or not by judging the field, if the field is in accordance with the field under the trigger condition, changing the order state, and if the field is not in accordance with the field under the trigger condition, not changing the order state, namely not going to the next processing link, and feeding back the processed information to the requester.

The process is based on a business processing process, namely before the examination and approval, the state of the event to be examined and approved needs to be determined.

S320: receiving an approval rule newly-built request sent by a requester, and configuring an approval rule form.

Specifically, an examination and approval rule form template is preset, and the examination and approval rule form template triggers a requester to fill in an examination and approval rule form on an information input interface.

And receiving information input on an information input interface and sent by a requester, and generating a rule approval form based on the input information.

The new request of the approval rule can be sent to the server side by the client side. The form template of the approval rule is of a form-shaped structure, and the form template comprises an identifier used for approval and is used for distinguishing different approval rules. Specifically, the identifier may be a name of the approval action, or may be a name of the approval action numbered.

In an embodiment, in response to the new approval rule creation request, a corresponding approval rule form is generated according to a rule name carried in the new approval rule creation request.

The non-programmer can perform input processing on the examination and approval rule form template on an interactive interface of the client, specifically inputting a rule name. Such as contract approval, seal approval, customer entry, and the like. The client sends an approval rule newly-built request carrying the rule name to the server, and the server generates an approval rule form based on the rule name.

S330, determining an approval node based on the approval rule form.

Specifically, based on the examination and approval rule form, the information of the examination and approval personnel and the examination and approval triggering conditions at each stage are determined.

In this embodiment, the validation of the approval staff information and the corresponding approval triggering condition for each stage includes the following processes:

and receiving the list of the examination and approval persons, various judgment parameters and various judgment types input in the information input interface.

And the applicant selects the information of the examining and approving personnel in each stage in the list of the examining and approving personnel.

The applicant selects a specified judgment parameter from the multiple judgment parameters.

The applicant selects a specified judgment type from the multiple judgment types.

And obtaining the trigger condition of each stage according to the specified judgment parameter and the specified judgment type of each stage and the trigger value of each stage which is set and sent by the requester.

In this embodiment, the approver information and the trigger condition may be input by a non-programmer on the interactive interface of the client. And the client side sends the information to the server side, so that the server side obtains the information of the examination and approval personnel and the triggering condition.

An approval flow may include multiple phases, such as an approval flow of a request for funds, may include a department manager approval phase, a general manager approval phase, and so forth.

One or more approval personnel in one stage can enter the next stage when a plurality of approval personnel pass the approval. The information of the approvers may be information of persons corresponding to one or more approvers, and the information of the persons may include names, job names, mailbox addresses, user IDs, and the like.

The triggering condition is a judgment condition for triggering the examination and approval personnel at the stage to carry out examination and approval. For example, the amount requested is greater than 100, e.g., the department manager has completed the approval.

In an embodiment, after the server generates the examination and approval rule form, the examination and approval rule form can be returned to the requester of the new examination and approval rule request, and the requester is triggered to display an information input interface; and then receiving the information of the approval personnel and the triggering conditions of each stage input by the user on the information input interface, which are sent by the requester.

The requesting party may be the client sending the new request for approval rules above. The client can display an information input interface, and a user can specify the examination and approval personnel and the triggering conditions of each stage in sequence on the information input interface. And then the client sends the information of the approval personnel and the triggering condition to the client. The requester provides a graphical operation interface, and non-developers can freely make and modify the approval rules after learning, so that the process of needing to communicate with the development frequently and meeting the requirements is eliminated. The approval logic can be graphically displayed without having to review the code rules at a glance.

And S340, generating an approval flow corresponding to the approval rule based on the approval nodes.

One examination and approval rule form corresponds to only one examination and approval flow. And according to the examination and approval rule form, calling the corresponding examination and approval flow through the corresponding calling interface. The approval flow comprises the information of the approval personnel of each stage in sequence and the triggering conditions for triggering the approval personnel of the stage to carry out approval.

And S350, detecting an approval process formed based on the approval flow, and determining the approval progress.

Specifically, according to the state value completed by the applicant at each stage, an approval process is determined; and based on the approval process, accepting the approval completion notification and modifying the current approval state.

And in the same stage, a plurality of approvers can simultaneously carry out approval operation. In practical application, when all the parallel approvers complete approval, if approval in a refusal state exists, the state that the application form is refused is returned to the application to which the approval belongs, and if all the approvers agree, the state that the application enters the next stage is returned to the application to which the approval belongs.

In one embodiment, the server may receive a status value for each stage of the requestor configuration at completion. The status value refers to the status of the approver's determination of the application at each stage when the stage is complete. The client may modify the application state of the master application form based on the returned state value. For example, such as a single request, the status value may be the status of the request, and it is assumed that the single request is divided into four stages, namely, approval by a business approver- > confirmation by a department manager- > confirmation by a general manager- > return of the request. And then after the approval of the corresponding business approver is finished, returning the contract to the application (client) to which the approval belongs and entering a stage of waiting for the department manager to confirm, and so on, continuously updating the state of the application of the request until all processes are finished.

And S360, based on the approval progress, finishing the change of the service state and feeding back to the requester.

Fig. 4 is a detailed flowchart illustration of the custom business process approval flow generation method provided in this embodiment, which includes the following steps:

1. the user business process drives the business object change to generate a trigger, and the trigger binds the event type, the event source business object and the object change.

2. And monitoring the generation of the trigger by the approval stream engine, detecting whether the defined approval rule is met or not by the adapter, if the approval rule is not matched, the current user behavior cannot trigger the approval, and if the approval rule is matched, outputting the trigger and the matched result to the scheduler.

3. The scheduler acquires an input rule and calls the parser to parse out an approval node defined by the rule, and generates a request form, an approval node and an approval sheet, wherein each approver in the nodes can generate an approval sheet and lock an object.

4. And after receiving the approval list, the approver inputs approval results to approve or reject, and the scheduler judges whether the current node reaches the final state or not according to the current input.

5. And after the state of each node is finished, the scheduler sequentially processes the next step defined by the rule, if the step which meets the condition does not exist, the execution phase of the scheduler is finished, and the locked object is released.

6. And executing corresponding approval logic according to the approval result input by the approver, marking the application form as a refused state if refused, and modifying object data bound according to the trigger through the awakening device if agreeing.

7. And finally, executing the configuration defined by the user, and informing the center of sending the approval result to the applicant by the message, thereby finishing the execution of the whole process.

The figure is a block diagram of a custom business process approval flow generation device. The apparatus 700 for generating approval of customized business process comprises:

an event determining module 710, configured to receive an event trigger request sent by a requestor, determine whether an event is performed based on a trigger rule, and feed back the event to the requestor;

the examination and approval rule form configuration module 720 is used for receiving an examination and approval rule new request sent by a requester and configuring an examination and approval rule form;

the approval node determination module 730 is used for determining approval nodes based on the approval rule form;

the approval flow generation module 740 is configured to generate an approval flow corresponding to the approval rule based on the approval node;

an approval progress generation module 750, configured to detect an approval process formed based on the approval flow, and determine an approval progress;

and a result feedback module 760, configured to complete the change of the service state and feed back the change to the requestor based on the approval progress.

In one or more embodiments, a terminal device is disclosed, which includes a server including a memory, a processor, and a computer program stored on the memory and executable on the processor, the processor implementing an embodiment of a sparse reconstruction based signal reconstruction method when executing the program. For brevity, no further description is provided herein.

It should be understood that, in the present embodiment, a module may include units implemented in hardware, software, or firmware, and may be used interchangeably with other terms such as "logic," "logic block," "component," and "circuit. A module may be a single integrated component or a minimal unit or component of the single integrated component that is adapted to perform one or more functions. For example, according to an embodiment, the module may be implemented in the form of an application-specific integrated circuit (ASIC).

A computer readable signal medium may comprise a propagated data signal with computer program code embodied therein, for example, on a baseband or as part of a carrier wave. The propagated signal may take any of a variety of forms, including electromagnetic, optical, and the like, or any suitable combination. A computer readable signal medium may be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code on a computer readable signal medium may be propagated over any suitable medium, including radio, electrical cable, fiber optic cable, RF, or the like, or any combination of the preceding.

Computer program code required for the execution of aspects of the present application may be written in any combination of one or more programming languages, including object oriented programming, such as Java, Scala, Smalltalk, Eiffel, JADE, Emerald, C + +, C #, VB.NET, Python, and the like, or similar conventional programming languages, such as the "C" programming language, Visual Basic, Fortran 2003, Perl, COBOL 2002, PHP, ABAP, dynamic programming languages, such as Python, Ruby, and Groovy, or other programming languages. The programming code may execute entirely on the user's computer, as a stand-alone software package, partly on the user's computer, partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any network format, such as a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet), or in a cloud computing environment, or as a service, such as a software as a service (SaaS).

It should also be appreciated that in the foregoing description of embodiments of the present application, various features are sometimes grouped together in a single embodiment, figure, or description thereof for the purpose of streamlining the disclosure aiding in the understanding of at least one embodiment of the invention. However, this method of disclosure is not intended to require more features than are expressly recited in the claims. Indeed, the embodiments may be characterized as having less than all of the features of a single embodiment disclosed above.

Claims

1. A method for generating an approval flow of a user-defined business process is applied to a server and comprises the following steps:

determining an approval node based on the approval rule form;

2. The method for generating an approval flow of a custom business process according to claim 1, wherein the receiving an event trigger request sent by a requester, determining whether an event is performed based on a trigger rule and feeding back the event to the requester comprises: and matching the fields carried in the event request with preset trigger fields, determining whether behaviors are performed or not according to matching results, and feeding back the behaviors to a requester.

3. The method for generating an approval flow of a custom business process according to claim 1, wherein the step of receiving a new request of an approval rule sent by a requester and preparing an approval rule form comprises: presetting the examination and approval rule form template, sending the examination and approval rule form template to the requester end, and triggering the requester to fill in the examination and approval rule form on an information input interface.

4. The method for generating an approval flow of a custom business process according to claim 3, wherein accepting a new request of an approval rule sent by a requesting party and preparing an approval rule form further comprises: and receiving the information input on the information input interface and sent by the requester, and generating an approval rule form based on the information.

5. The method for generating the custom business process approval flow according to claim 4, wherein determining the approval node based on the approval rule form comprises: and determining the information of the examination and approval personnel and examination and approval triggering conditions of each stage based on the examination and approval rule form.

6. The method for generating the approval flow of the custom business process according to claim 5, wherein the approval rule form comprises a judgment type, a judgment parameter corresponding to the judgment type and approval personnel information corresponding to the judgment parameter.

7. The method for generating the approval flow of the custom business process according to claim 6, wherein the determining of the approval staff information and the approval triggering conditions at each stage based on the approval rule form includes: receiving a list of the examination and approval personnel, a plurality of judgment parameters and a plurality of judgment types which are input in an information input interface; receiving the information of the examination and approval personnel of each stage selected from the list of examination and approval personnel sent by the requesting party, and a designated judgment parameter selected from the multiple judgment parameters and a designated judgment type selected from the multiple judgment types; and acquiring the trigger condition of each stage according to the specified judgment parameter and the specified judgment type of each stage and the trigger value of the stage sent by the requester.

8. The method for generating the approval flow of the custom business process according to claim 7, wherein the generating the approval flow corresponding to the approval rule based on the approval node comprises: and generating the approval flow according to the approval personnel information and the approval triggering conditions at each stage.

9. The method for generating the approval flow of the custom business process according to claim 1, wherein the detecting an approval process formed based on the approval flow and determining an approval progress comprises: determining an approval process according to the state value completed by the applicant at each stage; and based on the approval process, accepting the approval completion notification and modifying the current approval state.

10. An approval-flow generation apparatus, comprising: