JP2021043716A - Scenario execution device, scenario execution method, and program - Google Patents

Abstract

To receive, during the execution of a scenario of an automation tool, a user instruction regarding the execution of the scenario.SOLUTION: A function execution unit of a scenario execution device executes a predetermined function according to a user operation. A reading unit reads processing modules in execution order, from a scenario file that indicates processing modules, which are either a user operation module representing a user operation on the function execution unit or a user interface module representing the use of an interface that performs notification to a user and receives a response, and the execution order of the processing modules. When the user operation module is read, an operation control unit controls an input unit in such a way as to perform a user operation indicated by the user operation module. When the user interface module is read, a notification unit performs notification to the user indicated by the user interface module, and an execution control unit continues or stops the execution of the scenario file based on the received response.SELECTED DRAWING: Figure 2

Description

The present invention relates to a scenario execution device, a scenario execution method, and a program.

RPA (Robotic Process Automation), which is a type of automation tool, is a technology that can automatically perform routine tasks that have been performed manually by operating the user interface of an information processing device such as a PC (personal computer). For example, a scenario describing a work procedure is created (see, for example, Patent Document 1), and a PC executes the work based on the description of the scenario to automatically reproduce the work performed manually (for example,). See Patent Document 2). With RPA, time cost and human cost can be reduced, and work mistakes can be reduced. On the other hand, there is a technique in which a PC automatically starts an application program when it detects the occurrence of a trigger specified by the user and notifies the user (for example, Patent Document 3).

Japanese Patent No. 5026451 Japanese Patent No. 4883638 Japanese Patent No. 4055911

As described above, the RPA describes a series of routine manual operations using the user interface in a scenario, and causes the PC to automatically execute the operations. Therefore, it is not necessary for the user to perform an operation for inputting an instruction to the PC while the scenario is being executed. However, there are cases where the user wants to instruct the operation to be executed by the PC at his / her discretion.

In view of the above circumstances, it is an object of the present invention to provide a scenario execution device, a scenario execution method, and a program that can receive a user's instruction regarding the execution of a scenario during the execution of a scenario of an automation tool.

One aspect of the present invention is an input unit for inputting a user operation, a function execution unit that executes a predetermined function according to the user operation by the input unit, and a user operation module representing a user operation on the function execution unit. One or more processing modules which are user interface modules representing the use of an interface for receiving a notification to and a response to the notification, a storage unit for storing a scenario file indicating the execution order of the processing modules, and an execution target. A reading unit that reads the processing module from the scenario file in the order of execution, a determination unit that determines whether the processing module read by the reading unit is the user operation module or the user interface module, and the determination unit. When it is determined that the user operation module is the operation control unit which controls the input unit so as to perform the user operation indicated by the user operation module, and when it is determined that the determination unit is the user interface module. , The notification unit that notifies the user indicated by the user interface module, and the continuation or termination of the execution of the scenario file or the execution of another scenario file based on the response received in response to the notification by the notification unit. It is a scenario execution device including an execution control unit for performing the above.

One aspect of the present invention is the above-mentioned scenario execution device, and the user interface module corresponds to an instruction content and subsequent processing information indicating continuation or termination of execution of the scenario file or execution of another scenario file. The execution control unit includes the attached information, and the execution control unit continues or ends the execution of the scenario file, or the like, according to the subsequent processing information set in the user interface module in response to the instruction content indicated by the received response. Execute the scenario file of.

One aspect of the present invention is the scenario execution device described above, and the subsequent processing information includes information on the processing module to be executed next in the case of continuation of execution of the scenario file.

One aspect of the present invention is the above-mentioned scenario execution device, and when the execution control unit is set with information that the user interface module does not receive a response, the notification unit gives the notification. After that, the execution of the scenario file to be executed is continued.

One aspect of the present invention is the scenario execution device described above, wherein the response includes a set value of a variable, and the execution control unit executes the scenario file to obtain the variable before transmission of the notification. The value of is updated to the set value of the variable included in the response, and the execution of the scenario file to be executed is continued using the updated variable.

One aspect of the present invention is the scenario execution device described above, wherein the response includes a setting value of property information representing a setting related to the processing module, and the execution control unit executes execution of the scenario file to be executed. When continuing, the processing module included in the scenario file is executed using the set value of the property information included in the response.

One aspect of the present invention is the scenario execution device described above, wherein the notification includes the value of a variable obtained by executing the scenario file to be executed before the transmission of the notification.

One aspect of the present invention is the above-mentioned scenario execution device, in which the notification by the notification unit is transmitted to the user's terminal device after the data format is converted by the conversion device, and the execution control unit is used. The response returned from the terminal device and whose data format has been converted by the conversion device is received.

One aspect of the present invention is the scenario execution device described above, wherein the conversion device transmits the notification to the terminal device and receives the response from the terminal device by chat, e-mail, or telephone. Do.

One aspect of the present invention is a scenario execution method executed by a scenario execution device, in which a function execution step for executing a predetermined function according to a user operation by an input unit and a user for executing the function by the function execution step. An execution target indicating one or more processing modules that are user operation modules that represent operations or user interface modules that represent the use of an interface that notifies the user and receives a response to the notification, and the execution order of the processing modules. A read step of reading the processing modules from the scenario file in the order of execution, a determination step of determining whether the processing module read in the read step is the user operation module or the user interface module, and the determination step. When it is determined that the user operation module is the user operation module, the operation control step for controlling the input unit to perform the user operation indicated by the user operation module, and when it is determined to be the user interface module in the determination step, Based on the notification step that notifies the user indicated by the user interface module and the response received in response to the notification by the notification step, the execution of the scenario file is continued or terminated, or the execution of another scenario file is executed. It is a scenario execution method having an execution control step to be performed.

One aspect of the present invention is a program for causing a computer to function as the above-mentioned scenario execution device.

According to the present invention, it is possible to receive a user's instruction regarding execution of a scenario during execution of a scenario of an automation tool.

It is a block diagram of the scenario execution system by one Embodiment of this invention. It is a functional block diagram which shows the structure of the scenario execution apparatus by the same embodiment. It is a functional block diagram which shows the structure of the terminal apparatus by the same embodiment. It is a functional block diagram which shows the structure of the conversion apparatus by the same embodiment. It is a figure which shows the screen display example in the scenario execution apparatus by the same embodiment. It is a figure which shows the screen display example in the scenario execution apparatus by the same embodiment. It is a figure which shows the screen display example in the scenario execution apparatus by the same embodiment. It is a figure which shows the screen display example in the scenario execution apparatus by the same embodiment. It is a figure which shows the screen display example in the scenario execution apparatus by the same embodiment. It is a figure which shows the screen display example in the scenario execution apparatus by the same embodiment. It is a figure which shows the screen display example in the terminal apparatus by the same embodiment. It is a flow diagram which shows the scenario generation processing of the scenario execution apparatus by the same embodiment. It is a flow figure which shows the scenario execution process of the scenario execution apparatus by the same embodiment. It is a flow figure which shows the scenario execution process of the scenario execution apparatus by the same embodiment. It is a sequence diagram of the scenario execution system at the time of notification execution by the same embodiment. It is a figure which shows the example of the log data.

Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.
FIG. 1 is a configuration diagram of a scenario execution system 100 according to an embodiment of the present invention. The scenario execution system 100 includes a scenario execution device 1 and a terminal device 3 of a user who uses RPA, and a conversion device 5 of a business operator. RPA is an example of an automation tool. Examples of users are, but are not limited to, businesses, schools, organizations, and so on. In the figure, only one scenario execution device 1 and one terminal device 3 are shown, but the number of users and the number of scenario execution devices 1 and terminal devices 3 used by each user are arbitrary. The business operator that owns the conversion device 5 may be a business operator that provides the RPA service, or may be another business operator. The scenario execution device 1, the terminal device 3, and the conversion device 5 are connected to the network 9 wirelessly or by wire. The network 9 is, for example, a public network such as the Internet or a mobile phone network, but may be a private network such as a LAN (Local Area Network), or may be a combination of a public network and a private network. A service providing device 7 of a business operator that provides a communication service using the network 9 is connected to the network 9. The number of service providing devices 7 connected to the network 9 is arbitrary. The user may have a conversion device 5 and a service providing device 7.

The scenario execution device 1 is an information processing device such as a PC, and executes an RPA scenario. The scenario shows the operations performed on the scenario execution device 1 by the user interface and the execution order of the operations. The terminal device 3 is, for example, a smartphone, a tablet terminal, a PC, a mobile phone, or the like. The conversion device 5 is realized by an information processing device such as a server computer, for example. The conversion device 5 converts the notification addressed to the terminal device 3 received from the scenario execution device 1 during scenario execution into a data format corresponding to the network service provided by the service providing device 7, and transmits the notification to the service providing device 7. Further, the conversion device 5 receives the response returned by the terminal device 3 in response to the transmitted notification from the service providing device 7. The conversion device 5 converts the data format of the received response into a data format that can be received by the scenario execution device 1, and transmits the data format to the scenario execution device 1. The scenario execution device 1 continues or ends the execution of the scenario or executes another scenario according to the user's instruction indicated by the response. The communication service provided by the service providing device 7 is a messenger service using an SNS (Social Networking Service) or the like, an e-mail, an SMS (short message service), a telephone, or the like. Examples of messenger services are chat tools such as LINE®, Slack®, TEAMS®.

FIG. 2 is a functional block diagram showing the configuration of the scenario execution device 1 according to the embodiment of the present invention, and only the functional blocks related to the present embodiment are extracted and shown. The scenario execution device 1 includes a communication unit 11, a storage unit 12, an input unit 13, a display unit 14, and a processing unit 15. The communication unit 11 communicates with another device via the network 9. The storage unit 12 stores the scenario file. A scenario file is a file in which a scenario is described. The scenario shows the processing modules and the execution order of the processing modules. The processing module includes a user operation module and a user interface module. The user operation module represents a user operation using a user interface. The target of the user operation is, for example, an application program (hereinafter, also referred to as an application) or an OS (Operation System) executed in the scenario execution device 1. The user interface module represents the use of an interface for notifying a user and receiving a response from the user to the notification. The notification to the user and the reception of the response to the notification are performed, for example, via the network 9. The user interface module may only notify the user. The content of the notification to the user and the subsequent processing information for each response received in response to the notification are added to the user interface module. Subsequent processing information indicates processing to be performed in response to a response. For example, the subsequent processing information includes continuation of execution of the scenario file being executed, termination of execution of the scenario file being executed, execution start of another scenario file different from the scenario file being executed, and the like.

The input unit 13 is configured by using an existing input device such as a keyboard, a pointing device (mouse, tablet, etc.), a button, and a touch panel. The input unit 13 is a user interface operated by the user when inputting a user's instruction to the scenario execution device 1. The display unit 14 is an image display device such as a CRT (Cathode Ray Tube) display, a liquid crystal display, or an organic EL (Electro Luminescence) display.

The processing unit 15 includes a scenario creation unit 16, a scenario execution management unit 17, a scenario execution unit 18, and a function X execution unit 19.

The scenario creation unit 16 includes a creation information receiving unit 161, a screen display control unit 162, and a scenario registration unit 163. The creation information receiving unit 161 receives the information regarding the creation of the scenario input by the user by the input unit 13. The screen display control unit 162 displays the scenario creation screen on the display unit 14. The scenario creation screen displays a list of processing modules that can be used for scenario creation, and information on the processing modules that make up the scenario being created and their execution order. The scenario registration unit 163 generates a scenario file in which a scenario created based on the selection of the processing module performed by the user using the scenario creation screen and the specification of the execution order of the selected processing module is described. The value of the property information input by the user by the input unit 13 is added to the processing module. The property information includes variables representing settings related to the processing module and their values. The scenario registration unit 163 registers the generated scenario file in the storage unit 12.

The scenario execution management unit 17 manages the execution of the scenario. The scenario execution management unit 17 may store the scenario execution schedule in the storage unit 12 according to the instruction input by the user by the input unit 13. The scenario execution management unit 17 instructs the scenario execution unit 18 to execute the scenario according to the stored execution schedule.

The scenario execution unit 18 includes a reading unit 181, a determination unit 182, an operation control unit 183, a notification unit 184, and an execution control unit 185. The reading unit 181 reads the processing modules in the order of execution from the scenario file in which the scenario instructed to be executed by the scenario execution management unit 17 is described. The determination unit 182 determines whether the processing module read by the reading unit 181 is a user operation module or a user interface module. When the determination unit 182 determines that the determination unit 182 is a user operation module, the operation control unit 183 controls the input unit 13 to perform the user operation indicated by the user operation module.

When the determination unit 182 determines that the user interface module is a user interface module, the notification unit 184 transmits a notification to the user indicated by the user interface module to the conversion device 5. The execution control unit 185 receives the response transmitted by the terminal device 3 from the conversion device 5 in response to the notification by the notification unit 184. The execution control unit 185 continues or interrupts the execution of the scenario file or executes another scenario file according to the subsequent processing information set in the user interface module in response to the received response. If the execution of the scenario file is continued, the setting value of the variable entered by the user may be included in the response. The execution control unit 185 updates the value of the variable obtained before sending the notification by executing the scenario file to the setting value of the variable included in the response, and uses the variable of the updated setting value of the scenario file. Continue execution. In addition, when the execution of the scenario file is continued, the setting value of the property information may be included in the response. When the execution control unit 185 continuously executes the scenario file, the execution control unit 185 executes the processing module included in the scenario file by using the set value of the property information included in the response.

The function X execution unit 19 executes the function X according to an operation using the input unit 13. Function X is a function that can be used to execute a scenario, and can be any function. The function X may be realized by the CPU executing the application program. For example, the function X can be any function implemented in a PC, such as spreadsheets, document editing, a web browser, postcard creation, and drawing. In the figure, the function X execution unit 19 (X = A, B, C) that executes the function X is described as the function A execution unit 19a, the function B execution unit 19b, and the function C execution unit 19c.

FIG. 3 is a functional block diagram showing the configuration of the terminal device 3, and only the functional blocks related to the present embodiment are extracted and shown. The terminal device 3 includes a communication unit 31, a control unit 32, a display unit 33, and an input unit 34. The communication unit 31 communicates with another device via the network 9. The control unit 32 performs a process of displaying the data received via the communication unit 31 on the display unit 33, and a process of transmitting and receiving information via the communication unit 31 according to an instruction input by the input unit 34. The display unit 33 is an image display device such as a CRT display, a liquid crystal display, or an organic EL display. The input unit 34 is configured by using an existing input device such as a keyboard, a pointing device, a button, and a touch panel. When the terminal device 3 is a smartphone or a mobile phone, the terminal device 3 further includes a receiving unit and a transmitting unit for a call.

FIG. 4 is a functional block diagram showing the configuration of the conversion device 5, and only the functional blocks related to the present embodiment are extracted and shown. The conversion device 5 includes a communication unit 51, a storage unit 52, and a conversion unit 53. The communication unit 51 communicates with another device via the network 9. The storage unit 52 stores the conversion rule of the data format for each network service. The conversion unit 53 converts the notification addressed to the terminal device 3 received from the scenario execution device 1 into a data format corresponding to the network service provided by the service providing device 7 according to the conversion rule stored in the storage unit 52 and outputs the notification. To do. Further, the conversion unit 53 receives the response returned from the terminal device 3 to the scenario execution device 1 from the service providing device 7, and sets the data format of the received response to the scenario execution device according to the conversion rule stored in the storage unit 52. Converts 1 into a receivable data format and outputs it. When communicating with the terminal device 3 using chat, the conversion unit 53 may have a chatbot function. Further, for example, when communicating with the terminal device 3 using a telephone, the conversion unit 53 has a voice synthesizer that converts text into voice and outputs it, and a voice recognition device that converts input voice into text. ..

5 and 10 are diagrams showing an example of screen display in the scenario execution device 1. The scenario creation screen 200a shown in FIG. 5 has a library display area 201 and a scenario creation area 202. The library display area 201 is an area for displaying a list of available processing modules by module name. The module name is the name of the processing module. The list of processing modules includes user operation modules and user interface modules. The scenario creation area 202 is an area for designating the execution order of the processing modules.

Here, a case where there are a user notification module and a property setting module as user interface modules will be described. The user notification module only notifies the user, or notifies the user and receives the response from the user, and determines the subsequent processing according to the user instruction set in the response. The property setting module notifies the user and receives the response from the user, sets the setting value of the property information set in the response to the property information of the processing module in the scenario, and continues the execution of the scenario.

The user selects the module name of the processing module to be added from the list of processing modules displayed in the library display area 201 by the input unit 13 such as a mouse. The processing module to be added is described as an additional processing module. In the figure, the case where the additional processing module is the user notification module is shown as an example. "User notification" is the module name of the user notification module. The user drags the selected additional processing module to the scenario creation area 202 (drag and drop) with the mouse. As a result, the scenario creation screen 200b shown in FIG. 6 is displayed.

The scenario execution device 1 additionally displays the processing symbol 212-1 that displays the module name of the additional processing module at the end position of the drag in the scenario creation area 202 of the scenario creation screen 200b shown in FIG. The end position is between the node 211-1 representing the start of the scenario and the node 211-2 representing the end of the scenario. When the user instructs the property input of the processing symbol 212-1 by the input unit 13 such as a mouse, the scenario execution device 1 displays the property input screen 220 shown in FIG. 7. The property input instruction of the processing symbol 212-1 can be, for example, an operation of double-clicking on the display of the processing symbol 212-1.

The property input screen 220 includes a target application input field 221, a connection setting input field 222, utterance type selection buttons 223a and 223b, and an utterance setting area 224. The target application input field 221 specifies an application of the network service used for notifying the user to the terminal device 3. The specified applications are various messenger services, e-mail, unique UI (user interface), user's locale application, telephone, and the like. In the connection setting input field 222, the transmission destination of the notification using the application selected in the target application input field 221 is input by text. In the case of a messenger service such as chat, the ID and name of the user used as the destination in the messenger service are set. For email, an email address is set. In the case of a telephone, a telephone number is set. The selection buttons 223a and 223b each select whether the type of utterance is notification only or there is a user response. With user response means to give a notification and further receive a user's response to the notification.

The utterance setting area 224 differs depending on whether the type of utterance is notification only or there is a user response. When the utterance setting is only notification, the utterance setting area 224 has a notification message input field 225 and a notification variable input field 226. When the utterance setting has a user response, the utterance setting area 224 has a user response button setting area 227 and a notification interval selection button 228 in addition to the notification message input field 225 and the notification variable input field 226.

In the notification message input field 225, a message to be notified to the user is input by text. In the notification variable input field 226, among the variables obtained by executing the scenario, the variable that notifies the user of the value is input. The variable is selected by the pull-down menu, and the variable name used for notification is entered by text. The pull-down menu displays the variables used in the scenario.

In the user response button setting area 227, a button for the user to respond is set in the terminal device 3 that has received the notification. The button setting area 227 for user response includes a button display name input field 2271, an action selection field 2272 for selecting an action (action) when a button is selected, and a variable selection field for selecting a variable for which the user sets a value. Includes 2273 and.

In the button display name input field 2271, a character string to be displayed on the button for the user to input a response is input. The action set in the action selection field 2272 and the variable set in the variable selection field 2273 are used as subsequent processing information. The action is to execute the specified processing module in the scenario (continue execution of the scenario), set the value in the variable and execute the specified processing module in the scenario (continue execution of the scenario), end the execution of the scenario, and specify the scenario. Execution, hold, etc. In the action selection field 2272 shown in the figure, an action can be selected from the pull-down menu. If the scenario continues to run, the user selects the next processing module to run. For example, the module name of the processing module that follows the user notification module is included in the pull-down menu and displayed, and the user is made to select the processing module that follows. If there is only one processing module following the user notification module, the module name may be omitted. When the value is set in the variable and the specified processing module in the scenario is executed, the variable used in the scenario is displayed in the variable selection field 2273 by the pull-down menu, and the user is made to select the variable for which the value is set. When executing the specified scenario, the scenario file name is displayed in the action selection field 2272 including the pull-down menu, and the user is made to select the scenario file name of the scenario to be executed. The notification interval selection button 228 is a button for selecting a time interval for resending the notification when the response notified to the user cannot be received or the action is pending.

When the user performs a save operation such as clicking the OK button 229 on the property input screen 220 by the input unit 13, the scenario execution device 1 displays the property input screen 220 in association with the user notification module represented by the processing symbol 212-1. Stores the property information of the entered setting value.

FIG. 7 further shows an example of the notification screen 400 displayed on the display unit 33 of the terminal device 3. The terminal device 3 receives a notification from the conversion device 5 using the implemented messenger service application, and displays the notification screen 400. The notification content is based on the content set on the property input screen 220, and the conversion device 5 receives this setting content from the scenario execution device 1. The text 401 is a display of the text entered in the notification message input field 225. The text 402 is a display of the variable name input in the notification variable input field 226 and the value of the variable in which the variable name is set. The buttons 403a, 403b, 403c, and 403d display the button display name input in the button display name input field 2271. When the user selects any of the buttons 403a, 403b, 403c, and 403d, the terminal device 3 transmits a response in which the identification information of the selected button is set as the instruction content.

FIG. 8 shows a scenario creation screen 200c after the scenario is completed. In the scenario creation area 202, rectangular processing symbols 212-1 to 212-4 in which the module name of the processing module selected by the user by the input unit 13 is described are displayed. Arrows 213-1 to 213-6 represent the execution order of the processing modules. The arrow 213-1 from the node 211-1 indicating the start indicates that the processing module represented by the processing symbol 212-2 at the tip of the arrow is executed after the scenario starts. The arrow 213-2 indicates that the processing module represented by the processing symbol 212-2 at the base of the arrow is executed, and then the processing module represented by the processing symbol 212-1 at the tip of the arrow is executed. The arrow 213-3 indicates that the processing module represented by the processing symbol 212-1 at the base of the arrow is executed, and then the processing module represented by the processing symbol 212-3 at the tip of the arrow is executed. The arrow 213-4 indicates that the processing module represented by the processing symbol 212-1 at the base of the arrow is executed, and then the processing module represented by the processing symbol 212-4 at the tip of the arrow is executed. After executing the user notification module of the processing symbol 212-1, which of the processing symbol 212-3 and the processing symbol 212-4 represents the processing module to be executed is determined by the user response button setting area 227 of the property input screen 220. Follows the contents set in and the response from the user.

FIG. 9 shows a scenario creation screen 200d in which a scenario is created using the property setting module. In the scenario creation area 202, rectangular processing symbols 215 to 215-3 in which the module name of the processing module selected by the user by the input unit 13 is described are displayed. Arrows 216-1 to 216-4 indicate that the execution order of the processing modules is the processing symbols 215-1, 215-2, 215-3. The processing symbols 215-1 and 215-3 represent the user operation module, and the processing symbols 215-2 represent the property setting module.

When the user instructs the property input of the processing symbol 215-1 such as double-clicking on the display of the processing symbol 215-1 by the input unit 13 such as a mouse, the scenario execution device 1 is the user operation module of the processing A. Display the property input screen. The user inputs the setting value of the property information of the process A to the property input screen by the input unit 13. When the user performs the property information saving operation by the input unit 13, the scenario execution device 1 associates the user operation module of the process A represented by the process symbol 215-1 with the user operation module of the process A, and the process A input to the property input screen. Store property information.

Similarly, when the user instructs the property input of the process symbol 215-3 by the input unit 13, the scenario execution device 1 displays the property input screen of the user operation module of the process B. The user inputs the setting value of the property information of the process B to the property input screen by the input unit 13. When the user performs the property information saving operation by the input unit 13, the scenario execution device 1 associates the user operation module of the process B represented by the process symbol 215-3 with the user operation module of the process B represented by the process symbol 215-3, and causes the process B input to the property input screen. Store property information.

The property information of the present embodiment includes identification information of each of the one or more variables, the value of each variable, and the description of the variables. As the variable identification information, for example, a combination of the group name to which the variable belongs and the variable name is used. The property information may further include information in the data format of the variable. The same variable can be used for the property information of multiple user operation modules. For example, the variables used for the property information of the user operation module of process A may be used for the property information of the user operation module of process B.

When the user instructs the property input of the processing symbol 215-2 by the input unit 13, the scenario execution device 1 displays the property input screen 250 shown in FIG. 10 on the display unit 14. The property input screen 250 includes a target application input field 251, a connection setting input field 252, and an utterance setting area 253. The target application input field 251 specifies a network service application used for notifying the user to the terminal device 3, similarly to the target application input field 221 (FIG. 7). In the connection setting input field 252, similarly to the connection setting input field 222 (FIG. 7), the transmission destination of the notification using the application selected in the target application input field 251 is input by text.

The utterance setting area 253 has a welcome message input field 254, a close message input field 255, a setting property information input area 256, and a notification interval selection button 257. The welcome message is described in text in the welcome message input field 254. The welcome message is the first message notified to the user when the property setting module is started. The close message is described in text in the close message input field 255. The close message is a message to be notified when the reception of the instruction from the user is finished.

In the setting property information input area 256, among the variables of the property information, the identification information of the variable for which the user is requested to set the value and the answer method of the setting value of the variable are input. The setting property information input area 256 includes a group name input field 2561, a variable name input field 2562, a description input field 2563, a type input field 2564, and a display input field 2565. The group name, variable name, and description of the variables used in the property information of one or more processing modules in the scenario are set in the group name input field 2561, the variable name input field 2562, and the description input field 2563, respectively. The scenario execution device 1 may display a list of all variables used in the property information of each processing module in the scenario, and the user may select a variable from the display by the input unit 13. The scenario execution device 1 inputs the group name, variable name, and description of the selected variable into the group name input field 2561, the variable name input field 2562, and the description input field 2563, respectively.

The type input field 2564 selects the type of the answer method of the set value from the pull-down menu. The types are, for example, dates, buttons, texts, numbers, and the like. The display input field 2565 sets the display name to be displayed on the button when the type is the button. This display name is used as a variable setting value. The notification interval selection button 257 is a button for selecting a time interval for resending the notification when the response notified to the user cannot be received.

When the user performs a save operation such as clicking the OK button 258 on the property input screen 250 by the input unit 13, the scenario execution device 1 displays the property input screen 250 in association with the property setting module represented by the processing symbol 215-2. Stores the property information of the entered setting value. The scenario execution device 1 may set the type of utterance indicating that there is a user response or the type of utterance indicating notification and property setting in the property information of the property setting module. Further, the scenario execution device 1 may update the property information in association with the response reception and set the subsequent processing information indicating the continuation of the scenario execution in the property information. That is, the next processing module of the property setting module is specified as the processing module to be executed after receiving the response.

FIG. 11 is a diagram showing an example of a notification screen 410 displayed on the display unit 33 of the terminal device 3. The terminal device 3 receives a notification from the conversion device 5 using the implemented messenger service application, and displays the notification screen 410. The notification content is based on the content set on the property input screen 250, and the conversion device 5 receives this setting content from the scenario execution device 1. The message 421 first transmitted from the conversion device 5 is a display of the welcome message input in the welcome message input field 254.

The messages 422 to 428 are based on the contents input in the setting property information input area 256. The message 422 transmitted from the conversion device 5 is a message requesting the setting value of the variable name "start date" first input in the setting property information. The message 423 transmitted from the terminal device 3 is a set value of the start date input by the user to the terminal device 3. The message 424 transmitted from the conversion device 5 is a message requesting the setting value of the variable name “end date” input second in the setting property information. The message 425 transmitted from the terminal device 3 is a set value of the end date input by the user to the terminal device 3.

The message 426 transmitted from the conversion device 5 is a message requesting the setting value of the variable name “category” input third in the setting property information. Since the "button" is set in the variable type input field 2564 of the variable name "category", the conversion device 5 displays the buttons 427-1 to 427-4 for selecting the set value. The data is transmitted to the terminal device 3. Buttons 427-1 to 427-4 display "fruits and vegetables", "fresh fish", "meat", and "all" set in the display input field 2565 as button names, respectively. When the user selects any of the buttons 427-1 to 427-4 displayed on the terminal device 3, the terminal device 3 transmits the button name of the selected button as a message 428 to the conversion device 5.

When the conversion device 5 receives the setting values of all the variables set in the setting property information input area 256, the conversion device 5 displays the setting values of each variable and requests confirmation whether the setting contents are correct, and the setting contents are displayed. Display data for displaying buttons 430-1 and 430-2 for inputting a response as to whether or not they are correct is transmitted. When the user selects any of the buttons 430-1 and 430-2 displayed on the terminal device 3, the terminal device 3 transmits the button name of the selected button as a message 431 to the conversion device 5. The conversion device 5 receives a response in which the setting contents are set to be correct, and transmits a message 432 to the terminal device 3. Message 432 is a display of the close message entered in the close message input field 255.

In the above, two types of user interface modules, a user notification module and a property setting module, are used, but the user notification module and the property setting module may be used as one user interface module. In this case, the property input screen of the user interface module can use, for example, a property input screen 220 shown in FIG. 7 with a button for selecting a notification and a property setting added as the type of utterance. When the user selects the notification and the property setting, the scenario execution device 1 displays the utterance setting area 253 instead of the utterance setting area 224 of the property input screen 220.

FIG. 12 is a flow chart showing a scenario generation process in the scenario execution device 1. The creation information receiving unit 161 of the scenario execution device 1 determines whether or not the addition of the processing module has been input (step S110). For example, the user selects an additional processing module from the list of processing modules displayed in the library display area 201 of the scenario creation screen by the input unit 13 such as a mouse, and drags it to the scenario creation area 202. In this case, the creation information receiving unit 161 receives the information of the selected additional processing module and the information of the drag end position from the input unit 13, and determines that the addition of the processing module has been input (step S110: YES). ). The screen display control unit 162 additionally displays a processing symbol for displaying the processing module name of the additional processing module at the end position of the drag (step S115). The scenario creation unit 16 returns to the process of step S110.

On the other hand, when it is determined that the addition of the processing module has not been input (step S110: NO), the creation information receiving unit 161 determines whether or not the property setting instruction has been input (step S120). For example, the user double-clicks the processing symbol representing the processing module for which the property is set by the input unit 13. The processing module whose property is to be set is described as the processing module to be set. The creation information receiving unit 161 receives the information of the processing symbol for which the property setting instruction has been operated from the input unit 13, and determines that the property setting instruction has been input (step S120: YES). The screen display control unit 162 displays the property input screen of the setting target processing module represented by the processing symbol for which the property setting instruction has been given (step S125). The user inputs the setting values of various variables used for the property information of the processing module to be set in the property input screen, and operates the OK button (step S130). The creation information receiving unit 161 stores the setting target processing module and the property information including the set values of various input variables in association with each other. The scenario creation unit 16 returns to the process of step S110.

When it is determined in step S120 that the property setting instruction has not been input (step S120: NO), the creation information receiving unit 161 determines whether or not the scenario creation end has been input (step S135). When the creation information receiving unit 161 determines that the scenario creation end has not been input (step S135: NO), the creation information receiving unit 161 performs a process according to the user operation (step S140), and returns to the process of step S110. On the other hand, when the creation information receiving unit 161 determines that the scenario creation end has been input (step S135: YES), the creation information receiving unit 161 instructs the scenario registration unit 163 to perform the process. The scenario registration unit 163 generates a scenario file describing the created scenario, writes it to the storage unit 12, and ends the scenario generation flow (step S145).

In the above, the additional processing module is selected from the list of processing modules displayed in the library display area 201, but the user operation module can be arbitrarily generated. For example, the creation information receiving unit 161 records the instruction given by the input unit 13 from the time when the user inputs the operation recording start instruction by the input unit 13 to the time when the operation recording end instruction is input, and executes the recorded content. Generate a processing module. The user can select this generated processing module as an additional processing module.

13 and 14 are flow charts showing the scenario execution process in the scenario execution device 1. The scenario execution management unit 17 of the scenario execution device 1 detects that the information of the scenario to be executed and the execution start have been input by the input unit 13 (step S210). Alternatively, the scenario execution management unit 17 detects that the execution timing of the scenario to be executed indicated by the execution schedule registered in advance has come. The reading unit 181 reads a scenario file in which the scenario to be executed is described from the storage unit 12 (step S215). The reading unit 181 sets the first processing module described in the scenario file as the execution target module (step S220).

The reading unit 181 reads the information of the execution target module from the scenario file (step S225). The information of the execution target module includes the type of the execution target module, the setting value of each variable of the property information of the execution target module, and the processing module in the next execution order of the execution target module. The determination unit 182 determines whether the type of the processing target module is a user operation module or a user interface module (step S230).

When the determination unit 182 determines that the type of the processing target module is the user operation module (step S230: user operation module), the determination unit 182 instructs the operation control unit 183 to perform the process. The operation control unit 183 controls the input unit 13 so as to perform the user operation indicated by the processing target module (step S235).

The reading unit 181 determines whether or not the next execution order of the processing target module is the end node (step S240). When the reading unit 181 determines that the next execution order is the end node (step S240: YES), the reading unit 181 ends the execution of the scenario (step S245). On the other hand, when the reading unit 181 determines that the next execution order is not the end node (step S240: NO), the processing module in the next execution order is set as a new execution target module (step S250), and the process from step S225 is started. Repeat the process.

When the determination unit 182 determines in step S230 that the type of the processing target module is the user interface module (step S230: user interface module), the determination unit 182 instructs the notification unit 184 to perform the process. The notification unit 184 generates a notification transmission request in which the notification to the user is set according to the set value indicated by the property information of the execution target module (step S255). The notification unit 184 transmits the generated notification transmission request to the conversion device 5 (step S260). The notification unit 184 determines whether or not only notification is set in the property information of the user interface module (step S265). When the notification unit 184 determines that only the notification is set (step S265: YES), the notification unit 184 proceeds to the process of step S240. In step S240, the reading unit 181 determines whether or not the next execution order is the end node.

On the other hand, the notification unit 184 determines that only the notification is not set when the property information has a user response, the notification and the property setting are set, or the processing target module is the property setting module (). Step S265: NO). In this case, the notification unit 184 activates the timer for the time indicated by the notification interval set in the property information (step S270). When the notification unit 184 does not receive the response (step S275: NO), the notification unit 184 determines whether or not the timer has detected the expiration (step S280). When the notification unit 184 determines that the expiration of the timer has not been detected (step S280: NO), the process from step S275 is repeated.

When the notification unit 184 receives the response (step S275: YES), the notification unit 184 executes the process of FIG. The notification unit 184 resets the timer and outputs a response to the execution control unit 185 (step S310). The execution control unit 185 reads the subsequent processing information corresponding to the instruction content indicated by the received response from the property information of the user interface module which is the processing target module. The execution control unit 185 determines the type of the read subsequent processing information (step S315).

When the execution control unit 185 determines that the type of subsequent processing information is on hold, the execution control unit 185 instructs the notification unit 184 to perform the processing. The notification unit 184 performs the process from step S270 in FIG. When the execution control unit 185 determines that the type of subsequent processing information is the execution of the specified processing module, the execution control unit 185 sets the designated processing module as the processing module in the next execution order (step S320). The reading unit 181 performs the process from step S225.

When the execution control unit 185 sets a value in a variable and determines that the execution of the specified processing module is the execution of the subsequent processing information, the value of the variable obtained by executing the scenario is set in the response. After updating to the value of the variable (step S325), the process of step S320 is performed.

When the type of subsequent processing information indicates the execution of the specified scenario, the execution control unit 185 ends the execution of the currently executing scenario (step S330), and outputs a start instruction of the specified scenario to the scenario execution management unit 17. (Step S335). The scenario execution management unit 17 newly starts the scenario execution process shown in FIGS. 13 and 14 for the designated scenario.

When the type of subsequent processing information indicates the end of execution of the scenario, the execution control unit 185 ends the execution of the currently executing scenario (step S340).

When the type of subsequent processing information updates the property information to indicate continuation of scenario execution, the execution control unit 185 performs the process of step S345. Note that the execution control unit 185 may consider that the processing target module is a property setting module as subsequent processing information that updates the property information and indicates continuation of scenario execution. The execution control unit 185 updates the setting value of the variable included in the property information associated with the processing module in the scenario according to the setting value of the variable of the property information set in the response (step S345). The execution control unit 185 performs the process from step S240 (or step S250) of FIG.

When the notification unit 184 determines that the timer has expired in step S280 (step S280: YES), the number of times the notification transmission request is transmitted reaches a predetermined upper limit, or the first notification transmission request is made. If a predetermined time has elapsed from the transmission of, arbitrary error processing such as ending the scenario may be performed.

FIG. 15 is a sequence diagram of the scenario execution system 100 when the user interface module is executed. First, the processing at the time of executing the user notification module will be described. The notification unit 184 of the scenario execution device 1 generates a notification transmission request according to the value set in the property information of the user notification module (step S410). The notification transmission request includes the target application, the notification destination, the type of utterance, the message to be notified to the user, the variable name and value of the variable to be notified to the user, the button number and the button display of the user response button. The name and the variable name of the variable set by the user are set. For example, the button numbers are assigned in the order in which the button display names are input. A part of the message to be notified to the user, the variable name and value of the variable to be notified to the user, the button number and button display name of the user response button, and the variable name of the variable set by the user are in the notification transmission request. It may be set. The notification unit 184 sets the address information of its own device as the transmission source of the notification transmission request. The communication unit 11 transmits the notification transmission request generated by the notification unit 184 to the conversion device 5 (step S415).

The communication unit 51 of the conversion device 5 outputs the received notification transmission request to the conversion unit 53. The conversion unit 53 reads the conversion rule corresponding to the network service represented by the target application from the storage unit 52. The conversion unit 53 converts the notification transmission request received from the scenario execution device 1 according to the read conversion rule, and generates a user notification addressed to the terminal device 3 (step S420). The user notification is set by the user, the destination of the notification, the message to be notified to the user, the variable name and value of the variable to be notified to the user, the button display data for displaying the button of each button display name, and the user. Contains the variable name of the variable to be used. When the network service is e-mail, instead of the button display data, a text associated with the button number and the button display name is set in the user notification. The communication unit 51 of the conversion device 5 transmits the generated user notification to the service providing device 7 (step S425).

The service providing device 7 transmits the received user notification to the terminal device 3 indicated by the destination of the notification (step S430). The control unit 32 of the user's terminal device 3 displays the user notification received by the communication unit 31 on the display unit 33 (step S435). For example, the terminal device 3 displays the notification screen 400 shown in FIG. 7. The user confirms the content to be displayed, and when a response is required, selects one of the displayed buttons by the input unit 34 (step S440). The control unit 32 transmits a response in which the button number or the button display name of the selected button is set as the instruction content to the service providing device 7 (step S445). When it is necessary to set the value of the variable, the control unit 32 further transmits a response in which the value of the variable input by the user by the input unit 34 is set. The service providing device 7 transmits the response received from the terminal device 3 to the conversion device 5 (step S450). In the case of e-mail, the user returns an e-mail in which the button number or the value of the variable is described in the body or subject as the instruction content. The service providing device 7 transmits the e-mail returned from the terminal device 3 to the conversion device 5 as a response to the notification.

The communication unit 51 of the conversion device 5 receives a response from the service providing device 7. The conversion unit 53 of the conversion device 5 discards the response when the utterance type of the notification transmission request indicates only notification. When the utterance type of the notification transmission request indicates a notification and a user response, the conversion unit 53 of the conversion device 5 reads the conversion rule according to the type of network service used in the received response from the storage unit 52. The conversion unit 53 converts the data format of the response according to the conversion rule (step S455), and transmits the converted response to the scenario execution device 1 (step S460). The notification unit 184 of the scenario execution device 1 acquires the instruction content from the response received by the communication unit 31 (step S465).

According to the above, for example, the conversion device 5 transmits a notification to the terminal device 3 by the chat interface based on the notification transmission request received from the scenario execution device 1. The terminal device 3 displays the notification received by the chat interface, and the user confirms the display and responds to the instruction. The instruction content transmitted by the chat interface is returned to the conversion device 5, and the conversion device 5 transmits the instruction content to the scenario execution device 1. The scenario execution device 1 executes subsequent processing according to the received instruction content.

When a telephone is selected as the target application, the conversion unit 53 of the conversion device 5 performs conversion using the voice synthesizer and the voice recognition device. The conversion unit 53 embeds the message set in the notification transmission request, the variable name and value of the variable to be notified to the user, and each button number or button display name at a predetermined position in the fixed phrase according to the conversion rule. Generate a text message. For example, assume that the button display name of the button number "1" is "execute scenario B" and the button display name of the button number "2" is "end scenario A". The conversion unit 53 displays the button number and the button in the fixed phrase, such as "Please press <1> when <execute scenario B> and <2> when <end scenario A>." Generate text data by embedding the name in the position surrounded by <>.

The conversion unit 53 calls the telephone number of the terminal device 3 set in the notification transmission request. When the terminal device 3 responds and the conversion device 5 and the terminal device 3 are in a call state, the conversion unit 53 synthesizes a text message by voice and outputs it. When the user hears the message, the terminal device 3 utters the instruction content or presses the number button indicating the instruction content. The conversion unit 53 of the conversion device 5 recognizes the user's utterance content or push button sound by voice and converts it into a text instruction content, or receives the number of the pressed button as a signal.

The process S1 from step S420 to step S435 in FIG. 15 and the process S2 from step S440 to step S450 may be repeated as necessary. For example, the content of the notification screen 400 may be transmitted in a plurality of times.

Next, the processing at the time of executing the property setting module will be described. As in the case of executing the user notification module, the scenario execution device 1 transmits / receives data to / from the conversion device 5 via the communication unit 11, and the conversion device 5 transmits / receives data to / from the scenario execution device 1 and the service providing device 7 via the communication unit 51. And the data is transmitted and received, and the terminal device 3 transmits and receives data to and from the service providing device 7 via the communication unit 31, but the description of these processes will be omitted below.

The notification unit 184 of the scenario execution device 1 generates a notification transmission request in which the property information of the property setting module is set (step S410). The notification transmission request includes the target application, the notification destination, the type of utterance indicating the notification and the property setting, the welcome message and the close message, and the number and variable of each variable input in the setting property information input area 256. The name, type and display are set. The numbers are assigned in the order of input to the setting property information input area 256. The notification unit 184 sets the address information of its own device as the source of the notification transmission request and transmits it to the conversion device 5 (step S415).

The conversion unit 53 of the conversion device 5 reads the target application from the notification transmission request received from the scenario execution device 1, and reads the conversion rule corresponding to the network service represented by the read target application from the storage unit 52. The conversion unit 53 converts the notification transmission request received from the scenario execution device 1 according to the read conversion rule, and generates a user notification addressed to the terminal device 3 (step S420). First, the conversion unit 53 generates a user notification addressed to the terminal device 3 in which the welcome message is set, and transmits the user notification to the service providing device 7 (step S425). The service providing device 7 transmits the received user notification to the terminal device 3 indicated by the destination of the user notification (step S430). The control unit 32 of the terminal device 3 displays the user notification received from the service providing device 7 on the display unit 33 (step S435). For example, the message 421 (FIG. 11) is displayed on the display unit 33.

Next, the conversion unit 53 of the conversion device 5 displays the variable name of the variable number 1 and generates a user notification addressed to the terminal device 3 in which a message requesting transmission of the set value of the variable is set (step S420). ), Sent to the service providing device 7 (step S425). The service providing device 7 transmits the received user notification to the terminal device 3 indicated by the destination of the user notification (step S430). The control unit 32 of the terminal device 3 displays the user notification received from the service providing device 7 on the display unit 33 (step S435). For example, the message 422 (FIG. 11) is displayed on the display unit 33.

The user inputs a set value according to the content displayed on the display unit 33 and performs a transmission operation (step S440). The control unit 32 transmits a response in which the input set value is set (step S445). The service providing device 7 transmits the response received from the terminal device 3 to the conversion device 5 (step S450).

Upon receiving the response, the conversion unit 53 of the conversion device 5 determines whether or not there is a variable to be set included in the notification transmission request that has not received the set value. When the conversion unit 53 determines that there is a variable for which the set value has not been received, the conversion unit 53 generates a user notification similar to the variable of the number 1 for the variable of the next number (step S420) and transmits the user notification to the service providing device 7. (Step S425).

When the type and display indicating the button are added to the variable, the conversion unit 53 generates button display data for displaying the button with the text indicated by each display as the button name. The conversion unit 53 adds the generated button display data to the user notification and transmits the data. As a result, for example, the control unit 32 of the terminal device 3 displays the message 426 and the buttons 427-1 to 427-4 (FIG. 11) on the display unit 33. When the user selects one of the buttons (step S440), the control unit 32 transmits a response in which the display name of the selected button or the identification information of the button is set (step S445).

When the conversion unit 53 of the conversion device 5 receives a response from the service providing device 7 and determines that it has received the setting values of all the variables to be set included in the notification transmission request, the user for confirming the setting values. Generate a notification (step S420). For example, the conversion unit 53 displays the set value of each received variable, generates a user notification addressed to the terminal device 3 including a message requesting confirmation of whether the set content is correct, and transmits the user notification to the service providing device 7. (Step S425). The conversion unit 53 may add button display data for displaying a button for inputting a response as to whether or not the setting content is correct to the user notification and transmit the data. The service providing device 7 transmits the received user notification to the terminal device 3 indicated by the destination of the notification (step S430). The control unit 32 of the user terminal device 3 displays the user notification received from the service providing device 7 on the display unit 33 (step S435). For example, the message 424 and the buttons 430-1 and 430-2 (FIG. 11) are displayed on the display unit 33.

The user inputs the confirmation result to the terminal device 3 according to the content displayed on the display unit 33 (step S440). The control unit 32 transmits a response in which the input confirmation result is set (step S445). For example, the confirmation result is information that identifies the button selected by the user. The service providing device 7 transmits the response received from the terminal device 3 to the conversion device 5 (step S450).

When the conversion unit 53 of the conversion device 5 receives the response in which the confirmation result indicating that the set value is correct is set, the conversion unit 53 generates a user notification addressed to the terminal device 3 for which the close message is set (step S420), and the service providing device. It is transmitted to 7 (step S425). The service providing device 7 transmits the received user notification to the terminal device 3 indicated by the destination of the notification (step S430). The control unit 32 of the user terminal device 3 displays the user notification received from the service providing device 7 on the display unit 33 (step S435). For example, message 432 (FIG. 11) is displayed on the display unit 33.

Further, the conversion unit 53 of the conversion device 5 converts the data format according to the conversion rule to generate a response in which the set value of each variable acquired from the response received from the service providing device 7 is set (step S455). , Sent to the scenario execution device 1 (step S460). The notification unit 184 of the scenario execution device 1 acquires the set value of each variable as an instruction content from the received response (step S465).

According to the above, for example, the conversion device 5 receives the set value of the property information from the terminal device 3 by the chat interface based on the notification transmission request received from the scenario execution device 1. The conversion device 5 transmits the set value of the property information received from the terminal device 3 to the scenario execution device 1. The scenario execution device 1 executes the scenario by using the set value of the received property information.

In the case of e-mail, the conversion unit 53 of the conversion device 5 includes a welcome message read from the notification transmission request, a list of variable names of each variable, and if the variable names have buttons and displays, the same. Set up an email that includes a display as a user notification. The user returns an e-mail describing the value of each variable from the terminal device 3. The service providing device 7 transmits the e-mail returned from the terminal device 3 to the conversion device 5 as a response to the notification.

When a telephone is selected as the target application, the conversion unit 53 of the conversion device 5 calls the telephone number of the terminal device 3 set in the notification transmission request. When the terminal device 3 responds and the conversion device 5 and the terminal device 3 are in a call state, the conversion unit 53 synthesizes the contents of the above-mentioned user notification by voice and outputs it. When the user hears the message, the terminal device 3 utters the above-mentioned set value. The conversion unit 53 of the conversion device 5 recognizes the user's utterance content by voice and obtains a set value.

In the scenario execution system 100, the scenario execution device 1 executes the user notification module to execute the process for receiving the variable setting value from the user's terminal device 3, and the scenario execution device 1 executes the property setting module. By doing so, the same processing as when receiving the setting value of each variable of the property information may be performed.

Further, the scenario execution device 1 and the terminal device 3 may be the same device. When the scenario execution device 1 and the terminal device 3 are the same device, the scenario execution device 1 functions as a conversion device 5 and a service providing device related to the chat service, except for the function of transmitting and receiving data between the devices via the network 9. It may have the function of 7. In this case, the scenario execution device 1 can notify the user and receive the response from the user to the notification without going through the network 9. Further, when the scenario execution device 1 and the terminal device 3 are the same device, and the scenario execution device 1 has the function of the conversion unit 53 of the conversion device 5 using the voice synthesizer and the voice recognition device, the scenario execution device 1 is executed. The device 1 can perform a voice notification to the user and a response by the user's utterance without going through the network 9.

According to the embodiment described above, the scenario execution device can receive a user's instruction regarding the execution of the scenario during the execution of the scenario of the automation tool, and can perform the subsequent processing according to the instruction.

For example, by setting the execution order of the user notification module to just before the end node of the scenario, or by arranging the user notification module on the route when an error occurs in the scenario, the user can complete the execution of the scenario or generate an error. Can be notified to. For example, a user can efficiently execute a business by having a scenario execution device execute a scenario while he / she is doing business at another place or while he / she is out on a business trip. However, in the past, in order to know that the execution of the currently executing scenario was completed in order to execute the next scenario, or that the execution of the scenario was interrupted for some reason, the user actually checked the scenario execution device. I had to do it. Therefore, a user who is doing business in another place frequently goes to check the scenario execution device or monitors in front of the scenario execution device. In addition, the user may not be able to know until returning to work that the scenario instructed to be executed before the business trip was interrupted due to an error.

According to the scenario execution device of the present embodiment, it is possible to notify the user that the scenario execution has been completed or that the scenario has been interrupted for some reason during the execution of the scenario. Therefore, the user does not need to perform monitoring to frequently check the scenario execution status of the scenario execution device. In addition, the user who receives the notification can remotely control the operation of the scenario execution device by instructing the scenario execution device to perform the work. Therefore, the user can have the scenario execution device automatically perform the work while performing his / her own work without being restricted by time and place, so that the work efficiency can be improved more effectively than before. It will be possible.

Further, even in the same scenario, the user may change the property information before causing the scenario execution device to execute the scenario. Conventionally, the setting value of the property information is directly input to the property input screen displayed by the scenario execution device, or the setting value input to a text file or the like at the time of executing the scenario is read by the scenario execution device. In this case, the user needs to consciously change the property information setting, and it is difficult to intuitively change the property information and execute the scenario. According to the scenario execution device of the present embodiment, by arranging the property setting module at the beginning of the scenario, the chat window is displayed on the terminal device of the user in the local environment at the time of scenario execution, and the property is confirmed interactively. It is also possible to change the information settings. In this way, property information can be set while checking in a user-interactive format, so even users with low RPA skills can intuitively set property information and reduce setting errors in scenarios. Can be executed.

In the above, the user uses the scenario execution device 1 to generate the scenario, but the user may create the scenario using a scenario creation device (information processing device) such as a PC different from the scenario execution device 1. .. In this case, the scenario creation device may include an input unit 13, a display unit 14, a scenario creation unit 16, and other functional units such as a communication unit 11 and a scenario execution management unit 17.

The functions of the scenario execution device 1, the terminal device 3, the conversion device 5, and the service providing device 7 in the above-described embodiment may be realized by a computer. In that case, the program for realizing this function may be recorded on a computer-readable recording medium, and the program recorded on the recording medium may be read by the computer system and executed. The term "computer system" as used herein includes hardware such as an OS and peripheral devices. The "computer-readable recording medium" refers to a portable medium such as a flexible disk, a magneto-optical disk, a ROM, or a CD-ROM, or a storage device such as a hard disk built in a computer system. Further, a "computer-readable recording medium" is a communication line for transmitting a program via a network such as the Internet or a communication line such as a telephone line, and dynamically holds the program for a short period of time. It may also include a program that holds a program for a certain period of time, such as a volatile memory inside a computer system that serves as a server or a client in that case. Further, the above-mentioned program may be a program for realizing a part of the above-mentioned functions, and may be a program for realizing the above-mentioned functions in combination with a program already recorded in the computer system.

According to the embodiment described above, the scenario execution device includes an input unit, a function execution unit, a storage unit, a reading unit, a determination unit, an operation control unit, a notification unit, and an execution control unit. .. The input unit inputs user operations. The function execution unit executes a predetermined function according to a user operation by the input unit. The function execution unit is, for example, a function A execution unit 19a, a function B execution unit 19b, and a function C execution unit 19c. The storage unit stores one or more processing modules that are user operation modules or user interface modules, and a scenario file that indicates the execution order of those processing modules. The user operation module represents a user operation for the function execution unit. The user interface module represents the use of an interface that notifies the user and receives a response from the user. The reading unit reads the processing modules from the execution target scenario file in the order of execution. The determination unit determines whether the processing module read by the reading unit is a user operation module or a user interface module. When the determination unit determines that the user operation module is the operation control unit, the operation control unit controls the input unit so as to perform the user operation indicated by the user operation module. When the determination unit determines that the user interface module is used, the notification unit notifies the user indicated by the user interface module. The notification may include the value of a variable obtained before the transmission of the notification by executing the scenario file to be executed. The execution control unit continues or ends the execution of the scenario file or executes another scenario file based on the response received in response to the notification by the notification unit.

The user interface module may include information in which the instruction content is associated with the continuation or termination of the execution of the scenario file or the subsequent processing information indicating the execution of another scenario file. The execution control unit continues or ends the execution of the scenario file or executes another scenario file according to the subsequent processing information set in the user interface module in response to the instruction content indicated by the received response. The subsequent processing information may include information on the processing module to be executed next in the case of continuing the execution of the scenario file.

When the user interface module is set with information that the response is not received, such as notification, the execution control unit continues the execution of the scenario file after the notification unit notifies.

The response may include the set value of the variable. The execution control unit updates the value of the variable obtained before sending the notification by executing the scenario file to the setting value of the variable included in the received response, and uses the updated variable to execute the scenario to be executed. Continue executing the file.

In addition, the response may include a setting value of property information representing a setting related to the processing module. When the execution control unit continues to execute the scenario file to be executed, the execution control unit executes the processing module included in the scenario file by using the setting value of the property information included in the received response.

The notification by the notification unit is transmitted to the user's terminal device after the data format is converted by the conversion device. The execution control unit receives the response returned from the terminal device and whose data format has been converted by the conversion device. The conversion device transmits a notification to the terminal device and receives a response from the terminal device by, for example, chatting, e-mail, or telephone.

Although the embodiments of the present invention have been described in detail with reference to the drawings, the specific configuration is not limited to this embodiment, and includes designs and the like within a range that does not deviate from the gist of the present invention.

1 ... Scenario execution device, 3 ... Terminal device, 5 ... Conversion device, 7 ... Service providing device, 9 ... Network, 11 ... Communication unit, 12 ... Storage unit, 13 ... Input unit, 14 ... Display unit, 15 ... Processing unit , 16 ... Scenario creation unit, 17 ... Scenario execution management unit, 18 ... Scenario execution unit, 19a ... Function A execution unit, 19b ... Function B execution unit, 19c ... Function C execution unit, 31 ... Communication unit, 32 ... Control unit , 33 ... Display unit, 34 ... Input unit, 51 ... Communication unit, 52 ... Storage unit, 53 ... Conversion unit, 100 ... Scenario execution system, 161 ... Creation information receiving unit, 162 ... Screen display control unit, 163 ... Scenario registration Unit, 181 ... Reading unit, 182 ... Judgment unit, 183 ... Operation control unit, 184 ... Notification unit, 185 ... Execution control unit

Claims (11)

Input section for inputting user operations and
A function execution unit that executes a predetermined function according to a user operation by the input unit, and a function execution unit.
One or more processing modules that are user operation modules that represent user operations on the function execution unit or user interface modules that represent the use of interfaces that notify users and receive responses to the notifications, and execution of the processing modules. A storage unit that stores scenario files that indicate the order,
A reading unit that reads the processing module from the scenario file to be executed in the order of execution, and
A determination unit that determines whether the processing module read by the reading unit is the user operation module or the user interface module, and
When it is determined that the determination unit is the user operation module, the operation control unit that controls the input unit to perform the user operation indicated by the user operation module, and the operation control unit.
When the determination unit determines that the user interface module is the user interface module, the notification unit that notifies the user indicated by the user interface module and the notification unit.
An execution control unit that continues or terminates the execution of the scenario file or executes another scenario file based on the response received in response to the notification by the notification unit.
Scenario execution device. The user interface module includes information in which the instruction content is associated with the continuation or termination of the execution of the scenario file or the subsequent processing information indicating the execution of another scenario file.
The execution control unit continues or ends the execution of the scenario file or executes the other scenario file according to the subsequent processing information set in the user interface module in response to the instruction content indicated by the received response. Do, do
The scenario execution device according to claim 1. The subsequent processing information includes information on the processing module to be executed next in the case of continuation of execution of the scenario file.
The scenario execution device according to claim 2. When the user interface module is set with information that the user interface module does not receive a response, the execution control unit continues to execute the scenario file to be executed after the notification unit gives the notification.
The scenario execution device according to claim 3. The response contains the set value of the variable.
The execution control unit updates the value of the variable obtained before the transmission of the notification by executing the scenario file to the set value of the variable included in the response, and executes using the updated variable. Continue execution of the target scenario file,
The scenario execution device according to any one of claims 1 to 3. The response includes a setting value of property information representing a setting related to the processing module.
When the execution control unit continues the execution of the scenario file to be executed, the execution control unit executes the processing module included in the scenario file by using the set value of the property information included in the response.
The scenario execution device according to claim 1 or 2. The notification includes the value of a variable obtained before the transmission of the notification by executing the scenario file to be executed.
The scenario execution device according to any one of claims 1 to 6. The notification by the notification unit is transmitted to the terminal device of the user after the data format is converted by the conversion device.
The execution control unit receives the response returned from the terminal device and whose data format has been converted by the conversion device.
The scenario execution device according to any one of claims 1 to 7. The conversion device transmits the notification to the terminal device and receives the response from the terminal device by chat, e-mail, or telephone.
The scenario execution device according to claim 8. It is a scenario execution method executed by the scenario execution device.
A function execution step that executes a predetermined function according to a user operation by the input unit,
It is a user operation module that represents a user operation for executing the function by the function execution step, or a user interface module that represents the use of an interface between notifying the user and receiving a response to the notification. A read step of reading the processing modules in the execution order from the execution target scenario file indicating the above processing modules and the execution order of the processing modules.
A determination step for determining whether the processing module read in the read step is the user operation module or the user interface module, and a determination step.
When it is determined in the determination step that the user operation module is used, the operation control step for controlling the input unit to perform the user operation indicated by the user operation module, and
When it is determined that the user interface module is the user interface module in the determination step, the notification step for notifying the user indicated by the user interface module, and the notification step.
An execution control step for continuing or terminating the execution of the scenario file or executing another scenario file based on the response received in response to the notification by the notification step.
Scenario execution method with. A program for causing a computer to function as the scenario execution device according to any one of claims 1 to 9.

Images