Automation management apparatus, automation management method, and non-transitory computer-readable storage medium

Abstract

To provide an automation management device, an automation management method, and an automation management program capable of omitting a log-in / log-out instruction of a user to be executed by not only serially designating an instruction but also adopting setting of a hierarchical structure when setting an instruction to an RPA, and setting timing when a hierarchy changes as timing of user switching.SOLUTION: In an RPA scenario in which operation target scenarios in which RPA operation instructions for robotic process automation are set are hierarchically set using an RPA execution program, the switching setting of a login user is determined by identifying the separation of the operation target scenarios set in parallel in the same layer, and the RPA operation instructions set in the RPA scenario are switched and executed in units of login users.SELECTED DRAWING: Figure 2

Description

[Technical Field]

[0001] The present invention relates to an automation management device, an automation management method, and an automation management program. [Background technology]

[0002] Patent Document 1 discloses a configuration in which login and logout are performed by RPA (Robotic Process Automation) in a proposal creation process. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Publication No. 2023-80834 Summary of the Invention [Problem to be solved by the invention]

[0004] However, the invention described in Patent Document 1 above has a problem in that in an RPA scenario that requires user switching, clear login / logout operation commands must be specified at the time of user switching.

[0005] The present invention has been made in consideration of the above-mentioned problems, and aims to provide an automation management device, an automation management method, and an automation management program that, when setting commands for an RPA, do not just specify the commands serially but also incorporate the setting of a hierarchical structure, and by setting the timing of a change in hierarchy as the timing of user switching, can omit the login and logout commands for the executing user. [Means for solving the problem]

[0006] In order to solve the above-mentioned problems and achieve the object, the automation management device of the present invention is an automation management device having a memory unit and a control unit, wherein the memory unit comprises an RPA scenario in which operation target scenarios in which RPA operation commands for robotic process automation are set are set hierarchically, and a development application storage means for storing an RPA execution program, and the control unit comprises an execution means for using the RPA execution program to identify the boundaries of the operation target scenarios set in parallel at the same hierarchical level in the RPA scenario, thereby determining the switching setting of the login user, and switching and executing the RPA operation commands set in the RPA scenario on a login user basis.

[0007] Furthermore, in the automation management device of the present invention, the execution means uses the RPA execution program to identify the division of the operation target scenarios set in parallel at the same hierarchical level in the RPA scenario, thereby determining the switching setting of the logged-in user, and by executing the RPA operation command that sets the login processing and logout processing for each executing user, the RPA operation command set in the RPA scenario is switched and executed on a per-login user basis.

[0008] Furthermore, the automation management method of the present invention is an automation management method to be executed by an automation management device having a memory unit and a control unit, wherein the memory unit comprises an RPA scenario in which operation target scenarios in which RPA operation commands for robotic process automation are set are hierarchically set, and a development application storage means for storing an RPA execution program, and is characterized in that the method includes an execution step of using the RPA execution program executed in the control unit to identify the boundaries of the operation target scenarios set in parallel at the same hierarchical level in the RPA scenario, thereby determining the switching settings of the logged-in user, and switching and executing the RPA operation commands set in the RPA scenario on a logged-in user basis.

[0009] In addition, the automation management program of the present invention is an automation management program to be executed by an automation management device having a memory unit and a control unit, wherein the memory unit comprises an RPA scenario in which operation target scenarios in which RPA operation commands for robotic process automation are set are hierarchically set, and a development application storage means for storing an RPA execution program, and the control unit executes an execution step in which the RPA execution program is used to identify the boundaries of the operation target scenarios set in parallel at the same hierarchical level in the RPA scenario, thereby determining the switching settings of the login user, and switching and executing the RPA operation commands set in the RPA scenario on a login user basis. [Effects of the Invention]

[0010] The present invention has the advantage of improving the visibility of automatic operation settings and enabling intuitive operation. Furthermore, the present invention has the advantage of facilitating the automation of regression testing and contributing to a reduction in testing man-hours. Furthermore, the present invention has the advantage of making it possible to easily set complex automatic operation procedures that involve user switching. Furthermore, the present invention has the advantage of making it possible to detect defects that were difficult to find using conventional regression testing. [Brief explanation of the drawings]

[0011] [Figure 1] FIG. 1 is a diagram illustrating an example of a conventional RPA operation command setting process. [Figure 2] FIG. 2 is a block diagram showing an example of the configuration of the automation management device according to this embodiment. [Figure 3] FIG. 3 is a flowchart showing an example of processing by the automation management device in this embodiment. [Figure 4] FIG. 4 is a diagram showing an example of an outline of the automation management process in this embodiment. [Figure 5]FIG. 5 is a diagram showing an example of an outline of the automation management process in this embodiment. [Figure 6] FIG. 6 is a diagram showing an example of a scenario creation process in this embodiment. [Figure 7] FIG. 7 is a diagram showing an example of a scenario creation screen in this embodiment. [Figure 8] FIG. 8 is a diagram showing an example of a scenario management table in this embodiment. [Figure 9] FIG. 9 is a diagram showing an example of the correspondence between the scenario creation screen and scenario setting information in this embodiment. [Figure 10] FIG. 10 is a diagram showing an example of the scenario execution process in this embodiment. [Figure 11] FIG. 11 is a diagram showing an example of the scenario execution process in this embodiment. [Figure 12] FIG. 12 is a diagram showing an example of the scenario execution process in this embodiment. [Figure 13] FIG. 13 is a diagram showing an example of a scenario creation process in this embodiment. [Figure 14] FIG. 14 is a diagram showing an example of a scenario creation process in this embodiment. [Figure 15] FIG. 15 is a diagram showing an example of a scenario creation process in this embodiment. [Figure 16] FIG. 16 is a diagram showing an example of a scenario creation process in this embodiment. [Figure 17] FIG. 17 is a diagram showing an example of a scenario creation process in this embodiment. [Figure 18] FIG. 18 is a diagram showing an example of a scenario creation process in this embodiment. [Figure 19] FIG. 19 is a diagram showing an example of a scenario creation process in this embodiment. [Figure 20] FIG. 20 is a diagram showing an example of a scenario creation process in this embodiment. [Figure 21] FIG. 21 is a diagram showing an example of a scenario creation process in this embodiment. [Figure 22] FIG. 22 is a diagram showing an example of a scenario creation process in this embodiment. [Figure 23] FIG. 23 is a diagram showing an example of a scenario creation process in this embodiment. [Figure 24] FIG. 24 is a diagram showing an example of a scenario creation process in this embodiment. [Figure 25] FIG. 25 is a diagram showing an example of a scenario creation process in this embodiment. [Figure 26] FIG. 26 is a diagram showing an example of a scenario creation process in this embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0012] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS An embodiment of the present invention will be described in detail with reference to the accompanying drawings. However, the present invention is not limited to this embodiment.

[0013] [1. Overview] First, an overview of the present invention will be described with reference to Fig. 1. Fig. 1 is a diagram showing an example of a conventional RPA operation command setting process.

[0014] In recent years, low-code development tools have been gaining attention as a tool that simplifies application development, and their use is even expanding into mission-critical enterprise systems. In this context, a system for maintaining the quality of applications created with low-code development tools is essential, and regression testing using RPA is gaining attention as a means to achieve this. Furthermore, because many business operations require automating data entry tasks previously performed manually in existing applications without modifying the applications, multiple Excel® applications and input screens must be simultaneously launched and operated in parallel. Furthermore, because multiple users must be able to switch between different execution modes in a single task, such as from application to approval, the resulting serialization of operation commands makes it impossible to detect the completion of a single user's processing. Therefore, hierarchical organization of scenario commands is likely meaningless, making explicit user switching commands essential.

[0015] (1) Conventionally, when issuing operation commands to an RPA, the commands were set serially, so in an RPA scenario where users were switched, it was difficult to determine the range of operations for a specific user.

[0016] For example, as shown in Figure 1, in the past, when issuing operation commands to an RPA, the commands were specified serially, which made the scenario less readable and required costs for user switching settings.

[0017] Therefore, in this embodiment, a mechanism is provided that visually supports and visualizes user switching operations when setting automatic screen operations. That is, in this embodiment, when setting commands for RPA, a mechanism is provided that incorporates hierarchical setting rather than simply specifying them serially, making it easier to check operation commands on the screen using the hierarchical structure.

[0018] (2) In addition, in the past, in RPA scenarios that required user switching, it was necessary to clearly specify login and logout operation commands at the time of user switching.

[0019] Therefore, in this embodiment, a mechanism is provided for automatically determining a login operation based on user switching operation settings using a hierarchical structure. Here, when focusing on unit testing of ERP (Enterprise Resources Planning: core information system), it is possible to set simpler RPA commands by imposing constraints on RPA operations on the premise that operations are completed starting from a specific user. Therefore, in this embodiment, when setting commands, a mechanism is provided that incorporates hierarchical structure settings rather than simply specifying them serially, so that the timing of the hierarchy change corresponds to the timing of user switching, and therefore login and logout commands for the executing user can be omitted.

[0020] [2. Configuration] An example of the configuration of the automation management device 100 according to this embodiment will be described with reference to Fig. 2. Fig. 2 is a block diagram showing an example of the configuration of the automation management device 100 according to this embodiment.

[0021] 2, the automation management device 100 is a commercially available desktop personal computer. Note that the automation management device 100 is not limited to a stationary information processing device such as a desktop personal computer, but may also be a portable information processing device such as a commercially available notebook personal computer, a PDA (Personal Digital Assistant), a smartphone, or a tablet personal computer.

[0022] The automation control device 100 includes a control unit 102, a communication interface unit 104, a storage unit 106, and an input / output interface unit 108. The units included in the automation control device 100 are connected to each other so as to be able to communicate with each other via any communication path.

[0023] The communication interface unit 104 communicably connects the automation management device 100 to the network 300 via a communication device such as a router and a wired or wireless communication line such as a dedicated line. The communication interface unit 104 has a function of communicating data with other devices via the communication line. Here, the network 300 has a function of connecting the automation management device 100 and the server 200 so that they can communicate with each other, and is, for example, the Internet or a LAN (Local Area Network).

[0024] An input device 112 and an output device 114 are connected to the input / output interface unit 108. The output device 114 may be a monitor (including a touch panel), a speaker, or a printer. The input device 112 may be a keyboard, a mouse, a microphone, or a monitor that cooperates with a mouse to achieve a pointing device function. In the following, the output device 114 may be referred to as the monitor 114 or the printer 114, and the input device 112 may be referred to as the keyboard 112 or the mouse 112.

[0025] The storage unit 106 stores various databases, tables, files, etc. The storage unit 106 stores computer programs that work in conjunction with an OS (Operating System) to issue commands to a CPU (Central Processing Unit) to perform various processes. The storage unit 106 may be, for example, a memory device such as a RAM (Random Access Memory) or a ROM (Read Only Memory), a fixed disk device such as a hard disk, a flexible disk, or an optical disk. The storage unit 106 includes a development application database 106a.

[0026] The development application database 106a stores automation management data. Here, the development application database 106a may store a low-code development tool. The development application database 106a may also store a (server-type / client-type) RPA tool including an RPA execution program. The development application database 106a may also store a scenario management table including an RPA scenario in which an operation target scenario is set in which an RPA operation command for robotic process automation is set. The development application database 106a may also store various screens including a scenario creation screen on which an RPA operation command for robotic process automation can be set.

[0027] The control unit 102 is a CPU or the like that performs overall control of the automation management device 100. The control unit 102 has an internal memory for storing control programs such as an OS, programs that define various processing procedures, required data, etc., and executes various information processing based on these stored programs. Functionally, the control unit 102 includes a creation screen display unit 102a, a hierarchical display unit 102b, a scenario creation unit 102c, and an execution unit 102d.

[0028] The creation screen display unit 102a displays a scenario creation screen on which RPA operation commands for robotic process automation can be set. Here, the creation screen display unit 102a may use a low-code development tool to display the scenario creation screen on which RPA operation commands for robotic process automation can be set.

[0029] The hierarchical display unit 102b superimposes on the scenario creation screen a block in which an RPA operation command can be set, when a request for setting an RPA operation command related to an execution user is set. Here, the hierarchical display unit 102b may superimpose on the scenario creation screen a block in a lower hierarchical level of the scenario creation screen in which an RPA operation command related to the execution user can be set. Furthermore, when a request for setting an RPA operation command to switch the login user from the execution user to another execution user is set, the hierarchical display unit 102b may superimpose on the scenario creation screen, at the same hierarchical level as the block, another block in which an RPA operation command related to the other execution user can be set. Furthermore, the hierarchical display unit 102b may selectably display predetermined RPA operation commands, excluding login switching, on the scenario creation screen, and when a predetermined RPA operation command is selected, set the predetermined RPA operation command in a lower hierarchical level of the block.

[0030] The scenario creation unit 102c creates an operation target scenario in which an RPA operation command for robotic process automation is set. Here, when an RPA operation command related to an execution user is set in a block, the scenario creation unit 102c may create an operation target scenario in which the RPA operation command for robotic process automation is set. Furthermore, the scenario creation unit 102c may register an RPA scenario in which operation target scenarios are set hierarchically in the development application database 106a based on the hierarchical structure set on the scenario creation screen.

[0031] The execution unit 102d uses the RPA execution program to execute the RPA operation command set in the RPA scenario. Here, the execution unit 102d may use the RPA execution program to identify a division between operation target scenarios set in parallel on the same tier in the RPA scenario, thereby determining a login user switching setting, and switch and execute the RPA operation command set in the RPA scenario for each login user. Furthermore, the execution unit 102d may use the RPA execution program to identify a division between operation target scenarios set in parallel on the same tier in the RPA scenario, thereby determining a login user switching setting, and execute the RPA operation command in which login processing and logout processing for each execution user are set, thereby switch and execute the RPA operation command set in the RPA scenario for each login user.

[0032] [3. Specific Examples] A specific example of this embodiment will be described with reference to FIGS.

[0033] [Automation Management Processing] An example of automation management processing in this embodiment will now be described with reference to Fig. 3. Fig. 3 is a flowchart showing an example of processing by the automation management device 100 in this embodiment.

[0034] As shown in FIG. 3, the creation screen display unit 102a uses a low-code development tool to display on the output device 114 a scenario creation screen on which RPA operation commands for robotic process automation can be set (step SA-1).

[0035] Then, when the scenario creator sets a request to set an RPA operation command related to the executing user via the input device 112, the hierarchy display unit 102b superimposes on the scenario creation screen a block that is at a lower level of the scenario creation screen and in which an RPA operation command related to the executing user can be set (step SA-2).

[0036] Then, the hierarchical display unit 102b determines whether or not the scenario creator has set, via the input device 112, a request to set an RPA operation command to switch the login user from the execution user to another execution user (step SA-3).

[0037] If the hierarchical display unit 102b determines that a setting request to switch the login user from the regular user to another regular user has been set (step SA-3: Yes), the hierarchical display unit 102b proceeds to step SA-4.

[0038] Then, the hierarchy display unit 102b superimposes other blocks on the scenario creation screen at the same hierarchy as the block, in which RPA operation commands related to the other executing user can be set (step SA-4), and transitions the processing to step SA-6.

[0039] On the other hand, if the hierarchical display unit 102b determines that a setting request to switch the login user from the regular user to another regular user has not been set (step SA-3: No), the hierarchical display unit 102b proceeds to step SA-5.

[0040] Then, the hierarchy display unit 102b displays specified RPA operation commands, excluding login switching, on the scenario creation screen in a selectable manner, and when the scenario creator selects a specified RPA operation command via the input device 112, it sets the specified RPA operation command in the lower hierarchy of the block (step SA-5) and transitions the processing to step SA-6.

[0041] Then, the execution unit 102d determines whether or not an RPA scenario in which the target scenarios are set hierarchically has been registered in the development application database 106a based on the hierarchical structure set on the scenario creation screen (step SA-6).

[0042] If the executing unit 102d determines that the RPA scenario is not registered (step SA-6: No), the executing unit 102d shifts the process to step SA-3.

[0043] On the other hand, if the executing unit 102d determines that the RPA scenario has been registered (step SA-6: Yes), it stores a scenario management table including the RPA scenario in the development application database 106a, and proceeds to step SA-7.

[0044] Then, the execution unit 102d uses the RPA execution program to identify the boundaries of the scenarios to be operated that are set in parallel at the same hierarchical level in the RPA scenario, thereby determining the switching settings for the login user, and by executing the RPA operation commands that set the login processing and logout processing for each executing user, switches and executes the RPA operation commands set in the RPA scenario on a login user basis (step SA-7), and terminates the processing.

[0045] An example of the automation management process in this embodiment will now be described with reference to Figures 4 and 5. Figures 4 and 5 are diagrams showing an example of the outline of the automation management process in this embodiment.

[0046] As shown in FIG. 4, in this embodiment, the execution user switching settings are hierarchically structured on the scenario creation screen, thereby improving the readability of the scenario and enabling cost reduction in user switching settings.

[0047] As shown in FIG. 5, in this embodiment, the RPA execution program interprets the execution settings and registered scenario contents, determines the user who will execute the operation, and performs the operation.

[0048] An example of an outline of a scenario creation process in this embodiment will be described with reference to Fig. 6 and Fig. 7. Fig. 6 is a diagram showing an example of a scenario creation process in this embodiment. Fig. 7 is a diagram showing an example of a scenario creation screen in this embodiment.

[0049] As shown in Figure 6, when creating the scenario "Is the approval process from the workflow application correct?" in this embodiment, if the scenario creator clicks the New button on the scenario creation screen shown in Figure 7, a new text box for the business partner is created, and if an application is made by the scenario creator, the screen returns to the list screen, allowing confirmation that the details have been added, and the information to be approved is displayed and approved.

[0050] An example of a scenario management table in this embodiment will be described with reference to Fig. 8. Fig. 8 is a diagram showing an example of a scenario management table in this embodiment.

[0051] As shown in Fig. 8, the scenario management table in this embodiment is data that is created when a scenario is registered. Here, as shown in Fig. 8, the start RPA operation key is a list of keys for RPA operations that start a scenario, and the targets of the start RPA operation key are operations that can be selected in the "Screen Start Operation" dialog, and the processing flow is such that A1 starts first, and A2 starts after all the RPA operations under it have been processed. Also, as shown in Fig. 8, the operation type is a classification of RPA operations. Also, as shown in Fig. 8, the RPA operation key list is a list of keys for RPA operations that are operated on the corresponding screen (the active screen at execution time).

[0052] An example of the correspondence between the scenario creation screen and scenario setting information in this embodiment will be described with reference to Fig. 9. Fig. 9 is a diagram showing an example of the correspondence between the scenario creation screen and scenario setting information in this embodiment.

[0053] FIG. 9 shows the correspondence between the RPA operation commands set by the scenario creator on the scenario creation screen and the scenario setting information included in the scenario management table.

[0054] An example of scenario execution processing in this embodiment will be described with reference to Figures 10 to 12. Figures 10 to 12 are diagrams showing an example of scenario execution processing in this embodiment.

[0055] 10 to 12, in this embodiment, execution settings, which are information necessary to execute a scenario, are held as setting data separate from the scenario settings, and the set contents are saved in the development application database 106a, making it possible to determine the unit of execution by the RPA for each execution setting. Therefore, in this embodiment, multiple execution settings are registered in one system, and when issuing an execution instruction to the RPA, the RPA is instructed which setting to use for execution.

[0056] Here, an example of the details of the scenario creation process in this embodiment will be described with reference to Fig. 13 to Fig. 26. Fig. 13 to Fig. 26 are diagrams showing an example of the scenario creation process in this embodiment.

[0057] As shown in Fig. 13, in this embodiment, when a scenario creator creates a new scenario, they create the new scenario from the scenario menu and enter a scenario code (CD) and a scenario name. Here, as shown in Fig. 13, in this embodiment, a button for creating a new scenario is provided in the scenario menu, and clicking this control launches the scenario creation screen, allowing scenario creation, so the scenario creator sets the operations in the order in which the RPA will actually execute them. Note that, as shown in Fig. 13, in this embodiment, the operation for automatically launching the screen when creating a new scenario is set, and the operation for launching the screen is set in the order indicated by the arrows.

[0058] As shown in Figure 14, [1] when the scenario is executed only by the default user, in this embodiment, a scenario creation screen is displayed in which an RPA operation command that does not involve login switching is set within the scenario.

[0059] On the other hand, [2] when a scenario involves login switching, as shown in Figures 15 to 17, in this embodiment, the RPA operation command for login switching is set, and the user who will perform the switching is set, and the RPA operation command for login switching makes it possible to execute the operation as a user other than the user who will execute the operation at the time of execution.

[0060] Specifically, in this embodiment, as shown in FIG. 15, [2-1] "Start a new screen" is clicked, as shown in FIG. 16, [2-2] Login switch is selected from the screen start operation, and the Confirm button is pressed, and as shown in FIG. 17, [2-3] the user to execute is entered.

[0061] Then, [3] when selecting a definition to operate, as shown in Figures 18 to 20, in this embodiment, a list of all definitions existing in the definition management table is displayed as options in a list, which involves launching the screen and setting an RPA operation command for operating the screen, and the definition name of the definition to operate on is searched for from the list.

[0062] Specifically, in this embodiment, as shown in FIG. 18, [3-1] "Add Operation" is clicked, [3-2] "Launch Screen" is selected, and the Confirm button is pressed. As shown in FIG. 19, [3-3] the definition to be launched is selected. Based on the control information in the definition management table (which stores the definition ID in the background at the time of selection), the screen layout is displayed below the selection list. Here, as shown in [3-2] of FIG. 18, in this embodiment, the operations that can be set in the hierarchy below login switching are limited, and only operations that launch a screen, such as "RPA Operation: Launch Screen," can be specified. Also, as shown in [3-3] of FIG. 19, in this embodiment, a list of all definitions in the definition management table is displayed as options, and the definition name of the definition to be operated is searched from the list. Furthermore, the screen layout / screen in this embodiment may refer to a screen design stored in the definition management table and created from control information.

[0063] Then, [4] when setting the operation content (RPA operation command), in this embodiment, as shown in Figures 21 to 26, it is selected whether to operate the control of the selected definition or to perform other fixed operations.

[0064] Specifically, in this embodiment, the RPA operation command for basic page operations is set by clicking "Add operation" in the approval registration frame [4-1] as shown in Figure 22, the control to be operated in the definition [4-2] is selected as shown in Figure 23, the operation based on the control selected in [4-3] [4-2] is selected as shown in Figures 24 and 25, and similar operations are performed to complete the scenario setting as shown in Figure 26.

[0065] Here, as shown by "*1" in Figure 22, in this embodiment, operations to be performed in the Customer Master Maintenance (List) can be added by clicking "Add Operation" in the Customer Master Maintenance (List) box, and a new RPA operation key is added to the list after the RPA operation key A12 "Screenshot" in the RPA operation key list for RPA operation key A1 in the scenario setting information of the scenario management table shown in Figure 9. Also, as shown by "*2" in Figure 22, in this embodiment, operations to be performed in the Approval Registration can be added by clicking "Add Operation" in the Approval Registration box, and the RPA operation keys "A211," "A212," and "A213" are added to the RPA operation key list for "Operate Screen" and "Approval Registration" in the RPA operation key A21 shown in Figure 9. Also, as shown in "*3" in Figure 22, in this embodiment, by adding "Add operation" in the login switch frame, an operation to launch another screen for the user set in the login switch can be added, and in the RPA operation key list for "Login switch" of RPA operation key A2 shown in Figure 9, this operation adds a new RPA operation key to the list after "Operate screen" and "Approval registration" of RPA operation key A21. Also, as shown in Figure 22, in this embodiment, operating a control within a definition is considered a basic page operation, and starting to operate another definition of the low-code platform is considered "Operate screen."

[0066] 23, in this embodiment, a target is selected from a list of operable controls in the definition selected in [3-3] and common operation targets that are not dependent on the definition settings. Here, in this embodiment, the system-wide operation target that is not dependent on the definition settings may be "Message Box Yes" or "Message Box No," etc. Also, in this embodiment, the master page may be a page that brings together functions common to the screen (displaying, adding, modifying, deleting data), and inheritance can reduce the cost of setting up the inheritance destination, and the operation is unified because the inheritance destination cannot change the controls located on the master page.

[0067] Also, as shown in Fig. 24, in this embodiment, a text box is selected, and character input is selected in the operation selection. Here, as shown in Fig. 24, in this embodiment, the displayed title is automatically set by combining the name of the target control selected in the operation target selection with the name of the operation selected in the operation selection. Also, as shown in Fig. 25, in this embodiment, a button or the like is selected, and click is selected in the operation selection.

[0068] Furthermore, as shown in Figure 26, in this embodiment, in response to the operation of the "Add operation" and "Start a new screen" buttons at each position arranged in the frame of the screen, the inner RPA operation key is added to the RPA operation key list held by the RPA operation key of the corresponding frame. Therefore, when registration is performed with the settings set up to this point, the parent-child relationship between the RPA operation key and the RPA operation key list is maintained so that the visualized hierarchical structure can be reproduced, and the corresponding data shown in the scenario setting information of the scenario management table shown in Figure 9 is registered.

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

[0070] Furthermore, this embodiment can contribute to reducing waste and promoting paperless and electronic systems, thereby contributing to the achievement of SDGs Goals 12, 13, and 15.

[0071] Furthermore, this embodiment can contribute to strengthening control and governance, which can contribute to the achievement of Goal 16 of the SDGs.

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

[0073] For example, among the processes described in the embodiments, all or part of the processes described as being performed automatically can be performed manually, or all or part of the processes described as being performed manually can be performed automatically using known methods.

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

[0075] Furthermore, with regard to the automation management device 100, the components shown in the drawings are functional concepts, and do not necessarily have to be physically configured as shown in the drawings.

[0076] For example, all or any part of the processing functions of the automation management device 100, particularly the processing functions performed by the control unit 102, may be implemented by a CPU and a program interpreted and executed by the CPU, or may be implemented as hardware using wired logic. The program is recorded on a non-transitory computer-readable recording medium containing programmed instructions for causing the information processing device to execute the processes described in this embodiment, and is mechanically read by the automation management device 100 as needed. That is, a computer program for providing instructions to the CPU in cooperation with the OS and performing various processes is recorded in a storage unit such as a ROM or HDD (Hard Disk Drive). This computer program is executed by being loaded into RAM, and cooperates with the CPU to form the control unit.

[0077] The computer program may also be stored in an application program server connected to the automation management device 100 via any network, and may be downloaded in whole or in part as needed.

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

[0079] Furthermore, a "program" is a data processing method written in any language or description method, and does not matter whether it is in the form of source code or binary code. Note that a "program" is not necessarily limited to a single structure, but also includes a structure that is distributed as multiple modules or libraries, or a structure that achieves its function by cooperating with a separate program, such as an OS. Note that the specific configuration and reading procedure for reading a recording medium in each device shown in this embodiment, as well as the installation procedure after reading, can use well-known configurations and procedures.

[0080] The various databases stored in the memory unit 106 are storage means such as memory devices such as RAM and ROM, fixed disk devices such as hard disks, flexible disks, and optical disks, and store various programs, tables, databases, and web page files used for various processes and providing websites.

[0081] The automation control device 100 may be configured as an information processing device such as a known personal computer or workstation, or may be configured as the information processing device to which any peripheral device is connected. The automation control device 100 may also be realized by installing software (including programs, data, etc.) that causes the device to perform the processes described in this embodiment.

[0082] Furthermore, the specific form of distribution and integration of the devices is not limited to that shown in the drawings, and all or part of them can be configured by functionally or physically distributing and integrating them in any unit depending on various additions or functional loads. In other words, the above-described embodiments can be implemented in any combination, or embodiments can be implemented selectively. [Industrial Applicability]

[0083] The present invention is useful in various industries, including the software industry that deals with RPA. [Explanation of symbols]

[0084] 100 Automation Control Devices 102 Control section 102a Creation screen display section 102b Hierarchy display section 102c Scenario Creation Department 102d Executive Department 104 Communication interface unit 106 Storage section 106a Development Application Database 108 Input / Output Interface Section 112 Input Device 114 Output Device 200 servers 300 Network

Claims

1. An automation management device comprising a memory unit and a control unit, The storage unit an RPA scenario in which operation target scenarios in which RPA operation commands for robotic process automation are set are hierarchically set, and a development application storage means for storing an RPA execution program; Equipped with The control unit an execution means for determining a switching setting of a login user by identifying a division of the operation target scenarios set in parallel at the same layer in the RPA scenario using the RPA execution program, and switching and executing the RPA operation command set in the RPA scenario on a login user basis; An automation management device comprising:

2. The execution means The automation management device described in claim 1, characterized in that the RPA execution program is used to identify the division of the operation target scenarios set in parallel at the same hierarchical level in the RPA scenario, thereby determining the switching setting of the login user, and executing the RPA operation command that sets login processing and logout processing for each executing user, thereby switching and executing the RPA operation command set in the RPA scenario on a per-login user basis.

3. An automation management method to be executed by an automation management device having a storage unit and a control unit, The storage unit an RPA scenario in which operation target scenarios in which RPA operation commands for robotic process automation are set are hierarchically set, and a development application storage means for storing an RPA execution program; Equipped with Executed in the control unit: an execution step of using the RPA execution program to identify a division of the operation target scenarios set in parallel at the same layer in the RPA scenario, thereby determining a switching setting of a login user, and switching and executing the RPA operation command set in the RPA scenario on a login user basis; 1. An automation management method comprising:

4. An automation management program to be executed by an automation management device having a storage unit and a control unit, The storage unit an RPA scenario in which operation target scenarios in which RPA operation commands for robotic process automation are set are hierarchically set, and a development application storage means for storing an RPA execution program; Equipped with In the control unit, an execution step of using the RPA execution program to identify a division of the operation target scenarios set in parallel at the same layer in the RPA scenario, thereby determining a switching setting of a login user, and switching and executing the RPA operation command set in the RPA scenario on a login user basis; Automation management program for running

Images