Information processing device and program

Abstract

An information processing device according to one aspect comprises a scenario retaining unit, a storage unit, a scenario modification unit, and a scenario execution unit. The scenario retaining unit reads operation information which defines the content of an automatic operation and which includes operation target information that specifies an operation target to be subjected to the automatic operation. The storage unit stores a database in which first operation target information and second operation target information differing from the first operation target information are associated with each other. When first operation information including the first operation target information has been read, the scenario modification unit modifies the first operation target information in the first operation information to the second operation target information on the basis of the database. The scenario execution unit executes a first automatic operation on the basis of the modified first operation information.

Description

Information processing device and program

[0001] The embodiments relate to an information processing device and a program.

[0002] As part of the promotion of digital transformation (DX), robotic process automation (RPA) technology is being utilized. Most RPA tools are no-code or low-code. For this reason, unlike macro functions, RPA is known as a tool that can relatively easily streamline routine tasks such as office automation (OA) work, even if you do not have programming knowledge.

[0003] "WinActorTM RPA is a Japanese-made RPA tool that realizes business improvement," https: / / winactor.biz / rpa / rpa.html

[0004] Each RPA product has its own unique way of expressing the operation procedures (scenarios) to be automated. Therefore, creating and modifying scenarios is relatively easy, but it does require the acquisition of a certain level of skill.

[0005] When the target of RPA automation changes due to an update to an application used in a business system, the scenario must be revised. If the change in the target of automation is local, such as a change in screen design, major revisions to the scenario are often unnecessary. However, even in such cases, scenario revisions can be difficult unless the person in question has the skills to revise scenarios specific to RPA.

[0006] The present invention has been made in view of the above circumstances, and an object of the present invention is to provide an information processing device and a program that allow easy modification of a scenario.

[0007] An information processing device according to one aspect includes a scenario holding unit, a memory unit, a scenario correction unit, and a scenario execution unit. The scenario holding unit reads operation information defining the content of an automatic operation, the operation information including operation target information that identifies an operation target to be subjected to the automatic operation. The memory unit stores a database that associates first operation target information with second operation target information that differs from the first operation target information. When first operation information including the first operation target information is read, the scenario correction unit corrects the first operation target information in the first operation information to the second operation target information based on the database. The scenario execution unit executes a first automatic operation based on the corrected first operation information.

[0008] According to the embodiment, it is possible to provide an information processing device and a program that can easily modify a scenario.

[0009] FIG. 1 is a block diagram showing an example of the configuration of a business system device including an information processing device according to an embodiment. FIG. 2 is a block diagram showing an example of the hardware configuration of the information processing device according to an embodiment. FIG. 3 is a block diagram showing an example of the functional configuration of the information processing device according to an embodiment. FIG. 4 is a diagram showing an example of the data structure of a scenario file stored in the information processing device according to an embodiment. FIG. 5 is a diagram showing an example of the data structure of an update history DB stored in the information processing device according to an embodiment. FIG. 6 is a flowchart showing an example of scenario execution processing in the information processing device according to an embodiment. FIG. 7 is a flowchart showing an example of operation information correction processing in the information processing device according to an embodiment. FIG. 8 is a flowchart showing an example of DB update processing in the information processing device according to an embodiment. FIG. 9 is a flowchart showing an example of DB update processing in the information processing device according to a first modified example. FIG. 10 is a block diagram showing an example of the functional configuration of the information processing device according to a second modified example.

[0010] Hereinafter, embodiments will be described with reference to the drawings. In the following description, components having the same functions and configurations will be given the same reference numerals.

[0011] 1. Embodiment First, an information processing device according to an embodiment will be described.

[0012] 1.1 Configuration 1.1.1 Business System FIG. 1 is a block diagram showing an example of the configuration of a business system including an information processing apparatus according to an embodiment.

[0013] The business system 1 is, for example, a business network established within a company. As shown in FIG.

[0014] The information processing device 100 is, for example, an information processing device such as a PC or a server. The information processing device 100 has a function of assisting in the execution of various processes using multiple business applications by implementing an RPA tool. Specifically, the information processing device 100 is configured to automatically execute, using the RPA tool, a series of processes that are executed based on the operation of a user terminal 200 by a user. Hereinafter, the flow of a series of processes that are automatically executed by the information processing device 100 is also referred to as a "scenario." The process for automatically executing a series of processes based on a scenario is also referred to as a "scenario execution process."

[0015] The user terminal 200 is an information processing terminal such as a PC, a tablet, or a smartphone. The user terminal 200 instructs the information processing device 100 to execute a scenario. The user terminal 200 also receives a notification when an error occurs in the scenario executed by the information processing device 100.

[0016] 1.1.2 Information Processing Apparatus Next, the configuration of the information processing apparatus 100 will be described.

[0017] FIG. 2 is a block diagram illustrating an example of a hardware configuration of the information processing apparatus according to the embodiment.

[0018] As shown in FIG. 2, the information processing device 100 includes, for example, a control circuit 11, a storage 12, a communication module 13, an interface 14, a drive 15, and a storage medium 16.

[0019] The control circuit 11 is a circuit that controls the overall components of the information processing device 100. The control circuit 11 includes a CPU (central processing unit), a RAM (random access memory), a ROM (read only memory), etc. The CPU of the control circuit 11 controls the entire information processing device 100 in accordance with a program stored in the ROM of the control circuit 11. The RAM of the control circuit 11 has a working area for the CPU of the control circuit 11. The ROM of the control circuit 11 stores programs and the like used by the information processing device 100.

[0020] The storage 12 includes, for example, a hard disk drive (HDD) or a solid state drive (SSD). The storage 12 stores information used in the scenario execution process by the information processing device 100.

[0021] The communication module 13 is a circuit used for transmitting and receiving data between the information processing device 100 and the user terminal 200. The communication module 13 may be configured to connect the information processing device 100 to a network (not shown).

[0022] The interface 14 is an interface that manages communication with the user. The interface 14 includes input devices and output devices. The input devices include, for example, a keyboard, a touch panel, and operation buttons. The output devices include, for example, an LCD (Liquid Crystal Display) or an EL (Electroluminescence) display, a printer, etc. The output device displays, on a display, multiple business applications that are automatically executed by the RPA tool, for example.

[0023] The drive 15 is a device for reading software stored in the storage medium 16. The drive 15 includes, for example, a CD (Compact Disk) drive or a DVD (Digital Versatile Disk) drive.

[0024] The storage medium 16 is a medium that stores software electrically, magnetically, optically, mechanically, or chemically. The storage medium 16 may store a program used by the information processing device 100.

[0025] FIG. 3 is a block diagram illustrating an example of a functional configuration of the information processing apparatus according to the embodiment.

[0026] 3, the control circuit 11 of the information processing device 100 functions as a computer including a scenario holding unit 21, a scenario execution unit 22, a scenario correction unit 23, and a DB update unit 24. The storage 12 of the information processing device 100 stores a scenario file 31 and an update history DB 32.

[0027] The scenario holding unit 21 reads the scenario file 31, for example, in units of operation information within the scenario file 31.

[0028] FIG. 4 is a diagram showing an example of the data structure of a scenario file stored in the information processing apparatus according to the embodiment.

[0029] The scenario file 31 is created by, for example, a user who is an operator of the RPA tool. As shown in Fig. 4, the scenario file 31 is, for example, a text file that defines a series of processes to be automatically executed by the RPA tool. The scenario file 31 includes multiple pieces of operation information.

[0030] The operation information is information that defines individual processes included in a series of processes to be automatically executed. Each of the plurality of operation information includes, for example, operation type information and operation target information.

[0031] The operation type information is information for specifying the specific content (operation type) of the operation executed by the corresponding process. Specifically, for example, the operation target information is information for specifying a GUI (graphical user interface) object (operation target) on the screen that is the target of the operation executed by the corresponding process.

[0032] In the example shown in FIG. 4, the portion enclosed by "{" and "}" corresponds to one piece of operation information. Of the operation information, information defined by "type" corresponds to operation type information. Of the operation information, information defined by "target" corresponds to operation target information. The operation target information includes information such as an application name, a control type, and a name, for example.

[0033] Specifically, in the first piece of operation information shown in Fig. 4, the operation type is "input." The operation target is a GUI object whose application name is "chrome," whose control type is "edit," and whose name is specified by "A." In the second piece of operation information shown in Fig. 4, the operation type is "click." The operation target is a GUI object whose application name is "chrome," whose control type is "button," and whose name is specified by "B."

[0034] The scenario execution unit 22 performs a scenario execution process based on the operation information read by the scenario storage unit 21. The scenario execution unit 22 performs a process using a plurality of business applications in the order of the operation information described in the scenario file 31, for example.

[0035] In the case of a scenario execution process based on the scenario file 31 shown in Figure 4, the scenario execution unit 22, for example, performs input processing on a GUI object identified by the application name "chrome", control type "edit", and name "A", and then performs click processing on a GUI object identified by the application name "chrome", control type "button", and name "B".

[0036] The scenario modification unit 23 executes an operation information modification process based on the update history DB 32 each time the scenario execution unit 22 executes a process corresponding to the operation information. The operation information modification process includes, for example, a process of determining whether or not to modify the operation target information in the operation information, and a process of modifying the operation target information when it is determined that the operation target information should be modified. The scenario modification unit 23 outputs the operation information redefined by the modified operation target information to the scenario execution unit 22.

[0037] FIG. 5 is a diagram illustrating an example of a data structure of an update history DB stored in the information processing apparatus according to the embodiment.

[0038] The update history DB 32 is generated and updated by, for example, a user who is the operator of the RPA tool. As shown in Fig. 5, the update history DB 32 is a database having a matrix data structure consisting of multiple rows and multiple columns. Each of the multiple rows corresponds to an operation target. Each of the multiple columns corresponds to a change history. The multiple columns associated with the change history include, for example, one "operation environment (old)" column and one or more "operation environment (new)" columns.

[0039] The "Operation Environment (Old)" column corresponds to, for example, the operating environment when the scenario file 31 was first generated. The "Operation Environment (New)" column corresponds to, for example, the operating environment that was changed after the scenario file 31 was generated.

[0040] A set of operation object information and update date and time is stored in one data area specified by a set of one row and one column. In the example of Fig. 5, the data area corresponding to the row of operation object "A" and the column of operation environment (old) stores the fact that operation object information defined by the application name "chrome", the control type "edit", and the name "A" was generated at date and time "D1" as operation object information for identifying operation object "A". The data area corresponding to the row of operation object "B" and the column of operation environment (old) stores the fact that operation object information defined by the application name "chrome", the control type "button", and the name "B" was generated at date and time "D1" as operation object information for identifying operation object "B".

[0041] Furthermore, the data area corresponding to the row of operation target "A" and the column of operation environment (new) stores that operation target information defined by the application name "msedge", control type "edit", and name "A" was generated at date and time "D2" as operation target information for identifying operation target "A". The data area corresponding to the row of operation target "B" and the column of operation environment (new) stores that operation target information defined by the application name "msedge", control type "button", and name "B" was generated at date and time "D2" as operation target information for identifying operation target "B".

[0042] The DB update unit 24 executes DB update processing when automatic execution based on operation information fails because the operation target cannot be detected from the operation target information in the scenario file 31. The DB update processing is processing for updating the update history DB 32 so that the operation target information in the scenario file 31 can be corrected to operation target information that can detect the operation target in the operation information correction processing. The DB update unit 24 includes, for example, a selection unit 24a and a registration unit 24b.

[0043] The selection unit 24a selects an operation target to be detected from GUI objects displayed on the display of the interface 14 based on the operation target information in the scenario file 31. Any method can be applied to select the operation target. Specifically, for example, the selection unit 24a can use the string edit distance when property information of the operation target is expanded into a string of characters, or the similarity of the strings, in the selection process of the operation target. Here, for example, the Levenshtein distance or the like can be applied to the string edit distance. For example, the N-gram or the like can be applied to the similarity of sentences.

[0044] The registration unit 24b generates new operation target information (operation target information for update) that can identify the operation target selected by the selection unit 24a. The registration unit 24b then registers the generated operation target information for update in the update history DB 32. Specifically, for example, if a row corresponding to the selected operation target does not exist in the update history DB 32, the registration unit 24b adds a new row corresponding to the selected operation target to the update history DB 32. The registration unit 24b then stores a set of the operation target information for update and the update date and time in a data area corresponding to the row corresponding to the selected operation target and the column for the operation environment (new). The set of the operation target information for update and the update date and time may overwrite the existing column for the operation environment (new), or may be stored in a new data area created by adding a new column for the operation environment (new).

[0045] 1.2 Operation Next, the operation of the information processing device 100 will be described.

[0046] 1.2.1 Scenario Execution Processing FIG. 6 is a flowchart showing an example of scenario execution processing in the information processing device according to the embodiment.

[0047] When the start conditions for the scenario execution process are satisfied (start), the scenario storage unit 21 reads operation information for the execution target from the scenario file 31 (S11). The start conditions for the scenario execution process are specified, for example, by a user who is the operator of the RPA tool. The scenario execution process may be set to be executed periodically.

[0048] The scenario correction unit 23 executes an operation information correction process based on the operation information read in the process of S11 (S12). The operation information correction process will be described in detail later.

[0049] The scenario execution unit 22 automatically executes a process corresponding to the operation target based on the operation information that has been subjected to the operation information correction process in S12 (S13).

[0050] The DB update unit 24 determines whether the automatic execution in the process of S13 was successful (S14).

[0051] If the automatic execution has failed (S14; no), the DB update unit 24 determines whether or not the detection of the operation target has been successful based on the operation target information in the operation information (S15).

[0052] If the detection of the operation target fails (S15; no), the DB update unit 24 executes DB update processing (S16). The details of the DB update processing will be described later.

[0053] After the DB update process in S16, the DB update unit 24 determines whether the update of the update history DB 32 has been successful (S17).

[0054] If the automatic execution is successful (S14; yes), or if the update history DB 32 is successful (S17; yes), the scenario holding unit 21 determines whether all the operation information that should be read in the scenario file 31 has been read (S18).

[0055] If operation information to be read remains in the scenario file 31 (S18; no), the scenario holding unit 21 reads the operation information to be read from the scenario file 31 (S11). Then, the subsequent processes of S12 to S18 are executed. In this way, the processes of S11 to S18 are repeatedly executed until all operation information to be read in the scenario file 31 has been read.

[0056] If automatic execution fails but detection of the operation target is successful (S15; yes), if updating of the update history DB32 fails (S17; no), or if all operation information that should be read in the scenario file 31 has been read (S18; yes), the scenario execution process ends (end).

[0057] 1.2.2 Operation Information Correction Processing Fig. 7 is a flowchart showing an example of operation information correction processing in the information processing apparatus according to the embodiment. The processing of S21 to S25 shown in Fig. 7 corresponds to the processing of S12 in Fig. 6.

[0058] When the operation information of the operation target to be executed is read from the scenario file 31 (start), the scenario correction unit 23 searches the ``Operation Environment (old)'' column of the update history DB 32 for a row that stores data that matches the operation target information in the operation information read from the scenario file 31 (S21).

[0059] As a result of the processing in S21, the scenario correction unit 23 determines whether or not there is a row in the "operation environment (old)" column that stores data that matches the operation target information read from the scenario file 31 (S22).

[0060] If there is a row in the "Operation Environment (Old)" column that stores data that matches the operation target information read from the scenario file 31 (S22; yes), the scenario correction unit 23 determines whether there is an "Operation Environment (New)" column in the row that was determined to match the operation target information read from the scenario file 31 in the processing of S22 (S23).

[0061] If the row determined to match the operation target information read from the scenario file 31 has an "Operation Environment (New)" column (S23; yes), the scenario correction unit 23 selects the "Operation Environment (New)" column associated with the most recent update date from one or more "Operation Environment (New)" columns in the row determined to match the operation target information read from the scenario file 31 (S24).

[0062] The scenario correction unit 23 corrects the operation target information read from the scenario file 31 with the data stored in the "operation environment (new)" column selected in the processing of S24 from one or more "operation environment (new)" columns in the row determined to match the operation target information read from the scenario file 31 (S25).

[0063] If there is no row in the "Operation Environment (Old)" column that stores data that matches the operation target information read from the scenario file 31 (S22; no), if there is no "Operation Environment (New)" column in the row that is determined to match the operation target information (S23; no), or after processing in S25, the operation information correction process ends (end).

[0064] 1.2.3 DB Update Processing Fig. 8 is a flowchart showing an example of DB update processing in the information processing apparatus according to the embodiment. The processing of S31 to S37 shown in Fig. 8 corresponds to the processing of S16 in Fig. 6.

[0065] If the cause of the failure in automatic execution is failure to detect the operation target (start), the selection unit 24a selects the operation target that best matches the operation target information read from the scenario file 31 from the GUI objects displayed on the display of the interface 14 (S31).

[0066] As a result of the process of S31, the selection unit 24a determines whether or not the selection of the operation object that best matches the operation object information read from the scenario file 31 has been successful (S32).

[0067] If the selection of the operation target that best matches the operation target information read from the scenario file 31 fails (S32; no), the DB update unit 24 determines that the DB update process has failed and terminates the DB update process (end).

[0068] If the selection of the operation target that best matches the operation target information read from the scenario file 31 is successful (S32; yes), the registration unit 24b generates updated operation target information based on the operation target selected in the processing of S31 (S33). That is, the registration unit 24b generates new operation target information that can identify the operation target selected in the processing of S31 as updated operation target information.

[0069] The registration unit 24b refers to the update history DB 32 and searches for a row in which data matching the operation target information read from the scenario file 31 is stored in any of the columns (S34).

[0070] As a result of the process of S34, the registration unit 24b determines whether or not there is a row in which data matching the operation target information read from the scenario file 31 is stored in any column (S35).

[0071] If there is no row in any column in which data matching the operation target information read from the scenario file 31 is stored (S35; no), the registration unit 24b adds a row in which data matching the operation target information read from the scenario file 31 is stored to the update history DB 32 (S36). In this case, the column in which data matching the operation target information read from the scenario file 31 is stored is, for example, the "operation environment (old)" column.

[0072] If there is a row in which data matching the operation target information read from the scenario file 31 is stored in any column (S35; yes), or after processing of S36, the registration unit 24b adds an "Operation Environment (New)" column to the matching row, which stores the updated operation target information generated in processing of S33 and the update date (S37).

[0073] After the process of S37, the DB update unit 24 determines that the DB update process has been successful, and ends the DB update process (end).

[0074] 1.3 Effects of the Embodiment According to the embodiment, the scenario file 31 includes operation information that defines the content of an automatic operation, including operation target information that identifies an operation target to be subjected to the automatic operation. The scenario storage unit 21 reads the scenario file 31. The storage 12 stores an update history DB 32 that associates first operation target information with second operation target information that differs from the first operation target information. When the scenario correction unit 23 reads first operation information including the first operation target information, it corrects the first operation target information in the first operation information to the second operation target information based on the update history DB 32. The scenario execution unit 22 executes the first automatic operation based on the corrected first operation information. As a result, if the business application targeted by the first automatic operation is a localized operation, such as a design change, the scenario file 31 can be automatically corrected without the user having to modify the scenario file 31 itself. This reduces the burden on the user of modifying the scenario file 31.

[0075] Furthermore, if an operation target is not detected based on the second operation target information in the first automatic operation, the selection unit 24a automatically selects a new operation target corresponding to the second operation target information from the GUI objects on the screen. The registration unit 24b generates third operation target information that identifies the selected new operation target as updated operation target information, and updates and registers the second operation target information in the update history DB 32 to the third operation target information. This makes it possible to automatically perform the update process of the update history DB 32 that is necessary to automatically correct the scenario file 31. This further reduces the burden on the user of correcting the scenario file.

[0076] 2. Modifications, etc. Various modifications can be applied to the above-described embodiment.

[0077] The following mainly describes the configuration and operation that are different from the embodiment, and the description of the configuration and operation that are the same as the embodiment will be omitted as appropriate.

[0078] 2.1 First Modification In the above embodiment, the case where the selection unit 24a automatically selects the operation target has been described, but this is not limiting. For example, the operation target may be configured to be manually selected by the user.

[0079] The selection unit 24a selects one or more candidate operation targets to be detected based on the operation target information in the scenario file 31 from the GUI objects displayed on the display of the interface 14. Any method can be applied to select the candidate operation targets. Specifically, for example, the selection unit 24a can use the string edit distance when the property information of the operation targets is expanded into character strings, or the similarity of the character strings, in the process of selecting the candidate operation targets. Here, for example, the Levenshtein distance or the like can be applied to the string edit distance. For example, the N-gram or the like can be applied to the similarity of the sentences.

[0080] The selection unit 24a presents one or more selected operation target candidates to the user via the user terminal 200. For example, the selection unit 24a displays information on the display of the user terminal 200 indicating that an operation target could not be detected based on the operation target information in the scenario file 31. The selection unit 24a then further displays one or more selected operation target candidates on the display of the user terminal 200 in a state in which the user can select any one of the operation targets. When the user selects an operation target via the user terminal 200, the selection unit 24a outputs the selection result to the registration unit 24b.

[0081] With the above configuration, the selection unit 24a can output the result of manual selection by the user to the registration unit 24b as the final selection result.

[0082] 9 is a flowchart showing an example of DB update processing in the information processing device according to the first modified example, which corresponds to FIG. 8 in the embodiment.

[0083] If the cause of the failure in automatic execution is failure to detect the operation target (start), the selection unit 24a selects one or more candidate operation targets that match the operation target information read from the scenario file 31 from the GUI objects displayed on the display of the interface 14 (S41).

[0084] The selection unit 24a presents one or more candidates for the operation target selected in the process of S41 to the user via the user terminal 200 (S42).

[0085] The selection unit 24a waits until the user selects an operation target from one or more operation target candidates presented in the process of S42, or until a timeout occurs (S43).

[0086] As a result of the process of S43, the selection unit 24a determines whether or not the selection of the operation object that best matches the operation object information read from the scenario file 31 has been successful (S44).

[0087] If the selection of the operation target that best matches the operation target information read from the scenario file 31 fails (i.e., the user does not select an operation target before the timeout occurs) (S43; no), the DB update unit 24 determines that the DB update process has failed and terminates the DB update process (end).

[0088] If the selection of the operation target that best matches the operation target information read from the scenario file 31 is successful (i.e., the user selects an operation target before the timeout occurs) (S43; yes), the registration unit 24b generates updated operation target information based on the operation target selected by the user (S45). That is, the registration unit 24b generates new operation target information that can identify the operation target manually selected by the user as updated operation target information.

[0089] The registration unit 24b refers to the update history DB 32 and searches for a row in which data matching the operation target information read from the scenario file 31 is stored in any of the columns (S46).

[0090] The registration unit 24b determines whether or not there is a row in which data matching the operation target information read from the scenario file 31 is stored in any column as a result of the process of S46 (S47).

[0091] If there is no row in any column in which data matching the operation target information read from the scenario file 31 is stored (S47; no), the registration unit 24b adds a row in which data matching the operation target information read from the scenario file 31 is stored to the update history DB 32 (S48). In this case, the column in which data matching the operation target information read from the scenario file 31 is stored is, for example, the "operation environment (old)" column.

[0092] If there is a row in which data matching the operation target information read from the scenario file 31 is stored in any column (S47; yes), or after processing of S48, the registration unit 24b adds an "Operation Environment (New)" column to the matching row, which stores the updated operation target information generated in processing of S45 and the update date (S49).

[0093] After the process of S49, the DB update unit 24 determines that the DB update process has been successful, and ends the DB update process (end).

[0094] According to the first modification, when an operation target is not detected based on the second operation target information in the first automatic operation, the selection unit 24a selects one or more candidates for a new operation target corresponding to the second operation target information from the GUI objects on the screen and presents the candidates to the user. When the user selects one of the one or more candidates as a new operation target, the registration unit 24b generates third operation target information identifying the selected new operation target as updated operation target information and updates and registers the second operation target information in the update history DB 32 as the third operation target information. This allows the user to manually select a new operation target from the candidates selected by the selection unit 24a. This prevents operation target information identifying an incorrect operation target from being registered in the update history DB 32.

[0095] 2.2 Second Modification Although the above embodiment has described a case where the information processing device 100 is connected to one user terminal 200, this is not limiting. For example, the information processing device 100 may be connected to a plurality of user terminals 200. In this case, the update history DB 32 may be updated by a plurality of users via a plurality of user terminals 200.

[0096] Fig. 10 is a block diagram showing an example of the functional configuration of an information processing device according to Modification 2. Fig. 10 corresponds to Fig. 3 in the embodiment.

[0097] As shown in FIG. 10, the information processing apparatus 100 has a local environment LOCAL and a shared usage environment SHARE.

[0098] The local environment LOCAL is an area where, for example, an RPA tool is implemented, and includes a scenario storage unit 21, a scenario execution unit 22, a scenario correction unit 23, and a DB update unit 24.

[0099] The shared usage environment SHARE is, for example, an area commonly managed by a plurality of users. In the shared usage environment SHARE, a scenario file 31 and an update history DB 32 are stored.

[0100] The update history DB 32 can be updated by DB update processing by multiple users by being placed in the shared use environment SHARE. This allows for centralized management of update histories, for example, even when a scenario file 31 is shared by multiple users.

[0101] 2.3 Others In the above-described embodiment, a case has been described in which multiple "operation environment (new)" columns may be added to the update history DB 32, but this is not limited to this. For example, if there are multiple "operation environment (new)" columns, data with update dates other than the most recent may be deleted sequentially. In this case, it is possible to prevent the number of "operation environment (new)" columns in the update history DB 32 from increasing more than necessary.

[0102] In the above-described embodiment, the case where the program for executing the scenario execution process is executed by the information processing device 100 has been described, but this is not limiting. For example, the program for executing the scenario execution process may be executed by computational resources on a cloud configured on a network (not shown).

[0103] The present invention is not limited to the above-described embodiments, and various modifications can be made in the implementation stage without departing from the spirit of the invention. Furthermore, the embodiments may be implemented in appropriate combinations, in which case the combined effects can be obtained. Furthermore, the above-described embodiments include various inventions, and various inventions can be extracted by combining selected elements from the disclosed elements. For example, if the problem can be solved and the desired effect can be obtained even if some elements are deleted from all elements shown in the embodiments, the configuration from which these elements are deleted can be extracted as an invention.

[0104] 1... Business system 11... Control circuit 12... Storage 13... Communication module 14... Interface 15... Drive 16... Storage medium 21... Scenario storage unit 22... Scenario execution unit 23... Scenario correction unit 24... DB update unit 24a... Selection unit 24b... Registration unit 31... Scenario file 32... Update history DB 100... Information processing device 200... User terminal

Claims

1. An information processing device comprising: a scenario storage unit that reads operation information that defines the content of an automatic operation, the operation information including operation target information that identifies an operation target that is the target of the automatic operation; a memory unit that stores a database that associates first operation target information with second operation target information that is different from the first operation target information; a scenario correction unit that, when first operation information including the first operation target information is read, corrects the first operation target information in the first operation information to the second operation target information based on the database; and a scenario execution unit that executes a first automatic operation based on the corrected first operation information.

2. An information processing device as described in claim 1, further comprising: a selection unit that, when an operation target is not detected based on the second operation target information in the first automatic operation, selects a new operation target corresponding to the second operation target information from GUI objects on the screen; and a registration unit that generates third operation target information that identifies the new operation target and updates and registers the second operation target information in the database to the third operation target information.

3. The information processing device according to claim 2, wherein the selection unit presents the new operation target to the user, and the registration unit, when the user selects the new operation target, generates the third operation target information and updates and registers the second operation target information in the database to the third operation target information.

4. A program for causing a computer to function as each unit of the information processing device according to any one of claims 1 to 3.

Images