Guide task creation method and device, equipment and medium

Abstract

The embodiment of the invention discloses a method and device for creating a guide type task, equipment and a medium. The method comprises the steps of obtaining a guide type task creating template, wherein the guide type task creating template comprises trigger setting element information and rendering rule element information; using the guide type task creating template to generate related instances for creating the guide type task; and driving the related instance for creating the guide type task, automatically rendering and updating a front-end interface according to the rendering rule element information, loading the trigger setting element information, and creating the guide type task. The embodiment of the invention can be applied to a guide type task system.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of software engineering, and specifically to a method, apparatus, device and medium for creating a wizard-style task. Background Art

[0002] Wizard-based systems are a common type of computer system, usually used in scenarios such as software installation, online registration, and e-commerce transactions. It can break down a complex process into multiple simple steps, making it easier for users to understand and operate. Wizard-based systems usually provide services to users in the form of wizard-based tasks.

[0003] Wizard tasks are mainly created by users through the wizard task system according to actual needs. However, in the process of using the wizard task system to create wizard tasks, the inventor found that users need to configure business trigger details and front-end interface rendering rules for each wizard task according to personalized needs, resulting in a long wizard task creation development cycle and low delivery efficiency. Summary of the invention

[0004] The embodiments of the present application provide a method, apparatus, device and medium for creating a wizard-type task to solve the problem of long development cycle and low delivery efficiency of wizard-type task creation.

[0005] In a first aspect, an embodiment of the present application provides a method for creating a wizard task, the method comprising:

[0006] Acquire a wizard task creation template, wherein the wizard task creation template includes: trigger setting element information and rendering rule element information;

[0007] Using the wizard task creation template, generating relevant instances for creating wizard tasks;

[0008] Drive the related instances of creating the wizard task, automatically render and update the front-end interface according to the rendering rule element information, load the trigger setting element information, and create the wizard task.

[0009] In a second aspect, an embodiment of the present application provides a device for creating a wizard task, the device comprising:

[0010] A template acquisition module, used to acquire a wizard task creation template, wherein the wizard task creation template includes: trigger setting element information and rendering rule element information;

[0011] An instance generation module, used to use the wizard task creation template to generate a related instance for creating a wizard task;

[0012] The wizard task creation module is used to drive the relevant instances of creating the wizard task, automatically render and update the front-end interface according to the rendering rule element information, load the trigger setting element information, and create the wizard task.

[0013] In a third aspect, an embodiment of the present application provides an electronic device, comprising: one or more processors; a storage device on which one or more programs are stored, and when the one or more programs are executed by the one or more processors, the one or more processors implement the method described in any embodiment of the first aspect.

[0014] In a fourth aspect, an embodiment of the present application provides a computer-readable medium having a computer program stored thereon, which, when executed by a processor, implements the method described in any embodiment of the first aspect.

[0015] The creation method, apparatus, device and medium of a wizard task provided by the embodiment of the present application, the wizard task can be created according to the wizard template, and because the wizard template contains trigger setting element information and rendering rule element information, in the process of creating the wizard task, the trigger can be quickly configured and changed according to the trigger setting element information according to the changes in user needs, and because the wizard template also contains rendering rule element information, the technical solution provided by the embodiment of the present application supports the configuration of flexible rendering rules, and the rendering rule element information can be set up in the front-end interface. The technical solution provided by the embodiment of the present application can significantly reduce the development workload of wizard task creation, improve development efficiency, and solve the problem of long development cycle and low delivery efficiency of wizard task creation. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] Other features, objects and advantages of the present application will become more apparent by reading the detailed description of non-limiting embodiments made with reference to the following drawings:

[0017] Figure 1 is a flowchart of an embodiment of a method for creating a wizard task of the present application;

[0018] Figure 2 It is a structural diagram of an embodiment of a device for creating a wizard-style task of the present application;

[0019] Figure 3 It is a schematic diagram of the structure of an electronic device used to implement an embodiment of the present application. DETAILED DESCRIPTION

[0020] All actions to obtain signals, information or data in this application are carried out in compliance with the relevant data protection laws and policies of the country where they are located, and with the authorization given by the owner of the corresponding device.

[0021] The present application will be further described in detail below in conjunction with the accompanying drawings and embodiments. It is to be understood that the specific embodiments described herein are only used to explain the relevant invention, rather than to limit the invention. It should also be noted that, for ease of description, only the parts related to the relevant invention are shown in the accompanying drawings.

[0022] It should be noted that, in the absence of conflict, the embodiments and features in the embodiments of the present application can be combined with each other. The present application will be described in detail below with reference to the accompanying drawings and in combination with the embodiments.

[0023] Please refer to Figure 1 , which shows a process 100 of an embodiment of a method for creating a wizard-style task according to the present application. The method for creating a wizard-style task can be applied to various electronic devices with data processing functions. For example, the electronic devices may include but are not limited to cloud servers, physical servers, etc. The execution subject of the method for creating a wizard-style task may be a processor in the electronic device.

[0024] The wizard task creation method, device, equipment and medium provided in the embodiments of the present application can be applied in various wizard task systems, for example: can be applied in the intelligent stack (Intelligent Stack, iStack) wizard installation task platform to support iStack cloud management platform installation, computing cluster installation, storage cluster installation, initialization of hosts and other wizard installation tasks.

[0025] like Figure 1 As shown, the method for creating the wizard task includes the following steps:

[0026] Step 101: Obtain a wizard task creation template, where the wizard task creation template includes: trigger setting element information and rendering rule element information.

[0027] In this embodiment, various wizard task creation templates can be preset and stored in a template library. When a wizard task needs to be created, step 101 can obtain the required wizard task creation template from the template library.

[0028] In this embodiment, the trigger setting element information may include but is not limited to:

[0029] Job trigger ID, trigger type, trigger sequence, trigger job type, and trigger job parameters, etc.

[0030] Optionally, the trigger type may include but is not limited to: request instruction (command), pipeline (pipeline) and jump link (href).

[0031] In this embodiment, the rendering rule element information may include but is not limited to:

[0032] Rendering interface type, rendering type, rendering order, rendering style, and rendering related state matching expressions, etc.

[0033] Optionally, the rendering interface type may include but is not limited to: automatic form (autoform), host interface (hosts), pipeline interface (pipeline), information display interface (info), etc.

[0034] Optionally, the rendering type may include but is not limited to: text (string), option (select), and media (media).

[0035] Optionally, the rendering style may include but is not limited to: rendering position and rendering color, etc.

[0036] In this embodiment, the wizard task creation template may include multiple types. Exemplarily, the wizard task creation template provided in this embodiment may include but is not limited to:

[0037] Task template table, task stage template table, task attribute specification table, task job trigger table, task instance table and task stage instance table, etc.

[0038] Based on the wizard task creation template described above, the trigger setting element information can be carried in the task job trigger table, and the rendering rule element information can be carried in the task stage template table, the task attribute specification table, the task job trigger table and the task stage instance table.

[0039] It should be noted that the wizard-style task creation template described above is only a specific example of this embodiment, and in actual use, other templates may also be included, such as a task attribute instance table, a task trigger instance table, and a job execution instance table, etc., which will not be described one by one here.

[0040] In order to enable technical personnel in this field to have a deeper understanding and knowledge of the wizard-style task creation template provided in the embodiment of the present application, the wizard-style task creation template may include: task template table, task stage template table, task attribute specification table, task job trigger table, task instance table and task stage instance table as an example, and the constituent elements and format of each template are explained below.

[0041] Exemplary, the wizard-style task creation template includes:

[0042] 1. Task template table. The components of the task template include:

[0043] (1)Task template ID

[0044] (2) Task template name

[0045] (3) Task template description

[0046] (4) Creation time

[0047] (5) Update time

[0048] Optional, (6) Online status

[0049] Exemplarily, the format of the task template table may be as shown in Table 1 below:

[0050]

[0051] Table 1

[0052] Application example: When the technical solution provided in this embodiment is used to support the installation of the iStack cloud management platform, the specific settings of the task template table can be shown in Table 2:

[0053]

[0054] Table 2

[0055] 2. Task phase template table

[0056] (1)Task template ID

[0057] (2) Phase name

[0058] In this embodiment, the stage names may include, but are not limited to: initialization configuration, host information configuration, installation of cloud management applications, installation result confirmation, etc.

[0059] (3) Phase ID

[0060] (4) Stage sequence

[0061] (5) Rendering interface type

[0062] In this embodiment, the rendering interface types may include, but are not limited to: automatic forms (autoform), host interfaces (hosts), pipeline interfaces (pipeline), and information display interfaces (info).

[0063] Optional, (6) Online status

[0064] Exemplarily, the format of the task phase template table may be as shown in Table 3 below:

[0065]

[0066] Table 3

[0067] Application example: When the technical solution provided in this embodiment is used to support the installation of the iStack cloud management platform, the specific settings of the task stage template table can be shown in Table 4:

[0068]

[0069] Table 4

[0070] 3. Task attribute specification table

[0071] (1) Job attribute specification ID

[0072] (2)Task template ID

[0073] (3) Attribute name

[0074] In this embodiment, the attribute name may include but is not limited to: storage cluster code, storage cluster name, computing cluster code, computing cluster name, large page reservation type, istack installation intervention, system administrator account, system administrator password and istack address, etc.

[0075] (4) Rendering type

[0076] In this embodiment, the rendering type may include but is not limited to: text (string), option (select), and media (media).

[0077] (5) Rendering order

[0078] (6) Rendering associated state matching expression

[0079] In this embodiment, the rendering-related state matching expression refers to "task state @ task stage state @ whether in the current stage", and whether to render can be determined based on the latest state of the task and stage operation.

[0080] For example, the format of the task attribute specification table may be as shown in Table 5 below:

[0081]

[0082] Table 5

[0083] Application example: When the technical solution provided in this embodiment is used to support the installation of the iStack cloud management platform, the specific settings of the task attribute specification table can be shown in Table 6:

[0084]

[0085]

[0086]

[0087] Table 6

[0088] 4. Task job trigger table

[0089] (1) Job trigger ID

[0090] (2)Task template ID

[0091] (3) Trigger type

[0092] In this embodiment, the task job trigger table may include but is not limited to: request instructions (command), pipelines (pipeline), jump links (href), etc.

[0093] (4) Trigger sequence

[0094] (5) Trigger job type

[0095] (6) Trigger job parameters

[0096] (7) Rendering style

[0097] In this embodiment, the rendering style may include but is not limited to: rendering position (bottom, etc.) and rendering color (primary, etc.).

[0098] (8) Rendering order

[0099] (9) Rendering associated state matching expression

[0100] (10) Online status

[0101] Exemplarily, the format of the task job trigger table may be as shown in Table 7 below:

[0102]

[0103] Table 7

[0104] Application example: When the technical solution provided in this embodiment is used to support the installation of the iStack cloud management platform, the specific settings of the task job trigger table can be as shown in Table 8:

[0105]

[0106]

[0107]

[0108] Table 8

[0109] 5. Task instance table

[0110] (1) Task instance ID

[0111] (2)Task template ID

[0112] (3) Task name

[0113] (4) Current stage ID

[0114] (5) Update time

[0115] (6) Task status

[0116] For example, the format of the task instance table may be as shown in Table 9 below:

[0117]

[0118] Table 9

[0119] Application example: When the technical solution provided in this embodiment is used to support the installation of the iStack cloud management platform, the specific settings of the task instance table can be shown in Table 10:

[0120]

[0121] Table 10

[0122] 6. Task Phase Instance Table

[0123] (1) Task phase instance ID

[0124] (2) Stage sequence

[0125] (3) Rendering interface type

[0126] (4) Stage start time

[0127] (5) End time of the stage

[0128] (6) Task phase status

[0129] For example, the format of the task phase instance table may be as shown in Table 11 below:

[0130]

[0131] Table 11

[0132] Application example: When the technical solution provided in this embodiment is used to support the installation of the iStack cloud management platform, the specific settings of the task stage instance table can be shown in Table 12:

[0133]

[0134] Table 12

[0135] Step 102: Use the wizard task creation template to generate relevant instances for creating the wizard task.

[0136] In this embodiment, relevant examples of the wizard task may include but are not limited to:

[0137] Task instances, stage instances, property instances, job trigger instances, and job execution instances, etc.

[0138] Step 103: drive the creation of relevant instances of the wizard-style task, automatically render and update the front-end interface according to the rendering rule element information, load the trigger setting element information, and create the wizard-style task.

[0139] For example: In the task job trigger table shown in Table 8, trigger ID: 10000201, trigger sequence: start task, rendering associated state matching expression: (re2)new@new@.*, indicating that only wizard tasks with task status of new and stage status of new are rendered, and the rendering position is the bottom and the main color. When the task status or stage status becomes in progress (running), it will not be rendered, and the trigger with the trigger sequence of start task cannot be executed again. According to business needs, whether to render can be determined based on the task status, stage status, and whether it is the current stage, thereby opening up the effect of whether to display attributes and whether the job trigger can be executed. When the trigger is executed, according to the trigger job type ID command = task.start, the job of starting the task will be triggered.

[0140] For another example, in the task job trigger table shown in Table 8, trigger ID: 10000204, trigger sequence: detect environment, trigger type is pipeline, trigger job type is ansible=init-check, indicating an ansible job named init-check (host environment detection), trigger job parameters are hosts=all, timeDiff=${timeDiff}, indicating execution on all hosts in the task for host time difference detection.

[0141] The method for creating a wizard task provided in the embodiment of the present application can create a wizard task according to a wizard template. Since the wizard template contains trigger setting element information and rendering rule element information, in the process of creating a wizard task, the trigger can be quickly configured and changed according to the trigger setting element information according to changes in user needs. Moreover, since the wizard template also contains rendering rule element information, the technical solution provided in the embodiment of the present application supports the configuration of flexible rendering rules, and the rendering rule element information can be set up in the front-end interface. The technical solution provided in the embodiment of the present application can significantly reduce the development workload of wizard task creation, improve development efficiency, and solve the problems of long development cycle and low delivery efficiency of wizard task creation.

[0142] Please refer to Figure 2 As an implementation of the methods shown in the figures, the present application provides an embodiment of a device for creating a wizard-style task. The device embodiment corresponds to the method shown in the above embodiments, and the device can be specifically applied to various electronic devices.

[0143] like Figure 2 As shown, the wizard task creation device 200 of this embodiment includes:

[0144] The template acquisition module 201 is used to acquire a wizard task creation template, wherein the wizard task creation template includes: trigger setting element information and rendering rule element information;

[0145] An instance generation module 202 is used to generate a related instance of creating a wizard task using the wizard task creation template;

[0146] The wizard task creation module 203 is used to drive the related instances of creating the wizard task, automatically render and update the front-end interface according to the rendering rule element information, load the trigger setting element information, and create the wizard task.

[0147] Optionally, the wizard-style task creation template includes:

[0148] Task template table, task phase template table, task attribute specification table, task job trigger table, task instance table and task phase instance table;

[0149] The trigger setting element information is carried in the task job trigger table;

[0150] The rendering rule element information is carried in the task stage template table, the task attribute specification table, the task job trigger table and the task stage instance table.

[0151] Optionally, the task stage template table includes: task template ID, stage name, stage ID, stage sequence and rendering interface type; and / or,

[0152] The task attribute specification table includes: job attribute specification ID, task template ID, attribute name, rendering type, rendering order and rendering associated state matching expression; and / or,

[0153] The task job trigger table includes: job trigger ID, task template ID, trigger type, trigger sequence, trigger job type, trigger job parameter, rendering style, rendering sequence and rendering associated state matching expression; and / or,

[0154] The task stage instance table includes: task stage instance ID, stage sequence, rendering interface type, stage start time, stage end time and task stage status.

[0155] Optionally, the trigger setting element information includes: job trigger ID, trigger type, trigger sequence, trigger job type and trigger job parameters.

[0156] Optionally, the trigger types include: request instruction, pipeline and jump link.

[0157] Optionally, the rendering rule element information includes: rendering interface type, rendering type, rendering order, rendering style and rendering associated state matching expression.

[0158] Optionally, the rendering interface types include: automatic form, host interface, pipeline interface and information display interface; and / or,

[0159] The rendering types include: text, options and media; and / or,

[0160] The rendering style includes: rendering position and rendering color.

[0161] The specific implementation method of the wizard task creation device provided in the embodiment of the present application can be found in the wizard task creation method provided in the above embodiment, and will not be repeated here.

[0162] The wizard task creation device provided in the embodiment of the present application can create a wizard task according to a wizard template. Since the wizard template contains trigger setting element information and rendering rule element information, in the process of creating a wizard task, the trigger can be quickly configured and changed according to the trigger setting element information according to changes in user needs. Moreover, since the wizard template also contains rendering rule element information, the technical solution provided in the embodiment of the present application supports the configuration of flexible rendering rules, and the rendering rule element information can be set up in the front-end interface. The technical solution provided in the embodiment of the present application can significantly reduce the development workload of wizard task creation, improve development efficiency, and solve the problems of long development cycle and low delivery efficiency of wizard task creation.

[0163] Reference below Figure 3 , which shows a schematic structural diagram of an electronic device for implementing some embodiments of the present application. Figure 3 The electronic device shown is merely an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.

[0164] like Figure 3As shown, the electronic device 300 may include a processing device (e.g., a central processing unit, a graphics processing unit, etc.) 301, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 302 or a program loaded from a storage device 308 into a random access memory (RAM) 303. In the RAM 303, various programs and data required for the operation of the electronic device 300 are also stored. The processing device 301, the ROM 302, and the RAM 303 are connected to each other via a bus 304. An input / output (I / O) interface 305 is also connected to the bus 304.

[0165] Typically, the following devices may be connected to the I / O interface 305: input devices 306 including, for example, a touch screen, a touch pad, a keyboard, a mouse, a camera, a microphone, an accelerometer, a gyroscope, etc.; output devices 307 including, for example, a liquid crystal display (LCD), a speaker, a vibrator, etc.; storage devices 308 including, for example, a disk, a hard disk, etc.; and communication devices 309. The communication devices 309 may allow the electronic device 300 to communicate with other devices wirelessly or by wire to exchange data. Although Figure 3 The electronic device 300 is shown with various devices, but it should be understood that it is not required to implement or possess all the devices shown. More or fewer devices may be implemented or possessed instead. Figure 3 Each block shown in the figure may represent one device, or may represent multiple devices as required.

[0166] In particular, according to some embodiments of the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, some embodiments of the present application include a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a program code for executing the method shown in the flowchart. In some such embodiments, the computer program can be downloaded and installed from the network through the communication device 309, or installed from the storage device 308, or installed from the ROM 302. When the computer program is executed by the processing device 301, the above-mentioned functions defined in the method of some embodiments of the present application are executed.

[0167] It should be noted that the computer-readable medium described in some embodiments of the present application may be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. The computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In some embodiments of the present application, a computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in combination with an instruction execution system, device or device. In some embodiments of the present application, a computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, which carries a computer-readable program code. This propagated data signal may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. The computer readable signal medium may also be any computer readable medium other than a computer readable storage medium, which may send, propagate or transmit a program for use by or in conjunction with an instruction execution system, apparatus or device. The program code contained on the computer readable medium may be transmitted using any suitable medium, including but not limited to: wires, optical cables, RF (radio frequency), etc., or any suitable combination of the above.

[0168] In some embodiments, the client and the server may communicate using any currently known or future developed network protocol such as HTTP (HyperText Transfer Protocol), and may be interconnected with any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include a local area network ("LAN"), a wide area network ("WAN"), an internet (e.g., the Internet), and a peer-to-peer network (e.g., an ad hoc peer-to-peer network), as well as any currently known or future developed network.

[0169] The computer-readable medium may be included in the electronic device; or it may exist independently without being installed in the electronic device. The computer-readable medium carries one or more programs. When the one or more programs are executed by the electronic device, the electronic device: obtains a wizard task creation template, the wizard task creation template includes trigger setting element information and rendering rule element information; uses the wizard task creation template to generate a related instance of creating a wizard task; drives the related instance of creating a wizard task, automatically renders and updates the front-end interface according to the rendering rule element information, loads the trigger setting element information, and creates a wizard task.

[0170] Computer program code for performing the operations of some embodiments of the present application may be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, C++; and also conventional procedural programming languages ​​such as "C" language or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, or may be connected to an external computer (e.g., through the Internet using an Internet service provider), including a local area network (LAN) or a wide area network (WAN).

[0171] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present application. In this regard, each square box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the module, the program segment or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two square boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0172] The units described in some embodiments of the present application may be implemented by software or hardware. The units described may also be set in a processor, for example, it may be described as: a processor includes a first determination unit, a second determination unit, a selection unit, and a third determination unit. The names of these units do not, in some cases, constitute limitations on the units themselves.

[0173] The functions described above herein may be performed at least in part by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that may be used include: field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), complex programmable logic devices (CPLDs), and the like.

[0174] The above description is only some preferred embodiments of the present application and an explanation of the technical principles used. Those skilled in the art should understand that the scope of the invention involved in the embodiments of the present application is not limited to the technical solutions formed by the specific combination of the above technical features, but should also cover other technical solutions formed by any combination of the above technical features or their equivalent features without departing from the above invention concept. For example, the above features are replaced with (but not limited to) the technical features with similar functions disclosed in the embodiments of the present application to form a technical solution.

Claims

1. A method for creating a wizard task, characterized in that: The method comprises: Acquire a wizard task creation template, wherein the wizard task creation template includes: trigger setting element information and rendering rule element information; Using the wizard task creation template, generating relevant instances for creating wizard tasks; Drive the related instances of creating the wizard task, automatically render and update the front-end interface according to the rendering rule element information, load the trigger setting element information, and create the wizard task.

2. The method according to claim 1, characterized in that: The wizard task creation template includes: Task template table, task phase template table, task attribute specification table, task job trigger table, task instance table and task phase instance table; The trigger setting element information is carried in the task job trigger table; The rendering rule element information is carried in the task stage template table, the task attribute specification table, the task job trigger table and the task stage instance table.

3. The method according to claim 2, characterized in that The task stage template table includes: task template ID, stage name, stage ID, stage sequence and rendering interface type; and / or, The task attribute specification table includes: job attribute specification ID, task template ID, attribute name, rendering type, rendering order and rendering associated state matching expression; and / or, The task job trigger table includes: job trigger ID, task template ID, trigger type, trigger sequence, trigger job type, trigger job parameter, rendering style, rendering sequence and rendering associated state matching expression; and / or, The task stage instance table includes: task stage instance ID, stage sequence, rendering interface type, stage start time, stage end time and task stage status.

4. The method according to claim 1, characterized in that The trigger setting element information includes: job trigger ID, trigger type, trigger sequence, trigger job type and trigger job parameters.

5. The method according to claim 4, characterized in that The trigger types include: request instruction, pipeline and jump link.

6. The method according to claim 1, characterized in that The rendering rule element information includes: rendering interface type, rendering type, rendering order, rendering style and rendering associated state matching expression.

7. The method according to claim 6, characterized in that The rendering interface types include: automatic form, host interface, pipeline interface and information display interface; and / or, The rendering types include: text, options and media; and / or, The rendering style includes: rendering position and rendering color.

8. A device for creating a wizard task, characterized in that: The device comprises: A template acquisition module, used to acquire a wizard task creation template, wherein the wizard task creation template includes: trigger setting element information and rendering rule element information; An instance generation module, used to use the wizard task creation template to generate a related instance for creating a wizard task; The wizard task creation module is used to drive the relevant instances of creating the wizard task, automatically render and update the front-end interface according to the rendering rule element information, load the trigger setting element information, and create the wizard task.

9. An electronic device, characterized in that: include: one or more processors; a storage device having one or more programs stored thereon, When the one or more programs are executed by the one or more processors, the one or more processors implement the method according to any one of claims 1 to 7.

10. A computer readable medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the method according to any one of claims 1 to 7 is implemented.

Images