Method, device, equipment and medium for integrating heterogeneous service system and workflow system

Abstract

The invention relates to the field of computer application, in particular to a method, a device, equipment and a medium for integrating a heterogeneous business system and a workflow system.The method comprises the steps that business entity modeling is conducted on business receipts of the heterogeneous system, and a business table structure, a field type and a business entity referenced by associated fields are described in a setting form; binding a corresponding heterogeneous service system data query API (Application Program Interface) for the created service entity; performing approval form modeling, binding a mapping relationship between form control display contents and business entity fields, generating an approval form, and mapping business form data in real time by the approval form; performing flow modeling, defining a flow chart and binding a flow event, and calling a heterogeneous service system data query API to write back service form data at the event execution time; and modifying a submission button response event of the business form, and calling an open standard API of the workflow system to initiate an approval process. And flow centralized management and control are realized, approval entrances are unified, and consistent approval experience is provided.

Description

Technical Field

[0001] The present application relates to the field of computer application technology, and in particular to a method, apparatus, device and medium for integrating heterogeneous business systems with workflow systems. Background Art

[0002] During enterprise informatization efforts, legacy heterogeneous business systems often exist. However, enterprises seek to achieve centralized process control, unify approval portals, and enhance user experience through a workflow system. Process flow is closely tied to business forms, requiring approvers to review form data when handling tasks. Furthermore, process branching conditions are often defined using business fields, with the value of a form field determining the path forward. For example, leave applications exceeding three days require approval from the general manager. This close connection between processes and forms necessitates workflow systems supporting form approval across heterogeneous systems. Two solutions are commonly employed to address this issue.

[0003] Solution 1: Business fields used in the workflow are used as input data (process variables) for the process definition. When the heterogeneous system initiates the process and calls the API, the input parameters are passed. The workflow system only stores the key field values of the business document via the process variables. Furthermore, the approval form viewed by the approver is embedded in the heterogeneous system form via an iframe. This solution's business fields used in the process definition conditions frequently change, and storing only the key business field values cannot meet the requirements of dynamic process evolution. Furthermore, the heterogeneous system's business forms and the workflow system's internal forms will have inconsistent styles, preventing a consistent user experience. Solution 2: Develop a set of business forms within the workflow system, push the heterogeneous system data to the workflow system, and then initiate the process within the workflow system. This solution requires creating a corresponding database table in the workflow system for each type of integrated business document to store the business system data. This places significant pressure on the workflow system's database and prevents heterogeneous systems with strict security policies from dumping business data.

[0004] In view of the shortcomings of the above two solutions, there is an urgent need for a more complete integration method of heterogeneous business systems and workflow systems to achieve efficient integration of heterogeneous business systems and workflow systems, meet the needs of centralized control of enterprise processes and unified approval portals, and improve user experience. Summary of the Invention

[0005] To solve the problem of incompatibility between historical heterogeneous business systems and workflows during enterprise informatization construction, the present invention provides a method, device, equipment and medium for integrating heterogeneous business systems with workflow systems, realizing centralized process control capabilities, unifying approval entrances, and improving user experience.

[0006] In a first aspect, the technical solution of the present invention provides a method for integrating a heterogeneous business system with a workflow system, comprising the following steps: S1. Model the business entity of the business documents of heterogeneous systems in the workflow system, and describe the business entity of the business table structure, field type and associated field references in a set form; S2. Bind the corresponding heterogeneous business system data query API to the created business entity; S3. Modeling an approval form in the workflow system, binding the mapping relationship between the form control display content and the business entity fields, and generating an approval form. The approval form maps the business form data in real time; S4. Model the process in the workflow system, define the flowchart and bind the process events. When the event is executed, call the heterogeneous business system data query API to write back the business form data. S5. Modify the submit button response event of the business form in the heterogeneous business system and call the standard API opened by the workflow system to initiate the approval process.

[0007] Business entity modeling of heterogeneous system forms is performed in the form of JsonSchema, and real-time calls are made through interfaces to query heterogeneous system business data, so as to enable the form engine to bind approval form data and the process engine to determine the direction of the process based on business fields.

[0008] Specifically, by binding data query APIs and real-time calls, there is no need to migrate data from heterogeneous business systems to the workflow system, reducing the complexity and risk of data migration while avoiding additional pressure on heterogeneous system databases. Business entity modeling and real-time data binding enable the workflow system to dynamically adapt to changes in the data structure of heterogeneous business systems to meet the needs of dynamic business evolution. Approval forms map business form data in real time to ensure that the form data viewed by approvers is consistent with the data in heterogeneous systems, avoiding style inconsistencies and providing a consistent approval experience. This achieves centralized control of heterogeneous business system processes and a unified approval portal, improving the efficiency and convenience of enterprise information management and facilitating centralized management and monitoring of processes by leaders and managers.

[0009] As a further limitation of the technical solution of the present invention, in step S1, business entity modeling includes: Analyze the entity type and field data type of business documents; Define the business entity number, name and field information in the workflow system, or directly build a business entity model by importing a conceptual data model file; the business entity model is used to select business fields when setting flow conditions in the process definition; the conceptual data model file is used to describe the data structure, entity relationship and field definition of heterogeneous business systems.

[0010] By importing conceptual data model files, you can quickly build business entity models, reducing manual definition workload and improving modeling efficiency. By clearly analyzing the entity types and field data types of business documents, the business entity model can accurately map the data structures of heterogeneous business systems, providing an accurate foundation for subsequent process definition and approval form modeling. The business entity model can be used to select business fields when setting flow conditions in process definitions, making process definitions more flexible and enabling flexible process flow configuration based on actual business needs.

[0011] As a further limitation of the technical solution of the present invention, step S2 specifically includes: In the workflow system integration object definition module, the created business entity is bound to the corresponding heterogeneous business system data query API, and the workflow system dynamically calls the data query API at runtime to obtain the data of the business form in the heterogeneous business system, and generates a native program file through the just-in-time compilation mechanism.

[0012] Dynamically calling the data query API at runtime enables real-time access to business form data from heterogeneous business systems, ensuring that the data displayed on the approval form is up-to-date, improving the accuracy and timeliness of approvals. Generating native program files through a just-in-time compilation mechanism optimizes system efficiency and stability, reduces runtime delays and errors, and improves overall system performance.

[0013] As a further limitation of the technical solution of the present invention, in step S3, the approval form is modeled in the form designer of the workflow system by using a drag-and-drop form modeling method, specifically including: Select the form template type and business entity; Select the required business fields and adjust the layout to generate the approval form.

[0014] The drag-and-drop form modeling method makes the creation of approval forms more intuitive and simple, reducing operational complexity and improving modeling efficiency. You can select the form template type and business entity based on actual business needs, flexibly select required business fields and adjust the layout to generate approval forms that meet business needs, enhancing the system's flexibility and adaptability.

[0015] As a further limitation of the technical solution of the present invention, in step S4, process modeling is performed in the process designer of the workflow system, specifically including: After building the form, create a process category based on the business entity, bind process events to the process category, and define the logic of process start, submission, cancellation, completion, and termination events; Draw a flowchart in the process designer and configure the start, approval, gateway, and end nodes.

[0016] The configuration of the start node includes: Set the process name; Bind the process start event, call the data query API, and obtain business data in real time; Define process variables for passing parameters to subsequent nodes; The configuration content of the approval node includes: approver settings, form binding and event binding; The configuration of the gateway node includes: Define branch logic based on business fields and parse business data in real time through a just-in-time compilation mechanism.

[0017] The configuration of the end node includes: Bind the process completion event and call the heterogeneous business system data query API to mark the business document status as approved; Configure optional callback parameters.

[0018] By creating process categories and binding process events, process management becomes clearer and more standardized, making it easier to categorize, manage, and monitor different types of business processes. By drawing flowcharts and configuring various nodes in the process designer, you can flexibly design processes based on actual business needs to meet the process requirements of different business scenarios.

[0019] The detailed configuration content from the start node to the end node enables full process control of the entire approval process, ensuring that each link of the process can be executed according to the predetermined logic. Calling the data query API and the just-in-time compilation mechanism in the start node and the gateway node can obtain and parse business data in real time, providing support for dynamic decision-making in the process. The gateway node defines branching logic based on business fields, allowing the process to dynamically select different execution paths based on actual business data, enhancing the flexibility and adaptability of the process. The end node binds the process completion event and calls the data query API to mark the business document status as approved, achieving timely feedback on process results and updating of business data, ensuring that the data in heterogeneous business systems is consistent with the approval process.

[0020] As a further limitation of the technical solution of the present invention, step S5 specifically includes: Add approval-related buttons to the forms of heterogeneous business systems; Set the document internal code and process classification parameters, publish the form after completing the settings, and initiate the approval process by calling the workflow system API.

[0021] By adding approval-related buttons to the forms of heterogeneous business systems and initiating the approval process by calling the workflow system API, seamless integration of heterogeneous business systems and workflow systems is achieved. Users can directly initiate the approval process within the heterogeneous business system interface without switching systems, improving the user experience. Setting document internal codes and process classification parameters makes the initiation of approval processes more flexible and accurate, and can be customized to meet the needs of different business documents and processes.

[0022] In a second aspect, the technical solution of the present invention further provides a device for integrating heterogeneous business systems with workflow systems, including an integration object definition module, a data query API binding module, a form design module, a process design module, and a process initiation module; The integrated object definition module is used to model business entities for business documents of heterogeneous systems in the workflow system, and to describe the business entities referenced by business table structures, field types, and associated fields in a set format; The data query API binding module is used to bind the corresponding heterogeneous business system data query API to the created business entity and dynamically obtain business data; The form design module is used to model the approval form in the workflow system, bind the mapping relationship between the form control display content and the business entity fields, and generate the approval form. The approval form maps the business form data in real time; The process design module is used to model processes in the workflow system, define flowcharts, and bind process events. When events are executed, the heterogeneous business system data query API is called to write back business form data. The process initiation module is used to modify the submit button response event of the business form in the heterogeneous business system and call the standard API opened by the workflow system to initiate the approval process.

[0023] The integration of heterogeneous business systems and workflow systems is divided into multiple modules, each responsible for a specific function. This makes the overall design clearer and more modular, facilitating development, maintenance, and expansion. It covers all key steps, including business entity modeling, data query API binding, approval form modeling, process modeling, and approval process initiation, providing a complete solution for integrating heterogeneous business systems and workflow systems.

[0024] As a further limitation of the technical solution of the present invention, the integrated object definition module is specifically used to analyze the entity type and field data type of the business document; define the business entity number, name and field information in the workflow system, or directly build the business entity model by importing the conceptual data model file; the business entity model is used to select the business field when setting the flow conditions in the process definition; the conceptual data model file is used to describe the data structure, entity relationship and field definition of the heterogeneous business system.

[0025] As a further limitation of the technical solution of the present invention, the data query API binding module is specifically used to bind the corresponding heterogeneous business system data query API to the business entity created in the workflow system integration object definition module, and the workflow system dynamically calls the data query API to obtain data during runtime, and generates native program files through the just-in-time compilation mechanism.

[0026] As a further limitation of the technical solution of the present invention, the form design module is used to model the approval form through a drag-and-drop form modeling method in the form designer of the workflow system, specifically including: selecting the form template type and business entity; checking the required business fields and adjusting the layout to generate the approval form.

[0027] As a further limitation of the technical solution of the present invention, the process design module performs process modeling in the process designer of the workflow system, specifically including: after building the form, creating process categories according to business entities, binding process events in the process categories, and defining the process start, submission, cancellation, completion and termination event logic; drawing a flowchart in the process designer, and configuring the start, approval, gateway and end nodes.

[0028] As a further limitation of the technical solution of the present invention, the configuration content of the start node includes: Set the process name; Bind the process start event, call the data query API, and obtain business data in real time; Define process variables for passing parameters to subsequent nodes; The configuration content of the approval node includes: approver settings, form binding and event binding; The configuration of the gateway node includes: Define branch logic based on business fields and parse business data in real time through a just-in-time compilation mechanism.

[0029] The configuration of the end node includes: Bind the process completion event and call the heterogeneous business system data query API to mark the business document status as approved; Configure optional callback parameters.

[0030] As a further limitation of the technical solution of the present invention, the process initiation module is specifically used to add approval-related buttons in the form of a heterogeneous business system; set the document internal code and process classification parameters, publish the form after completing the setting, and initiate the approval process by calling the workflow system API.

[0031] In a third aspect, the technical solution of the present invention also provides an electronic device, comprising: at least one processor; and a memory communicatively connected to the at least one processor; the memory stores computer program instructions that can be executed by the at least one processor, and the computer program instructions are executed by the at least one processor so that the at least one processor can execute the method for integrating heterogeneous business systems with workflow systems as described in the first aspect.

[0032] This approach provides hardware support for integrating heterogeneous business systems with workflow systems, ensuring that the method can be run on actual electronic devices and improving its feasibility. The collaborative work of the processor and memory enables efficient execution of each step in the integration method, ensuring system performance and responsiveness.

[0033] In a fourth aspect, the technical solution of the present invention also provides a non-transitory computer-readable storage medium, which stores computer instructions, and the computer instructions enable the computer to execute the method for integrating heterogeneous business systems with workflow systems as described in the first aspect.

[0034] It can be seen from the above technical solutions that this application has the following advantages: business entity modeling, form modeling, and process modeling are performed on the business documents to be integrated in the workflow system, and then the workflow engine opens a set of standard external API interfaces for heterogeneous systems to call when initiating processes. Process approvers perform task approval in the workflow system to drive the process flow. Finally, the workflow engine modifies the business data in the heterogeneous system by binding the business data write-back API through process events. This effectively solves the problem of the process engine driving the business process flow of the existing business system without storing the business data in the workflow system, realizes centralized process control, unifies the approval entrance, and provides a consistent approval experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0035] In order to more clearly illustrate the technical solution of the present application, the following is a brief introduction to the drawings required for the description. 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.

[0036] Figure 1 A flowchart of a method provided in an embodiment of the present invention.

[0037] Figure 2 A block diagram of a device provided in an embodiment of the present invention. DETAILED DESCRIPTION

[0038] In order to make the application objectives, features, and advantages of this application more obvious and easy to understand, the technical solutions protected by this application will be clearly and completely described below using specific embodiments and drawings. Obviously, the embodiments described below 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.

[0039] like Figure 1 As shown, an embodiment of the present invention provides a method for integrating a heterogeneous business system with a workflow system, comprising the following steps: S1. Model the business entity of the business documents of heterogeneous systems in the workflow system, and describe the business entity of the business table structure, field type and associated field references in a set form; In this step, business entity modeling includes: Analyze the entity type and field data type of business documents; Define the business entity number, name and field information in the workflow system, or directly build a business entity model by importing a conceptual data model file; the business entity model is used to select business fields when setting flow conditions in the process definition; the conceptual data model file is used to describe the data structure, entity relationship and field definition of heterogeneous business systems.

[0040] S2. Bind the corresponding heterogeneous business system data query API to the created business entity; This step specifically includes: In the workflow system integration object definition module, the created business entity is bound to the corresponding heterogeneous business system data query API, and the workflow system dynamically calls the data query API at runtime to obtain the data of the business form in the heterogeneous business system, and generates a native program file through the just-in-time compilation mechanism.

[0041] During runtime, the workflow system provides preprocessing and dynamic loading methods. It first automatically generates program source code from business entities and compiles it into native program files that can be run directly, providing a basic operating framework; during runtime, it dynamically calls heterogeneous system query APIs to obtain data and loads data synchronously.

[0042] S3. Modeling an approval form in the workflow system, binding the mapping relationship between the form control display content and the business entity fields, and generating an approval form. The approval form maps the business form data in real time; In this step, the approval form is modeled using the drag-and-drop form modeling method in the form designer of the workflow system, specifically including: Select the form template type and business entity; Select the required business fields and adjust the layout to generate the approval form.

[0043] The form designer provides a variety of form templates. You can create the required template type by checking it, select the business entity, check the required business fields, optimize and adjust the layout on the opened page, and obtain the approval form.

[0044] S4. Model the process in the workflow system, define the flowchart and bind the process events. When the event is executed, call the heterogeneous business system data query API to write back the business form data. The process modeling includes building a process classification and binding process events to the process classification, defining the event logic of process start, submission, cancellation, completion, termination, etc. When the relevant event type occurs, calling the heterogeneous system API to write back the business data; after building the process classification, adding a new process definition, binding the process classification, placing the start, approval, gateway, end and other nodes on the process design canvas as required, building a flowchart, and configuring as needed. In this step, process modeling is performed in the process designer of the workflow system, specifically including: After building the form, create a process category based on the business entity, bind process events to the process category, and define the logic of process start, submission, cancellation, completion, and termination events; Draw a flowchart in the process designer and configure the start, approval, gateway, and end nodes. It should be noted that the configuration of the start node includes: Set the process name; Bind the process start event, call the data query API, and obtain business data in real time; Define process variables for passing parameters to subsequent nodes; The configuration content of the approval node includes: approver settings, form binding and event binding; The configuration of the gateway node includes: Define branch logic based on business fields and parse business data in real time through a just-in-time compilation mechanism.

[0045] The configuration of the end node includes: Bind the process completion event and call the heterogeneous business system data query API to mark the business document status as approved; Configure optional callback parameters.

[0046] S5. Modify the submit button response event of the business form in the heterogeneous business system and call the standard API exposed by the workflow system to initiate the approval process. The heterogeneous business system modifies the submit button response event of the business form by adding approval-related buttons such as Submit for Approval and Cancel Submission to the form, adding approval-related interaction events when the buttons are clicked, setting relevant parameters such as the document internal code and process classification, and publishing the form to initiate the approval process after the settings are completed.

[0047] This step specifically includes: Add approval-related buttons to the forms of heterogeneous business systems; Set the document internal code and process classification parameters, publish the form after completing the settings, and initiate the approval process by calling the workflow system API.

[0048] It should be noted that the approval form pulls business form data in real time through the API, but does not store business data to avoid redundancy and security risks. The business form handles business logic, and the approval form handles process logic, collaborating through the workflow engine.

[0049] Add a "Submit for Approval" button to a business form in a heterogeneous system (such as a sales order form). Bind the button event to the standard API of the workflow system (such as startProcess(billType, billId)).

[0050] API call parameters: billType: document type (such as "sales order"), corresponding to the process classification in the workflow system.

[0051] billId: unique identifier of the business document (such as order number), used for subsequent data query and association.

[0052] Workflow system response: Match the predefined process model according to billType.

[0053] Call the heterogeneous system API (getBillJsonDataById) to obtain business data and generate an approval form.

[0054] Create a process instance and enter the first approval node (such as department manager approval).

[0055] The approval process is as follows: Initiation content: After calling the workflow system API, the approval process (such as multi-level approval and conditional branching) is started.

[0056] Process definition: pre-modeled in the workflow system, including: Approval nodes (such as manager approval and financial review).

[0057] Gateway rules (such as "Amount > 10,000 requires director's approval").

[0058] Write back events (update business status after approval).

[0059] In this application, the business form and approval form are physically separated and dynamically interact via an API to avoid data synchronization issues. The approval form renders business data using standardized templates, eliminating the need for managers to switch systems. The workflow system does not store business data, thus meeting enterprise security policies.

[0060] The business form is the data source, and the approval form is the process carrier. The two are dynamically linked via APIs and document IDs. The business form submission button triggers the approval process in the workflow system. Subsequent approval operations are completed within the workflow system, but the data always comes from heterogeneous business systems. Shadow forms and API calls enable an integrated model with "zero data storage and full process control."

[0061] JsonSchema is a standard format based on JSON (JavaScript Object Notation) that defines the structure, constraints, and validation rules for JSON data. It provides a standardized way to describe the expected format of JSON data, including data types, field constraints, and data relationships. JsonSchema's primary purpose is to ensure the integrity and consistency of JSON data and provide a universal way to verify that JSON data conforms to the expected structure.

[0062] This embodiment of the present invention provides a method for integrating workflows across heterogeneous business systems. This method uses JsonSchema to model business entities in heterogeneous system forms. It then uses real-time interface calls to query heterogeneous system business data, enabling the form engine to bind approval form data and the process engine to determine process flow based on business fields. Taking a sales order as an example, the method includes the following steps: Step 101: In the workflow system integration object definition module, business entity modeling is performed for business documents in heterogeneous systems. This model uses JSON Schema to describe the business table structure, field types, and the business entities referenced by associated fields. This business entity model can be used to select business fields when setting flow conditions in process definitions.

[0063] In the workflow system, you first need to analyze and sort out the business document entity types. Taking sales orders as an example, the required fields and corresponding data types are shown in Table 1. After the analysis is complete, define and add business entities in the system based on the analysis results. Add the business entity number, name, and other required information. You can also directly build business entities by importing a CDM file.

[0064] Table 1: Fields and corresponding data types

[0065] Step 102: In the workflow system integration object definition module, bind the business entity created in step 101 to the corresponding heterogeneous system data query API: getBillJsonDataById(String billType, String billId). The data query interface requires the return value to be JSON format data that conforms to the business entity JsonSchema defined in step 101.

[0066] The workflow system provides a just-in-time compilation mechanism. During design, business entities are defined and associated with data query APIs. At runtime, the workflow system provides preprocessing and dynamic loading methods. It automatically generates program source code from business entities and compiles it into native, runnable program files, providing a basic operational framework. During runtime, it dynamically calls heterogeneous system query APIs to retrieve data and load data synchronously, streamlining deployment and improving operational efficiency and stability.

[0067] Step 103: Create the approval form in the workflow system's form designer. The form designer provides a drag-and-drop form modeling method and supports binding form controls to business entity fields. The workflow system provides multiple form templates. Select the template type you want to create. Then, select the business entity created in Step 101, select the required sales order-related business fields, and optimize the layout on the page that opens to create the sales order form.

[0068] Step 104: Perform process modeling in the workflow system process designer, draw a flow chart, and bind process events to call heterogeneous system APIs at each execution time to write back business data.

[0069] After building the form, create a process category based on the business entity. Bind process events to the process category and define event logic for process start, submission, cancellation, completion, and termination. When relevant event types occur, heterogeneous system APIs are called to write back business data. After building the process category, add a new process definition and bind it to the process category. On the process design canvas, place nodes such as start, approval, gateway, and end as needed to build a flowchart and configure as needed.

[0070] Step 105: Modify the submit button response event of the business form in the heterogeneous business system and call the standard API exposed by the workflow system to initiate the process. Add approval-related buttons such as Submit for Approval and Cancel Submission to the form. Click the button to add an approval-related interaction event. Set relevant parameters such as the document internal code and process category to complete the setup. After the form is published, click the button on the form to initiate the approval process.

[0071] The method provided in this application effectively solves the problem of driving the business process flow of existing business systems by a process engine without storing business data in a workflow system, realizes centralized process control, unifies the approval entrance, provides a consistent approval experience, and has good promotion value.

[0072] like Figure 2 As shown, an embodiment of the present invention further provides a device for integrating a heterogeneous business system with a workflow system, comprising an integration object definition module, a data query API binding module, a form design module, a process design module, and a process initiation module; The integrated object definition module is used to model business entities for business documents of heterogeneous systems in the workflow system, and to describe the business entities referenced by business table structures, field types, and associated fields in a set format; The data query API binding module is used to bind the corresponding heterogeneous business system data query API to the created business entity and dynamically obtain business data; The form design module is used to model the approval form in the workflow system, bind the mapping relationship between the form control display content and the business entity fields, and generate the approval form. The approval form maps the business form data in real time; The process design module is used to model processes in the workflow system, define flowcharts, and bind process events. When events are executed, the heterogeneous business system data query API is called to write back business form data. The process initiation module is used to modify the submit button response event of the business form in the heterogeneous business system and call the standard API opened by the workflow system to initiate the approval process.

[0073] In some embodiments, the integration object definition module is specifically used to analyze the entity type and field data type of a business document; define the business entity number, name, and field information in the workflow system, or directly construct a business entity model by importing a conceptual data model file; the business entity model is used to select business fields when setting flow conditions in the process definition; the conceptual data model file is used to describe the data structure, entity relationship, and field definition of heterogeneous business systems. Further, the integration object definition module includes: Entity analysis unit, used to analyze and sort out business document entity types; The definition adding unit is used to add definitions in the system according to the analysis results. The business entity model is used to select business fields when setting flow conditions in the process definition.

[0074] In some embodiments, the data query API binding module is specifically used to bind the corresponding heterogeneous business system data query API to the business entity created in the workflow system integration object definition module, and the workflow system dynamically calls the data query API to obtain data at runtime, and generates a native program file through a just-in-time compilation mechanism.

[0075] The data query API binding module includes: Just-in-time compilation unit, used to define business entities at design time and associate data query APIs with the entities; The dynamic loading unit is used to provide preprocessing and dynamic loading methods at runtime. It first automatically generates program source code from business entities and compiles it into native program files that can be run directly, providing a basic operating framework; at runtime, it dynamically calls heterogeneous system query APIs to obtain data and loads data synchronously.

[0076] In some embodiments, the form design module is used to model the approval form through a drag-and-drop form modeling method in the form designer of the workflow system, specifically including: selecting the form template type and business entity; checking the required business fields and adjusting the layout to generate the approval form.

[0077] The form design module includes: The template selection unit is used to provide a variety of form templates and create the required template type by checking the box; A field binding unit is used to select the business entity and check the required business fields; The layout optimization unit is used to optimize and adjust the layout of the opened page to obtain the approval form.

[0078] In some embodiments, the process design module performs process modeling in the process designer of the workflow system, specifically including: after building the form, creating a process classification based on the business entity, binding process events in the process classification, and defining the process start, submission, cancellation, completion and termination event logic; drawing a flowchart in the process designer, and configuring the start, approval, gateway and end nodes.

[0079] The configuration of the start node includes: Set the process name; Bind the process start event, call the data query API, and obtain business data in real time; Define process variables for passing parameters to subsequent nodes; The configuration content of the approval node includes: approver settings, form binding and event binding; The configuration of the gateway node includes: Define branch logic based on business fields and parse business data in real time through a just-in-time compilation mechanism.

[0080] The configuration of the end node includes: Bind the process completion event and call the heterogeneous business system data query API to mark the business document status as approved; Configure optional callback parameters.

[0081] Through the above, the process design module includes: The process classification unit is used to build process classifications and bind process events to the process classifications to define event logic such as process start, submission, cancellation, completion, and termination; The flowchart construction unit is used to add new process definitions, bind process categories, place start, approval, gateway, end and other nodes on the process design canvas as needed, build a flowchart, and configure it as needed.

[0082] In some embodiments, the process initiation module is specifically used to add approval-related buttons in the form of a heterogeneous business system; set the document internal code and process classification parameters, publish the form after completing the settings, and initiate the approval process by calling the workflow system API.

[0083] Through the above, the process initiation module includes: Button response unit, used to modify the submit button response event of the business form in the heterogeneous business system; The parameter setting unit is used to add approval-related interaction events when clicking a button, and to set relevant parameters such as document internal code and process classification; The process initiation unit is used to publish the form to initiate the approval process after completing the settings.

[0084] An embodiment of the present invention further provides an electronic device, comprising: a processor, a communication interface, a memory, and a communication bus, wherein the processor, the communication interface, and the memory communicate with each other via the communication bus. The communication bus can be used to transmit information between the electronic device and the sensor. The processor can call the logic instructions in the memory to execute the following method: S1. Business entity modeling is performed on the business documents of the heterogeneous system in the workflow system, and the business entity referenced by the business table structure, field type, and associated fields is described in a set form; S2. The corresponding heterogeneous business system data query API is bound to the created business entity; S3. Approval form modeling is performed in the workflow system, and the mapping relationship between the form control display content and the business entity field is bound to generate an approval form; S4. Process modeling is performed in the workflow system, a flowchart is defined, and process events are bound. When the event is executed, the heterogeneous business system API is called to write back the business data; S5. The submit button response event of the business form is modified in the heterogeneous business system, and the standard API open to the workflow system is called to initiate the approval process.

[0085] Furthermore, the logical instructions in the aforementioned memory can be implemented as software functional units and, when sold or used as independent products, can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, or the portion that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in various embodiments of the present invention. The aforementioned storage media include various media capable of storing program code, such as USB flash drives, mobile hard drives, read-only memories (ROMs), random access memories (RAMs), magnetic disks, or optical disks.

[0086] An embodiment of the present invention provides a non-transitory computer-readable storage medium, which stores computer instructions, and the computer instructions enable a computer to execute the method provided by the above-mentioned method embodiment, for example, including: S1, business entity modeling of business documents of heterogeneous systems in a workflow system, describing the business table structure, field types and business entities referenced by associated fields in a set form; S2, binding the corresponding heterogeneous business system data query API for the created business entity; S3, modeling an approval form in the workflow system, binding the mapping relationship between the form control display content and the business entity field, and generating an approval form; S4, modeling a process in the workflow system, defining a flowchart and binding process events, and calling the heterogeneous business system API to write back business data when the event is executed; S5, modifying the submit button response event of the business form in the heterogeneous business system, and calling the standard API open to the workflow system to initiate the approval process.

[0087] The above description of the disclosed embodiments is intended to enable one skilled in the art to implement or use the present invention. Various modifications to these embodiments will be readily apparent to one skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present invention. Therefore, the present invention is not limited to the embodiments shown herein but is intended to conform to the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for integrating heterogeneous business systems with workflow systems, characterized in that: The steps include: S1. Model the business entity of the business documents of heterogeneous systems in the workflow system, and describe the business entity of the business table structure, field type and associated field references in a set form; S2. Bind the corresponding heterogeneous business system data query API to the created business entity; S3. Modeling an approval form in the workflow system, binding the mapping relationship between the form control display content and the business entity fields, and generating an approval form. The approval form maps the business form data in real time; S4. Model the process in the workflow system, define the flowchart and bind the process events. When the event is executed, call the heterogeneous business system data query API to write back the business form data. S5. Modify the submit button response event of the business form in the heterogeneous business system and call the standard API opened by the workflow system to initiate the approval process.

2. The method for integrating heterogeneous business systems with workflow systems according to claim 1, characterized in that: In step S1, business entity modeling includes: Analyze the entity type and field data type of business documents; Define the business entity number, name and field information in the workflow system, or directly build a business entity model by importing a conceptual data model file; the business entity model is used to select business fields when setting flow conditions in the process definition; the conceptual data model file is used to describe the data structure, entity relationship and field definition of heterogeneous business systems.

3. The method for integrating heterogeneous business systems with workflow systems according to claim 2, characterized in that: Step S2 specifically includes: In the workflow system integration object definition module, the created business entity is bound to the corresponding heterogeneous business system data query API, and the workflow system dynamically calls the data query API at runtime to obtain the data of the business form in the heterogeneous business system, and generates a native program file through the just-in-time compilation mechanism.

4. The method for integrating heterogeneous business systems with workflow systems according to claim 3, characterized in that: In step S3, the approval form is modeled in the form designer of the workflow system by dragging and dropping the form modeling method, which specifically includes: Select the form template type and business entity; Select the required business fields and adjust the layout to generate the approval form.

5. The method for integrating heterogeneous business systems with workflow systems according to claim 4, characterized in that: In step S4, process modeling is performed in the process designer of the workflow system, specifically including: After building the form, create a process category based on the business entity, bind process events to the process category, and define the logic of process start, submission, cancellation, completion, and termination events; Draw a flowchart in the process designer and configure the start, approval, gateway, and end nodes.

6. The method for integrating heterogeneous business systems with workflow systems according to claim 5, characterized in that: The configuration of the start node includes: Set the process name; Bind the process start event, call the data query API, and obtain business data in real time; Define process variables for passing parameters to subsequent nodes; The configuration content of the approval node includes: approver settings, form binding and event binding; The configuration of the gateway node includes: Define branch logic based on business fields and parse business data in real time through a just-in-time compilation mechanism. The configuration of the end node includes: Bind the process completion event and call the heterogeneous business system data query API to mark the business document status as approved; Configure optional callback parameters.

7. The method for integrating heterogeneous business systems with workflow systems according to claim 6, characterized in that: Step S5 specifically includes: Add approval-related buttons to the forms of heterogeneous business systems; Set the document internal code and process classification parameters, publish the form after completing the settings, and initiate the approval process by calling the workflow system API.

8. A device for integrating heterogeneous business systems with workflow systems, characterized in that: It includes integration object definition module, data query API binding module, form design module, process design module and process initiation module; The integrated object definition module is used to model business entities for business documents of heterogeneous systems in the workflow system, and to describe the business entities referenced by business table structures, field types, and associated fields in a set format; The data query API binding module is used to bind the corresponding heterogeneous business system data query API to the created business entity and dynamically obtain business data; The form design module is used to model the approval form in the workflow system, bind the mapping relationship between the form control display content and the business entity fields, and generate the approval form. The approval form maps the business form data in real time; The process design module is used to model processes in the workflow system, define flowcharts, and bind process events. When events are executed, the heterogeneous business system data query API is called to write back business form data. The process initiation module is used to modify the submit button response event of the business form in the heterogeneous business system and call the standard API opened by the workflow system to initiate the approval process.

9. An electronic device, characterized in that: The electronic device includes: at least one processor; and a memory communicatively connected to the at least one processor; the memory stores computer program instructions that can be executed by the at least one processor, and the computer program instructions are executed by the at least one processor to enable the at least one processor to execute the method for integrating heterogeneous business systems with workflow systems as described in any one of claims 1 to 7.

10. A non-transitory computer-readable storage medium, characterized in that The non-transitory computer-readable storage medium stores computer instructions, and the computer instructions enable the computer to execute the method for integrating heterogeneous business systems with a workflow system according to any one of claims 1 to 7.

Images