JP2024007276A - Scenario management apparatus, scenario management program, recording medium, and scenario management method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To allow a user to extract a desired activity from a scenario by simply identifying variables used for the activity or inputting values set for the variables.

SOLUTION: When activities A12-A15 to be extracted from among a plurality of activities A11-A16, A21-A26 are designated, a sub scenario creation unit 32 defines a sub scenario As for collectively executing the activities to be extracted. A variable declared in the activity A11 is determined as an input parameter, the variable being used in the sub scenario As, and the activity A11 being executed before the activities A12-A15 to be extracted in a scenario Sm. A display 243 displays a main scenario screen Dm for receiving an input of a value to be set for an input parameter arg1 of the sub scenario As, which is used in the scenario Sm.

SELECTED DRAWING: Figure 4B

COPYRIGHT: (C)2024,JPO&INPIT

Description

The present invention relates to RPA (Robotic Process Automation) technology that aims to reduce the user's work burden by automating the work that the user previously performed using a computer.

RPA can be used to automate tasks performed by a user by operating an application or the like run by a computer. This RPA automates work by executing a scenario (sometimes referred to as a "flow") that shows a procedure for executing a process by a computer. This scenario is created by combining multiple activities, each representing a process that you want the computer to perform. Furthermore, in RPA using such a scenario, there is a need to edit the scenario as appropriate. On the other hand, Patent Document 1 proposes a technique for editing a scenario by customizing the set values of variables used in the scenario.

Japanese Patent Application Publication No. 2020-113034

Incidentally, in a scenario, activities arranged in the same order may be executed at multiple locations in the scenario or at any location in another scenario. In such a case, it would be convenient for the user who edits the scenario to be able to extract the activities arranged in that order from a certain part of the scenario and reuse them in another part of the scenario. However, if the activity to be extracted uses a variable declared earlier, the user will need to set the variable in another location to make the activity achieve the desired behavior. be. In other words, when extracting an activity, the user needs to understand the variables and input setting values for the variables. However, it has not always been easy for users to understand the variables used in an activity or input settings for the variables.

This invention has been made in view of the above-mentioned problems, and it is an object of the present invention to enable a user to easily grasp the variables used in the activity and input setting values to the variables when extracting a desired activity from a scenario. With the goal.

A scenario management device according to the present invention is a scenario management device for managing a scenario for automating an operation for another application program, which includes a plurality of activities indicating operations, and the scenario management device manages a scenario that includes a plurality of activities indicating operations. A specification reception unit that accepts extraction target specifications that specify activities to be extracted; a batch activity creation unit that defines a batch activity to collectively execute the extraction target activities accepted by the specification reception unit; A parameter determination unit that determines variables used in activities that are declared in activities that are executed before the activity to be extracted in a scenario as input parameters, and input parameters of bulk activities used in scenarios. and a scenario display section that displays a screen that accepts input of setting values for.

A scenario management program according to the present invention causes a computer to function as the scenario management device described above.

A recording medium according to the present invention records the scenario management program described above so as to be readable by a computer.

A scenario management method according to the present invention is a scenario for automating operations on other application programs, and is a scenario management method for managing a scenario including a plurality of activities indicating operations, wherein A process in which the specification reception unit receives an extraction target specification that specifies activities to be extracted, a process in which a batch activity is defined to collectively execute the extraction target activities accepted by the specification reception unit, and a batch activity. The process of determining variables used in the scenario that are declared in an activity that is executed before the activity to be extracted as an input parameter, and the setting values for the input parameters of the bulk activity used in the scenario. displaying a screen that accepts input of the information.

In the present invention (scenario management device, scenario management program, recording medium, and scenario management method) configured as described above, an extraction target designation that specifies an activity to be extracted from among a plurality of activities is accepted by the designation reception unit. Then, a batch activity is defined to collectively execute the activities to be extracted. At this time, a variable used in the batch activity and declared in an activity executed before the extraction target activity in the scenario is determined as an input parameter. Then, a screen is displayed that accepts input of setting values for the input parameters of the batch activity used in the scenario. Therefore, the user can grasp the input parameters (variables) from the displayed screen and can further input setting values for the input parameters (variables). In this way, when the user extracts a desired activity from a scenario, it becomes possible for the user to easily grasp the variables used in the activity and input set values to the variables.

As described above, according to the present invention, when a user extracts a desired activity from a scenario, it becomes possible for the user to easily grasp the variables used in the activity and input setting values for the variables. ing.

1 is a block diagram showing an example of a scenario management system including a scenario management device according to the present invention. FIG. 3 is a block diagram showing an example of each functional unit configured in the calculation unit to create a sub-scenario. 10 is a flowchart showing an example of a method for creating a sub-scenario. FIG. 4 is a diagram showing an example of a process executed based on the flowchart of FIG. 3; FIG. 4 is a diagram showing an example of a process executed based on the flowchart of FIG. 3; FIG. 4 is a diagram showing an example of a process executed based on the flowchart of FIG. 3; FIG. 4 is a diagram showing an example of a process executed based on the flowchart of FIG. 3; FIG. 4 is a diagram showing an example of a process executed based on the flowchart of FIG. 3; 10 is a flowchart showing an example of editing a sub-scenario name. FIG. 6 is a diagram showing an example of a process executed based on the flowchart of FIG. 5; FIG. 6 is a diagram showing an example of a process executed based on the flowchart of FIG. 5; 10 is a flowchart showing an example of adding input parameters. FIG. 8 is a diagram showing an example of a process executed based on the flowchart of FIG. 7; FIG. 8 is a diagram showing an example of a process executed based on the flowchart of FIG. 7; FIG. 8 is a diagram showing an example of a process executed based on the flowchart of FIG. 7; FIG. 8 is a diagram showing an example of a process executed based on the flowchart of FIG. 7; FIG. 8 is a diagram showing an example of a process executed based on the flowchart of FIG. 7; FIG. 8 is a diagram showing an example of a process executed based on the flowchart of FIG. 7; A flowchart showing an example of adding an output parameter. 11 is a diagram illustrating an example of processing executed based on the flowchart of FIG. 10. FIG. 11 is a diagram illustrating an example of processing executed based on the flowchart of FIG. 10. FIG. 11 is a diagram illustrating an example of processing executed based on the flowchart of FIG. 10. FIG. 11 is a diagram illustrating an example of processing executed based on the flowchart of FIG. 10. FIG. 11 is a diagram illustrating an example of processing executed based on the flowchart of FIG. 10. FIG. 11 is a diagram illustrating an example of processing executed based on the flowchart of FIG. 10. FIG. 5 is a flowchart illustrating an example of output parameter type management. FIG. 13 is a diagram showing an example of a process executed based on the flowchart of FIG. 12; FIG. 3 is a diagram illustrating a configuration for switching screens to be displayed between a main scenario screen and a sub-scenario definition screen. FIG. 3 is a diagram illustrating a configuration for switching screens to be displayed between a main scenario screen and a sub-scenario definition screen. The figure which shows an example of the assist operation of a user input.

FIG. 1 is a block diagram showing an example of a scenario management system including a scenario management device according to the present invention. This scenario management system 1 includes a server 11 and a terminal device 2 that functions as a client of the server 11. The server 11 is a computer, and includes a storage section 111 configured with an HDD (Hard Disk Drive) or an SSD (Solid State Drive), and the scenario management program 12 is stored in the storage section 111.

The terminal device 2 is a computer for managing scenarios used in RPA. This terminal device 2 includes a calculation section 21, a memory section 22, a storage section 23, a UI (User Interface) 24, a communication section 25, and a bus 26. Transmission and reception of signals between 25 is performed via bus 26.

The calculation unit 21 is a processor such as a CPU (Central Processing Unit), and controls the memory unit 22, the storage unit 23, the UI 24, and the communication unit 25. The memory unit 22 includes a main memory, a cache memory, etc., and volatilely stores data based on instructions from the calculation unit 21, and the calculation unit 21 executes calculations using the data read from the memory unit 22. .

The storage unit 23 includes an HDD, an SSD, and the like, and stores data in a nonvolatile manner. The UI 24 includes input devices such as a keyboard 241 and a mouse 242, and output devices such as a display 243. Therefore, the user can perform input operations on the terminal device 2 by operating the keyboard 241 and mouse 242, and can check various data stored in the memory section 22 and storage section 23 by checking the display 243. . Note that it is not necessary to configure the input device and the output device separately, and they may be configured integrally using a touch panel display. Further, the communication unit 25 executes communication with the server 11. The communication unit 25 downloads the scenario management program 12 from the server 11, and the storage unit 23 stores the scenario management program 12. Further, when the calculation unit 21 executes the scenario management program 12, each functional unit shown in FIG. 2 for executing scenario management is configured in the calculation unit 21.

Incidentally, the manner in which the scenario management program 12 is provided to the terminal device 2 is not limited to downloading from the server 11. Therefore, it may be provided by other recording media such as an optical disc such as a DVD (Digital Versatile Disc) or a USB (Universal Serial Bus) memory. The terminal device 2 can store the scenario management program 12 read from these recording media in the storage unit 23.

Note that in this embodiment, the scenario used in RPA that is managed by the terminal device 2 refers to the operations that the user of the terminal device 2 or another person performs on application programs other than the scenario management program 12. This is a scenario for automation. The operation includes an operation of acquiring a value from an application program other than the scenario management program 12, an operation of processing the value, and an operation of inputting the value to an application program other than the scenario management program 12. The operation of acquiring values from an application program other than the scenario management program 12 includes a human operating the application program other than the scenario management program 12 in order to output reference information from an output device such as the display 243. In addition, operations for inputting values into application programs other than the scenario management program 12 are performed by humans using input devices such as the keyboard 241 and mouse 242 so that values are input into application programs other than the scenario management program 12. including doing. Examples include directly inputting a value using the keyboard 241, and selecting a value to be input from options displayed by an application program using an input device.

As described below, a scenario is composed of a plurality of activities, and each activity defines an operation to be performed by a computer. Examples of activities include:
・An activity that shows the acquisition of a table written in CSV (Comma-Separated Values) format, etc. ・An activity that narrows down the values in the table based on predetermined conditions ・An activity that extracts values from the table Various specific examples include activities that output to a web page, email address, etc., activities that access a predetermined web page, and activities that acquire images and text from a web page. By arranging the activities in a desired order using the UI 24, the user can create a scenario in which the activities are executed in that order. In particular, in this embodiment, it is possible to create a sub-scenario for collectively executing some of the activities that make up the scenario.

FIG. 2 is a block diagram showing an example of each functional unit configured in the calculation unit to create a sub-scenario. As described above, the calculation unit 21, the memory unit 22, and the UI 24 communicate with each other via the bus 26, but the bus 26 is omitted in FIG. 2. A scenario Sm is stored in the memory unit 22, and a sub-scenario (specifically, sub-scenario definition information Ss that defines the sub-scenario) is created by extracting activities from the scenario Sm. In the calculation unit 21, each functional unit is configured by the execution of the scenario management program 12 by the calculation unit 21. As shown in FIG. 2, the calculation unit 21 includes a specification reception unit 31, a subscenario creation unit 32, a subscenario definition unit 33, and a subscenario management unit 34 as functional units.

The designation receiving unit 31 receives a user's input to the UI 24 that designates an activity to be extracted as a sub-scenario. Further, the specification receiving unit 31 receives various inputs made by the user using the UI 24 with respect to the created sub-scenario. The sub-scenario creation unit 32 creates sub-scenario definition information Ss that defines a sub-scenario based on the designation received by the designation reception unit 31, and stores it in the memory unit 22. Further, the sub-scenario creation unit 32 includes a parameter determining unit 321 that determines parameters constituting the sub-scenario definition information Ss. The sub-scenario definition unit 33 manages the created sub-scenario definition information Ss. The sub-scenario management unit 34 manages the relationship between a sub-scenario defined by the sub-scenario definition information Ss and a scenario that uses the sub-scenario. Further, the sub-scenario management unit 34 includes a sub-scenario development unit 341 that develops the sub-scenario defined by the sub-scenario definition information Ss into activities that constitute the sub-scenario.

FIG. 3 is a flowchart showing an example of a sub-scenario creation method, and FIGS. 4A to 4E are diagrams showing an example of processing executed based on the flowchart of FIG. 3. The flowchart in FIG. 3 starts with the main scenario screen Dm shown in FIG. 4A being displayed on the display 243.

As shown in the main scenario screen Dm, the scenario Sm is composed of a plurality of activities A11 to A16 and A21 to A26 arranged in the order of execution. On the main scenario screen Dm, each activity is displayed as a combination of activity type information C indicating the type of the activity and definition information D defining details of the activity. The user edits the activity by specifying the value E of the definition information D.

Activity A11 is an activity that creates (in other words, declares) a character string type variable, and by executing this activity, variable V11 is created according to definition information D11. The definition information D11 includes definition information D111 that specifies the name of the variable V11 to be created, and definition information D112 that specifies the value to be acquired as the actual value of the variable V11. Specifically, in activity A11, the character string "overtime time file" is input as value E111 specified in definition information D111. Therefore, a variable V11 named "overtime time file" is created. In addition, in activity A11, a character string that is a file path is input as value E112 specified in definition information D112, and by executing this activity, the path of the file is changed to variable V11 (overtime file). is obtained as the actual value of In this example, the file specified by the path is a file from a specified spreadsheet software, but it may be a file from another spreadsheet software or a file handled by software other than the spreadsheet software. . In this example, a character string indicating the path of "overtime hours file_Sato", which is a spreadsheet file indicating information regarding overtime hours of "Mr. Sato", is acquired as the actual value of variable V11. Note that in the definition information D11, the value E112, which is an entity value, is specified by being directly input, but the value E112 is not limited to an entity value, and the method of specification is not limited to direct input. A declared variable may be specified as the value E112, or the specification of the value E112 may be accepted by displaying options and allowing the user to select an option. The same applies to other activities.

Activity A12 is an activity that opens a spreadsheet file with a path specified by definition information D12. Definition information D12 specifies the path of the spreadsheet file. In this example, "overtime time file", which is the name of variable V11 declared in activity A11, is input as value E12 specified in definition information D12, so the path is set to variable V11 defined in activity A11. It is specified. By executing activity A11, a character string with value E111, that is, a character string indicating the path of "overtime time file_Sato", is obtained as the actual value of variable V11. Therefore, by executing activity A12, "overtime time file_Sato" is opened.

Activity A13 is an activity that activates a specific sheet of the spreadsheet file that is active at the time the activity is executed, according to definition information D13. The definition information D13 includes definition information D131 that specifies a method for specifying a sheet to be made active, and definition information D132 that specifies a key for specifying the sheet. In this example, since activity A12 is executed immediately before activity A13, the "overtime time file_Sato" opened by executing activity A12 is the active spreadsheet file. Furthermore, in this example, since "sheet name" is selected as the value E131 specified in the definition information D131, the sheet is identified by the sheet name. Furthermore, in this example, since the character string "Overtime Hours Calculation" is input as the value E132 specified in the definition information D132, the sheet with the sheet name "Overtime Hours Calculation" is specified as the sheet to be activated. Ru. That is, in activity A13, the "overtime time calculation" sheet included in "overtime time file_Sato" opened in activity A12 is activated.

Activity A14 is an activity that declares variable V14 according to definition information D14, and activity A15 is an activity that declares variable V15 according to definition information D15. This is an activity that retrieves values from the active sheet. In this example, activities A14 and A15 are activities that acquire the value of a specific cell of the active sheet as an actual value, and the cell is specified by definition information D14 and D15. In this example, since the "overtime time calculation" sheet is active by activity A13, the value of the cell of the sheet is acquired as the actual value. The definition information D14 includes definition information D141 that specifies the name of the variable V14 to be created, definition information D142 that specifies the method for specifying the cell, and definition information D143 that specifies the key for specifying the cell. . In activity A14, since the character string "A.D." is input as the value E141 specified in the definition information D141, the variable name of the declared variable V14 is designated as "A.D.". Further, as the value E142 specified in the definition information D142, "A1 format specification" indicating a method of specifying cells by columns indicated by alphabets and rows indicated by numbers is selected, and the value specified in definition information D143 is selected. Since the character string "C10" is input as E143, the cell C10 located in column C and row 10 of the "overtime time calculation" sheet is specified as a specific cell. When the activity A14 is executed, a variable V14 whose name is "Western calendar" is declared, and the value input in the cell C10 of the "overtime calculation" sheet is input into the variable V14 as an actual value. In activity A15 as well, the active sheet is the "overtime calculation sheet", and like definition information D14, definition information D15 includes definition information D151, D152, and D153. In activity A15, the variable name of declared variable V15 is specified as "Month" as value E151 specified in definition information D151. In addition, since "A1 format specification" is selected as the value E152 specified in the definition information D151, and the character string "B7" is input as the value E153 specified in the definition information D153, "Overtime Cell B7 located in column B and row 7 of the "Time Calculation" sheet is specified. When activity A15 is executed, a variable V15 named "month" is declared, and the value input in cell B7 of the "overtime calculation" sheet is input into variable V15 as an actual value.

Activity A16 is an activity that sends an email having a body of a specific character string to a specific address according to definition information D16. The definition information D16 includes definition information D161 that specifies the destination of the email, and definition information D162 that specifies the text. In this example, since a character string including Mr. Sato's address is input as the value E161 specified in the definition information D161, an e-mail is sent to "Mr. Sato." In addition, in this example, the character string, the variable "Year" (variable V14), and the variable "Month" (variable V15) are input as the value E162 specified in the definition information D162, so the entity A character string that is a combination of a character string input as a value and a character string acquired as the actual value of the variable "Year" and the variable "Month" is specified as the body of the email. That is, when activity A14 acquires "2022" as the actual value of the variable "Year" (V14), and activity A15 acquires "5" as the actual value of the variable "Month" (V15), activity A16 acquires When executed, an email containing a string such as ``Overtime hours in May 2022 will be below the upper limit'' will be sent to Mr. Sato's address.

Activity A21 is an activity similar to activity A11. In this example, instead of the variable "overtime time file", a variable V21 named "overtime time file (2)" is declared, and its actual value is a spreadsheet that shows information about the overtime hours of "Mr. Suzuki". The definition information D21 specifies that a character string indicating the path of the file "overtime time file_Suzuki" is input to the variable V21.

Activity A22 is an activity similar to activity A12. In this example, in the definition information D12, the path for specifying the file to be opened is specified by the variable V21 defined in the activity A21, so the execution of the activity A22 opens the "overtime hours file_Suzuki".

Activity A23 is an activity similar to activity A13. In this example, activity A22 is executed immediately before activity A23, so the target file is different, but the sheet is specified like activity A13, so it is included in "overtime file_Suzuki" like activity A13. The "overtime calculation" sheet is activated.

Activity A24 and activity A25 are activities similar to activity A14. As definition information D24 of activity A24, similarly to activity A24, a value E241 for specifying the name of the variable V24, a value E242 for specifying the cell in which the value to be acquired as the actual value of the variable V24 is input, and a value Since E243 is input, the same execution result as activity A14 is obtained.

Specifically, in activity A24, a variable V24 whose name is "Year (2)" is declared, and the value of cell C10 of the sheet activated in activity A23 is obtained as the actual value of variable V24. Similarly, activity A25 declares a variable V25 named "Month (2)" based on values E251, E252, and E253 specified in definition information D25, and sets the actual value of variable V25 to the value of cell B7. is input.

Activity A26 is an activity similar to activity A16. Similar to activity A16, the character string of the text is specified by the value specified in definition information D26, and Mr. Suzuki's address is specified as the specific address. Therefore, similar to activity A16, when the actual value of the variable "year (2)" (V14) is 2022 and the variable "month (2)" (V15) is 5, when activity A26 is executed, the same result as activity A16 is generated. An email with the body text is sent to Mr. Suzuki's address.

In the scenario Sm shown above, similar activities are arranged in the same order in order to send predetermined emails to "Mr. Sato" and "Mr. Suzuki." On the other hand, according to the flowchart in FIG. 3, the user creates a sub-scenario that executes desired activities all at once from a scenario for sending a predetermined email to "Mr. Sato," for example, and can be duplicated. The duplicated sub-scenario is used to edit the activities included in the scenario Sm, and to edit the scenario Sm into a scenario that also sends a predetermined email to "Mr. Takahashi."

In step S101 of FIG. 3, the designation reception unit 31 determines whether some activities are designated as extraction targets from among the plurality of activities A11 to A16 and A21 to A26 constituting the scenario Sm, based on the user's operation on the UI 24. Judgment based on For example, as shown in FIG. 4B, the user selects some of the activities A12 to A15 and selects the option M11 "Extract to sub-scenario" from the menu M1 that is opened by a predetermined operation such as right-clicking. Activities A12 to A15 can be specified as extraction targets (extraction target designation). Displayed as the menu M1 are options for editing the selected activity, and an option M12 for setting the specified activity as a pause activity during scenario execution: ``Pause at this line during execution''.

When the specification receiving unit 31 receives the specification of the extraction target (“YES” in step S101), the sub-scenario creation unit 32 extracts the activities A12 to A15 specified as the extraction target from the scenario Sm (step S102). .

In step S103, the parameter determining unit 321 of the sub-scenario creating unit 32 determines input parameters based on the activities A12 to A15 to be extracted. Specifically, the parameter determination unit 321 determines the following input parameter conditions: - A variable used by the extraction target activity - A variable declared by an activity executed before the extraction target activity in the scenario A variable that satisfies the condition is determined as an input parameter. In this example, activities A12 to A15 are the activities to be extracted, so the activity that is executed before the activity to be extracted is activity A11, and in activity A11, the variable V11 whose name is "overtime time file" is is declared. Further, the variable V11 is used as the value E12 specified in the definition information D12 in the activity A12. Therefore, variable V11 satisfies the input parameter condition. Therefore, in step S103, variable V11 is determined as the input parameter.

In step S104, the parameter determining unit 321 determines output parameters based on the activities A12 to A15 to be extracted. Specifically, the parameter determination unit 321 satisfies the following output parameter conditions: - A variable whose actual value is obtained by executing the activity to be extracted - A variable used in an activity executed after the activity in question in the scenario A variable that satisfies the condition is determined as an output parameter. In this example, activities A12 to A15 are the activities to be extracted, and in activity A14, the actual value of variable 14 named "Year" is the actual value of variable 15, and in activity A15, the actual value of variable 15 named "Month" is , respectively. In addition, activities executed after the extraction target activity are activities A16, A21 to A26, and variable V14 (year) and variable V15 (month) are both equal to the value E162 specified in definition information D16 in activity A16. used as part of Therefore, each of the variable V14 (year) and the variable V15 (month) satisfies the output parameter condition. Therefore, in step S104, each of variable V14 (year) and variable V15 (month) is determined as an output parameter.

In this example, there are two variables, V14 and V15, that satisfy the output parameter condition. On the other hand, the parameter determining unit 321 determines each of the variables V14 (year) and V15 (month) as individual output parameters. In particular, in this example, variable V14 (variable "Year") and variable V15 (variable "Month") are all variables that satisfy the output parameter conditions when activities A12 to A15 are to be extracted. When the number of all variables satisfying the output parameter condition is 3 or more, all variables may be determined as output parameters, or at least one of them may be determined as an output parameter.

In step S105, the sub-scenario creation unit 32 adds the end activity Af after the extraction target activities A12 to A15. This end activity Af is an activity that returns as a result an actual value obtained as a variable determined as an output parameter, that is, outputs the actual value of the output parameter. In this example, variable V14 (year) and variable 15 (month) are determined as output parameters, so activity Af has the actual value obtained as variable V14 (year) and variable 15 (month). This is an activity that outputs the actual value. When the sub-scenario created in this way is executed, activities A12 to A15 and Af included in the sub-scenario are executed in this order, and the actual values of the output parameters variable V14 (year) and variable V15 (month) are is output as the result of sub-scenario As.

In this way, the sub-scenario definition information Ss that defines a sub-scenario that returns an output parameter in response to an input parameter is created by the sub-scenario creation unit 32. This sub-scenario definition information Ss includes at least activities A12 to A15, Af, input parameters IP, output parameters OP, and sub-scenario name NSs that constitute the sub-scenario. Note that unless otherwise specified, the sub-scenario name NSs is set to "new sub-scenario". The sub-scenario definition information Ss created in this way is stored in the memory section 22 by the sub-scenario creation section 32 (step S106). "New sub-scenario" as the sub-scenario name NSs when the user does not specify it is just an example. For example, a name combined with a number such as "sub-scenario 1" is set, and a certain sub-scenario is set. If there is already a sub-scenario with the same name set, a name with the corresponding number incremented may be set, such as "Sub-scenario 2".

In step S107, the sub-scenario management unit 34 replaces the activities A12 to A15 designated as extraction targets with the sub-scenario As in the scenario Sm (FIG. 4C). In the scenario Sm, the icon indicating the sub-scenario As indicates the name NSs of the sub-scenario As, the output parameter OP, and the input parameter IP. Note that, as described later, sub-scenarios As can be duplicated on the main scenario screen Dm, so in FIG. The scenario As is illustrated as a sub-scenario As1, and the input parameter IP is illustrated as an input parameter IP1. Furthermore, in this embodiment, since there are two output parameters for the sub-scenario As1, they are illustrated as output parameters OP1 and OP2, respectively.

The name of the input parameter IP1 is "arg1", and in the main scenario screen Dm displayed in step S107, the user operates the UI 24 to display definition information indicating the value EIP1 to be treated as the input parameter "arg1". DIP1 can be edited. In this embodiment, the variable "overtime time file" is set as an input parameter in step S103. That is, it is set that the value acquired as the actual value of the variable V11 named "overtime time file" is treated as the actual value input to the input parameter of the sub-scenario As. Therefore, as shown in FIG. 4C, a variable V11 named "overtime time file" is input as the value EIP1 specified in the definition information DIP1 specifying the input parameter IP1 on the main scenario screen Dm. Note that in this embodiment, since a variable is specified as the value EIP1, the value acquired as the entity value of the specified variable is treated as the input parameter IP1, but an entity value may be specified as the value EIP1. When an entity value is specified as the value EIP1, the entity value is treated as the input parameter IP1. Further, in this embodiment, a combination of a character string and a number "arg" is used as the name of the input parameter, but other values may be used as the name of the input parameter IP1. For example, the name of the variable determined as the input parameter may be used as the name of the input parameter IP1. In this case, the icon indicating the sub-scenario As in FIG. 4C displays "overtime time file=overtime time file". The name of a variable is set so that the user can easily understand the contents of the variable, so by using this name as the name of the input parameter, the user can easily understand the value to be set as the input parameter. It becomes easier.

Further, when the user inputs a definition display instruction to the UI 24, the sub-scenario management unit 34 causes the display 243 to display a sub-scenario definition screen Ds (FIG. 4D) showing sub-scenario definition information Ss that defines the sub-scenario As. Note that the definition display instruction can be executed, for example, by selecting "Move to sub-scenario definition" from the menu that opens when the settings button of the icon indicating sub-scenario As is selected in FIG. 4C. Note that the definition display instruction may be executed by selecting "Move to sub-scenario definition" from a menu opened by right-clicking while selecting the icon representing sub-scenario As.

As shown in FIG. 4D, the sub-scenario definition information Ss indicates the activities A12 to A15 to be extracted and the ending activity Af following the activities A12 to A15. Further, the sub-scenario definition information Ss has header information H. This header information H is information regarding the name of the sub-scenario, input parameters, and output parameters. As described above, when creating the sub-scenario definition information Ss, the name NSs of the sub-scenario becomes "new sub-scenario". Furthermore, the type of each output parameter OP1 and OP2 (in this example, both types are "numeric"), the name of input parameter IP1 (in this example, "overtime file"), and the type of input parameter IP1. (in this example, "character string") is indicated. Although the names of the output parameters OP1 and OP2 are not clearly specified in the header information H illustrated in FIG. It can be confirmed that the name is

The user can edit the value to be output as the output parameter OP on the sub-scenario definition screen Ds displayed on the display 243. In this embodiment, since the variable "A.D." is set as the output parameter OP2 of the sub-scenario As, by editing the definition information D14 of the activity A14 in which the variable "A.D." is declared, the value to be output as the output parameter OP2 can be set. is edited. Specifically, in the sub-scenario definition screen Ds shown in FIG. , sets the value of the cell to the value to be output as the output parameter OP2 of the sub-scenario As. According to this, the value acquired as the entity value of variable V14 (AD) is edited in activity A14, and the value acquired as the entity value of variable V14 (AD) is the value to be output as an output parameter in subscenario As. , it can be said that the value to be output as an output parameter is edited. Similarly, when text indicating another cell is input to the definition information D153 in which the value E153 of "B7" of the icon indicating activity A15 is input on the sub-scenario definition screen Ds, the sub-scenario definition unit 33 The value of the cell is set to the value to be output as the output parameter OP1 of sub-scenario As.

The user can edit the scenario Sm using the sub-scenario As created in this way. FIG. 4E shows the main scenario screen Dm of the scenario Sm edited using the created sub-scenario As. More specifically, activities A22 to A25 shown in FIG. 4C are deleted from the main scenario screen Dm in FIG. 4C, subscenario As2 is placed in their place, and input parameter IP2 (input parameter "Arg1") of subscenario As2 is A state is shown in which a variable V22 named overtime time file (2) is set as the value EIP2 specified in the definition information DIP2. When the user performs input to the UI 24 to delete, arrange, or change the definition information of an activity, the sub-scenario management unit 34 edits the scenario Sm in accordance with the input. In the scenario Sm of FIG. 4E, sub-scenario As1 performs the same operations as activities A12 to A15, and sub-scenario As2 performs the same operations as activities A22 to A25. Note that in this embodiment, the sub-scenario As is used for editing a plurality of activities included in the scenario Sm that sends a predetermined email to "Mr. Sato" and "Mr. Suzuki." It may be used to edit a scenario in which a predetermined email similar to that sent to "Mr. Sato" is sent to "Mr. Takahashi." Furthermore, in this embodiment, "Month" and "Year" are displayed as the names of the output parameters OP3 and OP4 in the sub-scenario As2, but the names of the output parameters OP are automatically changed when the sub-scenario is duplicated. It's okay. For example, to distinguish from the output parameters OP1 and OP2 in the sub-scenario As1, the names may be changed to "Month (1)" and "Year (1)." As in this embodiment, sub-scenario As is duplicated in order to perform similar processing at another position in scenario Sm, or to perform similar processing by inputting a different input parameter IP. Therefore, the value obtained as the actual value of the output parameter OP may be different between the sub-scenario As1 and the replicated sub-scenario As2. If the name of the output parameter OP is automatically changed when subscenario As is duplicated, output parameters that obtain different values as actual values can be easily treated as different output parameters, and the user can easily manage the scenario. be able to. Furthermore, in this embodiment, editing is performed to place subscenario As in place of activities A22 to A25 shown in FIG. 4C, but activities A22 to A25 are specified as extraction targets, and subscenarios As may be created. In this case, the created sub-scenario As is treated as a different sub-scenario from the sub-scenario As created with the activities A12 to A15 specified, and therefore it is preferable that a different sub-scenario name is given.

Incidentally, the name of the sub-scenario As created as described above can be edited as appropriate according to the user's input to the UI 24. FIG. 5 is a flowchart showing an example of sub-scenario name editing, and FIGS. 6A and 6B are diagrams showing an example of processing executed based on the flowchart of FIG. 5.

In step S201 of FIG. 5, the specification receiving unit 31 determines whether the sub-scenario name NSs indicated by the header information H of the sub-scenario definition screen Ds has been edited, based on the user's operation on the UI 24. When the specification reception unit 31 receives that the name NSs of the sub-scenario As has been changed from “new sub-scenario” (FIG. 4D) to “obtain overtime hours” (“YES” in step S201), the sub-scenario definition unit 33 changes the name NSs of the sub-scenario As from "new sub-scenario" to "obtain overtime hours" in the sub-scenario definition information Ss (step S202). FIG. 6A shows the sub-scenario definition screen Ds with the name NSs changed from "new sub-scenario" to "obtain overtime hours" from FIG. 4D. Further, in step S203, the sub-scenario management unit 34 changes the name of the sub-scenario As in the icon indicating the sub-scenario As to "obtain overtime hours" in the scenario Sm that calls the sub-scenario As. FIG. 6B shows a state in which the sub-scenario management unit 34 changes the name NSs indicating the sub-scenario As to "obtain overtime hours" in the scenario Sm. In this way, the name change of the sub-scenario As on the sub-scenario definition screen Ds is reflected on the main scenario screen Dm that displays the scenario Sm. Note that in this embodiment, since the scenario Sm calls the sub-scenario As, the name change is reflected on the main scenario screen Dm that displays the scenario Sm, but it only needs to be reflected on the part that calls the sub-scenario As. For example, when another sub-scenario calls sub-scenario As, the name change of sub-scenario As is reflected on the screen displaying the sub-scenario that calls sub-scenario As.

Note that the relationship between the sub-scenario As and the caller of the sub-scenario As in the scenario Sm can be determined based on the result of compiling the scenario Sm. That is, each time the user performs some kind of editing on the scenario Sm, the calculation unit 21 compiles the scenario Sm. On the other hand, the relationship between the sub-scenario As defined by the sub-scenario definition information Ss and the sub-scenario As called by the scenario Sm can be understood by referring to the compilation results. This is similar to the way in which the relationship between classes and instances can be understood from the compilation results in object-oriented programming languages.

In the embodiment described above, when the extraction target designation that designates the activities A12 to A15 to be extracted from among the plurality of activities A11 to A16 and A21 to A26 is received by the designation reception unit 31 (step S101), A sub-scenario As (batch activity) for collectively executing activities to be extracted is defined by the sub-scenario creation unit 32 (steps S102 to S105). At this time, variables used in sub-scenario As (that is, activities A12 to A15 to be extracted) and declared in activity A11 that is executed before activities A12 to A15 to be extracted in scenario Sm are: The input parameter IP is determined (step S103). Then, the main scenario screen Dm (FIG. 4C) that accepts the input of the setting value (variable V11 named overtime file) for the input parameter IP (input parameter "arg1") of the sub-scenario As used in the scenario Sm is displayed. 243. Therefore, the user can understand the input parameters of the sub-scenario As from the displayed main scenario screen Dm, and also set values for the input parameters (variable V11 (overtime time file), variable V21 (overtime time file (2)) etc.) can be specified. In this way, when the user extracts the desired activities A12 to A15 from the scenario Sm, it becomes possible for the user to easily grasp the input parameters used in the activities A12 to A15 and specify the setting values for the input parameters. .

Further, the sub-scenario As outputs the actual value of the output parameter, and the activity executed after the sub-scenario As in the scenario Sm uses the actual value of the output parameter output from the sub-scenario As. On the other hand, the parameter determining unit 321 is a variable whose actual value is obtained by executing the activities A12 to A15 to be extracted, and which is an activity executed after the activities A12 to A15 to be extracted in the scenario Sm. Variable V14 (year) and variable V15 (month) used in A16 are determined as output parameters (step S104). In this configuration, the output parameters of the sub-scenario As, which is the result of executing the sub-scenario As, are automatically determined, thereby reducing the burden on the user. Note that the variable determined as an output parameter in step S104 is output by activity Af so that the actual value of the variable is output to an activity executed after sub-scenario As as the execution result of sub-scenario As. set to the value.

Further, the parameter determining unit 321 determines the type of the output parameter to be the type of the actual value of the variable determined as the output parameter (step S104). In this configuration, the types of the output parameters OP1 and OP2 (year, month and year) are automatically determined, thereby reducing the burden on the user.

Further, the parameter determining unit 321 is a variable whose actual value is obtained by executing the activities A12 to A15 to be extracted, and is used in an activity executed after the activities A12 to A15 to be extracted in the scenario Sm. When there are two variables V14 and V15 (first and second variables) such as variable V14 (year) and variable V15 (month), each of variables V14 and V15 is determined as an output parameter (first first and second output parameters). Therefore, when the sub-scenario As is executed, the sub-scenario As outputs the actual value of the variable V14 (year) and the actual value of the variable V15 (month). On the other hand, the display 243 (scenario display section) displays a sub-scenario definition screen Ds that displays the two output parameters OP1 and OP2 independently of each other and accepts editing of each. In such a configuration, the user grasps the two output parameters OP1 and OP2 (year, year) that are output when the sub-scenario As is executed, and edits these output parameters OP1, OP2 (year, year). You can easily do the work you want to do. Here, the work of editing the output parameters OP1 and OP2 refers to, for example, the work of changing the setting values for the output parameters OP1 and OP2. Note that in this embodiment, a plurality of output parameters OP1 and OP2 can be set for the sub-scenario As. Compared to the case where only one output parameter can be set for a sub-scenario, the user can understand multiple output parameters as values obtained based on the same input parameter. In particular, in this embodiment, as described above, even if the number of values to be output is two or more, they are set as the output parameters OP1 and OP2, making it easy for the user to grasp the outline of the sub-scenario As.

Further, the sub-scenario management unit 34 creates a sub-scenario in a replication range (existence range of activities A22-A25) that is different from the existence range of activities A12 to A15 to be extracted in scenario Sm, that is, between activity A11 and activity A16. A copy of the scenario As is executed in response to an input to the UI 24 (designation reception unit) and displayed on the display 243 of the UI 24 (FIG. 4E). With this configuration, the sub-scenario As can be used in multiple ranges in the scenario Sm, which is convenient for the user who edits the scenario.

By the way, input parameters can be added to the sub-scenario As extracted as described above. FIG. 7 is a flowchart showing an example of adding an input parameter, and FIGS. 8A to 8C and FIGS. 9A to 9C are diagrams showing an example of processing executed based on the flowchart of FIG. 7.

In step S301 in FIG. 7, the specification reception unit 31 determines whether an addition target to the input parameters has been selected on the sub-scenario definition screen Ds based on the user's operation on the UI 24. The user can select an addition target by clicking on the addition target ("YES" in step S301). FIG. 8A shows a state in which the specification reception unit 31 has determined that the value E153 "B7" specified in the definition information D153 of the activity A15 has been selected, and the menu M3 for accepting the specification in step S302 is displayed. . When the user selects the option M31 "Add to input parameter" from the options displayed on the menu M3 with the value E153 selected as the addition target, the specification reception unit 31 specifies that the addition target is to be converted into an input parameter. is received (“YES” in step S302). In this manner, in steps S301 and S302, an addition target to be added to the input parameters is specified from among the variables or entity values used in the sub-scenario As (input parameter specification). Note that if the user selects anything other than "Add to input parameters" from the menu, the flowchart of FIG. 7 ends.

In step S303, the sub-scenario definition unit 33 determines whether the addition target is an entity value or a variable declared within the sub-scenario. The value "B7" selected as an addition target in the example of FIG. 8A is not a variable but an actual value. Therefore, in the example of FIG. 8A, in step S303, the sub-scenario definition unit 33 determines that the addition target is an actual value.

Then, the sub-scenario definition unit 33 creates a new variable V31 corresponding to the value “B7” to be added (step S304), and replaces the value “B7” with the variable V31 in the sub-scenario definition information Ss ( Step S305). In this example, the name of the variable V31 is "new variable", and as shown in FIG. 8B, the value "B7" as the value E153 in the activity A15 of the sub-scenario definition information Ss is the name of the variable V31 (variable "new variable"). ) is replaced with Further, the sub-scenario definition unit 33 defines the variable V31 as the input parameter IP (step S306). As a result, as shown in FIG. 8B, the variable "new variable" as the variable V31 is added as the input parameter IPa in the header information H of the sub-scenario definition information Ss. The type of this input parameter IPa is automatically set to the type ("character string") of the value "B7" selected as an addition target in steps S301 and S302 (step S307).

The execution results of steps S304 to S307 are updated by the sub-scenario definition section 33 into the sub-scenario definition information Ss stored in the memory section 22 (step S308). Further, the sub-scenario management unit 34 reflects the update of the sub-scenario definition information Ss in the scenario Sm (step S309). As a result, as shown in the main scenario screen Dm (FIG. 8C) displayed on the display 243, in each sub-scenario As called by the scenario Sm, the input parameter IPa is added as the input parameter IP of the sub-scenario As. , the value "B7" selected as the addition target in steps S301 and S302 is set in the definition information DIP2 as the value corresponding to the input parameter IPa. Specifically, the sub-scenario definition unit 33 adds the value "B7" corresponding to the input parameter IPa to the sub-scenario definition information Ss in association with the input parameter IPa. Then, the sub-scenario management unit 34 checks the value "B7" corresponding to the input parameter IPa by referring to the sub-scenario definition information Ss, and sets it to the input parameter IPa of the sub-scenario As on the main scenario screen Dm. Set the value "B7". According to this, the value "B7" is specified in the definition information D153 of the configuring activity A15, that is, the definition information of the configuring activity A15 is the sub-scenario As before the value "B7" is replaced with the variable V31. A similar execution result is obtained by specifying the variable V31 in D153, that is, by subscenario As after being replaced by the variable V31. More specifically, in the sub-scenario As, activity A15 that is executed using the entity value "B7" is replaced with an activity that is executed using the variable V31 that acquires the value "B7" as the entity value. Similar execution results are obtained.

Note that the user can appropriately change the actual value to be input into the input parameter IPa of the sub-scenario As shown on the main scenario screen Dm. Specifically, the user enters a character string specifying another cell on the sheet as the definition information DIPa from a state where the value "B7" is input as the definition information DIPa that defines the actual value to be input to the input parameter IPa. By inputting the character string, the character string can be specified as the entity value to be input to the input parameter IPa, and thereby the entity value input to the sub-scenario As is changed to the character string. Further, any variable can be specified as the definition information DIPa, and in this case, the value acquired as the actual value of the variable is input to the input parameter IPa.

On the other hand, FIG. 9A shows a state in which the variable "Month" declared in activity A15 of sub-scenario As is selected in step S301 and menu M3 is displayed. By selecting the option M31 in this menu M3, the variable "Month" is selected as an addition target. Therefore, in step S303, the sub-scenario definition unit 33 determines that the addition target is a variable declared within the sub-scenario. In this case, the sub-scenario definition unit 33 defines the variable "Month" to be added as the input parameter IPa (step S310). As a result, as shown in FIG. 9B, the variable "Month" is added as an input parameter in the header information H of the sub-scenario definition information Ss. Next, as shown in FIG. 9B, the sub-scenario definition unit deletes the activity A15 in which the selected variable "Month" is declared from the sub-scenario definition information Ss, and the activity Aa corresponding to the activity A15 is added to the scenario Sm. It is added to be executed before sub-scenario As is executed (step S311). Then, the type of "Month" as the input parameter OP2 added in the header information H of the sub-scenario definition information Ss is automatically changed to the type ("Numeric") of "Month" as the variable selected to be added. It is set (step S307).

The execution results of steps S310, S311, and S307 are updated by the sub-scenario definition section 33 into the sub-scenario definition information Ss stored in the memory section 22 (step S308). Further, the sub-scenario management unit 34 reflects the update of the sub-scenario definition information Ss in the scenario Sm (step S309). As a result, as shown in the main scenario screen Dm (FIG. 9C) displayed on the display 243, in each sub-scenario As called by the scenario Sm, the input parameter IPa is added and the input parameter IPa is defined. The variable "Month" selected as an addition target in steps S301 and S302 is set as the value specified in the definition information DIPa. Furthermore, in this case, since the variable "Month degree" is used in the sub-scenario As, the activity Aa that declares the variable "Month degree" will declare the variable "Month degree" before sub-scenario As is executed. It is added to scenario Sm. According to this, the actual value of the variable "Month" is obtained before adding the variable "Month" to the input parameter IPa of the sub-scenario As, that is, as the execution result of the activity A15 that constitutes the sub-scenario As. , the actual value of the variable "Monthly" is obtained even after adding the variable "Monthly" to the input parameter IPa of the sub-scenario As.

Note that the user can appropriately change the actual value to be input into the input parameter IPa of the sub-scenario As shown on the main scenario screen Dm. Specifically, the user inputs a different value to the value input as definition information DIPa that defines the entity value to be input to the input parameter IPa, thereby changing the entity value to be input to the input parameter IPa. Can be changed.

Furthermore, in this embodiment, among the variables included in sub-scenario As, variables declared before sub-scenario As are automatically determined as input parameters when creating the sub-scenario. It may be selected as an input parameter in S302. In this case, the variable is defined as an input parameter by a process similar to step S310.

In the above example, the designation reception unit 31 receives an input parameter designation that designates a variable or entity value included in the sub-scenario As as an input parameter (steps S301, S302). On the other hand, the sub-scenario definition unit 33 updates the input parameters of the sub-scenario As according to the input parameter designation in steps S301 and S302 (steps S306, S310, and S308). With this configuration, the user can use variables or actual values included in the sub-scenario As as input parameters, and can use the sub-scenario As more generally when editing the scenario. Furthermore, the user can designate input parameters by indicating the locations where variables and actual values are actually input in the activities that constitute the sub-scenario As. Therefore, in the sub-scenario As, variables or actual values included in the activity can be specified from the activity whose target value should be changed depending on the location where the sub-scenario As is executed.

Further, when a variable is specified in the input parameter specification to the specification reception unit 31 (“variable” in step S303), the sub-scenario definition unit 33 defines the variable specified in the input parameter specification as an input parameter (step S303). S310). With this configuration, the user can use variables included in the sub-scenario As as input parameters, and can use the sub-scenario As more generally when editing the scenario.

Furthermore, when an entity value is specified in the input parameter specification to the specification receiving unit 31 (“substantive value” in step S303), the sub-scenario definition unit 33 creates a new variable as a variable corresponding to the entity value specified in the input parameter specification. A variable is created (step S304). Further, the sub-scenario definition unit 33 replaces the relevant entity value with a new variable in the sub-scenario As (step S305), and defines the new variable as an input parameter (step S306). With this configuration, the user can use the actual value included in the sub-scenario As as an input parameter, and can use the sub-scenario As more generally when editing the scenario.

The actual value obtained as the new variable V31 (step S304) to be created depends on how the input parameter IPa is defined in the caller of the sub-scenario As that uses the variable V31 as the input parameter IPa. It changes. Therefore, the entity value specified by the user when creating the variable V31 in step S304 is retained as information indicating what entity value is used as the input parameter IPa in the subscenario As caller. . In addition, since the actual value of the variable V31 as the input parameter IPa changes depending on the definition information DIPa in the calling source of the sub-scenario As, if it is held in association with the sub-scenario definition information Ss, the sub-scenario definition information Ss may be displayed as an example of variables included in the sub-scenario As defined in .

By the way, in the sub-scenario As, an output parameter OP can be added. FIG. 10 is a flowchart showing an example of adding an output parameter, and FIGS. 11A to 11D are diagrams showing an example of processing executed based on the flowchart of FIG. 10. Here, unlike the above example, it is assumed that only the variable "Month" is set as the output parameter OP of sub-scenario As (Fig. 11A, Fig. 11B), and the variable "Year" is added as an output parameter (Fig. 11C). ~FIG. 11F) will be explained. Further, in FIGS. 11B and 11D, only a part of the scenario Sm (activity A11 and sub-scenario As) is shown.

In step S401 in FIG. 10, the specification receiving unit 31 receives an instruction to add an output parameter based on the user's operation on the UI 24. The end activity Af is provided with a menu display section Af1 for accepting operations on the end activity Af, and the user displays the menu M4 by clicking the menu display section Af1. FIG. 11C shows a state in which menu M4 is displayed. Menu M4 includes an option "Add output parameter" as option M41, and by selecting this option, an instruction to add an output parameter is accepted. When an instruction to add an output parameter is accepted, an input field N in which a value EOPa indicating definition information DOPa that defines the output parameter OPa to be added is specified is added to the end activity Af of the sub-scenario definition information. (Figure 11D). The user specifies the value to be output as the output parameter OPa by inputting a value into the input field N (step S402). In this embodiment, as shown in the end activity Af of FIG. 11E, the variable "Year" is input as the value EOPa. In this way, in steps S401 and S402, objects to be added to the output parameters are selected. Note that the input to the input field N may be made directly or by selecting from a pull-down menu displayed in the input field N. In the latter case, if the sub-scenario As includes multiple activities that acquire values, for example, among the values acquired by these multiple activities, the value that is not set in the output parameter OP can be set in the pull-down menu. Just display it.

In step S403, the sub-scenario definition unit 33 defines the variable "A.D." to be added as an output parameter (step S403). As a result, the output parameter OPa is added to the header information H, like the sub-scenario definition information Ss shown in FIG. 11E. The type of this output parameter OPa is automatically set to the same type as the value selected as an addition target (step S404). In this embodiment, since the numerical type variable "Year" is selected as the addition target, the type of the output parameter OPa is set to numerical value.

The execution results of steps S403 to S404 are updated by the sub-scenario definition section 33 into the sub-scenario definition information Ss stored in the memory section 22 (step S405). Further, the sub-scenario management unit 34 reflects the update of the sub-scenario definition information Ss in the scenario Sm (step S406). As a result, as shown in the main scenario screen Dm (FIG. 11F) displayed on the display 243, in the sub-scenario As called by the scenario Sm, the added output parameter OPa, ie, "Year" is added.

In the above example, the specification reception unit 31 accepts an output parameter specification that specifies a variable included in the sub-scenario As as the output parameter OP (steps S401, S402), and the sub-scenario definition unit 33 The output parameter OP of the sub-scenario As is updated (steps S403, S405). With such a configuration, the user can use variables included in the sub-scenario As as output parameters OP, and can use the sub-scenario As more generally when editing the scenario. Note that the objects to be added to the output parameters of the sub-scenario As are not limited to variables, and actual values included in the sub-scenario As may be added to the output parameters.

By the way, on the sub-scenario definition screen Ds, the settings related to the output parameter OP can be changed as appropriate according to the user's input to the UI 24. For example, in the example of FIG. 11E, the type of the output parameter OP1 is set to "numeric value", but the user can change the type of the output parameter OP1 to "character string" by inputting to the UI 24. In addition, in the example of FIG. 11E, the type of the output parameter OPa is set to "numeric value", but in the end activity Af, the variable "Year" as the value corresponding to the output parameter OPa is set to a "character string" type variable. By changing to , the settings can be changed so that a "character string" type value is output as the output parameter OPa. Furthermore, in this embodiment, the type of the variable is changed depending on the value acquired as the actual value of the variable. In the example of FIG. 11E, the value "B7" is set as the definition information D153 of the variable "Month" in the activity A15, and the value E153 set as the definition information D153 can be changed to the value "B9". can. In response to such a change in value E153, the type of the variable "Month" is changed in accordance with the type of the value obtained from cell B9. In this way, when changing settings related to output parameters, there is a difference between the type of output parameter OP defined in sub-scenario definition information Ss and the value type of end activity Af associated with the output parameter OP. Inconsistencies may occur. Therefore, you can manage the types of output parameters as follows.

FIG. 12 is a flowchart showing an example of output parameter type management, and FIG. 13 is a diagram showing an example of processing executed based on the flowchart of FIG. 12. In addition, in this example, in the sheet containing the cells in which the values obtained by executing activity A15 are input, cell B7 has a "numeric" type value, and cell B9 has a "character string" type value. Assume that it has been entered. In step S501, the specification reception unit 31 determines whether the setting related to the output parameter OP has been executed on the sub-scenario definition screen Ds based on the user's operation on the UI 24. For example, as shown in FIG. 13, the user can change the value specified in the definition information D153 regarding the variable "Month" in the activity A15 from "B7" to "B9". In the example of FIG. 13, the actual value of the variable "Month" obtained based on the value specified in the definition information D153 is output as the output parameter OP1, so changing the value specified in the definition information D153 is as follows: It is determined that the setting is related to the output parameter OP1 ("YES" in step S501). In the header information H of the sub-scenario definition information Ss, the type of the output parameter OP1 is defined according to the type of the value corresponding to the output parameter OP1 before the settings related to the output parameter OP1 are made. is defined as a "numeric value" type that corresponds to the value obtained from cell B7. The type of the value retrieved from cell B7 is "numeric", while the type of the value input in cell B9 is "character string", so it is retrieved as the actual value of the variable "Month". The value type becomes "string". As in the end activity Af, the variable "Month" is associated with the output parameter OP1. Therefore, when the value specified in the definition information D153 related to the variable "Month" is changed from "B7" to "B9", the type ("numeric value") of the output parameter OP1 and the output parameter OP1 in the end activity Af. The sub-scenario definition unit 33 determines that a mismatch has occurred between the value type (“character string”) associated with (“YES” in step S502).

If it is determined in step S502 that an inconsistency has occurred, the sub-scenario definition unit 33 displays alert L (step S503). In this case, the value returned as the activity execution result constituting the sub-scenario As, in other words, the type of value specified in the end activity Af indicating the activity execution result, and the value output from the sub-scenario As in the scenario Sm. This means that a mismatch has occurred in the type, in other words, the type of the output parameter of sub-scenario As. Therefore, in the end activity Af, an alert L is displayed, such as displaying a value with a mismatch in a different color from other values. Note that if changing the settings of an activity other than the end activity Af causes an inconsistency between the output parameter and the value associated with the output parameter in the end activity Af, change the settings that cause the inconsistency. An alert L indicating the activity performed may be displayed. In this embodiment, since an inconsistency occurs when the settings of activity A15 are changed, alert L may be displayed on activity A15. In addition, an alert L may be displayed in the header information H so that an output parameter with an inconsistency can be easily identified. Further, the display location of the alert L is not limited to one, and for example, the alert L may be displayed on both the end activity Af and the header information H.

The sub-scenario definition unit 33 determines whether the type of the output parameter OP1 in the header information H can be changed to the same type as the variable type set as the value returned by the end activity Af (step S505). Specifically, in the scenario Sm as the calling source that calls the sub-scenario As, it is determined whether the type of the output parameter OP1 can be changed while maintaining consistency with the location where the output parameter is used. In the scenario Sm that calls the sub-scenario As, it is determined whether the type of the output parameter can be changed while maintaining consistency with the activity that is executed after the sub-scenario As and uses the output parameter. For example, by referring to the type required for the output parameter in an activity in which the output parameter is used, it is determined whether the type of the output parameter OP1 of the header information H can be changed. Furthermore, for example, even if the type required for the output parameter in an activity in which the output parameter OP1 is used is different from the changed type of the output parameter OP1, the output parameter according to the type required for the output parameter OP1 may be changed. If type conversion is possible, it is determined that the type of output parameter OP1 can be changed. Since the output parameter of sub-scenario As is a value used in a subsequent activity, the type is often fixed to a specific type so that it can be used in the subsequent activity. Therefore, by determining in advance whether the output parameter has a value whose type can be changed, it is possible to change the methods that the user can select.

If the type of the output parameter OP1 can be changed (“YES” in step S505), the sub-scenario definition unit 33 changes the value associated with the output parameter OP1 in the output parameter OP1 of the header information H and the end activity Af. It is determined which type of change is selected (step S506). Specifically, a screen that allows the user to select an object to change the type is displayed on the display 243, and it is determined which value change has been selected based on the user's operation on the UI 24 on the screen. When the sub-scenario definition unit 33 determines that the user has selected to change the output parameter type (“output parameter” in step S506), the sub-scenario definition unit 33 changes the output parameter type in the header information H to the end activity. Af is changed to the value type associated with the output parameter (step S507). In this embodiment, since there is a mismatch between the output parameter OP1 and the variable "monthly degree" as a value associated with the output parameter OP1, the type of the output parameter OP1 is changed to the type of the variable "monthly degree". When the type of the output parameter is changed, the type of the output parameter matches the type of the value associated with the output parameter in the end activity Af, so the alert L displayed on the sub-scenario definition screen Ds is changed. Erase (step S508).

On the other hand, if it is determined in step S506 that the user has selected to change the value type associated with the output parameter OP1 in the end activity Af ("value type of end activity" in step S506), the sub-scenario definition unit 33 , the end activity Af is changed so that a value of the same type as the type of the output parameter OP1 of the header information H is obtained as a value associated with the output parameter OP1 from the end activity Af (step S510). In this example, the type of the output parameter OP1 of the header information H is "numeric value", whereas the type of the variable "month", which is the value associated with the output parameter OP1 in the end activity Af, is "character string". It is. In step S510, a process is added to the end activity Af to convert the entity value acquired as the variable "monthly degree" into a "numeric" type, so that the entity value acquired as the variable "monthly degree" is converted to the "numeric" type. The value is associated with the output parameter OP1. When the end activity Af is changed in this way, and the inconsistency between the output parameter type and the value type associated with the output parameter in the end activity Af is resolved, the sub-scenario definition unit 33 , the alert L is deleted on the sub-scenario definition screen Ds (step S508).

Furthermore, if it is determined that the type of the output parameter cannot be changed (“NO” in step S505), the sub The scenario definition unit 33 changes the ending activity Af (step S510) and erases the alert L on the sub-scenario definition screen Ds (step S508). Note that when changing the type of the output parameter OP or the value type of the end activity, a configuration may be adopted in which the user is asked to confirm whether or not the change can be made.

Due to this management of the output parameters OP in FIG. 12, type inconsistency occurs between the output parameters OP of sub-scenario As and the value (value of end activity Af) corresponding to the output parameters OP of sub-scenario As. If this happens, you can respond appropriately.

By the way, in the above embodiment, the main scenario screen Dm and the sub-scenario definition screen Ds are displayed on the display 243. These may be displayed in parallel, or the screen displayed on the display 243 may be configured to be switched between the main scenario screen Dm and the sub-scenario definition screen Ds, as described below.

FIGS. 14A and 14B are diagrams illustrating a configuration for switching the displayed screen between the main scenario screen and the sub-scenario definition screen. In FIG. 14A, a main scenario screen Dm is shown, and in FIG. 14B, a sub-scenario definition screen Ds is shown. The user can display a sub-scenario definition screen Ds related to the selected sub-scenario As by selecting a sub-scenario As on the main scenario screen and performing a predetermined operation. In FIG. 14A, the user selects one sub-scenario As from among the sub-scenarios As in the main scenario screen Dm displayed on the display 243, and selects a menu M4 related to the selected sub-scenario by a predetermined operation. Indicates the displayed state. Menu M4 includes an option M41 that says "Move to sub-scenario definition" and an option M42 that says "Develop sub-scenario." Both options M41 and M42 are options that are not displayed in connection with other activities of the scenario, but are included in a menu that is displayed when sub-scenario As is selected. When "Move to sub-scenario definition" is selected as option M41 from the displayed menu M4, a sub-scenario definition screen Ds shown in FIG. 14B is displayed on the display 243 for the selected sub-scenario As.

On the other hand, the user can display, from the sub-scenario definition screen Ds, a location where the sub-scenario As defined by the sub-scenario definition information Ss shown in the sub-scenario definition screen Ds is to be called. FIG. 14B shows a state in which the sub-scenario definition screen Ds is displayed on the display 243, and a menu M5 for displaying information related to the sub-scenario definition screen Ds is displayed by a predetermined operation. Menu M5 includes an option "Move to caller" as option M51. When option M51 "Move to caller" is selected from menu M5, a menu M52 for selecting one of the subscenario As callers defined on the subscenario definition screen Ds is displayed. In FIG. 14B, an option M521 ("caller 1") and an option M522 ("caller 2") are displayed as the menu M52. When the user selects the option M521 and selects "caller 1", the main scenario screen Dm corresponding to "caller 1" is displayed on the display 243, and the sub-scenario As is called on the main scenario screen Dm. The range (caller) is displayed. For example, if a large number of calling sources exist in the scenario Sm, the area surrounding the selected calling source is displayed on the display 243, including the selected calling source.

Furthermore, the user can instruct an operation for arranging an activity constituting the sub-scenario As instead of the sub-scenario As on the screen including the sub-scenario As. In FIG. 14A, when one sub-scenario As is selected and option M42 "Expand sub-scenario" of menu M4 opened by a predetermined operation is selected, option M421 ("expand only this sub-scenario") and option M422 (" ``Expand the two locations in use'') will be displayed. When option M421 is selected, the sub-scenario development unit 341 of the sub-scenario management unit 34 develops the sub-scenario As selected in the process of displaying the menu M4 into activities A12 to A15 that constitute the sub-scenario As. do. In other words, activities A12 to A15 are arranged instead of sub-scenario As. Further, when option M422 is selected, the sub-scenario development unit 341 of the sub-scenario management unit 34 converts the two sub-scenarios As (sub-scenario As1 and sub-scenario As2) included in the scenario Sm into two sub-scenarios As. Expand to the constituent activities A12 to A15.

In this way, the sub-scenario development unit 341 develops the sub-scenario As defined by the sub-scenario creation unit 32 into activities A12 to A15 that constitute the sub-scenario As, according to the input received by the specification reception unit 31. do. With such a configuration, the sub-scenario As can be easily returned to the activities A12 to A15 that make up the sub-scenario As.

As described above, in this embodiment, the storage unit 111 of the server 11 corresponds to an example of the "recording medium" of the present invention, the scenario management program 12 corresponds to an example of the "scenario management program" of the present invention, The terminal device 2 corresponds to an example of the "scenario management device" and "computer" of the present invention, the display 243 of the UI 24 corresponds to an example of the "scenario display section" of the present invention, and the specification reception section 31 corresponds to an example of the "scenario management device" and "computer" of the present invention. The sub-scenario creation unit 32 corresponds to an example of the “batch activity creation unit” of the present invention, and the parameter determination unit 321 corresponds to an example of the “parameter determination unit” of the present invention. The sub-scenario definition section 33 corresponds to an example of the "batch activity definition section" of the present invention, and the sub-scenario expansion section 341 corresponds to an example of the "batch activity expansion section" of the present invention, and includes activities A11 to A16, A21 to A26. corresponds to an example of "multiple activities" of the present invention, sub-scenario As corresponds to an example of "batch activity" of the present invention, scenario Sm corresponds to an example of "scenario" of the present invention, and spreadsheet software corresponds to an example of "another application program" of the present invention.

Note that the present invention is not limited to the above-described embodiments, and various changes can be made to the above-described embodiments without departing from the spirit thereof. For example, in the above embodiment, when editing the scenario Sm using the sub-scenario As, the input parameters of the sub-scenario As are appropriately set by the user. For example, in the example shown in FIG. 4E, "overtime time file (2)" is set for the input parameter arg1 for the second sub-scenario As. At this time, the user's input can be assisted as follows.

FIG. 15 is a diagram illustrating an example of an assist operation for user input. As shown in FIG. 15, when the user selects the input field for the variable arg1 in the second sub-scenario As called in the scenario Sm, candidates that can be input into the input field are displayed on the sub-scenario definition screen Ds. This candidate is a variable that has been declared in activities A11 and A21 that are executed before sub-scenario As in scenario Sm, and whose actual value has been obtained, and which includes the sub-scenario As in its scope (valid range of variables). be.

For example, if the user selects "overtime time file (2)" from the candidates "overtime time file" and "overtime time file (2)", then in the second sub-scenario As, the variable arg1 is set to "overtime time file". File(2)" is set. Therefore, in the sub-scenario As, the "overtime time file (2)" will be acquired.

In other words, a variable declared in an activity executed in scenario Sm has a scope that is the effective range of the variable. On the other hand, the display 243 (scenario display unit) shows variables whose scope includes the sub-scenario As as candidates for setting values for the input parameter arg1 of the sub-scenario As. With this configuration, the user can input a setting value to the input parameter arg1 while referring to candidates for the setting value. As a result, the user can easily input a setting value to the input parameter arg1.

Further, the target on which the process of extracting the sub-scenario As can be executed is not limited to the scenario Sm described above. In other words, the above scenario Sm is only one specific example, and the process of extracting sub-scenarios As can be executed for various scenarios Sm.

The present invention is applicable to RPA technology in general, which aims to reduce the user's work burden by automating the work that the user previously performed using a computer.

11...Server 111...Storage section (recording medium)
12...Scenario management program 2...Terminal device (scenario management device, computer)
24...UI
243...Display (scenario display section)
31...Designated Reception Department (Designated Reception Department)
32...Sub-scenario creation department (batch activity creation department)
321...Parameter determination section 33...Sub-scenario definition section (batch activity definition section)
341...Sub-scenario development section (batch activity development section)
A11-A16, A21-A26...Activity As...Sub-scenario (batch activity)
Sm…Scenario

Claims (14)

A scenario management device that manages a scenario for automating operations on other application programs, the scenario including a plurality of activities indicating the operations,
a designation reception unit that accepts an extraction target designation that designates an activity to be extracted from among the plurality of activities;
a batch activity creation unit that defines a batch activity for collectively executing the extraction target activities accepted by the specification reception unit;
a parameter determination unit that determines, as an input parameter, a variable that is used in the batch activity and is declared in an activity that is executed before the extraction target activity in the scenario;
a scenario display unit that displays a screen that accepts input of setting values for the input parameters of the batch activity used in the scenario;
A scenario management device comprising: A variable declared in the activity has a scope that is the valid range of the variable,
2. The scenario management device according to claim 1, wherein the scenario display unit displays variables whose scope includes the batch activity as candidates for the setting value for the input parameter. The parameter determining unit is configured to select, as an output parameter, a variable whose actual value is acquired by execution of the activity to be extracted, and which is used in an activity executed after the activity to be extracted in the scenario. decided as,
adding an end activity that returns an actual value of the variable determined as the output parameter to the bulk activity;
The scenario management device according to claim 1, wherein when the batch activity is executed, the batch activity outputs the actual value of the output parameter. The scenario management device according to claim 3, wherein the parameter determination unit determines the type of the entity value of the variable determined as the output parameter to be the type of the entity value as the type of the output parameter. The parameter determining unit selects a first parameter as a variable whose actual value is acquired by execution of the activity to be extracted, and which is used in an activity executed after the activity to be extracted in the scenario. If a variable and a second variable exist, determining the first variable as a first output parameter and determining the second variable as a second output parameter;
When the batch activity is executed, the batch activity outputs an actual value of the first output parameter and an actual value of the second output parameter,
3. The scenario display unit displays the first output parameter and the second output parameter independently of each other, and displays a screen that accepts editing of the first output parameter and editing of the second output parameter. The scenario management device described in . a bulk activity expansion unit that expands the bulk activity defined by the bulk activity creation unit into the activity specified as the extraction target when defining the bulk activity, in accordance with the input received by the specification reception unit; The scenario management device according to claim 1, further comprising: a scenario management device according to claim 1; The specification reception unit according to claim 1, wherein the specification reception unit executes replication of the batch activity to a replication range different from the existence range of the extraction target activity in the scenario, in response to an input to the specification reception unit. Scenario management device. It further includes a bulk activity definition section,
The specification receiving unit receives an input parameter specification that specifies a variable or an entity value included in the batch activity as the input parameter,
The scenario management device according to claim 1, wherein the batch activity definition unit updates the input parameters of the batch activity according to the input parameter designation. The scenario management device according to claim 8, wherein when a variable is specified by the input parameter specification in the specification reception unit, the collective activity definition unit defines the variable specified by the input parameter specification as the input parameter. . When an entity value is specified in the input parameter specification in the specification reception unit, the batch activity definition unit creates a new variable as a variable corresponding to the entity value specified in the input parameter specification, and 9. The scenario management device according to claim 8, wherein the entity value is replaced with the new variable and the new variable is defined as the input parameter. It further includes a bulk activity definition section,
The specification receiving unit receives an output parameter specification that specifies a variable or an entity value included in the batch activity as the output parameter,
The scenario management device according to claim 3, wherein the batch activity definition unit updates the output parameters of the batch activity according to the output parameter designation. A scenario management program that causes a computer to function as the scenario management device according to claim 1. A recording medium on which the scenario management program according to claim 12 is recorded in a readable manner by a computer. A scenario management method for managing a scenario for automating operations on other application programs, the scenario including a plurality of activities indicating the operations, the scenario management method comprising:
a step of receiving an extraction target designation specifying an activity to be extracted from among the plurality of activities by a designation reception unit;
defining a batch activity for collectively executing the extraction target activities accepted by the specification reception unit;
determining, as an input parameter, a variable used in the batch activity and declared in an activity executed before the extraction target activity in the scenario;
displaying a screen that accepts input of setting values for the input parameters of the batch activity used in the scenario;
A scenario management method with

Images