Process development platform, process development method, equipment and storage medium

Abstract

The invention discloses a process development platform, a process development method, equipment and a storage medium, and relates to the technical field of data processing, and the platform comprises a visual configuration module which is used for obtaining a process construction demand of a target user; the process modeling layer is used for constructing a target process structure through a process structure construction model based on the process construction requirement, receiving a process adjustment operation of the target user, and modeling the target process structure to obtain a target process modeling model; the third-party docking module is used for acquiring process access data corresponding to the target process modeling model by connecting a third-party standard interface; and the process development module is used for performing process development based on the target process modeling model and the process access data to generate a target process. According to the method, real-time data synchronization and standardized docking of the visual process platform and the third-party heterogeneous system can be realized, and interoperability and expansibility of the platform system are remarkably improved.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of data processing, and particularly relates to a process development platform and process development method, device and storage medium. BACKGROUND

[0002] Traditional visual process platforms generally have two core pain points: one is that when interfacing with third-party heterogeneous systems, there is a lack of standardized interaction mechanism, and adaptation code needs to be repeatedly developed for different systems, which is low in interfacing efficiency and high in maintenance cost; the other is that process events and data synchronization logic are closely coupled, and when the third-party system interface or deployment environment changes, the core code of the process platform needs to be modified, which is poor in expansibility. SUMMARY

[0003] The main purpose of the present application is to provide a process development platform and process development method, device and storage medium, aiming to realize real-time data synchronization and standardized interfacing of the visual process platform and the third-party heterogeneous system, and significantly improve the interoperability and expansibility of the platform system.

[0004] To achieve the above purpose, the present application provides a process development platform, which comprises a visual configuration module, a process modeling module, a third-party interfacing module and a process development module, The visual configuration module is used for obtaining process construction requirements of a target user. The process modeling module is used for constructing a target process structure based on the process construction requirements through a process structure construction model, receiving process adjustment operations of the target user, modeling the target process structure, and obtaining a target process modeling model. The third-party interfacing module is used for obtaining process access data corresponding to the target process modeling model through a connected third-party standard interface. The process development module is used for process development based on the target process modeling model and the process access data, and generating a target process.

[0005] In an embodiment, the process development platform further comprises a basic support module, which is used for managing and providing a standardized node library and a multi-environment configuration center.

[0006] In an embodiment, the process modeling module is further used for receiving process adjustment operations of the target user through a drag-and-drop process design tool and a visual process design tool.

[0007] In one embodiment, the process development platform further includes an event interaction rule module, which is used to configure core events in the entire lifecycle of the target process to define the triggering conditions, data interaction logic and exception handling mechanism of each core event, so as to realize standardized event-driven interaction.

[0008] In one embodiment, the process development platform further includes a business data modeling module, which is used to construct a visual form model, configure data validation rules, and perform version management on the visual form model.

[0009] To achieve the above objectives, this application proposes a process development method, including: Develop the process to acquire target users; Based on the process construction requirements, a target process structure is constructed through a process structure construction model, and the process adjustment operation of the target user is received to adjust the target process structure and obtain the target process modeling model. Obtain the process access data corresponding to the target process modeling model by connecting to a third-party standard interface; Based on the target process modeling model and the process access data, process development is performed to generate the target process.

[0010] In one embodiment, obtaining the process access data corresponding to the target process modeling model by connecting to a third-party standard interface includes: Based on the context information and business data in the target process modeling model, a process data access request is generated. Connect to the third-party standard interface and send the process data access request to the third-party system to receive the process access data returned by the third-party system.

[0011] In one embodiment, the method further includes: Detect whether the target user triggers the core events throughout the entire lifecycle of the target process; If so, then based on the event type of the core event, obtain the interaction logic and exception handling mechanism corresponding to the core event; The core events are managed based on the interaction logic and the exception handling mechanism.

[0012] In addition, to achieve the above objectives, this application also proposes a process development apparatus, the apparatus comprising: a memory, a processor, and a computer program stored in the memory and executable on the processor, the computer program being configured to implement the steps of the process development method as described above.

[0013] In addition, to achieve the above-mentioned purpose, the application further provides a storage medium, which is a computer readable storage medium, and a computer program is stored on the storage medium, and the computer program is executed by a processor to implement the steps of the flow development method.

[0014] In addition, to achieve the above-mentioned purpose, the application further provides a computer program product, which comprises a computer program, and the computer program is executed by a processor to implement the steps of the flow development method.

[0015] The application provides a flow development platform and a flow development method, device and storage medium, the flow development platform comprises: the visual configuration module, which is used to acquire the flow construction requirement of a target user; the flow modeling layer, which is used to construct a target flow structure based on the flow construction requirement through a flow structure construction model, receive a flow adjustment operation of the target user, model the target flow structure, and obtain a target flow modeling model; the third-party interface module, which is used to acquire flow access data corresponding to the target flow modeling model through a connection third-party standard interface; and the flow development module, which is used to develop a target flow based on the target flow modeling model and the flow access data, and generate a target flow. Thus, the requirement is acquired through the visual configuration module, the visual adjustment of the flow modeling layer is combined, the flow construction is completed without complex coding, the non-professional developers are adapted, the user can perform the flow adjustment operation in real time, the target flow structure can be dynamically optimized, the modeling deviation is reduced, the flow modeling accuracy is effectively improved, the access data is acquired based on the standard interface through the third-party interface module, the standardized integration is realized, the repeated development of the heterogeneous system connection is avoided, the integration complexity is reduced, the development continuity is ensured, the development process is carried out around the user requirement and the third-party data specification, the adaptation conflict is reduced, the modules have clear division of labor and smooth data flow, the closed loop is formed from the requirement acquisition, modeling to integrated development, and the flow generation cycle is shortened. BRIEF DESCRIPTION OF DRAWINGS

[0016] The accompanying drawings, which are incorporated into and form a part of the specification, illustrate an embodiment consistent with the present application and, together with the description, serve to explain the principles of the application.

[0017] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the accompanying drawings needed to be used in the embodiments or prior art description will be briefly introduced. Obviously, for those skilled in the art, other drawings can also be obtained without creative labor based on these drawings.

[0018] Figure 1 The system architecture diagram provided by the flow development platform of the present application; Figure 2 A scenario implementation diagram provided for the visual configuration of the process development method of the present application; Figure 3 A process schematic diagram provided for the first embodiment of the process development method of the present application; Figure 4 A device structure schematic diagram of the hardware running environment involved in the process development method in the embodiments of the present application.

[0019] The object implementation, functional features and advantages of the present application will be further described with reference to the accompanying drawings in conjunction with the embodiments. DETAILED DESCRIPTION

[0020] It should be understood that the specific embodiments described herein are only used to explain the technical solutions of the present application, and are not used to limit the present application.

[0021] In order to better understand the technical solutions of the present application, the following will be described in detail in conjunction with the drawings and specific embodiments of the specification.

[0022] It should be noted that the execution subject of the present embodiment can be a computing service device with data processing, network communication and program running functions, such as a tablet computer, a personal computer, a mobile phone, etc., or an electronic device, a big data service platform, a process development system, etc. capable of realizing the above functions. The present embodiment and the following embodiments will be described below taking the process development platform as an example.

[0023] Based on this, the present embodiment provides a process development platform, which is described in detail as follows with reference to Figure 1 , Figure 1 A system architecture diagram provided for the process development platform of the present application.

[0024] In the present embodiment, the process development platform comprises a visual configuration module, a process modeling module, a third-party interfacing module and a process development module, wherein: The visual configuration module is configured to obtain the process construction requirements of a target user. It should be noted that the visual configuration module refers to a functional module in the process development platform that provides a graphical operation interface for the target user to collect and organize the process development related requirements; the target user refers to the personnel who use the process development platform to design and develop processes, which can be business personnel, operation and maintenance personnel or low-code developers in an enterprise.

[0025] Further need to be explained, the process of building demand refers to the process related requirements proposed by the target user to achieve a specific business scenario (such as financial approval, order processing), including process node composition, node transfer rule, data interaction demand, the scope of connecting third party system and other contents. The core purpose of this module is to accurately capture the real needs of the target user through visual, low threshold interaction mode, avoid the disconnection between subsequent process development and actual business due to demand transmission deviation, and at the same time provide clear design basis for process modeling layer. In an embodiment, the visual configuration module can provide a demand template library, including standardized demand templates of common business scenarios (such as leave approval, purchase application), which can be modified by the target user based on the template to reduce the workload of demand input.

[0026] Specifically, the visual configuration module first shows the target user a structured demand collection interface, which is divided into four core areas of "basic information", "process node demand", "data demand" and "third party connection demand", such as: The target user fills in the process name, business attribution department, process priority and other contents in the "basic information" area; In the "process node demand" area, the nodes (such as "initiation node", "approval node" and "archiving node") that the process needs to include and the responsible person and execution time limit of each node are determined by checking and filling; In the "data demand" area, the business data (such as "order amount" and "approval opinion") needed for process operation and data source are marked; In the "third party connection demand" area, whether it is necessary to connect external system (such as ERP system and CRM system) and the specific data range of connection are selected; Further, the module performs real-time legality verification on the user input demand (such as the process name cannot be empty, the node responsible person needs to be in the enterprise organization structure), and stores the demand as "demand document" after verification, and synchronously pushes it to the process modeling layer.

[0027] For example, the financial personnel (target user) of a certain enterprise collects the "expense reimbursement process" construction demand through the visual configuration module: fill in the process name "employee expense reimbursement process" and attribution department "finance department" in the basic information area; In the process node demand area, check "initiation node (employee fills out)" "department manager approval node" "finance audit node" and "payment node", and set the department manager approval time limit to "3 working days"; In the data demand area, mark the data needed, such as "reimbursement amount", "reimbursement reason" and "invoice attachment"; In the third party connection demand area, select to connect "enterprise ERP system", and synchronize "reimbursement single information" to the ERP system to generate a payment order; After the module verifies that the demand is correct, a structured demand document is generated and pushed to the process modeling layer as the basis for process design.

[0028] Additionally, to further reduce the operation amount of the target user, a natural language instruction input by the target user can be received as the process construction requirement, so that the construction requirement in the natural language instruction is identified by the process structure construction model, wherein the natural language instruction refers to a process requirement description input by the target user in daily colloquial or written language (such as “design an employee leave process, which needs to be approved by a department manager, and if the leave days are more than 3 days, it also needs to be approved by a general manager”, without the need to follow a specific format.

[0029] The process modeling layer is configured to construct a target process structure based on the process construction requirement by using a process structure construction model, receive a process adjustment operation of the target user, model the target process structure, and obtain a target process modeling model. It should be noted that the process modeling layer refers to a core function layer of the process development platform for designing, adjusting and optimizing the process structure based on the process construction requirement of the target user; the process structure construction model refers to a process design model built-in the platform, which meets the international standard of BPMN2.0, contains a process node library, a flow rule engine, a simulation test component, and the like, and supports automatic generation of a preliminary process framework according to requirements; and the target process structure refers to an initial process framework generated by the process structure construction model based on the process construction requirement, which contains node layout and basic flow logic, but has not been adjusted and optimized by the user.

[0030] It should be further noted that the process adjustment operation refers to a modification operation of the initial process structure by the target user through a visual tool provided by the platform, such as adding / deleting a node, adjusting a node order, and modifying a flow condition; and the target process modeling model refers to a complete process design scheme finally formed after the adjustment and optimization of the target user, which can be used for subsequent development, and contains detailed node configuration, flow rule and data interaction definition.

[0031] Further, the purpose of this step is to convert the abstract process construction requirement into a concrete and executable process design scheme, to ensure that the process design is highly matched with the business requirement by allowing the target user to make real-time adjustments, and to guarantee the standardization and scalability of the process by using a standardized model. In a possible implementation, the process modeling layer can provide a “process simulation test” function, so that the target user can simulate the running of the process after adjusting the process, view the process flow effect, and assist in finding design defects.

[0032] Specifically, the process modeling layer first receives the process construction requirements pushed by the visualization configuration module, calls the process structure construction model to analyze the requirement content; the model automatically matches the corresponding nodes (such as "approval node" matches "user task node") from the standardized node library (provided by the basic support module) according to the node requirements in the requirements, generates an initial target process structure according to the business logic, and displays it to the target user in the form of a canvas; the target user adjusts the node position through the drag-and-drop process design tool, adds / deletes nodes (such as adding a "financial pre-audit node" after the "department manager approval node"), and modifies the jump conditions between nodes through the visual transfer rule configuration tool (such as "when the reimbursement amount is less than or equal to 1000 yuan, the department manager approval node directly enters the payment node; when the amount is greater than 1000 yuan, it needs to go through the financial audit node"). The process modeling layer records the user's adjustment operations in real time, synchronously updates the process structure, and provides "undo / redo" and "version saving" functions; when the target user confirms that the process design is correct, the module performs integrity checking on the process structure (such as ensuring that the process has a unique start node and end node, and all nodes have a transfer path), and generates a target process modeling model containing process XML configuration files, node details table, and transfer rule table, etc. after passing the verification.

[0033] For example, after the process modeling layer receives the "employee expense reimbursement process" construction requirements, it generates an initial process structure (initiation node → department manager approval node → financial audit node → payment node) through the process structure construction model; the financial personnel (target user) find that "when the reimbursement amount is less than or equal to 500 yuan, no financial audit is required", add a "branch gateway node" after the "department manager approval node" through the drag-and-drop tool, and set "when the reimbursement amount is less than or equal to 500 yuan, jump to the payment node", and "when the amount is greater than 500 yuan, jump to the financial audit node" through the transfer rule configuration tool; after the adjustment is completed, the process modeling layer performs integrity checking to confirm that the process has no design defects, and generates a "employee expense reimbursement process" modeling scheme containing node configuration and transfer rules.

[0034] The third-party interface module is configured to obtain process access data corresponding to the target process modeling model by connecting a third-party standard interface. It should be noted that the third-party interface module refers to a functional module in the process development platform that is specifically responsible for establishing a connection with external third-party systems to obtain external data required for process operation; the third-party standard interface refers to an interface provided by a third-party system (such as an ERP system, a CRM system) that conforms to the industry or platform unified specification, and the request format, return format, and calling protocol (such as HTTP / HTTPS) of the interface have been standardized, without the need for additional development of adaptation code by the platform.

[0035] Further need to be explained is that the process access data corresponding to the target process modeling model refers to the business data that the target process needs to obtain from the third-party system in the running process, and these data are the key basis for process flow (such as obtaining "order inventory data" from the ERP system to judge whether the order processing process continues), and the data range and format have been specified in the target process modeling model. The core purpose of this module to perform this operation is to break through the data barriers of the process development platform and the third-party heterogeneous system through standardized interface docking, to ensure that the external data required by the process running can be obtained in real time and accurately, to avoid process interruption due to data loss, and at the same time to reduce the repeated development work when docking different systems, to reduce the integration cost. In a possible implementation manner, the third-party docking module can provide an interface test function, before formally obtaining data, simulate sending a request to the third-party standard interface, verify the interface connectivity and data return format, and ensure normal docking.

[0036] Specifically, the third-party docking module first parses the third-party docking requirements defined in the target process modeling model, and clearly defines the third-party system name to be docked, the type of process access data required (such as "order basic information" and "customer credit level") and the corresponding third-party standard interface address; the module obtains the interface access parameters (such as interface key, access token, timeout time) of the third-party system under the current running environment (development / test / production) through the multi-environment configuration center of the basic support module; then according to the request format of the third-party standard interface, encapsulate "process identification", "data requirement range" and other information into a standardized request message; connect the third-party standard interface through HTTP / HTTPS protocol, send the request message; after receiving the response data returned by the third-party system, the module performs format conversion (such as converting JSON format data into structured data recognizable by the platform) and integrity check (such as checking whether the key fields such as "order amount" and "order number" exist) on the data; after the check is passed, the data is marked as "process access data" and stored in the data cache area of the platform, and the process development module is notified that the data is ready.

[0037] For example, in the "employee expense reimbursement process" modeling scheme, it is explicitly required to obtain "employee salary account information" from the enterprise ERP system (third-party system) as the basis for the payment node, and the corresponding third-party standard interface address is "http: / / erp.company.com / api / getSalaryAccount". The third-party interface module obtains the access token and timeout time (3000 ms) of the interface in the production environment from the multi-environment configuration center. According to the interface requirements, the request message (including "employee ID" and "process identifier") is encapsulated, and sent to the third-party standard interface through the HTTPS protocol. The response data returned by the ERP system (including employee name, salary account number, and bank of account opening) is converted into platform structured data, and the "salary account number" field is checked to exist and be correct. Finally, the data is stored as process access data for subsequent process development.

[0038] The process development module is configured to develop the target process based on the target process modeling model and the process access data, and generate the target process.

[0039] It should be noted that the process development module refers to a functional module that integrates the target process modeling model and the process access data in the process development platform, completes process code generation, configuration and deployment, and finally forms a runnable process. The process access data refers to the business data obtained from external systems by the third-party interface module to support the operation of the target process. The target process modeling model refers to the complete process design scheme output by the process modeling layer, including node configuration and flow rule. The target process refers to a process instance that can run in an actual business scenario after development and deployment, and has complete functions such as node execution, data flow, and exception handling.

[0040] It should be further noted that the core purpose of this module to perform this operation is to convert the process modeling in the design stage into a runnable running process, and to ensure that the process can meet the actual business needs by integrating internal and external data, while realizing the automation and standardization of process development, reducing the workload and errors of manual coding. In one possible implementation, the process development module can support process version management, automatically create a new version each time a target process is generated, record version change content, and facilitate subsequent rollback or iterative optimization.

[0041] Specifically, the process development module first receives the process access data pushed by the third-party interface module, associates and matches it with the data requirements in the target process modeling model (such as binding "employee salary account information" with the data requirements of the payment node); then calls the built-in code generation engine of the platform, and automatically generates process code (such as Java code, process configuration XML file) that meets the platform operation specifications according to the node configuration and flow rule of the target process modeling model. The code contains data calling logic (such as automatically reading employee salary account information in the payment node) and node execution logic (such as automatically reminding when the approval node is not processed within the timeout period); the module performs syntax checking and logic checking on the generated code (such as checking whether the data calling interface exists and whether the flow transfer condition is complete); after the checking is passed, the process deployment configuration is completed in combination with the multi-environment configuration (such as database connection information and log storage path) provided by the basic support module; finally, the process test is started to simulate the complete running process of the process from initiation to end, verify the normal flow transfer of the process node and accurate data calling; after the test is passed, the process is marked as "available state", that is, the target process is generated, and the target user can initiate the process in actual business.

[0042] For example, after the process development module receives "employee salary account information" (process access data), it is associated with the "employee expense reimbursement process" modeling scheme, and the account information is bound to the "payment node"; the code generation engine automatically generates process code according to the node order and flow rule in the process modeling, and the code contains the logic of "automatically pushing to the department manager for approval after the employee initiates the reimbursement" and "directly calling the salary account information to execute the payment if the amount is ≤500 yuan after the department manager's approval"; after the module checks that the code has no syntax error and the data calling interface is normal, the deployment is completed in combination with the database configuration of the production environment; during the simulation test, the employee initiates the reimbursement (amount 400 yuan), the process automatically flows to the department manager for approval, and after the approval is passed, the salary account information is directly read to complete the "payment" node execution, and after the test is passed, the "employee expense reimbursement process" (target process) is generated for actual use by the enterprise employees.

[0043] The embodiment is used for acquiring process construction requirements of a target user through the visual configuration module; the process modeling layer is used for constructing a target process structure through a process structure construction model based on the process construction requirements, receiving a process adjustment operation of the target user, modeling the target process structure, and obtaining a target process modeling model; the third-party interfacing module is used for acquiring process access data corresponding to the target process modeling model through a connection third-party standard interface; and the process development module is used for process development based on the target process modeling model and the process access data, and generating a target process. Thus, requirements are acquired through the visual configuration module, visual adjustment of the process modeling layer is combined, process construction can be completed without complex coding, non-professional developers are adapted, process adjustment operations of the user are supported in real time, the target process structure can be dynamically optimized, modeling deviation is reduced, process modeling precision is effectively improved, access data is acquired based on a standard interface through the third-party interfacing module, standardized integration is realized, repeated development of heterogeneous system interfacing is avoided, integration complexity is reduced, development coherence is guaranteed, the development process is ensured to be carried out around user requirements and third-party data specifications, and adaptation conflicts are reduced. In the embodiment, each module has clear division of labor and smooth data flow, a closed loop is formed from requirement acquisition, modeling to integrated development, and a process generation period is shortened.

[0044] In a feasible implementation, the process development platform further includes a basic support module, which is used for managing and providing a standardized node library and a multi-environment configuration center.

[0045] It should be noted that the basic support module refers to a core technical base of the process development platform, which provides unified resource management and environment configuration capabilities for upper modules such as process modeling, third-party interfacing, and process development, and is a key module for guaranteeing stable operation and flexible expansion of the platform. The standardized node library refers to a set of process nodes stored in the basic support module and conforming to the BPMN2.0 international standard, which covers 12 types of basic nodes such as start nodes, end nodes, user task nodes, service task nodes, exclusive gateways, and parallel gateways. The attributes of each node (such as execution rules, timeout strategies, and responsible person configuration items) have been uniformly encapsulated, and developers can adjust parameters through a configuration interface without coding for reuse. The multi-environment configuration center refers to a functional component in the basic support module for storing and managing configuration information of multiple running environments such as development environments, test environments, and production environments. The configuration information includes database connection parameters, third-party interface access keys, process engine running parameters, interface call timeout times, and the like. The configuration center supports one-key synchronization and differential management between environments to ensure consistent running parameters of processes in different environments and avoid integration failures caused by environment configuration differences.

[0046] Further need to explain is that the stable operation of the platform refers to that the process development platform can avoid crashes or function abnormalities caused by resource missing or configuration conflicts when processing process modeling, data docking, process generation and other operations; the flexible expansion of the platform refers to that the platform can adapt to changes in business requirements (such as adding process node types or switching running environments), and can realize function upgrade or environment migration without modifying the core code. The core purpose of this module is to solve the problems of low development efficiency and many running faults caused by poor node reusability and chaotic environment configuration in traditional process platforms through unified resource management and environment configuration, and to provide stable and scalable technical support for the upper modules.

[0047] In a possible implementation, the standardized node library of the basic support module supports custom node expansion. Target users can develop exclusive nodes that meet specific business scenarios (such as financial approval and cross-system data synchronization) based on the expansion interface provided by the platform, and integrate them into the standardized node library for unified management, further improving the adaptability of the platform.

[0048] Specifically, the management of the standardized node library by the basic support module includes two types of operations: “basic node maintenance” and “custom node expansion”: For basic nodes, the module regularly updates node attribute configuration templates (such as optimizing the timeout reminder strategy of user task nodes), and supports target users to adjust node parameters (such as setting the number of retries for service task nodes) through a visual interface, without the need for coding to complete node reuse; For custom nodes, the module provides node development SDK and interface documents. After target users develop node logic according to the document specifications, they can submit it to the standardized node library through the “node registration” function. The module automatically checks the node compatibility (such as whether it meets the BPMN2.0 standard and whether there are interface conflicts), and after the check is passed, it can be used in all process modeling scenarios.

[0049] In the management of multi-environment configuration center, the module adopts a storage structure of “environment grouping + configuration item classification”, classifies the configurations of development, testing and production environments respectively, and divides the configuration items under each environment into “database configuration”, “interface configuration” and “engine configuration”; supports target users to copy the configurations of one environment to other environments through the “one-key synchronization” function, and provides a “differential comparison” tool to highlight the configuration differences between different environments (such as different database IPs), avoiding process running faults caused by inconsistent configurations; when the interface address of a third-party system or the database connection information changes, target users only need to modify the corresponding configuration items in the multi-environment configuration center, without the need to adjust the code of the upper modules, realizing the decoupling of configuration and business logic.

[0050] The embodiment sets the basic support module, solves the problems of low process node reusability and complex configuration by the standardized node library, reduces the complexity of process modeling, eliminates the running risk caused by environment configuration disorder by the multi-environment configuration center, and realizes flexible adjustment of configuration. The two cooperate to build a stable and extensible technical base for the process development platform, ensure that the upper modules (process modeling layer, third-party interface module, etc.) can run efficiently and reliably, and finally improve the overall efficiency and quality of process development.

[0051] In a possible implementation, the process modeling module is further configured to receive the process adjustment operation of the target user through a drag-and-drop process design tool and a visual process design tool.

[0052] It should be noted that the drag-and-drop process design tool refers to a graphical tool provided by the process modeling module, which allows the target user to complete the layout and connection of the process nodes through mouse dragging operation. The tool has an entry to the standardized node library, and the target user can directly drag the node to the design canvas. The visual process design tool refers to a graphical operation tool provided by the process modeling module for configuring process details (such as node attributes, flow transfer rules, and data interaction logic), including node configuration pop-up window, flow transfer rule editor, and data mapping interface. The process adjustment operation refers to the modification operation of the target user to make the process design meet the business requirements, including adding / deleting nodes, adjusting node positions, modifying node attributes, configuring flow transfer conditions, and defining data interaction rules.

[0053] It can be understood that the core purpose of the module receiving the process adjustment operation through the two tools is to reduce the technical threshold of process design, so that non-professional developers can also complete process adjustment through graphical operation, while ensuring that the adjustment process is intuitive and efficient, reducing design deviation caused by complex operation, and finally improving the accuracy and efficiency of process modeling. In a possible implementation, the drag-and-drop process design tool supports batch node operations (such as batch selection, copying, and deleting nodes), and the visual process design tool supports real-time preview of flow transfer rules (such as displaying the process path after the rule takes effect immediately after configuration is completed), further improving the operation convenience.

[0054] Specifically, the process modeling module synchronously loads the drag-and-drop process design tool and the visual process design tool after the target user enters the process design interface: For the drag-and-drop process design tool, the tool left side displays a standardized node library (provided by the underlying support module), including start node, end node, user task node, etc. The target user adds the required node to the middle design canvas by mouse dragging, and the flow transfer relationship between the nodes is established by dragging the connection line between the nodes. The tool automatically absorbs the node position and aligns the connection line to ensure the neat layout of the process. At the same time, the "canvas zoom" and "node locking" functions are provided to avoid process structure confusion caused by misoperation.

[0055] For the visual process design tool, when the target user selects a node in the canvas, the tool automatically pops up a node configuration pop-up window, which displays configurable items (such as "basic attributes" of the user task node, including node name and responsible person, "execution rules" including timeout time and retry number) in "basic attributes", "execution rules" and "data interaction". The target user completes the configuration through input box, drop-down selection, and check box. When the target user selects the connection line between the nodes, the tool pops up a flow transfer rule editor, which supports configuring the transfer condition through "conditional expression" (such as "jump when the form field 'amount' > 1000") or "enumeration selection" (such as "enter the next node if the processing result is 'pass'"). Syntax errors (such as expression format error) are prompted in real time during configuration to ensure that the rules are legal. Please refer to Figure 2 .

[0056] Further, the two tools are synchronized in real time with the target user's operation. After adjusting the node by dragging, the configuration items of the visual tool are automatically associated and updated. After modifying the configuration, the canvas of the drag-and-drop tool synchronously displays the configuration results (such as labeling the node responsible person).

[0057] In this embodiment, through the cooperation of the drag-and-drop process design tool and the visual process design tool, the process adjustment operation is divided into two intuitive steps of "node layout" and "detail configuration". The target user can complete the adjustment of the complex process without writing code, which greatly reduces the technical threshold. At the same time, the real-time synchronization and error prompt function of the tool reduces the operation mistakes and design deviations, ensures that the design scheme after process adjustment can accurately match the business requirements, and lays a good foundation for subsequent process development and operation.

[0058] In a feasible implementation manner, the process development platform further comprises an event interaction rule module, which is configured to configure the core events in the whole life cycle corresponding to the target process, to define the trigger condition, data interaction logic and exception handling mechanism of each core event, and to realize the standardized interaction driven by events.

[0059] It should be noted that the event interaction rule module refers to a functional module in the process development platform that is responsible for defining the event interaction logic of the target process throughout the life cycle, and is a core component for realizing the standardized docking of the process platform and third-party systems; the life cycle of the target process refers to the complete running process of the target process from initialization, initiation, node flow to final end, covering data preparation before process start, task processing during running, and state archiving after end; the core event refers to an event that plays a key role in data synchronization and process promotion in the life cycle of the target process, such as Table 1.

[0060] It should be further noted that the trigger condition refers to a specific operation or scenario that triggers the core event, such as triggering the initialization event when the process initiation page is opened, and triggering the data verification event when the user clicks the 'check' button on the filling page; the data interaction logic refers to the data transmission rules between the process platform and the third-party system after the core event is triggered, including the data request format (including context information and business data), the return data format (including processing results and returned data); the exception handling mechanism refers to the coping strategy when the data interaction fails (such as interface call timeout, data format error), such as retry mechanism, error prompt, data rollback, etc.; the event-driven standardized interaction refers to taking the core event as a medium, realizing low coupling and high efficiency of data synchronization and process collaboration between the process platform and the heterogeneous third-party system through unified trigger conditions, data formats and exception handling rules.

[0061] Further, the core purpose of the module is to solve the pain point of "no standardized mechanism, need to develop and adapt code repeatedly" when the traditional process platform is docked with the third-party system, to reduce the integration difficulty of heterogeneous systems by defining unified event interaction rules, to ensure real-time synchronization of process events and form data, and to improve system interoperability and extensibility. In one possible implementation, the event interaction rule module can provide an event interaction simulation test function, and after the target user completes the configuration, the core event can be simulated to trigger, view the data interaction process and exception handling effect, and discover rule configuration defects in advance.

[0062] Specifically, the event interaction rule module first shows the target user a core event configuration interface, which lists 6 types of core events according to "event type", which can be referred to Table 1.

[0063] Table 1

[0064] Further, the target user selects the event to be configured (such as an initialization event, a process initiation event); for the selected core event, the module provides a trigger condition configuration item, and the target user sets the trigger scenario by means of drop-down selection or custom input (such as selecting “when the process initiation page is filled in” as the trigger condition of the initialization event); then enters the data interaction logic configuration link, the module provides a standardized data format template, and the target user only needs to check the context fields (such as operator ID, process definition ID, environment identifier) and business data fields (such as order number, reimbursement amount) required for process interaction, and the module automatically generates a data request format; at the same time, the module configures the analysis rules of the returned data of the third-party system, and clearly defines the mapping relationship between the returned fields and the internal data of the process (such as mapping “order_no” returned by the third-party system to “order number” in the process); in the configuration of the exception handling mechanism, the module provides preset exception scenario options (such as parameter error, interface timeout, data format error), and the target user selects a processing strategy for each scenario (such as selecting “retry 3 times with an interval of 1000 milliseconds” for interface timeout, and selecting “display the prompt ‘parameter error, please check’” for parameter error); after all the rule configurations are completed, the module performs integrity checking on the configuration content (such as ensuring that each core event has a trigger condition and an exception handling strategy), and generates an “event interaction rule configuration document” after the checking is passed, which is synchronized to the third-party interface module and the process development module, to ensure that the event interaction is performed according to the rules during the subsequent process running.

[0065] The embodiment sets the event interaction rule module, decomposes the complex interaction logic of the whole life cycle of the process into six types of standardized core events, and solves the problem of “repeated development and high coupling” when the traditional process platform is connected with the third-party system by uniformly configuring the trigger condition, data format and exception handling mechanism. On the one hand, the third-party system only needs to implement the interface method of the corresponding event according to the rules, without needing to pay attention to the event pushing and routing details, thereby greatly reducing the connection threshold; on the other hand, the process platform is driven by the standardized events, ensures the consistency of the interaction logic with different heterogeneous systems, improves the system expandability, and the exception handling mechanism guarantees the stability of the process running, thereby providing key support for the efficient integration of the process and the third-party system.

[0066] In a feasible implementation manner, the process development platform further comprises a business data modeling module, which is configured to construct a visual form model and configure a data verification rule, and perform version management on the visual form model.

[0067] It should be noted that the business data modeling module refers to a function module in the process development platform specially responsible for designing process operation required business forms, defining data verification logic, and managing form versions, which is a key component to guarantee the accuracy and traceability of process data; the visual form model refers to a form template designed through a graphical interface for collecting and displaying process business data, including basic fields (such as strings, numbers, dates) and advanced fields (such as field linkage, data dictionary association, and attachment upload), which can be directly embedded into process nodes for target users to fill in or view.

[0068] It should be further noted that the data verification rule refers to a logical rule for verifying the legality of form data, including basic verification (such as prohibiting non-numeric content in numeric fields) and custom verification (such as regular expression verification, numeric range verification, and cross-field verification); the version management of the visual form model refers to the management mechanism of "version number + state", which records the creation, modification, and rollback process of the form model, ensures the traceability of historical process data, and avoids data anomalies of the initiated process due to model changes.

[0069] Further, the core purpose of the module is to solve the problems of "complicated form design, inflexible data verification, and no traceability of model changes" in traditional process platforms, to reduce the threshold of form construction through visual design, to ensure data accuracy through detailed verification rules, and to guarantee process data consistency through version management, thereby providing reliable business data support for process operation. In one possible implementation, the business data modeling module can provide a form template library, including standardized form templates for common business scenarios such as leave application, expense reimbursement, and procurement approval, which can be directly reused or modified by target users, further improving the efficiency of form construction.

[0070] Specifically, the business data modeling module provides a canvas-based form design interface: the left side of the interface displays a field library, including 10 types of basic fields (strings, numbers, dates, Boolean values, drop-down lists, etc.) and advanced fields (field linkage, data dictionary association, and attachment upload), target users add fields to the right side of the form canvas by dragging and dropping, and double-clicking the field to configure properties (such as setting the maximum length of a string field, the precision of a numeric field, and the content of a drop-down list); for advanced fields such as "field linkage", the module provides a visual configuration popup window, target users select the trigger field (such as "province") and the linkage field (such as "city"), and set the linkage logic (such as selecting "Zhejiang Province", the "city" field loads options such as Hangzhou and Ningbo), without writing code to achieve complex field interaction.

[0071] In the "configure data check rules" link, the module provides a check rule configuration entry for each field: basic check rules can be directly checked (such as "required" and "prohibit input space"); custom check rules support target users to input regular expressions, set numerical ranges, and configure cross-field checks (such as "end date > start date"), while allowing custom check failure prompt text (such as "please enter the correct mobile phone format"); after the completion of the check rule configuration, the module supports real-time preview testing, and the target user can view the check effect by inputting test data, ensuring that the rule takes effect.

[0072] In "visual form model version management", the module assigns a unique identifier to each form model, creates an initial version V1.0 (draft state), and the target user modifies the model (such as adding fields, modifying check rules), the module automatically upgrades the version number (such as V1.1), and records the version change log (including the modifier, modification time, and modification content, such as "2025-05-20 Zhang San added'reimbursement attachment' field"); support version rollback function, the target user can choose a historical version (such as rolling back from V1.2 to V1.1), and the old version model is not deleted, ensuring that the historical form data can still be normally called based on the old version, avoiding data anomalies.

[0073] This embodiment sets up a business data modeling module to build a complete business data guarantee system from three dimensions of "form design-data check-version management": visual form design reduces the operation threshold of non-professionals, fine check rules ensure the accuracy of process data, and version management ensures the traceability of model changes and the consistency of historical data. The three solve the core pain points of business data management in traditional process platforms, provide high-quality business data support for process operation, and improve the overall efficiency and reliability of process development.

[0074] Based on this, the embodiment of the application provides a process development platform, referring to Figure 3 , Figure 3 The process development method provided in Embodiment One of the application.

[0075] In this embodiment, the process development method includes steps S61-S64.

[0076] Step S61, acquire the process construction requirements of the target user; Specifically, the flow development platform performs this step through a visual configuration module, which first presents a structured requirement collection interface to the target user, which is divided into four core areas: "basic information", "flow node requirements", "data requirements", and "third-party interface requirements". The target user fills in the flow name (such as "employee expense reimbursement process"), the business department (such as "finance department"), and the flow priority (such as "high / medium / low") in the "basic information" area. In the "flow node requirements" area, the user specifies the nodes that the flow needs to include (such as "initiation node", "department manager approval node", "finance audit node") and the responsible person and execution time limit for each node by checking and filling in. In the "data requirements" area, the user labels the business data needed for the flow to run and the data source (such as "reimbursement amount" from employee fill-in, "employee job level" from HR system). In the "third-party interface requirements" area, the user selects whether to interface with external systems and the specific data range for the interface (such as "interface with ERP system to obtain employee payroll account information"). The module performs real-time legality verification on the user's input requirements (such as the flow name cannot be empty, the node responsible person must be within the enterprise organizational structure), and after verification, the requirements are structured and stored as "requirement documents", which are pushed to the flow modeling module to prepare for subsequent flow structure construction.

[0077] In step S62, based on the flow construction requirements, the target flow structure is constructed through a flow structure construction model, and the target user's flow adjustment operation is received to adjust the target flow structure, obtaining a target flow modeling model. It should be noted that in one possible implementation, a flow simulation test function can be provided, and after the target user adjusts the flow, the flow can be simulated to run and view the flow transfer effect (such as "whether the reimbursement amount of 300 yuan is directly skipped for financial audit"), which can assist in discovering design defects.

[0078] Specifically, the process modeling module first receives process construction requirements, calls the process structure construction model to parse the requirement content: the model matches the corresponding nodes (such as "approval node" matches "user task node") from the standardized node library provided by the basic support module according to the node requirements in the requirements, generates an initial target process structure in the order of business logic, and displays it to the target user in the form of a canvas; the target user adjusts the node layout (such as moving the "financial audit node" to the "department manager approval node") through the drag-and-drop process design tool, adds / deletes nodes (such as adding a "branch gateway node" to implement segmented approval of the amount), and sets the transfer conditions for the connection between nodes (such as "when the reimbursement amount is less than or equal to 500 yuan, jump from the department manager approval node to the payment node; when the amount is greater than 500 yuan, jump to the financial audit node") through the visual transfer rule configuration tool. The rule configuration takes effect in real time without the need to restart the platform; the process modeling module records the user's adjustment operations in real time, provides "undo / redo" and "version saving" functions to avoid loss of requirements due to operation errors; when the target user confirms that the process design is correct, the module performs integrity checking on the process structure (such as ensuring that the process has a unique start node and end node, and all nodes have a transfer path), and generates a target process modeling model containing a process XML configuration file, a node detail table, and a transfer rule table after the checking is passed. The model is pushed to the third-party interface module and the process development module.

[0079] Step S63, obtain the process access data corresponding to the target process modeling model through the connection of the third-party standard interface; It should be noted that the third-party standard interface refers to the interface provided by the third-party system (such as ERP system, HR system, CRM system) to the outside, which conforms to the industry or platform unified specification. This platform can provide a connection JAR package supporting JDK1.8 and above versions, which internally defines the interface definitions of 6 process events (corresponding to initialization, data validation, process initiation, task submission, data acquisition, and state update events). Each interface is strictly defined by JSON Schema: Input parameter format: fixedly contains "context information" (operator ID / name, operation time, process definition ID, environment identifier, etc.) and "business data" (form field key-value pair); Return value format: uniformly contains "processing result" (success / fail), "result description" (such as failure reason), and "return data" (such as form default values returned by the initialization event). In abnormal scenarios, standardized error codes (such as "E001" for parameter error and "E002" for system call timeout) are returned.

[0080] Thus, the third-party system only needs to introduce the JAR package and implement the interface method of the corresponding event to customize the data processing logic (such as storing process data into the own database, calling the internal CRM system to synchronize customer information, and encrypting sensitive fields), without the need to develop codes for event listening, data format conversion, routing distribution, and the like, thereby greatly reducing the connection threshold.

[0081] Specifically, the third-party connection module first parses the target process modeling model to determine the name of the third-party system to be connected, the type of process access data required (such as “employee salary account information” and “employee job level”), and the corresponding third-party standard interface address; obtains the interface access parameters (such as interface token, timeout time, and SSL certificate information) of the third-party system under the current running environment (development / test / production) through the multi-environment configuration center of the basic support module; encapsulates the “process identification”, “data requirement range”, “operator information”, and the like into a standardized request message according to the request format of the third-party standard interface; connects the third-party standard interface through the HTTP / HTTPS protocol, sends the request message, and starts timeout monitoring (the default timeout time is 3000 milliseconds); after receiving the response data returned by the third-party system, the module performs format conversion (such as converting JSON format data into structured data recognizable by the platform) and integrity check (such as checking whether the “salary account number” and “opening bank” and the like exist and whether the format is correct); after the check passes, the data is marked as “process access data”, stored in the data cache area of the platform, and a “data ready” notification is sent to the process development module; if the request times out or the data check fails, the module automatically triggers the retry mechanism (the default number of retries is 3, and the interval is 1000 milliseconds), and after the retry fails, error logs are recorded and the target user is prompted to troubleshoot the connection problem.

[0082] In step S64, process development is performed based on the target process modeling model and the process access data, and a target process is generated.

[0083] Specifically, the process development module first receives process access data, binds it to the data requirements in the target process modeling model (such as binding "employee salary account information" to "payment node" as the data source for the payment operation), calls the built-in code generation engine of the platform, and automatically generates process code (such as Java code, process engine configuration file) that meets the platform operation specifications according to the node configuration and flow rule in the target process modeling model. The code contains node execution logic (such as "after the employee initiates the reimbursement, automatically push the approval task to the department manager"), data calling logic (such as "when the payment node is executed, read the bound salary account information"), and exception handling logic (such as "when the approval is overdue for 3 working days, automatically send a reminder email"). The module performs syntax checking (such as checking whether the code has syntax errors) and logic checking (such as verifying whether the data calling interface exists and the flow transfer condition is complete) on the generated code. After passing the verification, combined with the running parameters of the multi-environment configuration center of the basic support module (such as database connection information, log storage path), the process deployment and configuration (such as deploying the process code to the process engine, configuring the database table structure for storing process data) are completed. Subsequently, the process test is started, simulating the target user initiating the process (such as the employee submitting the reimbursement form), processing the task (such as the manager approving it), verifying the normal flow transfer of the process node and the accurate data calling (such as the payment node successfully reading the salary account information). After passing the test, the process is marked as "available state", that is, the target process is generated, and the target user can initiate and use the process in the actual business of the enterprise.

[0084] The embodiment obtains the process construction requirements of the target user, constructs the target process structure based on the process construction requirements through the process structure construction model, receives the process adjustment operation of the target user, adjusts the target process structure, obtains the target process modeling model, and then obtains the process access data corresponding to the target process modeling model through the connection of the third-party standard interface, and generates the target process based on the target process modeling model and the process access data, thereby supporting the acquisition of process construction requirements through a visual interface or natural language instructions, reducing the operation amount of manually filling out structured forms by the target user, adapting to non-professional developers, improving the demand collection efficiency, and at the same time, obtaining the process access data through the third-party standard interface, without repeatedly developing and adapting codes for different systems, reducing the integration complexity of heterogeneous systems, ensuring real-time and accurate data synchronization, avoiding process interruption caused by data loss, and finally forming a closed loop from demand acquisition, modeling adjustment to data docking and process generation. Each link is connected through standardized tools and interfaces, reducing manual intervention and repetitive work, significantly improving the overall efficiency of process development, and quickly responding to business requirements.

[0085] In an implementable embodiment, the obtaining of the process access data corresponding to the target process modeling model through connection of the third-party standard interface comprises: In step S71, a process data access request is generated based on the context information and the business data in the target process modeling model. It should be noted that the context information refers to basic information related to the process running scenario, and specifically includes operator ID, operator name, operation time, process definition ID, environment identifier (such as dev development environment, prod production environment), which are used by the third-party system to identify the request source and running scenario; the business data refers to the core business parameters required for the target process running, such as "employee ID" and "reimbursement order number" in the employee expense reimbursement process, and "order number" and "supplier ID" in the procurement process, which are directly associated with the specific business information to be returned by the third-party system.

[0086] Further, the process data access request refers to a standardized request message for obtaining process access data from the third-party system, ensuring that the third-party system can be identified and parsed. The core purpose of this step is to generate accurate and compliant request messages by integrating key information in the target process modeling model, to avoid the third-party system from being unable to return data due to missing request parameters or format errors, while ensuring that the request content is highly matched with the process requirements, and only the necessary data for process running is obtained, reducing invalid data transmission.

[0087] Specifically, the third-party interfacing module first extracts the context information and business data from the target process modeling model: In terms of context information, the ID and name of the current operator are automatically obtained (synchronized from the platform user authentication system), the current operation time is generated in the format of "YYYY-MM-DD HH:MM:SS", the unique process definition ID of the target process is read from the configuration file of the target process modeling model, and the current running environment identifier is obtained from the multi-environment configuration center of the basic support module. In terms of business data, according to the third-party interfacing requirements defined in the target process modeling model, the core parameters related to process access data are filtered out, such as the need to obtain "employee salary account information" in the employee expense reimbursement process, and the "employee ID" is extracted as business data.

[0088] Subsequently, according to the preset JSON format template, the context information and the business data are packaged into the process data access request, wherein the context information is uniformly placed under the "context" field, and the business data is uniformly placed under the "businessData" field, so as to ensure the clear field level; after the packaging is completed, the third-party interface module performs format checking on the request message, checks whether there is a missing field (such as whether the "process definition ID" is missed), a data format error (such as whether the operation time format is correct), and if the checking fails, the missing field is automatically completed or the target user is prompted to correct the error; after the checking is passed, the final process data access request is generated, and is waiting for subsequent sending to the third-party system.

[0089] In step S72, the third-party standard interface is connected, the process data access request is sent to the third-party system, and the process access data returned by the third-party system is received.

[0090] It should be noted that the third-party system refers to an external business system that has data interaction needs with the process development platform, such as an ERP system that stores employee salary information, an HR system that manages employee job levels, so as to be connected and requested through a standardized interface, to realize low-coupling data interaction between the process development platform and the third-party heterogeneous system, to solve the pain point of "repeated development of adaptation code and high maintenance cost for different systems" in the traditional process platform, and to ensure real-time and accurate acquisition of process access data.

[0091] Specifically, the third-party interface module first obtains the address of the third-party standard interface from the target process modeling model, and obtains the access parameters required for connecting the third-party system in the current running environment from the multi-environment configuration center of the basic support module, including the interface calling token (for identity authentication), the request timeout time (default 3000 milliseconds), the SSL certificate required for the HTTPS protocol (if the third-party system interface uses the HTTPS protocol).

[0092] Then, a connection is established with the third-party standard interface: if the interface uses the HTTP protocol, a connection is established directly via TCP; if the HTTPS protocol is used, an SSL certificate is loaded first to complete authentication, and then an encrypted connection is established; after the connection is successfully established, the third-party integration module sends the process data access request to the third-party system in the format required by the third-party standard interface (such as JSON), and starts a timeout timer; if the response data returned by the third-party system is received within the timeout period, the module first parses the response data (converting the JSON format data into structured data that can be recognized internally by the platform), and then performs integrity verification according to the data requirements defined in the target process modeling model, checking whether it contains the necessary key fields (such as checking whether "salary account number" and "bank name" are included when obtaining employee salary account information); if the verification passes, the response data is marked as "process access data", stored in the platform's data cache, and a "data ready" notification is sent to the process development module; if no response is received within the timeout or the response data verification fails, the module starts a retry mechanism, records an error log (including request content and error reason) after a retry failure, and prompts the target user to check the third-party system interface or network problems.

[0093] In the process of establishing a connection between the process development platform and third-party systems, standard third-party interfaces, including registration interfaces, are used to adapt to the environment configurations between the two. Specifically, the event service (a core component of the process development platform's "third-party interface layer," responsible for standardized event scheduling and interaction between the "process development platform and third-party systems," implementing functions around the "six standardized events") provides an environment registration interface (path: / event / api / env / register) using the HTTP / HTTPS protocol. After the third-party system is deployed, complete deployment information for each environment must be submitted. The information fields and requirements are shown in Table 2. Table 2

[0094] The embodiment generates a process data access request based on the context information and the business data in the target process modeling model, connects the third-party standard interface, sends the process data access request to the third-party system through the third-party standard interface, receives the process access data returned by the third-party system, ensures that the request content is highly matched with the process demand, avoids that the third-party system cannot be recognized due to data missing or redundancy, improves the request effectiveness, sends the request through the third-party standard interface, does not need to develop differentiated adaptation codes for different third-party systems, reduces the repeated development workload, reduces the integration complexity of heterogeneous systems, and improves the connection efficiency and maintainability. Further, by directly connecting the third-party standard interface and sending the request, the process access data returned by the third-party system can be received in real time, the external data required in the process running is updated in time, the process is interrupted or the decision deviation is avoided due to data lag, and the process continuity is ensured. The request content strictly follows the range defined in the target process modeling model, only the business data required in the process running (such as the employee salary account information obtained from the ERP system) is obtained, the third-party system data is avoided to be excessively collected, the data security and privacy protection requirements are met, and the interference of invalid data on the process running is reduced.

[0095] In a feasible implementation, the method further includes: Step S81, detecting whether a target user triggers a core event in a full life cycle of the target process; It should be noted that the full life cycle refers to a complete running process of the target process from initialization, initiation, node flow to final end, covering stages such as form filling preparation before process start, task processing in running, and state archiving after end; the core event refers to 6 types of standardized events that play a key role in target process data synchronization and process promotion, specifically including initialization event, data verification event, process initiation event, submission task event, data acquisition event, and state update event, so as to ensure that the key operations in the target process running process are accurately captured, and the process interruption or the data synchronization with the third-party system is avoided due to the core event omission.

[0096] Specifically, the event interaction rule module as an execution subject first reads 6 types of core events corresponding to the whole life cycle of the target process and the triggering scenarios of each type of event (such as the initialization event corresponding to "the target user opens the process initiation page to fill in the interface", and the process initiation event corresponding to "the target user clicks the 'initiate' button on the page to fill in") from the target process modeling model; then deploys an event listening component in the running interface of the target process, which is associated with the operation buttons, interface loading actions, and the like of the target process, and collects the operation behavior data (such as the operation type, operation time, and operation interface) of the target user in real time; the component matches the collected operation behavior data with the preset core event triggering scenarios, for example, when the target user opens the interface to fill in the "employee expense reimbursement process", the operation behavior data matches the "initialization event triggering scenario", and it is determined that the initialization event is triggered.

[0097] If the operation performed by the target user (such as modifying the content of the text box on the page to fill in) does not match any core event triggering scenario, it is determined that the core event is not triggered; the event interaction rule module records the detection results in real time, and if it is determined that the core event is triggered, immediately marks the event type (such as "initialization event") and pushes it to the subsequent step; if not, it continues to listen to the operation behavior of the target user to ensure that no core event is missed in the whole life cycle.

[0098] For example, after monitoring the event triggering (such as the user clicking the "initiate" button to trigger the "process initiation event"), the event type (such as "PROCESS_START"), context information, and business data are automatically encapsulated, an event message is generated, and the event message is pushed to the event service through an internal RPC protocol.

[0099] If yes, in step S82, the interaction logic and the exception handling mechanism corresponding to the core event are obtained based on the event type of the core event. It should be noted that the interaction logic refers to the data transmission rules between the process development platform and the third-party system and the processing logic inside the process after a certain type of core event is triggered, including the data request format (including context information + business data), the return data analysis rule, and the process node promotion logic; the exception handling mechanism refers to the preset coping strategy for the abnormal scenarios (such as parameter error, interface timeout, and data format error) that may occur in the interaction process of a certain type of core event, including the retry mechanism, the error prompt mode, and the data rollback rule, which avoids the confusion in event processing due to "no unified rules and repeated development of adaptation logic", and at the same time ensures that there is a clear coping strategy for abnormal scenarios, and improves the accuracy and stability of event processing.

[0100] Specifically, after determining the trigger of the core event and determining the event type, the event interaction rule module first queries the preset event interaction rule library, such as Table 1; according to the event type of the core event (such as "data verification event") as a query condition, the interaction logic corresponding to the type of event is accurately located: for example, the interaction logic of the data verification event is "the process development platform sends a form data request to the third-party system, receives the verification result returned by the third-party system, and if the verification is passed, the "initiate" button is activated, and if the verification fails, the error field is highlighted"; at the same time, the exception handling mechanism corresponding to the type of event is called: for example, "if the third-party system returns a parameter error, display the "form data format exception, please check" prompt; if the interface call times out, automatically retry 3 times with an interval of 1000 milliseconds, and if the retry fails, record the error log"; the module performs integrity check on the called interaction logic and exception handling mechanism to ensure that there is no logic loss (such as the interaction logic needs to include data request and return analysis, and the exception handling mechanism needs to cover common exception scenarios); after the check is passed, the interaction logic and the exception handling mechanism are encapsulated as "event processing rule package" and pushed to the process development module simultaneously to provide basis for subsequent core event management.

[0101] Step S83, based on the interaction logic and the exception handling mechanism, the core event is managed.

[0102] It should be noted that the management of the core event means that the normal processing flow of the core event is executed according to the interaction logic, and the exception handling mechanism is started when an exception occurs, so as to ensure that the core event processing meets the target process requirements and the third-party system interface specification.

[0103] Specifically, when the process triggers an event, the event is accurately pushed through three-level scheduling of "process development platform (process engine) - event service - third-party system", and the specific process is as follows: (1) Event triggering and reporting: the process engine detects the triggering of an event (such as a user clicking the "initiate" button to trigger the "process initiation event"), automatically encapsulates the event type (such as "PROCESS_START"), context information, and business data, generates an event message, and pushes it to the event service through an internal RPC protocol.

[0104] (2) Event service analysis and routing: after the event service receives the message, it performs three core operations: A. Event type matching: according to the event type (such as "PROCESS_START") to map to the corresponding interface (such as the ProcessStartService interface implemented by the third-party system), determine the interface access path (such as concatenating "interfacePath + / processStart").

[0105] B. Environment information matching: Obtain the current environment (such as "prod") from the "envFlag" field of the event context, and query the deployment information (serverIp, apiPort, apiProtocol) of the third-party system in the environment.

[0106] C. Push parameter encapsulation: According to the interface requirements of the third-party system, convert the event message into an HTTP / HTTPS request (automatically load SSL certificate in HTTPS scenario), set the request header (including identity authentication Token, automatically generated by JAR package) and timeout.

[0107] (3) Event push and result feedback: The event service initiates a request to the third-party system interface, and after receiving the returned result, synchronously feeds back to the process engine: A. If "success" is returned: the process engine performs subsequent operations (such as recording initiation logs and advancing process nodes).

[0108] B. If "fail" or request timeout is returned: the process engine triggers a retry mechanism (default retry 3 times, interval 1000 milliseconds), and after retry failure, records error logs and shows error prompts (such as "system interface timeout, please try later") to the user, ensuring the consistency of the process state.

[0109] The embodiment detects whether the target user triggers the core event of the whole life cycle in the target process, and then if so, based on the event type of the core event, obtains the interaction logic and exception handling mechanism corresponding to the core event, thereby managing the core event based on the interaction logic and the exception handling mechanism, and then through real-time detection of the target user's triggering behavior of the core event (such as initialization, process initiation, task submission, etc.) of the whole life cycle of the target process, ensures that there is no event missing, avoids process interruption or data synchronization lag due to events not being responded in time, and through calling the preset exception handling mechanism (such as retry, data rollback, error prompt), quickly responds when the event processing appears abnormal (such as interface timeout, data format error), reduces the influence of the exception on the process, guarantees the stability of the process, and solves the pain points of the traditional process platform "high coupling degree of exception handling, not timely response".

[0110] It should be understood that the size of the serial number of each step in the above embodiment does not mean the order of execution, and the execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiment of the present application.

[0111] The application provides a flow development device, comprising: at least one processor; and a memory connected with the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform the flow development method in the above embodiment one.

[0112] Reference will now be made to the following description Figure 4 which shows a structural schematic diagram of a flow development device suitable for implementing the embodiments of the application. The flow development device in the embodiments of the application can include, but is not limited to, mobile terminals such as mobile phones, notebook computers, digital broadcast receivers, PDAs (Personal Digital Assistant), PADs (Portable Application Description), PMPs (Portable Media Player), vehicle-mounted terminals (for example, vehicle-mounted navigation terminals), and the like, and fixed terminals such as digital TVs, desktop computers, and the like. Figure 4 The flow development device shown is merely an example and should not bring any limitation to the functions and use range of the embodiments of the application.

[0113] As shown in Figure 4 , the flow development device can include a processing apparatus 1001 (for example, a central processor, a graphic processor, or the like) which can perform various appropriate actions and processes according to programs stored in a read-only memory 1002 or loaded from a storage apparatus 1003 into a random access memory 1004. In the random access memory 1004, various programs and data required for the operation of the flow development device are also stored. The processing apparatus 1001, the read-only memory 1002, and the random access memory 1004 are connected to each other through a bus 1005. An input / output interface 1006 is also connected to the bus. Generally, the following systems can be connected to the input / output interface 1006: input apparatuses 1007 including, for example, a touch screen, a touch pad, a keyboard, a mouse, an image sensor, a microphone, an accelerometer, a gyroscope, and the like; output apparatuses 1008 including, for example, a liquid crystal display (LCD), a speaker, a vibrator, and the like; the storage apparatus 1003 including, for example, a magnetic tape, a hard disk, and the like; and a communication apparatus 1009. The communication apparatus 1009 can allow the flow development device to perform wireless or wired communication with other devices to exchange data. Although the flow development device having various systems is shown in the figure, it should be understood that all the systems shown are not required to be implemented or provided. More or less systems can be alternatively implemented or provided.

[0114] In particular, according to the embodiments disclosed in the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, the embodiments disclosed in the present application include a computer program product comprising a computer program carried on a computer readable medium, the computer program containing program code for executing the method shown in the flowchart. In such embodiments, the computer program can be downloaded and installed from a network through a communication device, or installed from the storage device 1003, or installed from the read-only memory 1002. When the computer program is executed by the processing device 1001, the above-mentioned functions defined in the method of the embodiments disclosed in the present application are executed.

[0115] The process development device provided by the present application adopts the process development method in the above-mentioned embodiments, and can solve the technical problems in the background art. Compared with the prior art, the process development device provided by the present application has the same beneficial effects as the process development method provided by the above-mentioned embodiments, and other technical features in the process development device are the same as the features disclosed in the previous embodiment method, which will not be repeated here.

[0116] It should be understood that parts of the present application can be realized by hardware, software, firmware or a combination thereof. In the description of the above-mentioned embodiments, specific features, structures, materials or characteristics can be combined in any one or more embodiments or examples in a suitable manner.

[0117] The above is merely specific implementation of the present application, but the protection scope of the present application is not limited thereto, any person skilled in the art can easily think of changes or replacements within the technical scope disclosed in the present application, which should be covered in the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

[0118] The present application provides a computer readable storage medium having stored thereon computer readable program instructions (i.e. computer program) for executing the process development method in the above-mentioned embodiments.

[0119] The computer readable storage medium provided in the application may be, for example, a U disk, but is not limited to an electric, magnetic, optical, electromagnetic, infrared, or semiconductor system or device, or any combination of the above. More specific examples of the computer readable storage medium may include, but are not limited to, an electric connection with one or more conductive wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the embodiment, the computer readable storage medium may be any tangible medium containing or storing a program that can be used by or in combination with an instruction execution system or device. The program code contained on the computer readable storage medium can be transmitted by any suitable medium, including but not limited to an electric wire, an optical cable, an RF (Radio Frequency), and the like, or any suitable combination of the above.

[0120] The computer readable storage medium described above may be contained in the process development device, or may exist separately without being assembled into the process development device.

[0121] The computer readable storage medium described above carries one or more programs, which, when executed by the process development device, cause the process development device to: obtain a process construction requirement of a target user, construct a target process structure based on the process construction requirement through a process structure construction model, receive a process adjustment operation of the target user, adjust the target process structure to obtain a target process modeling model, obtain process access data corresponding to the target process modeling model through a connection third-party standard interface, and develop a target process based on the target process modeling model and the process access data to generate the target process.

[0122] Computer program code for carrying out operations of the present application can be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C++ or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code can execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer can be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection can be made to an external computer (for example, through the Internet using an Internet Service Provider).

[0123] The computer program instructions can also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide processes for implementing the functions / acts specified in the flowchart and / or block diagram block or blocks.

[0124] The modules involved in the embodiments of the present application can be implemented in software or hardware. In some cases, the name of the module does not constitute a limitation on the module itself.

[0125] The readable storage medium provided by the present application is a computer readable storage medium, which stores computer readable program instructions (i.e. computer programs) for executing the above flow development method, and can solve the technical problems in the background art. Compared with the prior art, the computer readable storage medium provided by the present application has the same beneficial effects as the flow development method provided by the above embodiments, which will not be described here.

[0126] The embodiment of the present application provides a computer program product, comprising a computer program, which realizes the steps of the flow development method as described above when executed by a processor.

[0127] The computer program product provided by the present application can solve the technical problems in the background art. Compared with the prior art, the beneficial effects of the computer program product provided by the embodiment of the present application are the same as those of the flow development method provided by the above-mentioned embodiment, and are not described here.

[0128] The above-mentioned is only part of the embodiments of the present application, and does not limit the patent scope of the present application. Any equivalent structural transformation, direct / indirect application in other related technical fields made by using the content of the present application specification and drawings within the technical concept of the present application are included in the patent protection scope of the present application.

Claims

1. A process development platform comprising a visual configuration module, a process modeling module, a third-party interface module, and a process development module, characterized in that: the visual configuration module is configured to obtain process construction requirements of a target user; the process modeling layer is configured to construct a target process structure based on the process construction requirements through a process structure construction model, receive process adjustment operations of the target user, model the target process structure, and obtain a target process modeling model; the third-party interface module is configured to obtain process access data corresponding to the target process modeling model by connecting a third-party standard interface; the process development module is configured to develop a target process based on the target process modeling model and the process access data, and generate the target process.

2. The process development platform of claim 1, wherein, Further comprising a basic support module configured to manage and provide a standardized node library and a multi-environment configuration center.

3. The process development platform of claim 1, wherein, The process modeling module is further configured to receive process adjustment operations of the target user through a drag-and-drop process design tool and a visual process design tool.

4. The process development platform of claim 1, wherein, Further comprising an event interaction rule module configured to configure core events in the entire life cycle of a target process to define trigger conditions, data interaction logic, and exception handling mechanisms of each core event, and realize event-driven standardized interaction.

5. The process development platform of claim 1, wherein, Further comprising a business data modeling module configured to construct a visual form model and configure data verification rules, and perform version management on the visual form model.

6. A process development method characterized by, The method comprises: obtaining process construction requirements of a target user; constructing a target process structure based on the process construction requirements through a process structure construction model, receiving process adjustment operations of the target user, adjusting the target process structure, and obtaining a target process modeling model; obtaining process access data corresponding to the target process modeling model by connecting a third-party standard interface; developing a target process based on the target process modeling model and the process access data, and generating the target process.

7. The process development method of claim 6, wherein, The method further comprises: detecting whether a core event in the entire life cycle of the target process is triggered by the target user; if so, obtaining interaction logic and exception handling mechanisms corresponding to the core event based on the event type of the core event; 8. The process development method of claim 6, wherein, managing the core event based on the interaction logic and the exception handling mechanisms. The process development device comprises a memory, a processor, and a computer program stored on the memory and executable on the processor, wherein the computer program is configured to implement the steps of the process development method according to any one of claims 6 to 8. ​ ​ 9. A flow development device, characterized by, ​ 10. A storage medium, characterized by The storage medium is a computer readable storage medium, and the storage medium stores a computer program. The computer program is executed by the processor to implement the steps of the flow development method in any one of claims 6 to 8.

Images