TW202125236A - Developing method and developing device for event processing file - Google Patents

Abstract

This present disclosure provides a developing method. The developing method includes steps of: receiving a drawing instruction from a user and generating a flowchart according to the drawing instruction; receiving a first editing instruction and a second editing instruction from the user and generating an event processing diagram according to the flowchart, the first editing instruction and the second editing instruction, wherein at least one event component is imported into the flowchart according to the first editing instruction, and event attributes of the flowchart are set according to the second editing instruction; and compiling the event processing diagram to generate the event processing file. The developing method and the developing device of the present disclosure can improve the design efficiency of the event processes and the development efficiency of event-driven systems.

Description

Development method and device of event processing file

This case is about a computer technology field, especially a method and device for developing event processing files.

In related technologies, business process modeling usually uses flowcharts generated by graphical notation to express complex process semantics and provide intuitive assistance to business personnel. However, this kind of flowchart cannot be directly converted into an executable business process file. In particular, in event-driven systems, it is often necessary to achieve or control the direction of the business process based on the intermediate state of the event processing process, and related technologies cannot meet this requirement. It should be noted that the information disclosed in the background art section above is only used to enhance the understanding of the background of the case, and therefore may include information that does not constitute the prior art known to those of ordinary skill in the art.

The purpose of this case is to provide an event processing file development method and event processing file development device, which are used to overcome the problems caused by the limitations and defects of related technologies to at least a certain extent.

In order to achieve the foregoing objective, this case provides a method for developing event processing files, which includes the steps of: receiving a drawing instruction from the user, and generating a flowchart according to the drawing instruction; receiving a first editing instruction and a second editing instruction from the user, according to The flowchart, the first editing instruction, and the second editing instruction generate an event processing diagram, wherein at least one business element is imported into the flowchart according to the first editing instruction, and an event attribute of the flowchart is set according to the second editing instruction; and the compilation event Process the diagram to generate an event processing file.

In one embodiment, the development method further includes: providing the user with an icon for drawing a flowchart. The icon includes a start icon, an end icon, a business element icon, a decision branch icon, a constraint condition icon, and a connection. Icon.

In one embodiment, the business element includes a description file and a function file. The function file includes executable code that implements at least one business function. The description file includes metadata and interface description information of the function file.

In one embodiment, the flowchart includes a business element icon, and the first editing instruction includes: clicking on the business element icon and linking it to the business element.

In one embodiment, the event attributes include start event attributes, and the types of start event attributes include data polling trigger, data push trigger, and presentation layer state transfer application programming interface (Rest API: Representational State Transfer Application Programming Interface) trigger.

In one embodiment, the flowchart includes a start icon, and the second editing instruction includes: click the start icon, and enter the parameters of the start event attribute in the opened start event attribute editing window.

In one embodiment, the event attribute includes an end event attribute, and the end event attribute includes the return value of the end event and the execution condition of the end event.

In one embodiment, the flowchart includes an end icon, and the second editing instruction includes: clicking the end icon, and inputting the end event attribute parameter in the opened end event attribute editing window.

In one embodiment, the event attribute includes a business event attribute, and the business event attribute includes an executable method, and the executable method is one of at least one business function of the business element.

In one embodiment, the business event attributes include input parameters and return values.

In one embodiment, the business event attributes include execution conditions.

In one embodiment, the business event attribute includes an execution mode, and the execution mode is serial or parallel.

In one embodiment, the flowchart includes a business element icon and a connection icon, and the second editing instruction includes: clicking the connection icon pointing to the business element icon, and inputting the parameters of the business event attribute in the opened business event attribute editing window .

In order to achieve the foregoing purpose, this case further provides a development device for event processing files, including: a drawing module, which receives user drawing instructions, and generates a flowchart according to the drawing instructions; an editing module, which receives user first editing instructions and second editing instructions, Generate an event processing diagram according to the flowchart, the first editing instruction, and the second editing instruction, wherein the editing module imports at least one business element in the flowchart according to the first editing instruction, and sets the event attribute of the flowchart according to the second editing instruction; And compile the module, compile the event processing diagram to generate the event processing file.

In one embodiment, the business element includes a description file and a function file. The function file includes executable code for realizing at least one business function. The description file includes metadata and interface description information of the function file.

In one embodiment, the flowchart includes a business element icon, and the first editing instruction includes: clicking on the business element icon and linking it to the business element.

In one embodiment, the event attributes include start event attributes, and the types of start event attributes include data polling trigger, data push trigger, and presentation layer state transition application program interface trigger.

In one embodiment, the flowchart includes a start icon, and the second editing instruction includes: click the start icon, and enter the parameters of the start event attribute in the opened start event attribute editing window.

In one embodiment, the event attribute includes an end event attribute, the flowchart includes an end icon, and the second editing instruction includes: clicking the end icon and inputting the end event attribute parameter in the opened end event attribute editing window.

In one embodiment, the event attribute includes a business event attribute, and the business event attribute includes an executable method, and the executable method is one of at least one business function of the business element.

In one embodiment, the business event attributes include input parameters and return values.

In one embodiment, the business event attributes include execution conditions.

In one embodiment, the business event attribute includes an execution mode, and the execution mode is serial or parallel.

In one embodiment, the flowchart includes a business element icon and a connection icon, and the second editing instruction includes: clicking the connection icon pointing to the business element icon, and inputting the parameters of the business event attribute in the opened business event attribute editing window .

In order to achieve the foregoing objective, this case also provides an event processing file development device, including: a memory; and a processor coupled to the associated memory. The processor is configured to execute any of the above based on instructions stored in the memory. Item method.

In order to achieve the foregoing objective, the present case further provides a computer-readable storage medium on which a program is stored, and the program is implemented in an exemplary embodiment of the present case when the program is executed by a processor.

The event processing file development method provided in this case imports business components into the flowchart according to the user’s drawing instructions and editing instructions, sets the event attributes in the flowchart, generates event processing diagrams and compiles them to generate The execution of the event processing file, the compilation process includes the smart verification of the syntax and semantics of the event processing file. The event processing file can be loaded by the event-driven system and generate event routing, which improves the design efficiency of the business process and the development efficiency of the event-driven system. On the other hand, because the editing of event attributes in this case is independent of the functions of business components, it can also well realize the dynamic evolution and update of business processes.

It should be understood that the above general description and the following detailed description are only exemplary and explanatory, and cannot limit the case.

Example embodiments will now be described more fully with reference to the accompanying drawings. However, the example embodiments can be implemented in various forms, and should not be construed as being limited to the examples set forth herein; on the contrary, the provision of these embodiments makes this case more comprehensive and complete, and fully conveys the idea of the example embodiments to the present Technicians in the field. The described features, structures or characteristics can be combined in one or more embodiments in any suitable way. In the following description, many specific details are provided to give a full understanding of the implementation of this case. However, those skilled in the art will realize that the technical solutions of the present case can be practiced without one or more of the specific details, or other methods, constituent elements, devices, steps, etc. can be used. In other cases, the known technical solutions are not shown or described in detail to avoid overwhelming the crowd and obscure all aspects of the case.

In addition, the drawings are only schematic illustrations of the present case, and the same drawing symbols in the drawings indicate the same or similar parts, and thus their repeated description will be omitted. Some of the block diagrams shown in the drawings are functional entities and do not necessarily correspond to physically or logically independent entities. These functional entities may be implemented in the form of software, or implemented in one or more hardware modules or integrated circuits, or implemented in different networks and/or processor devices and/or microcontroller devices.

The exemplary implementation of this case will be described in detail below with reference to the accompanying drawings.

Figure 1 is a flowchart of a method for developing an event processing file in an exemplary embodiment of this case. Referring to Figure 1, the development method of event handling files can include:

Step S1, receiving a drawing instruction from the user, and generating a flowchart according to the drawing instruction;

Step S2, receiving a first editing instruction and a second editing instruction from the user, generating an event processing diagram according to the flowchart, the first editing instruction, and the second editing instruction, wherein the first editing instruction is described in the flowchart according to the first editing instruction. Import at least one business element into the, and set an event attribute of the flowchart according to the second editing instruction;

Step S3, compiling the event processing diagram to generate an event processing file.

The event processing file development method provided in this case imports business components into the flowchart according to the user’s drawing instructions and editing instructions, sets the event attributes in the flowchart, generates event processing diagrams and compiles them to generate The executed business process file, that is, the event processing file, can be loaded by the event-driven system and generate event routing, which improves the design efficiency of the business process and the development efficiency of the event-driven system. On the other hand, because the setting of event attributes in this case is independent of the functions of business elements, the trend of business processes can be enriched or controlled by setting event attributes, and the dynamic evolution and update of business processes can also be well realized.

The steps of the development method 100 are described in detail below.

Figure 2 is a schematic diagram of an editing interface and flowchart provided by an exemplary embodiment of this case.

Referring to Figure 2, in an exemplary embodiment of the method, in step S1, the method 100 may further include providing the user with an illustration for drawing the flowchart. The illustration includes, but is not limited to, the start illustration 21, The end diagram 22, the business component diagram 23, the decision branch diagram 24, the constraint condition diagram 25, and the connection diagram 26, these diagrams can be used for customers to implement rich business process description solutions.

Among them, the start icon 21 and the end icon 22 are used to indicate the beginning and end of the business process; the business element icon 23 is used to indicate the business function; the decision branch icon 24 is used to indicate the decision condition and the corresponding execution of each decision condition Path; Constraint condition graphic 25 is used to represent logical relationship constraint conditions, such as AND, OR, XOR, etc.; connection graphic 26 is used to indicate the execution sequence, for example, when the connection graphic points from the business element icon A to the business element icon When B, it means that the business element associated with business element icon A is executed first, and then the business element associated with business element icon B is executed. The user can select a suitable icon according to the actual needs of the business process and draw it on a user editing interface 200 by adding, dragging and dropping, etc., to form the flowchart shown in FIG. 2. The above-mentioned diagrams are merely illustrative, and in some other embodiments, more types of diagrams may be provided for the user. In other embodiments of the present case, the editing interface 200 may also include other design styles, and the editing interface 200 shown in FIG. 2 is only for illustration.

In step S1, the user's drawing instruction includes but is not limited to drag and drop. For example, according to the needs of the business process, the user can click the icon in the icon organization column on the left side of the graphical editing interface 200 to place the desired icon on the user editing interface, and adjust the size of the icon by dragging and dropping. The absolute position and the relative position between the icons. The development method of this case can receive the above-mentioned drawing instructions of the user multiple times, and generate a flowchart in the user editing interface 200 according to the drawing instructions. It should be noted that the flowchart shown in Figure 2 is only an example, and the flowchart may only include some of the above illustrations. For example, the flowchart may consist of only the start icon 21, the end icon 22, and the business The component diagram 24 and the connection diagram 26 are composed. In other embodiments of the present case, the flowchart may also include other types of icons, and the current icons may also be designed in other shapes, and the present case is not limited to this. Moreover, those skilled in the art can also design the diagram of the flowchart by themselves, that is, not call it from the diagram column shown in FIG. 2.

In step S2, at least one service element is imported into the flowchart according to the first editing instruction, and the event attribute of the flowchart is set according to the second editing instruction.

Figure 3 is a schematic diagram of importing business elements into the flowchart shown in Figure 2 in an exemplary embodiment of this case. Referring to Figure 3, for the business element icon, the first editing instruction includes but is not limited to clicking on the business element icon and associating it to the business element.

After the user clicks on the business element icon 23 and associates it with the business element, the development method of this case can import the business element corresponding to the business element icon 23 according to the first editing instruction. In order to improve the design efficiency of the user, the name of the associated business component can be displayed on the business component icon 23 after the import is completed. In this embodiment, the first editing instruction can be executed after the flowchart is completely generated. In other embodiments, the first editing instruction can also be executed after the flowchart is partially generated, as long as there is a business element icon.

In an exemplary embodiment of this case, the business element includes a description file and a function file. Among them, the function file is an executable code for executing one or more business functions; the description file includes the metadata of the function file and an interface description information. The interface description of all or part of the business function can be added to the description file corresponding to the function file according to actual needs, and all or part of the business function can be exposed without changing the function file.

In an exemplary embodiment of this case, it is allowed to use a preset description language to write description files corresponding to different business units. The function files corresponding to different business units can be written in the same or different programming languages, which has good scalability. . The default description language may be XML, for example, but this case is not limited to this. In addition, a business component library including common business functions can be provided for users to call, so as to further improve the design efficiency of business processes. In some other embodiments of this case, users can also write business components by themselves according to business needs.

Although flowcharts can roughly indicate the direction of business process execution, they cannot enrich or control the direction of business processes based on event attributes. In step S2, it is also necessary to set the event attribute of the flowchart according to the second editing instruction. The editing of the event attribute is independent of the function of the business element, which can better realize the dynamic evolution and update of the business process.

In an exemplary embodiment of this case, the event attribute includes the initial event attribute. The start event attribute determines the process start mode of the business process, that is, what conditions trigger the execution of the business process.

Figure 4 is an editing window for the attributes of the start event in an exemplary embodiment of the present invention.

Referring to FIGS. 3 and 4, the user's second editing command includes but is not limited to clicking the start event icon, and the properties of the start event are set in the opened edit window of the start event properties. In the embodiment shown in Figure 4, this case provides three icons of timer, external, and space for users to click and choose, which in turn correspond to the three commonly used event-driven data polling triggers, data push triggers, and Rest API triggers. The trigger mode of the system improves the user's development efficiency. However, this case is not limited to this, and those skilled in the art should know that the start event attribute can also include other types of commonly used trigger modes.

In an exemplary embodiment of this case, the event attribute includes a business event attribute, and the business event attribute includes an executable method, and the executable method determines the business function to be executed by the business element in the business process. An example is as follows: Suppose a business element includes three business functions A, B, and C. By setting the executable method, one of the three business functions can be selected and the business element can be used flexibly.

In some other embodiments of this case, the business event attribute may also include an input parameter and a return value, and the business logic can be enriched by setting the input parameter and return value. An example is as follows: Assuming that there is no sequential connection between business element A and business element B in the flowchart, but business element A needs to call the return value of business element B, you can set the input parameters of business element A to that of business element B The return value is used to implement the call to the return value of business element B. It should be noted that the input parameter and return value of the business event attribute can be set to null, where, when the input parameter of the business event attribute is set to null, the actual input parameter of the business element is connected to it in sequence The return value of the last business element; when the return value of the business event attribute is set to null, it means that the business element has no return value.

In some other embodiments of this case, the business event attribute further includes an execution mode, and the execution mode is, for example, serial or parallel. Still taking the above-mentioned service component A and service component B as examples, the execution mode of service component B can be set to serial, and then service component A will wait for service component B to complete execution and obtain a return value before executing.

In other embodiments of this case, the business event attribute may also include an execution condition, that is, a constraint condition for executing the business element.

When the business components remain unchanged but part of the business process needs to be adjusted, by setting the business event attributes, there is no need to redraw the flowchart or re-import the business components to modify the business process to generate a new event processing diagram and Compiling greatly saves the design phase of the user's business process.

Figure 5 is an editing window for business event attributes in an exemplary embodiment of this case.

With reference to Figures 3 and 5, the user's second editing instruction includes but is not limited to clicking the connection icon pointing to the target business component icon, and setting the business event attribute in the opened business event attribute editing window.

In Figure 5, the field condition indicates the execution condition, the field mode indicates the execution mode, the field operationId indicates the executable method, the field inputParam indicates the input parameter, and the field return indicates the return value. The user can edit in the open Enter the parameters of the business event attributes in the corresponding fields of the window. It should be noted that in other embodiments of this case, users can also adjust or set the types and parameters of business event attributes by themselves according to actual conditions.

In an exemplary embodiment of this case, the event attribute of the flowchart includes an end event attribute.

Figure 6 shows the editing window of the end event attribute in an exemplary embodiment of this case.

Referring to Figure 6, the user's second editing command includes, but is not limited to, clicking on the connection icon pointing to the end icon, and inputting the parameters of the end event attribute in the opened edit window of the end event attribute. In Figure 6, similar to the business event attribute of the business component, the end event attribute includes the constraint condition, execution mode and input parameters of the end event, corresponding to the field condition, field mode and field inputParam respectively. The user can enter the corresponding field Enter the parameter of the end event attribute in the bit. For example, when the parameters of the field condition, field mode, and field inputParam are all empty (null), it means that the end event has no constraint conditions, the execution mode is parallel, and the input parameter is the previous one connected to it in sequence The return value of the business component is the return value of the business process. It should be noted that in other embodiments of this case, the user can also adjust or set the types and parameters of the end event attributes by themselves according to the actual situation.

Figures 7A to 7C are schematic diagrams of editing event attributes of an exemplary embodiment of the present invention.

Please refer to Figures 7A to 7B first, which respectively show the business event attribute parameters of the business element "compute" and the business element "smallHandler". In Figure 7A, if the parameter of the field condition is empty, it means that the business element "compute" has no constraint conditions; the parameter of the field operationId is "0000(compute)", it means that the executable method of the business element is code "0000" "Corresponding business function, the character "(compute)" is to facilitate user identification, the business function corresponding to this code has been defined in the description file of the business element; the parameter of the field inputParam is empty, the business element is preset The input parameter of "compute" is the return value of the business element "process"; the parameter of the field mode is invoke, which means that the execution mode of the business element is serial; the parameter of the return field is var_compute, which represents the business element's The return value is var_compute. In Figure 7B, in the attribute editing window of the business component "smallHandler", the parameter of the field condition is: $(var_compute).value>10, the parameter of the field inputParam is $(var_compute), and the parameter of the field operationId The parameter is 0000 (handle), the field return and the field mode are set to empty, which means that the constraint condition of the business element "smallHandler" needs to call the return value of the business element "compute", and the input parameter is the return of the business element "compute" Value (that is, the member variable value of var_compute), its executable method is the business function corresponding to parameter 0000, its return value is empty, and its execution mode is parallel. Figure 7C shows the attribute parameters of the end event of the business process. These parameter settings represent that the end event is unconstrained, the execution mode is parallel, and the input parameter is the return value of the business element "compute".

Therefore, it is not difficult to conclude from the above embodiment that although according to the flowchart, the business elements "compute", "smallHandler" and the end event are parallel, according to the event attributes, the business element "smallHandler" or the end event will wait for the business element "compute" "Execute after the execution is complete. The editing of event attributes is independent of the business functions of business elements, and the trend of business processes can be enriched or controlled by setting event attributes, and the dynamic evolution and update of business processes can also be well realized.

In other embodiments of this case, the development method may further include: receiving a third editing action of the user, and importing a URL-mapping file or a groovy instruction file according to the third editing action, as a supplement to the event processing file, and further enriching the business process. The third editing action includes, but is not limited to, associating the above-mentioned files in the editing interface shown in FIG. 2.

The event processing file development method provided in this case imports business components into the flowchart according to the user’s drawing instructions and editing instructions, sets the event attributes in the flowchart, generates event processing diagrams and compiles them to generate The executed event processing file can be loaded by the event-driven system and generate event routing, which improves the design efficiency of the business process and the development efficiency of the event-driven system. On the other hand, because the editing of the event attributes in this case is independent of the function of the business element, the trend of the business process can be enriched or controlled by setting the event attributes, and the dynamic evolution and update of the business process can also be well realized. In some embodiments, the provided graphical editing interface allows the user to draw a flowchart and set event attributes in the interface, which improves the user's business development efficiency.

Corresponding to the above method embodiment, this case also provides an event processing file development device, which can be used to execute the above method embodiment.

Figure 8 is a block diagram of an event processing file development device in an exemplary embodiment of this case.

Referring to Figure 8, the device 800 for developing event processing files may include:

The drawing module 801 receives a drawing instruction from the user, and generates a flowchart according to the drawing instruction;

The editing module 802 receives a first editing instruction and a second editing instruction from the user, and generates an event processing diagram according to the flowchart, the first editing instruction, and the second editing instruction, wherein, according to the first editing instruction At least one business element is imported into the flowchart, and the event attribute of the flowchart is set according to the second editing instruction;

The compiling module 803 compiles the event processing graph to generate an event processing file. Since each function of the development device 800 has been described in detail in its corresponding method embodiment, this case will not be repeated here.

It should be noted that although several modules or units of the device for action execution are mentioned in the above detailed description, this division is not mandatory. In fact, according to the implementation of this case, the features and functions of two or more modules or units described above can be embodied in one module or unit. Conversely, the features and functions of a module or unit described above can be further divided into multiple modules or units to be embodied.

In an exemplary embodiment of this case, an electronic device capable of implementing the above method is also provided.

Those skilled in the art can understand that various aspects of the present invention can be implemented as a system, a method, or a program product. Therefore, various aspects of the present invention can be specifically implemented in the following forms, namely: a complete hardware implementation, a complete software implementation (including firmware, microcode, etc.), or a combination of hardware and software. Collectively referred to as "circuits", "modules" or "systems".

The electronic device 900 according to this embodiment of the present invention will be described below with reference to FIG. 9. The electronic device 900 shown in FIG. 9 is only an example, and should not bring any limitation to the function and application scope of the embodiment of the present invention.

As shown in Figure 9, the electronic device 900 is represented in the form of a general-purpose computing device. The components of the electronic device 900 may include, but are not limited to: the aforementioned at least one processing unit 910, the aforementioned at least one storage unit 920, and a bus 930 connecting different system components (including the storage unit 920 and the processing unit 910).

Wherein, the storage unit stores a program code, which can be executed by the processing unit 910, so that the processing unit 910 executes the steps according to various exemplary embodiments of the present invention described in the "Exemplary Method" section of this specification. For example, the processing unit 910 can execute the development method as shown in Figure 1.

The storage unit 920 may include a readable medium in the form of a volatile storage unit, such as a random access storage unit (RAM) 9201 and/or a cache storage unit 9202, and may further include a read-only storage unit (ROM) 9203.

The storage unit 920 may also include a program/utility tool 9204 having a set (at least one) program module 9205. Such program module 9205 includes but is not limited to: an operating system, one or more application programs, other program modules, and Program data, each of these examples or some combination may include the realization of the network environment.

The bus 930 may represent one or more of several types of bus structures, including a storage unit bus or a storage unit controller, a peripheral bus, a graphics acceleration port, a processing unit, or any bus structure using a variety of bus structures Local bus.

The electronic device 900 may also communicate with one or more external devices 600 (such as keyboards, pointing devices, Bluetooth devices, etc.), and may also communicate with one or more devices that enable a user to interact with the electronic device 900, and/or Communicate with any device (eg, router, modem, etc.) that enables the electronic device 900 to communicate with one or more other computing devices. This communication can be performed through an input/output (I/O) interface 950. In addition, the electronic device 900 may also communicate with one or more networks (such as a local area network (LAN), a wide area network (WAN), and/or a public network, such as the Internet) through the network interface card 960. As shown in the figure, the network interface card 960 communicates with other modules of the electronic device 900 through the bus 930. It should be understood that although not shown in the figure, other hardware and/or software modules can be used in conjunction with the electronic device 900, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID System, tape drive and data backup storage system, etc.

Through the description of the above embodiments, those skilled in the art can easily understand that the example embodiments described here can be implemented by software, or by combining software with necessary hardware. Therefore, the technical solution according to the implementation of this case can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, hard disk, removable hard disk, etc.) or on the Internet , Including several instructions to enable a computing device (which can be a personal computer, server, terminal device, or network device, etc.) to execute the method according to the implementation of this case.

In an exemplary embodiment of this case, a computer-readable storage medium is also provided, on which is stored a program product capable of implementing the above-mentioned method in this specification. In some possible implementation manners, various aspects of the present invention can also be implemented in the form of a program product, which includes a program code. When the program product runs on a terminal device, the program code is used to make the terminal device execute the program. The steps according to various exemplary embodiments of the present invention are described in the above-mentioned "Exemplary Method" section of the specification.

With reference to Figure 10, a program product 1000 for implementing the above method according to an embodiment of the present invention is described, which can adopt a portable compact hard disk read-only memory (CD-ROM) and include program codes, and It can be run on a terminal device, such as a personal computer. However, the program product of the present invention is not limited thereto. In this document, the readable storage medium can be any tangible medium that includes or stores a program, and the program can be used by or combined with an instruction execution system, device, or device.

The program product can use any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. The readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the above. More specific examples (non-exhaustive list) of readable storage media include: electrical connections with one or more wires, portable hard drives, hard drives, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact hard disk read-only memory (CD-ROM), optical memory, magnetic memory , Or any suitable combination of the above.

The computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, and readable program code is carried therein. This propagated data signal can take many forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the foregoing. The readable signal medium may also be any readable medium other than a readable storage medium, and the readable medium may send, propagate, or transmit a program for use by or in combination with the instruction execution system, apparatus, or device.

The program code included on the readable medium can be transmitted by any suitable medium, including but not limited to wireless, wired, optical cable, RF, etc., or any suitable combination of the above.

The programming code used to perform the operation of the present invention can be written in any combination of one or more programming languages. The programming language includes object-oriented programming languages—such as Java, C++, etc., as well as conventional procedural programming languages. -Such as "C" language or similar programming languages. The code can be executed entirely on the user's computing device, partly on the user's device, executed as a stand-alone software package, partly on the user's computing device and partly executed on the remote computing device, or entirely on the remote computing device. On the end computing device or server. In the case of remote computing equipment, the remote computing equipment can be connected to user computing equipment through any kind of network, including local area network (LAN) or wide area network (WAN), or can be connected to external computing Equipment (for example, using an Internet service provider to connect via the Internet).

In addition, the above-mentioned drawings are merely schematic illustrations of the processing included in the method according to an exemplary embodiment of the present invention, and are not intended for limitation. It is easy to understand that the processing shown in the above drawings does not indicate or limit the time sequence of these processings. In addition, it is easy to understand that these processes can be executed synchronously or asynchronously in multiple modules, for example.

After considering the specification and practicing the invention of this case, those skilled in the art will easily think of other implementation schemes of this case. This application is intended to cover any variations, uses, or adaptive changes in this case, and these variations, uses, or adaptive changes follow the general principles of the case and include common knowledge or customary technical means in the technical field that are not disclosed in this case. The description and embodiments are only regarded as exemplary, and the true scope and concept of the case are pointed out by the claims.

100: Development Method 21: Start icon 22: End icon 23: Business component icon 24: Decision branch diagram 25: Constraint condition diagram 26: Connection icon 200: User editing interface 600: External device 800: Development device 801: drawing module 802: Edit module 803: Compile Module 900: electronic equipment 910: Processing Unit 920: storage unit 9201: Random Access Storage Unit 9202: Cache storage unit 9203: read-only storage unit 9204: Programs/Utilities 9205: program module 930: Bus 950: input/output interface 960: network interface card 1000: Program products S1~S3: steps

The drawings here are incorporated into the specification and constitute a part of the specification, show embodiments conforming to the case, and are used together with the specification to explain the principle of the case. Obviously, the drawings in the following description are only some embodiments of this case. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative work. Figure 1 is a flowchart of a method for developing an event processing file in an exemplary embodiment of this case. Figure 2 is a schematic diagram of an editing interface and flowchart provided by an exemplary embodiment of this case. Figure 3 is a schematic diagram of importing business elements into the flowchart shown in Figure 2 in an exemplary embodiment of this case. Figure 4 is an editing window for the attributes of the start event in an exemplary embodiment of the present invention. Figure 5 is an editing window for business event attributes in an exemplary embodiment of this case. Figure 6 shows the editing window of the end event attribute in an exemplary embodiment of this case. Figures 7A to 7C are schematic diagrams of editing event attributes of an exemplary embodiment of the present invention. Figure 8 is a block diagram of an event processing file development device in an exemplary embodiment of this case. Figure 9 is a block diagram of an electronic device in an exemplary embodiment of this case. Figure 10 is a schematic diagram of a computer-readable storage medium in an exemplary embodiment of this case.

100: Development Method

S1~S3: steps

Claims (26)

A method for developing an event processing file is characterized in that it comprises the following steps: Receiving a drawing instruction from the user, and generating a flowchart according to the drawing instruction; Receive a first edit instruction and a second edit instruction from the user, generate an event processing diagram according to the flowchart, the first edit instruction, and the second edit instruction, wherein the first edit instruction is in the flowchart according to the first edit instruction Import at least one business element, and set an event attribute of the flowchart according to the second editing instruction; and Compile the event processing diagram to generate an event processing file. For example, the development method of the event processing file in claim 1, wherein the development method also includes: Provide users with at least one icon for drawing the flowchart. The icon includes a start icon, an end icon, a business component icon, a decision branch icon, a constraint condition icon, and a connection Icon. For example, the method for developing an event processing file in claim 1, wherein the business element includes a description file and a function file, the function file includes an executable code that implements at least one business function, and the description file includes the metadata of the function file And an interface description information. For example, the method for developing an event processing file in claim 3, wherein the flowchart includes a business element icon, and the first editing instruction includes: Click on the business component icon and associate it to the business component. For example, in the method for developing an event processing document of request 1, the event attribute includes a start event attribute, and the types of the start event attribute include a data polling trigger, a data push trigger, and a presentation layer state transition application program interface trigger. For example, the method for developing an event processing file in claim 5, wherein the flowchart includes a first icon, and the second editing instruction includes: Click the start icon to set the start event attribute in the opened start event attribute edit window. For example, in the method for developing an event processing file of request 1, the event attribute includes an end event attribute, and the end event attribute includes a return value of an end event and an execution condition of an end event. For example, the method for developing an event processing file in claim 7, wherein the flowchart includes an end icon, and the second editing instruction includes: Click the end icon, and enter the end event attribute parameters in an open end event attribute editing window. For example, the method for developing an event processing file in claim 3, wherein the event attribute includes a business event attribute, the business event attribute includes an executable method, and the executable method is one of at least one of the business functions of the business element . For example, in the method for developing an event processing file in request item 3, the business event attribute includes an input parameter and a return value. For example, in the method for developing an event processing file in claim 3, the business event attribute includes an execution condition. For example, in the method for developing an event processing file in claim 3, the business event attribute includes an execution mode, and the execution mode is serial or parallel. For example, the method for developing an event processing file in any one of request items 9 to 12, wherein the flowchart includes a business element icon and a connection icon, and the second editing instruction includes: Click the connection icon pointing to the business element icon, and enter a parameter of the business event attribute in the opened business event attribute editing window. An event processing file development device, which is characterized in that it comprises: A drawing module, receiving a drawing instruction from the user, and generating a flow chart according to the drawing instruction; An editing module receives a first editing instruction and a second editing instruction from the user, and generates an event processing diagram according to the flowchart, the first editing instruction and the second editing instruction, wherein the editing module is based on The first editing instruction imports at least one business element into the flowchart, and sets an event attribute of the flowchart according to the second editing instruction; and A compiling module compiles the event processing graph to generate an event processing file. For example, the development device of claim 14, wherein the service element includes a description file and a function file, the function file includes an execution code for realizing at least one service function, and the description file includes metadata of the function file and an interface description information. For example, the development device of claim 14, wherein the flowchart includes a business element icon, and the first editing instruction includes: Click on the business component icon and associate it to the business component. For example, the development device of claim 14, wherein the event attribute includes a start event attribute, and the types of the start event attribute include a data polling trigger, a data push trigger, and a presentation layer state transition application program interface trigger. For example, the development device of claim 17, wherein the flowchart includes a first icon, and the second editing instruction includes: Click the start icon, and enter the parameters of the start event attribute in the opened start event attribute edit window. For example, the development device of claim 14, wherein the event attribute includes an end event attribute, the flowchart includes an end icon, and the second editing instruction includes: Click the end icon, and enter the end event attribute parameters in an open end event attribute editing window. For example, the development device of claim 15, wherein the event attribute includes a business event attribute, the business event attribute includes an executable method, and the executable method is one of at least one of the business functions of the business element. For example, the development device of claim 15, wherein the business event attribute includes an input parameter and a return value. For example, the development device of claim 15, wherein the business event attribute includes an execution condition. For example, the development device of claim 15, wherein the business event attribute includes an execution mode, and the execution mode is serial or parallel. For example, the development device of any one of claims 20 to 23, wherein the flowchart includes a service element icon and a connection icon, and the second editing command includes: Click the connection icon pointing to the business element icon, and enter a parameter of the business event attribute in the opened business event attribute editing window. An electronic device, characterized in that it comprises: A memory; and A processor coupled to the memory, wherein the processor is configured to execute the method for developing an event processing file such as any one of request items 1-12 based on instructions stored in the memory. A computer-readable storage medium has a program stored thereon, and when the program is executed by a processor, the method for developing an event processing file such as any one of request items 1-12 is realized.

Images