Event execution process creation method and device, equipment, medium and product

Abstract

The invention discloses an event execution process creation method and device, equipment, a medium and a product. The method comprises the steps of obtaining a plurality of process nodes on an event execution process in response to an operation of triggering and creating the event execution process by a user; for a process node of the event execution process, creating a node control corresponding to the process node; acquiring node data corresponding to the node control; the node data comprises a control name, a control type, input data, output data and a precursor control name; storing the node data in a storage space corresponding to the node control according to a preset format; according to the input data, the output data and the precursor control name corresponding to each node control, determining a calling relationship between different node controls; and associating each node control based on the calling relationship to generate an event execution process. According to the embodiment of the invention, the low-code data platform is flexibly arranged, the data processing capability is improved, and the low-code data development accuracy is improved.

Description

Technical Field

[0001] The present application belongs to the technical field of data development, and in particular, relates to a method, device, equipment, medium and product for creating an event execution process. Background Art

[0002] A low-code data platform is a platform that develops applications in a visual way. It allows professionals who have no programming experience but are familiar with the business to complete application development through a graphical user interface using drag-and-drop components.

[0003] At present, in the process of using low-code data platforms for application development, for scenarios of multi-person collaboration, parallel development, or maintenance of multiple versions, the low-code data platform's logical definition of each component is not perfect, resulting in inflexibility in the low-code data development orchestration, affecting the ability to process data and reducing the accuracy of low-code data development. Summary of the invention

[0004] The embodiments of the present application provide an event execution process creation method, device, equipment, medium and product, which can flexibly orchestrate the low-code data platform, improve data processing capabilities, and improve the accuracy of low-code data development.

[0005] On the one hand, an embodiment of the present application provides a method for creating an event execution process, the method comprising:

[0006] In response to a user's operation of triggering creation of an event execution process, a plurality of process nodes on the event execution process are obtained;

[0007] For a process node of the event execution process, create a node control corresponding to the process node;

[0008] Obtain node data corresponding to the node control; the node data includes control name, control type, input data, output data and predecessor control name;

[0009] Storing the node data in a storage space corresponding to the node control according to a preset format;

[0010] Determine the calling relationship between different node controls according to the input data, output data and predecessor control name corresponding to each node control;

[0011] Based on the calling relationship, each of the node controls is associated to generate an event execution process.

[0012] Optionally, when the node control is a target type control, the predecessor control name in the node data of the node control is empty;

[0013] The target type control is the starting control, or the first operation control in the process branch.

[0014] Optionally, the node data also includes a control attribution name, and the control attribution name is used to indicate that the process node corresponding to the node control belongs to the process branch corresponding to the branch process name.

[0015] Optionally, the node data also includes a control branch name, and the control branch name is used to indicate that the node control belongs to a process sub-branch of the process branch.

[0016] Optionally, storing the node data in a storage space corresponding to the node control in a preset format includes:

[0017] Obtain at least one element in the node data;

[0018] For each element, perform data parsing on the element to obtain a first keyword of the element and a first value corresponding to the keyword;

[0019] Performing type analysis on the first value based on the first keyword to obtain a field type corresponding to the first value;

[0020] Generate a key-value table based on the field type and the first value;

[0021] The key-value table is stored in a storage space corresponding to the node control according to a preset format.

[0022] Optionally, the key-value table includes a first key-value table, and generating the key-value table based on the field type and the first value includes:

[0023] In a case where the field type of the first value is determined to be a basic type, determining the field name corresponding to the element as a second keyword, and determining the first value as a second value corresponding to the second keyword;

[0024] A first key-value table is generated based on the second keyword and the second value.

[0025] Optionally, the key-value table includes a second key-value table, and generating the key-value table based on the field type and the first value includes:

[0026] In the case where the field type is determined to be an object type, determining an internal element type corresponding to the element as a filler object of the element, the internal element type indicating a field type of the internal sub-element, the element including at least one sub-element;

[0027] In the case where the field types of the filling objects are all determined to be basic types, the field names corresponding to the field types of the filling objects are determined as the third keywords, and the values ​​corresponding to the filling objects are determined as the third values ​​corresponding to the third keywords;

[0028] The second key-value table is generated based on the third keyword and the third value.

[0029] Optionally, the key-value table includes a third key-value table, and generating the key-value table based on the field type and the first value includes:

[0030] In the case where the field type is an array type and the element includes multiple sub-elements, determining the field type of each sub-element;

[0031] In the case where the field types of the multiple sub-elements are all determined to be the basic type, the field name corresponding to the element is determined as the fourth keyword, and the field type corresponding to the multiple sub-elements is used as the fourth value to generate a third key value table of the element;

[0032] The storing the key-value table in a storage space corresponding to the node control according to a preset format includes:

[0033] The third key-value table is stored in a position in the queue corresponding to the fourth keyword until each sub-element in the queue is stored with a corresponding third key-value table.

[0034] On the other hand, an embodiment of the present application provides an event execution process creation device, the device comprising:

[0035] An acquisition module, used for acquiring multiple process nodes on the event execution process in response to a user's triggering operation of creating an event execution process;

[0036] A creation module, used for creating a node control corresponding to a process node of the execution process;

[0037] The acquisition module is also used to acquire the node data corresponding to the node control; the node data includes the control name, control type, input data, output data and the predecessor control name;

[0038] A storage module, used to store the node data in a storage space corresponding to the node control according to a preset format;

[0039] A determination module, used to determine the calling relationship between different node controls according to the input data, output data and predecessor control name corresponding to each node control;

[0040] The association module is used to associate each of the node controls based on the calling relationship to generate an event execution process.

[0041] In another aspect, an embodiment of the present application provides an electronic device, the device comprising: a processor and a memory storing computer program instructions;

[0042] When the processor executes the computer program instructions, the event execution process creation method as described in the first aspect is implemented.

[0043] On the other hand, an embodiment of the present application provides a computer storage medium, on which computer program instructions are stored. When the computer program instructions are executed by a processor, the event execution process creation method described in the first aspect is implemented.

[0044] On the other hand, an embodiment of the present application provides a computer program product. When the instructions in the computer program product are executed by a processor of an electronic device, the electronic device executes the event execution process creation method as described in the first aspect.

[0045] The event execution process creation method, device, equipment, medium and product of the embodiments of the present application, when a user creates an event execution process on a low-code platform, obtains the process nodes on the event execution process, and in each process node, a corresponding node control is required to implement the data execution action, that is, the node data of each node control is stored in the corresponding storage space according to a preset format, and then the calling relationship between different node controls is determined through different node data to generate an event execution process, so that users can flexibly create event execution processes and improve the data processing capabilities of event execution processes, thereby improving the accuracy of low-code data development. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0047] Figure 1 It is a flowchart of a method for creating an event execution process provided by an embodiment of the present application;

[0048] Figure 2 This is an example diagram of an event execution process provided by an embodiment of the present application;

[0049] Figure 3 is an example diagram of a starting control provided by an embodiment of the present application;

[0050] Figure 4 is an example diagram of an operation control provided by an embodiment of the present application;

[0051] Figure 5 is a structural diagram of an event execution process creation device provided by another embodiment of the present application;

[0052] Figure 6 It is a structural diagram of an electronic device provided by yet another embodiment of the present application. DETAILED DESCRIPTION

[0053] The features and exemplary embodiments of various aspects of the present application will be described in detail below. In order to make the purpose, technical solutions and advantages of the present application clearer, the present application will be further described in detail below in conjunction with the accompanying drawings and specific embodiments. It should be understood that the specific embodiments described herein are only intended to explain the present application, rather than to limit the present application. For those skilled in the art, the present application can be implemented without the need for some of these specific details. The following description of the embodiments is only to provide a better understanding of the present application by illustrating the examples of the present application.

[0054] It should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the statement "include..." do not exclude the existence of other identical elements in the process, method, article or device including the elements.

[0055] In order to solve the problems of the prior art, the embodiments of the present application provide a method, device, equipment, medium and product for creating an event execution process.

[0056] When users create an event execution process on a low-code platform, they obtain the process nodes on the event execution process, and in each process node, a corresponding node control is required to implement the data execution action, that is, the node data of each node control is stored in the corresponding storage space according to a preset format, and then the calling relationship between different node controls is determined through different node data to generate an event execution process, so that users can flexibly create event execution processes and improve the data processing capabilities of event execution processes, thereby improving the accuracy of low-code data development.

[0057] The following first introduces the event execution process creation method provided in the embodiment of the present application.

[0058] Figure 1 FIG. 1 is a flow chart showing a method for creating an event execution process according to an embodiment of the present application. Figure 1 As shown, the event execution process creation method may include S101-S106:

[0059] S101, in response to a user's operation of triggering creation of an event execution process, a plurality of process nodes on the event execution process are obtained.

[0060] In this embodiment, when the user uses the low-code data platform to create an event execution process, due to the limitations of the low-code platform, there are multiple process nodes in the event execution process, and the multiple process nodes may involve different sub-processes, or involve the same process node. Therefore, when obtaining multiple process nodes in the event execution process, it is also necessary to arrange each process node according to the execution order of the event execution process according to the flowchart pre-entered by the user. So that it is more convenient to generate the event execution process on the low-code data platform later.

[0061] S102, for a process node of the execution process, create a node control corresponding to the process node.

[0062] In this embodiment, after the process nodes are obtained as mentioned above, in order to automatically generate the event execution process so that the low-code platform can automatically output the time execution process, it is necessary to create a node control in the low-code data platform for each process node, so as to form an execution carrier of the event execution process through the node control, thereby facilitating the execution of the event execution process.

[0063] S103, obtaining node data corresponding to the node control.

[0064] In this embodiment, as an example, the node data includes a control name, a control type, input data, output data, and a predecessor control name.

[0065] In some embodiments, there are different types of node controls for an event execution process, wherein the types of node controls include start controls and operation controls. The start control corresponds to the start node in the event execution process, that is, a trigger node in an event execution process. When the start control starts working, it means that the event execution process starts at this time. The operation control corresponds to other process nodes in the event execution process except the start node, so as to realize the entire execution process of the event execution process.

[0066] Reference Figure 2 , Figure 2 This is an example diagram of an event execution process, in which the node control corresponding to the timer is the starting control, and all other node controls are operation controls.

[0067] S104, storing the node data in a storage space corresponding to the node control according to a preset format.

[0068] In some embodiments, for each node control, the corresponding node data input by the user can be obtained, that is, the control name, control type, input data, output data and predecessor control name are obtained, where the value of the control name is of String type, which is the unique identifier of the control in an event execution process, the value of the control type is of String type, which is used to indicate the control type, the input data uses input_param as the key, and the value is of Object type, which is used to indicate the input parameters of the node control; the output data uses output_param as the key, and the value is of Object type, which is used to indicate what output data the node control has; the predecessor control name uses run_after as the key, and the value is of String type, which is used to identify the name of the previous control of the node control.

[0069] In some other embodiments, when the node control is a target type control, the predecessor control name in the node data of the node control is empty;

[0070] The target type control is the starting control, or the first operation control in a process branch.

[0071] In this embodiment, when a node control is a starting control, there is no predecessor control for the node control, so the name of the predecessor control of the node control is empty.

[0072] In addition, when the event execution process includes a process branch, for the first node control of the process branch, the node control does not have a predecessor control on the process branch, so the predecessor control name of the node control needs to be set to empty.

[0073] In some embodiments, the node data also includes a control attribution name, and the control attribution name is used to indicate that the process node corresponding to the node control belongs to the process branch corresponding to the branch process name.

[0074] As an example, the control belonging name uses belong_to as the key and the value is of String type, which is used to identify which control containing the sub-branch process the control belongs to. If it does not belong to the sub-branch process of other controls, the field is blank (null) or not filled in.

[0075] In some other embodiments, the node data also includes a control branch name, and the control branch name is used to indicate that the node control belongs to a process sub-branch of the process branch.

[0076] As an example, the control belongs to the branch name using nest_to as the key, the value is of String type, which is used to identify which branch of the control containing the sub-branch process the control belongs to. If the control belongs to a branch, the control name must not be null.

[0077] Reference Figure 3 and Figure 4 , Figure 3 This is an example diagram of the node data of the timer. Figure 4 This is an example diagram of node data for log control-2.

[0078] In some embodiments, S104 may include:

[0079] Get at least one element in the node data;

[0080] For each element, perform data analysis on the element to obtain the first keyword of the element and its corresponding first value;

[0081] Performing type analysis on the first value based on the first keyword to obtain a field type corresponding to the first value;

[0082] Generate a key-value table based on the field type and the first value;

[0083] The key-value table is stored in the storage space corresponding to the node control according to the preset format.

[0084] In this embodiment, since the low-code data platform usually stores node data in JSON format, the JSON format includes three types of field formats, namely string type, number type, Boolean type, array type, object type and blank type, among which string type, number type and Boolean type are basic types, and array type and object type are composite types.

[0085] When storing node data in the corresponding storage space, it is first necessary to parse the data for each element in the node data to obtain the first keyword and its corresponding first value, that is, the original key-value pair, and then determine the field type corresponding to the first value in the element through the first keyword, generate a key-value table for the field type and the first value, and then store the node data in the storage space in the form of a key-value table.

[0086] For example, the first keyword is: name, and the first value is watermelon. At this time, the field type corresponding to the first keyword is string type, and the corresponding key-value table is name-string. Storing the key-value table in the corresponding storage space is not only convenient for storage, but also when generating the event execution process, it can also call the data of other node controls through different keywords, thereby accurately generating the event execution process.

[0087] In some other embodiments, the key-value table includes a first key-value table, and generating the key-value table based on the field type and the first value includes:

[0088] In the case where the field type of the first value is determined to be the basic type, the field name corresponding to the element is determined as the second keyword, and the first value is determined to be the second value corresponding to the second keyword;

[0089] A first key-value table is generated based on the second keyword and the second value.

[0090] In this embodiment, since each element may be a different character type, different key value tables need to be generated for different field types. When the field type corresponding to the first value is the basic type, it is necessary to determine the field name corresponding to the element as the second keyword, and then determine the first value as the second value, and then generate a first key value table to store the first key value table.

[0091] For example, the first keyword is name, and the first value is watermelon. The field type corresponding to the first keyword is string type, and the corresponding key-value table is name-string. The key-value table is stored in the corresponding storage space.

[0092] In another embodiment, the key-value table includes a second key-value table, and generating the key-value table based on the field type and the first value includes:

[0093] In the case where the field type is determined to be an object type, the internal element type corresponding to the element is determined to be a filler object of the element, the internal element type represents the field type of the internal sub-element, and the element includes at least one sub-element;

[0094] In the case where the field types of the filling objects are all determined to be basic types, the field names corresponding to the field types of the filling objects are determined as the third keywords, and the values ​​corresponding to the filling objects are determined as the third values ​​corresponding to the third keywords;

[0095] A second key-value table is generated based on the third keyword and the third value.

[0096] In this embodiment, when the field type is an object type, since the object type is a composite type, multiple types are nested in the element, so it is necessary to determine the fill object of the element, and then repeat data parsing of the fill object until all fill objects are of the basic type, and then determine the numerical value corresponding to the fill object as the third numerical value, and determine the field type corresponding to the fill object as the third keyword, thereby generating a second key value table, and then storing the second key value table in the corresponding storage space.

[0097] In some other embodiments, the key-value table may further include a third key-value table. Generating the key-value table based on the field type and the first value may include:

[0098] When the field type is an array type and the element includes multiple sub-elements, determine the field type of each sub-element;

[0099] In the case where the field types of multiple sub-elements are all determined to be the basic type, the field name corresponding to the element is determined as the fourth keyword, and the field types corresponding to the multiple sub-elements are used as the fourth value to generate a third key value table of the element;

[0100] Storing the key-value table in the preset format to the storage space corresponding to the node control includes:

[0101] The third key-value table is stored in the position corresponding to the fourth keyword in the queue until each sub-element in the queue is stored with the corresponding third key-value table.

[0102] In this embodiment, when the field type of an element is an array type, the element includes multiple sub-elements, that is, the element is a set of series, so data parsing is required for each sub-element in the series. When the field types corresponding to all sub-elements are basic types, the field name corresponding to the element is determined as the fourth keyword, and the field type corresponding to the sub-element is the fourth numerical value, thereby generating a third part-time job table, storing the third part-time job table at the position corresponding to the fourth keyword, and storing the third key-value table corresponding to each sub-element.

[0103] For example: the element name is fruitlist, which includes three sub-elements, namely name, price and discount. The fourth value corresponding to name is watermelon, the fourth value corresponding to price is 3, and the fourth value corresponding to discount is 7. At this time, the third key-value table is fruitlist[name: string; price: number; discount: number], and then the third key-value table is stored in the corresponding storage space.

[0104] S105, determining the calling relationship between different node controls according to the input data, output data and predecessor control name corresponding to each node control.

[0105] In this embodiment, after the corresponding node data is stored in the storage space, since the node data determines the data that can be called and the data that can be output by the node, the calling relationship between different node controls can be determined based on the input data and output data, so that the node controls can be automatically arranged according to the event execution process to improve the event execution process.

[0106] In some other embodiments, the output data of each node control can be determined as the output data of the node control before calling the process node, so as to facilitate the determination of the calling relationship.

[0107] In some other embodiments, the input data of each node control may reference the output data of the forward control as the input data of the node control to obtain real-time node data.

[0108] S106, associating each node control based on the calling relationship to generate an event execution process.

[0109] In this embodiment, after the call relationship is obtained, each node control is associated so that the process node corresponding to each node control is associated according to the event execution process created by the user to generate an event execution process.

[0110] When users create an event execution process on a low-code platform, they obtain the process nodes on the event execution process, and in each process node, a corresponding node control is required to implement the data execution action, that is, the node data of each node control is stored in the corresponding storage space according to a preset format, and then the calling relationship between different node controls is determined through different node data to generate an event execution process, so that users can flexibly create event execution processes and improve the data processing capabilities of event execution processes, thereby improving the accuracy of low-code data development.

[0111] Reference Figure 5 The embodiment of the present application further provides an event execution process creation device, and the event execution process creation device 500 may include:

[0112] An acquisition module 501 is used to acquire multiple process nodes on the event execution process in response to a user's operation of triggering the creation of an event execution process;

[0113] A creation module 502 is used to create a node control corresponding to a process node of an execution process;

[0114] The acquisition module 501 is also used to acquire the node data corresponding to the node control; the node data includes the control name, control type, input data, output data and the predecessor control name;

[0115] The storage module 503 is used to store the node data in a storage space corresponding to the node control according to a preset format;

[0116] The determination module 504 is used to determine the calling relationship between different node controls according to the input data, output data and the name of the predecessor control corresponding to each node control;

[0117] The association module 505 is used to associate various node controls based on the calling relationship to generate an event execution process.

[0118] As an optional implementation, when the node control is a target type control, the name of the predecessor control in the node data of the node control is empty;

[0119] The target type control is the starting control, or the first operation control in a process branch.

[0120] As an optional implementation, the node data also includes a control attribution name, and the control attribution name is used to indicate that the process node corresponding to the node control belongs to the process branch corresponding to the branch process name.

[0121] As an optional implementation, the node data also includes a control branch name, and the control branch name is used to indicate that the node control belongs to a process sub-branch of the process branch.

[0122] As an optional implementation, the storage module 504 may also be used for:

[0123] Get at least one element in the node data;

[0124] For each element, perform data analysis on the element to obtain the first keyword of the element and its corresponding first value;

[0125] Performing type analysis on the first value based on the first keyword to obtain a field type corresponding to the first value;

[0126] Generate a key-value table based on the field type and the first value;

[0127] The key-value table is stored in the storage space corresponding to the node control according to the preset format.

[0128] As an optional implementation manner, the key-value table includes a first key-value table, and the storage module 504 can also be used for:

[0129] In the case where the field type of the first value is determined to be the basic type, the field name corresponding to the element is determined as the second keyword, and the first value is determined to be the second value corresponding to the second keyword;

[0130] A first key-value table is generated based on the second keyword and the second value.

[0131] As an optional implementation manner, the key-value table includes a second key-value table, and the storage module 504 can also be used for:

[0132] In the case where the field type is determined to be an object type, the internal element type corresponding to the element is determined to be a filler object of the element, the internal element type represents the field type of the internal sub-element, and the element includes at least one sub-element;

[0133] In the case where the field types of the filling objects are all determined to be basic types, the field names corresponding to the field types of the filling objects are determined as the third keywords, and the values ​​corresponding to the filling objects are determined as the third values ​​corresponding to the third keywords;

[0134] A second key-value table is generated based on the third keyword and the third value.

[0135] As an optional implementation manner, the key-value table includes a third key-value table, and the storage module 504 can also be used for:

[0136] When the field type is an array type and the element includes multiple sub-elements, determine the field type of each sub-element;

[0137] In the case where the field types of multiple sub-elements are all determined to be the basic type, the field name corresponding to the element is determined as the fourth keyword, and the field types corresponding to the multiple sub-elements are used as the fourth value to generate a third key value table of the element;

[0138] Storing the key-value table in the preset format to the storage space corresponding to the node control includes:

[0139] The third key-value table is stored in the position corresponding to the fourth keyword in the queue until each sub-element in the queue is stored with the corresponding third key-value table.

[0140] Figure 6 A schematic diagram of the hardware structure of an electronic device provided in an embodiment of the present application is shown.

[0141] The electronic device may include a processor 601 and a memory 602 storing computer program instructions.

[0142] Specifically, the processor 601 may include a central processing unit (CPU), or an application specific integrated circuit (ASIC), or may be configured to implement one or more integrated circuits of the embodiments of the present application.

[0143] The memory 602 may include a large capacity memory for data or instructions. By way of example and not limitation, the memory 602 may include a hard disk drive (HDD), a floppy disk drive, a flash memory, an optical disk, a magneto-optical disk, a magnetic tape, or a universal serial bus (USB) drive or a combination of two or more of these. In one example, the memory 602 may include a removable or non-removable (or fixed) medium, or the memory 602 is a non-volatile solid-state memory. The memory 602 may be inside or outside the integrated gateway disaster recovery device.

[0144] In one example, the memory 602 may be a read-only memory (ROM). In one example, the ROM may be a mask-programmed ROM, a programmable ROM (PROM), an erasable PROM (EPROM), an electrically erasable PROM (EEPROM), an electrically rewritable ROM (EAROM), or a flash memory, or a combination of two or more of these.

[0145] The memory 602 may include a read-only memory (ROM), a random access memory (RAM), a magnetic disk storage medium device, an optical storage medium device, a flash memory device, an electrical, optical or other physical / tangible memory storage device. Therefore, generally, the memory includes one or more tangible (non-transitory) computer-readable storage media (e.g., a memory device) encoded with software including computer-executable instructions, and when the software is executed (e.g., by one or more processors), it is operable to perform the operations described with reference to the video query method according to the first aspect of the present disclosure.

[0146] The processor 601 reads and executes the computer program instructions stored in the memory 602 to implement Figure 1 A method for creating an event execution process in the illustrated embodiment.

[0147] In one example, the electronic device may further include a communication interface 603 and a bus 604. Figure 6 As shown, the processor 601, the memory 602, and the communication interface 603 are connected via a bus 604 and communicate with each other.

[0148] The communication interface 603 is mainly used to implement communication between various modules, devices, units and / or equipment in the embodiments of the present application.

[0149] Bus 604 includes hardware, software or both, and the parts of electronic equipment are coupled to each other.For example, but not limitation, bus may include accelerated graphics port (Accelerated Graphics Port, AGP) or other graphics bus, enhanced industry standard architecture (Extended Industry Standard Architecture, EISA) bus, front side bus (Front Side Bus, FSB), hypertransmission (Hyper Transport, HT) interconnection, industry standard architecture (IndustryStandard Architecture, ISA) bus, infinite bandwidth interconnection, low pin count (LPC) bus, memory bus, micro channel architecture (MCA) bus, peripheral component interconnection (PCI) bus, PCI-Express (PCI-X) bus, serial advanced technology attachment (SATA) bus, video electronics standard association local (VLB) bus or other suitable bus or two or more of these combinations. In appropriate cases, bus 604 may include one or more buses. Although the present application embodiment describes and shows a specific bus, the application considers any suitable bus or interconnection.

[0150] The electronic device can execute the video query method in the embodiment of the present application, thereby realizing the combination Figure 1-Figure 4 The described event execution process creation method and device.

[0151] In addition, in combination with the event execution process creation method in the above embodiment, the present application embodiment can provide a computer storage medium for implementation. The computer storage medium stores computer program instructions; when the computer program instructions are executed by a processor, any event execution process creation method in the above embodiment is implemented.

[0152] In an optional embodiment, in combination with the event execution process creation method in the above embodiment, the embodiment of the present application can provide a computer program product for implementation, and the instructions in the computer program product are executed by a processor of an electronic device, so that the electronic device can implement any one of the event execution process creation methods in the above embodiment.

[0153] It should be clear that the present application is not limited to the specific configuration and processing described above and shown in the figures. For the sake of simplicity, a detailed description of the known method is omitted here. In the above embodiments, several specific steps are described and shown as examples. However, the method process of the present application is not limited to the specific steps described and shown, and those skilled in the art can make various changes, modifications and additions, or change the order between the steps after understanding the spirit of the present application.

[0154] The functional blocks shown in the above block diagram can be implemented as hardware, software, firmware or a combination thereof. When implemented in hardware, it can be, for example, an electronic circuit, an application specific integrated circuit (ASIC), appropriate firmware, a plug-in, a function card, etc. When implemented in software, the elements of the present application are programs or code segments that are used to perform the required tasks. The program or code segment can be stored in a machine-readable medium, or transmitted on a transmission medium or a communication link by a data signal carried in a carrier wave. "Machine-readable medium" can include any medium capable of storing or transmitting information. Examples of machine-readable media include electronic circuits, semiconductor memory devices, ROM, flash memory, erasable ROM (EROM), floppy disks, CD-ROMs, optical disks, hard disks, optical fiber media, radio frequency (RF) links, etc. The code segment can be downloaded via a computer network such as the Internet, an intranet, etc.

[0155] It should also be noted that the exemplary embodiments mentioned in this application describe some methods or systems based on a series of steps or devices. However, this application is not limited to the order of the above steps, that is, the steps can be performed in the order mentioned in the embodiment, or in a different order from the embodiment, or several steps can be performed simultaneously.

[0156] Aspects of the present disclosure are described above with reference to the flowchart and / or block diagram of the method, device (system) and computer program product according to the embodiment of the present disclosure. It should be understood that each box in the flowchart and / or block diagram and the combination of each box in the flowchart and / or block diagram can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device to produce a machine so that these instructions executed by the processor of the computer or other programmable data processing device enable the implementation of the function / action specified in one or more boxes of the flowchart and / or block diagram. Such a processor can be, but is not limited to, a general-purpose processor, a special-purpose processor, a special application processor, or a field programmable logic circuit. It can also be understood that each box in the block diagram and / or flowchart and the combination of boxes in the block diagram and / or flowchart can also be implemented by dedicated hardware that performs a specified function or action, or can be implemented by a combination of dedicated hardware and computer instructions.

[0157] The above are only specific implementation methods of the present application. Those skilled in the art can clearly understand that for the convenience and simplicity of description, the specific working processes of the systems, modules and units described above can refer to the corresponding processes in the aforementioned method embodiments, and will not be repeated here. It should be understood that the protection scope of the present application is not limited to this. Any technician familiar with the technical field can easily think of various equivalent modifications or replacements within the technical scope disclosed in this application, and these modifications or replacements should be included in the protection scope of this application.

Claims

1. A method for creating an event execution process, characterized in that: include: In response to a user's operation of triggering creation of an event execution process, a plurality of process nodes on the event execution process are obtained; For a process node of the event execution process, create a node control corresponding to the process node; Obtain node data corresponding to the node control; the node data includes control name, control type, input data, output data and predecessor control name; Storing the node data in a storage space corresponding to the node control according to a preset format; Determine the calling relationship between different node controls according to the input data, output data and predecessor control name corresponding to each node control; Based on the calling relationship, each of the node controls is associated to generate an event execution process.

2. The method according to claim 1, characterized in that In the case where the node control is a target type control, the name of the predecessor control in the node data of the node control is empty; The target type control is the starting control, or the first operation control in the process branch.

3. The method according to claim 1, characterized in that The node data also includes a control attribution name, and the control attribution name is used to indicate that the process node corresponding to the node control belongs to the process branch corresponding to the branch process name.

4. The method according to claim 3, characterized in that The node data also includes a control branch name, and the control branch name is used to indicate that the node control belongs to a process sub-branch of a process branch.

5. The method according to claim 1, characterized in that The storing the node data in a storage space corresponding to the node control according to a preset format includes: Obtain at least one element in the node data; For each element, perform data parsing on the element to obtain a first keyword of the element and a first value corresponding to the keyword; Performing type analysis on the first value based on the first keyword to obtain a field type corresponding to the first value; Generate a key-value table based on the field type and the first value; The key-value table is stored in a storage space corresponding to the node control according to a preset format.

6. The method according to claim 5, characterized in that The key-value table includes a first key-value table, and the generating the key-value table based on the field type and the first value includes: In a case where the field type of the first value is determined to be a basic type, determining the field name corresponding to the element as a second keyword, and determining the first value as a second value corresponding to the second keyword; A first key-value table is generated based on the second keyword and the second value.

7. The method according to claim 5, characterized in that The key-value table includes a second key-value table, and the generating the key-value table based on the field type and the first value includes: In the case where the field type is determined to be an object type, an internal element type corresponding to the element is determined as a filler object of the element, the internal element type represents a field type of an internal sub-element, and the element includes at least one sub-element; In the case where the field types of the filling objects are all determined to be basic types, the field names corresponding to the field types of the filling objects are determined as the third keywords, and the values ​​corresponding to the filling objects are determined as the third values ​​corresponding to the third keywords; The second key-value table is generated based on the third keyword and the third value.

8. The method according to claim 5, characterized in that The key-value table includes a third key-value table, and the generating the key-value table based on the field type and the first value includes: In the case where the field type is an array type and the element includes multiple sub-elements, determining the field type of each sub-element; In the case where the field types of the multiple sub-elements are all determined to be the basic type, the field name corresponding to the element is determined as the fourth keyword, and the field type corresponding to the multiple sub-elements is used as the fourth value to generate a third key value table of the element; The storing the key-value table in a storage space corresponding to the node control according to a preset format includes: The third key-value table is stored in a position in the queue corresponding to the fourth keyword until each sub-element in the queue is stored with a corresponding third key-value table.

9. An event execution process creation device, characterized in that: include: An acquisition module, used for acquiring multiple process nodes on the event execution process in response to a user's triggering operation of creating an event execution process; A creation module, used for creating a node control corresponding to a process node of the execution process; The acquisition module is also used to acquire the node data corresponding to the node control; the node data includes the control name, control type, input data, output data and the predecessor control name; A storage module, used to store the node data in a storage space corresponding to the node control according to a preset format; A determination module, used to determine the calling relationship between different node controls according to the input data, output data and predecessor control name corresponding to each node control; The association module is used to associate each of the node controls based on the calling relationship to generate an event execution process.

10. An electronic device, characterized in that: The device comprises: a processor and a memory storing computer program instructions; When the processor executes the computer program instructions, the event execution process creation method as described in any one of claims 1-8 is implemented.

11. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer program instructions, and when the computer program instructions are executed by a processor, the event execution process creation method according to any one of claims 1 to 8 is implemented.

12. A computer program product, characterized in that When the instructions in the computer program product are executed by a processor of an electronic device, the electronic device executes the event execution process creation method as described in any one of claims 1 to 8.

Images