Workflow implementation method, device, equipment, storage medium and program product

Abstract

The present application discloses a workflow implementation method, apparatus, equipment, storage medium and program product, which relates to the field of computer application technology, by integrating a form plug-in and a process designer plug-in at the front end. The workflow can be implemented by performing corresponding design operations on the front end, without the need to develop complex pages or write program codes for business processes. Specifically, for form design, the form elements are determined by a form plug-in. For flowchart design, the construction of flowcharts and node design are implemented based on the process designer plug-in. The flowchart is stored as a flowchart file in a specified format, and the node authority control data is stored in a database table. In this way, the flowchart file can be directly imported into the process engine and an access interface to the database table can be provided to the process engine, thereby realizing the workflow. The present application has the technical effect of effectively reducing the technical difficulty of workflow implementation and improving the flexibility of the workflow.

Description

Technical Field

[0001] The present application relates to the field of computer application technology, and in particular to a workflow implementation method, apparatus, device, storage medium, and program product. Background Art

[0002] Workflows are the process of expressing and computing the logic and rules that organize the tasks within a workflow using appropriate computer models. Workflows are automated and communicated between multiple participants using computers according to predetermined rules to achieve a specific business goal.

[0003] Workflow management systems are one of the core tools for enterprise information management, used to improve work efficiency and collaboration. Currently, process design and task allocation methods are often relatively fixed. Implementing workflows requires specialized technical personnel to develop interfaces and write business process programs, resulting in limited flexibility and poor user experience.

[0004] How to reduce the technical difficulty of realizing workflow is a technical problem that technicians in this field urgently need to solve. Summary of the Invention

[0005] The present application provides a workflow implementation method, apparatus, equipment, storage medium and program product, which can automatically implement workflows based on the user's design and operation behaviors on the front end without the need to develop complex pages or write program code for business processes. It can effectively reduce the technical difficulty of workflow implementation and improve the flexibility of workflows.

[0006] This application provides a workflow implementation method, including:

[0007] Monitor the front end of the design workflow; wherein the front end integrates a form plug-in that provides a form design operation interface and a process designer plug-in that provides a process design operation interface;

[0008] In response to the form design operation fed back by the form plug-in, determining the form elements required for constructing the workflow;

[0009] In response to the process building operation fed back by the process designer plug-in, a flowchart corresponding to the workflow is constructed in combination with the form elements, and a flowchart file is stored in a specified format;

[0010] In response to the node configuration operation fed back by the process designer plug-in, defining, configuring permissions and binding actions on the nodes of the flowchart, and storing node permission control data in a database table;

[0011] The flowchart file is imported into a process engine and an access interface of the database table is provided to the process engine to implement the workflow.

[0012] This application also provides a workflow implementation device, including:

[0013] A front-end monitoring module is used to monitor the front-end of the design workflow; wherein the front-end integrates a form plug-in that provides a form design operation interface and a process designer plug-in that provides a process design operation interface;

[0014] A form design module, configured to determine form elements required for constructing a workflow in response to the form design operation fed back by the form plug-in;

[0015] A process design module, configured to respond to the process building operation fed back by the process designer plug-in, construct a flowchart corresponding to the workflow in combination with the form elements, and store the flowchart file in a specified format;

[0016] A node design module, configured to define, configure permissions, and bind actions to nodes of the flowchart in response to node configuration operations fed back by the process designer plug-in, and store node permission control data in a database table;

[0017] The workflow implementation module is used to import the flowchart file into a process engine and provide the process engine with an access interface to the database table to implement the workflow.

[0018] The present application also provides an electronic device, comprising: a memory for storing a computer program; and a processor for implementing the steps of any of the above-mentioned workflow implementation methods when executing the computer program.

[0019] The present application also provides a computer-readable storage medium, in which a computer program is stored. When the computer program is executed by a processor, the steps of any of the above-mentioned workflow implementation methods are implemented.

[0020] The present application also provides a computer program product, including a computer program, which implements the steps of any of the above-mentioned workflow implementation methods when executed by a processor.

[0021] This application integrates a form plug-in that provides a form design operation interface and a process designer plug-in that provides a process design operation interface on the front end. It can be achieved that users only need to perform corresponding design operations on the front end, that is, the workflow can be realized without developing complex pages or writing program code for business processes. Specifically, this application divides the workflow implementation into two parts: form design and flowchart design. For form design, the form elements can be determined through the form plug-in. For flowchart design, the construction of the flowchart and the node design can be implemented based on the process designer plug-in. The flowchart is stored as a flowchart file in the specified format, and the node permission control data is stored in the database table. In this way, the flowchart file can be directly imported into the process engine and the database table access interface can be provided to the process engine to realize the workflow. That is, in the workflow implementation process, there is no need to write a process program or carry out the specific design of complex pages. Only design operations need to be performed on the front end.

[0022] This application has the technical effect of effectively reducing the technical difficulty of workflow implementation and improving the flexibility of workflow. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0024] Figure 1 A flowchart of a workflow implementation method provided in an embodiment of the present application;

[0025] Figure 2 An overall schematic diagram of a workflow implementation provided in an embodiment of the present application;

[0026] Figure 3 A schematic diagram of a process definition provided in an embodiment of the present application;

[0027] Figure 4 A process management diagram provided for an embodiment of the present application;

[0028] Figure 5 A schematic diagram of a workflow application process provided in an embodiment of the present application;

[0029] Figure 6 A schematic diagram of a workflow process approval provided in an embodiment of the present application;

[0030] Figure 7 A schematic diagram of the structure of a workflow implementation device provided in an embodiment of the present application;

[0031] Figure 8 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application;

[0032] Figure 9 A schematic diagram of the specific structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0033] The following will be combined with the accompanying drawings in the embodiments of this application to clearly and completely describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are only part of the embodiments of this application, not all of them. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0034] It should be noted that, in the description of this application, the terms "comprises," "includes," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or elements inherent to such process, method, article, or device. The terms "first," "second," etc., in this application are used to distinguish similar objects, and are not used to describe a particular order or sequence.

[0035] In order to enable those skilled in the art to better understand the present application, the present application is further described in detail below with reference to the accompanying drawings and specific implementation methods.

[0036] Please refer to Figure 1 , Figure 1 A flowchart of a workflow implementation method provided in an embodiment of the present application, the method comprising:

[0037] S101. Monitor the front end of the design workflow.

[0038] Among them, the front-end integration provides a form plug-in that provides a form design operation interface and a process designer plug-in that provides a process design operation interface.

[0039] In this application, a form plug-in and a process designer plug-in are integrated into the front end of the workflow design. The form plug-in can provide a form design operation interface for performing form design operations. The process designer plug-in can provide a process design operation interface for performing process design operations.

[0040] In this application, the front end can be monitored to obtain form design operations and process design operations (process building and node configuration).

[0041] S102: In response to the form design operation fed back by the form plug-in, determine the form elements required for constructing the workflow.

[0042] When monitoring is combined with form design, you can clearly define the form elements required to build the corresponding workflow form. Form elements are the components that make up a form. You can choose different components as form elements based on actual business needs.

[0043] In actual applications, various components required by the workflow corresponding to the form can be designed in advance, and the selection service of these components can be provided through the form design operation interface.

[0044] In one specific embodiment of the present application, the components corresponding to pre-built form elements can be numbered and named. These components can then be displayed in a list based on their numbers and names in the form design interface, with corresponding selection boxes set. This allows the user to determine which components have been selected by responding to their selections, facilitating quick batch selection of components. Furthermore, default components (or recommended components) can be set for form elements, allowing users to add, delete, and select components based on the default components, accelerating component selection.

[0045] In actual applications, the form design interface can provide pre-designed components and corresponding drag-and-drop selection services. By dragging components, you can determine which form elements are required to build the workflow.

[0046] Customized form design is the basis for process application and operation. In this embodiment, the front end integrates a form plug-in to allow users to quickly build the form elements required for the process by dragging and dropping.

[0047] In one specific embodiment of the present application, in response to a form design operation fed back by a form plug-in, determining the form elements required for constructing a workflow includes: in response to a dragging action during the form design operation, determining a target component to be dragged from basic components displayed on the form design operation interface and advanced components for dynamically generating data content; and determining the target component as a form element. In this embodiment, form elements are divided into basic components and advanced components to meet business needs of varying complexity.

[0048] Basic components, including but not limited to the following examples.

[0049] Single-line text box: used to collect single-line text information entered by the user, such as simple text data such as name and number. The data format is: {"id":"","type":"TextInput","name":"","key":"","value":""}.

[0050] Multi-line text box: Suitable for scenarios where users need to enter more text content, such as description information, notes, etc. The data format is: "id":"","type":"TextareaInput","name":"","key":"","value":""}.

[0051] Password box: specially used to enter sensitive information such as passwords. The data format is: {"id":"","type":"Password","name":"","key":"","value":""}.

[0052] Radio button: provides a set of mutually exclusive options, and the user can only select one of them. The data format is: {"id":"","type":"SinglePicker","name":"","key":"","options":["Option 1","Option 2"]}.

[0053] Checkbox: Allows users to select multiple options from a group of options. Data format: {"id":"","type":"MultiplePicker","name":"","key":"","options":["Option 1","Option 2"]}.

[0054] Table: used to display and collect structured data. The data format is: {"id":"","type":"TableList","name":"","key":"","props":{"columns":[]}}.

[0055] Advanced components, including but not limited to the following examples:

[0056] Dynamic radio button: Compared with ordinary radio buttons, its options can be dynamically generated according to business rules by configuring the data source, such as province. The data format is: {"id":"","type":"Dynamics_SinglePicker","name":"","key":"","url":"","options":[]}.

[0057] Dynamic checkbox: Similar to the principle of dynamic radio button, options can be dynamically generated by configuring the data source and support multiple selections, such as interests and hobbies. The data format is: {"id":"","type":"Dynamics_MultiplePicker","name":"","key":"","url":"","options":[]}.

[0058] Dynamic table: It can dynamically interact with backend data by configuring the data source according to business needs, such as a list of personnel or equipment stored in the backend. The data format is: {"id":"","type":"Dynamics_TableList","name":"","key":"","props":{"columns":[]}}.

[0059] The data format of the above components and the field parsing are shown in Table 1.

[0060] Table 1 is the definition table of component-field

[0061]

[0062] That is, basic components cover common data input requirements, are easy to understand and use, are quick for users to learn and use, and can meet most basic business scenarios; advanced components are highly flexible and can dynamically adjust content based on real-time data or business rules to adapt to complex and changing business scenarios.

[0063] S103 . In response to the process building operation fed back by the process designer plug-in, a flowchart corresponding to the workflow is constructed in combination with form elements, and the flowchart file is stored in a specified format.

[0064] Process design is a key step in customizing processes. The front-end integrates a process designer plug-in to provide users with a convenient operation method, allowing them to quickly build the required flowchart by dragging and dropping.

[0065] Among them, the flowchart design can be designed in accordance with the BPMN (Business Process Model and Notation) standard specifications.

[0066] Specifically, users can drag and drop to create a flowchart by combining form elements. This means that when building each node in the flowchart, the functionality provided by the specific form elements must be incorporated. For example, if different approval directions are required, a checkbox must be included in the form element.

[0067] In one embodiment of the present application, the process design interface provides a node drag-and-drop operation. Accordingly, in response to the process building operation feedback from the process designer plug-in, a flowchart corresponding to the workflow is constructed in conjunction with form elements. This includes: responding to the node dragging behavior in the process building operation and determining the flowchart's start node, task node, gateway node, and end node in conjunction with the form elements. In other words, in this embodiment, the front-end integrates the process designer plug-in to provide users with a convenient operation method, allowing them to quickly build the flowchart required for the process by dragging and dropping. The start node, as the starting point of the entire workflow, marks the start of the process. In the process definition, the start node is the trigger point for creating a process instance. During page design, users can determine the starting position of the process by dragging the start node icon to the flowchart editing area. Form permissions and applicant permissions can be set for the start node; for details, refer to the node setting section. Task nodes represent tasks in the process that require manual processing. In actual business operations, this includes tasks such as manager approval and personnel approval in the leave application process. After dragging a task node in the flowchart design area, users can configure basic information, form permissions, approval permissions, and binding actions. For details, refer to the node setting steps. Gateway nodes are used to control process branching, merging, and conditional judgments. Common gateways include exclusive gateways (selecting a branch path to continue the process based on conditions) and parallel gateways (opening multiple branches for parallel execution). After dragging an exclusive gateway onto the flowchart, the user must set judgment conditions for it. End nodes: Mark the end of the entire workflow. When the process reaches the end node, the process instance is complete, and the associated tasks and data processing are also concluded.

[0068] In one embodiment of the present application, storing the flowchart file in a specified format includes storing the flowchart file in the specified format according to Extensible Markup Language. That is, the resulting flowchart can be stored in the bpmn.xml format (where bpmn corresponds to the BPMN standard and .xml corresponds to the file extension of Extensible Markup Language), and the flowchart file can be directly called by the process engine.

[0069] Flowcharts can be stored in a predefined format. For example, the process definition data structure is as follows:

[0070] {"id": "Primary key ID",

[0071] "design_id": "Process definition ID",

[0072] "name": "Process name",

[0073] "form_id": "Form ID",

[0074] "process_id": "Process diagram ID",

[0075] "bpmn_xml": "Process definition file content",

[0076] "status": "Process status",

[0077] "version": "Process version",

[0078] "create_time": "",

[0079] "update_time": "",

[0080] "deploy_time": ""

[0081] }.

[0082] For the fields of the above definition process, please refer to Table 2.

[0083] Table 2 is the process-field interpretation table

[0084]

[0085] S104 , in response to the node configuration operation fed back by the process designer plug-in, define the nodes of the flowchart, configure permissions, and bind actions, and then store node permission control data in a database table.

[0086] Process design primarily encompasses two key components: flowchart design and node design. Permission control for process nodes can be stored and managed in independent database tables. Flowchart design and node permission control work together to ensure effective process management and smooth operation.

[0087] In this embodiment, in response to the node configuration operation, the nodes of the flow chart are defined, permissions are configured, and actions are bound, and then the node permission control data is stored in the database table.

[0088] In a specific embodiment of the present application, in response to the node configuration operation feedback from the process designer plug-in, the nodes of the flowchart are defined, permissions configured, and actions bound, including: defining the nodes according to the definition behavior in the node configuration operation; configuring the permissions of the nodes according to the configuration behavior in the node configuration operation; and binding the actions of the nodes according to the binding behavior in the node configuration operation.

[0089] Among them, according to the configuration behavior in the node configuration operation, the node is configured with permissions, including: using the configuration behavior to determine the target permission to be configured; if the target permission is a form permission, then determining the permission details to be configured from hidden permissions, read-only permissions, editable permissions and encrypted permissions, and determining the target field from multiple form fields corresponding to the node; configuring permission details for the target field.

[0090] Among them, according to the configuration behavior in the node configuration operation, the node is configured with permissions, including: using the configuration behavior to determine the target permission to be configured; if the target permission is the approval permission, the fixed object or dynamic object corresponding to the node is used to determine the approval subject.

[0091] Among them, using dynamic objects to determine the approval subject includes: if the dynamic object is an applicant, then if specified conditions are met, the applicant is determined as the approval subject; if the dynamic object is a dynamic form element, then the approval subject is dynamically determined using the value of a specified element in the dynamic form element.

[0092] The nodes of the flowchart are defined, permissions are configured, and actions are bound, including: if the page corresponding to the node has an advanced component, then during the action binding process, the data source is configured for the advanced component in the node to dynamically generate data content.

[0093] For ease of description, the following describes the specific implementation of node definition, permission configuration, and action binding.

[0094] The process node design consists of four parts: general settings (i.e. node definition), permission configuration (such as form permission settings and approval permission settings) and action binding.

[0095] General settings include defining the node ID, node name, node description, and operation type. The node ID and node name correspond to the node information in the flowchart. The operation type, as a node extension attribute, requires additional storage and is categorized as: approval operation, return operation, and transfer operation. These operations are primarily used in the approval process, displaying different approval operations based on different approval nodes.

[0096] Form permission settings: In the design of workflow nodes based on the process engine, form permission settings are an important part of ensuring data security and process specifications. It mainly focuses on fine-grained control at the form field level, covering hidden, read-only, editable, and field encryption. Regarding field encryption, it includes but does not include: [Hidden]: Under specific process nodes, some form fields may not be suitable for display to the current operating user, such as age; [Read-only]: The field content can only be viewed but cannot be modified. For example, the workload completed by an employee; [Editable]: In contrast to the read-only status, the editable permission gives the user the ability to input and modify the form fields; [Encrypted]: For form fields involving sensitive information, such as account numbers and passwords, in addition to the above-mentioned permission control, field encryption processing must also be considered. In the form permission settings, encryption processing can be enabled for specific fields. The encryption method uses a symmetric encryption algorithm (SM4 algorithm). The national encryption algorithm is more secure and reliable. Through form field-level permission control and field encryption settings, form data can be accurately managed at different nodes of the custom workflow based on business needs and role permissions, ensuring both the security and confidentiality of data and the standardization and orderliness of process operations. At the same time, the SM4 national encryption algorithm is more secure and efficient, and meets the requirements of information technology innovation.

[0097] Approval authority settings: In custom workflow node design based on a process engine, setting approval authority is key to ensuring process compliance and efficient flow. Approval authority comes in two types: static and dynamic. Static approval authority is categorized as: designated personnel, designated departments, and designated organizations. Dynamic approval authority is categorized as: applicants and form elements. Specific scenarios include: [Static - Designated Person]: Directly specifying a specific individual as the approver. For example, in the leave application process for some small projects, only the department manager may have approval authority. [Static - Designated Department]: The entire department is designated as the entity with approval authority. For example, in the company's office supply procurement process, a designated department may be responsible for approval. [Static - Designated Organization]: Suitable for large-scale enterprises with complex organizational structures, involving specific organizations composed of multiple departments or subsidiaries. [Dynamic - Applicant]: In certain business processes, the applicant themselves may also have approval authority under specific circumstances. [Dynamic - Form Element Selection]: Dynamically determine the approver based on the value of a specific element in the form. Static approval authority is clear and stable, the approval person is fixed, it is less likely to have unclear authority or buck-passing, and the process execution is efficient; dynamic approval authority is flexible and changeable, and the approval path can be dynamically adjusted according to actual business data and scenarios to adapt to complex and changing business needs and improve the level of process automation.

[0098] Action Binding Settings: Action binding is a core feature for integrating custom processes with third-party systems. Through flexible configuration, it effectively connects to third-party systems and enhances workflow scalability. Specific configuration items include: pre- or post-approval, third-party interface address, and form field mapping. This not only improves system flexibility and scalability, but also simplifies the process of integrating third-party services, supports complex data interaction scenarios, enhances the user experience, and promotes data consistency and accuracy.

[0099] That is, through the cooperation of the above four parts, from basic information definition, data permission management, approval permission control and dynamic field mapping, all aspects of the process nodes are fully covered, and a complete, flexible and scalable workflow system is jointly built to meet the diverse needs of enterprises.

[0100] Specifically, the data structure of the permission control of this process node is as follows:

[0101] {"id": "Primary key ID",

[0102] "design_id": "Process definition ID",

[0103] "process_id": "Process diagram ID",

[0104] "task_id": "Flowchart node ID",

[0105] "task_name": "node name",

[0106] "task_remark": "Node description",

[0107] "task_button": "Node operation type",

[0108] "form_auth": [{"Field ID": {"auth": ["R","H","W"],"encrypted": "true"}}],

[0109] "assignee_auth": {

[0110] "rule": "",

[0111] "val": {"userIds": [],"roleIds": [],"orgIds": [],"formField": []}

[0112] },"task_event": {

[0113] "event": "",

[0114] "url": "Interface address",

[0115] "mapping": [

[0116] {"formField": "","thirdField": ""}]}}.

[0117] The fields of the data structure for node authority control are explained in Table 3 below.

[0118] Table 3 is the data structure of node authority control - field interpretation table

[0119]

[0120] The data structure design provided in this embodiment can achieve fine-grained permission control of process nodes, ensure the security and flexibility of the process, and support dynamic data interaction to improve the scalability of the system.

[0121] SM4 encryption algorithm: This is a block symmetric encryption algorithm used to encrypt and decrypt data to ensure data and information security. This encryption and decryption algorithm is shown in Table 4.

[0122] Table 4 is the annotation table of SM4 encryption algorithm

[0123]

[0124] In actual applications, it can also be implemented with the help of algorithm APIs (application programming interfaces) provided by other cryptographic libraries, which is more in line with the needs of actual development scenarios.

[0125] S105: Import the flowchart file into the process engine and provide the process engine with an access interface to the database table to implement the workflow.

[0126] To facilitate understanding of how to implement the workflow based on the flowchart file and the database table access interface, the following is a brief description of process management.

[0127] Please refer to Figure 4 , process management includes four core functions (edit, publish, suspend, activate), the specific operation sequence Figure 4 shown.

[0128] Process editing (initial creation) is the execution of the process definition module and the starting point of the entire process lifecycle. During this stage, the process is constructed through two core functions: form design and process design. After the initial process definition is completed, the process is in an unpublished state and has not yet been put into actual use.

[0129] Process Release: Once a process has been fully designed and verified, it can be released. The defined process flow chart file is loaded and deployed through the process engine. After successful deployment, the [Process Definition] status is updated synchronously.

[0130] Suspend a process: When you need to temporarily stop further execution of a process due to business adjustments, system maintenance, or other reasons, you can use the process suspension function. Suspend the published process through the process engine. After the suspension is successful, the [Process Definition] status will be updated synchronously.

[0131] Process activation: When the factors that caused the process to suspend are eliminated, the process can be restored to normal through the process activation function; the suspended process is activated through the process engine, and the [Process Definition] status is updated synchronously after successful activation.

[0132] Process Editing (Suspend and then Edit): As business development and needs change, published processes may need to be adjusted. To do this, select Suspend Process -> Edit Process to modify the process. During this time, the process will be unavailable and must be published again after editing is complete.

[0133] The workflow process operation includes two stages: [Process Application] and [Process Approval].

[0134] In a specific embodiment of the present application, a workflow process application is implemented, including: after receiving the process application, determining whether the process definition has been published; if so, using the process engine to obtain the start node identifier of the flowchart; using the start node identifier to obtain the corresponding node permission data, and performing page rendering, loading the corresponding form elements, and obtaining the application page; in response to the application submission operation on the application page, using the process engine to obtain the target node identifier of the flowchart; using the target node identifier to obtain the process node permission data, and performing page rendering, loading the corresponding form elements, and obtaining the approval page; using the process engine to start the process instance, and saving the approver and process definition in the process example to complete the process application process.

[0135] First, a process application is initiated. The workflow management system then determines whether the process definition has been published. If not, the system displays a notification indicating that the process has not been published. If it has, the system proceeds. The system then obtains the flowchart's starting node ID from the process engine and, based on that node ID, retrieves the custom process node permissions. The page then renders, loading the form elements. The user fills out the form and submits the application. After the application is submitted, the system obtains the next node ID from the process engine and, based on that node ID, retrieves the custom process node permissions. The specific approver is then retrieved from the approval permissions. Finally, the process engine initiates the process instance (attaching the approver and process definition to the process instance as process variables), completing the process application.

[0136] In a specific embodiment of the present application, workflow process approval is implemented, including: utilizing a process engine to obtain a to-do list; if there are to-do tasks in the to-do list, selecting a target task from the to-do tasks; utilizing a process engine to obtain a target node identifier corresponding to the target task in the flowchart; utilizing the target node identifier to obtain corresponding node authority data, and performing page rendering, loading corresponding form elements, and obtaining a to-do details page; obtaining an approval operation type in response to an approval operation on the to-do details page; if the approval operation type is an agree operation, utilizing a process engine to obtain a next target node identifier corresponding to the target task in the flowchart; if the approval operation type is a return operation, utilizing a process engine to obtain the most recently approved historical approval record, utilizing the historical approval record to modify the flowchart, utilizing a process engine to complete the current task, and restoring the flowchart; if the approval operation type is a transfer operation, utilizing a process engine to perform task transfer processing.

[0137] First, the system retrieves the logged-in user's to-do list from the process engine. If no to-do list exists, the to-do list is empty. If a to-do list exists, the user can select one. After selecting a to-do list, the system retrieves the node ID of the flowchart corresponding to the to-do list from the process engine. Based on the node ID, it retrieves the custom process node permissions. The system then renders the to-do details page, displaying information such as the action type and form elements.

[0138] Finally, the user performs approval operations based on the information on the page. Approval operation types include consent, return, and transfer. The specific follow-up approval process is as follows.

[0139] a) If the consent operation is performed, the system obtains the next node ID through the process engine, then obtains the custom process node permission information based on the node ID, obtains the specific approver based on the approval permission, and finally completes the current to-do through the process engine.

[0140] b) If a return operation is performed, the system obtains the historical approval records of the process instance through the process engine (in reverse order of approval time), filters the most recently approved record, queries the target node among the corresponding node IDs, and then modifies the flowchart (points the next target node of the current approval node to the filtered node). The current task is then completed through the process engine, and then the flowchart is restored (advantages: dynamically modifying the target node of the process line to realize the rejection function, breaking away from the control constraints of the process line, improving the flexibility and adaptability of the process, and strengthening the process control capability).

[0141] c) If a transfer operation is performed, the user selects the transferee, and the system transfers the task through the process engine.

[0142] The workflow implementation method provided by the embodiment of the present application is applied, by integrating a form plug-in that provides a form design operation interface and a process designer plug-in that provides a process design operation interface at the front end. It can be achieved that the user only performs corresponding design operations at the front end, that is, the workflow can be implemented without developing complex pages or writing program codes for business processes. Specifically, the present application divides the workflow implementation into two parts: form design and flowchart design. For form design, the determination of form elements can be achieved through the form plug-in. For flowchart design, the construction of flowcharts and node design can be achieved based on the process designer plug-in. The flowchart is stored as a flowchart file in a specified format, and the node authority control data is stored in a database table. In this way, the flowchart file can be directly imported into the process engine and the access interface of the database table can be provided to the process engine, thereby realizing the workflow. That is, the workflow implementation process does not require the writing of process programs or the specific design of complex pages. It only requires the design operations to be performed at the front end.

[0143] This application has the technical effect of effectively reducing the technical difficulty of workflow implementation and improving the flexibility of workflow.

[0144] Specifically, the workflow implementation method provided in the embodiment of the present application has the following technical effects in practical applications: Flexibility: Through flexible and changeable process definitions, users can drag and drop to build forms and processes as needed, and easily cope with various complex and changeable business scenarios; through the various operations provided by process management, the process status can be flexibly controlled throughout the entire life cycle of the process, so that the process can be adjusted in time with changes in the company's business and always meet actual operational needs; Accuracy: The form components are rich and field-level permission control can be performed to avoid the entry of irrelevant or erroneous information and ensure accurate data collection; Security: Form permission settings can encrypt sensitive fields to prevent data from being stolen or tampered with during storage and transmission; through field-level permission control, different users' access and operations to form data are restricted to avoid data leakage caused by unauthorized operations and ensure data security; Scalability: Action binding supports configuration interface addresses and form field mappings, and can seamlessly connect to third-party systems to achieve data interaction and functional collaboration between different systems.

[0145] Through the description of the above implementation methods, those skilled in the art can clearly understand that the method according to the above embodiment can be implemented by means of software plus the necessary general hardware platform, and of course it can also be implemented by hardware, but in many cases the former is a better implementation method.

[0146] Please refer to Figure 7 , an embodiment of the present application further provides a workflow implementation device, the device comprising:

[0147] The front-end monitoring module 101 is used to monitor the front-end of the design workflow; wherein the front-end integrates a form plug-in that provides a form design operation interface and a process designer plug-in that provides a process design operation interface;

[0148] The form design module 102 is used to determine the form elements required for constructing the workflow in response to the form design operation fed back by the form plug-in;

[0149] The process design module 103 is used to respond to the process building operation feedback from the process designer plug-in, build a flowchart corresponding to the workflow in combination with form elements, and store the flowchart file in a specified format;

[0150] The node design module 104 is used to define, configure permissions, and bind actions to the nodes of the flowchart in response to the node configuration operation fed back by the process designer plug-in, and store the node permission control data in the database table;

[0151] The workflow implementation module 105 is used to import the flowchart file into the process engine and provide the process engine with an access interface to the database table to implement the workflow.

[0152] The device provided by the embodiment of the present application is applied, by integrating a form plug-in that provides a form design operation interface and a process designer plug-in that provides a process design operation interface at the front end. It can be achieved that the user only performs corresponding design operations at the front end, that is, the workflow can be realized without developing complex pages or writing program codes for business processes. Specifically, the present application divides the workflow implementation into two parts: form design and flowchart design. For form design, the determination of form elements can be achieved through the form plug-in. For flowchart design, the construction of flowcharts and node design can be achieved based on the process designer plug-in. The flowchart is stored as a flowchart file in a specified format, and the node authority control data is stored in a database table. In this way, the flowchart file can be directly imported into the process engine and the access interface of the database table can be provided to the process engine, thereby realizing the workflow. That is, the workflow implementation process does not require the writing of process programs or the specific design of complex pages. It only requires the design operations to be performed at the front end.

[0153] This application has the technical effect of effectively reducing the technical difficulty of workflow implementation and improving the flexibility of workflow.

[0154] In a specific embodiment of the present application, the form design module is specifically used to respond to the dragging behavior in the form design operation, determine the target component to be dragged from the basic components displayed on the form design operation interface and the advanced components for dynamically generating data content; and determine the target component as a form element.

[0155] In a specific implementation of the present application, the node design module is specifically used to configure a data source for the advanced component in the node during the action binding process if the page corresponding to the node has an advanced component to dynamically generate data content.

[0156] In a specific implementation of the present application, the node design module is specifically used to define the node according to the definition behavior in the node configuration operation; configure the node's permissions according to the configuration behavior in the node configuration operation; and bind the node's actions according to the binding behavior in the node configuration operation.

[0157] In a specific implementation of the present application, the node design module is specifically used to use configuration behavior to determine the target permission to be configured; if the target permission is a form permission, the permission details to be configured are determined from hidden permissions, read-only permissions, editable permissions and encrypted permissions, and the target field is determined from multiple form fields corresponding to the node; and the permission details are configured for the target field.

[0158] In a specific implementation of the present application, the node design module is specifically used to use the configuration behavior to determine the target authority to be configured; if the target authority is the approval authority, the approval subject is determined using the fixed object or dynamic object corresponding to the node.

[0159] In a specific implementation of the present application, the node design module is specifically used to, if the dynamic object is an applicant, determine the applicant as the approval subject if the specified conditions are met; if the dynamic object is a dynamic form element, dynamically determine the approval subject using the value of the specified element in the dynamic form element.

[0160] In a specific embodiment of the present application, the process design operation interface provides a node dragging operation; accordingly, the process design module is specifically used to respond to the node dragging behavior of the process building operation, and determine the start node, task node, gateway node and end node of the flowchart in combination with the form elements.

[0161] In a specific implementation of the present application, the process design module is specifically used to store the flowchart file in a specified format according to the extensible markup language.

[0162] In a specific embodiment of the present application, the workflow implementation module is specifically used to determine whether the process definition has been published after receiving a process application; if so, use the process engine to obtain the start node identifier of the flowchart; use the start node identifier to obtain the corresponding node permission data, and perform page rendering, load the corresponding form elements, and obtain the application page; in response to the application submission operation on the application page, use the process engine to obtain the target node identifier of the flowchart; use the target node identifier to obtain the process node permission data, and perform page rendering, load the corresponding form elements, and obtain the approval page; use the process engine to start the process instance, and save the approver and process definition in the process example to complete the process application process.

[0163] In a specific implementation of the present application, the workflow implementation module is specifically used to use the process engine to obtain a to-do list; if there are to-do tasks in the to-do list, select the target task from the to-do tasks; use the process engine to obtain the target node identifier corresponding to the target task in the flowchart; use the target node identifier to obtain the corresponding node authority data, and perform page rendering, load the corresponding form elements, and obtain the to-do details page; in response to the approval operation of the to-do details page, obtain the approval operation type; if the approval operation type is an approval operation, use the process engine to obtain the next target node identifier corresponding to the target task in the flowchart; if the approval operation type is a return operation, use the process engine to obtain the most recently approved historical approval record, use the historical approval record to modify the flowchart, use the process engine to complete the current task, and restore the flowchart; if the approval operation type is a transfer operation, use the process engine to perform task transfer processing.

[0164] For the description of the features in the embodiment corresponding to the workflow implementation device, please refer to the relevant description of the embodiment corresponding to the workflow implementation method, and no further details will be given here.

[0165] Corresponding to the above method embodiment, an embodiment of the present application further provides an electronic device. The electronic device described below and the workflow implementation method described above can refer to each other.

[0166] See also Figure 8 As shown, the electronic device includes:

[0167] Memory 332, for storing computer programs;

[0168] The processor 322 is configured to implement the steps of the workflow implementation method of the above method embodiment when executing a computer program.

[0169] For details, please refer to Figure 9 , Figure 9 This is a schematic diagram of the specific structure of an electronic device provided in this embodiment. This electronic device may vary significantly due to different configurations or performance. It may include one or more central processing units (CPUs) (for example, one or more processors) and memory 332. The memory 332 stores one or more computer programs 342 or data 344. The memory 332 may be temporary storage or permanent storage. The program stored in the memory 332 may include one or more modules (not shown), each of which may include a series of instruction operations in the data processing device. Furthermore, the processor 322 may be configured to communicate with the memory 332 to execute the series of instruction operations in the memory 332 on the electronic device 301.

[0170] The electronic device 301 may further include one or more power supplies 326 , one or more wired or wireless network interfaces 350 , one or more input / output interfaces 358 , and / or one or more operating systems 341 .

[0171] The steps in the workflow implementation method described above can be implemented by the structure of an electronic device.

[0172] Corresponding to the above method embodiments, embodiments of the present application further provide a readable storage medium. The readable storage medium described below and the workflow implementation method described above can be referenced in correspondence with each other. Embodiments of the present application further provide a computer-readable storage medium storing a computer program, wherein the computer program is configured to execute the steps of any of the above-described workflow implementation method embodiments when executed.

[0173] In an exemplary embodiment, the computer-readable storage medium may include, but is not limited to, various media that can store computer programs, such as a USB flash drive, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk, or an optical disk.

[0174] An embodiment of the present application further provides a computer program product, which includes a computer program. When the computer program is executed by a processor, the steps of any of the above-mentioned workflow implementation method embodiments are implemented.

[0175] An embodiment of the present application further provides another computer program product, including a non-volatile computer-readable storage medium, wherein the non-volatile computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps in any of the above-mentioned workflow implementation method embodiments are implemented.

[0176] Those skilled in the art may further appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the above description has generally described the composition and steps of each example according to function. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art may 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 this application.

[0177] Specific examples are used herein to illustrate the principles and implementation methods of this application. The description of the above embodiments is only intended to help understand the method and core ideas of this application. It should be noted that those skilled in the art may make several improvements and modifications to this application without departing from the principles of this application, and such improvements and modifications also fall within the scope of protection of this application.

Claims

1. A workflow implementation method, characterized in that: include: Monitor the front end of the design workflow; wherein the front end integrates a form plug-in that provides a form design operation interface and a process designer plug-in that provides a process design operation interface; In response to the form design operation fed back by the form plug-in, determining the form elements required for constructing the workflow; In response to the process building operation fed back by the process designer plug-in, construct a flowchart corresponding to the workflow in combination with the form elements, and store the flowchart file in a specified format, including storing the flowchart file in a specified format according to extensible markup language; In response to the node configuration operation fed back by the process designer plug-in, defining, configuring permissions and binding actions for the nodes of the flowchart, and storing node permission control data in a database table; Importing the flowchart file into a process engine and providing the process engine with an access interface to the database table to implement the workflow; Wherein, implementing the workflow includes: Obtaining a to-do list using the process engine; If there are to-do tasks in the to-do list, selecting a target task from the to-do tasks; Using the process engine to obtain the target node identifier corresponding to the target task in the process diagram; Use the target node identifier to obtain the corresponding node authority data, render the page, load the corresponding form element, and obtain the to-do details page; In response to an approval operation on the to-do details page, obtaining an approval operation type; If the approval operation type is an approval operation, using the process engine to obtain the next target node identifier corresponding to the target task in the process diagram; If the approval operation type is a return operation, the process engine is used to obtain the most recently approved historical approval record, and after modifying the flowchart using the historical approval record, the process engine is used to complete the current task and restore the flowchart; If the approval operation type is a transfer operation, the process engine is used to perform task transfer processing.

2. The method according to claim 1, characterized in that In response to the form design operation fed back by the form plug-in, form elements required for constructing a workflow are determined, including: In response to the dragging behavior in the form design operation, determining a target component to be dragged from basic components displayed on the form design operation interface and advanced components for dynamically generating data content; The target component is determined to be the form element.

3. The method according to claim 2, characterized in that Defining the nodes of the flowchart, configuring permissions and binding actions, including: If the page corresponding to the node has the advanced component, then during the action binding process, a data source is configured for the advanced component in the node to dynamically generate data content.

4. The method according to claim 1, wherein In response to the node configuration operation fed back by the process designer plug-in, defining, configuring permissions, and binding actions on the nodes of the flowchart, including: Defining the node according to the defined behavior in the node configuration operation; Performing permission configuration on the node according to the configuration behavior in the node configuration operation; Action binding is performed on the node according to the binding behavior in the node configuration operation.

5. The method according to claim 4, characterized in that According to the configuration behavior in the node configuration operation, the node is configured with permissions, including: Determine the target permission to be configured using the configuration behavior; If the target permission is a form permission, the permission details to be configured are determined from hidden permissions, read-only permissions, editable permissions, and encrypted permissions, and the target field is determined from the multiple form fields corresponding to the node; The permission details are configured for the target field.

6. The method according to claim 4, characterized in that According to the configuration behavior in the node configuration operation, the node is configured with permissions, including: Determine the target permission to be configured using the configuration behavior; If the target authority is approval authority, the approval subject is determined using the fixed object or dynamic object corresponding to the node.

7. The method according to claim 6, characterized in that Determining the approval subject by utilizing the dynamic object includes: If the dynamic object is an applicant, then the applicant is determined as the approval subject if the specified conditions are met; wherein the specified conditions are that the applicant is a pre-specified person or department; If the dynamic object is a dynamic form element, the approval subject is dynamically determined using the value of a specified element in the dynamic form element; wherein the specified element includes a user ID, a user role, an organization ID, and a form field.

8. The method according to claim 1, characterized in that The process design operation interface provides node dragging operation; Accordingly, in response to the process building operation fed back by the process designer plug-in, a flowchart corresponding to the workflow is constructed in combination with the form elements, including: In response to the node dragging behavior of the process building operation, and in combination with the form elements, the start node, task node, gateway node and end node of the flow chart are determined.

9. The method according to any one of claims 1 to 8, characterized in that Implementing the workflow includes: After receiving the process application, determine whether the process definition has been published; If yes, then using the process engine to obtain the start node identifier of the flow chart; Using the start node identifier, the corresponding node authority data is obtained, and the page is rendered, the corresponding form element is loaded, and the application page is obtained; In response to an application submission operation on the application page, obtaining a target node identifier of the flowchart using the process engine; Using the target node identifier to obtain the process node authority data, and then rendering the page, loading the corresponding form element, and obtaining the approval page; The process engine is used to start a process instance, and the approver and the process definition are saved in the process instance to complete the process application process.

10. A workflow implementation device, characterized in that: include: A front-end monitoring module is used to monitor the front-end of the design workflow; wherein the front-end integrates a form plug-in that provides a form design operation interface and a process designer plug-in that provides a process design operation interface; A form design module, configured to determine form elements required for constructing a workflow in response to the form design operation fed back by the form plug-in; a process design module, configured to respond to the process building operation fed back by the process designer plug-in, construct a flowchart corresponding to the workflow in combination with the form elements, and store the flowchart file in a specified format, including storing the flowchart file in a specified format according to extensible markup language; A node design module, configured to define, configure permissions, and bind actions to nodes of the flowchart in response to node configuration operations fed back by the process designer plug-in, and store node permission control data in a database table; A workflow implementation module, configured to import the flowchart file into a process engine and provide the process engine with an access interface to the database table to implement the workflow; Wherein, implementing the workflow includes: Obtaining a to-do list using the process engine; If there are to-do tasks in the to-do list, selecting a target task from the to-do tasks; Using the process engine to obtain the target node identifier corresponding to the target task in the process diagram; Use the target node identifier to obtain the corresponding node authority data, render the page, load the corresponding form element, and obtain the to-do details page; In response to an approval operation on the to-do details page, obtaining an approval operation type; If the approval operation type is an approval operation, using the process engine to obtain the next target node identifier corresponding to the target task in the process diagram; If the approval operation type is a return operation, the process engine is used to obtain the most recently approved historical approval record, and after modifying the flowchart using the historical approval record, the process engine is used to complete the current task and restore the flowchart; If the approval operation type is a transfer operation, the process engine is used to perform task transfer processing.

11. An electronic device, characterized in that: include: Memory for storing computer programs; A processor, configured to implement the steps of the workflow implementation method according to any one of claims 1 to 9 when executing the computer program.

12. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program, wherein the computer program, when executed by a processor, implements the steps of the workflow implementation method according to any one of claims 1 to 9.

13. A computer program product comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the workflow implementation method according to any one of claims 1 to 9 are implemented.

Images