Execution control device, execution control method, and execution control program

Abstract

To make it possible to flexibly select the timing for re-executing a program (flow) that has failed to execute.SOLUTION: A display control unit displays, on a display unit, a manual instruction button for instructing manual re-execution of a program in which an execution error has occurred, and a reservation execution button for instructing re-execution based on a schedule, and when the manual instruction button is operated, displays on the display unit a top priority execution button for instructing immediate execution of the program in which the execution error has occurred, and a queue execution button for setting the execution order of the program in which the execution error has occurred to the end of programs waiting to be executed. Users can re-execute the program in which the execution error has occurred at desired timing by operating the desired button. As a result, the program (flow) can be re-executed flexibly according to user's desired timing as the timing for re-executing the program (flow) that has failed to execute.SELECTED DRAWING: Figure 1

Description

Technical Field

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

Background Art

[0002] Today, with the progress of the introduction of AI (Artificial Intelligence) or RPA (Robotic Process Automation) and its penetration into society, routine work or standardized operations are scheduled and largely automated.

[0003] Patent Document 1 (Japanese Patent Application Laid-Open No. 2015-219920) discloses a control system that enables calibration so as to cause as little interference as possible to the operations performed by an operator or other users.

[0004] When this control system executes calibration, it acquires information for specifying the common sheet type used in the printing device to be monitored, determines whether the state of the printing device satisfies a predetermined condition according to the printing amount of the printing device, and determines whether the printing device holds the common sheet type based on the acquired information. Then, when it is determined that the predetermined condition is satisfied and that the common sheet type is held, calibration is executed by causing the printing device to print on the common sheet type. The result of the calibration executed using the common sheet type is applied to other sheet types. Thereby, the execution of calibration is enabled so as to cause as little interference as possible to the operations performed by an operator or other users.

[0005] This Patent Document 1 discloses a technique in paragraph 0022 and the like that can specify the scheduled execution and manual execution of calibration.

Prior Art Documents

Patent Documents

[0006]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0007] Execution of a predetermined program (flow) such as background processing may fail. As causes of this execution failure, various causes can be considered, such as problems with business masters, setting mistakes, environmental troubles, etc., from the application layer to the physical layer. Identifying the cause and implementing recovery requires high intellectual ability and skills, which is difficult for general users and takes time. Also, for example, programs (flows) such as in-business alert notifications or file linkages between systems will cause problems in business when their execution fails.

[0008] Here, for a program (flow) that has failed in execution, there are cases where it is desired to re-execute it immediately rather than identifying the cause of failure, and there are also cases where it is re-executed based on a desired schedule, such as re-executing outside business hours. For these reasons, there is a need for a technology that enables flexible selection of the timing to re-execute a program (flow) that has failed in execution.

[0009] The present invention has been made in view of the above problems, and an object thereof is to provide an execution control device, an execution control method, and an execution control program that enable flexible selection of the timing to re-execute a program (flow) that has failed in execution.

Means for Solving the Problems

[0010] In order to solve the above problems and achieve the object, the execution control device according to the present invention includes a reserved execution button for instructing re-execution of a program in which an execution error has occurred at a desired schedule, a highest-priority execution button for manually instructing immediate execution of the program in which the execution error has occurred, and a waiting-order execution button for manually setting the execution order of the program in which the execution error has occurred at the end of the programs waiting to be executed, and a display control unit that displays them on a display unit; a setting control unit that, when the reserved execution button is operated, stores the execution schedule of the program in which the execution error has occurred in a schedule execution setting storage unit that stores the schedules of the programs waiting to be executed, and when the highest-priority execution button is operated, sets the execution order of the program in which the execution error has occurred to the top execution order with respect to an execution order storage unit that stores the pre-execution program information indicating the program before execution in the execution order specified for each program, and when the waiting-order execution button is operated, sets the execution order of the program in which the execution error has occurred at 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.

[0011] In addition, in order to solve the above-described problems and achieve the object, the execution control method according to the present invention includes a display control step in which a display control unit displays on a display unit a reservation execution button for instructing re-execution of a program in which an execution error has occurred at a desired schedule, a top-priority execution button for manually instructing immediate execution of the program in which the execution error has occurred, and a queued execution button for manually setting the execution order of the program in which the execution error has occurred at the end of the programs waiting for execution; a setting control step in which, when the reservation execution button is operated, a setting control unit stores the execution schedule of the program in which the execution error has occurred in a schedule execution setting storage unit in which the schedules of the programs waiting for execution are stored, when the top-priority execution button is operated, sets the execution order of the program in which the execution error has occurred to the top execution order with respect to an execution order storage unit in which pre-execution program information indicating the program before execution is stored in the execution order specified for each program, and when the queued execution button is operated, sets the execution order of the program in which the execution error has occurred at the end of the execution order stored in the execution order storage unit; and an execution control step in which an execution control unit 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.

[0012] Also, in order to solve the above-described problems and achieve the object, the execution control program according to the present invention causes a computer to display, on a display unit, a reservation execution button for instructing re-execution of a program in which an execution error has occurred at a desired schedule, a highest priority execution button for manually instructing immediate execution of the program in which the execution error has occurred, and a queued execution button for manually setting the execution order of the program in which the execution error has occurred at the end of the programs waiting for execution; a display control unit that, when the reservation execution button is operated, stores the execution schedule of the program in which the execution error has occurred in a schedule execution setting storage unit that stores the schedules of the programs waiting for execution, and when the highest priority execution button is operated, sets the execution order of the program in which the execution error has occurred to the top execution order with respect to an execution order storage unit that stores, in the specified execution order for each program, the pre-execution program information indicating the program before execution, and when the queued execution button is operated, sets the execution order of the program in which the execution error has occurred at the end of the execution order stored in the execution order storage unit; and a setting control unit that functions as 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.

Effect of the Invention

[0013] The present invention can flexibly select the timing for re-executing a program (flow) that has failed in execution.

Brief Description of the Drawings

[0014]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Figure 17

Figure 18

Figure 19

Figure 20

Figure 21

Figure 22

Figure 23

Figure 24

Figure 25

Figure 26

Figure 27

Figure 28

Figure 29

Figure 30

Figure 31

Figure 32

Figure 33

Figure 34

Figure 35

Figure 36

Figure 37

Figure 38

Figure 39

Figure 40

Figure 41

Embodiment for Carrying Out the Invention

[0015] Hereinafter, an execution control device according to an embodiment to which the present invention is applied will be described in detail with reference to the drawings. Note that the present invention is not limited to the following embodiments. Also, "program" and "flow" will be described as synonyms.

[0016] (Hardware Configuration) As shown in FIG. 1, the execution control device 1 of the 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. As the output device 7, a display unit such as a monitor device (including a home TV), a printing device, or a speaker device corresponds. As the input device 6, in addition to a keyboard device, a mouse device, and a microphone device, a monitor device that realizes a pointing device function in cooperation with the mouse device can be used. 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).

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

[0018] (Functional Configuration of Execution Control Device) Next, the control unit 3 functions as a display control unit 20 and an asynchronous manager 21 as shown in FIG. 1 by executing the execution control program stored in the storage unit 2. The asynchronous manager 21 includes a background execution management unit 22, a flow execution unit 23, an instruction creation unit 24, a storage control unit 25, and the like. The background execution management unit 22, the instruction creation unit 24, and the storage control unit 25 are examples of a setting control unit. Also, the flow execution unit 23 is an example of an execution control unit.

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

[0020] When the reserved 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 an execution error has occurred in a schedule execution setting storage unit (flow schedule execution setting master 14) in which the schedules of the programs waiting for execution are stored.

[0021] Also, when the highest priority 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 set the execution order of the program in which an execution error has occurred to the top execution order with respect to an execution order storage unit (flow execution instruction work 12) in which pre-execution program information indicating the program before execution is stored in the specified execution order for each program.

[0022] In addition, when the background execution management unit 22, instruction creation unit 24, and memory control unit 25 that constitute the setting control unit operate the waiting execution button in sequence, they set the execution order of the program in which the execution error has occurred to the end of the execution order stored in the execution order storage unit (flow execution instruction work 12).

[0023] 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).

[0024] In addition, the display control unit 20 displays the execution conditions at the time of executing the program in which the execution error has occurred on the display unit (output device 7) together with the reservation execution button 33, the highest priority execution button 31, and the waiting execution button 32 in sequence. When the execution conditions are changed by the background execution management unit 22, instruction creation unit 24, and memory control unit 25 that constitute the setting control unit, the changed execution conditions are reset to the program in which the execution error has occurred as the execution conditions for the program in which the execution error has occurred. Then, the execution control unit (flow execution unit 23) re-executes the program in which the execution error has occurred based on the reset execution conditions.

[0025] In addition, changeable information indicating whether change is possible is added to the parameters included in the execution conditions. In this case, the display control unit 20 changes and displays the display form of the parameters that can be changed and the parameters that cannot be changed among the parameters based on the changeable information.

[0026] In addition, re-execution possible information indicating whether re-execution is possible is added to the program in which the execution error has occurred. In this case, when the re-execution possible information that permits re-execution is added to the program in which the execution error has occurred, the display control unit 20 displays the reservation execution button 33, the highest priority execution button 31, and the waiting execution button 32 in sequence on the display unit (output device 7) to enable re-execution of the program in which the execution error has occurred.

[0027] In addition, user privilege information indicating a user who permits the re - execution of a program in which an execution error has occurred is added to the program in which the execution error has occurred. In this case, the execution control unit (flow execution unit 23) refers to an execution permission storage unit (flow execution permission master 44 in FIG. 6) in which the user privilege information of each user is stored.

[0028] Then, the execution control unit (flow execution unit 23) determines whether the user privilege of the user who instructs the re - execution of the program in which the execution error has occurred is a user with the user privilege for the re - execution of the program in which the execution error has occurred. When it is determined that the instruction for re - execution is from a user with the user privilege for the re - execution of the program in which the execution error has occurred, the execution control unit re - executes the program in which the execution error has occurred.

[0029] In addition, when the immediate execution of a program in which an execution error has occurred is instructed by the top - priority execution button 31, the execution control unit (flow execution unit 23) refers to a top - priority execution permission storage unit (top - priority execution permission master 45 in FIG. 7) in which immediate execution user information indicating a user to whom the immediate execution user privilege is granted is stored. Then, when the execution control unit (flow execution unit 23) determines that the user who instructed the immediate execution of the program in which the execution error has occurred by the top - priority execution button 31 is a user to whom the immediate execution user privilege is granted, the execution control unit re - executes the program in which the execution error has occurred.

[0030] (Operation Outline) FIG. 2 is a diagram showing an operation outline of the execution control device 1 according to the embodiment. As shown in this FIG. 2, for example, when an execution error occurs when executing a program (flow) in the background, the display control unit 20 displays the top - priority execution button 31, the execution - in - turn button 32, and the 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).

[0031] When the highest-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 to interrupt and be set at the head of the programs (flows) arranged in the execution order in the flow execution instruction work 12. As a result, the background execution management unit 22 and the flow execution unit 23 immediately re-execute the program (flow) that has caused an execution error.

[0032] When the queued 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 execution order in the flow execution instruction work 12. As a result, the background execution management unit 22 and the flow execution unit 23 can re-execute the program (flow) that has caused an execution error following the previously set program (flow).

[0033] When the scheduled execution button 33 is operated, the instruction creation unit 24 and the memory control unit 25 set the 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 the 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 has caused an execution error is re-executed.

[0034] To explain in more detail, the background execution management unit 22 periodically monitors the data of the flow execution instruction work 12 in the state management DB 11. The monitoring target is only the data of the flow execution instruction work 12 whose "status" is unprocessed. The background execution management unit 22 transmits to the flow execution unit 23 a flow ID that identifies the program associated with the scheduled execution date and time as an argument. Thereby, the flow execution unit 23 executes the program (flow) corresponding to the flow ID. When the background execution management unit 22 transmits the flow ID as an argument to the flow execution unit 23, or when the processing of this program (flow) is completed, the background execution management unit 22 performs a rewrite process on the "status" of the target data of the flow execution instruction work 12.

[0035] In addition, the background execution management unit 22 sequentially processes the execution of programs (flows) in the following order.

[0036] a. Those with "instruction type" being "2: highest priority"> ascending order of "scheduled execution date and time" b. Those with "instruction type" being "0: schedule" or "1: waiting in order"> ascending order of [scheduled execution date and time]

[0037] Thereby, even if those with "instruction type" being "2: highest priority" are added afterwards, they can always be interruptively executed prior to the existing "b" and given priority to "a".

[0038] In addition, the background execution management unit 22 is set in advance by a task schedule or the like on a web server device or a DB server so that this process is automatically executed periodically.

[0039] The flow execution unit 23 determines the program (flow) to be executed based on the flow ID of the argument transmitted from the background execution management unit 22. Based on the flow ID of the argument, the flow execution unit 23 performs the actual processing of the program (flow) according to the definition content of the detailed settings (see Figure 3) of the flow setting master 41.

[0040] (Configuration of various masters) FIG. 3 is a diagram showing an example of the flow setting master 41 stored in the master DB 13. As shown in this FIG. 3, the flow setting master 41 includes a flow identification number (flow ID), a system, a re-execution permission flag, and detailed settings, etc. In the example of this FIG. 3, it shows that the program (flow) of the qualification expiration alert is set to be executable by the Personnel Department, but re-execution is not permitted (re-execution permission flag = 0: rejected). Also, the program (flow) of the disaster alert linkage is set to be executable by the Operations Management Department, indicating that re-execution is also permitted (re-execution permission flag = 1: permitted). Further, the flow execution unit 23 performs the actual processing of the program (flow) according to the defined content of the "detailed settings".

[0041] FIG. 4 is a diagram showing an example of the schedule master 42 stored in the master DB 13. The schedule master 42 includes a schedule ID and schedule detailed settings, etc. In the example of this FIG. 4, the schedule ID of "EveryDay230" indicates that it is a schedule ID for designating the execution of the program (flow) at 2:30 every morning. Similarly, the schedule ID of "Every10minUntil2300" indicates that it is a schedule ID for designating the execution of the program (flow) every 10 minutes until 23:00 every day.

[0042] FIG. 5 is a diagram showing an example of the flow parameter master 43 stored in the master DB 13. As shown in this FIG. 5, the flow parameter master 43 includes a flow ID, a parameter ID, a data type, a mandatory flag, a default value, and a re-execution value change permission flag, etc. In the case of the example of this FIG. 5, the re-execution value change permission flag of the program (flow) with the flow ID of "qualification expiration alert" is "1: permitted", indicating that the value of the parameter can be changed during re-execution. Similarly, in the case of the example of this FIG. 5, the re-execution value change permission flag of the parameter of the "calculation type" of the program (flow) with the flow ID of "attendance calculation execution" is "0: rejected", indicating that it is not permitted to change the value of the parameter during re-execution.

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

[0044] FIG. 7 is a diagram showing an example of the highest priority execution permission master 45 stored in the master DB 13. In this highest priority execution permission master 45, user group information (internal user group Guid) for which immediate execution of a program (flow) is permitted is registered (stored).

[0045] FIG. 8 is a diagram showing an example of the user master 46 stored in the master DB 13. As shown in this FIG. 8, the user master 46 stores an internal user Guid, a user ID, a user name, a password, and the like.

[0046] FIG. 9 is a diagram showing an example of the user group master 47 stored in the master DB 13. As shown in this FIG. 9, the user group master 47 stores an internal user group Guid, a user group name, and the like.

[0047] FIG. 10 is a diagram showing an example of the user group member master 48 stored in the master DB 13. As shown in this FIG. 10, the user group member master 48 stores an internal user group Guid, an internal user Guid, and the like.

[0048] FIG. 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 this FIG. 11, the flow schedule execution setting parameter master 49 stores a schedule execution setting ID, a parameter ID, a setting value, and the like.

[0049] FIG. 12 is a diagram showing an example of a flow schedule execution setting master 14 stored in the master DB 13. As shown in this FIG. 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, an error source instruction Guid, etc.

[0050] FIG. 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 FIG. 13, the flow execution instruction parameter work 50 stores an instruction Guid, a parameter ID, an execution value, etc.

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

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

[0053] First, when an operator designates the setting of the execution of a desired program (flow), the display control unit 20 controls the display of the execution instruction common screen illustrated in FIG. 15 via the output device 7. The display control unit 20 displays, on this execution instruction common screen, a selection field for the program (flow) that designates execution, an input field for the schedule, an input field for the parameter, a most-priority execution button 31, a queued execution button 32, a reserved execution button 33, etc. for designating the timing of execution.

[0054] The display control unit 20 refers to the flow setting master 41, detects only the program name of the program (flow) for which the operator has execution authority, and displays it in the selection field for the program (flow) to be executed.

[0055] Also, the display control unit 20 refers to the schedule master 42 and displays the execution schedule in the schedule input field. Further, the display control unit 20 displays the value of the parameter set in the flow parameter master 43 in the parameter input field. By changing the parameter set in the flow parameter master 43, the value of the parameter displayed in the parameter input field can be changed to a desired value.

[0056] As described above, the top - priority execution button 31 is a button operated when interrupting the program (flow) waiting to be executed to the head of the programs (flows) waiting to be executed and making it execute with the highest priority. The sequential - execution button 32 is a button operated when setting the program (flow) to the end of the programs (flows) waiting to be executed and making it execute in order. The reserved - execution button 33 is a button operated when executing the program (flow) by specifying a desired schedule.

[0057] The display control unit 20 may display the top - priority execution button 31 and the sequential - execution button 32 only when manual execution of the program (flow) is specified. Also, the display control unit 20 refers to the top - priority execution permission master 45 shown in FIG. 7 and displays the top - priority execution button 31 only when it is determined that the user group, operator, etc. are permitted to specify top - priority execution (not displayed if not permitted). Further, the display control unit 20 may display the schedule input field and the reserved - execution button only when schedule execution of the program (flow) is specified.

[0058] (Red - execution instruction common screen) Next, when the operator designates the setting for re - executing a desired program (flow), the display control unit 20 controls the display via the output device 7 to display a re - execution instruction common screen illustrated in FIG. 16. The display form of this re - execution instruction common screen is substantially the same as that of the above - mentioned execution instruction common screen. That is, the display control unit 20 provides, on this re - execution instruction common screen, a selection column for the program (flow) to be re - executed, an input column for the original schedule, an input column for the temporary schedule, an input column for parameters, an input column for the parameters (previous values) at the previous execution, a most - priority execution button 31 for designating the execution timing, a queued execution button 32, a reserved execution button 33, and the like.

[0059] The display control unit 20 controls the display or non - display of the original schedule and the original setting name depending on whether the instruction type of the flow execution instruction work 12 is a schedule (previous execution method), and controls the display or non - display of the temporary schedule and the temporary setting name depending on whether the instruction type of the transfer item (current execution method) is a schedule. That is, by referring to the flow execution instruction work 12, the display control unit 20 displays the program (flow) in which an error occurred during the previous execution in the selection column of the program (flow) to be re - executed. Also, by referring to the flow execution instruction work 12, the display control unit 20 displays the schedule of the program (flow) in which an error occurred during the previous execution in the input column for the original schedule. Note that "original" means the program (flow) in which an error occurred during the previous execution.

[0060] Also, by referring to the flow execution instruction parameter work 50, the display control unit 20 detects the parameter value (previous value) of the program (flow) in which an error occurred during the previous execution and displays it in the input column for the parameters (previous values) at the previous execution.

[0061] As described above, the top - priority execution button 31 is a button that is operated when interrupting the program (flow) to be re - executed at the head of the programs (flows) waiting to be executed and causing it to be executed with top - priority. The sequential - execution button 32 is a button that is operated when setting the program (flow) to be re - executed at the end of the programs (flows) waiting to be executed and causing it to be executed in order. The reserved - execution button 33 is a button that is operated when specifying a desired schedule and causing the program (flow) to be re - executed to be executed.

[0062] The display control unit 20 may display the top - priority execution button 31 and the sequential - execution button 32 only when manual execution of the program (flow) is specified. Also, the display control unit 20 refers to the top - priority execution permission master 45 shown in FIG. 7 and displays the top - priority execution button 31 only when it is determined that the top - priority execution specification is permitted for the user group, operator, etc. (when not permitted, it is not displayed). Also, the display control unit 20 may display the schedule input field and the reserved - execution button only when schedule execution of the program (flow) is specified.

[0063] (Execution authority and re - execution authority of the program (flow)) The execution or re - execution of the program (flow) is divided into a "normal authority" that sets it at the end of the programs (flows) waiting to be executed and executes it in order (normal execution) and a "top - priority authority" that interrupts and executes it at the head of the programs (flows) waiting to be executed. The display control unit 20 refers to the flow - setting master 41, flow - execution permission master 44, top - priority execution permission master 45, user master 46, user - group master 47, and user - group member master 48 shown in FIG. 17 for the normal authority of the program (flow) (in particular, refers to the flow - execution permission master 44) to determine the user group to which the execution authority is granted for that program (flow). Also, at the time of re - execution, the display control unit 20 further refers to the "re - execution permission flag" in the flow - setting master 41 in addition to such execution authority.

[0064] In addition, the display control unit 20 assumes normal authority for the highest priority for a program (flow), and determines whether the highest priority is granted to the user group in the "Highest Priority Execution Permission Master 45". When the display control unit 20 has normal authority but the highest priority is not set, the highest priority execution button 31 is made non-displayed for the execution instruction common screen or the re-execution instruction common screen.

[0065] (Example of determination result) FIG. 18 is a diagram showing an example of such a determination result. In this FIG. 18, "〇" indicates "authorized", and "×" indicates "not authorized". For example, in the case of user 10001, it has normal authority for flow A during execution but does not have the highest priority. Also, in the case of user 10001, it has normal authority for flow A during re-execution but does not have the highest priority. Similarly, in the case of user 10002, it does not have both normal authority and the highest priority for flow A during execution and re-execution. Also, in the case of user 10003, it has both normal authority and the highest priority for flow A during execution and re-execution.

[0066] (Display control of parameters, etc.) Next, the 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, as shown in FIG. 14, the retry classification, instruction type, and error source instruction Guid as "delivery items".

[0067] The "retry classification" is information indicating whether the program (flow) is for the first execution or for re-execution. In the case of the first execution, "0: execution" is set, and in the case of re-execution, "1: re-execution" is set.

[0068] As for the "instruction type" of the delivery item, when the execution or re - execution of the program (flow) is based on a schedule, "0: schedule" is set, and when the execution is based on a manual operation, "1: manual" is set.

[0069] The "error source instruction Guid" is a Guid that enables the restoration of the program (flow), parameters, and schedule at the time of the previous execution when the program (flow) is re - executed.

[0070] The display control of parameters, etc. for each combination pattern of such delivery items is as follows.

[0071] First, when the "instruction type" of the delivery item is "1: manual" and the "retry category" is "0: execution", the display control unit 20, as shown in Fig. 19(a), displays the highest - priority execution button 31 and the execution - waiting - in - line button 32 on the execution instruction common screen shown in Fig. 15. Also, the display control unit 20 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 fields of the execution instruction common screen in a state where the operator can change them, as shown in Fig. 19(a).

[0072] Next, when the "instruction type" of the delivery item is "0: schedule" and the "retry category" is "0: execution", the display control unit 20, as shown in Fig. 20(a), displays the reserved execution button 33 on the execution instruction common screen shown in Fig. 15. Also, the display control unit 20 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 together with the schedule of the program (flow) in the parameter input fields of the execution instruction common screen, as shown in Fig. 20(a). Each parameter is always displayed in a state where the operator can change it.

[0073] Next, FIG. 21 shows an example where the execution in accordance with the execution order was manually set during the previous execution (originally manual), and the normal execution in accordance with the execution order was manually set also during re-execution. In this case, the "instruction type" of the delivery item is "1: Manual", and the "retry classification" is "1: Re-execution". As shown in FIG. 21(a), the display control unit 20 displays the top-priority execution button 31 and the waiting-in-order execution button 32 on the re-execution instruction common screen.

[0074] Also, the display control unit 20 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 as shown in FIG. 21(a), displays them in the input field of the previous value on the re-execution instruction common screen in a non-modifiable state as the "previous value".

[0075] Also, as shown in FIG. 21(b), the re-execution value change permission classification for the first parameter is set to "1: Permitted", the re-execution value change permission classification for the second parameter is set to "1: Permitted", and the re-execution value change permission classification for the third parameter is set to "0: Denied". Therefore, since the re-execution value change permission classification for the third parameter in the input field of the parameters of the program (flow) to be re-executed is set to "0: Denied", the display control unit 20 inputs the value at the previous execution in a non-modifiable state, and inputs the value at the previous execution in a modifiable state in the input fields of the first parameter and the second parameter. In this case, the first parameter and the second parameter can be arbitrarily changed by the operator. The example in FIG. 21(a) is an example where the operator changed the first parameter to a first new value, and the second parameter used the previous value without being changed.

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

[0077] Also, the display control unit 20 refers to the flow parameter master 43 shown in FIG. 22(b), reads the first value of the first parameter for the fourth flow, and as shown in FIG. 22(a), displays it as the "previous value" in the input field for the previous value on the re-execution instruction common screen. Further, as shown in FIG. 22(b), since the re-execution value change permission classification of the first value of this first parameter is "1: permitted", the display control unit 20 displays the first value of the first parameter in the input field for the value of the first parameter on the re-execution instruction common screen in a state where the operator can change it.

[0078] Next, FIG. 23 shows an example where the execution based on the schedule was set during the previous execution (originally schedule), and the re-execution is set to be manual during the re-execution. In this case, the "instruction type" of the delivery item is "1: manual", and the "retry classification" is "1: re-execution". As shown in FIG. 23(a), the display control unit 20 displays the highest priority execution button 31 and the execution button waiting in line 32 on the re-execution instruction common screen.

[0079] Also, the display control unit 20 refers to the flow parameter master 43 shown in FIG. 23(b), reads the first value of the first parameter for the fifth flow, but as shown in FIG. 23(a), it is always displayed in the input field for the "previous value" in a state where the operator cannot change it. Since the re-execution value change permission classification for the first value of this first parameter is "0: rejected", the display control unit 20 displays the first value of the first parameter in the input field for the first parameter in a state where it cannot be changed.

[0080] Next, FIG. 24 shows an example where execution based on a schedule was set during the previous execution (original schedule), and re - execution based on the schedule was also set during re - execution. In this case, the “instruction type” of the delivery item is “0: schedule”, and the “retry classification” is “1: re - execution”. As shown in FIG. 24(a), the display control unit 20 displays the flow name at the previous execution (the 6th flow), the previous schedule (original schedule: 15:00 on weekdays), the original setting name (Flow B 15:00 on weekdays), the temporary schedule (every 10 minutes (up to 3 times)), the temporary setting name (Flow B every 10 minutes (3)), and the reserved execution button 33 on the re - execution instruction common screen.

[0081] Also, the display control unit 20 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 6th flow. In this example, depending on the re - execution value change permission classification, the change of the first value of the first parameter is permitted (1: permitted), but the change of the second value of the second parameter is not permitted (0: rejected).

[0082] Therefore, the display control unit 20 displays the first value of the first parameter in the input field for the value of the first parameter in a state where the operator can change it, and displays the second value of the second parameter in the input field for the value of the second parameter in a state where the operator cannot change it. 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 the input field for the previous value in a state where they cannot be changed.

[0083] (Manual execution instruction) Next, when a manual execution instruction is given, the operator selects and operates "Execution Instruction (Manual)" from the job list displayed on the menu screen shown in Fig. 25(a). The display control unit 20 displays the execution instruction (manual) screen shown in Fig. 25(b) via the output device 7 when the retry classification of the delivery item is "0: Execution" and the instruction type is "1: Manual". The display control unit 20 displays a selection bar for a desired program (flow), an input field for the qualification classification, a top-priority execution button 31, and a queued execution button 32 on this execution instruction (manual) screen. Each parameter is always displayed in a state where it can be changed by the operator.

[0084] The operator selects a program (flow) to be manually executed, such as "Qualification Expiration Alert", from the program (flow) selection bar. Also, the operator inputs the qualification classification such as "1: XX Qualification", which is the qualification for executing this "Qualification Expiration Alert", into the input field for the qualification classification. Then, the operator operates the top-priority execution button 31 or the queued execution button 32.

[0085] Figs. 26(a) to 26(d) show the flow setting master 41, the flow parameter master 43, the flow execution instruction work 12, and the flow execution instruction parameter work 50. When the top-priority execution button 31 is operated by the operator, the storage control unit 25 updates the "instruction type" of the flow execution instruction work 12 shown in Fig. 26(c) to "2: Top Priority". Also, when the queued execution button 32 is operated by the operator, the storage control unit 25 updates the "instruction type" of the flow execution instruction work 12 shown in Fig. 26(c) to "1: Queued". Note that the storage control unit 25 updates the "scheduled execution date and time" of the flow execution instruction work 12 shown in Fig. 26(c) to the current date and time.

[0086] (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 classification 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 a desired program (flow), an input field for a desired schedule, an input field for the schedule setting name, an input field for the qualification classification, and a reservation execution button 33 on this execution settings (schedule) screen.

[0087] The operator selects a program (flow) to be executed according to a schedule such as "Expired Qualification Alert" from the selection field for the program (flow). Also, the operator inputs a qualification classification such as "1: XX Qualification", which is the qualification for executing this "Expired Qualification Alert", into the input field for the qualification classification. Further, the operator inputs a desired schedule for executing the program (flow), such as "2:30 every morning", into the input field for the schedule, and inputs a desired setting name, such as "Expired Qualification Alert at 2:30 in the morning". Then, the operator operates the reservation execution button 33.

[0088] Figs. 28(a) to 28(e) show the schedule master 42, the flow schedule execution settings master 14, the flow schedule execution settings parameter master 49, the flow execution instruction work 12, and the flow execution instruction parameter work 50. When the reservation execution button 33 is operated by the operator, the memory control unit 25 stores the master data in the flow schedule execution settings master 14 shown in Fig. 28(b) and the flow schedule execution settings parameter master 49 shown in Fig. 28(c). Also, the instruction creation unit 24 that periodically monitors the set master data calculates the next execution date and time based on the current time and the schedule settings. Then, the memory control unit 25 sets a schedule for "Expired Qualification Alert" with the "instruction type" set to "0: Schedule" and the "scheduled execution date and time" set to 2:30 every morning in the flow execution instruction work 12 shown in Fig. 28(d).

[0089] Regarding the creation of batch execution instructions, when 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, when 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.

[0090] The schedule set for the flow execution instruction work 12 in this way is regularly monitored by the background execution management unit 22 and sent to the flow execution unit 23 when the execution date and time arrives.

[0091] (Display of Execution Result Inquiry Screen) Next, the execution control device 1 of the embodiment displays a list of the execution results of each program (flow), and can select and re-execute the program (flow) in which an execution error has occurred. When displaying a list of the execution results of each program (flow), the operator selects the "Execution Result Inquiry" job from the menu screen shown in Fig. 29(a). Thereby, the display control unit 20 displays a list of the execution results of each program (flow) via the execution result inquiry screen shown in Fig. 29(b). Also, the display control unit 20 displays a schedule re-setting button 61 and a manual re-execution button 62 together with this list on the execution result inquiry screen.

[0092] Further, when a record (detail) of a desired execution result is selected and operated by the operator 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).

[0093] Figure 30(a) shows the flow execution instruction work 12. Also, Figure 30(b) shows the reference data referred to when displaying the execution result inquiry screen. As shown in this Figure 30(b), the display control unit 20 acquires and displays the execution schedule setting name of the flow schedule execution setting master 14 as the "setting name" in the list, and acquires and displays from the flow ID of the flow execution instruction work 12 as the "program (flow)" in the list.

[0094] Also, the display control unit 20 acquires and displays the "result" in the list from the "status" of the flow execution instruction work 12, and acquires and displays the "processing date and time" in the list from "processing start" to "processing end" of the flow execution instruction work 12. Also, the display control unit 20 displays the time from "processing start" to "processing end" of the flow execution instruction work 12 as the "processing time" in the list, and acquires and displays the "processing result" of the flow execution instruction work 12 as the "message" in the list.

[0095] Also, the display control unit 20 acquires and displays the "rerun" in the list from the "retry classification" of the flow execution instruction work 12, and acquires and displays the "instruction type" of the flow execution instruction work 12 as the "instruction type" in the list.

[0096] Also, Figure 30(c) shows the reference data referred to when displaying the detailed log of Figure 29(c). As shown in this 30(c), the display control unit 20 acquires and displays the "task" of the detailed log as the "task ID" of the flow execution log 53 shown in Figure 30(d), and acquires and displays the "status" of the detailed log from the "status" of the flow execution log 53.

[0097] Also, the display control unit 20 displays the date and time indicated by "processing start" to "processing end" of the flow execution log 53 shown in Figure 30(d) as the "processing date and time" of the detailed log, and acquires and displays the "message" of the flow execution log 53 as the "message" of the detailed log.

[0098] (Manual rerun of the program (flow) for which an execution error occurred during the previous manual execution) Next, the execution control device 1 of the embodiment can select a program (flow) in which an execution error has occurred from the execution results thus listed and re-execute it manually. That is, as shown in FIGS. 31(a) and 31(b), when an operator selects a record (detail) of the program (flow) to be re-executed from the list of the above-described execution results and operates the manual re-execution button 62, the display control unit 20, when the retry classification of the delivery item is "1: Re-execute" and the instruction type is "1: Manual", uses the "Instruction Guid" of the selected row in FIG. 31(b) as the error source instruction Guid and displays a re-execution instruction (manual) screen shown in FIG. 31(c) via the output device 7.

[0099] At this time, since the re-execution value change permission classifications for the parameter IDs of "Transmission Target" and "Redelivery Classification" in the flow parameter master 43 shown in FIG. 32(b) are both "1: Permitted", the display control unit 20 displays the input fields for the parameters of "Transmission Target" and "Redelivery Classification" shown in FIG. 31(c) in a state where the operator can change the values. Note that since it is an execution instruction for re-execution, the display control unit 20 displays the name of the program (flow) executed last time in a state where it cannot be changed, and also displays the previous value, which is the parameter used at the previous execution, in a state where it cannot be changed.

[0100] The operator sets the parameters of the program (flow) to be re-executed for this re-execution instruction (manual) screen. The example in FIG. 31(c) is an example of re-executing the program (flow) of "Batch transmission of training emails", and the operator sets the parameter of "Transmission Target" to "All" and the parameter of "Redelivery Classification" to "Redelivery". When the operator sets the parameters, the operator operates the top-priority execution button 31 or the execution button waiting in line 32.

[0101] 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 operation of the top priority execution button 31 or the waiting-in-line execution button 32, in the flow execution instruction work 12, as shown in FIG. 32(c), the "instruction type" is "1: waiting in line" or "2: top priority", and the "status" is "2: error".

[0102] When the top priority execution button 31 or the waiting-in-line execution button 32 is operated, the storage control unit 25 generates a record with the "instruction type" set to "1: waiting in line" or "2: top priority" according to the button operated by the operator, the "status" set to "0: unprocessed", and the "processing result" blank, as shown in FIG. 32(e), and adds this record 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. Thereby, the error source instruction Guid of the record added in FIG. 32(e) can be associated with the instruction Guid in FIG. 32(c), and the added record can be held. Note that the storage control unit 25 stores the parameters of "all" in the "transmission target" and the parameter of "retransmission" in the "retransmission category" in the flow execution instruction parameter work 50, as shown in FIG. 32(f).

[0103] (Resetting in the schedule setting of the program (flow) in which an execution error occurred when manually executed last time) Next, an operation of selecting a program (flow) that caused an execution error by manual execution from the above-listed execution results, changing the execution form to execution based on a schedule, and reconfiguring this schedule will be described. In this case, as shown in FIGS. 33(a) and 33(b), the operator displays the list of the above-described execution results, selects the record (detail) of the program (flow) to be re-executed, and operates the schedule reconfiguration button 61. When the retry classification of the delivery item is "1: Re-execute" and the instruction type is "0: Schedule", the display control unit 20 displays the re-execution setting (schedule) screen shown in FIG. 33(c) via the output device 7 based on the "instruction Guid" of the selected row in FIG. 33(b).

[0104] At this time, since the re-execution value change permission classifications for the parameter IDs of "transmission target" and "retransmission classification" in the flow parameter master 43 shown in FIG. 34(b) are both "1: Permitted", the display control unit 20 displays the input fields for the parameters of "transmission target" and "retransmission classification" shown in FIG. 33(c) in a state where the operator can change the values. Note that since the schedule reconfiguration button 61 has been operated this time, the display control unit 20 displays the name of the program (flow) executed last time in a state where it cannot be changed, and also displays the previous value, which is the parameter used at the previous execution, in a state where it cannot be changed.

[0105] In addition, the display control unit 20 displays the input field for the temporary schedule, which is the input field for the schedule to be reconfigured, the input field for the setting name (temporary setting name) of the temporary schedule, and the input field for the parameters of the program (flow) to be reconfigured.

[0106] The example in Fig. 33(c) is an example of re-executing the program (flow) for "batch sending of training emails". The operator sets the parameter of "recipient" to "all", and the parameter of "resending category" to "resend". Also, in the example of Fig. 33(c), the operator sets the "temporary schedule" to "Server restart at 2:30 am" which is the schedule for restarting the server device at 2:30 am, and sets the "temporary setting name" to "Batch handling of training emails". When the operator re-sets the schedule and parameters in this way, the operator operates the reservation execution button 33.

[0107] Figs. 34(a) to 34(h) show the flow setting master 41, the flow parameter master 43, the flow execution instruction work 12 before schedule re-setting, the flow execution instruction parameter work 50, the flow schedule execution setting master 14 after schedule re-setting, the flow schedule execution setting parameter master 49, the flow execution instruction work 12 after schedule re-setting, and the flow execution instruction parameter work 50. Before the operation of the reservation execution button 33, as shown in Fig. 34(c), the "instruction type" of the flow execution instruction work 12 is "1: waiting in order" or "2: highest priority", and the "status" is "2: error".

[0108] On the contrary, after the operation of the reservation execution button 33, as shown in Fig. 34(g), the memory control unit 25 inputs the above-mentioned "temporary setting name" such as "Server restart at 2:30 am" to the "schedule ID", 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", generates a record with a blank "processing result", and adds it to the flow execution instruction work 12. The memory control unit 25 stores the parameter of "all" for the re-set "recipient" and the parameter of "resend" for the "resending category" in the flow schedule execution setting parameter master 49 and the flow execution instruction parameter work 50 respectively, as shown in Figs. 34(f) and 34(h).

[0109] (Example of re - executing a program (flow) that had an execution error when manually executed previously, in each schedule obtained by dividing the calculation target) Next, an example of selecting a program (flow) that had an execution error when manually executed from the above - listed execution results and executing it in each schedule obtained by dividing the calculation target will be described. In this case, as shown in FIGS. 35(a) and 35(b), the operator displays the list of the above - mentioned execution results, selects the record (detail) of the program (flow) to be re - executed, and operates the schedule re - setting button 61. Thereby, the display control unit 20 displays the re - execution setting (schedule) screen shown in FIG. 35(c) via the output device 7.

[0110] At this time, since the re - execution value change permission categories for the parameter IDs of "employee category" and "target company" in the flow parameter master 43 shown in FIG. 36(b) are both "1: permitted", the display control unit 20 displays the input fields for the parameters of "employee category" and "target company" shown in FIG. 35(c) in a state where the operator can change the values. Note that since the schedule re - setting button 61 has been operated this time, the display control unit 20 displays the name of the program (flow) executed previously in a state where it cannot be changed, and also displays the previous value, which is the parameter used at the previous execution, in a state where it cannot be changed.

[0111] In addition, the display control unit 20 displays the input field for the temporary schedule, which is the input field for the schedule to be re - set, the input field for the setting name (temporary setting name) of the temporary schedule, and the input field for the parameters of the program (flow) to be re - set.

[0112] Here, by adjusting the parameter values to divide the processing range, the affected range can be narrowed to identify the error occurrence location. For example, when checking the error list, assume that most errors occur in the employee classification of part-time or temporary workers. After corresponding to all of these and then re-executing, it takes time and will affect employees who do not have errors. Therefore, in order to divide the calculation target to narrow the affected range, for example, first perform salary calculation for employee classifications other than part-time and temporary workers.

[0113] In this case, assume that time zones with less impact on the workload are, for example, 11:00 am, 16:00 pm, 19:00 pm, etc. Then, for the first time, calculate at 11:00 am today with the "employee classification" set to "regular / contract". That is, as illustrated in FIG. 35(c), the operator sets the parameter of "employee classification" to "regular employees and contract employees (regular / contract)" and the parameter of "target company" to "10". Also, the operator sets the "temporary schedule" to 11:00 am today and specifies the re-execution of the program (flow). The "temporary setting name" is "Handling of monthly salary calculation". When the operator re-sets the schedule and parameters in this way, the operator operates the reservation execution button 33.

[0114] FIGS. 36(a) to 36(h) show the flow setting master 41, the flow parameter master 43, the flow execution instruction work 12 before schedule re-setting, the flow execution instruction parameter work 50, the flow schedule execution setting master 14 after schedule re-setting, the flow schedule execution setting parameter master 49, the flow execution instruction work 12 after schedule re-setting, and the flow execution instruction parameter work 50. Before the operation of the reservation execution button 33, as shown in FIG. 36(c), the "instruction type" of the flow execution instruction work 12 is "1: waiting in line" or "2: highest priority", and the "status" is "2: error".

[0115] On the other hand, after the operation of the reservation execution button 33, as shown in Fig. 36(g), the memory control unit 25 inputs the program name (flow name) such as "Monthly salary calculation" into the "Flow ID", and inputs the above-mentioned "temporary setting name" such as "11:00 today" into the "Schedule ID", sets the "Instruction type" to "0: Schedule", sets the "Scheduled execution date and time" to "2022 / 9 / 1 11:00:00", sets the "Status" to "0: Unprocessed", and generates a record with a blank "Processing result", and adds it to the flow execution instruction work 12.

[0116] At this time, the memory control unit 25 adds the same instruction Guid as the instruction Guid shown in Fig. 32(c) to the record to be added. Thereby, the error source instruction Guid of the record in Fig. 32(e) added and the instruction Guid in Fig. 32(c) can be associated, and the added record can be held. At this time, the memory control unit 25 inherits the error source instruction Guid from the flow schedule execution setting master 14 through the flow execution instruction work 12. Thereby, when performing split execution, the re-execution results can be managed in an associated manner in a 1:N relationship.

[0117] Note that the memory control unit 25 stores the parameters of "Regular / Contract" of the re-set "Employee classification" and the parameter of "10" of the "Target company" in the flow schedule execution setting parameter master 49 and the flow execution instruction parameter work 50 as shown in Figs. 36(f) and 36(h), respectively.

[0118] In this way, when the first reservation setting is made and the reservation execution button 33 is operated, the display control unit 21 redisplay the execution result inquiry screen shown in FIG. 35(b). When the operator operates the schedule re - setting 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). The operator sets the employee category to be calculated as "Part - Time / Part - Time Job" considering the above - mentioned error response time for the second - displayed re - execution setting screen, sets the execution time to 16:00 this afternoon, and operates the reservation execution button 33. As a result, the calculation target can be divided and the salary calculation can be executed according to each schedule. The storage control unit 25 generates a record corresponding to this second schedule and adds it to the flow execution instruction work 12 as described above.

[0119] (Example of manually re - executing a program (flow) that had an execution error when executed in the previous schedule setting) Next, an example of selecting a program (flow) that had an execution error by executing based on a schedule from the above - listed execution results and changing the execution form to manual execution and then executing the program (flow) will be described. In this case, as shown in FIGS. 37(a) and 37(b), the operator displays the above - mentioned list of execution results, selects the record (detail) of the program (flow) to be re - executed, and operates the manual re - execution button 62. When the retry category 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 FIG. 37(c) via the output device 7 based on the "Instruction Guid" of the selected row in FIG. 37(b).

[0120] At this time, since the re-execution value change permission sections for the "processing category" and "associated company" parameter IDs of the flow parameter master 43 shown in FIG. 38(b) are both "0: Denied", the input fields for the parameters of the "processing category" and "associated company" shown in FIG. 37(c) are displayed to the operator in a state where the values cannot be changed. Note that since the schedule reset button 61 has been operated this time, the display control unit 20 displays the name of the program (flow) executed last time in a state where it cannot be changed, and also displays the previous value, which is the parameter used during the previous execution, in a state where it cannot be changed.

[0121] In this case, the display control unit 20 displays, on the re-execution instruction (manual) screen in a state where they cannot be changed, 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 setting name at that time, and the "previous value", which is the value of the previous parameter. Also, the display control unit 20 displays, in the input field of the parameter, a parameter having the same value as the "previous value", which is the value of the previous parameter, in a state where it cannot be changed.

[0122] The example in FIG. 37(c) is an example of re-executing the program (flow) of the "master synchronization flow". The operator displays the parameter of the "processing category" at the same value as that at the previous schedule execution, i.e., "Add / Update", in a state where it cannot be changed, and displays the parameter of the "associated company" at the same value as that at the previous schedule execution, i.e., "10,20", in a state where it cannot be changed. In this way, with the parameters set to the same values as the previous time, the highest priority execution button 31 or the execution button waiting in line 32 is operated.

[0123] Figs. 38(a) to 38(h) show the flow setting master 41, the flow parameter master 43, the flow schedule execution setting master 14, the flow schedule execution setting parameter master 49, the flow execution instruction work 12 before manual re-execution, the flow execution instruction parameter work 50, the flow execution instruction work 12 after manual re-execution, and the flow execution instruction parameter work 50. Before manual re-execution, in the flow execution instruction work 12, as shown in Fig. 38(e), the "instruction type" is "0: schedule" and the "status" is "2: error".

[0124] When the memory control unit 25 is manually re-executed and the operator operates the highest priority execution button 31, the "instruction type" shown in Fig. 38(g) is set to "2: highest priority", and when the operator operates the waiting turn execution button 32, the "instruction type" shown in Fig. 38(g) is set to "1: waiting turn", the "status" is set to "0: unprocessed", the "processing result" is blank, and a record is generated and added to the flow execution instruction work 12.

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

[0126] At this time, since the schedule reset button 61 was operated this time, the display control unit 20 displays the name of the program (flow) executed last time, the original schedule, and the original setting name in a state where they cannot be changed, and also displays the previous value, which is the parameter used when the previous schedule was executed, in a state where it cannot be changed.

[0127] In addition, the display control unit 20 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 classification for the "file name" and "closing date classification", which are parameter IDs. As shown in FIG. 40(b), the re-execution value change permission classification for the "file name" parameter is "1: Permitted", and the re-execution value change permission classification for the "closing date classification" parameter is "0: Denied". Therefore, as shown in FIG. 39(c), the display control unit 20 displays the input field for the "file name" parameter in a state where the operator can change the value, and displays the input field for the "closing date classification" parameter in a state where the operator cannot change the value. When the operator inputs the temporary schedule, the temporary setting name, and the file name, the operator operates the reservation execution button 33.

[0128] FIGS. 40(a) to 40(f) show the flow setting master 41, the flow parameter master 43, the flow schedule execution setting master 14 after schedule reset, the flow schedule execution setting parameter master 49, the flow execution instruction work 12 before schedule reset, and the flow execution instruction parameter work 50. Before the reservation execution by the temporary schedule, as shown in FIG. 40(e), the "instruction type" of the flow execution instruction work 12 is "0: Schedule", and the "status" is "2: Error".

[0129] In contrast, FIGS. 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 schedule reset, and the flow execution instruction parameter work 50. After the operation of the reservation execution button 33, the memory control unit 25 inputs the above-mentioned "temporary setting name" such as "16:20 today" to the "schedule ID" of the flow execution instruction work 12 shown in FIG. 41(c), sets the "instruction type" to "0: schedule", sets the "scheduled execution date and time" to "2022 / 9 / 1 16:20:00", sets the "status" to "0: unprocessed", and generates a record with a blank "processing result", and adds it to the flow execution instruction work 12.

[0130] Note that the memory control unit 25 stores the parameters of the "file name" and "closing date classification" reset as a temporary schedule in the flow schedule execution setting parameter master 49 and the flow execution instruction parameter work 50 as shown in FIGS. 41(b) and 41(d), respectively.

[0131] (Effects of the Embodiment) As is clear from the above description, the execution control device 1 of the embodiment can flexibly select the timing for re-executing a program (flow) that has failed in execution.

[0132] Also, regardless of the type of instruction at the error source, it can be flexibly selected and responded to according to the situation such as the environmental conditions and the convenience of the person in charge.

[0133] Also, by adjusting the parameter values and dividing the processing range, the influence range can be narrowed to identify the error occurrence location.

[0134] Also, by associating re-execution with the execution error log, the details of the execution log of the same instruction can be managed, and it can also be utilized for the consistency of log management and future responses in control.

[0135] Specifically, the following effects can be obtained.

[0136] 1. Even when a manually executed flow process results in an error, there may be a case where a schedule re-execution is desired. In this case, in order to avoid inconvenience to the person in charge or the busy state of the server, manual execution is to be avoided. Also, instead of the timing when the cause of the error has been resolved, a function is required to set the schedule at an arbitrary time zone and re-execute. When performing such a schedule setting for re-execution, there are risks of changing the existing settings and forgetting to delete the temporarily created schedule settings.

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

[0138] 2. When an error occurs when a program is executed based on a schedule, there may be a case where manual re-execution is desired in operations etc. where immediate recovery is required.

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

[0140] 3. When re-executing a program (flow), regarding the reusability of the initial execution conditions, there are cases such as "want to re-use some of the initial execution conditions and re-execute with some changes", "do not permit changes to the initial execution conditions and force re-execution as it is", "want to prevent the case where something that should not be changed is mistakenly changed during retry", etc.

[0141] The execution control device 1 of the embodiment has a function of restoring the initial execution conditions when re-executing the program (flow). The changeable execution conditions and the unchangeable execution conditions at the time of re-execution can be set for each execution condition. Therefore, input mistakes etc. of the execution conditions at the time of re-execution can be prevented.

[0142] 4. For each program (flow), there are programs (flows) that may be rerun and programs (flows) that should not be rerun. That is, for example, operations such as closing processes or system cooperation flows, which require immediate response in case of errors, are programs (flows) that may be rerun. On the other hand, test programs (flows) or complex and heavy processing operation flows may affect existing flows in the operation environment when rerun, so they are programs (flows) that should not be rerun.

[0143] The execution control device 1 of the embodiment enables setting whether to rerun a program (flow) for each program (flow). Therefore, rerun can be controlled according to the type of program (flow) and the like.

[0144] 5. For each user authority, there are programs (flows) that the user wants to execute (or rerun) and programs (flows) that the user does not want to execute. For example, there may be cases where execution authority is given only to the person in charge for operation flows within the scope of business.

[0145] The execution control device 1 of the embodiment enables setting whether to execute a program (flow) for each user. Therefore, security for program (flow) execution can be improved.

[0146] [Contribution to the Sustainable Development Goals (SDGs) led by the United Nations] This embodiment can contribute to improving business efficiency and making appropriate business decisions for enterprises, so it can contribute to Goals 8 and 9 of the SDGs.

[0147] In addition, this embodiment can contribute to reducing waste loss and promoting paperless and digitalization, so it can contribute to Goals 12, 13, and 15 of the SDGs.

[0148] In addition, this embodiment can contribute to strengthening control and governance, so it can contribute to Goal 16 of the SDGs.

[0149] [Other Embodiments] In addition to the above-described embodiments, the present invention may be implemented in various different embodiments within the scope of the technical idea described in the claims.

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

[0151] Also, regarding the processing procedures, control procedures, specific names, information including parameters such as registered data and search conditions for each process, screen examples, and database configurations shown in this specification and the drawings, they can be arbitrarily changed unless otherwise specified.

[0152] Also, regarding the execution control device 1, each of the illustrated components is a functional concept, and it is not necessarily physically configured as shown in the figure.

[0153] For example, regarding the processing functions provided by the execution control device 1, particularly each processing function performed by the control unit 3 and the control unit 3, all or any part of them may be realized by a CPU (Central Processing Unit) and a program interpreted and executed by the CPU, or may be realized as hardware by wired logic. The program is recorded on a non-transitory computer-readable recording medium including 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 for giving commands to the CPU in cooperation with the OS to perform various processes is recorded in a storage unit such as a ROM or HDD. This computer program is executed by being loaded into the RAM and constitutes the control unit 3 in cooperation with the CPU.

[0154] Also, the execution control program of the execution control device 1 may be stored in another server device connected to the execution control device 1 via an arbitrary network, and all or part of it can be downloaded as necessary.

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

[0156] Also, a "program" is a data processing method described in an arbitrary language or description method, and is not limited to a form such as source code or binary code. Note that the "program" is not necessarily limited to being configured singly, and also includes those that are distributed as a plurality of modules or libraries, or those that achieve their functions in cooperation with another program typified by an OS. Regarding the specific configuration, reading procedure, and installation procedure after reading for reading the recording medium in the execution control device 1 shown in the embodiment, well-known configurations and procedures can be used.

[0157] The storage unit 2 is a storage means such as a memory device like a RAM or a ROM, a fixed disk device like a hard disk, a flexible disk, and an optical disk, and stores various programs, tables, databases, and files for web pages used for various processes and website provision.

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

[0159] Furthermore, the specific form of the distribution and integration of the devices is not limited to that shown in the drawings, and all or part of them can be functionally or physically distributed and integrated in arbitrary units according to various additions or according to the function load. That is, the above-described embodiments may be arbitrarily combined and implemented, or the embodiments may be selectively implemented.

Industrial Applicability

[0160] The present invention functions effectively for re-executing a program that performs, for example, background processing.

Explanation of Signs

[0161] 1 Execution control device 2 Storage unit 3 Control unit 4 Communication interface unit 5 Input / output interface unit 6 Input device 7 Output device 11 State management database (state 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 Memory Control Unit 31 Re-priority Execution Button 32 Execution-in-Queue Button 33 Scheduled Execution Button 41 Flow Configuration Master 42 Schedule Master 43 Flow Parameter Master 44 Flow Execution Permission Master 45 Highest-priority Execution Permission Master 46 User Master 47 User Group Master 48 User Group Member Master 49 Flow Schedule Execution Configuration Parameter Master 50 Flow Execution Instruction Parameter Work 53 Flow Execution Log 61 Schedule Reconfiguration Button 62 Manual Re-execution Button

Claims

1. A reservation execution button for instructing re-execution of a program that has encountered an execution error at a desired schedule, a top-priority execution button for manually instructing immediate execution of the program that has encountered the execution error, and a queued execution button for manually setting the execution order of the program that has encountered the execution error to the end of the programs waiting to be executed, and a display control unit that displays them on a display unit; When the reservation execution button is operated, the execution schedule of the program that has encountered the execution error is stored in a schedule execution setting storage unit where the schedules of the programs waiting to be executed are stored. When the top-priority execution button is operated, the pre-execution program information indicating the program before execution is set to the top execution order for the execution order storage unit in which the execution order is stored in the specified execution order for each program. When the queued execution button is operated, a setting control unit that sets the execution order of the program that has encountered the execution error to the end of the execution order stored in the execution order storage unit; 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; An execution control device having the above.

2. The display control unit displays, on the display unit, the execution conditions at the time of execution of the program that has encountered the execution error, together with the reservation execution button, the top-priority execution button, and the queued execution button. When the execution condition is changed, the setting control unit resets the changed execution condition as the execution condition for the program that has encountered the execution error to the program that has encountered the execution error. The execution control unit re-executes the program that has encountered the execution error based on the reset execution condition. The execution control device according to claim 1, characterized by the above.

3. Changeable information indicating whether or not a change is possible is added to the parameters included in the execution conditions. The display control unit changes and displays the display form of the parameters that can be changed and the parameters that cannot be changed based on the changeable information among the parameters. The execution control device according to claim 2, characterized by the above.

4. The program in which the execution error has occurred is added with re-execution permission information indicating whether re-execution is possible. When the re-execution permission information that permits re-execution is added to the program in which the execution error has occurred, the display control unit displays the reservation execution button, the highest priority execution button, and the waiting execution button on the display unit, and enables re-execution of the program in which the execution error has occurred. The execution control device according to claim 3, characterized in that.

5. The program in which the execution error has occurred is added with user authority information indicating a user who permits re-execution of the program in which the execution error has 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 who instructs re-execution of the program in which the execution error has occurred is a user with the user authority for re-execution of the program in which the execution error has occurred. When it is determined that the instruction for re-execution is from a user with the user authority for re-execution of the program in which the execution error has occurred, the program in which the execution error has occurred is re-executed. The execution control device according to claim 4, characterized in that.

6. When the immediate execution of the program in which the execution error has occurred is instructed by the highest priority execution button, the execution control unit refers to the highest priority execution permission storage unit in which the immediate execution user information indicating a user to whom the immediate execution user authority is given is stored, and when it is determined that the user who has instructed the immediate execution of the program in which the execution error has occurred by the highest priority execution button is a user to whom the immediate execution user authority is given, the program in which the execution error has occurred is re-executed. The execution control device according to claim 5, characterized in that.

7. A display control step in which the display control unit displays a reservation execution button for instructing re-execution of a program in which an execution error has occurred at a desired schedule, a highest priority execution button for manually instructing immediate execution of the program in which the execution error has occurred, and a waiting execution button for manually setting the execution order of the program in which the execution error has occurred at the end of the programs waiting for execution on the display unit. When the reservation execution button is operated, the setting control unit causes the schedule of execution of the program in which the execution error has occurred to be stored in the schedule execution setting storage unit in which the schedules of the programs waiting for execution are stored. When the top priority execution button is operated, the setting control unit sets the execution order of the program in which the execution error has occurred to the top execution order with respect to the execution order storage unit in which the pre-execution program information indicating the program before execution is stored in the specified execution order for each of the programs. When the execution in order button is operated, the setting control unit sets the execution order of the program in which the execution error has occurred to the end of the execution order stored in the execution order storage unit. The execution control unit performs execution control of each program according to the schedule of each program stored in the schedule execution setting storage unit, and performs execution control of each program in the execution order stored in the execution order storage unit. An execution control method comprising: **Claim 8** A computer, 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 at a desired schedule, a top priority execution button for manually instructing immediate execution of the program in which the execution error has occurred, and an execution in order button for manually setting the execution order of the program in which the execution error has occurred to the end of the programs waiting for execution. When the reservation execution button is operated, the setting control unit causes the schedule of execution of the program in which the execution error has occurred to be stored in the schedule execution setting storage unit in which the schedules of the programs waiting for execution are stored. When the top priority execution button is operated, the setting control unit sets the execution order of the program in which the execution error has occurred to the top execution order with respect to the execution order storage unit in which the pre-execution program information indicating the program before execution is stored in the specified execution order for each of the programs. When the execution in order button is operated, the setting control unit sets the execution order of the program in which the 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 performs execution control of each program according to the schedule of each program stored in the schedule execution setting storage unit and performs execution control of each program in the execution order stored in the execution order storage unit. An execution control program characterized by:

Images