JP7701400B2 - Execution control device, execution control method, and execution control program - Google Patents

Description

The present invention relates to an execution control device, an execution control method, and an execution control program.

Today, as AI (Artificial Intelligence) and RPA (Robotic Process Automation) are increasingly being introduced and permeating society, routine or standard tasks are being scheduled and automated on a large scale.

Patent document 1 (JP 2015-219920 A) discloses a control system that can perform calibration so as to minimize interference with the work performed by an operator or other users.

When performing calibration, this control system acquires information for identifying the common sheet type used in the monitored printing device, determines whether the state of the printing device meets specified conditions depending on the printing volume of the printing device, and determines whether the common sheet type is held in the printing device based on the acquired information. Then, if it is determined that the specified conditions are met and that the common sheet type is held, calibration is performed by having the printing device print on the common sheet type. The results of the calibration performed using the common sheet type are applied to other sheet types. This makes it possible to perform calibration with as little disruption as possible to the work performed by the operator or other users.

Patent document 1 discloses, in paragraph 0022 and elsewhere, a technology that allows you to specify whether calibration should be scheduled or manually executed.

JP 2015-219920 A

There are cases where a specific program (flow) such as background processing fails to execute. This execution failure can be caused by a variety of factors, from the application layer to the physical layer, such as problems with business masters, configuration errors, and environmental problems. Identifying the cause and implementing recovery requires advanced knowledge and skills, which is difficult and time-consuming for general users. Furthermore, for example, if a program (flow) such as an alert notification within a business or file integration between systems fails to execute, it can cause disruption to business operations.

In some cases, it may be desirable to immediately re-execute a program (flow) that has failed to execute, rather than identifying the cause of the failure. In other cases, the program may be re-executed based on a desired schedule, such as outside of business hours. For these reasons, there is a demand for technology that allows for flexible selection of the timing for re-executing a program (flow) that has failed to execute.

The present invention has been made in consideration of the above-mentioned problems, and aims to provide an execution control device, an execution control method, and an execution control program that enable flexible selection of the timing for re-executing a program (flow) that has failed to execute.

In order to solve the above problems and achieve the object, the execution control device according to the present invention has a display control unit that displays on a display unit a reservation execution button for instructing re-execution of a program in which an execution error has occurred according to a desired schedule, a top priority execution button for manually instructing immediate execution of a program in which an execution error has occurred, and a waiting execution button for manually setting the execution order of a program in which an execution error has occurred to the end of programs waiting to be executed; a setting control unit that, when the reservation execution button is operated, stores the execution schedule of the program in which an execution error has occurred in a schedule execution setting storage unit in which schedules of programs waiting to be executed are stored, and, when the top priority execution button is operated, sets the execution order of the program in which an execution error has occurred to the first execution order in the execution order storage unit in which pre-execution program information indicating programs before execution is stored in the execution order specified for each program, and, when the waiting execution button is operated, sets the execution order of the program in which an execution error has occurred to the end of the execution order stored in the execution order storage unit; and an execution control unit that executes and controls each program according to the schedule of each program stored in the schedule execution setting storage unit, and executes and controls each program in the execution order stored in the execution order storage unit.

In order to solve the above-mentioned problems and achieve the object, the execution control method according to the present invention includes a display control step in which the display control unit displays on the display unit a reserved execution button for instructing re-execution of the program in which an execution error has occurred according to a desired schedule, a top priority execution button for manually instructing immediate execution of the program in which an execution error has occurred, and a queue execution button for manually setting the execution order of the program in which an execution error has occurred to the end of the programs waiting to be executed; a setting control step in which, when the reserved execution button is operated, the setting control unit stores the execution schedule of the program in which an execution error has occurred in a schedule execution setting storage unit in which the schedules of programs waiting to be executed are stored, and, when the top priority execution button is operated, sets the execution order of the program in which an execution error has occurred to the first execution order in the execution order storage unit in which pre-execution program information indicating the programs before execution is stored in the execution order specified for each program, and, when the queue execution button is operated, sets the execution order of the program in which an execution error has occurred to the end of the execution order stored in the execution order storage unit; and an execution control step in which the execution control unit executes and controls each program according to the schedule of each program stored in the schedule execution setting storage unit, and executes and controls each program in the execution order stored in the execution order storage unit.

In order to solve the above problems and achieve the object, the execution control program of the present invention causes a computer to function as a display control unit that displays on a display unit a reservation execution button for instructing re-execution of a program in which an execution error has occurred according to a desired schedule, a top priority execution button for manually instructing immediate execution of a program in which an execution error has occurred, and a waiting execution button for manually setting the execution order of a program in which an execution error has occurred to the end of programs waiting to be executed, a setting control unit that, when the reservation execution button is operated, stores the execution schedule of a program in which an execution error has occurred in a schedule execution setting storage unit in which schedules of programs waiting to be executed are stored, and, when the top priority execution button is operated, sets the execution order of a program in which an execution error has occurred to the first execution order in an execution order storage unit in which pre-execution program information indicating programs before execution is stored in an execution order specified for each program, and, when the waiting execution button is operated, sets the execution order of a program in which an execution error has occurred to the end of the execution order stored in the execution order storage unit, and an execution control unit that controls the execution of each program according to the schedule of each program stored in the schedule execution setting storage unit and controls the execution of each program in the execution order stored in the execution order storage unit.

The present invention makes it possible to flexibly select the timing for re-executing a program (flow) that has failed to execute.

FIG. 1 is a block diagram showing a hardware configuration of an execution control device according to an embodiment of the present invention. FIG. 2 is a diagram showing an outline of the operation of the execution control device according to the embodiment. FIG. 3 is a diagram illustrating an example of a flow setting master stored in the master DB. FIG. 4 is a diagram showing an example of a schedule master stored in the master DB. FIG. 5 is a diagram showing an example of the flow parameter master stored in the master DB. FIG. 6 is a diagram illustrating an example of the flow execution permission master stored in the master DB. FIG. 7 is a diagram showing an example of the highest priority execution permitted master stored in the master DB. FIG. 8 is a diagram illustrating an example of the user master stored in the master DB. FIG. 9 is a diagram illustrating an example of the user group master stored in the master DB. FIG. 10 is a diagram showing an example of user group member master stored in the master DB. FIG. 11 is a diagram showing an example of the flow schedule execution setting parameter master stored in the master DB. FIG. 12 is a diagram illustrating an example of the flow schedule execution setting master stored in the master DB. FIG. 13 is a diagram showing an example of a flow execution instruction parameter work stored in the state management DB. FIG. 14 is a diagram showing an example of a flow execution instruction work stored in the state management DB. FIG. 15 is a diagram showing a display example of the execution instruction common screen. FIG. 16 is a diagram showing a display example of the common re-execution instruction screen. FIG. 17 is a diagram for explaining execution authority and re-execution authority for a program (flow). FIG. 18 is a diagram showing an example of a determination result. FIG. 19 is a diagram for explaining the display operation of parameters etc. when the "instruction type" of the delivery item is "1: manual" and the "retry category" is "0: execute". FIG. 20 is a diagram for explaining the display operation of parameters and the like when the "instruction type" of the delivery item is "0: schedule" and the "retry category" is "0: execute." FIG. 21 is a diagram for explaining the display operation of parameters, etc., when the previous execution was performed manually and, when re-executing, the "instruction type" of the delivery item is "1: manual" and the "retry category" is "1: re-execution." FIG. 22 is a diagram for explaining the display operation of parameters, etc., when the previous execution was performed manually, and then when the transfer item "Instruction type" is "0: Schedule" and the "Retry category" is "1: Re-execution." FIG. 23 is a diagram for explaining other display operations of parameters, etc., when the previous execution was performed on a schedule and, when re-executing, the "instruction type" of the delivery item is "1: manual" and the "retry category" is "1: re-execution." FIG. 24 is a diagram for explaining other display operations of parameters, etc., when the previous execution was performed on a schedule and, when re-executing, the "instruction type" of the delivery item is "0: schedule" and the "retry category" is "1: re-execution." FIG. 25 is a diagram showing an example of the execution instruction (manual) screen. FIG. 26 is a diagram for explaining the update operation of the instruction type of the flow execution instruction work when the top priority execution button is operated and when the turn waiting execution button is operated on the execution instruction (manual) screen. FIG. 27 is a diagram showing an example of the execution setting (schedule) screen. FIG. 28 is a diagram for explaining the operation of setting a schedule. FIG. 29 is a diagram showing an example of the execution result inquiry screen. FIG. 30 is a diagram for explaining how the execution result inquiry screen and the detailed log screen are displayed. FIG. 31 is a diagram for explaining the manual re-execution operation of a program (flow) in which an execution error has occurred. FIG. 32 is a diagram showing how data in a flow execution instruction work is updated by manually re-executing a program (flow) in which an execution error has occurred. FIG. 33 is a diagram for explaining the operation of resetting a schedule for a program (flow) in which an execution error has occurred. FIG. 34 is a diagram showing how data of a flow execution instruction work is updated by rescheduling a program (flow) in which an execution error has occurred. FIG. 35 is another diagram for explaining the operation of resetting a schedule for a program (flow) in which an execution error has occurred. FIG. 36 is a diagram showing how data of a flow execution instruction work is updated by rescheduling a program (flow) in which an execution error has occurred. FIG. 37 is a diagram for explaining another example of manual re-execution of a schedule of a program (flow) in which an execution error has occurred. FIG. 38 is a diagram showing how data in a flow execution instruction work is updated by manually re-executing a program (flow) in which an execution error has occurred. FIG. 39 is a diagram for explaining an example of executing a program (flow) that has caused an execution error when executed according to a schedule by changing the schedule and executing the program. FIG. 40 is a diagram showing data of a flow execution instruction work before the schedule of a program (flow) in which an execution error has occurred is re-set. FIG. 41 is a diagram showing how data in a flow execution instruction work is updated by rescheduling a program (flow) in which an execution error has occurred.

The execution control device according to the embodiment of the present invention will be described in detail below with reference to the drawings. Note that the present invention is not limited to the embodiment below. In addition, the explanation will be given assuming that "program" and "flow" are synonymous.

(Hardware configuration)
As shown in Fig. 1, an execution control device 1 according to an embodiment includes a storage unit 2, a control unit 3, a communication interface unit 4, and an input/output interface unit 5. An input device 6 and an output device 7 are connected to the input/output interface unit 5. The output device 7 corresponds to a display unit such as a monitor device (including a home television), a printing device, or a speaker device. The input device 6 may be a keyboard device, a mouse device, a microphone device, or a monitor device that cooperates with a mouse device to realize a pointing device function. The communication interface unit 4 is connected to a network such as a wide area network such as the Internet or a private network such as a LAN (Local Area Network).

The storage unit 2 may be, for example, a storage device such as a ROM (Read Only Memory), a RAM (Random Access Memory), a HDD (Hard Disk Drive), or an SSD (Solid State Drive). The storage unit 2 stores an execution control program for controlling the re-execution of a program (flow) in which an error occurs during execution. The storage unit 2 also stores a state management database (state management DB) 11 having a flow execution instruction work 12, which is a storage area, and a master DB 13 having a flow schedule execution setting master 14, which is a storage area. These will be described in detail later.

(Functional configuration of the execution control device)
Next, the control unit 3 executes the execution control program stored in the memory unit 2, thereby functioning as a display control unit 20 and an asynchronous manager 21, as shown in Fig. 1. The asynchronous manager 21 includes a background execution management unit 22, a flow execution unit 23, an instruction creation unit 24, and a memory control unit 25. The background execution management unit 22, the instruction creation unit 24, and the memory control unit 25 are examples of a setting control unit. Also, the flow execution unit 23 is an example of an execution control unit.

The display control unit 20 displays on the display unit (output device 7 in FIG. 1) a scheduled execution button (reference number 33 in FIG. 2) for instructing re-execution of the program in which an execution error has occurred on a desired schedule, a top priority execution button (reference number 31 in FIG. 2) for manually instructing immediate execution of the program in which an execution error has occurred, and a waiting execution button (reference number 32 in FIG. 2) for manually setting the execution order of the program in which an execution error has occurred to the end of the programs waiting to be executed.

When the reservation execution button is operated, the background execution management unit 22, the instruction creation unit 24, and the storage control unit 25 that constitute the setting control unit store the execution schedule of the program in which the execution error occurred in the schedule execution setting storage unit (flow schedule execution setting master 14) that stores the schedules of programs waiting to be executed.

When the top priority execution button is operated, the background execution management unit 22, instruction creation unit 24, and storage control unit 25, which constitute the setting control unit, set the execution order of the program in which the execution error occurred to the top of the execution order in the execution order storage unit (flow execution instruction work 12), in which pre-execution program information indicating the program before execution is stored in the execution order specified for each program.

In addition, when the wait-for-turn execution button is operated, the background execution management unit 22, instruction creation unit 24, and memory control unit 25 that constitute the setting control unit set the execution order of the program in which the execution error occurred to the end of the execution order stored in the execution order memory unit (flow execution instruction work 12).

The execution control unit (flow execution unit 23) controls the execution of each program according to the schedule of each program stored in the schedule execution setting storage unit (flow schedule execution setting master 14), and controls the execution of each program in the execution order stored in the execution order storage unit (flow execution instruction work 12).

The display control unit 20 also displays on the display unit (output device 7) the execution conditions at the time of execution of the program in which the execution error occurred, together with the scheduled execution button 33, the top priority execution button 31, and the queue execution button 32. When the execution conditions are changed, the background execution management unit 22, the instruction creation unit 24, and the memory control unit 25 constituting the setting control unit reset the changed execution conditions to the program in which the execution error occurred as the execution conditions for the program in which the execution error occurred. Then, the execution control unit (flow execution unit 23) re-executes the program in which the execution error occurred based on the reset execution conditions.

In addition, changeability information indicating whether the parameters can be changed is added to the parameters included in the execution conditions. In this case, the display control unit 20 changes the display form of the changeable and unchangeable parameters among the parameters based on the changeability information.

In addition, re-execution permission information indicating whether or not re-execution is possible is added to the program in which the execution error occurred. In this case, if re-execution permission information permitting re-execution is added to the program in which the execution error occurred, the display control unit 20 displays the reserved execution button 33, the top priority execution button 31, and the queue execution button 32 on the display unit (output device 7), thereby enabling the program in which the execution error occurred to be re-executed.

In addition, the program in which the execution error occurred is provided with user authority information indicating the users who are permitted to re-execute the program in which the execution error occurred. In this case, the execution control unit (flow execution unit 23) refers to the execution permission storage unit (flow execution permission master 44 in FIG. 6) in which the user authority information of each user is stored.

Then, the execution control unit (flow execution unit 23) determines whether the user issuing the instruction to re-execute the program in which the execution error occurred has the user authority to re-execute the program in which the execution error occurred, and when it is determined that the instruction to re-execute has come from a user with the user authority to re-execute the program in which the execution error occurred, it re-executes the program in which the execution error occurred.

When the top priority execution button 31 is used to instruct immediate execution of the program in which an execution error has occurred, the execution control unit (flow execution unit 23) refers to the top priority execution permission memory unit (top priority execution permission master 45 in FIG. 7) in which immediate execution user information indicating a user who has been granted user authority for immediate execution is stored. Then, when the execution control unit (flow execution unit 23) determines that the user who has instructed immediate execution of the program in which an execution error has occurred using the top priority execution button 31 is a user who has been granted user authority for immediate execution, it re-executes the program in which an execution error has occurred.

(Operation overview)
Fig. 2 is a diagram showing an outline of the operation of the execution control device 1 according to the embodiment. As shown in Fig. 2, for example, if an execution error occurs when executing a program (flow) in the background, the display control unit 20 displays a top priority execution button 31, a waiting execution button 32, and a reserved execution button 33 via the output device 7. The operator selects and operates the button that matches the timing for re-executing the program (flow).

When the top priority execution button 31 is operated, the instruction creation unit 24 and the memory control unit 25 set the program (flow) to be re-executed at the top of the programs (flows) arranged in the execution order in the flow execution instruction work 12. This causes the background execution management unit 22 and the flow execution unit 23 to immediately re-execute the program (flow) that caused the execution error.

When the wait-for-turn execution button 32 is operated, the instruction creation unit 24 and the memory control unit 25 set the program (flow) to be re-executed at the end of the programs (flows) arranged in the order of execution in the flow execution instruction work 12. This allows the background execution management unit 22 and the flow execution unit 23 to re-execute the program (flow) that has caused an execution error following the program (flow) that was set earlier.

When the reservation execution button 33 is operated, the instruction creation unit 24 and the memory control unit 25 set information indicating the program (flow) whose execution date and time (schedule) has been specified by the operator in the flow schedule execution setting master 14. The background execution management unit 22 and the flow execution unit 23 set information indicating the program (flow) that has caused an execution error in the flow execution instruction work 12 so that it can be executed at the specified date and time. Then, when the specified date and time arrives, the program (flow) that caused the execution error is re-executed.

To explain in more detail, the background execution management unit 22 periodically monitors the data of the flow execution instruction work 12 in the status management DB 11. The only data monitored is that of the flow execution instruction work 12 whose "status" is unprocessed. The background execution management unit 22 sends a flow ID that identifies the program associated with the scheduled execution date and time to the flow execution unit 23 as an argument. This causes the flow execution unit 23 to execute the program (flow) corresponding to the flow ID. When the background execution management unit 22 has sent the flow ID as an argument to the flow execution unit 23, or when the processing of this program (flow) has ended, it performs a process of rewriting the "status" of the data that is the target of the flow execution instruction work 12.

In addition, the background execution management unit 22 processes the execution of programs (flows) sequentially in the following order:

a. "Instruction type" is "2: Top priority">"Scheduled execution date and time" ascending order b. "Instruction type" is "0: Schedule" or "1: Waiting">"Scheduled execution date and time" ascending order

This means that even if an instruction type of "2: highest priority" is added later, "a" can always be executed in priority over the existing "b".

The background execution management unit 22 also sets up this process in advance using a task schedule on the web server device or DB server so that it is executed automatically on a regular basis.

The flow execution unit 23 determines the program (flow) to be executed based on the flow ID of the argument sent from the background execution management unit 22. Based on the flow ID of the argument, the actual processing of the program (flow) is performed according to the definition of the detailed settings of the flow setting master 41 (see FIG. 3).

(Configuration of various masters)
3 is a diagram showing an example of the flow setting master 41 stored in the master DB 13. As shown in FIG. 3, the flow setting master 41 includes a flow identification number (flow ID), a system, a re-execution permission flag, and detailed settings. In the example of FIG. 3, the program (flow) for the qualification expiration alert is set to be executable by the human resources department, but re-execution is not permitted (re-execution permission flag=0: denial). In addition, the program (flow) for the disaster alert linkage is set to be executable by the operation management department, and re-execution is also permitted (re-execution permission flag=1: permission). In addition, the flow execution unit 23 performs substantial processing of the program (flow) according to the definition of the "detailed settings".

Figure 4 is a diagram showing an example of a schedule master 42 stored in the master DB 13. The schedule master 42 is configured to include a schedule ID, detailed schedule settings, etc. In the example of Figure 4, the schedule ID "EveryDay230" indicates that it is a schedule ID that specifies the execution of a program (flow) at 2:30 every morning. Similarly, the schedule ID "Every10minUntil2300" indicates that it is a schedule ID that specifies the execution of a program (flow) every 10 minutes until 11pm every day.

Figure 5 is a diagram showing an example of flow parameter master 43 stored in master DB 13. As shown in this Figure 5, flow parameter master 43 is composed of flow ID, parameter ID, data type, required category, default value, re-execution value change permission category, etc. In the example of Figure 5, the re-execution value change permission category of the program (flow) with the flow ID of "Qualification expiration alert" is "1: Allowed", indicating that the parameter value can be changed when re-executing. Similarly, in the example of Figure 5, the re-execution value change permission category of the parameter "Calculation category" of the program (flow) with the flow ID of "Time attendance calculation execution" is "0: Denied", indicating that the parameter value cannot be changed when re-executing.

Figure 6 is a diagram showing an example of the flow execution permission master 44 stored in the master DB 13. As shown in Figure 6, the flow execution permission master 44 is configured to include system information and internal user group information (internal user group Guid), etc.

Figure 7 is a diagram showing an example of the top priority execution permission master 45 stored in the master DB 13. In this top priority execution permission master 45, user group information (internal user group Guid) that is permitted to set the immediate execution of a program (flow) is registered (stored).

Figure 8 is a diagram showing an example of a user master 46 stored in the master DB 13. As shown in Figure 8, the user master 46 stores an internal user Guid, user ID, user name, password, etc.

Figure 9 is a diagram showing an example of user group master 47 stored in master DB 13. As shown in Figure 9, the user group master 47 stores internal user group Guids, user group names, etc.

Figure 10 is a diagram showing an example of the user group member master 48 stored in the master DB 13. As shown in Figure 10, the user group member master 48 stores internal user group Guids and internal user Guids, etc.

Figure 11 is a diagram showing an example of the flow schedule execution setting parameter master 49 stored in the master DB 13. As shown in Figure 11, the flow schedule execution setting parameter master 49 stores a schedule execution setting ID, a parameter ID, a setting value, etc.

Figure 12 is a diagram showing an example of the flow schedule execution setting master 14 stored in the master DB 13. As shown in this Figure 12, the flow schedule execution setting master 14 stores a schedule execution setting ID, an execution schedule setting name, a flow ID, a schedule ID, and an error source instruction Guid, etc.

Figure 13 is a diagram showing an example of a flow execution instruction parameter work 50 stored in the state management DB 11. As shown in this Figure 13, the flow execution instruction parameter work 50 stores an instruction Guid, a parameter ID, an execution value, etc.

Figure 14 is a diagram showing an example of a flow execution instruction work 12 stored in the status management DB 11. As shown in Figure 14, the flow execution instruction work 12 stores an instruction Guid, schedule execution setting ID, flow ID, schedule ID, instruction type, scheduled execution date and time, next scheduled execution date and time, status, processing result, processing start time, processing end time, retry category, error source instruction Guid, etc. Among these, the "status" stores the execution status of the program (flow), such as "normal completion" or "error".

(Common execution instruction screen)
Next, FIG. 15 shows a common execution instruction screen used when setting the execution of a desired program (flow), and FIG. 16 shows a common re-execution instruction screen used when setting the re-execution of a desired program (flow).

First, when the operator specifies settings for the execution of a desired program (flow), the display control unit 20 controls the display of the common execution instruction screen shown in FIG. 15 via the output device 7. On this common execution instruction screen, the display control unit 20 displays a selection field for the program (flow) to be executed, a field for inputting a schedule, a field for inputting parameters, a top priority execution button 31 for specifying the timing of execution, a queue execution button 32, and a reservation execution button 33, etc.

By referring to the flow setting master 41, the display control unit 20 detects only the program names of the programs (flows) for which the operator has been granted execution authority, and displays them in the selection field for the program (flow) to be specified for execution.

The display control unit 20 also refers to the schedule master 42 and displays the execution schedule in the schedule input field. The display control unit 20 also displays the parameter values set in the flow parameter master 43 in the parameter input field. By changing the parameters set in the flow parameter master 43, the parameter values displayed in the parameter input field can be changed to desired values.

As described above, the top priority execution button 31 is a button that is operated when the program (flow) is to be placed at the head of programs (flows) waiting to be executed and executed with top priority. The waiting order execution button 32 is a button that is operated when the program (flow) is to be placed at the end of programs (flows) waiting to be executed and executed in order. The scheduled execution button 33 is a button that is operated when the program (flow) is to be executed according to a desired schedule.

The display control unit 20 may display the top priority execution button 31 and the queue execution button 32 only when manual execution of the program (flow) is specified. The display control unit 20 also refers to the top priority execution permission master 45 shown in FIG. 7, and displays the top priority execution button 31 only when it determines that the user group, operator, etc. is permitted to specify execution with top priority (it is not displayed if not permitted). The display control unit 20 may also display the schedule input field and the reservation execution button only when scheduled execution of the program (flow) is specified.

(Retry instruction common screen)
Next, when the operator specifies the setting for re-execution of a desired program (flow), the display control unit 20 controls the display of a re-execution instruction common screen, as exemplified in Fig. 16, via the output device 7. The display form of this re-execution instruction common screen is substantially the same as the execution instruction common screen described above. That is, the display control unit 20 displays, on this re-execution instruction common screen, a selection field for the program (flow) to be re-executed, an input field for the original schedule, an input field for the temporary schedule, an input field for parameters, an input field for parameters (previous values) at the time of the previous execution, a top priority execution button 31 for specifying the timing of execution, a queue execution button 32, and a reservation execution button 33, etc.

The display control unit 20 controls whether to display or hide the original schedule and original setting names depending on whether the instruction type of the flow execution instruction work 12 is a schedule (previous execution method), and also controls whether to display or hide the temporary schedule and temporary setting names depending on whether the instruction type of the delivery item (current execution method) is a schedule. That is, the display control unit 20 refers to the flow execution instruction work 12 to display the program (flow) in which an error occurred the previous time it was executed in the selection field for the program (flow) to be specified for re-execution. Also, the display control unit 20 refers to the flow execution instruction work 12 to display the schedule of the program (flow) in which an error occurred the previous time it was executed in the input field for the original schedule. Note that "original" means the program (flow) in which an error occurred the previous time it was executed.

The display control unit 20 also refers to the flow execution instruction parameter work 50 to detect the parameter value (previous value) of the program (flow) in which an error occurred the previous time it was executed, and displays it in the input field for the parameter (previous value) from the previous execution.

As described above, the top priority execution button 31 is a button that is operated when the program (flow) to be re-executed is placed at the head of programs (flows) waiting to be executed, and executed with top priority. The queue execution button 32 is a button that is operated when the program (flow) to be re-executed is set at the end of programs (flows) waiting to be executed, and executed in order. The scheduled execution button 33 is a button that is operated when the program (flow) to be re-executed is executed according to a desired schedule.

The display control unit 20 may display the top priority execution button 31 and the queue execution button 32 only when manual execution of the program (flow) is specified. The display control unit 20 also refers to the top priority execution permission master 45 shown in FIG. 7, and displays the top priority execution button 31 only when it determines that the user group, operator, etc. is permitted to specify execution with top priority (hides if not permitted). The display control unit 20 may also display the schedule input field and the reservation execution button only when scheduled execution of the program (flow) is specified.

(Program (flow) execution and re-execution authority)
The execution or re-execution of a program (flow) is divided into "normal authority" which is set at the end of the programs (flows) waiting to be executed and executed in order (normal execution), and "highest priority authority" which is executed by interrupting the beginning of the programs (flows) waiting to be executed. Regarding the normal authority for a program (flow), the display control unit 20 refers to the flow setting master 41, flow execution permission master 44, highest priority execution permission master 45, user master 46, user group master 47, and user group member master 48 shown in FIG. 17 (especially the flow execution permission master 44) and determines the user group that has been granted execution authority for that program (flow). In addition to such execution authority, the display control unit 20 also refers to the "re-execution permission flag" of the flow setting master 41 when re-executing.

The display control unit 20 also determines whether the highest priority authority for a program (flow) is based on normal authority and whether the highest priority authority has been granted to the user group in the "highest priority execution permission master 45." If the display control unit 20 has normal authority but has not set the highest priority authority, it hides the highest priority execution button 31 on the execution instruction common screen or re-execution instruction common screen.

(Example of judgment result)
FIG. 18 is a diagram showing an example of such a determination result. In FIG. 18, "◯" indicates "authorized" and "×" indicates "not authorized." For example, user 10001 has normal authority for flow A at the time of execution, but does not have top priority authority. User 10001 has normal authority for flow A at the time of re-execution, but does not have top priority authority. Similarly, user 10002 has neither normal authority nor top priority authority for flow A at the time of execution and re-execution. User 10003 has both normal authority and top priority authority for flow A at the time of execution and re-execution.

(Display control of parameters, etc.)
Next, information indicating the program (flow) to be executed or re-executed is set in the flow execution instruction work 12 as shown in Fig. 2. The information indicating the program (flow) to be executed or re-executed set in the flow execution instruction work 12 includes a retry category, an instruction type, and an error source instruction Guid as "delivery items" as shown in Fig. 14.

"Retry category" is information that indicates whether the program (flow) is being executed for the first time or is being re-executed. If it is being executed for the first time, "0: Execute" is set, and if it is being re-executed, "1: Re-execute" is set.

As for the "instruction type" of the delivery item, if the execution or re-execution of the program (flow) is based on a schedule, "0: Schedule" is set, and if it is based on manual operation, "1: Manual" is set.

The "error source instruction Guid" is a Guid that allows the program (flow), parameters, and schedule from the previous execution to be restored when the program (flow) is executed again.

The display control of parameters etc. for each combination pattern of such delivery items is as follows:

First, when the "Instruction Type" of the delivery item is "1: Manual" and the "Retry Category" is "0: Execute", the display control unit 20 displays the top priority execution button 31 and the wait for turn execution button 32 on the execution instruction common screen shown in FIG. 15, as shown in FIG. 19(a). The display control unit 20 also refers to the flow parameter master 43 shown in FIG. 19(b), reads out the first value of the first parameter and the second value of the second parameter for the first flow, and displays them in the parameter input field on the execution instruction common screen in a state that can be changed by the operator, as shown in FIG. 19(a).

Next, when the "Instruction Type" of the delivery item is "0: Schedule" and the "Retry Category" is "0: Execute", the display control unit 20 displays the reservation execution button 33 on the execution instruction common screen shown in FIG. 15, as shown in FIG. 20(a). The display control unit 20 also refers to the flow parameter master 43 shown in FIG. 20(b), reads out the first value of the first parameter and the second value of the second parameter for the second flow, and displays them in the parameter input field on the execution instruction common screen together with the program (flow) schedule, as shown in FIG. 20(a). Each parameter is always displayed in a state that allows the operator to change it.

Next, FIG. 21 shows an example in which execution was manually set according to the execution order during the previous execution (originally manual), and normal execution according to the execution order is also manually set when re-executing. In this case, the "instruction type" of the delivery item is "1: manual" and the "retry category" is "1: re-execution." As shown in FIG. 21(a), the display control unit 20 displays a top priority execution button 31 and a waiting order execution button 32 on the common re-execution instruction screen.

The display control unit 20 also refers to the flow parameter master 43 shown in FIG. 21(b), reads out the first value of the first parameter, the second value of the second parameter, and the third value of the third parameter for the third flow, and displays them as the "previous value" in the previous value input field of the common screen for instructing re-execution in an unchangeable state, as shown in FIG. 21(a).

As shown in FIG. 21(b), the re-execution value change permission category for the first parameter is set to "1: Allowed", the re-execution value change permission category for the second parameter is set to "1: Allowed", and the re-execution value change permission category for the third parameter is set to "0: Denied". Therefore, the display control unit 20 inputs the value at the time of the previous execution in an unchangeable state for the third parameter in the parameter input field of the program (flow) to be re-executed, since the re-execution value change permission category is set to "0: Denied", and inputs the values at the time of the previous execution in an changeable state into the input fields of the first parameter and the second parameter. In this case, the first parameter and the second parameter can be changed arbitrarily by the operator. The example in FIG. 21(a) is an example in which the operator changes the first parameter to the first new value, and the second parameter is an example in which the previous value is used as it is without being changed.

Next, FIG. 22 shows an example where the previous execution was set manually according to the execution order (originally manual), and the next execution is set to be re-executed according to a schedule. In this case, the "instruction type" of the delivery item is "0: Schedule" and the "retry category" is "1: Re-execution". As shown in FIG. 22(a), the display control unit 20 displays a reservation execution button 33 on the common re-execution instruction screen together with the schedule timing (temporary schedule) and the temporary setting name.

The display control unit 20 also refers to the flow parameter master 43 shown in FIG. 22(b), reads out the first value of the first parameter for the fourth flow, and displays it as the "previous value" in the previous value input field of the re-execution instruction common screen, as shown in FIG. 22(a). As shown in FIG. 22(b), the re-execution value change permission category for the first value of this first parameter is "1: Allowed", so the display control unit 20 displays the first value of the first parameter in the first parameter value input field of the re-execution instruction common screen in a state where it can be changed by the operator.

Next, FIG. 23 shows an example in which execution based on a schedule was set during the previous execution (originally scheduled), and manual re-execution is set when re-executing. In this case, the "instruction type" of the delivery item is "1: manual" and the "retry category" is "1: re-execution." As shown in FIG. 23(a), the display control unit 20 displays a top priority execution button 31 and a queue execution button 32 on the common re-execution instruction screen.

The display control unit 20 also refers to the flow parameter master 43 shown in FIG. 23(b) and reads out the first value of the first parameter for the fifth flow, but as shown in FIG. 23(a), it always displays it in the "previous value" input field in a state where it cannot be changed by the operator. Because the re-execution value change permission category for the first value of this first parameter is "0: Denied", the display control unit 20 displays the first value of the first parameter in the first parameter input field in a state where it cannot be changed.

Next, FIG. 24 shows an example in which execution based on a schedule was set during the previous execution (original schedule), and re-execution based on the schedule is also set when re-executing. In this case, the "instruction type" of the delivery item is "0: schedule" and the "retry category" is "1: re-execution". As shown in FIG. 24(a), the display control unit 20 displays on the common re-execution instruction screen the flow name from the previous execution (flow 6), the previous schedule (original schedule: weekdays at 3 p.m.), the original setting name (flow B weekdays at 3 p.m.), the temporary schedule (every 10 minutes (up to 3 times)), the temporary setting name (flow B every 10 minutes (3)), and the reservation execution button 33.

The display control unit 20 also refers to the flow parameter master 43 shown in FIG. 24(b) and reads out the first value of the first parameter and the second value of the second parameter for the sixth flow. In this example, the re-execution value change permission category allows the first value of the first parameter to be changed (1: allowed), but does not allow the second value of the second parameter to be changed (0: denied).

Therefore, the display control unit 20 displays the first value of the first parameter in the input field for the first parameter value in a state in which it can be changed by the operator, and displays the second value of the second parameter in the input field for the second parameter value in a state in which it cannot be changed by the operator. Note that the display control unit 20 displays both the first value of the first parameter and the second value of the second parameter in a state in which they cannot be changed in the input field for the previous value.

(Manual execution instructions)
Next, when issuing an execution instruction manually, the operator selects "Execution instruction (manual)" from the job list displayed on the menu screen shown in Fig. 25(a). When the retry category of the delivery item is "0: execution" and the instruction type is "1: manual", the display control unit 20 displays the execution instruction (manual) screen shown in Fig. 25(b) via the output device 7. On this execution instruction (manual) screen, the display control unit 20 displays a selection field for the desired program (flow), an input field for the qualification category, a top priority execution button 31, and a wait for turn execution button 32. Each parameter is always displayed in a state in which it can be changed by the operator.

The operator selects a program (flow) to be executed manually, such as a "Qualification Expiration Alert," from the program (flow) selection field. The operator also inputs a qualification category, such as "1: XX qualification," which is the qualification for executing this "Qualification Expiration Alert," into the qualification category input field. The operator then operates the top priority execution button 31 or the queue execution button 32.

Figures 26(a) to 26(d) show the flow setting master 41, flow parameter master 43, flow execution instruction work 12, and flow execution instruction parameter work 50. When the operator operates the top priority execution button 31, the memory control unit 25 updates the "instruction type" of the flow execution instruction work 12 shown in Figure 26(c) to "2: top priority". When the operator operates the wait-for-turn execution button 32, the memory control unit 25 updates the "instruction type" of the flow execution instruction work 12 shown in Figure 26(c) to "1: wait-for-turn". The memory control unit 25 updates the "scheduled execution date and time" of the flow execution instruction work 12 shown in Figure 26(c) to the current date and time.

(Schedule setting)
Next, when executing a program (flow) based on a schedule, the operator selects "Execution Settings (Schedule)" from the job list displayed on the menu screen shown in Fig. 27(a). When the retry category of the delivery item is "0: Execution" and the instruction type is "0: Schedule", the display control unit 20 displays the execution settings (schedule) screen shown in Fig. 27(b) via the output device 7. The display control unit 20 displays a selection field for the desired program (flow), an input field for the desired schedule, an input field for the schedule setting name, an input field for the qualification category, and a reservation execution button 33 on this execution settings (schedule) screen.

The operator selects the program (flow) to be executed on a schedule, such as "Qualification Expiration Alert", from the program (flow) selection field. The operator also inputs a qualification category, such as "1: XX qualification", which is the qualification for executing this "Qualification Expiration Alert", into the qualification category input field. The operator also inputs a desired schedule for executing the program (flow), such as "Every morning at 2:30", into the schedule input field, and inputs a desired setting name, such as "Qualification Expiration Alert 2:30 am". The operator then operates the reservation execution button 33.

Figures 28(a) to 28(e) show the schedule master 42, the flow schedule execution setting master 14, the flow schedule execution setting parameter master 49, the flow execution instruction work 12, and the flow execution instruction parameter work 50. When the operator operates the reservation execution button 33, the storage control unit 25 stores the master data in the flow schedule execution setting master 14 shown in Figure 28(b) and the flow schedule execution setting parameter master 49 shown in Figure 28(c). In addition, the instruction creation unit 24, which periodically monitors the set master data, calculates the next execution date and time based on the current time and the schedule settings. Then, the storage control unit 25 sets a schedule for "Qualification Expiration Alert" for the flow execution instruction work 12 shown in Figure 28(d) with "Instruction Type" set to "0: Schedule" and "Scheduled Execution Date and Time" set to 2:30 a.m. every morning.

When creating a batch execution instruction, if the current time is 2:20 AM on September 30, 2022, the instruction creation unit 24 creates a batch execution instruction for 2:30 AM on September 30, 2022 as the next execution date and time. Also, if the current time is 2:31 AM on September 30, 2022, the instruction creation unit 24 creates a batch execution instruction for 2:30 AM on October 1, 2022 as the next execution date and time.

The schedule set for the flow execution instruction work 12 in this manner is periodically monitored by the background execution management unit 22 and transmitted to the flow execution unit 23 when the execution date and time arrives.

(Display of execution result inquiry screen)
Next, the execution control device 1 according to the embodiment displays a list of the execution results of each program (flow), and is capable of selecting a program (flow) in which an execution error has occurred and re-executing it. When displaying a list of the execution results of each program (flow), the operator selects the job "execution result inquiry" from the menu screen shown in FIG. 29(a). This causes the display control unit 20 to display a list of the execution results of each program (flow) via the execution result inquiry screen shown in FIG. 29(b). In addition, the display control unit 20 displays a schedule reset button 61 and a manual re-execution button 62 on the execution result inquiry screen together with this list.

When the operator selects a record (details) of a desired execution result from the list of execution results displayed on the execution result inquiry screen shown in FIG. 29(b), the display control unit 20 displays the detailed execution results of each task included in the program (flow) selected by the operator via the detail log screen shown in FIG. 29(c).

Figure 30 (a) shows the flow execution instruction work 12. Figure 30 (b) shows the reference data that is referenced when displaying the execution result inquiry screen. As shown in Figure 30 (b), the display control unit 20 obtains and displays the execution schedule setting name from the flow schedule execution setting master 14 as the "setting name" in the list, and obtains and displays the "program (flow)" in the list from the flow ID of the flow execution instruction work 12.

The display control unit 20 also obtains and displays the "Results" in the list from the "Status" of the flow execution instruction work 12, and obtains and displays the "Processing Date and Time" in the list from the "Processing Start" to "Processing End" of the flow execution instruction work 12. The display control unit 20 also displays the "Processing Time" in the list as the time from the "Processing Start" to the "Processing End" of the flow execution instruction work 12, and obtains and displays the "Message" in the list as the "Processing Result" of the flow execution instruction work 12.

The display control unit 20 also obtains and displays the "retry category" of the flow execution instruction work 12 as the "retry" in the list, and obtains and displays the "instruction type" of the flow execution instruction work 12 as the "instruction type" in the list.

Figure 30(c) shows the reference data that is referenced when displaying the detailed log in Figure 29(c). As shown in this Figure 30(c), the display control unit 20 obtains and displays the "task" of the detailed log from the "task ID" of the flow execution log 53 shown in Figure 30(d), and obtains and displays the "status" of the detailed log from the "status" of the flow execution log 53.

The display control unit 20 also displays the "processing date and time" of the detailed log as the date and time indicated by "processing start" to "processing end" in the flow execution log 53 shown in FIG. 30(d), and obtains and displays the "message" of the flow execution log 53 as the "message" of the detailed log.

(Manually re-running a program (flow) that encountered an execution error the last time it was run manually)
Next, the execution control device 1 of the embodiment is capable of manually re-executing a program (flow) in which an execution error has occurred by selecting the program (flow) in which an execution error has occurred from the execution results displayed in the list in this way. That is, when the operator selects the record (details) of the program (flow) to be re-executed from the list of the execution results described above as shown in Figures 31(a) and 31(b) and operates the manual re-execution button 62, the display control unit 20 displays the re-execution instruction (manual) screen shown in Figure 31(c) via the output device 7, with the "instruction Guid" of the selected line in Figure 31(b) as the error source instruction Guid, if the retry classification of the delivery item is "1: re-execution" and the instruction type is "1: manual".

At this time, since the re-execution value change permission categories for the parameter IDs of "Send target" and "Re-send category" in the flow parameter master 43 shown in FIG. 32(b) are both "1: Allowed", the display control unit 20 displays the input fields for each parameter of "Send target" and "Re-send category" shown in FIG. 31(c) in a state in which the operator can change the values. Note that since this is an instruction to execute a re-execution, the display control unit 20 displays the name of the previously executed program (flow) in an unchangeable state, and displays the previous value, which is the parameter used in the previous execution, in an unchangeable state.

The operator sets the parameters of the program (flow) to be re-executed on this re-execution instruction (manual) screen. The example in FIG. 31 (c) is an example of re-execution of the program (flow) "Bulk sending of training emails", in which the operator sets the "To whom" parameter to "Everyone" and the "Resend category" parameter to "Resend". After setting the parameters, the operator operates the top priority execution button 31 or the queue execution button 32.

Figures 32(a) to 32(f) show the flow setting master 41, the flow parameter master 43, the flow execution instruction work 12 before the re-execution instruction, the flow execution instruction parameter work 50, the flow execution instruction work 12 after the re-execution instruction, and the flow execution instruction parameter work 50. Before the top priority execution button 31 or the queue execution button 32 is operated, the flow execution instruction work 12 has an "instruction type" of "1: queue" or "2: top priority" as shown in Figure 32(c) and a "status" of "2: error."

When the top priority execution button 31 or the waiting execution button 32 is operated, the storage control unit 25 generates a record with the "instruction type" set to "1: waiting" or "2: top priority" according to the button operated by the operator, the "status" set to "0: unprocessed", and the "processing result" set to blank, as shown in FIG. 32(e), and adds this to the flow execution instruction work 12. At this time, the storage control unit 25 adds the same instruction Guid as the instruction Guid shown in FIG. 32(c) to the record to be added. This allows the added record to be held by associating the error source instruction Guid of the added record in FIG. 32(e) with the instruction Guid in FIG. 32(c). The storage control unit 25 stores the reset parameters of "Everyone" for "Target" and "Resend" for "Resend Classification" in the flow execution instruction parameter work 50 as shown in FIG. 32(f).

(Resetting the schedule of a program (flow) that caused an execution error the last time it was run manually)
Next, the operation of selecting a program (flow) that has caused an execution error by being manually executed from the execution results displayed in the above list, changing the execution form to execution based on a schedule, and resetting this schedule will be described. In this case, the operator displays the list of the above execution results as shown in Figures 33(a) and 33(b), selects the record (details) of the program (flow) to be re-executed, and operates the schedule reset button 61. When the retry classification of the delivery item is "1: re-execution" and the instruction type is "0: schedule", the display control unit 20 displays the re-execution setting (schedule) screen shown in Figure 33(c) via the output device 7 based on the "instruction Guid" of the selected row in Figure 33(b).

At this time, since the re-execution value change permission categories for the parameter IDs of "Send target" and "Resend category" in the flow parameter master 43 shown in FIG. 34(b) are both "1: Allowed", the display control unit 20 displays the input fields for each parameter of "Send target" and "Resend category" shown in FIG. 33(c) in a state in which the operator can change the values. Note that since the schedule reset button 61 was operated this time, the display control unit 20 displays the name of the previously executed program (flow) in an unchangeable state, and also displays the previous value, which is the parameter used in the previous execution, in an unchangeable state.

The display control unit 20 also displays an input field for the temporary schedule, which is an input field for the schedule to be reset, an input field for the setting name of the temporary schedule (temporary setting name), and an input field for the parameters of the program (flow) to be reset.

The example in Figure 33(c) is an example of re-executing the "Bulk sending of training emails" program (flow), in which the operator sets the "Target" parameter to "Everyone" and the "Resend category" parameter to "Resend." Also, the example in Figure 33(c) is an example in which the operator sets the "Temporary schedule" to "Server restart 2:30," which is a schedule for restarting the server device at 2:30 AM, and sets the "Temporary setting name" to "Bulk handling of training emails." After re-setting the schedule and parameters in this way, the operator operates the reservation execution button 33.

Figures 34(a) to 34(h) show the flow setting master 41, flow parameter master 43, flow execution instruction work 12 before schedule resetting, flow execution instruction parameter work 50, flow schedule execution setting master 14 after schedule resetting, flow schedule execution setting parameter master 49, flow execution instruction work 12 after schedule resetting, and flow execution instruction parameter work 50. Before the reservation execution button 33 is operated, the flow execution instruction work 12 has an "instruction type" of "1: waiting in line" or "2: highest priority" and a "status" of "2: error" as shown in Figure 34(c).

In response to this, after the reservation execution button 33 is operated, the storage control unit 25 inputs the above-mentioned "Temporary setting name" such as "Server restart 2:30" into the "Schedule ID" as shown in FIG. 34(g), sets the "Instruction type" to "0: Schedule", sets the "Execution reservation date and time" to "2022/10/2 2:30:00", sets the "Status" to "0: Unprocessed", and sets the "Processing result" to blank, and adds this record to the flow execution instruction work 12. The storage control unit 25 stores the reset "Everyone" parameter for "To whom" and the "Resend" parameter for "Resend category" in the flow schedule execution setting parameter master 49 and the flow execution instruction parameter work 50, respectively, as shown in FIG. 34(f) and FIG. 34(h).

(An example of re-executing a program (flow) that had an execution error the last time it was run manually, on each schedule with divided calculation targets.)
Next, an example will be described in which a program (flow) that has caused an execution error by being manually executed is selected from the execution results displayed in the above list, and executed in each schedule into which the calculation target is divided. In this case, as shown in Figures 35(a) and 35(b), the operator displays the list of the above execution results, selects the record (details) of the program (flow) to be re-executed, and operates the schedule re-setting button 61. This causes the display control unit 20 to display the re-execution setting (schedule) screen shown in Figure 35(c) via the output device 7.

At this time, the display control unit 20 displays the input fields for each parameter of "employee category" and "target company" shown in FIG. 35(c) in a state in which the operator can change the values, because the re-execution value change permission categories for each parameter ID of "employee category" and "target company" in the flow parameter master 43 shown in FIG. 36(b) are both "1: Allowed." Note that, because the schedule reset button 61 was operated this time, the display control unit 20 displays the name of the previously executed program (flow) in an unchangeable state, and also displays the previous value, which is the parameter used in the previous execution, in an unchangeable state.

The display control unit 20 also displays an input field for the temporary schedule, which is an input field for the schedule to be reset, an input field for the setting name of the temporary schedule (temporary setting name), and an input field for the parameters of the program (flow) to be reset.

Here, by adjusting the parameter values and dividing the processing range, it is possible to narrow the scope of impact and identify where the error occurred. For example, when checking the error list, it is possible to find that most of the errors were in the part-time or casual employee category. If the program were to be re-run after dealing with all of these, it would take time, which would affect employees who did not have errors. For this reason, in order to divide the calculation target in order to narrow the scope of impact, for example, payroll calculations would first be performed on employee categories other than part-time and casual.

In this case, if the time periods with least impact on workload are, for example, 11:00 AM, 4:00 PM, and 7:00 PM, the first calculation will be performed at 11:00 AM today with "Employee Category" set to "Regular/Contract." That is, as shown in the example of FIG. 35(c), the operator sets the "Employee Category" parameter to "Regular and Contract Employee (Regular/Contract)" and the "Target Company" parameter to "10." The operator also sets the "Temporary Schedule" to 11:00 AM today and specifies that the program (flow) should be re-executed. The "Temporary Setting Name" is "Current Month's Payroll Calculation Handling." After resetting the schedule and parameters in this way, the operator operates the reservation execution button 33.

Figures 36(a) to 36(h) show the flow setting master 41, flow parameter master 43, flow execution instruction work 12 before schedule resetting, flow execution instruction parameter work 50, flow schedule execution setting master 14 after schedule resetting, flow schedule execution setting parameter master 49, flow execution instruction work 12 after schedule resetting, and flow execution instruction parameter work 50. Before the reservation execution button 33 is operated, the flow execution instruction work 12 has an "instruction type" of "1: waiting in line" or "2: highest priority" and a "status" of "2: error" as shown in Figure 36(c).

In response to this, after the reservation execution button 33 is operated, the memory control unit 25 inputs a program name (flow name) such as "Current month's payroll calculation" into the "Flow ID", inputs the above-mentioned "Temporary setting name" such as "Today at 11:00" into the "Schedule ID", sets the "Instruction type" to "0: Schedule", sets the "Planned execution date and time" to "2022/9/1 11:00:00", sets the "Status" to "0: Unprocessed", and creates a record with the "Processing result" left blank, as shown in FIG. 36 (g), and adds it to the flow execution instruction work 12.

At this time, the storage control unit 25 adds an instruction Guid that is the same as the instruction Guid shown in FIG. 32(c) to the record to be added. This allows the error source instruction Guid of the added record in FIG. 32(e) to be associated with the instruction Guid in FIG. 32(c) and the added record to be stored. At this time, the storage control unit 25 inherits the error source instruction Guid from the flow schedule execution setting master 14 via the flow execution instruction work 12. This allows the re-execution results to be associated and managed in a 1:N relationship when split execution is performed.

The storage control unit 25 stores the reset "Employee Category" parameter of "Permanent/Contract" and the reset "Target Company" parameter of "10" in the flow schedule execution setting parameter master 49 and the flow execution instruction parameter work 50, as shown in Figures 36(f) and 36(h), respectively.

In this way, when the first reservation is set and the reservation execution button 33 is operated, the display control unit 21 displays the execution result inquiry screen shown in FIG. 35(b) again. When the operator operates the schedule reset button 61 on this execution result inquiry screen, the display control unit 21 displays the second re-execution setting screen shown in FIG. 35(c). In this second re-execution setting screen, the operator sets the employee classification of the calculation target to "part-time/casual worker" taking into account the error response time described above, sets the execution time to 4:00 p.m. today, and operates the reservation execution button 33. This makes it possible to divide the calculation target and execute payroll calculations according to each schedule. The memory control unit 25 generates a record corresponding to this second schedule and adds it to the flow execution instruction work 12, as described above.

(An example of manually re-executing a program (flow) that encountered an execution error the last time it was run via a schedule setting.)
Next, an example will be described in which a program (flow) that has caused an execution error by being executed based on a schedule is selected from the execution results displayed in the above list, and the execution form is changed to manual execution to execute the program (flow). In this case, the operator displays the list of the above execution results as shown in Figures 37(a) and 37(b), selects the record (details) of the program (flow) to be re-executed, and operates the manual re-execution button 62. When the retry classification of the delivery item is "1: re-execution" and the instruction type is "1: manual", the display control unit 20 displays the re-execution setting (schedule) screen shown in Figure 37(c) via the output device 7 based on the "instruction Guid" of the selected row in Figure 37(b).

At this time, since the re-execution value change permission categories for the parameter IDs of "Processing category" and "Partner company" in the flow parameter master 43 shown in FIG. 38(b) are both "0: Denied", the display control unit 20 displays the input fields for each parameter of "Processing category" and "Partner company" shown in FIG. 37(c) in a state in which the operator cannot change the values. Note that since the schedule reset button 61 was operated this time, the display control unit 20 displays the name of the previously executed program (flow) in an unchangeable state, and displays the previous value, which is the parameter used in the previous execution, in an unchangeable state.

In this case, the display control unit 20 displays the "program (flow) name" of the program (flow) executed based on the schedule last time, the "original schedule" which is the schedule set last time, the "original setting name" which is the name of the setting at that time, and the "previous value" which is the previous parameter value in an unchangeable state on the re-execution instruction (manual) screen. The display control unit 20 also displays a parameter with the same value as the "previous value" which is the previous parameter value in the parameter input field in an unchangeable state.

The example in Figure 37 (c) is an example of re-executing the "Master synchronization flow" program (flow), where the operator displays the "Processing category" parameter as "Add/Update", which is the same value as when the schedule was last executed, in an unchangeable state, and the "Partner company" parameter as "10, 20", which is the same value as when the schedule was last executed, in an unchangeable state. In this way, with the parameters set to the same values as when the schedule was last executed, the operator operates the top priority execution button 31 or the queue execution button 32.

Figures 38(a) to 38(h) show the flow setting master 41, flow parameter master 43, flow schedule execution setting master 14, flow schedule execution setting parameter master 49, flow execution instruction work 12 before manual re-execution, flow execution instruction parameter work 50, flow execution instruction work 12 after manual re-execution, and flow execution instruction parameter work 50. Before manual re-execution, the flow execution instruction work 12 has an "instruction type" of "0: Schedule" and a "status" of "2: Error" as shown in Figure 38(e).

After manual re-execution, if the operator operates the top priority execution button 31, the memory control unit 25 sets the "instruction type" shown in FIG. 38(g) to "2: top priority", and if the operator operates the wait-for-turn execution button 32, creates a record with the "instruction type" shown in FIG. 38(g) set to "1: wait-for-turn", the "status" set to "0: unprocessed", and the "processing result" set to blank, and adds it to the flow execution instruction work 12.

(An example of re-executing a program (flow) that caused an execution error when it was executed on a schedule last time, by changing the schedule settings.)
Next, an example will be described in which a program (flow) that caused an execution error when executed based on a schedule last time is re-executed by changing the schedule. In this case, the operator displays the list of execution results described above as shown in Fig. 39(a) and Fig. 39(b), selects the record (details) of the program (flow) to be re-executed, and operates the schedule re-setting button 61. When the retry classification of the delivery item is "1: re-execution" and the instruction type is "0: schedule", the display control unit 20 displays the re-execution setting (schedule) screen shown in Fig. 39(c) via the output device 7 based on the "instruction Guid" of the selected line in Fig. 39(b).

In this case, because the schedule reset button 61 was operated this time, the display control unit 20 displays the name of the previously executed program (flow), the original schedule, and the original setting name in an unchangeable state, and also displays the previous values, which are the parameters used when the schedule was last executed, in an unchangeable state.

The display control unit 20 also displays an input field for the temporary schedule, which is an input field for the schedule to be reset, an input field for the setting name (temporary setting name) of the temporary schedule, and an input field for the parameters of the program (flow) to be reset. At this time, the display control unit 20 refers to the flow parameter master 43 shown in FIG. 40(b) and refers to the re-execution value change permission category of the parameter IDs "file name" and "closing date category". As shown in FIG. 40(b), the re-execution value change permission category for the parameter "file name" is "1: permitted", and the re-execution value change permission category for the parameter "closing date category" is "0: denied". Therefore, as shown in FIG. 39(c), the display control unit 20 displays the parameter input field for "file name" in a state in which the operator can change the value, and displays the parameter input field for "closing date category" in a state in which the operator cannot change the value. After inputting the temporary schedule, the temporary setting name, and the file name, the operator operates the reservation execution button 33.

Figures 40(a) to 40(f) show the flow setting master 41, flow parameter master 43, flow schedule execution setting master 14 after schedule resetting, flow schedule execution setting parameter master 49, flow execution instruction work 12 before schedule resetting, and flow execution instruction parameter work 50. Before the reservation is executed based on the temporary schedule, the flow execution instruction work 12 has an "instruction type" of "0: schedule" and a "status" of "2: error" as shown in Figure 40(e).

In contrast, Figures 41(a) to 41(d) show the flow schedule execution setting master 14, the flow schedule execution setting parameter master 49, the flow execution instruction work 12 after the schedule has been reset, and the flow execution instruction parameter work 50. After the reservation execution button 33 is operated, the storage control unit 25 inputs the above-mentioned "temporary setting name" such as "Today 16:20" into the "Schedule ID" of the flow execution instruction work 12 shown in Figure 41(c), creates a record with the "Instruction type" set to "0: Schedule", the "Scheduled execution date and time" set to "2022/9/1 16:20:00", the "Status" set to "0: Unprocessed", and the "Processing result" set to blank, and adds it to the flow execution instruction work 12.

The storage control unit 25 stores the parameters of "file name" and "closing date classification" reset as the temporary schedule in the flow schedule execution setting parameter master 49 and the flow execution instruction parameter work 50, as shown in Figures 41(b) and 41(d), respectively.

(Effects of the embodiment)
As is clear from the above description, the execution control device 1 according to the embodiment can flexibly select the timing for re-executing a program (flow) that has failed to be executed.

In addition, regardless of the type of instruction causing the error, you can flexibly select and respond according to the situation, such as the environment conditions and the convenience of the person in charge.

Also, by adjusting parameter values and dividing the processing range, you can narrow the affected area and identify the location of the error.

In addition, by associating re-execution with the execution error log, it is possible to manage the outcome of execution logs for the same instructions, which can be used to ensure consistency in log management for control purposes and for future responses.

Specifically, the following effects can be achieved:

1. There are cases where you want to re-run the schedule even if an error occurs during manually executed flow processing. In this case, you want to avoid manual execution to avoid inconvenience to the person in charge and to avoid the server being busy. Also, there is a need for a function that allows you to set a schedule and re-run the process at any time, rather than when the cause of the error is resolved. When setting a schedule for such re-execution, there is a risk of changing the existing settings and forgetting to delete the temporary schedule settings.

However, in the embodiment, the execution control device 1 can temporarily enable the desired schedule setting for re-execution and re-execute the program (flow).

2. If an error occurs when running a program based on a schedule, you may want to manually re-run the program in cases where immediate recovery is required.

The execution control device 1 according to the embodiment has a function for manually re-executing or executing with the highest priority a program (flow) that has been executed according to a schedule, and can enable re-execution in a short time, such as immediately.

3. When re-executing a program (flow), there are cases where you want to reuse some of the original execution conditions and change some before re-executing, you want to force a re-execution without allowing changes to the original execution conditions, and you want to prevent accidentally changing something that shouldn't be changed when retrying.

The execution control device 1 according to the embodiment has a function of restoring the original execution conditions when a program (flow) is re-executed. Changeable and unchangeable execution conditions during re-execution can be set for each execution condition. This makes it possible to prevent input errors in the execution conditions during re-execution.

4. For each program (flow), there are programs (flows) that may be re-run and programs (flows) that should not be re-run. In other words, for example, closing processes or system integration flows, or other tasks that require immediate action in the event of an error, are programs (flows) that may be re-run. In contrast, test programs (flows) or complex business flows with heavy processing are programs (flows) that should not be re-run, as there is a risk that re-running them could affect existing flows in the operational environment.

The execution control device 1 of the embodiment allows the possibility of re-executing a program (flow) to be set for each program (flow). Therefore, re-execution can be controlled according to the type of program (flow), etc.

5. For each user authority, there are programs (flows) that you want the user to be able to execute (or re-execute) and programs (flows) that you do not want the user to be able to execute. For example, you may want to grant a person authority to execute only business flows that are within the scope of their work.

The execution control device 1 of the embodiment allows each user to set whether or not to execute a program (flow). This improves security for the execution of programs (flows).

[Contribution to the United Nations-led Sustainable Development Goals (SDGs)]
This embodiment can contribute to improving business efficiency and promoting appropriate management decisions by companies, thereby making it possible to contribute to Goals 8 and 9 of the SDGs.

In addition, this embodiment can contribute to reducing waste and promoting paperless and electronic systems, which can contribute to the achievement of SDGs Goals 12, 13, and 15.

In addition, this embodiment can contribute to strengthening control and governance, making it possible to contribute to Goal 16 of the SDGs.

[Other embodiments]
The present invention may be embodied in various different embodiments other than those described above within the scope of the technical concept set forth in the claims.

For example, among the processes described in the embodiments, all or part of the processes described as being performed automatically can be performed manually, or all or part of the processes described as being performed manually can be performed automatically using a known method.

In addition, the processing procedures, control procedures, specific names, registered data for each process, information including parameters such as search conditions, screen examples, and database configurations shown in this specification and drawings may be changed as desired unless otherwise specified.

Furthermore, with regard to the execution control device 1, each component shown in the figure is a functional concept, and does not necessarily have to be physically configured as shown in the figure.

For example, the processing functions of the execution control device 1, particularly the control unit 3 and each processing function performed by the control unit 3, may be realized in whole or in part by a CPU (Central Processing Unit) and a program interpreted and executed by the CPU, or may be realized as hardware using wired logic. The program is recorded on a non-transient computer-readable recording medium that contains programmed instructions for causing the information processing device to execute the processes described in this embodiment, and is mechanically read by the execution control device 1 as necessary. That is, a computer program is recorded in a storage unit such as a ROM or HDD for working with the OS to give instructions to the CPU and perform various processes. This computer program is executed by being loaded into RAM, and works with the CPU to configure the control unit 3.

In addition, the execution control program of this execution control device 1 may be stored in another server device connected to the execution control device 1 via any network, and it is also possible to download all or part of it as necessary.

The execution control program for executing the processes described in this embodiment may be stored in a non-transitory computer-readable recording medium, or may be configured as a program product. Here, the term "recording medium" includes any "portable physical medium" such as a memory card, a Universal Serial Bus (USB) memory, a Secure Digital (SD) card, a flexible disk, a magneto-optical disk, a ROM, an Erasable Programmable Read Only Memory (EPROM), an Electrically Erasable and Programmable Read Only Memory (EEPROM (registered trademark)), a Compact Disk Read Only Memory (CD-ROM), a Magneto-Optical Disk (MO), a Digital Versatile Disk (DVD), and a Blu-ray (registered trademark) Disc.

A "program" is a data processing method written in any language or description method, and may be in any format, such as source code or binary code. Note that a "program" is not necessarily limited to a single structure, but also includes a structure that is distributed as multiple modules or libraries, or a structure that achieves its function by working with a separate program, such as an OS. Note that the specific structure and reading procedure for reading a recording medium in the execution control device 1 shown in the embodiment, as well as the installation procedure after reading, can use well-known structures and procedures.

The memory unit 2 is a storage means such as a memory device such as RAM or ROM, a fixed disk device such as a hard disk, a flexible disk, or an optical disk, and stores various programs, tables, databases, and web page files used for various processes and providing websites.

The execution control device 1 may be configured as an information processing device such as a known personal computer device or a workstation, or may be configured as an information processing device to which any peripheral device is connected. The information processing device may also be realized by implementing software (including programs or data, etc.) that realizes the processing described in this embodiment.

Furthermore, the specific form of distribution and integration of the devices is not limited to that shown in the figures, and all or part of them can be functionally or physically distributed and integrated in any unit depending on various additions or functional loads. In other words, the above-mentioned embodiments can be implemented in any combination, or the embodiments can be implemented selectively.

The present invention is effective for re-executing programs that perform background processing, etc.

REFERENCE SIGNS LIST 1 Execution control device 2 Memory unit 3 Control unit 4 Communication interface unit 5 Input/output interface unit 6 Input device 7 Output device 11 Status management database (status management DB)
12 Flow execution instruction work 13 Master database (Master DB)
14 Flow schedule execution setting master 20 Display control unit 21 Asynchronous manager 22 Background execution management unit 23 Flow execution unit 24 Instruction creation unit 25 Storage control unit 31 Repriority execution button 32 Wait-for-turn execution button 33 Reservation execution button 41 Flow setting master 42 Schedule master 43 Flow parameter master 44 Flow execution permission master 45 Top priority execution permission master 46 User master 47 User group master 48 User group member master 49 Flow schedule execution setting parameter master 50 Flow execution instruction parameter work 53 Flow execution log 61 Schedule reset button 62 Manual re-execution button

Claims (8)

a display control unit that displays on a display unit a scheduled execution button for instructing re-execution of the program in which an execution error has occurred according to a desired schedule, a top priority execution button for manually instructing immediate execution of the program in which an execution error has occurred, and a queue execution button for manually setting the execution order of the program in which an execution error has occurred to the end of programs waiting to be executed;
a setting control unit which, when the reserved execution button is operated, stores a schedule for the execution of the program in which an execution error has occurred in a schedule execution setting storage unit in which schedules of programs waiting to be executed are stored, and, when the top priority execution button is operated, sets the execution order of the program in which an execution error has occurred to the top of the execution order in an execution order storage unit in which pre-execution program information indicating programs before execution is stored in an execution order designated for each of the programs, and, when the waiting execution button is operated, sets the execution order of the program in which an execution error has occurred to the end of the execution order stored in the execution order storage unit;
an execution control unit that controls the execution of each of the programs in accordance with the schedule of each of the programs stored in the schedule execution setting storage unit and in the execution order stored in the execution order storage unit;
An execution control device having: the display control unit displays, on the display unit, an execution condition at the time of execution of the program in which the execution error occurred, together with the reserved execution button, the top priority execution button, and the turn waiting execution button;
when the execution condition is changed, the setting control unit resets the changed execution condition to the program in which the execution error has occurred as an execution condition for the program in which the execution error has occurred;
the execution control unit re-executes the program in which the execution error has occurred based on the reset execution condition;
2. The execution control device according to claim 1 . The parameters included in the execution conditions are added with changeability information indicating whether the parameters can be changed,
the display control unit changes a display form of the changeable parameters and the unchangeable parameters among the parameters based on the changeability information, and displays the changeable parameters and the unchangeable parameters;
3. The execution control device according to claim 2, The program in which the execution error occurred is provided with re-executability information indicating whether or not the program can be re-executed,
the display control unit, when the re-execution permission information permitting re-execution is added to the program in which an execution error has occurred, displays the reserved execution button, the top priority execution button, and the queued execution button on the display unit, thereby enabling re-execution of the program in which an execution error has occurred;
4. The execution control device according to claim 3, The program in which the execution error occurred is provided with user authority information indicating a user who is permitted to re-execute the program in which the execution error occurred,
the execution control unit refers to an execution permission storage unit in which the user authority information of each user is stored, and determines whether the user authority of the user issuing an instruction to re-execute the program in which an execution error has occurred is a user with user authority to re-execute the program in which an execution error has occurred, and when it is determined that the instruction to re-execute the program in which an execution error has occurred is issued by a user with user authority to re-execute the program in which an execution error has occurred, re-executes the program in which an execution error has occurred;
The execution control device according to claim 4 . the execution control unit, when an instruction to execute the program in which the execution error has occurred is given by pressing a top priority execution button, refers to a top priority execution permission storage unit in which real-time execution user information indicating a user to whom user authority for real-time execution has been granted is stored, and when it is determined that the user who has given an instruction to execute the program in which the execution error has occurred by pressing the top priority execution button is a user to whom user authority for real-time execution has been granted, re-executes the program in which the execution error has occurred;
The execution control device according to claim 5 . a display control step in which a display control unit displays on a display unit a scheduled execution button for instructing re-execution of the program in which an execution error has occurred according to a desired schedule, a top priority execution button for manually instructing immediate execution of the program in which an execution error has occurred, and a queue execution button for manually setting the execution order of the program in which an execution error has occurred to the end of programs waiting to be executed;
a setting control step of, when the reserved execution button is operated, storing a schedule for the execution of the program in which an execution error has occurred in a schedule execution setting storage unit in which schedules of programs waiting to be executed are stored, when the top priority execution button is operated, setting the execution order of the program in which an execution error has occurred to the top of the execution order in an execution order storage unit in which pre-execution program information indicating programs before execution is stored in an execution order designated for each of the programs, and when the turn waiting execution button is operated, setting the execution order of the program in which an execution error has occurred to the end of the execution order stored in the execution order storage unit;
an execution control step in which an execution control unit controls the execution of each of the programs in accordance with the schedule of each of the programs stored in the schedule execution setting storage unit, and controls the execution of each of the programs in the execution order stored in the execution order storage unit;
The execution control method includes: Computer,
a display control unit that displays on a display unit a scheduled execution button for instructing re-execution of the program in which an execution error has occurred according to a desired schedule, a top priority execution button for manually instructing immediate execution of the program in which an execution error has occurred, and a queue execution button for manually setting the execution order of the program in which an execution error has occurred to the end of programs waiting to be executed;
a setting control unit which, when the reserved execution button is operated, stores a schedule for the execution of the program in which an execution error has occurred in a schedule execution setting storage unit in which schedules of programs waiting to be executed are stored, and, when the top priority execution button is operated, sets the execution order of the program in which an execution error has occurred to the top of the execution order in an execution order storage unit in which pre-execution program information indicating programs before execution is stored in an execution order designated for each of the programs, and, when the waiting execution button is operated, sets the execution order of the program in which an execution error has occurred to the end of the execution order stored in the execution order storage unit;
functioning as an execution control unit that controls the execution of each of the programs in accordance with the schedule of each of the programs stored in the schedule execution setting storage unit and in the execution order stored in the execution order storage unit;
An execution control program comprising:

Images