Data processing method and device, equipment, storage medium and program product

Abstract

The invention provides a data processing method and device, equipment, a storage medium and a program product, which are applied to various workflow arrangement scenes such as cloud technology, artificial intelligence, intelligent transportation and vehicle-mounted. The data processing method comprises the steps of presenting a node selection area and a workflow arrangement area, and presenting a selected target form node in the workflow arrangement area in response to a node selection operation of moving form nodes in the node selection area to the workflow arrangement area; in response to a form construction operation for the target form node, presenting a form item selection control and a form presentation area; in response to a form item selection operation for the form item selection control, presenting the target form in the form presentation area; in response to a first confirmation operation for the target form, presenting a target form node and a target workflow; and outputting arrangement success information in response to a second confirmation operation for the target form node and the target workflow. According to the invention, the workflow arrangement efficiency can be improved.

Description

Technical Field

[0001] This application relates to data processing technology in the field of computer applications, and particularly relates to a data processing method, apparatus, device, storage medium, and program product. Background Art

[0002] A workflow refers to a way of representing an actual business model through a flow chart; through a workflow, specific business processes can be completed in an automated manner. Generally, the execution of a workflow can be triggered by a form. However, when constructing a workflow, a manual coding method is often used to generate a form for triggering the execution of the workflow, which affects the construction efficiency of the workflow. Summary of the Invention

[0003] Embodiments of this application provide a data processing method, apparatus, device, storage medium, and program product, which can improve the construction efficiency of a workflow.

[0004] The technical solution of the embodiments of this application is implemented as follows:

[0005] Embodiments of this application provide a data processing method, the method including:

[0006] Present a node selection area and a workflow orchestration area, and in response to a node selection operation of moving a form node in the node selection area to the workflow orchestration area, present the selected target form node in the workflow orchestration area, where the target form node is used to trigger the execution of a workflow;

[0007] In response to a form construction operation on the target form node, present a form item selection control and a form presentation area;

[0008] In response to a form item selection operation on the form item selection control, present a target form constructed by at least one selected form item in the form presentation area;

[0009] In response to a first confirmation operation on the target form, present the target workflow triggered by the target form node;

[0010] In response to a second confirmation operation on the target form node and the target workflow, output a successful orchestration message.

[0011] Embodiments of this application provide a data processing apparatus, the data processing apparatus including:

[0012] A node selection module, configured to present a node selection area and a workflow orchestration area, and in response to a node selection operation of moving a form node in the node selection area to the workflow orchestration area, present the selected target form node in the workflow orchestration area, where the target form node is used to trigger the execution of a workflow;

[0013] A form construction module, configured to present form item selection controls and a form presentation area in response to a form construction operation on the target form node;

[0014] The form construction module is further configured to present a target form constructed by at least one selected form item in the form presentation area in response to a form item selection operation on the form item selection controls;

[0015] The node selection module is further configured to present a target workflow triggered by the target form node in response to a first confirmation operation on the target form;

[0016] An orchestration processing module, configured to output an orchestration success message in response to a second confirmation operation on the target form node and the target workflow.

[0017] In an embodiment of the present application, the form item selection controls are presented in a form item editing area; the form construction module is further configured to present information of at least one selected form item in the form item editing area in response to the form item selection operation on the form item selection controls, where the form item information includes at least one of the following: form item description, extended information, form item label, form item type, required flag, type label, form value; and present the target form constructed by at least one of the form items in the form presentation area, where at least one of the form items corresponds to at least one of the form item information one by one.

[0018] In an embodiment of the present application, the node selection module is further configured to present the node selection area and the workflow orchestration area including the target form node in response to a form confirmation operation on the target form; and present the target workflow triggered by the target form node in the workflow orchestration area in response to a node addition operation performed on the target form node in the node selection area, where the first confirmation operation includes the form confirmation operation and the node addition operation.

[0019] In an embodiment of the present application, the node selection module is further configured to present at least one selected workflow node in the workflow orchestration area.

[0020] In an embodiment of the present application, the node selection module is further configured to, in response to a form confirmation operation for the target form, present the node selection area and the workflow orchestration area including the target form node and at least one of the workflow nodes; in response to a node addition operation for the node selection area, present, in the workflow orchestration area, the target workflow triggered by the target form node, where the target workflow includes at least one of the workflow nodes and one or more workflow nodes added by the node addition operation; or, in response to the form confirmation operation for the target form, present the node selection area and the workflow orchestration area, and present, in the workflow orchestration area, the target form node and the target workflow constructed by at least one of the workflow nodes triggered by the target form node.

[0021] In an embodiment of the present application, the data processing device further includes a form response module, configured to, in response to a form access request, present the target form; in response to a form submission operation for the target form, obtain target form information; execute the target workflow based on the target form information to obtain a workflow execution result; and present a form submission result of the target form based on the workflow execution result.

[0022] In an embodiment of the present application, the form response module is further configured to, in response to the form access request, obtain form access information, where the form access information includes one or both of a target form identifier and an access account; perform access verification based on the form access information to obtain an access verification result, where the access verification includes at least one of the following: validity verification of a form address corresponding to the target form identifier, access account permission verification, form opening verification, and access account login status verification; and present the target form when the access verification result indicates that the access verification is passed.

[0023] In an embodiment of the present application, the orchestration processing module is further configured to, in response to the second confirmation operation for the target form node and the target workflow, store the target form and the target workflow correspondingly to obtain a form-workflow relationship between the form and the workflow, and present the orchestration success information.

[0024] In an embodiment of the present application, the form response module is further configured to determine the target workflow corresponding to the target form based on the form-workflow relationship; instantiate the target workflow into a target workflow instance based on the target form information; and execute the target workflow instance to obtain the workflow execution result.

[0025] In the embodiment of the present application, the form response module is further configured to parse the target workflow instance to obtain an application instance execution order and an application instance set, where each application instance in the application instance set is an instance result of an application corresponding to a workflow node in the target workflow; based on the application instance execution order and the application instance set, iteratively perform the following processing: determine a to-be-executed application instance from the application instance set based on the application instance execution order; execute the to-be-executed application instance to obtain an application execution result; when the to-be-executed application instance is the last to-be-executed application instance, the iteration ends, and the application execution result obtained at the end of the iteration is determined as the workflow execution result.

[0026] In the embodiment of the present application, the form response module is further configured to, in response to the process of pushing the to-be-executed application instance to the application instance queue, perform an increase process on the number of to-be-executed instances; in response to the process of obtaining the to-be-executed application instance from the application instance queue, perform a decrease process on the number of to-be-executed instances and an increase process on the number of instances in execution; in response to the obtaining of the application execution result, perform a decrease process on the number of instances in execution; when the number of to-be-executed instances is a first specified number and the number of instances in execution is a second specified number, determine that the to-be-executed application instance is the last application instance.

[0027] In the embodiment of the present application, the form response module is further configured to determine a reference application instance and a reference execution index of the to-be-executed application instance; combine the reference application instance and the reference execution index to obtain a target execution result from an execution result set, where the execution result set includes each execution result of each executed application instance in the target workflow instance; execute the to-be-executed application instance based on the target execution result to obtain the application execution result; store the to-be-executed application instance, the current execution index of the to-be-executed application instance, and the application execution result in the execution result set in a corresponding manner.

[0028] In the embodiment of the present application, the data processing device further includes a form configuration module, configured to present a form configuration area in response to a configuration trigger operation for the target form node; present form configuration information in response to a form configuration operation performed in the form configuration area, where the form configuration information includes at least one of the following: test data, form title, form description, form submission account, form associated account, login status detection flag, and echo output information; present the form item selection control and the form presentation area in response to a configuration confirmation operation for the form configuration information, where the form construction operation includes the configuration trigger operation, the form configuration operation, and the configuration confirmation operation.

[0029] In an embodiment of the present application, the data processing device further includes a list presentation module, configured to present a workflow browsing control for the successfully orchestrated information; in response to a workflow browsing operation on the workflow browsing control, present a workflow list, where the attributes of the workflow list include at least one of the following: workflow name, form address, creation time, start flag; present the target workflow in the workflow list.

[0030] An embodiment of the present application provides an electronic device for data processing, the electronic device includes:

[0031] a memory, configured to store computer-executable instructions or a computer program;

[0032] a processor, configured to implement the data processing method provided by the embodiment of the present application when executing the computer-executable instructions or the computer program stored in the memory.

[0033] An embodiment of the present application provides a computer-readable storage medium, storing computer-executable instructions or a computer program, the computer-executable instructions or the computer program being configured to implement the data processing method provided by the embodiment of the present application when executed by a processor.

[0034] An embodiment of the present application provides a computer program product, including computer-executable instructions or a computer program, the computer-executable instructions or the computer program being configured to implement the data processing method provided by the embodiment of the present application when executed by a processor.

[0035] The embodiment of the present application at least has the following beneficial effects: In the process of constructing a workflow, when presenting a selected target form node in the workflow orchestration area, a form item selection control and a form presentation area can be presented by triggering a form construction operation on the target form node; and since the form item selection control is used to select form items, the form presentation area is used to present at least one selected form item, and the at least one selected form item is used to construct a target form; therefore, the construction of the target form can be realized through visual operations, and then, based on the constructed form, a workflow is constructed, which can improve the construction efficiency of the workflow. BRIEF DESCRIPTION OF THE DRAWINGS

[0036] Figure 1 is a schematic diagram of the architecture of the data processing system provided by the embodiment of the present application;

[0037] Figure 2 is a kind of Figure 1 terminal provided by the embodiment of the present application;

[0038] Figure 3 is a schematic flowchart of the image processing method provided by the embodiment of the present application Figure 1 ;

[0039] Figure 4 It is a schematic diagram of an exemplary orchestration workflow provided by an embodiment of the present application;

[0040] Figure 5 It is a flowchart of an image processing method provided by an embodiment of the present application Figure 2 ;

[0041] Figure 6 It is a flowchart of an execution target workflow provided by an embodiment of the present application;

[0042] Figure 7 It is a schematic diagram of an exemplary workflow creation provided by an embodiment of the present application;

[0043] Figure 8 It is a schematic diagram of an exemplary form configuration provided by an embodiment of the present application;

[0044] Figure 9 It is a schematic diagram of an exemplary form creation provided by an embodiment of the present application;

[0045] Figure 10 It is another schematic diagram of an exemplary form creation provided by an embodiment of the present application;

[0046] Figure 11 It is another schematic diagram of an exemplary workflow creation provided by an embodiment of the present application;

[0047] Figure 12 It is a schematic diagram of an exemplary workflow list provided by an embodiment of the present application;

[0048] Figure 13 It is a flowchart of an exemplary form creation provided by an embodiment of the present application;

[0049] Figure 14 It is a flowchart of an exemplary form response provided by an embodiment of the present application;

[0050] Figure 15 It is a schematic diagram of an exemplary form submission provided by an embodiment of the present application;

[0051] Figure 16 It is a schematic diagram of an exemplary workflow instance execution provided by an embodiment of the present application;

[0052] Figure 17 It is a flowchart of an exemplary workflow instance execution provided by an embodiment of the present application;

[0053] Figure 18 It is a schematic diagram of an exemplary execution of an application instance queue provided by an embodiment of the present application;

[0054] Figure 19 This is a schematic diagram of global data for an exemplary application instance provided by an embodiment of the present application. Detailed implementation manners

[0055] In order to make the objectives, technical solutions, and advantages of the present application clearer, the present application will be further described in detail below with reference to the accompanying drawings. The described embodiments should not be construed as limitations on the present application. All other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the scope of protection of the present application.

[0056] In the following description, reference is made to "some embodiments", which describe a subset of all possible embodiments. However, it can be understood that "some embodiments" can be the same subset or different subsets of all possible embodiments and can be combined with each other without conflict.

[0057] In the following description, the terms "first / second / third / fourth" are used to distinguish similar objects and do not represent a specific order for the objects. It can be understood that "first / second / third / fourth" can be interchanged with a specific order or sequence when allowed, so that the embodiments of the present application described herein can be implemented in an order other than that illustrated or described herein.

[0058] In the embodiments of the present application, the term "module" or "unit" refers to a computer program with a predetermined function or a part of a computer program, which works together with other related parts to achieve a predetermined goal, and can be fully or partially implemented by using software, hardware (such as a processing circuit or a memory), or a combination thereof. Similarly, a processor (or multiple processors or memories) can be used to implement one or more modules or units. In addition, each module or unit can be a part of an overall module or unit that includes the function of the module or unit.

[0059] Unless otherwise defined, all technical and scientific terms used in the embodiments of the present application have the same meaning as commonly understood by those of ordinary skill in the technical field to which the present application belongs. The terms used in the embodiments of the present application are only for the purpose of describing the embodiments of the present application and are not intended to limit the present application.

[0060] Before further elaborating on the embodiments of the present application, the nouns and terms involved in the embodiments of the present application are explained. The nouns and terms involved in the embodiments of the present application are applicable to the following explanations.

[0061] 1) Workflow is a computational model of a work process; it refers to the automation of part or the whole of a business process in a computer application environment, and is an abstract and general description of the business rules between the work process and its various operation steps. A workflow is usually a description of the process of automatically transmitting documents, information, or tasks among multiple participants according to a certain predetermined rule by using a computer to achieve a certain business goal. Among them, a workflow can represent the actual business model in the form of a flowchart, and through the workflow, specific business processing can be completed in an automated manner.

[0062] 2) A workflow engine refers to the routing controller of a workflow. Usually, a workflow corresponds to an actual business in circulation, and the execution route of the workflow is controlled by the instance data corresponding to the current application module (APP, simply referred to as an application). In addition, the transfer rules are specified when the workflow is defined, and the transfer rules are determined based on the instance data and variable expressions corresponding to the current application. In the embodiments of the present application, the workflow engine is used to parse the instance data and variable expressions corresponding to the current application according to the context environment when the workflow is executed, and determine the next execution direction of the workflow.

[0063] 3) An application module or an application is used to implement a function or an interface service. In the embodiments of the present application, an application is an atomic task, which is the most basic execution unit in a workflow.

[0064] 4) An application module instance, simply referred to as an application instance, is obtained by instantiating an application. That is to say, an application is equivalent to a template, and the usually corresponding parameters are default parameters. While an application instance uses a template and actual business parameters. In the embodiments of the present application, the application instance data and the application together constitute an application instance.

[0065] 5) A workflow definition language is used to describe the syntax specification of a workflow. For example, the "Json" language.

[0066] 6) A path syntax expression is used to index the input data or output data of each application instance in a workflow. For example, "{AppInstId.data.0.name}". Through the path syntax expression, dynamic parsing and reference of data can be realized during the execution of the workflow. In the embodiments of the present application, the reference data of an application instance can be a path syntax expression.

[0067] 7) A workflow task, also known as a workflow instance or an execution task, refers to a to-be-executed instance generated when the execution of a workflow is triggered. In the embodiments of the present application, different input parameters of the workflow corresponding to when the execution of the workflow is triggered will generate different workflow instances.

[0068] 8) Form, an interface interaction element for collecting input information, usually including fields for input or selection to capture the input information, and may also include submission controls such as buttons for sending the captured input information to a specified processing device.

[0069] 9) Form engine, used to create, manage, and process forms; through the form engine, forms can be added to business applications, and forms can be customized by means of drag-and-drop and configuration; the form engine is also used to implement functions such as data validation, data binding, layout, and styling to improve the efficiency of collecting input data; thus, it can reduce the complexity of form generation, improve the form generation efficiency, and the flexibility in terms of functions and styles.

[0070] 10) Low-code refers to the process of quickly creating business programs by using visual components and predefined templates. When implementing low-code, functions such as drag-and-drop interface design, visual modeling tools, flowcharts, and predefined templates can be used to quickly build business programs. Through low-code, the consumption and time-consuming of business program development can be reduced, and it can be integrated into existing systems and data sources. The workflow construction process provided in the embodiments of the present application is a low-code method.

[0071] 11) In response to, used to represent the conditions or states on which the executed operations depend. When the dependent conditions or states are met, one or more operations to be executed can be real-time or can have a set delay; without special instructions, there is no restriction on the execution order of multiple operations to be executed.

[0072] 12) Operation is a way to trigger a device to perform processing. For example, click operation, double-click operation, long-press operation, swipe operation, gesture operation, drag operation, received trigger instructions, etc.; in addition, various operations in the embodiments of the present application can be a single operation or a general term for multiple operations; and various operations in the embodiments of the present application can be touch operations or non-touch operations.

[0073] It should be noted that the execution of the workflow can be triggered by a form. However, when constructing a workflow, it is often the case that a form for triggering the execution of the workflow is generated by manual coding. That is to say, first determine the form layout and add form items based on the form requirements, then implement the form interaction logic, debugging, and testing based on the form requirements, and finally deploy and maintain the form. Among them, the form requirements are determined based on the business requirements, including the functions, interfaces, interaction logics, etc. of the form; the form layout includes the positions, sizes, arrangement methods, etc. of each form item in the form, which can be implemented using Hyper Text Markup Language (HTML) and Cascading Style Sheets (CSS); the form interaction logic includes form validation and submitting form data, etc., which can be implemented using a scripting language (for example, JavaScript language); debugging and testing are used to ensure the normality of the form functions and interaction logics; deployment and maintenance refer to deploying the form to application devices such as servers for access after completing the debugging and testing of the form, and regularly maintaining and updating it to ensure the stability and security of the form. In this way, the complexity of form acquisition is increased, which affects the acquisition time and quality of the form, and further affects the construction efficiency of the workflow.

[0074] Based on this, the embodiments of the present application provide a data processing method, apparatus, device, computer-readable storage medium, and computer program product, which can improve the construction efficiency of the workflow. The following describes an exemplary application of the electronic device for data processing (hereinafter simply referred to as the data processing device) provided by the embodiments of the present application. The data processing device provided by the embodiments of the present application can be implemented as various types of terminals such as smart phones, smart watches, laptop computers, tablet computers, desktop computers, smart home appliances, set-top boxes, smart in-vehicle devices, portable music players, personal digital assistants, dedicated messaging devices, intelligent voice interaction devices, portable game devices, and smart speakers, or can also be implemented as a server. The following will describe the exemplary application when the data processing device is implemented as a terminal.

[0075] See Figure 1 , Figure 1 is a schematic diagram of the architecture of the data processing system provided by the embodiments of the present application; as Figure 1As shown, to support a data processing application, in a data processing system 100, terminals 400 (exemplarily showing terminals 400-1 and 400-2) are connected to a server 200 through a network 300; the network 300 can be a wide area network, a local area network, or a combination of both; the server 200 is used to respond to service requests from the terminals 400 (such as requests for storing forms and workflows, responding to form requests, executing workflow requests, etc.). Additionally, the data processing system 100 further includes a database 500 for providing data support to the server 200; and, Figure 1 Shown in it is a case where the database 500 is independent of the server 200. In addition, the database 500 can also be integrated in the server 200, and the embodiments of this application do not limit this.

[0076] The terminal 400 is used to present a node selection area and a workflow orchestration area (exemplarily showing a graphical interface 410-1), and in response to a node selection operation of moving a form node in the node selection area to the workflow orchestration area, present the selected target form node in the workflow orchestration area, where the target form node is used to trigger the execution of a workflow; in response to a form construction operation on the target form node, present form item selection controls and a form presentation area; in response to a form item selection operation on the form item selection controls, present a target form constructed by at least one selected form item in the form presentation area (exemplarily showing a graphical interface 410-2); in response to a first confirmation operation on the target form, present the target workflow triggered by the target form node; in response to a second confirmation operation on the target form node and the target workflow, output an orchestration success message.

[0077] In some embodiments, the server 200 can be an independent physical server, or a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, Content Delivery Network (CDN), and big data and artificial intelligence platforms. The terminals and the server can be directly or indirectly connected through wired or wireless communication methods, and the embodiments of this application do not limit this.

[0078] See Figure 2 , Figure 2 is a structural schematic diagram of a terminal provided by an embodiment of this application; as Figure 1 in Figure 2As shown, the terminal 400 includes: at least one processor 410, a memory 450, at least one network interface 420 and a user interface 430. The various components in the terminal 400 are coupled together through a bus system 440. It can be understood that the bus system 440 is used to realize the connection and communication between these components. In addition to the data bus, the bus system 440 also includes a power bus, a control bus and a status signal bus. However, for the sake of clarity, Figure 2 Various buses are labeled as bus system 440 .

[0079] The processor 410 can be an integrated circuit chip with signal processing capabilities, such as a general-purpose processor, a digital signal processor (DSP), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc., where the general-purpose processor can be a microprocessor or any conventional processor, etc.

[0080] The user interface 430 includes one or more output devices 431 that enable presentation of media content, including one or more speakers and / or one or more visual display screens. The user interface 430 also includes one or more input devices 432, including user interface components that facilitate user input, such as a keyboard, mouse, microphone, touch screen display, camera, other input buttons and controls.

[0081] The memory 450 may be removable, non-removable, or a combination thereof. Exemplary hardware devices include solid-state memory, hard disk drives, optical disk drives, etc. The memory 450 may optionally include one or more storage devices that are physically remote from the processor 410.

[0082] The memory 450 includes a volatile memory or a non-volatile memory, and may also include both volatile and non-volatile memories. The non-volatile memory may be a read-only memory (ROM), and the volatile memory may be a random access memory (RAM). The memory 450 described in the embodiments of the present application is intended to include any suitable type of memory.

[0083] In some embodiments, memory 450 can store data to support various operations, examples of which include programs, modules, and data structures, or a subset or superset thereof, as exemplarily described below.

[0084] Operating system 451, including system programs for processing various basic system services and performing hardware-related tasks, such as a framework layer, a core library layer, a driver layer, etc., for implementing various basic services and processing hardware-based tasks;

[0085] A network communication module 452 for reaching other electronic devices via one or more (wired or wireless) network interfaces 420. Exemplary network interfaces 420 include: Bluetooth, Wi-Fi (Wireless Fidelity), Universal Serial Bus (USB), etc.

[0086] A presentation module 453 for enabling the presentation of information (such as a user interface for operating peripheral devices and displaying content and information) via one or more output devices 431 associated with the user interface 430 (such as a display screen, a speaker, etc.).

[0087] An input processing module 454 for detecting and translating one or more user inputs or interactions from one of the one or more input devices 432.

[0088] In some embodiments, the data processing device provided by the embodiments of the present application can be implemented in software. Figure 2 Shown is a data processing device 455 stored in the memory 450, which can be software in the form of programs and plugins, etc., including the following software modules: a node selection module 4551, a form building module 4552, an orchestration processing module 4553, a form response module 4554, a form configuration module 4555, and a list presentation module 4556. These modules are logical, so they can be combined arbitrarily or further split according to the functions implemented. The functions of each module will be described below.

[0089] In some embodiments, the data processing device provided by the embodiments of the present application can be implemented in hardware. As an example, the device provided by the embodiments of the present application can be a processor in the form of a hardware decoding processor, which is programmed to execute the data processing method provided by the embodiments of the present application. For example, a processor in the form of a hardware decoding processor can adopt one or more Application Specific Integrated Circuits (ASICs), DSPs, Programmable Logic Devices (PLDs), Complex Programmable Logic Devices (CPLDs), Field-Programmable Gate Arrays (FPGAs), or other electronic components.

[0090] In some embodiments, a terminal or a server may implement the data processing method provided in the embodiments of the present application by running various computer-executable instructions or computer programs. For example, the computer-executable instructions may be commands at the microprogram level, machine instructions, or software instructions. The computer program may be a native program or a software module in an operating system; it may be a native application (APPlication, APP), that is, a program that needs to be installed in the operating system to run, such as a workflow orchestration APP or a resource management APP; it may also be a small program that can be embedded in any APP, that is, a program that only needs to be downloaded to the browser environment to run. In short, the above computer-executable instructions may be instructions in any form, and the above computer programs may be application programs, modules, or plugins in any form.

[0091] Next, the data processing method provided in the embodiments of the present application will be described in conjunction with the exemplary applications and implementations of the data processing device provided in the embodiments of the present application. In addition, the data processing method provided in the embodiments of the present application is applied to various workflow orchestration scenarios such as cloud technology, artificial intelligence, intelligent transportation, and vehicle-mounted.

[0092] See Figure 3 , Figure 3 is a flowchart of the image processing method provided in the embodiments of the present application Figure 1 , where Figure 3 the execution subject of each step in Figure 3 is the data processing device; the following will be described in conjunction with

[0093] Step 101: Present a node selection area and a workflow orchestration area. In response to a node selection operation of moving a form node in the node selection area to the workflow orchestration area, present the selected target form node in the workflow orchestration area.

[0094] In the embodiments of the present application, when the data processing device receives a request to execute workflow orchestration, in response to the request, a node selection area and a workflow orchestration area are presented to complete the workflow orchestration in the workflow orchestration area by selecting nodes from the node selection area. First, when the operation of moving a form node in the node selection area to the workflow orchestration area is executed, the data processing device receives the node selection operation of moving the form node in the node selection area to the workflow orchestration area; at this time, the data processing device responds to the node selection operation and presents the selected form node in the workflow orchestration area, where the selected form node is the target form node.

[0095] It should be noted that the node selection area is used to present various nodes for choreographing a workflow, including form nodes and workflow nodes. Among them, the workflow node refers to the business node in the workflow, and the form node refers to the node used to trigger the execution of the workflow. Thus, the target form node can be used to trigger the execution of the workflow; the workflow choreography area is used to present each node selected from the node selection area and the execution order between the selected nodes; the node selection operation refers to the operation of selecting the form node used to trigger the execution of the workflow from the selection area and presenting the selected form node in the workflow choreography area. For example, drag-and-drop operations, click operations in the choreography mode, and so on.

[0096] Step 102: In response to a form building operation on the target form node, present a form item selection control and a form presentation area.

[0097] In the embodiment of the present application, when performing form building on the target form node, the data processing device also receives the form building operation; at this time, the data processing device responds to this form building operation and starts to perform form building processing on the target form node. Here, the data processing device first presents a form item selection control and a form presentation area to select form items through the form item selection control to complete the form building in the form presentation area.

[0098] It should be noted that the form building operation may refer to an operation for triggering form building on the target form node. For example, a long-press operation on the target form node, a right-click operation on the target form node, and an operation of clicking the form building option for the result of the right-click operation, and so on. The form item selection control refers to a control used to select various form items; the form presentation area is used to present the form items selected through the form item selection control, that is, the form presentation area is used to preview the form built through the form item selection control.

[0099] In the embodiment of the present application, the form building operation may also refer to a configuration trigger operation, a form configuration operation, and a configuration confirmation operation; at this time, the data processing device responds to the form building operation on the target form node and presents a form item selection control and a form presentation area, including: the data processing device first responds to the configuration trigger operation on the target form node and presents a form configuration area; then responds to the form configuration operation performed in the form configuration area and presents form configuration information; finally, responds to the configuration confirmation operation for the form configuration information and presents a form item selection control and a form presentation area.

[0100] It should be noted that when form configuration is performed on a target form node, the data processing device receives a configuration trigger operation. Thus, the configuration trigger operation refers to an operation that triggers form configuration for the target form node. For example, a right-click operation on the target form node and an operation of clicking on a form configuration option in the result of the right-click operation, and so on. In response to the configuration trigger operation, the data processing device presents a form configuration area, which includes at least one of the following controls: a test data control, a form title control, a form description control, a submission account control, an associated account control, a login status detection control, an echo output control, and a configuration confirmation control. When form configuration is performed on the target form node in the form configuration area, the data processing device receives a form configuration operation. Thus, the form configuration operation refers to an operation that performs form configuration on the target form node. For example, an operation of inputting configuration information for each control in the form configuration area, and so on. When confirmation is made for the form configuration information to start form construction, the data processing device receives a configuration confirmation operation. Thus, the configuration confirmation operation refers to an operation that triggers form construction for the form configuration information. For example, an operation of triggering a configuration confirmation control (such as a form design button) for the form configuration information, and so on. In response to the configuration confirmation operation, the data processing device starts form construction by presenting a form item selection control and a form presentation area. Among them, the form configuration information includes at least one of the following: test data, form title, form description, form submission account, form associated account, login status detection flag, and echo output information.

[0101] It should also be noted that the test data control is used to adopt test data, and the test data is used to identify whether it is data for testing; the form title control is used to collect the form title, and the form title is the title of the form; the form description control is used to collect the form description, and the form description is used to explain the form; the submission account control is used to collect the form submission account, and the form submission account refers to the account that is allowed to submit the form; the associated account control is used to collect the form associated account, and the form associated account refers to the account to be notified when the form is submitted; the login status detection control is used to collect the login status detection flag, and the login status detection flag refers to whether the submission of the form is restricted to the case where the account is in the logged-in state; the echo output control is used to collect the echo output information, and the echo output information is used to determine the information to be displayed after the form is submitted.

[0102] Step 103: In response to a form item selection operation on the form item selection control, present a target form constructed by at least one selected form item in the form presentation area.

[0103] In an embodiment of the present application, when a form item is selected through a form item selection control to construct a form for a target form node, the data processing device also receives a form item selection operation for the form item selection control; at this time, in response to the form item selection operation, the data processing device presents at least one selected form item in the form presentation area, where the form constructed by the at least one selected form item is the target form; thus, by presenting at least one selected form item in the form presentation area, the data processing device realizes the presentation of the constructed target form.

[0104] It should be noted that the form item selection operation refers to the operation of selecting a form item through a form item selection control and presenting the selected form item in the form presentation area; for example, the operation of triggering the form item selection control and selecting a form item from the presented form item list, or the operation of dragging a form item in the presented form item list, etc.; and, the form item selection operation can select at least one form item for constructing the target form. In addition, the target form is the form corresponding to the target form node.

[0105] In an embodiment of the present application, the form item selection control is presented in the form item editing area, and the form item editing area is used to present the form item information of each selected form item. The form item information refers to the various field information of the form item, which can be in text form, visual form, or a combination of both; at this time, in response to the form item selection operation for the form item selection control, the data processing device presents the target form constructed by at least one selected form item in the form presentation area, including: in response to the form item selection operation for the form item selection control, the data processing device presents at least one selected form item information in the form item editing area and presents the target form constructed by at least one form item in the form presentation area.

[0106] It should be noted that the form item information includes at least one of the following: form item description (Desc), extension information (Extension), form item key (Key), form item type (Type), required flag (Required), form item name (Label), form item value (Value); among them, the form item description is used to explain the form item, for example, parameter description or note, etc.; the form item key refers to the key name corresponding to the form item; the form item type refers to the type of the form item, for example, input box, selection box, rich text, etc. In addition, at least one form item corresponds to at least one form item information one by one.

[0107] Step 104: In response to the first confirmation operation for the target form, present the target workflow triggered by the target form node.

[0108] In an embodiment of the present application, when a confirmation is made for a target form or a confirmation is made for a target form and a workflow is constructed for a target form node, the data processing device receives a first confirmation operation; at this time, in response to the first confirmation operation, the data processing device presents the target form node corresponding to the target form and the target workflow triggered by the target form node.

[0109] It should be noted that the target workflow includes C workflow nodes, where C is a positive integer, and the C workflow nodes can be obtained through a node selection operation (in this case, C≥1), or can be obtained through the first confirmation operation (in this case, C≥1), or can be a combination of both (in this case, C>1), and so on. The embodiments of the present application do not limit this.

[0110] In an embodiment of the present application, when the first confirmation operation includes a form confirmation operation and a node addition operation, the data processing device, in response to the first confirmation operation for the target form, presents the target workflow triggered by the target form node, including: the data processing device, in response to the form confirmation operation for the target form, presents a node selection area and a workflow arrangement area including the target form node; in response to the node addition operation performed on the target form node in the node selection area, the target workflow triggered by the target form node is presented in the workflow arrangement area.

[0111] It should be noted that when a completion confirmation is made for the construction of the target form, the data processing device receives the form confirmation operation for the target form. Thus, the form confirmation operation is used to confirm that the construction of the target form has been completed. For example, clicking the save form button, etc.; at this time, in response to the form confirmation operation, the data processing device presents the node selection area and the workflow arrangement area again, and the presented workflow arrangement area includes the target form node for which the form construction has been completed. When a workflow node in the node selection area is moved to the workflow arrangement area, the data processing device receives the node addition operation performed on the target form node in the node selection area. Thus, the node addition operation refers to the operation of moving a workflow node in the node selection area to the workflow arrangement area. For example, the operation of dragging a workflow node in the node selection area to the workflow arrangement area, etc.; at this time, in response to the node addition operation, the data processing device presents the target workflow constructed by the selected C workflow nodes in the workflow arrangement area. Therefore, the C workflow nodes in the target workflow are obtained through the node addition operation in the first confirmation operation.

[0112] In S101 of the embodiment of the present application, after presenting the selected target form node in the workflow orchestration area, the data processing method further includes: the data processing device presenting at least one selected workflow node in the workflow orchestration area; that is, after selecting the target form node and before constructing the target form, at least one workflow node has been selected to construct the target workflow.

[0113] Correspondingly, in response to a first confirmation operation for the target form, the data processing device presents the target workflow triggered by the target form node, including: the data processing device presents a node selection area and a workflow orchestration area including the target form node and at least one workflow node in response to a form confirmation operation for the target form; in response to a node addition operation for the node selection area, the data processing device presents the target workflow triggered by the target form node in the workflow orchestration area, where the target workflow includes at least one workflow node and one or more workflow nodes added by the node addition operation; that is, after completing the construction of the target form, one or more workflow nodes are added, so that at this time, the C workflow nodes in the target workflow are obtained through the node selection operation and the node addition operation in the first confirmation operation.

[0114] Alternatively, in response to a form confirmation operation for the target form, the data processing device presents a node selection area and a workflow orchestration area, and presents the target form node and the target workflow constructed by at least one workflow node triggered by the target form node in the workflow orchestration area; that is, at this time, the C workflow nodes in the target workflow are obtained through the node selection operation.

[0115] It should be noted that here, the first confirmation operation still includes a form confirmation operation and a node addition operation.

[0116] It can be understood that the workflow node can be selected before the construction of the target form, or after the construction of the target form, or can be selected before and after the construction of the target form. In this way, the flexibility of workflow construction can be improved.

[0117] Step 105, in response to a second confirmation operation for the target form node and the target workflow, output a successful orchestration message.

[0118] In the embodiment of the present application, when it is confirmed that the workflow orchestration has been completed for the presented target form node and target workflow, the data processing device also receives the second confirmation operation for the target form node and the target workflow; at this time, the data processing device responds to the second confirmation operation and outputs a successful orchestration message to indicate that the workflow orchestration is successful.

[0119] It should be noted that the second confirmation operation refers to the operation performed when confirming that the workflow orchestration has been completed for the target form node and the target workflow. For example, the operation of clicking the save workflow button, etc. The orchestration success information refers to the prompt information indicating that the workflow orchestration is successful. Here, the orchestration success information can be output by presenting the prompt information, or by playing the prompt information, or by sending the prompt information, or it can be a combination of the above, etc. The embodiments of the present application do not limit this.

[0120] Exemplarily, refer to Figure 4 , Figure 4 which is a schematic diagram of an exemplary orchestration workflow provided by the embodiments of the present application; as Figure 4 shown, a node selection area 4-11 and a workflow orchestration area 4-12 are presented in the interface 4-1. In response to the node selection operation of moving the form node in the node selection area 4-11 to the workflow orchestration area, the selected target form node 4-13 is presented in the workflow orchestration area 4-12; in response to the form construction operation for the target form node 4-13, a form item selection control 4-21 and a form presentation area 4-22 are presented in the interface 4-2; in response to the form item selection operation for the form item selection control 4-21, a target form 4-23 constructed by the selected at least one form item is presented in the form presentation area 4-22; in response to the first confirmation operation for the target form 4-23, a target workflow 4-31 triggered by the target form node 4-13 is presented in the interface 4-3; in response to the second confirmation operation for the target form node 4-13 and the target workflow 4-31, an orchestration success information 4-41 is presented in the interface 4-4.

[0121] It can be understood that during the process of constructing the workflow, when the selected target form node is presented in the workflow orchestration area, the form item selection control and the form presentation area can be presented by triggering the form construction operation for the target form node; and since the form item selection control is used to select form items, the form presentation area is used to present the selected at least one form item, and the selected at least one form item is used to construct the target form; therefore, the construction of the target form can be achieved through visual operations, and further, based on the constructed form, the workflow can be constructed, which can improve the construction efficiency of the workflow.

[0122] Refer to Figure 5 , Figure 5 which is a schematic flowchart of the image processing method provided by the embodiments of the present application Figure 2 , where Figure 5 the execution subject of each step in Figure 5As shown, after step 105, steps 106 to 109 are further included; that is, after the data processing device outputs the successful orchestration information in response to the second confirmation operation for the target form node and the target workflow, the data processing method further includes steps 106 to 109, which are described separately below.

[0123] Step 106: In response to a form access request, present the target form.

[0124] In the embodiment of the present application, when accessing the target form based on a business processing task, the data processing device also receives a form access request; at this time, the data processing device presents the target form in response to the form access request to collect form information based on the presented target form.

[0125] Exemplarily, when the target form is a leave application form in an organization, when an organization member applies for leave through the leave application form, the data processing device also receives a form access request.

[0126] It should be noted that the data processing device can directly present the target form in response to the form access request, or can also present the target form after verifying the form access request. The embodiment of the present application does not limit this.

[0127] In the embodiment of the present application, when the data processing device presents the target form after verifying the form access request, presenting the target form in response to the form access request by the data processing device includes: the data processing device obtains form access information in response to the form access request; and performs access verification based on the form access information to obtain an access verification result; finally, when the access verification result indicates that the access verification is passed, present the target form.

[0128] It should be noted that the form access information includes one or both of the target form identifier and the access account. Among them, the target form identifier refers to the form identifier of the target form, and the form identifier is used to uniquely identify the form, and the access account refers to the account for accessing the target form. Here, the data processing device performs access verification on the form access information in combination with the form configuration information. The access verification includes at least one of the following: validity verification of the form address corresponding to the target form identifier, form opening verification, access account permission verification, and access account login status verification; among them, the validity verification of the form address corresponding to the target form identifier is used to verify whether the form address corresponding to the target form identifier is valid (also known as correct), that is, whether the form address can access the target form. If so, the verification is passed, otherwise it fails; the access account permission verification is used to verify whether the access account is the form submission account. If so, the verification is passed, otherwise it fails; the access account login status verification refers to whether the access account is obtained. If so, the verification is passed, otherwise it fails.

[0129] Step 107: In response to a form submission operation for a target form, obtain target form information.

[0130] In an embodiment of the present application, when information is input into the target form and the input information is submitted, the data processing device receives the form submission operation for the target form; at this time, in response to the form submission operation, the data processing device obtains the information input through the target form, and here the information input through the target form is referred to as target form information.

[0131] Step 108: Execute a target workflow based on the target form information to obtain a workflow execution result.

[0132] In an embodiment of the present application, the data processing device uses the target form information as the input data of the target workflow, and then executes the target workflow based on the target form information. The obtained execution result is the workflow execution result; thus, the workflow execution result is the execution result of the target workflow when the input data is the target form information.

[0133] See Figure 6 , Figure 6 is a schematic flowchart of executing a target workflow provided by an embodiment of the present application. Among them, Figure 6 the execution entity of each step in Figure 6 is the data processing device; as

[0134] shown in

[0135] Step 1081: Determine a target workflow corresponding to the target form based on the form-workflow relationship.

[0136] It should be noted that each time the workflow orchestration is completed, the data processing device stores the correspondence between the constructed form and the constructed workflow in the form-workflow relationship; thus, in the embodiments of the present application, the data processing device responds to the second confirmation operation for the target form node and the target workflow, and outputs an orchestration success message, including: the data processing device responds to the second confirmation operation for the target form node and the target workflow, stores the target form and the target workflow correspondingly, obtains the form-workflow relationship between the form and the workflow, and presents the orchestration success message.

[0137] Step 1082: Based on the target form information, instantiate the target workflow into a target workflow instance.

[0138] It should be noted that the data processing device uses the target form information as the input parameter of the target workflow to instantiate the target workflow, and thus obtains the target workflow instance. Therefore, the target workflow instance refers to the target workflow with the target form information as the input parameter.

[0139] Step 1083: Execute the target workflow instance to obtain a workflow execution result.

[0140] It should be noted that after the data processing device obtains the target workflow instance, it executes the target workflow instance, and the obtained execution result is the workflow execution result; thus, the workflow execution result refers to the output data when the input parameter of the target workflow is the target form information.

[0141] Continue to refer to Figure 6 , in the embodiments of the present application, Step 1083 can be implemented through Steps 10831 to 10834; that is to say, the data processing device executes the target workflow instance to obtain a workflow execution result, including Steps 10831 to 10834, and the following will explain each step separately.

[0142] Step 10831: Parse the target workflow instance to obtain the application instance execution order and the application instance set.

[0143] It should be noted that since the target workflow includes C workflow nodes, and each workflow node in the C workflow nodes corresponds to an application, when the target workflow is instantiated into a target workflow instance, the application is instantiated into an application instance; therefore, the target workflow instance includes an application instance set composed of C application instances, and each application instance in the application instance set is an instance result of the application corresponding to the workflow node in the target workflow. Thus, the data processing device can obtain the application instance set by parsing the target workflow instance. In addition, since the target workflow includes the execution order among C applications, therefore, for the target workflow instance, the execution order among the C application instances is the application instance execution order.

[0144] In the embodiment of the present application, the data processing device iteratively performs the following processes (step 10832 and step 10833) based on the application instance execution order and the application instance set, so as to sequentially execute the application instance set based on the application instance execution order.

[0145] Step 10832: Determine the to-be-executed application instance from the application instance set based on the application instance execution order.

[0146] In the embodiment of the present application, when starting to execute the target workflow instance, the data processing device obtains the first to-be-executed application instance from the application instance set based on the application instance execution order, and thus obtains the to-be-executed application instance; during the execution process of the target workflow instance, the data processing device obtains the next to-be-executed application instance from the application instance set based on the current execution instance and the application instance execution order, and thus obtains the to-be-executed application instance.

[0147] Step 10833: Execute the to-be-executed application instance to obtain an application execution result.

[0148] It should be noted that after the data processing device obtains the to-be-executed application instance, it executes the to-be-executed application instance, and the obtained execution result is the application execution result; thus, the application execution result is the execution result of the to-be-executed application instance.

[0149] In the embodiment of the present application, the data processing device executes the to-be-executed application instance to obtain an application execution result, including: the data processing device first determines the reference application instance and the reference execution index of the to-be-executed application instance; then combines the reference application instance and the reference execution index to obtain a target execution result from the execution result set; finally, executes the to-be-executed application instance based on the target execution result to obtain an application execution result.

[0150] It should be noted that the referenced application instance refers to the application instance referenced in the input parameters of the to-be-executed application instance; the referenced execution index refers to the execution order of the referenced application instance, for example, the 3rd time. Here, the execution result set includes the execution results of each executed application instance in the target workflow instance, that is, the corresponding relationship among the application instance, the execution result, and the execution index is included in the execution result set; thus, the data processing device can find the corresponding execution result in the execution result set by combining the referenced application instance and the referenced execution index, which is the target execution result. Finally, the data processing device directly uses the target execution result as the input data of the to-be-executed application instance, or uses the processing result of the target execution result as the input data of the to-be-executed application instance to execute the to-be-executed application instance, and the obtained execution result is the application execution result.

[0151] Correspondingly, after the data processing device executes the to-be-executed application instance and obtains the application execution result, the data processing method further includes storing the processing of the application execution result in the execution result set, that is: the data processing device stores the to-be-executed application instance, the current execution index of the to-be-executed application instance, and the application execution result in the execution result set in a corresponding manner. The current execution index refers to the current execution order of the to-be-executed application instance.

[0152] Step 10834, when the to-be-executed application instance is the last to-be-executed application instance, the iteration ends, and the application execution result obtained at the end of the iteration is determined as the workflow execution result.

[0153] It should be noted that when there are still to-be-executed application instances after the data processing device determines the to-be-executed application instance, steps 10832 and 10833 are iteratively executed; while when the to-be-executed application instance is the last to-be-executed application instance, the iteration ends.

[0154] In the embodiment of the present application, after the data processing device determines the to-be-executed application instance from the application instance set based on the application instance execution order, the data processing method further includes: the data processing device performs an increase process on the to-be-executed quantity in response to the process of pushing the to-be-executed application instance to the application instance queue; and performs a decrease process on the to-be-executed quantity and an increase process on the in-execution quantity in response to the process of obtaining the to-be-executed application instance from the application instance queue.

[0155] It should be noted that the execution of application instances can be realized through a distributed execution by an application instance queue; thus, when determining the execution of a target workflow instance, it is judged whether the execution of each application instance in the target workflow instance is completed through two variables, namely, the number of applications to be executed and the number of applications in execution. Among them, the number of applications to be executed refers to the number of application instances to be executed in the application instance queue for the target workflow instance, and the number of applications in execution refers to the number of application instances in the execution state for the target workflow instance. Here, when the data processing device pushes the application instance to be executed into the application instance queue, it can perform an increment process on the number of applications to be executed to increase the current number of applications to be executed by a third specified number (for example, 1, 3, etc.); and when the application instance to be executed is taken out from the application instance queue to execute the application instance to be executed, it can perform a decrement process on the number of applications to be executed to reduce the current number of applications to be executed by the third specified number, and perform an increment process on the number of applications in execution to increase the current number of applications in execution by a fourth specified number (for example, 1, 2, etc.).

[0156] Correspondingly, after the data processing device executes the application instance to be executed and obtains the application execution result, the data processing method further includes: the data processing device performs a decrement process on the number of applications in execution in response to the obtaining of the application execution result; and when the number of applications to be executed is a first specified number (for example, 0) and the number of applications in execution is a second specified number (for example, 0), it is determined that the application instance to be executed is the last application instance.

[0157] It should be noted that after the data processing device obtains the application execution result, it indicates that the execution of the application instance to be executed has been completed. Thus, a decrement process is performed on the number of applications in execution to reduce the current number of applications in execution by the fourth specified number. Here, the data processing device judges whether the execution of the last application instance in the target workflow instance is completed through the number of applications to be executed and the number of applications in execution.

[0158] In the embodiment of the present application, the data processing device can realize the distributed processing of workflow instances by pushing the target workflow instance into the workflow instance queue to improve the execution efficiency of workflow instances.

[0159] Step 109: Present the form submission result of the target form based on the workflow execution result.

[0160] In the embodiments of the present application, the data processing device may directly use the workflow execution result as the form submission result of the target form, or use the processing result of the workflow execution result as the form submission result. The embodiments of the present application do not limit this; here, it may be determined based on the echo output information in the form configuration information, and the echo output information may indicate that the workflow execution result is the form submission result, or may indicate the processing content of the workflow execution result (for example, displaying the data ranked in the top 3, etc.). Among them, the form submission result refers to the output information after submitting the target form.

[0161] In the embodiments of the present application, after the data processing device outputs the successful orchestration information in response to the second confirmation operation for the target form node and the target workflow, the data processing method further includes: the data processing device first presents a workflow browsing control for the successful orchestration information; then, in response to the workflow browsing operation for the workflow browsing control, presents a workflow list, and presents the target workflow in the workflow list.

[0162] It should be noted that the attributes of the workflow list include at least one of the following: workflow name, form address, creation time, start flag; among them, the start flag is used for form start verification.

[0163] Next, an exemplary application of the embodiments of the present application in an actual application scenario will be described. This exemplary application describes the process of constructing a form and a workflow in a visual manner during the workflow orchestration process, and executing the workflow through the form when the workflow orchestration is completed.

[0164] It should be noted that this exemplary application includes two processes: form creation and form response. Among them, the form response process further includes a workflow instance execution process, which will be described separately below.

[0165] See Figure 7 , Figure 7 is an exemplary workflow creation schematic diagram provided by the embodiments of the present application; as Figure 7 shown, on the interface 7-1, there are displayed a title 7-11 (New Workflow), a selection area 7-12 (referred to as a node selection area), and a configuration area 7-13 (referred to as a workflow orchestration area). The selection area 7-12 includes triggers to be selected 7-121 (referred to as form nodes) and logics, etc.; when a drag operation is performed on the trigger 7-121 in the trigger 7-121 and the trigger 7-121 is dragged to the configuration area 7-13, a form trigger node 7-131 (referred to as a target form node) is presented in the configuration area 7-13.

[0166] When for Figure 7When the form trigger node 7-131 in Figure 8 performs a form configuration operation (referred to as a configuration trigger operation), refer to Figure 8 which is an exemplary form configuration schematic diagram provided by an embodiment of the present application; as Figure 8 shown, in the area 8-12 of the interface 8-1, the form trigger node 7-131 is presented; in the configuration area 8-11 (referred to as the form configuration area) of the interface 8-1, a title 8-111, debug data setting information 8-112, form title setting information 8-113, form description setting information 8-114, form-filling member setting information 8-115, concerned member setting information 8-116, start login state setting information 8-117, echo output setting information 8-118, form definition control 8-119 are presented, and a save and effect button 8-131, a reset button 8-132, a save as button 8-133, and a cancel button 8-134 are also presented.

[0167] It should be noted that the form-filling member setting information 8-115 is used to set the members who fill in the form, that is, the accounts including the form-filling permissions are set; the default is any account. The start login state setting information 8-117 is used to set whether the access to the form judges the login state of the account. If so, an account in the unlogged state cannot access the form.

[0168] When Figure 8 the form definition control 8-119 in Figure 9 is triggered to create a form, refer to Figure 9 which is an exemplary form creation schematic diagram provided by an embodiment of the present application; as Figure 9 shown, the interface 9-1 includes a form item addition area 9-11 (referred to as a form item editing area) and a form preview area 9-12 (referred to as a form presentation area); among them, the form item addition area 9-11 is used for visual configuration of the form, and a control 9-111 for adding form items (referred to as a form item selection control) is presented. The control 9-111 is used to add various form items. As shown in the form item list 9-112, a confirm button 9-113 and a cancel button 9-114 are also presented; the form preview area 9-12 is used to present a form (referred to as a target form) corresponding to at least one form item information added in the form item addition area 9-11, and is also used to present a preview prompt message 9-121.

[0169] It should be noted that the various form items to be added in the form item list 9-112 include the following types: single-line text, multi-line text, number, switch, password, drop-down list, radio, checkbox, single file, multi-file, rich text, date, time, date and time, separator, and hidden field, etc.

[0170] Refer to Figure 10 forFigure 10 is another exemplary form creation schematic diagram provided by an embodiment of the present application; as Figure 10 shown, the interface 10-1 includes a form item addition area 10-11 and a form preview area 10-12; among them, in the form item addition area 10-11, at least one added form information 10-111 and a control 10-112 for adding form items are presented, and a confirmation button 10-113 and a cancellation button 10-114 are also presented; in the form preview area 10-12, at least one form item 10-121 corresponding to at least one form information 10-111 is presented, and a preview prompt message 10-122 is also presented.

[0171] It should be noted that the data structure of each form item can be described by a form item array, and the form item array is "{description attribute (Desc): description attribute value, extension attribute (Extension): extension attribute value, key attribute (Key): key attribute value (for example, 'xx'), label attribute (Label): label attribute value (for example, rich text), required item attribute (Required): required item attribute value (for example, no (False)), type attribute (Type): type attribute value (for example, rich text type (Rich_Text)), value attribute (Value): value attribute value (for example, '\n')}"; among them, the type attribute is used to distinguish the type of the form item; in addition, after each form item is added in the editor, it corresponds to a form item array.

[0172] When the Figure 10 confirmation button 10-113 in is triggered, the form creation is completed. At this time, a form address for accessing the form is generated for the created form, for example, "https: / / xxxx.com / workflow / diversity / form / user-submit / …". Among them, the form address is unique, and the corresponding form can be accessed through the correct form address.

[0173] In an embodiment of the present application, for the created form, the business process for the form processing result can also be configured by dragging.

[0174] See Figure 11 , Figure 11 is another exemplary workflow creation schematic diagram provided by an embodiment of the present application; as Figure 11 shown, in the interface 11-1, the empty operation node under the logical option in the selection area 11-11 is dragged to the configuration area 11-13 to be used as the subsequent business processing of the created form trigger node 11-12.

[0175] After the creation of the entire workflow is completed, the created form workflow (referred to as the target workflow) can be presented in the workflow list.

[0176] See Figure 12 , Figure 12 which is an exemplary schematic diagram of a workflow list provided by an embodiment of the present application; as Figure 12 shown, in interface 12-1, there are presented a workflow management control 12-11 and a workflow list 12-12; each record in the workflow list 12-12 is a workflow, including name, form, time, and whether it is enabled, etc.; among them, workflow 12-121 is the workflow corresponding to Figure 11 .

[0177] Based on Figures 7 to 12 , see Figure 13 , Figure 13 which is an exemplary form creation flowchart provided by an embodiment of the present application; as Figure 13 shown, this exemplary form creation process includes steps 1301 to 1308, and each step will be described separately below.

[0178] Step 1301, start creating a form.

[0179] It should be noted that, as Figure 7 shown, by selecting the form trigger node, the form creation process is started. In addition, starting to create a form is a processing process at the front-end application level.

[0180] Step 1302, start setting the form basic information (referred to as form configuration information).

[0181] It should be noted that, as Figure 8 shown, when the form basic information setting operation is triggered by the form trigger, the processing process of setting the form basic information is started.

[0182] Step 1303, set the form-filling members (referred to as form submission accounts).

[0183] It should be noted that the setting of the form-filling members can be achieved through Figure 8 the form-filling member setting information 8-115 in.

[0184] Step 1304, set the login state (referred to as the login status detection flag).

[0185] It should be noted that the setting of the login state can be achieved through Figure 8 the startup login state setting information 8-117 in.

[0186] Step 1305, set the form structure.

[0187] It should be noted that the setting of the form structure can be achieved by adding Figure 9 the form items shown, and the process of setting the form structure is as Figure 10 shown. Additionally, starting to set the form basic information, setting the form-filling members, setting the login state, and setting the form structure are the processing procedures at the form processing level.

[0188] Step 1306, Orchestrate the form workflow (referred to as the target workflow).

[0189] It should be noted that the orchestration of the form workflow can be achieved through Figure 11 the following.

[0190] Step 1307, Save the form workflow.

[0191] It should be noted that saving the form workflow means storing the orchestrated form workflow; for example, when the button to trigger saving the workflow is received, the process of saving the form workflow is executed.

[0192] Step 1308, Save the mapping relationship between the form address and the form workflow (referred to as the form workflow relationship).

[0193] It should be noted that saving the mapping relationship between the form address and the form workflow means storing the form address and the form workflow correspondingly. Additionally, orchestrating the form workflow, saving the form workflow, and saving the mapping relationship between the form address and the form workflow are the processing procedures at the service orchestration level.

[0194] The following describes the form response process.

[0195] Refer to Figure 14 , Figure 14 which is an exemplary form response flowchart provided by an embodiment of the present application; as Figure 14 shown, this exemplary form response process includes Step 1401 to Step 1417, and each step will be described separately below.

[0196] Step 1401, Start accessing the form.

[0197] It should be noted that in response to the form access request, the requested form is determined to start accessing the form. Among them, starting to access the form is a processing procedure at the front-end application level.

[0198] Step 1402, Form routing.

[0199] It should be noted that form routing means routing to the form address to be accessed according to the requested form. Additionally, form routing is a processing procedure at the form processing level.

[0200] Step 1403: Determine whether the form address is valid (referred to as validity verification). If it is, execute Step 1405; if not, execute Step 1404.

[0201] It should be noted that to determine whether the routed form address exists, if it exists, it is valid; otherwise, it is invalid. Additionally, determining whether the form address is valid is a processing flow at the form processing level.

[0202] Step 1404: Present a prompt indicating that the form address is invalid.

[0203] It should be noted that presenting a prompt indicating that the form address is invalid is a processing flow at the front - end application level.

[0204] Step 1405: Determine whether the form is enabled (referred to as form enabling verification). If it is, execute Step 1407; if not, execute Step 1406.

[0205] It should be noted that determining whether the form is enabled is a processing flow at the front - end application level.

[0206] Step 1406: Present a prompt indicating that the form is not enabled.

[0207] It should be noted that presenting a prompt indicating that the form is not enabled is a processing flow at the form processing level.

[0208] Step 1407: Determine whether the access account is a form - filling member (referred to as access account permission verification). If it is, execute Step 1409; if not, execute Step 1408.

[0209] It should be noted that determining whether the access account is a form - filling member is a processing flow at the form processing level.

[0210] Step 1408: Present a prompt indicating no form - filling permission.

[0211] It should be noted that presenting a prompt indicating no form - filling permission is a processing flow at the front - end application level.

[0212] Step 1409: Obtain the form submission information (referred to as target form information).

[0213] It should be noted that obtaining the form submission information is a processing flow at the form processing level.

[0214] See Figure 15 , Figure 15 which is an exemplary form submission schematic diagram provided by an embodiment of the present application; as Figure 15As shown, in interface 15-1, a title 15-11 and a form 15-12 are presented; when the information input operation is completed for each form item in the form, the submit button 15-13 is triggered, and thus the form submission information is received. A cancel button 15-14 is also presented in interface 15-1.

[0215] Step 1410: Determine whether the form submission information passes the verification. If not, execute step 1411; if so, execute step 1412.

[0216] It should be noted that determining whether the form submission information passes the verification is a processing flow at the form processing level.

[0217] Step 1411: Present a prompt indicating that the form submission information is invalid.

[0218] It should be noted that presenting a prompt indicating that the form submission information is invalid is a processing flow at the front-end application level.

[0219] Step 1412: Determine the corresponding form workflow.

[0220] It should be noted that based on the mapping relationship between the form address and the form workflow, the form workflow corresponding to the form address is determined. Additionally, determining the corresponding form workflow is a processing flow at the service orchestration level.

[0221] Step 1413: Pass the form parameters to the form workflow.

[0222] It should be noted that the form submission information is passed as form parameters into the form workflow to create a workflow instance. Additionally, passing the form parameters to the form workflow is a processing flow at the form processing level.

[0223] Step 1414: Create a workflow instance (referred to as the target workflow instance).

[0224] It should be noted that creating a workflow instance is a processing flow at the service orchestration level. The creation of the workflow instance corresponds to the creation of an Execution record table, and the fields of the Execution record table are shown in Table 1.

[0225] Table 1

[0226]

[0227] Among them, the execution identifier refers to the workflow instance identifier; the process relationship records the process structure of the workflow, so that the execution order of the workflow is determined based on the process relationship. Here, the process relationship includes the start application instance (StartAppInstId), the end application instance (DestAppInstId), and each application structure (App). Among them, the application structure includes the application instance name (App Name), parameter items (Parameters, including parameters, parameter values, parameter types, and parameter descriptions), the application template (Template) adopted by the application instance, the coordinate position (Position) of the application instance on the front-end visual editor canvas, the unique identifier (InstId) representing the application instance in the workflow, the identifier (PrevAppInstIds) of the previous application instance pointed to, the identifier (NextAppInstIds) of the next application instance pointed to, the output result (Output) of the application instance, the error message (Error) when an error occurs during the execution of the application instance, the status (AppInstStatus) of the application instance, the start time (StartTime) of the application instance execution, and the end time (EndTime) of the application instance execution.

[0228] It should be noted that the application structure describes the relevant information of an application. The parameters in the parameter items usually include the variable expressions of the application, and the variable expressions can be path expressions or path expressions with functions; the parameter type is a data type. The application instance identifier corresponds to the application and is used to determine the application. The status of the application instance includes being processed, unprocessed, and processed, etc.

[0229] It should also be noted that the form workflow can be described in a specified language (for example, JSON language), and the described content includes form configuration information and description information of each included application.

[0230] In the embodiment of the present application, the generated execution record table is stored in the database, and the corresponding execution identifier is stored (Pushed) in the execution message queue (denoted as Execution#Queue) so that the back-end distributed workflow engine can execute workflow instances in parallel; that is, the workflow engine obtains the workflow instances to be executed from the execution message queue.

[0231] See Figure 16 , Figure 16 is an exemplary schematic diagram of the execution of a workflow instance provided by the embodiment of the present application; as Figure 16As shown, the execution message queue 16-2 includes workflow instances 16-11 to 16-13, and the workflow instance 16-14 is to be pushed to the execution message queue 16-2; the workflow instances dequeued (Popped) from the execution message queue 16-2 are executed by the workflow engine 16-3; among them, the workflow engine 16-3 is a workflow engine cluster, including multiple containers for executing workflow instances (exemplarily showing containers 16-41 to 16-4M, where M is a positive integer greater than 1).

[0232] Step 1415, execute the workflow instance.

[0233] It should be noted that the execution entity for executing the workflow instance can be the workflow engine.

[0234] See Figure 17 , Figure 17 is an exemplary execution flowchart of a workflow instance provided by an embodiment of the present application; as Figure 17 shown, this exemplary execution process of the workflow instance includes steps 1701 to 1712, and each step will be described separately below.

[0235] Step 1701, parse the workflow instance.

[0236] It should be noted that after the workflow engine obtains the workflow instance to be executed, it sets the status of each application instance in the workflow instance to the to-be-processed status; and parses the workflow instance to obtain the trigger application instance in the workflow instance.

[0237] Step 1702, push the application instance to be executed to the application instance queue.

[0238] It should be noted that the application instance to be executed is the application instance to be enqueued currently, which can be the trigger application instance or an application instance other than the trigger application instance. Each application instance in the application instance queue describes the application instance (AppInst), workflow instance identifier (Execution ID), application instance identifier (AppInst ID), and index. In this way, after the execution of each application instance in the application instance queue is completed, the corresponding workflow instance and the execution result of the application instance can be determined based on this description.

[0239] See Figure 18 , Figure 18 is an exemplary execution schematic diagram of an application instance queue provided by an embodiment of the present application; as Figure 18As shown, the application instance queue 18-2 includes application instances 18-11 to 18-13, and the application instance 18-14 is to be pushed to the application instance queue 18-2; the application instances dequeued from the application instance queue 18-2 are executed by the workflow engine 18-3; among them, the workflow engine 18-3 is a workflow engine cluster, including multiple containers for executing workflow instances (exemplarily shown as containers 18-41 to 18-4N, where N is a positive integer greater than 1).

[0240] Step 1703: Update the status count.

[0241] It should be noted that the status count of the workflow instance is implemented by two variables, the number in the queue (in_queue_count) and the number being executed (running_app_count). See Table 2.

[0242] Table 2

[0243] Variable Description Quantity in queue Quantity of the application instance of the currently executing workflow instance in the application instance queue Quantity in execution Quantity of the executing application instances corresponding to the currently executing workflow instance

[0244] Among them, when both the number in the queue and the number being executed are equal to 0, it indicates that the execution of the currently executed workflow instance ends.

[0245] In the embodiments of the present application, the update operation of the status count is shown in Table 3.

[0246] Table 3

[0247] Variable Operation Quantity in queue Decrease by 1 / Increase by 1 Quantity in execution Increase by 1 / Decrease by 1

[0248] It should be noted that when pushing an application instance into the application instance queue, for the number in the queue, an increment operation is performed; when an application instance dequeues from the application instance queue, for the number in the queue, a decrement operation is performed, and for the number being executed, an increment operation is performed; when the execution of the application instance is completed, for the number being executed, a decrement operation is performed.

[0249] Step 1704: Read the application instance from the application instance queue for execution. Execute Step 1703 and Step 1705.

[0250] Step 1705: Set the status of the read application instance to being executed.

[0251] It should be noted that after the distributed workflow engine obtains the application instance to be processed from the application instance queue, it updates the status corresponding to the application instance to being executed and sets the start execution time.

[0252] See Table 4. Table 4 is the data structure of the application instance provided in the embodiments of the present application.

[0253] Table 4

[0254]

[0255]

[0256] It should be noted that during the execution of a workflow instance, an application is executed at least once; for an application that is executed multiple times, there are multiple execution results corresponding to it [{application instance identifier = x, index = 0}, {application instance identifier = x, index = 1}, …, {application instance identifier = x, index = D}]. The execution result of a specified instance of the application instance can be uniquely confirmed through the application instance identifier and the index field.

[0257] In addition, the data structure of each application instance can be described as "index: 0, maximum index value: 1 application instance: application instance description, parameters: parameter key, parameter value, parameter type, parameter description, template: application template adopted by the application instance, coordinate position of the application instance on the front-end visual editor canvas, unique identifier representing the application instance in the workflow, identifier of the previous application instance pointed to, identifier of the next application instance pointed to, output result of the application instance, error message when an error occurs during the execution of the application instance, status of the application instance, start time of the execution of the application instance, and end time of the execution of the application instance."

[0258] Among them, the index represents the index position of the current App execution record, starting from 0. If a loop is used, the index of the App in the loop body increases sequentially from 0. The maximum index value is used to record the number of times the current App is executed. Here, when obtaining the execution result of the App in the execution instance, since the App may be executed multiple times (loop callback), it is first necessary to obtain the number of times it is executed, that is, the maximum index value, and then sequentially obtain all the execution results of the App according to the application instance identifier and index of the App.

[0259] Step 1706: Parse the parameters in the application instance.

[0260] It should be noted that the parameter types include string type (String), boolean type (Boolean), numerical type (Number), etc. The parameter value can be either a constant (such as a number or a string) or a path syntax expression that references the execution result of an already executed application instance. For example, {<application instance identifier>.data}, {<application instance identifier>.parameter.<parameter value>} (where parameter.<parameter value> is a path syntax expression).

[0261] Since the runtime data of each application instance is stored in the database. To parse the path syntax expressions used in the application instance parameters. First, it is necessary to load the execution data of all application instances under the current workflow instance into memory to form a global data based on the application instance mapping.

[0262] See Figure 19 , Figure 19 is a schematic diagram of the global data of an exemplary application instance provided by an embodiment of the present application; as Figure 19 shown, among application instances 19-1 to 19-L, each application instance corresponds to an input / output data structure (including input data, output data set, start time, end time, running status, and error information, where the output data set includes the full execution result of the application instance).

[0263] It should be noted that the runtime data structure of the workflow refers to the runtime data of the executed application module instances. Here, when the workflow engine executes the workflow, it corresponds to a data structure of a dictionary structure (Map), which is used to store the input data, output data, and exceptions of each application module instance in the workflow, and is a global-level information. It is located through the instance identifier of the App instance, and the input and output data of any App instance in the workflow are globally obtained. Then these path syntax expressions are parsed and replaced with the corresponding data.

[0264] Step 1707: Execute the application instance based on the parsed parameters.

[0265] Step 1708: Store the execution result of the application instance. Then execute Step 1703 and Step 1709.

[0266] It should be noted that when the execution of the application instance is completed and the execution result of the application instance is obtained, the execution result of the application instance is stored in the database. Then, by subtracting 1 from the number of executions in progress, variable update is achieved.

[0267] Step 1709: Determine whether there is a next application instance. If so, execute 1702; if not, execute Step 1710.

[0268] Step 1710: Determine whether the status count meets the end condition. If so, execute 1711; if not, execute Step 1704.

[0269] It should be noted that if the number in the execution instance queue and the number of executions in progress are not all equal to 0, continue to consume the application instances in the application instance queue. If the status counts are all equal to 0, the execution instance ends, starts to clear the running caches of each application instance, and sets the execution instance status to the completed status.

[0270] Step 1711: Clear the caches of each application instance.

[0271] It should be noted that after the execution of each application instance in the workflow instance is completed, the caches occupied by each application instance are cleared. For example, the execution results of cache clearing, etc.

[0272] Step 1712: Update the execution status of the workflow instance.

[0273] It should be noted that after the execution of each application instance in the workflow instance is completed, it indicates that the execution of the workflow instance has been completed. Thus, the execution status of the workflow instance is updated to the completed status, and the data in the execution table in the database is updated.

[0274] Step 1416: Obtain the execution result of the workflow instance.

[0275] It should be noted that obtaining the execution result of the workflow instance is a processing flow at the front-end application level.

[0276] Step 1417: Output the execution result.

[0277] It should be noted that outputting the execution result is a processing flow at the front-end application level.

[0278] It can be understood that when orchestrating a workflow and building a form based on low-code visualization, it can reduce the complexity and difficulty of form development, reduce the time and workload of writing code, and improve development efficiency. It can also intuitively display the layout and style of the form, enhancing the flexibility and maintainability of form adjustment. Additionally, building a form based on low-code visualization encapsulates form components to form a reusable component library, which can improve reusability. Furthermore, building a form based on low-code visualization can customize components and plugins, enhancing scalability.

[0279] The following continues to describe the exemplary structure of the software module for the data processing device 455 provided in the embodiments of the present application. In some embodiments, as Figure 2 shown, the software modules stored in the data processing device 455 in the memory 450 may include:

[0280] A node selection module 4551, configured to present a node selection area and a workflow orchestration area, and in response to a node selection operation of moving a form node in the node selection area to the workflow orchestration area, present the selected target form node in the workflow orchestration area, where the target form node is used to trigger the execution of the workflow;

[0281] A form construction module 4552, configured to present form item selection controls and a form presentation area in response to a form construction operation for the target form node;

[0282] The form building module 4552 is further configured to present, in the form presentation area, a target form constructed by at least one selected form item in response to a form item selection operation on the form item selection control.

[0283] The node selection module 4551 is further configured to present a target workflow triggered by the target form node in response to a first confirmation operation on the target form.

[0284] The orchestration processing module 4553 is configured to output an orchestration success message in response to a second confirmation operation on the target form node and the target workflow.

[0285] In an embodiment of the present application, the form item selection control is presented in a form item editing area; the form building module 4552 is further configured to present, in the form item editing area, information of at least one selected form item in response to the form item selection operation on the form item selection control, where the form item information includes at least one of the following: form item description, extended information, form item label, form item type, required flag, type label, form value; and present, in the form presentation area, the target form constructed by at least one of the form items, where at least one of the form items corresponds to at least one of the form item information one by one.

[0286] In an embodiment of the present application, the node selection module 4551 is further configured to present the node selection area and the workflow orchestration area including the target form node in response to a form confirmation operation on the target form; and present, in the workflow orchestration area, a target workflow triggered by the target form node in response to a node addition operation performed on the target form node in the node selection area, where the first confirmation operation includes the form confirmation operation and the node addition operation.

[0287] In an embodiment of the present application, the node selection module 4551 is further configured to present at least one selected workflow node in the workflow orchestration area.

[0288] In an embodiment of the present application, the node selection module 4551 is further configured to, in response to a form confirmation operation for the target form, present the node selection area and the workflow orchestration area including the target form node and at least one of the workflow nodes; in response to a node addition operation for the node selection area, present, in the workflow orchestration area, the target workflow triggered by the target form node, where the target workflow includes at least one of the workflow nodes and one or more workflow nodes added by the node addition operation; or, in response to the form confirmation operation for the target form, present the node selection area and the workflow orchestration area, and present, in the workflow orchestration area, the target form node and the target workflow constructed by at least one of the workflow nodes triggered by the target form node.

[0289] In an embodiment of the present application, the data processing device 455 further includes a form response module 4554, configured to, in response to a form access request, present the target form; in response to a form submission operation for the target form, obtain target form information; execute the target workflow based on the target form information to obtain a workflow execution result; and present a form submission result of the target form based on the workflow execution result.

[0290] In an embodiment of the present application, the form response module 4554 is further configured to, in response to the form access request, obtain form access information, where the form access information includes one or both of a target form identifier and an access account; perform access verification based on the form access information to obtain an access verification result, where the access verification includes at least one of the following: validity verification of a form address corresponding to the target form identifier, access account permission verification, form opening verification, and access account login status verification; and present the target form when the access verification result indicates that the access verification is passed.

[0291] In an embodiment of the present application, the orchestration processing module 4553 is further configured to, in response to a second confirmation operation for the target form node and the target workflow, store the target form and the target workflow correspondingly to obtain a form-workflow relationship between the form and the workflow, and present the orchestration success information.

[0292] In an embodiment of the present application, the form response module 4554 is further configured to determine the target workflow corresponding to the target form based on the form-workflow relationship; instantiate the target workflow into a target workflow instance based on the target form information; and execute the target workflow instance to obtain the workflow execution result.

[0293] In an embodiment of the present application, the form response module 4554 is further configured to parse the target workflow instance to obtain an application instance execution order and an application instance set, where each application instance in the application instance set is an instance result of an application corresponding to a workflow node in the target workflow; based on the application instance execution order and the application instance set, iteratively perform the following processes: determine a to-be-executed application instance from the application instance set based on the application instance execution order; execute the to-be-executed application instance to obtain an application execution result; when the to-be-executed application instance is the last to-be-executed application instance, end the iteration, and determine the application execution result obtained at the end of the iteration as the workflow execution result.

[0294] In an embodiment of the present application, the form response module 4554 is further configured to, in response to the process of pushing the to-be-executed application instance to the application instance queue, perform an increase process on the to-be-executed quantity; in response to the process of obtaining the to-be-executed application instance from the application instance queue, perform a decrease process on the to-be-executed quantity and perform an increase process on the in-execution quantity; in response to the obtaining of the application execution result, perform a decrease process on the in-execution quantity; when the to-be-executed quantity is a first specified quantity and the in-execution quantity is a second specified quantity, determine that the to-be-executed application instance is the last application instance.

[0295] In an embodiment of the present application, the form response module 4554 is further configured to determine a reference application instance and a reference execution index of the to-be-executed application instance; combine the reference application instance and the reference execution index to obtain a target execution result from an execution result set, where the execution result set includes each execution result of each executed application instance in the target workflow instance; execute the to-be-executed application instance based on the target execution result to obtain the application execution result; store the to-be-executed application instance, the current execution index of the to-be-executed application instance, and the application execution result in the execution result set in a corresponding manner.

[0296] In an embodiment of the present application, the data processing device 455 further includes a form configuration module 4555, configured to present a form configuration area in response to a configuration trigger operation for the target form node; present form configuration information in response to a form configuration operation performed in the form configuration area, where the form configuration information includes at least one of the following: test data, form title, form description, form submission account, form associated account, login status detection flag, and echo output information; present the form item selection control and the form presentation area in response to a configuration confirmation operation for the form configuration information, where the form construction operation includes the configuration trigger operation, the form configuration operation, and the configuration confirmation operation.

[0297] In an embodiment of the present application, the data processing device 455 further includes a list presentation module 4556, which is configured to present a workflow browsing control for the successful orchestration information; in response to a workflow browsing operation on the workflow browsing control, present a workflow list, where the attributes of the workflow list include at least one of the following: workflow name, form address, creation time, start flag; present the target workflow in the workflow list.

[0298] An embodiment of the present application provides a computer program product, which includes computer-executable instructions or a computer program. The computer-executable instructions or the computer program are stored in a computer-readable storage medium. A processor of a data processing device reads the computer-executable instructions or the computer program from the computer-readable storage medium, and the processor executes the computer-executable instructions or the computer program, so that the data processing device executes the data processing method described above in the embodiments of the present application.

[0299] An embodiment of the present application provides a computer-readable storage medium, in which computer-executable instructions or a computer program are stored. When the computer-executable instructions or the computer program are executed by a processor, the processor will be caused to execute the data processing method provided in the embodiments of the present application. For example, Figure 3 the data processing method shown.

[0300] In some embodiments, the computer-readable storage medium may be a memory such as FRAM, ROM, flash memory, magnetic surface memory, optical disc, or CD-ROM; or may be various devices including one or any combination of the above memories.

[0301] In some embodiments, the computer-executable instructions may be in the form of a program, software, software module, script, or code, and may be written in any form of programming language (including compiled or interpreted languages, or declarative or procedural languages), and may be deployed in any form, including being deployed as an independent program or being deployed as a module, component, subroutine, or other unit suitable for use in a computing environment.

[0302] As an example, the computer-executable instructions may or may not correspond to a file in a file system, and may be stored as part of a file that stores other programs or data. For example, stored in one or more scripts in a Hyper Text Markup Language (HTML) document, stored in a single file dedicated to the program being discussed, or stored in multiple cooperating files (for example, files that store one or more modules, subroutines, or code portions).

[0303] As an example, the computer-executable instructions can be deployed to execute on one electronic device (in this case, this one electronic device is the data processing device), or to execute on multiple electronic devices located at one location (in this case, the multiple electronic devices located at one location are the data processing device), or, to execute on multiple electronic devices distributed at multiple locations and interconnected by a communication network (in this case, the multiple electronic devices distributed at multiple locations and interconnected by a communication network are the data processing device).

[0304] It can be understood that in the embodiments of the present application, regarding data related to operations and the like, when the embodiments of the present application are applied to specific products or technologies, user permission or consent needs to be obtained, and the collection, use, and processing of relevant data need to comply with relevant laws, regulations, and standards, conform to the principles of legality, propriety, and necessity, do not involve obtaining data types prohibited or restricted by laws and regulations, and do not interfere with the normal operation of the target website.

[0305] In summary, in the process of constructing a workflow in the embodiments of the present application, when the selected target form node is presented in the workflow orchestration area, by triggering the form construction operation on the target form node, the form item selection control and the form presentation area can be presented; and since the form item selection control is used to select form items, the form presentation area is used to present at least one selected form item, and the at least one selected form item is used to construct the target form; therefore, the construction of the target form can be achieved through visual operations, and further, based on the constructed form to construct the workflow, the construction efficiency of the workflow can be improved.

[0306] The above description is only for the embodiments of the present application and is not intended to limit the protection scope of the present application. Any modifications, equivalent replacements, and improvements made within the spirit and scope of the present application are all included in the protection scope of the present application.

Claims

1. A data processing method, characterized in that, The method includes: Presenting a node selection area and a workflow orchestration area, and in response to a node selection operation of moving a form node in the node selection area to the workflow orchestration area, presenting the selected target form node in the workflow orchestration area, where the target form node is used to trigger the execution of a workflow; In response to a form construction operation on the target form node, presenting a form item selection control and a form presentation area; In response to a form item selection operation on the form item selection control, presenting a target form constructed by at least one selected form item in the form presentation area; In response to a first confirmation operation on the target form, presenting the target workflow triggered by the target form node; In response to a second confirmation operation on the target form node and the target workflow, outputting an orchestration success message.

2. The method according to claim 1, characterized in that The form item selection control is presented in a form item editing area; The presenting, in the form presentation area, a target form constructed by at least one selected form item in response to a form item selection operation on the form item selection control includes: In response to the form item selection operation on the form item selection control, presenting information of at least one selected form item in the form item editing area, where the form item information includes at least one of the following: form item description, extended information, form item label, form item type, mandatory flag, type label, form value; In the form presentation area, presenting the target form constructed by at least one of the form items, where at least one of the form items corresponds one-to-one with at least one of the form item information.

3. The method according to claim 1, characterized in that, The presenting, in response to a first confirmation operation on the target form, the target workflow triggered by the target form node includes: In response to a form confirmation operation on the target form, presenting the node selection area and the workflow orchestration area including the target form node; In response to a node addition operation performed on the target form node in the node selection area, presenting the target workflow triggered by the target form node in the workflow orchestration area, where the first confirmation operation includes the form confirmation operation and the node addition operation.

4. The method according to claim 1, wherein After presenting the selected target form node in the workflow orchestration area, the method further includes: Presenting at least one selected workflow node in the workflow orchestration area; The presenting, in response to a first confirmation operation on the target form, the target workflow triggered by the target form node includes: In response to a form confirmation operation on the target form, presenting the node selection area and the workflow orchestration area including the target form node and at least one of the workflow nodes; in response to a node addition operation on the node selection area, presenting the target workflow triggered by the target form node in the workflow orchestration area, where the target workflow includes at least one of the workflow nodes and one or more workflow nodes added by the node addition operation; Alternatively, in response to the form confirmation operation for the target form, the node selection area and the workflow orchestration area are presented, and the target form node and the target workflow constructed by at least one of the workflow nodes triggered by the target form node are presented in the workflow orchestration area.

5. The method according to any one of claims 1 to 4, characterized in that, After outputting the successful orchestration information in response to the second confirmation operation for the target form node and the target workflow, the method further includes: In response to a form access request, presenting the target form; In response to a form submission operation for the target form, obtaining target form information; Executing the target workflow based on the target form information to obtain a workflow execution result; Based on the workflow execution result, presenting the form submission result of the target form.

6. The method according to claim 5, wherein The presenting the target form in response to a form access request includes: In response to the form access request, obtaining form access information, where the form access information includes one or both of a target form identifier and an access account; Performing access verification based on the form access information to obtain an access verification result, where the access verification includes at least one of the following: validity verification of the form address corresponding to the target form identifier, access account permission verification, form opening verification, and access account login status verification; When the access verification result indicates that the access verification is passed, presenting the target form.

7. The method according to claim 5, wherein The outputting the successful orchestration information in response to the second confirmation operation for the target form node and the target workflow includes: In response to the second confirmation operation for the target form node and the target workflow, correspondingly storing the target form and the target workflow to obtain a form-workflow relationship between the form and the workflow, and presenting the successful orchestration information; The executing the target workflow based on the target form information to obtain a workflow execution result includes: Determining the target workflow corresponding to the target form based on the form-workflow relationship; Instantiating the target workflow into a target workflow instance based on the target form information; Executing the target workflow instance to obtain the workflow execution result.

8. The method according to claim 7, wherein The executing the target workflow instance to obtain the workflow execution result includes: Parsing the target workflow instance to obtain an application instance execution order and an application instance set, where each application instance in the application instance set is an instance result of an application corresponding to a workflow node in the target workflow; Based on the application instance execution order and the application instance set, iteratively performing the following processing: Based on the application instance execution order, determining a to-be-executed application instance from the application instance set; Executing the to-be-executed application instance to obtain an application execution result; When the to-be-executed application instance is the last to-be-executed application instance, the iteration ends, and the application execution result obtained at the end of the iteration is determined as the workflow execution result.

9. The method according to claim 8, wherein After determining the to-be-executed application instance from the application instance set based on the execution order of the application instances, the method further includes: In response to the process of pushing the to-be-executed application instance to the application instance queue, performing an increment process on the number of to-be-executed instances; In response to the process of obtaining the to-be-executed application instance from the application instance queue, performing a decrement process on the number of to-be-executed instances and performing an increment process on the number of instances in execution; After executing the to-be-executed application instance and obtaining an application execution result, the method further includes: In response to obtaining the application execution result, performing a decrement process on the number of instances in execution; When the number of to-be-executed instances is the first specified number and the number of instances in execution is the second specified number, determining that the to-be-executed application instance is the last application instance.

10. The method according to claim 8, wherein Executing the to-be-executed application instance and obtaining an application execution result includes: Determining the referenced application instance and the reference execution index of the to-be-executed application instance; Combining the referenced application instance and the reference execution index to obtain a target execution result from an execution result set, where the execution result set includes each execution result of each executed application instance in the target workflow instance; Executing the to-be-executed application instance based on the target execution result to obtain the application execution result; After executing the to-be-executed application instance and obtaining an application execution result, the method further includes: Correspondingly storing the to-be-executed application instance, the current execution index of the to-be-executed application instance, and the application execution result into the execution result set.

11. The method according to any one of claims 1 to 4, characterized in that Responding to the form construction operation for the target form node and presenting a form item selection control and a form presentation area includes: Responding to the configuration trigger operation for the target form node and presenting a form configuration area; Responding to the form configuration operation performed in the form configuration area and presenting form configuration information, where the form configuration information includes at least one of the following: test data, form title, form description, form submission account, form associated account, login status detection flag, and echo output information; Responding to the configuration confirmation operation for the form configuration information and presenting the form item selection control and the form presentation area, where the form construction operation includes the configuration trigger operation, the form configuration operation, and the configuration confirmation operation.

12. The method according to any one of claims 1 to 4, characterized in that, After outputting an orchestration success message in response to the second confirmation operation for the target form node and the target workflow, the method further includes: Presenting a workflow browsing control for the orchestration success message; Responding to the workflow browsing operation for the workflow browsing control and presenting a workflow list, where the attributes of the workflow list include at least one of the following: workflow name, form address, creation time, start flag; Presenting the target workflow in the workflow list.

13. A data processing device, characterized in that, The data processing device includes: A node selection module, configured to present a node selection area and a workflow orchestration area, and in response to a node selection operation of moving a form node in the node selection area to the workflow orchestration area, present the selected target form node in the workflow orchestration area, wherein the target form node is used to trigger the execution of a workflow; A form construction module, configured to present form item selection controls and a form presentation area in response to a form construction operation on the target form node; The form construction module is further configured to present a target form constructed by at least one selected form item in the form presentation area in response to a form item selection operation on the form item selection control; The node selection module is further configured to present a target workflow triggered by the target form node in response to a first confirmation operation on the target form; An orchestration processing module, configured to output an orchestration success message in response to a second confirmation operation on the target form node and the target workflow.

14. An electronic device for data processing, characterized in that, The electronic device includes: A memory, configured to store computer-executable instructions or computer programs; A processor, configured to implement the data processing method according to any one of claims 1 to 12 when executing the computer-executable instructions or computer programs stored in the memory.

15. A computer-readable storage medium storing computer-executable instructions or a computer program, characterized in that, When the computer-executable instructions or computer programs are executed by the processor, the data processing method according to any one of claims 1 to 12 is implemented.

16. A computer program product, comprising computer-executable instructions or a computer program, characterized in that, When the computer-executable instructions or computer programs are executed by the processor, the data processing method according to any one of claims 1 to 12 is implemented.

Images