A management method and system for automatic software development

Abstract

The present invention belongs to the field of computer software technology. A management method and system for automatic software development are provided, which realizes the full process management of projects, executions, tasks, requirements, tests, tools and task template groups, wherein the project management process includes: after starting to create a project, after the basic information of the project is input, a project is created; if the project has related executions, it supports viewing or modifying related executions; if not, a new execution is created, after filling in the basic information of the execution, a new execution is added; if the execution has related tasks, it supports viewing or modifying related tasks, if not, a new related task is created, after adding the basic information of the related tasks, after the new related tasks are completed, it supports viewing or modifying the newly created tasks; the present invention can be applied to the automated development process of different software, greatly improving the software development efficiency.

Description

Technical Field

[0001] The present invention relates to the technical field of computer software, and in particular to a management method and system for automatic software development. Background Art

[0002] The statements in this section merely provide background art related to the present invention and do not necessarily constitute prior art.

[0003] At present, the basic process of obtaining software through code development methods is: first, the user puts forward requirements, the R&D personnel write code according to the user's requirements, and then the written code is packaged, and the packaged code is tested by testers. After the test is completed, the entire requirement can be released.

[0004] Today's software development projects are becoming larger and larger as demand increases. The increase in scale has brought a lot of troubles. Various functions are intricately intertwined. A software with more functions usually contains multiple modules. Each module requires a lot of time to write code, which is time-consuming and labor-intensive, and seriously affects the overall software development efficiency. Moreover, for each software, it is generally necessary to design separate management models such as project management, execution management, and task management, which greatly reduces the efficiency of software development. Summary of the invention

[0005] In order to address the deficiencies in the prior art, the present invention provides a management method and system for automatic software development, which realizes the full-process management of projects, executions, tasks, requirements, tests, tools and task template groups, and can be applied to the automated development processes of different software, greatly improving software development efficiency.

[0006] In order to achieve the above object, the present invention adopts the following technical solution:

[0007] In a first aspect, the present invention provides a management method for automatic software development.

[0008] A management method for automated software development, a project management process, including:

[0009] After starting to create a project, the basic information of the project is entered and a project is created;

[0010] If the project has related executions, you can view or modify related executions; if not, create a new execution, fill in the basic execution information, and add a new execution;

[0011] If there are related tasks to be executed, you can view or modify the related tasks. If not, create a new related task. After adding the basic information of the related task and completing the new related task, you can view or modify the newly created task.

[0012] As a further limitation of the present invention, the execution management process includes: selecting a project, determining whether there is an execution, if there is an execution, viewing or modifying the execution, and then operating the execution, if there is no execution, creating a new execution, and then operating the execution; determining whether there are related tasks for the execution, if there are related tasks, viewing or modifying the related tasks, if there are no related tasks, creating a new related task, and then operating the related tasks until the execution is completed.

[0013] As a further limitation of the present invention, execution exists under a project. All new executions should be created under the project to be created. When creating a new execution, select the template group to be bound. When starting the execution, the process of the corresponding template group is executed. It supports automatic creation of tasks based on templates or manual creation of tasks.

[0014] As a further limitation of the present invention, select a project, then select execution, determine whether there are related tasks for the execution, if there are related tasks, view or modify the related tasks, if there are no related tasks, create new related tasks, and then operate the related tasks until the execution is completed.

[0015] As a further limitation of the present invention, the requirements management process includes:

[0016] Get the basic information of the added requirement and determine whether there are sub-requirements. If there are sub-requirements, add the sub-requirements and get the basic information of the sub-requirements. If there are no sub-requirements, add comments and the requirement management is completed.

[0017] As a further limitation of the present invention, the test management process includes:

[0018] Add a new test case, select the test type, add test steps, and each test step supports the option of uploading attachments. If the test result is a successful execution, the test case is added. If the test result is a failed execution, the failed test case is converted into a bug.

[0019] As a further limitation of the present invention, the tool management process includes:

[0020] Add a tool and select the tool type. If the tool type is a command tool, add the tool ssh input and output address. If the tool type is web or third-party, add the tool ssh input and output address and tool address, and then add the input and output parameter list. When adding, select the variable type and give the variable name. After adding the input and output list, add the script and the tool creation is complete.

[0021] As a further limitation of the present invention, the task template group management process includes:

[0022] Create a new template group and create a template under the current template group. The task template can be a plural task, a singular task, or a task subgroup. When creating a plural task template, add script content to the pre-script. If creating a template subgroup, select another template group; fill in the basic information of the template. The template group represents a process, and the templates are connected in series through the dependency relationship between templates.

[0023] As a further limitation of the present invention, a template calls multiple tools. The tools have set the variables that need to be input when they are designed and created. The template needs to add tools and input resources for use when the tools are executed. The input resources are divided into two types: one is manual input. After the task is created according to the template, the specific variables are selected when the task is started. The other is to select the input and output variables of other templates under the same template group and bind them directly;

[0024] When adding a tool, select the tool you want to use, the system will automatically display the input variable name of the tool, and then set the variables in the template input resource directly after the tool variable name;

[0025] First define the variable name, then set the variable corresponding to the variable name. The output resource selection is manual input and tool output.

[0026] In a second aspect, the present invention provides a management system for automatic software development.

[0027] A management system for automatic software development, comprising:

[0028] The project management process module is configured as follows: after starting to create a project, after the basic information of the project is entered, a project is created. If the project has related executions, it supports viewing or modifying the related executions; if not, a new execution is created. After filling in the basic execution information, a new execution is added. If the execution has related tasks, it supports viewing or modifying the related tasks. If not, a new related task is created. After adding the basic information of the related tasks and completing the new related tasks, it supports viewing or modifying the new tasks.

[0029] The execution management process module is configured as follows: select a project, determine whether there is an execution, if there is an execution, view or modify the execution, and then operate the execution, if there is no execution, create a new execution, and then operate the execution; determine whether there is a related task for the execution, if there is a related task, view or modify the related task, if there is no related task, create a new related task, and then operate the related task until the execution is completed;

[0030] The task management module is configured to: select a project, then select execution, determine whether there are related tasks for the execution, if there are related tasks, then view or modify the related tasks, if there are no related tasks, then create a new related task, and then operate the related tasks until the execution is completed;

[0031] The requirement management module is configured to: obtain basic information of the added requirement, determine whether there is a sub-requirement, if there is a sub-requirement, add the sub-requirement, and obtain basic information of the sub-requirement; if there is no sub-requirement, add a comment, and the requirement management is completed;

[0032] The test management module is configured as follows: add a new test case, select a test type, add test steps, each test step supports the option of uploading attachments, if the test result is a successful execution, then the test case is added, if the test result is a failed execution, then the failed test case is converted into a bug;

[0033] The tool management module is configured as follows: add a tool, select the tool type, if the tool type is a command tool, add the tool ssh input and output address, if the tool type is web or third-party, add the tool ssh input and output address and tool address, then add the input and output parameter list, select the variable type and give the variable name when adding, after adding the input and output list, add the script, and the tool creation is completed;

[0034] The task template group management module is configured as follows: create a new template group, create a template under the current template group, the task template is a plural task, a singular task or a task subgroup. To create a plural task template, you need to add script content to the front script. If you create a template subgroup, select another template group and fill in the basic information of the template. The template group represents a process, and the templates are connected in series through the dependency relationship between templates.

[0035] Compared with the prior art, the present invention has the following beneficial effects:

[0036] The present invention innovatively proposes a management method and system for automatic software development, which realizes the full-process management of projects, executions, tasks, requirements, tests, tools and task template groups, can be applied to the automated development processes of different software, and greatly improves software development efficiency.

[0037] Advantages of additional aspects of the present invention will be given in part in the following description, and in part will become obvious from the following description, or will be learned through practice of the present invention. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] The accompanying drawings in the specification, which constitute a part of the present invention, are used to provide a further understanding of the present invention. The exemplary embodiments of the present invention and their descriptions are used to explain the present invention and do not constitute improper limitations on the present invention.

[0039] Figure 1 A schematic diagram of a project management process provided in Example 1 of the present invention;

[0040] Figure 2A schematic diagram of the execution management process provided by Embodiment 1 of the present invention;

[0041] Figure 3 A schematic diagram of a task management process provided in Example 1 of the present invention;

[0042] Figure 4 A schematic diagram of a demand management process provided by Embodiment 1 of the present invention;

[0043] Figure 5 A schematic diagram of a test management process provided in Example 1 of the present invention;

[0044] Figure 6 A schematic diagram of a tool management process provided in Example 1 of the present invention;

[0045] Figure 7 A schematic diagram of the task template group management process provided in Example 1 of the present invention. DETAILED DESCRIPTION

[0046] The present invention will be further described below in conjunction with the accompanying drawings and embodiments.

[0047] It should be noted that the following detailed descriptions are exemplary and are intended to provide further explanation of the present invention. Unless otherwise specified, all technical and scientific terms used herein have the same meanings as those commonly understood by those skilled in the art to which the present invention belongs.

[0048] In the absence of conflict, the embodiments of the present invention and the features of the embodiments may be combined with each other.

[0049] Embodiment 1:

[0050] This implementation proposes a management method for automatic software development, including a project management process, such as Figure 1 As shown, specifically, it includes: click Create Project, enter the basic information of the project as required, click Create, and a project is created; if the project has related executions, you can view or modify the related executions; if not, you can create a new execution, fill in the basic execution information, and add a new execution to complete; if the execution has related tasks, you can view or modify the tasks, if not, you can create a new task, and after adding the basic task information, the new task is completed.

[0051] like Figure 2 As shown, in execution management, you can add, delete, modify and check executions. Executions exist under projects. All new executions should be created under the project to be created. When creating a new execution, you can select the template group to be bound. In this way, when the execution is started, the process of the corresponding template group will be executed. Tasks can be created automatically according to the template, or they can be created manually.

[0052] like Figure 3As shown, when managing tasks, first select the project and execution, and the related tasks under the project and execution will be displayed. If there are any, you can view and modify them. If not, create a new task.

[0053] like Figure 4 As shown, in the demand management process, click Add Requirement, fill in the basic information of the requirement, determine whether the requirement has sub-requirements, if so, create sub-requirements, and then add the basic information of the sub-requirements. After adding the requirement, you can add multiple comments.

[0054] like Figure 5 As shown, in the test management process, add a new test case, select the test type, add test steps, and choose to upload attachments for each test step. If the test result is a successful execution, the test case is added. If the test result is a failed execution, the failed test case can be converted into a bug.

[0055] like Figure 6 As shown, in the tool management process, first add the tool, then select the tool type. If the tool type is a command tool, you only need to add the tool ssh input and output address. If the tool type is web or third-party, in addition to adding the tool ssh input and output address, you also need to add the tool address; then add the input and output parameter list. When adding, select the variable type and give the variable name; after adding the input and output list, add the script and the tool creation is complete.

[0056] like Figure 7 As shown, in the task template group management module, create a new template group and create a template under the current template group. Task templates can be plural tasks, singular tasks, and task subgroups. To create plural task templates, you need to add script content in the front script. If you create a template subgroup, you need to select another template group and then add some basic information about the template. The template group represents a process, which is connected in series through the dependency relationship between templates. Therefore, when creating a template, if you need to connect it in series with other templates, you need to add template dependencies.

[0057] Add input resources: A template can call multiple tools. The variables that need to be input have been set when the tool is designed and created. Therefore, if a template wants to add a tool, it must add input resources for use when the tool is executed. There are two types of input resources. One is manual input. After creating a task according to the template, start the task and then select specific variables. The other is to select the input and output variables of other templates in the same template group and bind them directly.

[0058] Add tool: When adding a tool, select the tool you want to use, and the system will automatically display the input variable name of the tool. Then you can directly set the variables in the template input resource after the tool variable name;

[0059] Add output resources: Just like adding input resources, you can first define the variable name, and then set the variable corresponding to the variable name. The difference from input resources is that input resources can choose manual input and input and output of other templates, while output resources can choose manual input and tool output.

[0060] In this implementation, the system interfaces are also designed, including: login interface, project management interface, execution management interface, user management interface, task management interface, template management interface, template group management interface, requirement management interface, adapter interface, task log management interface, test management interface, template dependency management interface, task comment management interface, test step management interface, bug management interface, tool management interface and template resource query interface.

[0061] Among them, the external interfaces are the requirement management interface, adapter interface, test step management interface and bug management interface; the internal interfaces are the project management interface, execution management interface, user management interface, task management interface, template management interface, template group management interface, task log management interface, test management interface, template dependency management interface, task comment management interface, tool management interface and template resource query interface.

[0062] The login interface is designed as follows: when a user logs in to the system, the system will perform two parts of verification, one is verification code verification, and the other is user authority verification. Verification code verification process: the login page displays a random verification code, and the user enters the verification code. If the verification code is correct, the verification is passed. Otherwise, the verification code needs to be re-entered until the verification code is correct. The verification code is implemented by saving the verification code value on the server through the session. The verification code information is carried when the front end is submitted, and the server verifies and clears it.

[0063] The process of user authority verification: (1) The user enters the username and password to log in, and the background verifies the username and password. If the verification is successful, a token is returned to the front end. The token is generated by TokenService using the better-performing ThreadLocalRandom to generate a random UUID, and then the sessionId (i.e., UUID) is used as the key and the user login information loginUser is saved in redis. The token validity period is refreshed and a token (i.e., JwtToken) containing the sessionId is generated; (2) After the front end receives the token, it sends a request with the token to access the corresponding interface; (3) After the interface receives the request, it uses the token for identity authentication to determine whether the user has the authority to access the interface; (4) If the user has the authority, the interface will return the corresponding data to the front end; if not, the interface will return a status code of 401 or 403 to the front end, indicating that the user has no access.

[0064] In this implementation, a module calling method based on a task manager is also provided. The task manager calls to create a task according to a template and sends the task creation instruction to the StackStorm platform. The StackStorm platform feeds back the task creation completion instruction to the task manager; the task starts automatically, the task manager queries the tool manager for the tool used in the template, and the tool manager sends the queried tool to the task manager; the task manager pulls resources and stores the pulled resources in the resource manager and the tool manager. The tool manager sends the queried tool and the parameters sent by the task manager to the adapter for execution adaptation; the adapter returns the execution result directly to the task manager, and the task manager stores the execution result in the resource manager; the task manager sends a task completion instruction to the StackStorm platform. After the StackStorm platform completes the specified action, it switches the task status and feeds back to the task manager; or, the task manager sends a task closing instruction to the StackStorm platform. After the StackStorm platform completes the specified action, it switches the task status and feeds back to the task manager.

[0065] In this implementation, the task manager is the core of the system scheduling. The system regards all tasks as an AOV directed graph. Each node in the graph is a task. The dependency between tasks is represented by edges. If task A has an edge pointing to task B, it means that task B depends on task A. If there are two edges pointing to B, (A, B) and (C, B), then A and C need to be completed before B can be started.

[0066] In order to reuse the process, the dependencies between tasks are defined as task template groups. Task template groups are composed of multiple task templates and the relationships between task templates. When creating an iteration of a project, you can specify a task template group. The system will dynamically create a directed graph of tasks based on the task template group.

[0067] In order to realize pipeline operation, the system stipulates that only when the conditions for task execution are met, the task will be actually created and visible to users. This ensures that the tasks visible to users are currently available. This requires the system to dynamically create tasks based on the task template group.

[0068] At the beginning of an iteration of agile development, the system will analyze whether the templates in the task template group have dependencies based on the AOV directed graph in the task template group, and then create a task based on the information in the task template. After the task is created, resources will be prepared for the task according to the definition in the task template, such as source code required for compilation tasks. After the task manager calls the resource manager to prepare the resources, if it is an automatic task, it calls the tool manager to execute the tool according to the tool specified by the task. If it is a manual task, it waits for the task to be started manually.

[0069] In this implementation, the tool manager provides tool management and invocation. Specifically, a tool is a type of entity managed by the system, which allows users to register multiple tools on the platform. The tool adapter is used as a microservice, and the name of the microservice can be configured to the system through configuration; when the tool is online, the tool will be registered with Nacos; when the tool is used, the tool manager will query the corresponding tool in Nacos and call the tool according to the adapter interface.

[0070] In this implementation, the tool manager provides a set of interface standards through which tools can complete tool integration. When integrating third-party tools, the third-party tool format should be converted into the platform tool format, and the adapter is used to complete this conversion operation.

[0071] In this implementation, the adapter calling process is the process of integrating the adapter into the system as a third-party tool. The process is as follows:

[0072] (1) Get the ssh address of the tool based on toolId, that is, copy the resource to the address of the tool;

[0073] (2) Get the template input according to the execution id and template id, which corresponds to the output resource of the previous template (a resource array storageList);

[0074] (3) Copy the acquired resources to the local tool, i.e., resource migration: traverse the resource array storageList, use the fetchById function in StorageServiceImpl, and find the corresponding resources in the app_storage table through storageId;

[0075] (4) Call the fetch function to get the corresponding resource type type, then compare the resource type. If it is a string, return it directly; if it is a git type, first determine whether localPath is empty. If it is empty, it means that there is no such repository and the repository needs to be cloned. If it is not empty, it only needs to be pulled; if it is a file type, copy the file to the tool path;

[0076] (5) Get the resource again, call the queryParamValue function to get the input parameter list and script required to call the tool, call the start interface of the tool management through FeignClient, and then call the corresponding tool.

[0077] In this implementation, the resource storage implements the centralized management of input data, intermediate data, and output data in the system. The core value of the resource storage lies in data migration in addition to data storage. When the system calls a tool, it needs to provide data support for the tool. At this time, the resource storage automatically places the resource in the specified directory through the resource ID and the target location, realizing the automatic acquisition of resources according to the ID. After the tool generates the result, it submits the data to the storage service. The resource storage in this implementation supports several data types such as code base, files, and folders.

[0078] In this implementation, the StackStorm platform is an event-driven automation system. In the software system, there are multiple tools, each of which can generate events and complete actions. The software uses rule files to implement the binding between events and actions. Events and actions are not limited to the same task. For example, when an event is triggered after a tool is executed, this event can trigger the start of other tools.

[0079] In this implementation, the entire pipeline system can be viewed as a multi-layer AOV directed graph, with the top layer consisting of the top-level activities and the relationships between activities. The system uses template groups to describe the AOV directed graph of "activities"; because the tasks of the system are dynamically generated, simply visualizing the tasks cannot present the entire process. Combining task templates and tasks can reveal which tasks have been started (some have not yet been created), and visualize the completion status, time, personnel information, and input and output information of the tasks.

[0080] This implementation also provides the function of achievement library management. The achievement library includes the management of controlled libraries and product libraries. The achievement in the system is actually a screening and classification management of resource libraries. A large number of intermediate resources will be generated during the development process. Many of these resources are useless to managers. Therefore, by marking the resources, useful resources can be managed in the form of achievement libraries, providing users with a management interface.

[0081] For the storage of results, different types of results are stored in different ways. Specifically, if a task is a compilation task, a git code library is obtained after the task is completed by calling the compilation tool. The results of this task are stored in the resource table as a data type of code library.

[0082] The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. For those skilled in the art, the present invention may have various modifications and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention shall be included in the protection scope of the present invention.

Claims

1. A management method for automatic software development, characterized in that: Project management process, including: After starting to create a project, the basic information of the project is entered and a project is created; If the project has related executions, you can view or modify related executions; if not, create a new execution, fill in the basic execution information, and add a new execution; If there are related tasks to be executed, you can view or modify the related tasks. If there are no related tasks, you can create a new related task. After adding the basic information of the related task and completing the new related task, you can view or modify the new task. Task template group management process, including: Create a new template group. Create a template under the current template group. The task template can be a plural task, a singular task, or a task subgroup. When creating a plural task template, add script content to the pre-script. If you create a template subgroup, select another template group. Fill in the basic information of the template. The template group represents a process. The templates are connected in series through the dependency relationship between templates. A template calls several tools. The tools have already set the variables that need to be input when they are designed and created. The template needs to add tools and input resources for use when the tools are executed. There are two types of input resources: one is manual input. After creating a task according to the template, start the task and then select specific variables. The other is to directly bind the input and output variables of other templates in the same template group. When adding a tool, select the tool you want to use, the system will automatically display the input variable name of the tool, and then set the variables in the template input resource directly after the tool variable name; First define the variable name, then set the variable corresponding to the variable name. The output resource selection is manual input and tool output; The task manager is the core of system scheduling. The system regards the task as an AOV directed graph. It adopts a module calling method based on the task manager. The task manager calls to create tasks according to the template and sends the task creation instructions to the StackStorm platform. The StackStorm platform feeds back the task creation completion instructions to the task manager. The task starts automatically. The task manager queries the tool manager for the tools used in the template, and the tool manager sends the queried tools to the task manager. The task manager pulls resources and stores the pulled resources in the resource manager and the tool manager. The tool manager sends the queried tools and the parameters sent by the task manager to the adapter for execution adaptation. The adapter returns the execution results to the task manager, and the task manager stores the execution results in the resource manager. The task manager sends the completion / close task instructions to the StackStorm platform. After the StackStorm platform completes the specified action, it switches the task status and feeds back to the task manager.

2. The management method for automatic software development according to claim 1, characterized in that: Execute management processes, including: Select a project and determine whether it has been executed. If it has been executed, view or modify the execution and then operate the execution. If it has not been executed, create a new execution and then operate the execution. Determine whether the execution has related tasks. If it has related tasks, view or modify the related tasks. If it does not have related tasks, create a new related task and then operate the related tasks until the execution is completed.

3. The management method for automatic software development according to claim 2, characterized in that: Executions exist under projects. All new executions should be created under the project to be created. When creating a new execution, select the template group to be bound. When starting the execution, the process of the corresponding template group is executed. It supports automatic creation of tasks based on templates or manual creation of tasks.

4. The management method for automatic software development according to claim 1, characterized in that: Task management process, including: Select a project, then select Execute to determine whether there are any related tasks for the execution. If there are related tasks, view or modify the related tasks. If there are no related tasks, create new related tasks and then operate the related tasks until the execution is completed.

5. The management method for automatic software development according to any one of claims 1 to 4, characterized in that: Requirements management process, including: Get the basic information of the added requirement and determine whether there are sub-requirements. If there are sub-requirements, add the sub-requirements and get the basic information of the sub-requirements. If there are no sub-requirements, add comments and the requirement management is completed.

6. The management method for automatic software development according to any one of claims 1 to 4, characterized in that: Test management process, including: Add a new test case, select the test type, add test steps, and each test step supports the option of uploading attachments. If the test result is a successful execution, the test case is added. If the test result is a failed execution, the failed test case is converted into a bug.

7. The management method for automatic software development according to any one of claims 1 to 4, characterized in that: Tool management process, including: Add a tool and select the tool type. If the tool type is a command tool, add the tool ssh input and output address. If the tool type is web or third-party, add the tool ssh input and output address and tool address, and then add the input and output parameter list. When adding, select the variable type and give the variable name. After adding the input and output list, add the script and the tool creation is complete.

8. A management system for automatic software development, using the management method for automatic software development according to any one of claims 1 to 7, characterized in that: include: The project management process module is configured as follows: after starting to create a project, after the basic information of the project is entered, a project is created. If the project has related executions, it supports viewing or modifying the related executions; if not, a new execution is created. After filling in the basic execution information, a new execution is added. If the execution has related tasks, it supports viewing or modifying the related tasks. If not, a new related task is created. After adding the basic information of the related tasks and completing the new related tasks, it supports viewing or modifying the new tasks. The execution management process module is configured as follows: select a project, determine whether there is an execution, if there is an execution, view or modify the execution, and then operate the execution, if there is no execution, create a new execution, and then operate the execution; determine whether there is a related task for the execution, if there is a related task, view or modify the related task, if there is no related task, create a new related task, and then operate the related task until the execution is completed; The task management module is configured to: select a project, then select execution, determine whether there are related tasks for the execution, if there are related tasks, then view or modify the related tasks, if there are no related tasks, then create a new related task, and then operate the related tasks until the execution is completed; The requirement management module is configured to: obtain basic information of the added requirement, determine whether there is a sub-requirement, if there is a sub-requirement, add the sub-requirement, and obtain basic information of the sub-requirement; if there is no sub-requirement, add a comment, and the requirement management is completed; The test management module is configured as follows: add a new test case, select a test type, add test steps, each test step supports the option of uploading attachments, if the test result is a successful execution, then the test case is added, if the test result is a failed execution, then the failed test case is converted into a bug; The tool management module is configured as follows: add a tool, select the tool type, if the tool type is a command tool, add the tool ssh input and output address, if the tool type is web or third-party, add the tool ssh input and output address and tool address, then add the input and output parameter list, select the variable type and give the variable name when adding, after adding the input and output list, add the script, and the tool creation is completed; The task template group management module is configured as follows: create a new template group, create a template under the current template group, the task template is a plural task, a singular task or a task subgroup. To create a plural task template, you need to add script content to the front script. If you create a template subgroup, select another template group and fill in the basic information of the template. The template group represents a process, and the templates are connected in series through the dependency relationship between templates.

Images