Timing starting method and system for realizing workflow double circulation

Abstract

The invention provides a timed starting method and system for achieving workflow double circulation, the method is applied to a process engine, and the method comprises the steps that outer circulation data corresponding to a target task is added into a timed task table of the process engine; the outer circulation data is obtained from a process definition file; before the timing starting time is reached, adding the internal circulation data corresponding to the target task into the timing task table; the internal loop data is obtained from the process definition file, and the internal loop data comprises the timing starting time, the execution period, the task instance and the number of cycles; and executing the task instance once every execution period from the timing starting time until the number of times of executing the task instance reaches the cycle number. The application supports dual-cycle timing start tasks, and improves the use experience.

Description

Technical Field

[0001] This application relates to the technical field of data processing, and specifically relates to a timing start method and system for implementing a double loop in a workflow. Background Art

[0002] The Flowable engine is an open-source workflow and BPM (Business Process Management) platform that provides a lightweight BPMN (Business Process Model and Notation) 2.0 process engine for modeling, executing, and managing business processes to provide a more flexible and scalable BPM solution.

[0003] The Flowable engine is applicable to various scenarios that require process automation. By using Flowable, organizations can improve the efficiency and transparency of business processes while reducing costs and complexity.

[0004] However, the timing start component of the Flowable engine only supports one-way loops. Summary of the Invention

[0005] An embodiment of this application provides a timing start method for implementing a double loop in a workflow, which supports double loop timing start tasks and improves the user experience.

[0006] In a first aspect, an embodiment of this application provides a timing start method for implementing a double loop in a workflow, which is applied to a process engine. The method includes:

[0007] Adding the outer loop data corresponding to the target task to the timing task table of the process engine; the outer loop data is obtained from the process definition file;

[0008] Before the arrival of the timing start time, adding the inner loop data corresponding to the target task to the timing task table; the inner loop data is obtained from the process definition file, and the inner loop data includes the timing start time, execution period, task instance, and number of loops;

[0009] Executing the task instance once every execution period starting from the timing start time until the number of times the task instance is executed reaches the number of loops.

[0010] In some embodiments, before adding the outer loop data corresponding to the target task to the timing task table of the process engine, it includes:

[0011] Saving the outer loop data and the inner loop data to the process definition file.

[0012] In some embodiments, after the task instance is executed once every execution period according to the timing start time until the number of times of executing the task instance reaches the number of loops, it includes:

[0013] Deleting the inner loop data in the timing task table.

[0014] In some embodiments, the outer loop data includes a timing start time and a timing end time, and the inner loop data is added to the timing task table every time before the timing start time during the timing start time and the timing end time.

[0015] In some embodiments, the inner loop data further includes a timing termination time, and the number of loops is equal to the quotient obtained by dividing the time difference between the timing start time and the timing termination time as the dividend by the execution period as the divisor.

[0016] In a second aspect, the present application further provides a timing start system for implementing a workflow double loop, which is applied to a process engine. The system includes:

[0017] A processing module, configured to add the outer loop data corresponding to the target task to the timing task table of the process engine; the outer loop data is obtained from a process definition file;

[0018] The processing module is further configured to add the inner loop data corresponding to the target task to the timing task table before the timing start time; the inner loop data is obtained from the process definition file, and the inner loop data includes the timing start time, the execution period, the task instance, and the number of loops;

[0019] An execution module, configured to execute the task instance once every execution period starting from the timing start time until the number of times of executing the task instance reaches the number of loops.

[0020] In some embodiments, it further includes:

[0021] A storage module, configured to save the outer loop data and the inner loop data to the process definition file.

[0022] In some embodiments, the execution module is further configured to execute the task instance once every execution period starting from the timing start time until the number of times of executing the task instance reaches the number of loops, and then delete the inner loop data in the timing task table.

[0023] In some embodiments, the outer loop data includes a timing start time and a timing end time, and the inner loop data is added to the timing task table every time before the timing start time during the timing start time and the timing end time.

[0024] In some embodiments, the inner loop data further includes a timing termination time, and the number of loops is equal to the quotient obtained by dividing the time difference between the timing start time and the timing termination time as the dividend by the execution period as the divisor.

[0025] A timing start method and system for implementing a workflow double loop provided by an embodiment of the present application add the outer loop data corresponding to a target task to the timing task table of the process engine; the outer loop data is obtained from a process definition file; before the timing start time arrives, the inner loop data corresponding to the target task is added to the timing task table; the inner loop data is obtained from the process definition file, and the inner loop data includes the timing start time, the execution period, the task instance, and the number of loops; starting from the timing start time, the task instance is executed once every execution period until the number of times the task instance is executed reaches the number of loops. The present application starts tasks with double loop timing, improving the usage experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0026] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the following will briefly introduce the drawings required for the description of the embodiments. Obviously, the drawings in the following description are only some embodiments of the present application. For those skilled in the art, without creative efforts, other drawings can be obtained based on these drawings.

[0027] Figure 1 Shows a flowchart of some exemplary timing start methods for implementing a workflow double loop;

[0028] Figure 2 Shows a scenario flowchart of some exemplary timing start methods for implementing a workflow double loop. DETAILED DESCRIPTION

[0029] The following will clearly and completely describe the technical solutions in some embodiments of the present application with reference to the drawings. Obviously, the described embodiments are only some embodiments of the present application, rather than all embodiments. Based on the embodiments provided by the present application, all other embodiments obtained by those of ordinary skill in the art belong to the scope of protection of the present application.

[0030] Unless the context otherwise requires, throughout the specification and claims, the term "comprising" is to be construed in an open, inclusive sense, i.e., "including, but not limited to". In the description of the specification, the terms "one embodiment", "some embodiments", "exemplary embodiments", "exemplarily" or "some examples", etc. are intended to indicate that a particular feature, structure, material or characteristic related to the embodiment or example is included in at least one embodiment or example of the present application. The schematic representations of the above terms do not necessarily refer to the same embodiment or example. In addition, the specific features, structures, materials or characteristics described above may be included in any one or more embodiments or examples in any appropriate manner.

[0031] Hereinafter, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the quantity of the indicated technical features. Thus, features defined with "first" and "second" may explicitly or implicitly include one or more of such features. In the description of the embodiments of the present application, unless otherwise stated, the meaning of "a plurality" is two or more.

[0032] "At least one of A, B, and C" has the same meaning as "at least one of A, B, or C", and both include the following combinations of A, B, and C: only A, only B, only C, the combination of A and B, the combination of A and C, the combination of B and C, and the combination of A, B, and C.

[0033] "A and / or B" includes the following three combinations: only A, only B, and the combination of A and B.

[0034] In addition, the use of "based on" means open and inclusive, because a process, step, calculation or other action "based on" one or more of the stated conditions or values may, in practice, be based on additional conditions or values other than those stated.

[0035] As used in the present application, "about", "substantially" or "approximately" includes the stated value and the average value within an acceptable deviation range of the specific value, where the acceptable deviation range is determined by those of ordinary skill in the art considering the measurement being discussed and the errors associated with the measurement of the specific quantity (i.e., the limitations of the measurement system).

[0036] Flowable fully supports the BPMN 2.0 specification. Flowable provides a powerful process engine for executing defined business processes. Flowable has a built-in form engine that can be used to create and manage forms in business processes. Flowable also provides a decision engine for executing complex business rules and decisions. Flowable allows tasks to be executed outside of the process, which is very useful for integrating external systems and applications. Flowable provides rich APIs that can be easily integrated with other systems and applications. Flowable allows developers to customize and extend its functionality to meet specific business requirements. As an open-source project, Flowable has an active community and also offers commercial support options. Flowable aims to be lightweight while providing high-performance process execution capabilities. Flowable is applicable to various scenarios that require process automation, including but not limited to enterprise resource planning (ERP), customer relationship management (CRM), supply chain management (SCM), etc. By using Flowable, organizations can improve the efficiency and transparency of business processes while reducing costs and complexity. However, the timed start component of Flowable only supports one-way loop timed starts, and the one-way loop limits the flexibility of process designers when creating complex business logics. In scenarios that require multiple loop conditions or nested loops, this limitation may prevent the realization of the expected business process design. For complex business processes that require multiple loop conditions to be controlled simultaneously, the one-way loop timed start component may not meet the requirements. When business requirements change and the loop logic needs to be adjusted, the one-way loop limitation may lead to difficulties in maintenance because it may be necessary to reconstruct the entire process or introduce additional components to adapt to the new loop requirements. In short, the timed start component of Flowable cannot handle multiple loop conditions or nested loops simultaneously.

[0037] The following describes the method and system for implementing the timed start of a workflow double loop in conjunction with the accompanying drawings of the specification to solve the above problems.

[0038] Refer to Figure 1 as shown Figure 1 which shows a schematic flowchart of some exemplary methods for implementing the timed start of a workflow double loop. The method for implementing the timed start of a workflow double loop is applied to a process engine, as Figure 1 shown, the method for implementing the timed start of a workflow double loop includes the steps:

[0039] S100. Add the outer loop data corresponding to the target task to the timed task table of the process engine; the outer loop data is obtained from the process definition file;

[0040] S200. Before reaching the timing start time, add the inner loop data corresponding to the target task to the timing task table; the inner loop data is obtained from the process definition file, and the inner loop data includes the timing start time, execution period, task instance, and number of loops.

[0041] S300. Starting from the timing start time, execute the task instance once every execution period until the number of times the task instance is executed reaches the number of loops.

[0042] Specifically, the process engine is the Flowable engine. The Flowable engine is a tool that helps organizations automate and optimize their business processes. The Flowable engine allows the use of the XML format to define the business processes of target tasks. The format of the process definition file is XML (eXtensible Markup Language). The process definition file defines the various steps, conditions, events, etc. of the entire process of the target task. There are two loop structures in the process definition, an outer loop and an inner loop. The process instance corresponding to the inner loop is nested within the process instance corresponding to the outer loop. For example, the process instance corresponding to the outer loop may be based on a date range (such as from September 15th to October 20th), while the process instance corresponding to the inner loop may be based on a shorter time interval (such as every 10 minutes).

[0043] The Flowable engine can find the outer loop data corresponding to the target task from the process definition file. The Flowable engine can find the inner loop data corresponding to the target task from the process definition file. The Flowable engine can parse the process definition file to obtain the timing start time, execution period, task instance, and number of loops in the inner loop data. The Flowable engine adds the found outer loop data to the timing task table (i.e., ACT_RU_TIMER_JOB) of the process engine. Then, within the time range specified by the outer loop data, before reaching the timing start time of the inner loop process instance specified by the inner loop data, the Flowable engine will find the inner loop data corresponding to the target task from the process definition file and add it to the timing task table (i.e., ACT_RU_TIMER_JOB) of the process engine. After that, the Flowable engine can trigger the execution of the process instance according to the data recorded in the timing task table (i.e., ACT_RU_TIMER_JOB) at the set execution period (i.e., time interval).

[0044] For example, in a production workshop, from September 1, 2024 to October 15, 2024, a process instance for Flowable heartbeat detection needs to be initiated every 10 minutes starting at 10 am every day and stop initiating processes at 6 pm. The process instance corresponding to the inner loop is to execute a task instance every 10 minutes from 10 am to 6 pm, and the task instance is Flowable heartbeat detection. The process instance corresponding to the outer loop is from September 1, 2024 to October 15, 2024.

[0045] In some embodiments, before adding the outer loop data corresponding to the target task to the timed task table of the process engine, it includes:

[0046] Save the outer loop data and the inner loop data to the process definition file.

[0047] Specifically, define two different timed events, one is the outer loop of the timed event based on the date range, and the other is the inner loop of the timed event based on the time interval. The two timed events can be converted into an XML file using the API provided by the Flowable engine.

[0048] In some embodiments, after executing the task instance once every execution period according to the timed start time until the number of times of executing the task instance reaches the loop times, it includes:

[0049] Delete the inner loop data in the timed task table.

[0050] Specifically, in the Flowable workflow management system, the timed task table (such as the ACT_RU_TIMER_JOB table) is used to store and manage timed tasks, which are usually associated with timer events in the process. When the inner loop ends, the inner loop data will be deleted from the ACT_RU_TIMER_JOB table. Since timed tasks will occupy database resources and system resources, deleting the records of the inner loop data can release these resources, and the released resources can be used to process new or more important tasks, thereby improving system performance. Deleting the completed inner loop data helps to keep the database clean and consistent, avoid data redundancy, and ensure that only the currently valid task records are retained in the database. The present application deletes the completed inner loop data in the ACT_RU_TIMER_JOB table to ensure the efficiency, accuracy, and compliance of the workflow management system.

[0051] In some embodiments, the outer loop data includes a timed start time and a timed end time, and the inner loop data is added to the timed task table every time before the timed start time during the timed start time and the timed end time.

[0052] Specifically, during the scheduled start time and the scheduled end time, the Flowable engine will repeatedly add the inner loop data to the scheduled task table before the scheduled start time for multiple times, and will repeatedly delete the added inner loop data in the scheduled task table after the execution times of the task instances in the inner loop reach the loop times, that is, reach the scheduled termination time.

[0053] In some embodiments, the inner loop data further includes a scheduled termination time, and the loop times is equal to the quotient obtained by dividing the time difference between the scheduled start time and the scheduled termination time as the dividend by the execution period as the divisor.

[0054] Specifically, subtract the scheduled start time from the scheduled termination time to obtain the time difference, and divide the time difference by the execution period to obtain the loop times.

[0055] For example, in the Flowable engine, both the ACT_RU_TIMER_JOB table and the ACT_RU_JOB table are related to the execution of timed tasks, but they each play different roles. The ACT_RU_TIMER_JOB table, i.e., the timed task table, is used to store information about timed tasks, including the type of task, the scheduled execution time (DUEDATE_ field), etc. The timed task table is mainly used to save those tasks that are planned to be executed at a certain time in the future. These timed tasks are stored in this table before reaching the scheduled time. The ACT_RU_JOB table, i.e., the execution task table, is used to store tasks that can be executed immediately. When the time of the timed task arrives, the Flowable engine will automatically move these timed tasks from the ACT_RU_TIMER_JOB table to the ACT_RU_JOB table. Once the task is moved to the ACT_RU_JOB table, the Flowable engine will immediately execute these timed tasks. Since the timed tasks in the ACT_RU_JOB table will be executed immediately, when the timed task reaches the set time, the Flowable engine can automatically move these timed tasks from the ACT_RU_TIMER_JOB table to the ACT_RU_JOB table because there is no need to check the scheduled time again, which can improve the execution efficiency and performance. When the timed task reaches the set time, the Flowable engine can automatically move these timed tasks from the ACT_RU_TIMER_JOB table to the ACT_RU_JOB table. The Flowable engine can better manage the state of the tasks, distinguish which tasks are to be executed and which are in the plan. In addition, it can also avoid repeated execution in the ACT_RU_TIMER_JOB table due to time matching, and can also help keep the ACT_RU_TIMER_JOB table clean, reduce unnecessary data accumulation, and facilitate the maintenance and optimization of database performance. In short, the automatic transfer of timed tasks from ACT_RU_TIMER_JOB to ACT_RU_JOB ensures that the timed tasks can be executed on time while maintaining the efficiency and orderliness of the database.

[0056] Exemplarily, Figure 2 The flowchart shows some exemplary heartbeat detection implementation workflows for the timed start method, such as Figure 2As shown, the data of the double loop (i.e., the outer loop data and the inner loop data) is recorded in the XML file defined by the process. The outer loop data defined in the XML file from September 15th to October 20th is searched and recorded in the scheduled task table. The scheduled task adds the inner loop data of today to the ACT_RU_TIMER_JOB table of the Flowable engine every day at midnight. The Flowable engine initiates a process instance every execution cycle according to the scheduled start time in the ACT_RU_TIMER_JOB record, and deletes the record of the inner loop data after the inner loop ends. Among them, the inner loop data is:

[0057] < / timerEventDefinition>;

[0058] <timecycle>R48 / PT10M< / timecycle> ;

[0059] <timedate>${StartDate}< / timedate> ;

[0060] .

[0061] It can be passed through <timereventdefinition>An element is used to define a timer event, and this element can contain <timedate>and <timecycle>The sub - element, the value in the timeDate tag is the start time of the scheduled start. In the value of the timeCycle tag, R48 represents 48 cycles, and PT10M means a time period with a duration of 10 minutes to initiate a task instance. After the deployment and release of this inner - loop data and other processes, data will be added to the underlying database ACT_RU_TIMER_JOB of Flowable, and the structure is as follows in the table:

[0062]

[0063]

[0064] Table 1, the structure of the inner - loop data.

[0065] The two most critical fields in the structure are DUE_DATE_ and REPEAT_. The Flowable engine will initiate a process instance at DUE_DATE_. After the process instance is initiated, the R48 / PT10M in the REPEAT_ field will be changed to R47 / PT10M. This will continue until the data corresponding to DUE_DATE_ and REPEAT_ is finally deleted. A scheduled task in this application executes the data of the outer loop (i.e., during the period from September 1, 2024 to October 15, 2024) according to the xml definition of the process. The scheduled task adds inner - loop data every night. When the outer loop ends on the last day, the inner loop stops tracking and adding records, realizing a double - loop scheduled start task.

[0066] In this application, by defining specific inner-loop data and outer-loop data in an XML file, the start time of a process instance can be precisely controlled to ensure that the process is executed according to a predetermined schedule. The outer-loop data and inner-loop data can be configured in the XML file, which enables flexible adjustment of the process scheduling without modifying the code or redeploying the process definition, improving the flexibility and configurability of task scheduled startup. By automatically adding the inner-loop data and outer-loop data to the ACT_RU_TIMER_JOB table, automatic startup of the process instance can be achieved, reducing manual intervention and improving efficiency. The outer-loop data and inner-loop data of the target task are both stored in the XML file, facilitating monitoring and maintenance. If the scheduled task needs to be adjusted, only the records in the XML file need to be modified. The inner loop is nested within the outer loop, which can reduce the burden on the Flowable engine. Especially when dealing with a large number of scheduled tasks, it can improve performance. The inner loop being nested within the outer loop can also separate the scheduling logic from the business logic, making the definition of the business process clearer and easier to understand and maintain. If the business requirements change and the loop logic needs to be adjusted, increasing the inner loop nested within the outer loop only requires modifying the scheduled task definition in the XML file without modifying the process logic, making the process definition more flexible and easy to expand. In summary, nesting the inner loop within the outer loop, storing the inner-loop data and outer-loop data in the XML file, and using the scheduled task mechanism of the Flowable engine to manage these loops can improve the flexibility, automation level, and performance of process management, while also reducing the maintenance cost and error rate.

[0067] In a second aspect, this application also provides a system for realizing the scheduled startup of a workflow double loop, which is applied to a process engine. The system includes:

[0068] A processing module, configured to add the outer-loop data corresponding to a target task to the scheduled task table of the process engine; the outer-loop data is obtained from a process definition file;

[0069] The processing module is further configured to add the inner-loop data corresponding to the target task to the scheduled task table before the scheduled start time; the inner-loop data is obtained from the process definition file, and the inner-loop data includes the scheduled start time, execution period, task instance, and number of loops;

[0070] An execution module, configured to execute the task instance once every the execution period starting from the scheduled start time until the number of times of executing the task instance reaches the number of loops.

[0071] This embodiment is a system embodiment corresponding to the above method embodiment. For specific content, refer to the above method embodiment and will not be elaborated here one by one.

[0072] In some embodiments, it further includes:

[0073] A storage module, configured to save the outer loop data and the inner loop data to the process definition file.

[0074] This embodiment is a system embodiment corresponding to the above method embodiment. For specific content, refer to the above method embodiment and will not be elaborated herein one by one.

[0075] In some embodiments, the execution module is further configured to execute the task instance once every execution period starting from the timing start time until the number of times of executing the task instance reaches the loop count, and then delete the inner loop data in the timing task table.

[0076] This embodiment is a system embodiment corresponding to the above method embodiment. For specific content, refer to the above method embodiment and will not be elaborated herein one by one.

[0077] In some embodiments, the outer loop data includes a timing start time and a timing end time, and the inner loop data is added to the timing task table every time before the timing start time during the period between the timing start time and the timing end time.

[0078] This embodiment is a system embodiment corresponding to the above method embodiment. For specific content, refer to the above method embodiment and will not be elaborated herein one by one.

[0079] In some embodiments, the inner loop data further includes a timing termination time, and the loop count is equal to the quotient obtained by dividing the time difference between the timing start time and the timing termination time as the dividend by the execution period as the divisor.

[0080] This embodiment is a system embodiment corresponding to the above method embodiment. For specific content, refer to the above method embodiment and will not be elaborated herein one by one.

[0081] In specific implementation, each of the above units or modules can be implemented as an independent entity, or can be combined arbitrarily to be implemented as the same or several entities. Each of the above units or modules can be applied to data collection in a supply chain management project with reference to the foregoing method embodiment and will not be elaborated herein.

[0082] Those of ordinary skill in the art can understand that all or part of the steps in the above-described various methods can be completed by instructions or by controlling relevant hardware through instructions. The instructions can be stored in a computer-readable storage medium and loaded and executed by a processor to implement the above method embodiments. Among them, the computer-readable storage medium can include: read-only memory (ROM, Read Only Memory), random access memory (RAM, Random Access Memory), magnetic disk or optical disk, etc.

[0083] In the above embodiments, the descriptions of the various embodiments have their own focuses. For the parts not detailed in a certain embodiment, reference can be made to the relevant descriptions of other embodiments. Those skilled in the art can clearly understand that for the convenience and conciseness of description, the specific working processes and the beneficial effects that can be brought by the above-described data acquisition system and its corresponding units can refer to the description of the timing calibration method in the above embodiments, and will not be elaborated herein specifically.

[0084] The above has introduced in detail a timing calibration method and system provided by the embodiments of the present application. Specific examples are used in this article to elaborate on the principle and implementation manner of the present application. The descriptions of the above embodiments are only used to help understand the method and its core idea of the present application; at the same time, for those skilled in the art, according to the idea of the present application, there will be changes in the specific implementation manner and application scope. In summary, the content of this specification should not be construed as a limitation to the present application.< / timecycle> < / timedate> < / timereventdefinition>

Claims

1. A timed start method for realizing a double-loop workflow, characterized in that: Applied to a process engine, the method comprises: Adding the outer loop data corresponding to the target task to the scheduled task table of the process engine; the outer loop data is obtained from the process definition file; Before the timing start time is reached, the inner loop data corresponding to the target task is added to the timing task table; the inner loop data is obtained from the process definition file, and the inner loop data includes the timing start time, execution cycle, task instance and number of loops; The task instance is executed once every the execution cycle starting from the timing start time until the number of executions of the task instance reaches the number of cycles.

2. The method for realizing a timed start of a double-loop workflow according to claim 1, characterized in that: Before adding the outer loop data corresponding to the target task to the scheduled task table of the process engine, the process includes: The outer loop data and the inner loop data are saved in the process definition file.

3. The method for realizing the timed start of the double-loop workflow according to claim 1, characterized in that: The step of executing the task instance once every execution period according to the timing start time until the number of executions of the task instance reaches the number of cycles includes: Delete the inner loop data in the scheduled task table.

4. The method for realizing a timed start of a double-loop workflow according to claim 1, characterized in that: The outer loop data includes a timing start time and a timing end time, and the inner loop data is added to the timing task table during the timing start time and the timing end time before the timing start time is reached.

5. The method for realizing a timed start of a double-loop workflow according to any one of claims 1 to 4, characterized in that: The inner loop data also includes a timing end time, the number of loops is equal to the time difference between the timing start time and the timing end time as the dividend, and the execution cycle is the quotient of the divisor.

6. A timed start system for realizing a double cycle of workflow, characterized in that: Applied to a process engine, the system includes: A processing module, used for adding the outer loop data corresponding to the target task to the scheduled task table of the process engine; the outer loop data is obtained from the process definition file; The processing module is further used to add the inner loop data corresponding to the target task to the scheduled task table before the scheduled start time is reached; the inner loop data is obtained from the process definition file, and the inner loop data includes the scheduled start time, execution cycle, task instance and number of loops; The execution module is used to execute the task instance once every the execution period starting from the timing start time until the number of times the task instance is executed reaches the number of cycles.

7. The timed start system for realizing a double cycle of workflow according to claim 6, characterized in that: Also includes: A storage module is used to save the outer loop data and the inner loop data into the process definition file.

8. The timed start system for realizing a double cycle of workflow according to claim 6, characterized in that: The execution module is further used to execute the task instance once every the execution period starting from the timing start time until the number of executions of the task instance reaches the number of cycles, and then delete the inner loop data in the timing task table.

9. The timed start system for realizing a double cycle of workflow according to claim 6, characterized in that: The outer loop data includes a timing start time and a timing end time, and the inner loop data is added to the timing task table during the timing start time and the timing end time before the timing start time is reached.

10. The timed start system for realizing a double cycle of workflow according to any one of claims 6 to 9, characterized in that: The inner loop data also includes a timing end time, the number of loops is equal to the time difference between the timing start time and the timing end time as the dividend, and the execution cycle is the quotient of the divisor.

Images