Cross-system digital workflow integration system, and workflow management method and system

Abstract

The present application relates to the technical field of workflow management, and discloses a cross-system digital workflow integration system, and a workflow management method and system. The method comprises: acquiring a customized workflow configuration table, and analyzing the customized workflow configuration table to determine logic control information; and on the basis of logic control information, performing management configuration on a default cyclic approval workflow template to generate a digital workflow. The present application can effectively improve the approval efficiency and reduce the error rate, so that the approval requirements of different service scenarios are met.

Description

Cross-system digital workflow integration system, workflow management method and system Technical Field

[0001] The present application relates to the field of workflow management technology, and specifically to a cross-system digital workflow integration system, a workflow management method and a system. Background Art

[0002] In the field of information technology innovation, the workflow approval process in the SAP (System Applications and Products) ERP (Enterprise Resource Planning) system has low approval efficiency and cannot be modified accordingly according to different approval requirements, resulting in an inability to meet the needs of complex business scenarios.

[0003] Summary of the Invention

[0004] In view of this, the present application provides a cross-system digital workflow integration system, a workflow management method and a system to solve the problem that the relevant workflow approval process has low approval efficiency and cannot be modified accordingly according to different approval requirements, resulting in the inability to meet the needs of complex business scenarios.

[0005] In a first aspect, the present application provides a workflow management method, the method comprising:

[0006] Obtain the custom process configuration table, analyze the custom process configuration table, and determine the logical control information;

[0007] Based on logical control information, the preset cyclic approval process template is managed and configured to generate a digital workflow.

[0008] A workflow management method provided in this embodiment manages and configures a preset cyclic approval process template based on logical control information, which can effectively improve approval efficiency and reduce error rate. Through the custom process configuration table, it can be freely customized according to different approval requirements, meeting the approval requirements of different business scenarios.

[0009] In an optional embodiment, the customized process configuration table includes: process code, step number, condition, process name, step description, approver type, approver ID, approver name, skippable step approval code, approval type, currency, approval amount, rejection node and text length.

[0010] In an optional embodiment, based on the logical control information, a preset cyclic approval process template is managed and configured to generate a digital workflow, including:

[0011] Determine approval conditions, countersignature node configuration information, economic node configuration information, and rejection node configuration information based on logical control information;

[0012] Configure approval conditions for approval nodes in the preset cyclic approval process template;

[0013] Based on the countersignature node configuration information, economic node configuration information and rejection node configuration information, the preset cyclic approval process template after the configuration of approval conditions is configured to generate a digital workflow.

[0014] A workflow management method provided in this embodiment configures the co-signing node configuration information, economic node configuration information, rejection node configuration information and approval conditions for a preset cyclic approval process template, meets the approval requirements of different business scenarios, expands the functional scope and depth of the workflow, enhances the usability and applicability of the workflow in the business system, improves the execution efficiency and accuracy of the business process, and reduces the risk of process errors.

[0015] In an optional embodiment, the method further includes:

[0016] In response to a user approval withdrawal operation, an approval withdrawal operation is performed in an approval node in a digital workflow.

[0017] This embodiment provides a workflow management method that expands the functionality of the workflow by performing an approval withdrawal operation in an approval node in a digital workflow, thereby enabling the workflow to adapt to the needs of various application scenarios.

[0018] In an optional embodiment, in response to a user's approval withdrawal operation, performing an approval withdrawal operation in an approval node in a digital workflow includes:

[0019] Obtain user roles and determine user approval permissions based on the user roles;

[0020] The reading information of the approval node is obtained. When the reading information of the approval node is in an unread state, based on the user's approval authority, in response to the user's approval withdrawal operation, the approval status corresponding to the approval node is modified to rejected.

[0021] This embodiment provides a workflow management method that strictly controls the calling authority of the workflow's pending withdrawal service, ensuring the stability and security of the workflow, and expands the functionality of the workflow through approval and withdrawal operations, so that the workflow can adapt to the needs of various application scenarios.

[0022] In a second aspect, the present application provides a workflow management system, the system comprising:

[0023] The analysis module is used to obtain the custom process configuration table, analyze the custom process configuration table, and determine the logic control information;

[0024] The management module is used to manage and configure the preset cyclic approval process template based on logical control information and generate a digital workflow.

[0025] In an optional implementation, the management module includes:

[0026] a determination unit, configured to determine approval conditions, countersignature node configuration information, economic node configuration information, and rejection node configuration information based on the logic control information;

[0027] The granting unit is used to configure approval conditions for approval nodes in the preset cyclic approval process template;

[0028] The configuration unit is used to configure the preset cyclic approval process template after the approval conditions are configured based on the counter-signing node configuration information, economic node configuration information and rejection node configuration information to generate a digital workflow.

[0029] In an optional embodiment, the method further includes:

[0030] The withdrawal module is used to respond to the user's approval withdrawal operation and perform the approval withdrawal operation in the approval node in the digital workflow.

[0031] In an optional embodiment, the withdrawal module includes:

[0032] The acquisition unit is used to obtain the user role and determine the user approval authority based on the user role;

[0033] The modification unit is used to obtain the reading information of the approval node, and when the reading information of the approval node is in the unread state, based on the user's approval authority, in response to the user's approval withdrawal operation, modify the approval status corresponding to the approval node to rejected.

[0034] In a third aspect, the present application provides a cross-system digital workflow integration system, including:

[0035] The workflow management system and the third-party system, the workflow management system is set in the cloud platform, the cloud platform is connected to the third-party system through a cloud connector, and the workflow management system is used to execute the workflow management method of the above-mentioned first aspect or any corresponding embodiment thereof. BRIEF DESCRIPTION OF THE DRAWINGS

[0036] In order to more clearly illustrate the specific implementation methods of the present application or the technical solutions in the prior art, the following is a brief introduction to the drawings required for use in the specific implementation methods or the description of the prior art. Obviously, the drawings described below are some implementation methods of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0037] FIG1 is a flow chart of a workflow management method according to an embodiment of the present application;

[0038] FIG2 is a schematic diagram of a traditional approval and development model according to an embodiment of the present application;

[0039] FIG3 is a schematic diagram of a preset cyclic approval process template according to an embodiment of the present application;

[0040] FIG4 is a flow chart of another workflow management method according to an embodiment of the present application;

[0041] FIG5 is a flow chart of another workflow management method according to an embodiment of the present application;

[0042] 6 is a schematic diagram of the system operations when an applicant initiates a process and an approver approves the process according to an embodiment of the present application;

[0043] FIG7 is a structural block diagram of a workflow management system according to an embodiment of the present application;

[0044] FIG8 is a schematic structural diagram of a cross-system digital workflow integration system according to an embodiment of the present application. DETAILED DESCRIPTION

[0045] To make the purpose, technical solutions, and advantages of the embodiments of the present application more clear, the technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without making creative efforts shall fall within the scope of protection of this application.

[0046] In the field of information technology innovation, in the workflow of SAP ERP system, the workflows between different system modules or different functional systems are usually separated, making it difficult to achieve effective integration.

[0047] The integration of related BTP (Business Technology Platform) Workflow products requires synchronizing process data to the cloud platform's HanaCloud (a database management system), which can lead to compliance risks. Furthermore, BTP Workflow does not support functions such as additional signatures, co-signatures, approval withdrawals, and read notifications. Approver information is also not synchronized with personnel-related information. Therefore, when faced with frequently changing personnel information, a significant amount of operational support is required. Furthermore, for intranet OA systems, manually selecting the next approver can lead to compliance risks in approvals.

[0048] According to an embodiment of the present application, an embodiment of a workflow management method is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0049] In this embodiment, a workflow management method is provided, which can be used in the above-mentioned mobile terminal. FIG1 is a flowchart of a workflow management method according to an embodiment of the present application. As shown in FIG1 , the process includes the following steps:

[0050] Step S101: Obtain a custom process configuration table, analyze the custom process configuration table, and determine logic control information.

[0051] Specifically, the customized process configuration table includes: process code, step number, condition, process name, step description, approver type, approver ID, approver name, skippable step approval code, approval type, currency, approval amount, rejection node and text length.

[0052] Optionally, the approval code for the skippable step is a code generated based on the process business data. If a step with a skip code is configured, the approval node will be skipped by default. If the process business data generates a corresponding skip code, this step will not be skipped. The approval type can distinguish between public tasks and normal approval tasks. Public tasks will send the to-do items to multiple users at the same time, but only one user is required to approve this step to pass (at the same time, the to-do tasks in other users' to-do lists disappear); the currency and the two approval amounts respectively define the currency and authorization range of the economic authorization of the approval step. If the approval amount involved in the process does not meet the corresponding configuration requirements (different currencies need to be converted by exchange rate), the approval flow will not go through the step with economic authorization configured; the approval flow defaults to the applicant step. If a rejection node is configured, the approval history can be used to find the approver information corresponding to the rejection node and assign it to the information of the next approver; the approver type can be compatible with the department head and corresponding position personnel information in the personnel master data.

[0053] Optionally, a custom process configuration table is constructed based on enterprise rules and enterprise risks, and the custom process configuration table is then displayed graphically so that users can make corresponding modifications based on actual needs.

[0054] Optionally, in the custom process configuration table, approvers can interact with positions and departments in the personnel master data, which can reduce the operation and maintenance workload caused by personnel changes.

[0055] Step S102: Based on the logic control information, the preset cyclic approval process template is managed and configured to generate a digital workflow.

[0056] Specifically, the traditional approval development model is shown in Figure 2. If business changes require tedious development changes, to address the defects of the traditional approval development model, the preset cyclic approval process template shown in Figure 3 is used to encapsulate the SAP BTP Workflow flowchart. The judgment node logic after the approver is controlled by a custom process configuration table.

[0057] Optionally, digital workflows can be equipped with automatic data validation to effectively prevent some errors. Validation types include pre-built form fields that check data and mark errors, pre-filled fields, automatic and dynamic routing based on data, etc. Well-defined workflows with automatic validation can reduce errors, speed up processing time, shorten employee training time and speed up approval.

[0058] Optionally, workflow management intuitively displays workflow loading to determine task priorities; and the workflow has automatic notification and reminder functions. Tasks are assigned to individuals or specific user roles and displayed by role, allowing different roles to act more agilely and quickly, and the workflow will notify relevant personnel before the deadline to ensure the smooth operation of the automated workflow.

[0059] This embodiment provides a workflow management method that manages and configures preset cyclic approval process templates based on logical control information, which can effectively improve approval efficiency and reduce error rates. Through the custom process configuration table, it can be freely customized according to different approval requirements, meeting the approval requirements of different business scenarios.

[0060] In this embodiment, a workflow management method is provided, which can be used in the above-mentioned mobile terminal. FIG4 is a flowchart of a workflow management method according to an embodiment of the present application. As shown in FIG4 , the process includes the following steps:

[0061] Step S401: Obtain a custom process configuration table, analyze the custom process configuration table, and determine logic control information. For details, please refer to step S101 of the embodiment shown in FIG1 , which will not be described in detail here.

[0062] Step S402: Based on the logic control information, the preset cyclic approval process template is managed and configured to generate a digital workflow.

[0063] Specifically, the above step S402 includes:

[0064] Step S4021: Determine the approval conditions, countersignature node configuration information, economic node configuration information, and rejection node configuration information based on the logic control information.

[0065] Step S4022: configuring approval conditions for the approval nodes in the preset cyclic approval process template.

[0066] Specifically, the logic control information is used to control the judgment of "whether to reject" in the preset cyclic approval process template.

[0067] Step S4023: Based on the countersignature node configuration information, the economic node configuration information, and the rejection node configuration information, the preset cyclic approval process template after the approval conditions are configured is configured to generate a digital workflow.

[0068] A workflow management method provided in this embodiment configures the co-signing node configuration information, economic node configuration information, rejection node configuration information and approval conditions for a preset cyclic approval process template, meets the approval requirements of different business scenarios, expands the functional scope and depth of the workflow, enhances the usability and applicability of the workflow in the business system, improves the execution efficiency and accuracy of the business process, and reduces the risk of process errors.

[0069] In this embodiment, a workflow management method is provided, which can be used in the above-mentioned mobile terminal. FIG5 is a flowchart of a workflow management method according to an embodiment of the present application. As shown in FIG5 , the process includes the following steps:

[0070] Step S501: Obtain a custom process configuration table, analyze the custom process configuration table, and determine logic control information. For details, please refer to step S401 of the embodiment shown in FIG4 , which will not be described in detail here.

[0071] Step S502: Based on the logic control information, the preset cyclic approval process template is managed and configured to generate a digital workflow. For details, please refer to step S401 of the embodiment shown in FIG4 , which will not be described in detail here.

[0072] Step S503: In response to the user's approval withdrawal operation, an approval withdrawal operation is performed in the approval node in the digital workflow.

[0073] Specifically, the above step S503 includes:

[0074] Step S5031: Obtain the user role and determine the user approval authority based on the user role.

[0075] Specifically, as a system administrator, a "To-do Withdrawal Service" is published. The service can redirect the approver's to-do to the to-do of the previous approver. The calling authority of the "To-do Withdrawal Service" needs to be strictly controlled to ensure the stability and security of the system. Only to-dos that meet the following conditions can call the service: Among them, the service calling user must be the most recent approver of the process to which the to-do belongs, that is, the withdrawal function cannot be withdrawn across steps.

[0076] Optionally, the approval form can only be viewed by the system administrator, process initiator, approver, and relevant readers. If others view it, an error message corresponding to insufficient permissions will be returned.

[0077] Step S5032: Obtain the reading information of the approval node. When the reading information of the approval node is in the unread state, based on the user's approval authority, in response to the user's approval withdrawal operation, change the approval status corresponding to the approval node to rejected.

[0078] Specifically, as shown in Figure 6, when the applicant adds a reviewer for the designated process in the review center, the corresponding personnel information and process information are recorded in the reading information record table; when the reviewer opens the process viewing page from the review center, the corresponding reading information record is updated to the "read" status; when the user performs an approval or rejection operation, the reading information of the current approval node is updated to the "approved" status or "rejected" status.

[0079] Optionally, the to-do item to be withdrawn must not have any user operations performed on it, including opening, approving, or rejecting it; the process approval has not ended, that is, the last approver cannot perform the withdrawal operation.

[0080] This embodiment provides a workflow management method that strictly controls the calling authority of the workflow's pending withdrawal service, ensuring the stability and security of the workflow, and expands the functionality of the workflow through approval and withdrawal operations, so that the workflow can adapt to the needs of various application scenarios.

[0081] A workflow management method is described below through a specific embodiment.

[0082] Example 1:

[0083] With BTP Workflow as the core and its functions expanded, the approval architecture implements functions such as additional signatures, countersignatures, approval withdrawal, and review and notification. The steps include:

[0084] Custom process engine implementation method:

[0085] Use the circular approval method to encapsulate the SAP BTP Workflow flowchart, use custom logic (i.e., logical control information) to control the judgment of "whether to reject", and customize the logic judgment based on the custom process configuration table; in the custom process configuration table, approvers can interact with the positions and departments in the personnel master data, which can reduce the operation and maintenance workload caused by personnel changes; at the same time, add the countersignature node, economic authorization and rejection node configuration in the custom process configuration table to meet the approval conditions of different business scenarios.

[0086] Compared with the traditional approval process development model, the preset cyclic approval process template can effectively improve approval efficiency and reduce error rate. At the same time, it can also be freely customized according to different approval requirements to meet the approval needs of different member units.

[0087] To-do withdrawal implementation method:

[0088] Although the process engine itself does not provide a recall function, the encapsulated approval flow is a cyclic approval mode, so the subordinate approvers and to-do owners can be easily changed without affecting the overall approval process.

[0089] As a system administrator, publish a "To-do Revocation Service" that redirects the approver's To-do to the previous approver's To-do. The call permissions for the "To-do Revocation Service" must be strictly controlled to ensure system stability and security. Only To-dos that meet the following conditions can call this service:

[0090] 1. The user who calls the service must be the most recent approver of the to-do process. This means that the withdrawal function cannot be used to withdraw the to-do from another step.

[0091] 2. The to-do item to be withdrawn must not have any user actions, including opening, approving, or rejecting.

[0092] 3. The process approval has not been completed, that is, the last approver cannot perform the withdrawal operation.

[0093] How to implement the reading function:

[0094] The process engine itself does not provide a reading function, but it can record reading information in a separate table structure and record the status of pending reading and read. The reading information record has the same structure as the approval history table.

[0095] When a user adds a reviewer for a specified process in the Review Center, the corresponding personnel information and process information will be recorded in the reading information record table; when the reviewer opens the process viewing page from the Review Center, the corresponding reading information record will be updated to the "read" status.

[0096] In addition, the approval form can only be viewed by the system administrator, process initiator, approver and relevant readers. Others will receive an error message indicating insufficient permissions.

[0097] In this embodiment, a workflow management system is also provided, which is used to implement the above-mentioned embodiments and optional implementation methods. Details already described will not be repeated here. As used below, the term "module" may refer to a combination of software and / or hardware that implements a predetermined function. Although the systems described in the following embodiments are preferably implemented in software, implementation using hardware, or a combination of software and hardware, is also possible and contemplated.

[0098] This embodiment provides a workflow management system, as shown in FIG7 , including:

[0099] The analysis module 701 is used to obtain the custom process configuration table, analyze the custom process configuration table, and determine the logic control information;

[0100] The management module 702 is used to manage and configure the preset cyclic approval process template based on the logical control information to generate a digital workflow.

[0101] In some optional implementations, the management module 702 includes:

[0102] A determination unit, configured to determine approval conditions, countersignature node configuration information, economic node configuration information, and rejection node configuration information based on the logic control information;

[0103] The granting unit is used to configure approval conditions for approval nodes in the preset cyclic approval process template;

[0104] The configuration unit is used to configure the preset cyclic approval process template after the approval conditions are configured based on the counter-signing node configuration information, economic node configuration information and rejection node configuration information to generate a digital workflow.

[0105] In some optional embodiments, the method further includes:

[0106] The withdrawal module is used to respond to the user's approval withdrawal operation and perform the approval withdrawal operation in the approval node in the digital workflow.

[0107] In some optional embodiments, the withdrawal module includes:

[0108] The acquisition unit is used to obtain the user role and determine the user approval authority based on the user role;

[0109] The modification unit is used to obtain the reading information of the approval node, and when the reading information of the approval node is in the unread state, based on the user's approval authority, in response to the user's approval withdrawal operation, modify the approval status corresponding to the approval node to rejected.

[0110] The further functional description of each of the above modules and units is the same as that of the above corresponding embodiments and will not be repeated here.

[0111] The workflow management system in this embodiment is presented in the form of functional units, where the units refer to ASIC (Application Specific Integrated Circuit) circuits, processors and memories that execute one or more software or fixed programs, and / or other devices that can provide the above functions.

[0112] The embodiment of the present application provides a cross-system digital workflow integration system, as shown in FIG8 , including:

[0113] The workflow management system 801 and the third-party system 802 , the workflow management system 801 is set in the cloud platform 803 , the cloud platform is connected to the third-party system 802 via a cloud connector 804 , and the workflow management system 801 is used to execute the above-mentioned workflow management method.

[0114] Specifically, the cloud platform 803 is connected and interacted with the third-party system 802 through the cloud connector 804, and the business data will not be saved to the cloud platform 803. This method can ensure the security and privacy of the data and better control the scope of data use. At the same time, the cloud connector 804 has high availability and scalability, which can meet the needs of complex business scenarios.

[0115] Optionally, the workflow management system 801 may adopt the workflow service of the SAP platform.

[0116] This embodiment provides a cross-system digital workflow integration system that achieves secure and isolated storage of business system information while ensuring the stability and consistency of data transmission; and it enables unified collaborative work between multiple different business systems, enabling more efficient completion of complex business processes, improving productivity and customer satisfaction.

[0117] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the embodiments of this application.

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

[0119] In the several embodiments provided in the embodiments of the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0120] Units described as separate components may or may not be physically separate, and components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0121] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0122] If the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the embodiment of the present application, or the part that contributes to the prior art or the part of the technical solution, can be embodied in the form of a software product, which is stored in a storage medium and includes a number of instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the various embodiments of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0123] Although the embodiments of the present application have been described with reference to the accompanying drawings, those skilled in the art may make various modifications and variations without departing from the spirit and scope of the present application, and such modifications and variations shall fall within the scope defined by the appended claims.

Claims

1. A workflow management method, characterized in that: The method comprises: Obtain a custom process configuration table, analyze the custom process configuration table, and determine logic control information; Based on the logic control information, the preset cyclic approval process template is managed and configured to generate a digital workflow.

2. The method according to claim 1, characterized in that The custom process configuration table includes: process code, step number, condition, process name, step description, approver type, approver ID, approver name, skippable step approval code, approval type, currency, approval amount, rejection node and text length.

3. The method according to claim 1, characterized in that Based on the logic control information, the preset cyclic approval process template is managed and configured to generate a digital workflow, including: Determine approval conditions, countersignature node configuration information, economic node configuration information, and rejection node configuration information based on the logic control information; Configuring the approval condition for the approval node in the preset cyclic approval process template; Based on the counter-signing node configuration information, economic node configuration information and rejection node configuration information, the preset cyclic approval process template after the approval conditions are configured is configured to generate the digital workflow.

4. The method according to claim 1, characterized in that Also includes: In response to a user approval withdrawal operation, an approval withdrawal operation is performed in an approval node in the digital workflow.

5. The method according to claim 4, characterized in that In response to the user's approval withdrawal operation, performing the approval withdrawal operation in the approval node in the digital workflow includes: Obtaining a user role, and determining user approval authority based on the user role; The reading information of the approval node is obtained, and when the reading information of the approval node is in an unread state, based on the user approval authority, in response to the user approval withdrawal operation, the approval state corresponding to the approval node is modified to rejected.

6. A workflow management system, characterized in that: The system comprises: An analysis module, used to obtain a custom process configuration table, analyze the custom process configuration table, and determine logic control information; The management module is used to manage and configure the preset cyclic approval process template based on the logical control information to generate a digital workflow.

7. The system according to claim 6, characterized in that The management module comprises: A determination unit, configured to determine approval conditions, countersignature node configuration information, economic node configuration information, and rejection node configuration information based on the logic control information; An assigning unit, used for configuring the approval condition for the approval node in the preset cyclic approval process template; The configuration unit is used to configure the preset cyclic approval process template after the approval conditions are configured based on the counter-signing node configuration information, economic node configuration information and rejection node configuration information to generate the digital workflow.

8. The system according to claim 6, characterized in that Also includes: The withdrawal module is used to respond to the user's approval withdrawal operation and perform an approval withdrawal operation in the approval node in the digital workflow.

9. The system according to claim 8, characterized in that The withdrawal module comprises: An acquisition unit, used to acquire a user role and determine the user approval authority based on the user role; The modification unit is used to obtain the reading information of the approval node, and when the reading information of the approval node is in an unread state, based on the user approval authority, in response to the user approval withdrawal operation, the approval state corresponding to the approval node is modified to rejected.

10. A cross-system digital workflow integration system, characterized in that: include: A workflow management system and a third-party system, wherein the workflow management system is arranged in a cloud platform, and the cloud platform is connected via a cloud The device is connected to the third-party system, and the workflow management system is used to execute the workflow management method described in any one of claims 1 to 5.

Images