Node configuration method and device

Abstract

The invention discloses a node configuration method and device, and belongs to the technical field of computers. The method comprises the following steps: in response to receiving an approval request sent by a first terminal, configuring information of a current node according to the approval request; sending the information of the current node to a corresponding second terminal for examination and approval; in response to the received approval result of the current node returned by the second terminal, determining configuration node information according to the approval result of the current node; and configuring the information of the next node according to the configuration node information.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to a node configuration method and apparatus. Background Technology

[0002] Node configuration is a core part of the workflow engine. It mainly implements the process of application software routing and passing information based on certain decisions and processing business processes sequentially according to a set of predefined rules, resulting in poor flexibility in the entire approval process. Summary of the Invention

[0003] The purpose of this application is to provide a node configuration method and apparatus to improve the flexibility of the approval process.

[0004] In a first aspect, the technical solution of this application provides a node configuration method, including: in response to receiving an approval request sent by a first terminal, configuring the information of the current node according to the approval request; sending the information of the current node to the corresponding second terminal for approval; in response to receiving the approval result of the current node returned by the second terminal, determining the configuration node information according to the approval result of the current node; and configuring the information of the next node according to the configuration node information.

[0005] Optionally, configuring the information of the next node based on the configuration node information includes: sending a preset configuration page to a third terminal corresponding to the next node; wherein the configuration page includes multiple configuration items corresponding to the configuration node information; and determining the information of the next node in response to receiving an edit request from the third terminal for the multiple configuration items; wherein the edit request is used to edit the configuration item information of the multiple configuration items.

[0006] Optionally, the multiple configuration items include at least two of the following: approval role configuration item, approval information configuration item, approval personnel configuration item, and node flow condition configuration item.

[0007] Optionally, the configuration page also includes a form editing permission configuration item; wherein, the form editing permission configuration item is used to restrict the third terminal's editing permission for configuration item information.

[0008] Optionally, the node configuration method further includes: sending the information of the next node to the corresponding third terminal for approval.

[0009] Optionally, if the configuration information of the approver configuration item includes information of multiple approvers, the information of the next node is sent to the corresponding third terminal for approval, including: sending the information of the next node to the third terminal corresponding to each of the multiple approvers for approval; if the approval result is received from the third terminal corresponding to any approver, the approval of the next node is completed.

[0010] Optionally, the node configuration method further includes: in response to receiving the approval result of the next node returned by the third terminal, determining whether the next node meets the corresponding node transfer conditions; if it is determined that the next node meets the corresponding node transfer conditions, then the next node is taken as the current node, and the step of determining the configuration node information based on the approval result of the current node continues to be executed.

[0011] Optionally, the node configuration method further includes: if it is determined that the next node does not meet the corresponding node flow conditions, then the approval result of the next node is taken as the final approval result of the approval request, and the final approval result is sent to the terminal.

[0012] Optionally, the next node can be multiple nodes that execute in parallel.

[0013] Secondly, this application provides a node configuration device, comprising: a request receiving module configured to receive an approval request sent by a first terminal; a first configuration module configured to configure the information of the current node according to the approval request in response to receiving the approval request; an information sending module configured to send the information of the current node to a corresponding second terminal for approval; a result receiving module configured to receive the approval result of the current node returned by the second terminal; an information determining module configured to determine the configuration node information according to the approval result of the current node in response to receiving the approval result of the current node; and a second configuration module configured to configure the information of the next node according to the configuration node information.

[0014] Thirdly, the present application provides a computer-readable storage medium storing program information, wherein a computer reads the program information and executes the steps of the node configuration method described in any one of the first aspects.

[0015] Fourthly, the present application provides a computer program product, including a computer program / instructions, which, when executed by a processor, implement the steps of the node configuration method described in any of the first aspects.

[0016] Fifthly, the present application provides an electronic device, including a memory, a processor, and a computer program stored in the memory, wherein the processor executes the computer program to implement the steps of the node configuration method described in any of the first aspects.

[0017] The technical solution provided in this application has the following technical effects compared with the prior art: This application provides a node configuration method and apparatus that, upon receiving an approval request from a first terminal, configures the information of the current node according to the approval request, and after the second terminal approves the current node, configures the information of the next node according to the configuration node information determined by the approval result of the current node. The node information is configured in real time as the approval process progresses; thus, the flexibility of the approval process is improved. Attached Figure Description

[0018] The preferred embodiments of this application will be described in detail below with reference to the accompanying drawings, which will help to understand the purpose and advantages of this application, wherein: Figure 1 This application provides an example of a node configuration method. Figure 2 This is a schematic diagram of the terminal structure provided in the embodiments of this application; Figure 3 A flowchart illustrating a node configuration method provided in an embodiment of this application; Figure 4 A schematic diagram of the business server provided in the embodiments of this application; Figure 5 A schematic diagram of a configuration page provided in an embodiment of this application; Figure 6 This is a schematic diagram of the structure of a node configuration device provided in an embodiment of this application; Figure 7 This is a schematic diagram of the hardware connection relationship of the electronic device for the node configuration method provided in the embodiments of this application. Detailed Implementation

[0019] The technical solutions of this application will now be clearly and completely described with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0020] In the description of this application, it should be noted that the terms "center," "upper," "lower," "left," "right," "vertical," "horizontal," "inner," and "outer," etc., indicate the orientation or positional relationship based on the orientation or positional relationship shown in the accompanying drawings. They are used only for the convenience of describing this application and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation. Therefore, they should not be construed as limitations on this application. Furthermore, the terms "first," "second," and "third" are used for descriptive purposes only and should not be construed as indicating or implying relative importance.

[0021] In the description of this application, it should be noted that, unless otherwise expressly specified and limited, the terms "installation," "connection," and "joining" should be interpreted broadly. For example, they can refer to a fixed connection, a detachable connection, or an integral connection; they can refer to a direct connection or an indirect connection through an intermediate medium; and they can refer to the internal communication between two components. Those skilled in the art can understand the specific meaning of the above terms in this application based on the specific circumstances.

[0022] Furthermore, the technical features involved in the different embodiments of this application described below can be combined with each other as long as they do not conflict with each other.

[0023] Existing technologies rely on a set of predefined rules to complete business process approvals. A business process refers to the sequential flow of activities related to a work item, including the work steps, procedures, and stages involved. For example, when initiating a leave application, multiple approval departments approve it level by level according to a set of predefined rules. However, this approach is only suitable for single, fixed approval scenarios.

[0024] However, with the increasing diversity of business needs, the existing solutions mentioned above are not suitable for diverse business requirements.

[0025] When this application receives an approval request from the first terminal, it configures the information of the current node according to the approval request. After the second terminal approves the current node, it configures the information of the next node according to the configuration node information determined by the approval result of the current node. The node information is configured in real time as the approval process progresses, thus improving the flexibility of the approval process.

[0026] The node configuration method provided in this application embodiment can be applied to, for example, Figure 1 In the application scenario shown, the first terminal 102 and the second terminal 106 communicate with the service server 104 via a network.

[0027] Both the first terminal 102 and the second terminal 106 can be used to display pages suitable for customized business scenarios (such as configuration pages or approval pages), and these customized pages can be pages pushed by the business server 104.

[0028] In this embodiment, the business server pushes the page to the terminal, allowing approvers to directly configure node information through a visual interface, thus improving the user experience.

[0029] In one example, the first terminal 102 and the second terminal 106 may have business applications installed. After logging into the business application through an account, the first terminal 102 can access the page pushed by the business server 104 on its front-end interface.

[0030] The business server 104 can push the page corresponding to the approval request initiated by the first terminal 102 to the first terminal 102 so that the corresponding page can be displayed on the first terminal 102. The first terminal 102 can respond by performing a configuration operation on the configuration page to configure the node (such as the current node or the next node) to complete the configuration of the node information. After configuring the node information, the approval page can be displayed on the second terminal 106 so that the node information can be approved on the approval page.

[0031] The first terminal 102 and the second terminal 106 can be, but are not limited to, various personal computers, laptops, smartphones, tablets, IoT devices, and portable wearable devices. IoT devices can include smart speakers, smart TVs, smart air conditioners, smart in-vehicle devices, etc. Portable wearable devices can include smartwatches, smart bracelets, head-mounted devices, etc. The business server 104 can be implemented using a standalone business server or a cluster of multiple business servers.

[0032] The business server 104 includes at least a display screen, which can be used to display the corresponding page (such as a configuration page or an approval page). Furthermore, the number of second terminals is not limited to one, to accommodate scenarios where multiple approval departments or personnel participate in the approval process.

[0033] Figure 2 This is an application scenario diagram of an embodiment of the present invention; in this embodiment, the node configuration method provided by this application can be implemented based on a business server, such as... Figure 2 In this embodiment, the front-end interface of a terminal (such as a first terminal or a second terminal) is used to display the page pushed by the business terminal. After the user logs in to the business application on the first terminal, the business server pushes the corresponding page to the first terminal so that the corresponding page can be displayed on the front-end interface 110 of the first terminal. For example, the configuration page can be displayed on the front-end interface 110 of the first terminal to configure node information; here, the front-end interface 110 refers to the display page on the first terminal where configuration operations (or approval operations) can be performed.

[0034] This application provides a node configuration method that can be applied to a business server, such as... Figure 3 As shown, the node configuration method includes the following steps: Step 301: In response to receiving the approval request sent by the first terminal, configure the information of the current node according to the approval request.

[0035] Step 303: Send the information of the current node to the corresponding second terminal for approval.

[0036] Step 305: In response to receiving the approval result of the current node returned by the second terminal, determine the configuration node information based on the approval result of the current node.

[0037] Step 307: Configure the information of the next node according to the configuration node information.

[0038] This application provides a node configuration method that, upon receiving an approval request from a first terminal, configures the information of the current node according to the approval request. After the second terminal approves the current node, the method configures the information of the next node according to the configuration node information determined by the approval result of the current node. The node information is configured in real time as the approval process progresses, thus improving the flexibility of the approval process.

[0039] The following describes the business server.

[0040] exist Figure 4 In the process, a process engine system can be configured on the business server. In this process engine system, the same listener can be configured for each node to achieve global listening of the business process. During the global listening process, the process engine system creates nodes (such as the current node or the next node) for the business process, configures the information of the node, and puts the processing logic of each node in the listener.

[0041] exist Figure 4 In addition, the business server is also configured with a system for business processing. This system can be used to configure node information, and when configuring the information of a node (such as the next node), the approval result of the previous node (such as the current node) should be called back.

[0042] The following example uses a procurement approval process.

[0043] The prerequisite node is department manager approval. The callback logic is as follows: Queries the approval roles associated with the current purchase order (such as finance, legal, etc.); Get the list of approvers for each role (e.g., approver A for the finance role); Define roles and approvers, and push the information to the next node.

[0044] The embodiments of this application can dynamically configure node information, such as approval roles and / or approvers, and support parallel approval or approval by role order. Compared with traditional process engine systems, which can only approve one node's information at a time when there are many process tasks, this improves the flexibility of the approval process.

[0045] The following describes the process of encapsulating roles and approvers using the configuration page.

[0046] exist Figure 5In this process, for an approval request initiated by an applicant, the information of the current node is first configured (e.g., the project department's approval role is configured as supervisor, the operation permission is configured as pending approval, and the candidate operations are approved and rejected). After the project department supervisor approves the request, the business process moves from the current node to the next node. A callback logic is used to configure the information of the next node (i.e., the approval role is configured as procurement, the operation permission is configured as pending review, and the candidate operations are approved and rejected). After configuring the information of the next node, the information of the next node is pushed to the procurement department's approval personnel for review, and after the review is approved, it is pushed to the procurement department supervisor for approval, until the entire business process corresponding to the approval request is completed.

[0047] In addition, the configuration page displayed on the front-end interface of the terminal generally only shows a few configuration items, which are used to configure the information of the next node; that is, the configuration items for configuring the information of the next node can be pushed to the corresponding terminal in the form of a page.

[0048] It should be noted that the node configuration method provided in this application embodiment is applicable to the Flowable framework and is suitable for scenarios from the perspective of process business, such as warehouse management, security management, and office management.

[0049] The following describes step 301 (i.e., in response to receiving the approval request sent by the first terminal, configuring the information of the current node according to the approval request) in detail.

[0050] In step 301, when the business server receives the approval request sent by the first terminal, it configures the information of the current node according to the approval request.

[0051] The approval request includes the information required for approval, such as applicant information, application content, application time limit, and approval time limit. Optionally, the approval request can be initiated by the applicant through a business application on the first terminal (such as a program for completing OA approvals) to the business server to request the completion of business-related approvals, such as the approval of various payments.

[0052] In one example, configuring the information of the current node based on the approval request may include: displaying the information of the current node on the configuration page of the business server after the business server receives the approval request.

[0053] In addition, in the process of configuring the information of the current node in this embodiment of the application, the configuration page of the business server is pre-logged into the first terminal (e.g., the configuration page is displayed on the front-end interface of the first terminal when the first terminal logs into the configuration page of the business server through an account (i.e., the configuration page is pushed to the first terminal), so that the information of the current node can be configured on the first terminal). In this way, the approval request can be initiated to the business server by editing the configuration item information of multiple configuration items in the configuration page, and the configuration of the information of the current node is completed on the configuration page.

[0054] Here, the configuration page displayed on the business server can include multiple configuration items. These items can be customized based on the approval request or configuration node information, such as customizing the configuration information for each item. Additionally, the approval page can include multiple approval items; once the approver completes the approval process for each item, the node approval is finished.

[0055] In one example, the first terminal is a business application logged in with an account. This allows the configuration page to be displayed on its front-end interface after an approval request is initiated. Furthermore, other terminals subsequently involved in the approval process can also interact with the business server by logging into the same application, such as displaying configuration or approval pages on their front-end interfaces.

[0056] It's important to note that the current node can be the node in the business process where its information is currently being configured. The next node can be the node in the business process where its information is about to be configured, meaning the business process transitions from the current node to the next node. When configuring the information of the next node, that next node can be considered the new current node, and the node the business process will move to next is the new next node.

[0057] Here, a business process is a process initiated in response to an approval request, and the direction of the business process is determined by the information of the configured nodes (such as the current node and the next node).

[0058] Before configuring the node information, the current node and the next node in this embodiment can be understood as nodes whose attribute values ​​are empty. Alternatively, it can be interpreted as follows: before configuring the information of the current node and the next node, the current node and the next node are simply two nodes without specific physical meaning; after configuring the information of the current node, its attributes are assigned corresponding values, giving it corresponding physical meaning; after configuring the information of the next node, its attributes are assigned corresponding values, giving it corresponding physical meaning.

[0059] In other words, by configuring the attribute values ​​for the current node and the next node respectively, the direction of the business process can be accurately determined.

[0060] Optionally, the information of the current node may include, but is not limited to, at least one of the following: approval role, approver, reviewer, information to be approved, approval time, candidate operation, and operation permissions.

[0061] Here, the current node's attributes are assigned corresponding values ​​through the approval request, giving them corresponding physical meaning. This means that the current node's information includes at least one of the following: approval role, approver, information to be approved, approval time, and operation permissions. The approval role can be a position held within the approval department (such as finance, legal, etc.), while the approver is the specific person within that department who performs the approval.

[0062] The following is a detailed description of step 303 (i.e., sending the information of the current node to the corresponding second terminal for approval).

[0063] In step 303, after configuring the information for the current node, the business server will push the information of the current node to the second terminal so that the approver corresponding to the second terminal can approve the information of the current node. Generally, the applicant is not the approver, so the second terminal is not the same terminal as the first terminal.

[0064] Here, information from the current node can be pushed to a second terminal via links, pages, or QR codes.

[0065] In one example, after configuring the information for the current node on the business server side, this information is pushed to a second terminal via a page (such as an approval page). This page is then displayed on the second terminal's front-end interface. This page shows the approval items corresponding to the current node's information. Different approvers generally have different access permissions for different approval items; that is, different approvers can operate on different approval items. Once an approver has completed operating on the approval items, the approval of the current node's information is complete. This page can be presented with different functions depending on the stage of the business server's process; for example, it might be a configuration page during the configuration stage and an approval page during the approval stage.

[0066] In addition, after configuring the information of the current node through the first terminal, the business server pushes the information of the current node to the second terminal in the form of an approval page, so that the approval page of the business server can be displayed on the front-end interface of the second terminal.

[0067] The following is a detailed description of step 305 (i.e., in response to receiving the approval result of the current node returned by the second terminal, determining the configuration node information based on the approval result of the current node).

[0068] After step 303 is completed, that is, after the approval of the information of the current node is completed through the second terminal, the approval result of the current node will be sent to the business server through the second terminal.

[0069] Here, the approval result of the current node can be the result generated by the approver approving the information of the current node through the second terminal. The approval result can be an intermediate result corresponding to the approval request (that is, the current node meets the corresponding node flow conditions). The approval result can be used to determine the configuration node information.

[0070] In step 305, the approval result of the node has a preset correspondence with the configuration items included in the configuration page. For example, the configuration node information includes at least one of the following: approver, reviewer, information to be approved, node flow conditions, etc., and the corresponding configuration items are approver configuration items, reviewer configuration items, approval information configuration items, and node flow conditions configuration items, etc.

[0071] It should be noted that many configuration items on the configuration page can be set according to specific approval requirements, which will not be elaborated here.

[0072] It should be noted that the configuration node information is used to configure the information of the next node.

[0073] In this context, "approver" refers to the personnel who approve nodes (such as the next stage). As an approver, their operational permissions generally include at least one of the following: approval permissions and review permissions. "Information pending approval" refers to information that requires approval from the approver.

[0074] In one example, the business server can display corresponding visual components on its page based on the different operation permissions of different approvers. For instance, the business server can render operation buttons (such as clickable touch components) corresponding to the operation permissions of the next node on its approval page, allowing users to perform operations on the approval items on the approval page by activating these buttons. It can be understood that approvers with approval permissions will see the approval operation buttons, while approvers with review permissions will see the review operation buttons.

[0075] In addition, the corresponding operation buttons are displayed according to the operation permissions of each approver, so that approvers without the corresponding operation permissions cannot process the nodes, thus ensuring the stability of operation permission control.

[0076] In addition, after receiving the approval result of the current node, the business server can also review the approval result and proceed with the subsequent steps only after the review is passed.

[0077] The following is a detailed description of step 307 (i.e., configuring the information of the next node based on the configuration node information).

[0078] In step 307, the business server configures the information of the next node based on the configuration node information.

[0079] Optionally, the information for the next node includes, but is not limited to, at least one of the following: the operating permissions of the next node, the reviewers of the next node, the approvers of the next node, and the candidate operations of the next node.

[0080] In this context, the approver at the next node can be anyone with operational authority over that node, and the candidate operations for the next node can be any operations that the approver at the next node is capable of performing. For example, continuing with the leave application scenario, when the current node is the leave application node, the next node can be the leave approval node. In this case, the operational authority of the next node can be "pending approval," the approver at the next node can be the leave applicant's supervisor, and the candidate operations for the next node can be "approved" or "disapproved."

[0081] It should be noted that the specific content of the above-mentioned operating permissions, reviewers, approvers, and candidate operations are related to the actual business scenario and are not specifically limited here.

[0082] In addition, the next node can be a single node or multiple nodes that execute in parallel. For example, if multiple approval departments participate in the approval of the next node at the same time, then the multiple approval departments are multiple nodes that execute in parallel.

[0083] The solution in this application adopts a progressive approach when configuring node information. First, multiple approval departments are identified, and then the approvers, reviewers, etc., within each approval department are determined. This can be achieved by editing the configuration items on the configuration page. For example, the configuration items may also include approval department configuration items, through which the departments participating in the approval can be modified. This operation is generally performed by the main person in charge of multiple approval departments. In other words, the second terminal can be the terminal of the person in charge of multiple approval departments.

[0084] Here, multiple nodes executing in parallel indicate that approval from multiple departments is required before the approval for the next node can be completed.

[0085] In one example of this application, configuring the information of the next node based on the configuration node information includes: sending a preset configuration page to a third terminal corresponding to the next node; wherein the configuration page includes multiple configuration items corresponding to the configuration node information; and in response to receiving an edit request sent by the third terminal for the multiple configuration items, determining the information of the next node; wherein the edit request is used to edit the configuration item information of the multiple configuration items.

[0086] When the business server receives the approval result for the current node from the second terminal, it pushes the configuration page to the third terminal for display on the third terminal's front-end interface. This configuration page includes multiple configuration items corresponding to the configuration node information. When these configuration items on the third terminal's front-end interface are edited, the information for the next node is configured based on the edited configuration item information.

[0087] Here, a configuration item is the basic unit in the configuration page, referring to the entity that needs to be controlled. Configuration item information is a detailed data set describing the attributes, status, and relationships of a configuration item; it is the metadata of the configuration item and a digital description of the configuration item.

[0088] Optionally, the multiple configuration items include at least two of the following: approval role configuration item, approval information configuration item, approval personnel configuration item, and node flow condition configuration item.

[0089] Here, the approval role configuration item is used to configure the corresponding role for node approval, such as approval by the finance department.

[0090] The approval information configuration item is used to configure the information to be approved for a node (such as the next node). If the approval of the next node requires the participation of multiple approval departments, such as approval department A being responsible for approving monetary information, approval department B being responsible for approving goods information, etc.; optionally, the information to be approved can be configured according to the responsibilities of each approval department.

[0091] The "Approval Personnel Configuration" item is used to configure the personnel responsible for the next stage of the approval process. The configuration information for this item can be set according to approval needs and / or business scenarios. Generally, this personnel is the relevant person in charge of the approval department, which will not be elaborated further here. For example, the configuration information for this item can be information about Approval Personnel A, information about Approval Personnel A or B, or information about all Approval Personnel. It should be noted that setting different configuration information for the "Approval Personnel Configuration" item can adapt to different approval needs.

[0092] The node flow condition configuration item is used to configure the flow conditions, which are used to determine whether to flow the business process from the current node to the next node.

[0093] Following on from the previous text, when the configuration information of the approver configuration item is edited, such as changing the information of approver A to approver A or B, the information of the next node will include the information of approver A or B. When approving the next node, only approver A or approver B needs to approve it, instead of both approvers A and B participating in the approval of the next node, thus improving approval efficiency.

[0094] Optionally, the configuration page also includes a form editing permission configuration item; wherein, the form editing permission configuration item is used to restrict the third terminal's editing permission for configuration item information.

[0095] Here, the above form editing permission configuration item can be used to configure the permissions of approvers to edit the configuration item information of each configuration item. For example, if the head of the approval department has the permission to edit the configuration item information of each configuration item, other personnel in the approval department do not have the permission to edit the configuration item information.

[0096] In this embodiment of the application, after configuring the information for the next node, the information is sent to the corresponding third terminal (and / or fourth terminal) for approval. For example, the third terminal is a terminal held by the superior of the approver corresponding to the fourth terminal.

[0097] Optionally, the information of the next node can be pushed to a third terminal via a link, page, or QR code.

[0098] For example, the information for the next node can be pushed to a third terminal through the approval page, so that the approval page can be displayed on the front-end interface of the third terminal, so that the relevant approvers can make the approval.

[0099] In one example, if the configuration information of the approver configuration item includes information of multiple approvers, the information of the next node is sent to the corresponding third terminal for approval, including: sending the information of the next node to the third terminal corresponding to each of the multiple approvers for approval; if the approval result is received from the third terminal corresponding to any approver, the approval of the next node is completed.

[0100] Following the previous text, after the configuration information of the approver configuration item is edited, such as changing the information of approver A to approver B, when approving the next node, the approval of the next node can be carried out using the information of approver A or B. In other words, as long as the approval result returned by approver A or B is received, the approval of the next node can be completed.

[0101] In some embodiments of this application, when the business server receives the approval result of the next node returned by the third terminal, it determines whether the next node meets the corresponding node transfer conditions; if it is determined that the next node meets the corresponding node transfer conditions, the next node is taken as the current node, and the step of determining the configuration node information based on the approval result of the current node continues to be executed.

[0102] When the business server receives the approval result of the next node returned by the third terminal, it can determine whether the next node meets the corresponding node transfer conditions. If it is determined that the next node meets the corresponding node transfer conditions, the next node is taken as the current node (that is, at this time, it is necessary to configure its information for the next node), and the above steps 305 to 307 are continued until the approval of the new next node is completed.

[0103] The node transition conditions can be used to define the rules for a business process to flow from the current node to the next node. For example, the process will only proceed to the next node if the approval result of the next node (which can be considered the current node) meets preset conditions (such as multiple indicator values). In addition, these node transition conditions can be set according to specific business scenarios to ensure that the approval result of each node meets certain standards before proceeding to the next node.

[0104] For example, the approval result of the next node includes multiple indicator values, which are used to match the node's flow conditions to determine whether the next node meets the corresponding flow conditions. Taking multiple approval departments corresponding to the next node as an example, if the approval department includes the finance department, if the amount exceeds the first threshold, it is approved by the finance department head; if the amount exceeds the second threshold, it is approved by the finance team leader (as in the fourth terminal), and then reviewed by the supervisor (as in the third terminal). If the approval department also includes the purchasing department, if the purchasing data exceeds the third threshold, it is approved by the purchasing department head; if the purchasing data exceeds the fourth threshold, it is approved by the purchasing personnel and then reviewed by the purchasing department head.

[0105] Here, when the next node meets the node flow conditions, including the first threshold and the third threshold, the information of the new next node is configured as follows: the approval role is finance, the approver is the finance manager and the operation permission is pending approval, and the approval role is procurement, the approver is the procurement manager and the operation permission is pending approval, and the reviewer is the procurement manager and the operation permission is pending review.

[0106] Optionally, when it is determined that the next node does not meet the corresponding node flow conditions, the node configuration method further includes: taking the approval result of the next node as the final approval result of the approval request, and sending the final approval result to the terminal.

[0107] Here, when it is determined that the next node does not meet the corresponding node flow conditions, the business server takes the approval result of the next node as the final approval result (i.e., the result obtained after completing the approval request). After obtaining the final approval result, it can push the final approval result to all terminals involved in the approval process, such as the first terminal, second terminal, and third terminal mentioned above, through a page (such as an approval result page), link, or QR code. In this way, the final approval result is synchronized to all terminals involved in the approval process, realizing automated process approval.

[0108] In addition, the node configuration method provided in this application embodiment is applicable when the node information is configured based on the information of the stage of the business process. For example, when an approval request is initiated, the node information is configured by the approval request; after the approval of the current node is completed, the information of the next node is configured by the configuration node information determined by the approval result of the current node.

[0109] It should be noted that the approval result in this application embodiment refers to the result of approval. That is to say, even if a node does not meet the node circulation conditions, its approval result is still the result of approval. This can avoid the node being unable to circulate normally due to the failure of approval.

[0110] like Figure 6 As shown, this application embodiment provides a node configuration device. Figure 6 In this configuration, the node configuration device includes: a request receiving module 601, configured to receive an approval request sent by a first terminal; The first configuration module 602 is configured to configure the information of the current node according to the approval request in response to receiving the approval request; the information sending module 603 is configured to send the information of the current node to the corresponding second terminal for approval; the result receiving module 604 is configured to receive the approval result of the current node returned by the second terminal; the information determining module 605 is configured to determine the configuration node information according to the approval result of the current node in response to receiving the approval result of the current node; and the second configuration module 606 is configured to configure the information of the next node according to the configuration node information.

[0111] This application provides a node configuration device in which, when the request receiving module receives an approval request sent by a first terminal, the first configuration module configures the information of the current node according to the approval request, and after the second terminal approves the current node, the second configuration module configures the information of the next node according to the configuration node information determined by the approval result of the current node. The node information is configured in real time as the approval process progresses, thus improving the flexibility of the approval process.

[0112] Optionally, the second configuration module 606 is further configured to: send a preset configuration page to a third terminal corresponding to the next node; wherein the configuration page includes multiple configuration items corresponding to the configuration node information; In response to receiving an edit request from a third terminal for multiple configuration items, the information of the next node is determined; wherein the edit request is used to edit the configuration item information of multiple configuration items.

[0113] Optionally, the multiple configuration items include at least two of the following: approval role configuration item, approval information configuration item, approval personnel configuration item, and node flow condition configuration item.

[0114] Optionally, the configuration page also includes a form editing permission configuration item; wherein, the form editing permission configuration item is used to restrict the third terminal's editing permission for configuration item information.

[0115] Optionally, the information sending module 603 is also configured to send the information of the next node to the corresponding third terminal for approval.

[0116] Optionally, if the configuration information of the approver configuration item includes information on multiple approvers, then the information sending module 603 is specifically configured as follows: The information of the next node is sent to the third terminal corresponding to each of the multiple approvers for approval. If an approval result is received from a third terminal corresponding to any approver, the approval for the next node is completed.

[0117] Optionally, the node configuration device further includes: The result receiving module 604 is also configured to receive the approval result of the next node returned by the third terminal; The condition determination module (not shown in the figure) is configured to determine whether the next node meets the corresponding node flow conditions in response to receiving the approval result of the next node returned by the third terminal. The execution module is configured to, if it is determined that the next node meets the corresponding node flow conditions, take the next node as the current node and continue to execute the step of determining the configuration node information based on the approval result of the current node.

[0118] Optionally, the node configuration device further includes: The result sending module (not shown in the figure) is configured to, if it is determined that the next node does not meet the corresponding node flow conditions, take the approval result of the next node as the final approval result of the approval request and send the final approval result to the terminal.

[0119] Optionally, the next node can be multiple nodes that execute in parallel.

[0120] This application provides a computer-readable storage medium storing program information. After reading the program information, the computer executes the steps of the node configuration method described in any of the above schemes.

[0121] This application provides a computer program product, including a computer program / instruction, which, when executed by a processor, implements the steps of the node configuration method described in any of the above schemes.

[0122] This application also provides an electronic device, such as... Figure 7As shown, the electronic device includes at least one processor 31 and at least one memory 32. The at least one memory 32 stores program information. After reading the program information, the at least one processor 31 executes the node configuration method described in any of the above method embodiments. The device may further include an input device 33 and an output device 34. The processor 31, memory 32, input device 33, and output device 34 can be communicatively connected. The memory 32, as a non-volatile computer-readable storage medium, can be used to store non-volatile software programs, non-volatile computer-executable programs, and modules. The processor 31 executes various functional applications and data processing by running the non-volatile software programs, instructions, and modules stored in the memory 32, thereby implementing the node configuration method provided in any of the above embodiments. The memory 32 may include a program storage area and a data storage area. The program storage area may store the operating system and at least one application program required for a function; the data storage area may store data created according to the use of the node configuration method, etc. Furthermore, the memory 32 may include high-speed random access memory and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other non-volatile solid-state storage device. In some embodiments, the memory 32 may optionally include memory remotely located relative to the processor 31, and this remote memory may be connected via a network to the apparatus performing the node configuration method. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof. The input device 33 may receive user clicks and generate signal inputs related to user settings and function control of the node configuration method. The output device 34 may include a display device such as a display screen. When the one or more modules are stored in the memory 32 and are run by the one or more processors 31, the node configuration method in any of the above method embodiments is executed.

[0123] As needed, the above technical solutions can be combined to achieve the best technical effect.

[0124] Obviously, the above embodiments are merely illustrative examples for clear explanation and are not intended to limit the implementation. Those skilled in the art will recognize that other variations or modifications can be made based on the above description. It is neither necessary nor possible to exhaustively list all possible implementations here. However, obvious variations or modifications derived therefrom are still within the scope of protection of this application.

Claims

1. A node configuration method, characterized in that, include: In response to receiving an approval request from the first terminal, configure the information of the current node according to the approval request; The information of the current node is sent to the corresponding second terminal for approval. In response to receiving the approval result of the current node returned by the second terminal, the configuration node information is determined based on the approval result of the current node; Configure the information of the next node based on the configured node information.

2. The node configuration method according to claim 1, characterized in that, The step of configuring the information of the next node according to the configured node information includes: A preset configuration page is sent to a third terminal corresponding to the next node; wherein, the configuration page includes multiple configuration items corresponding to the configuration node information; In response to receiving an edit request sent by the third terminal for the plurality of configuration items, the information of the next node is determined; wherein the edit request is used to edit the configuration item information of the plurality of configuration items.

3. The node configuration method according to claim 2, characterized in that, The multiple configuration items include at least two of the following: approval role configuration item, approval information configuration item, approval personnel configuration item, and node flow condition configuration item.

4. The node configuration method according to claim 2 or 3, characterized in that, The configuration page also includes a form editing permission configuration item; wherein, the form editing permission configuration item is used to restrict the third terminal's editing permission for the configuration item information.

5. The node configuration method according to claim 3, characterized in that, The method further includes: The information of the next node is sent to the corresponding third terminal for approval.

6. The node configuration method according to claim 5, characterized in that, If the configuration information of the approver configuration item includes information on multiple approvers, then sending the information of the next node to the corresponding third terminal for approval includes: The information of the next node is sent to the third terminal corresponding to each of the multiple approvers for approval. If an approval result is received from a third terminal corresponding to any approver, the approval for the next node is completed.

7. The node configuration method according to claim 5, characterized in that, The method further includes: In response to receiving the approval result of the next node returned by the third terminal, determine whether the next node meets the corresponding node transfer conditions; If it is determined that the next node meets the corresponding node transfer conditions, then the next node is taken as the current node, and the step of determining the configuration node information based on the approval result of the current node continues.

8. The node configuration method according to claim 7, characterized in that, The method further includes: If it is determined that the next node does not meet the corresponding node flow conditions, the approval result of the next node will be taken as the final approval result of the approval request, and the final approval result will be sent to the terminal.

9. The node configuration method according to claim 1, characterized in that, The next node consists of multiple nodes that execute in parallel.

10. A node configuration device, characterized in that, The device includes: The request receiving module is configured to receive approval requests sent by the first terminal; The first configuration module is configured to, in response to receiving the approval request, configure the information of the current node according to the approval request; The information sending module is configured to send the information of the current node to the corresponding second terminal for approval; The result receiving module is configured to receive the approval result of the current node returned by the second terminal; The information determination module is configured to determine configuration node information based on the approval result of the current node in response to receiving the approval result of the current node. The second configuration module is configured to configure the information of the next node based on the configuration node information.

Images