METHOD IMPLEMENTED BY COMPUTER AND COMPUTER SYSTEM FOR MONITORING THE AUTOMATION OF SOFTWARE EXECUTION
A centralized software coordinator addresses the limitations of existing automation monitoring systems by linking dependencies and providing a global view, enhancing error detection and maintenance efficiency in software automation processes.
Patent Information
- Application Number
- FR2022012509
- Authority / Receiving Office
- FR · FR
- Patent Type
- Utility models
- Current Assignee / Owner
- Filing Date
- 2022-11-29
- Publication Date
- 2024-11-22
- Estimated Expiration
- 2032-11-29
AI Technical Summary
Existing software automation monitoring systems fail to connect dependencies, identify impacts, and provide a global view of automation processes, leading to inefficiencies and user dissatisfaction due to process failures and complex interactions between software programs.
A one-stop-shop coordinator software that links dependencies, tracks data flow, and provides a centralized view of business processes, enabling error detection and improved maintenance by monitoring multiple automation software interfaces.
Facilitates quick error detection, enhances maintenance, and improves operational efficiency by offering a clear vision of digital activities, dynamic process mapping, and real-time monitoring across various applications.
Smart Images

Figure 00000000_0000_ABST
Abstract
Description
Title of the invention: COMPUTER-IMPLEMENTED METHOD AND COMPUTER SYSTEM FOR MONITORING THE AUTOMATION OF THE EXECUTION OF SOFTWARE Technical field of the invention
[0001] The present invention relates to a computer-implemented method for monitoring software execution automation and a computer system for monitoring software execution automation. It applies, in particular, to the field of software-assisted process automation. State of the art
[0002] The approaches described in this section are approaches that could be pursued, but not necessarily approaches that have been conceived or pursued previously. Therefore, unless otherwise indicated, it should not be assumed that any of the approaches described in this section constitute prior art simply because of its inclusion in this section.
[0003] Approaches to implementing codes for data exchange (automated interface technologies or APIs), as well as approaches to automating IT tasks (scheduler or RPA), do not allow for linking dependencies or identifying the impacts of automation for users of business processes. They also do not provide a global view (of all automated processes in the company) and a centralized view (grouped in one place).
[0004] Conversely, approaches based on code execution that track the execution of business processes (Business Activity Monitoring) do not rely on the exchange of data important to the business to track the automation of interfaces.
[0005] In the field of information technology, the automation of business processes through the use of software is driving productivity gains in all sectors. However, within organizations, the number of software programs and the complexity of interactions between these programs, both internally and externally with websites or third-party applications, are increasing to such an extent that processes are failing and user dissatisfaction is growing.
[0006] Currently, the only way to monitor various business automation software is to monitor each software individually. Summary of the invention
[0007] The present invention aims to overcome the aforementioned drawbacks as well as other disadvantages that could be overcome although not mentioned in the description below.
[0008] The concept of the present invention relates to the use of a one-stop coordinator (or orchestrator) software, which is connected to process automation software and other resources in such a way that dependencies can be linked, impacts identified and data flow tracked in a business process involving multiple automation software or interfaces.
[0009] Such an invention makes it possible to detect errors more quickly and improve the maintenance of automation software.
[0010] Such an invention may take the form of a cloud solution (installed on a client's server) providing true governance of digital exchanges, securing digital initiatives and offering users at least some of the following detailed advantages: - a simple and clear vision of digital activities and exchanges (technical data becomes understandable by company stakeholders), - a single measurement of the performance of all applications thanks to a dashboard and dynamic mapping of process execution, - automation of applications with automatic execution of digitalized tasks, - prioritization of data flows for better application responsiveness, - easy coordination of application processes, - planning of commercial operations on the same tool, - monitoring processes in a unified environment (for better reliability of operations), - real-time monitoring and control of process execution, - management of process execution successes and failures, - reduction of the time required to detect an incident and analyze the cause of the malfunction, - better cooperation between stakeholders (thanks to a shared vision between IT departments and other business units) through a single, collaborative interface, - a solution adapted to any application interface, the invention can, for example, natively use the connectors made available by Microsoft to connect to API applications, - an organizational vision of the exchange of information between internal or external actors of an organization, - operational research of a subject for a given process in order to ensure traceability of the latter and of GDPR data (for "General Data Protection Re- gulation") exchanged in a predefined context and - assessment of the financial impact of an erroneous data exchange by Business Unit and area of activity with the number of employees in the affected department. Brief description of the figures
[0011] Other advantages, aims and particular characteristics of the invention will emerge from the following non-exhaustive description of at least one method or system which is the particular subject of the present invention, in relation to the appended drawings, in which:
[0012] [Fig-1] represents, schematically and in the form of an organizational chart, a particular succession of steps of the method which is the subject of the present invention,
[0013] [Fig.2] schematically represents a particular embodiment of a system object of the present invention and
[0014] [Fig.3] schematically represents a sequence of execution of a sequence of software modules. Detailed description of the invention
[0015] This description is not exhaustive, since each feature of an embodiment can be combined with any other feature of any other embodiment in an advantageous manner.
[0016] Various inventive concepts may be embodied by one or more methods, an example of which has been provided. The steps performed in the method of the present invention may be ordered in any suitable manner. Accordingly, it is possible to construct embodiments in which the acts are performed in a different order than illustrated, which may include performing certain acts simultaneously, even if they are presented as sequential acts in the illustrated embodiments.
[0017] The indefinite articles "have" and "have", as used in the description and claims, are to be understood, unless otherwise clearly indicated, as meaning "at least one".
[0018] The expression "and / or", as used in the specification and in the claims, is to be understood as meaning "either or both" of the elements so conjoined, i.e., elements which are present conjunctively in some cases and disjunctively in other cases. Multiple elements listed with "and / or" are to be interpreted in the same way, i.e., "one or more" of the elements so conjoined. Other elements may optionally be present, other than the elements specifically identified by the "and / or" clause, whether or not related to those specifically identified elements. Thus, by way of non-limiting example, a reference to "A and / or B", when used in conjunction with open language such as "comprising", may refer, in a embodiment, to A only (possibly including elements other than B); in another embodiment, to B only (possibly including elements other than A); in yet another embodiment, to both A and B (possibly including other elements); etc.
[0019] As used in the specification and in the claims, "or" is to be understood as having the same meaning as "and / or" as defined above. For example, when separating elements in a list, "or" or "and / or" is to be interpreted as inclusive, i.e., the inclusion of at least one, but also more than a number or list of elements, and, optionally, additional non-enumerated elements. Only terms clearly indicating the contrary, such as "only one of" or "exactly one of", or, when used in the claims, "consisting of", will refer to the inclusion of only one of a number or list of elements.In general, the term "or" as used herein should be construed as indicating exclusive alternatives (i.e., "either, but not both") only when preceded by exclusivity terms, such as "either," "one of," "only one of," or "exactly one of." "Consisting essentially of," when used in the claims, has its ordinary meaning as used in the field of patent law.
[0020] As used in the specification and claims, the term "at least one", with reference to a list of one or more elements, is to be understood to mean at least one element selected from one or more of the elements in the list of elements, but not necessarily including at least one of each of the elements specifically listed in the list of elements and not excluding any combination of elements in the list of elements. This definition also allows for the optional presence of elements other than the specifically identified elements in the list of elements to which the term "at least one" refers, whether or not related to those specifically identified elements.Thus, by way of non-limiting example, "at least one of A and B" (or, equivalently, "at least one of A or B", or, equivalently, "at least one of A and / or B") may refer, in one embodiment, to at least one, optionally including more than one, A, without B present (and optionally including elements other than B); in another embodiment, to at least one, optionally including more than one, B, without A present (and optionally including elements other than A); in yet another embodiment, to at least one, optionally including more than one, A, and at least one, optionally including more than one, B (and optionally including other elements); etc.
[0021] In the claims, as well as in the above specification, all transitional expressions such as "comprising", "including", "carrying", "having", "containing", "involving", "holding", "composed of", and the like, are to be understood as open, i.e., as meaning including, but not limited to. Only the transitory expressions "consisting of" and "consisting essentially of" are to be closed or semi-closed transitory expressions, respectively.
[0022] It should be noted that the figures are not to scale.
[0023] According to one embodiment, the techniques described herein are implemented by at least one computing device. The techniques may be implemented in whole or in part using a combination of at least one server computer and / or other computing devices that are coupled using a network, such as a packet data network. The computing devices may be hardwired to perform the techniques or may include digital electronic devices such as at least one application-specific integrated circuit (ASIC) or field-programmable gate array (FPGA) that is permanently programmed to perform the techniques or may include at least one general-purpose hardware processor programmed to perform the techniques in accordance with program instructions in firmware, memory, other storage, or a combination.These computing devices may also combine custom hardwired logic, ASICs, or FPGAs with custom programming to perform the described techniques. The computing devices may be server computers, workstations, personal computers, portable computing systems, handheld devices, mobile computing devices, wearable devices, body-mounted or implantable devices, smartphones, smart appliances, interconnect devices, autonomous or semi-autonomous devices such as robots or unmanned ground or aerial vehicles, any other electronic device that incorporates hardwired and / or programmed logic to implement the described techniques, one or more virtual computing machines or instances in a data center, and / or a network of server computers and / or personal computers.
[0024] [Fig. 2] depicts a block diagram that illustrates an exemplary computer system with which an embodiment may be implemented. In the example of [Fig. 2], a computer system 205 and instructions for implementing the disclosed technologies in hardware, software, or a combination of hardware and software, are depicted schematically, e.g., as boxes and circles, at the same level of detail that is commonly used by those of ordinary skill in the art to which this disclosure relates to communicate about computer architecture and computer system implementations.
[0025] The computer system 205 includes an input / output (I / O) subsystem 220 that may include a bus and / or one or more other communication mechanisms for communicating information and / or instructions between components of the computer system 205 over electronic signal paths. The input / output subsystem 220 may include an input / output controller, a memory controller, and at least one input / output port. The electronic signal paths are shown schematically in the drawings, for example, as lines, one-way arrows, or two-way arrows.
[0026] At least one hardware processor 210 is coupled to the I / O subsystem 220 to process information and instructions. The hardware processor 210 may include, for example, a general-purpose microprocessor or microcontroller and / or a special-purpose microprocessor such as an embedded system or graphics processing unit (GPU) or a digital signal processor or an ARM processor. The processor 210 may include an integrated arithmetic logic unit (ALU) or may be coupled to a separate ALU.
[0027] The computer system 205 includes one or more memory units 225, such as a main memory, which is coupled to the I / O subsystem 220 to electronically digitally store data and instructions to be executed by the processor 210. The memory 225 may include volatile memory such as various forms of random access memory (RAM) or any other dynamic storage device. The memory 225 may also be used to store temporary variables or other intermediate information during execution of the instructions to be executed by the processor 210. Such instructions, when stored in a non-transitory computer-readable storage medium accessible to the processor 210, may transform the computer system 205 into a special purpose machine that is customized to perform the operations specified in the instructions.
[0028] The computer system 205 further includes non-volatile memory such as a read-only memory (ROM) 230 or other static storage device coupled to the I / O subsystem 220 for storing information and instructions for the processor 210. The ROM 230 may include various forms of programmable ROM (PROM) such as erasable PROM (EPROM) or electrically erasable PROM (EEPROM). A persistent storage unit 215 may include various forms of non-volatile random access memory (NVRAM), such as FLASH memory, or solid state storage, a magnetic disk, or an optical disk such as a CD-ROM or DVD-ROM and may be coupled to the I / O subsystem 220 for storing information and instructions. The storage 215 is an example of a non-transitory computer-readable medium that may be used to store instructions and data which, when executed by the processor 210, causes the execution of computer-implemented methods for performing the techniques of this document.
[0029] The instructions in memory 225, ROM 230, or storage 215 may comprise one or more sets of instructions that are organized into modules, methods, objects, functions, routines, or calls. The instructions may be organized as one or more computer programs, operating system services, or application programs, including mobile applications.The instructions may include an operating system and / or system software; one or more libraries to support multimedia, programming, or other functions; data protocol instructions or stacks to implement TCP / IP, HTTP, or other communications protocols; file format processing instructions to parse or render files encoded using HTML, XML, JPEG, MPEG, or PNG; user interface instructions to render or interpret commands for a graphical user interface (GUI), command-line interface, or text-based user interface; application software such as an office suite, Internet access applications, design and manufacturing applications, graphics applications, audio applications, software engineering applications, educational applications, games, or miscellaneous applications.The instructions may implement a web server, a web application server, or a web client. The instructions may be organized as a presentation layer, an application layer, and a data storage layer such as a relational database system using Structured Query Language (SQL) or no SQL, an object store, a graph database, a flat file system, or any other data storage.
[0030] The computer system 205 may be coupled via the I / O subsystem 220 to at least one output device 235. In one embodiment, the output device 235 is a digital computer display. Exemplary displays that may be used in various embodiments include a touchscreen or a light-emitting diode (LED) display or a liquid crystal display (LCD) or an e-paper display. The computer system 205 may include one or more other types of output devices 235, instead of or in addition to a display device. Examples of other output devices 235 include printers, ticket printers, plotters, projectors, sound cards or video cards, speakers, buzzers or piezoelectric devices or other audible devices, LED or LCD lamps or indicators, haptic devices, actuators, or servomotors.
[0031] At least one input device 240 is coupled to the I / O subsystem 220 to communicate signals, data, command selections, or gestures to the processor 210. Examples of input devices 240 include touchscreens, microphones, digital still and video cameras, alphanumeric and other keys, keyboards, graphics tablets, image scanners, joysticks, clocks, switches, buttons, dials, slides.
[0032] Another type of input device is a control device 245, which may perform cursor control or other automated control functions such as navigating a graphical interface on a display screen, alternatively or in addition to input functions. The control device 245 may be a touchpad, mouse, trackball, or cursor direction keys to communicate direction information and control selections to the processor 210 and to control movement of the cursor on the display 235. The input device may have at least two degrees of freedom in two axes, a first axis (e.g., x) and a second axis (e.g., y), which allows the device to specify positions in a plane.Another type of input device is a wired, wireless, or optical control device, such as a joystick, wand, console, steering wheel, pedal, gear shift mechanism, or other type of control device. An input device 240 may include a combination of several different input devices, such as a video camera and a depth sensor.
[0033] In another embodiment, the computer system 205 may include an Internet of Things (IoT) device in which one or more of the output device 235, the input device 240, and the control device 245 are omitted. Or, in such an embodiment, the input device 240 may include one or more cameras, motion detectors, thermometers, microphones, seismic detectors, other sensors or detectors, measuring devices, or encoders, and the output device 235 may include a special-purpose display such as a single-line LED or LCD display, one or more indicators, a display panel, a meter, a valve, a solenoid, an actuator, or a servomotor.
[0034] The computer system 205 may implement the techniques described herein using custom hardwired logic, at least one ASIC or FPGA, firmware, and / or instructions or program logic that, when loaded and used or executed in combination with the computer system, cause or program the computer system to operate as a special purpose machine. In one embodiment, the techniques described herein are executed by the computer system 205 in response to the processor 210 executing at least one sequence of at least one instruction contained in main memory 225. These instructions may be read into main memory 225 from another storage medium, such as memory 215. Execution of the sequences of instructions contained in main memory 225 causes processor 210 to execute the process steps described herein. In other embodiments, hard-wired circuits may be used instead of or in combination with software instructions.
[0035] The term "storage medium," as used herein, means any non-transitory medium that stores data and / or instructions that enable a machine to operate in a specific manner. These storage media may include non-volatile media and / or volatile media. Non-volatile media include, for example, optical or magnetic disks, such as memory 215. Volatile media include dynamic memory, such as memory 225. Common forms of storage media include, for example, a hard disk drive, a solid-state drive, a flash drive, a magnetic data storage medium, any optical or physical data storage medium, a memory chip, etc.
[0036] Storage media are distinct from, but may be used in conjunction with, transmission media. Transmission media assist in the transfer of information between storage media. For example, transmission media include coaxial cables, copper wires, and optical fibers, including wires that constitute a bus of the I / O subsystem 220. Transmission media may also take the form of acoustic or light waves, such as those generated during radio and infrared data communications.
[0037] Various forms of media may be involved in transporting at least one sequence of at least one instruction to the processor 210 for execution. For example, the instructions may initially be transported on a magnetic disk or solid-state drive of a remote computer. The remote computer may load the instructions into its dynamic memory and send the instructions over a communications link such as a fiber optic or coaxial cable or a telephone line using a modem. A modem or router local to the computer system 205 may receive the data over the communications link and convert the data into a format that can be read by the computer system 205.For example, a receiver such as a radio frequency antenna or an infrared detector may receive the data carried in a wireless or optical signal and suitable circuitry may provide the data to the I / O subsystem 220, for example by placing the data on a bus. The I / O subsystem 220 transports the data to the . memory 225, from which the processor 210 retrieves and executes instructions. Instructions received by the memory 225 may optionally be stored on the memory 215 before or after execution by the processor 210.
[0038] The computer system 205 also includes a communication interface 260 coupled to the bus 220. The communication interface 260 provides a bidirectional data communication coupling to the one or more network links 265 that are directly or indirectly connected to at least one communication network, such as a network 270 or a public or private cloud on the Internet. For example, the communication interface 260 may be an Ethernet network interface, an Integrated Services Digital Network (ISDN) card, a cable modem, a satellite modem, or a modem for providing a data communication connection to a corresponding type of communication line, for example, an Ethernet cable or a metallic cable of any type or a fiber optic line or a telephone line. The network 270 broadly represents a local area network (LAN), a wide area network (WAN), a campus network, an Internet network, or any combination thereof.The communications interface 260 may include a LAN card to provide a data communications connection to a compatible LAN, or a cellular radiotelephone interface that is wired to send or receive cellular data according to cellular radiotelephone wireless network standards, or a satellite radio interface that is wired to send or receive digital data according to satellite wireless network standards. In any such implementation, the communications interface 260 sends and receives electrical, electromagnetic, or optical signals over signal paths that carry digital data streams representing various types of information.
[0039] The network link 265 generally provides electrical, electromagnetic, or optical data communication, directly or via at least one network, to other data devices, using, for example, satellite, cellular, Wi-Fi, or BLUETOOTH technology. For example, the network link 265 may provide a connection via a network 270 to a host computer 250.
[0040] Further, the network link 265 may provide a connection via the network 270 or to other computing devices via interconnecting devices and / or computers that are operated by an Internet Service Provider (ISP) 275. The ISP 275 provides data communication services via a global packet data communication network represented by the Internet 280. A server computer 255 may be coupled to the Internet 280. The server 255 broadly represents any computer, data center, virtual machine or virtual computing instance with or without a hypervisor, or computer running a containerized program system such as DOCKER or KUBERNETES. The server 255 may represent an electronic digital service that is implemented using multiple computers or instances and is accessed and used by transmitting web service requests, uniform resource locator (URL) strings with parameters in HTTP payloads, API calls, application service calls, or other service calls. The computer system 205 and the server 255 may form elements of a distributed computing system that includes other computers, a processing cluster, a server farm, or other organization of computers that cooperate to perform tasks or run applications or services. The server 255 may include one or more sets of instructions that are organized as modules, methods, objects, functions, routines, or calls.The instructions may be organized as one or more computer programs, operating system services, or application programs, including mobile applications.The instructions may include an operating system and / or system software; one or more libraries to support multimedia, programming, or other functions; data protocol instructions or stacks to implement TCP / IP, HTTP, or other communications protocols; file format processing instructions to parse or render files encoded using HTML, XML, JPEG, MPEG, or PNG; user interface instructions to render or interpret commands for a graphical user interface (GUI), command-line interface, or text-based user interface; application software such as an office suite, Internet access applications, design and manufacturing applications, graphics applications, audio applications, software engineering applications, educational applications, games, or miscellaneous applications.The server 255 may include a web application server that hosts a presentation layer, an application layer, and a data storage layer such as a relational database system using Structured Query Language (SQL) or no SQL, an object store, a graph database, a flat file system, or other data storage.
[0041] The computer system 205 may send messages and receive data and instructions, including program code, via the network(s), the network link 265, and the communications interface 260. In the Internet example, a server 255 may transmit requested code for an application program via the Internet 280, the ISP 275, the local area network 270, and the communications interface 260. The received code may be executed by the processor 210 as it is received, and / or stored in memory 215, or other non-volatile memory for later execution.
[0042] The execution of instructions as described in this section may implement a process as an instance of a computer program that is currently running and consists of the program's code and its current activity. Depending on the operating system (OS), a process may consist of multiple threads that execute instructions concurrently. In this context, a computer program is a passive collection of instructions, while a process may be the actual execution of those instructions. Multiple processes may be associated with the same program; for example, having multiple instances of the same program open often means that more than one process is running. Multitasking may be implemented to allow multiple processes to share the processor 210.Although each processor 210 or processor core executes only one task at a time, the computer system 205 may be programmed to implement multitasking to allow each processor to switch between currently executing tasks without having to wait for each task to complete. In one embodiment, the switches may be performed when tasks perform input / output operations, when a task indicates that it can be switched, or upon hardware interrupts. Time sharing may be implemented to allow rapid response to user interactive applications by rapidly performing context switches to give the appearance of simultaneous execution of multiple processes.In one embodiment, for security and reliability reasons, an operating system may prevent direct communication between independent processes, by providing strictly mediated and controlled interprocess communication functionality.
[0043] [Fig. 1] schematically represents a particular succession of steps of the method 100 which is the subject of the present invention. This method 100, implemented by computer, for monitoring the automation of the execution of software, comprises: - a step 105 consisting of defining, on a computer interface, at least two software modules, each software module being associated with: - a digital software identifier representative of existing software to be executed or of an application interface to be addressed, - a runtime error code output format, and - a runtime error code output connector, - a step 110 of defining, on a computer interface, an execution sequence of at least two software execution automation processes, each software execution automation process being associated with an execution sequence of at least one defined software module, - a step 115 of execution, by a software execution orchestrator executed on the computing device, of the execution sequence of at least two processes of automating software execution by executing the associated software sequence, - a step 120 of receiving, by the software execution orchestrator, an error code from a software module during execution, and - a step 125 consisting of providing, on a computer interface, an output representative of the error code received and the digital identifier of the software associated with the software module at the origin of the error code.
[0044] The objective of definition step 105 is to digitize a business process based on several different software programs of the same type or different types in order to automate said business process. During definition step 105, the key modules of the automation process are defined as software modules.
[0045] The definition step 105 is performed, for example, by computer software executed on a computing device 205, as shown in [Fig. 2]. For example, during this definition step 105, instructions stored in the memory 215 and executed by the processor 210 trigger the communication of the input / output subsystem 220 with: - the output device 235, such as a computer screen, in order to show a graphical interface and - the input device 240, such as a mouse and keyboard, for collecting user input.
[0046] During this definition step 105, a user can add, modify and / or delete digital representations of software modules, each software module being associated with: - a digital software identifier representative of existing software to be executed or of an application interface to be addressed, - a runtime error code output format, and - a runtime error code output connector.
[0047] The digital identifier of the software is, for example, an API address, an executable file or the address of such an executable file.
[0048] In particular embodiments, at least one software module is a robotic process automation.
[0049] In particular embodiments, at least one software module is an application programming interface.
[0050] In particular embodiments, at least one software module is task scheduling software.
[0051] In particular embodiments, at least one software module is file transfer software.
[0052] The output format of the runtime error code is defined by the software, such error code output format typically being alphanumeric and corresponding, for each value, to a distinct error type. Such an error may further be associated with a comment, typically a string providing additional details associated with the error code received.
[0053] The runtime error code output connector is, for example, a software connector, such as an API or any other software output. Such a connector is responsible for transmitting the error codes according to the runtime error code output format.
[0054] For example, the output of step 105 is a list of software to be executed in order to achieve end-to-end automation of a business process, i.e. from standard input to standard output. The input itself depends on the nature of the first software to be executed while the output depends on the nature of the last software to be executed.
[0055] It is understood that the software modules may be organized into a taxonomy in which the software modules may be organized into levels of dependency between the software modules.
[0056] The definition step 110 is performed, for example, by computer software executed on a computer device 205, as shown in [Fig. 2]. This definition step 110 may be performed simultaneously with the software module definition step 105, insofar as such software modules may be defined and sequenced as said software modules are defined. During this definition step 110, for example, a user may select, on a graphical interface, a defined software module and assign a number of distinct parameters to said software module, such as: - a previous software module in the sequence, - a next software module in the sequence, - an execution mode of the software module, such as automatic, manual, deferred or orchestrated and / or - an execution authorization value, which may be associated with authentication information, such as a password or a token or any other digital secret allowing the interfacing of the software module with another software module (internal and / or external to the defined sequence) or an APL
[0057] In particular embodiments, as represented in [Fig.l], at least one software module is further associated with a validation type, said execution type being at least either manual, deferred, orchestrated or automatic, the execution step 115 further comprising, if the corresponding software module is associated with a manual validation type, a step 150 of validation by the user of the execution carried out by the software module.
[0058] A manual execution type corresponds to a software module requiring an input from the user, via an I / O subsystem 220, to initiate the execution of the software module.
[0059] An automatic execution type corresponds to a software module that does not require any user input to initiate execution of the software module.
[0060] A deferred, or delayed, execution type corresponds to a software module associated with an execution date (every night, for example), where the execution of the software module is carried out when the execution date is reached.
[0061] An orchestrated execution type corresponds to a software module associated with increased traceability of the execution, in which the execution logs are provided to a user during the execution of the software module.
[0062] The user validation step 150 may utilize an I / O subsystem 220 of a computing device. This I / O subsystem 220 may be, for example, a graphical interface displayed on a computer screen allowing a user to view the output of a software module and to validate, invalidate, or modify the output before use of this output by a downstream software module.
[0063] Execution step 115 is performed according to the defined sequence of software modules. The exact nature of execution step 115 depends on the nature of the software modules defined during software module definition step 105. In a particular example of this execution step 115: - a first software module receives, as input, a spreadsheet document containing employee names to be added to the organization, - a second software module uses the input spreadsheet to connect, for each row corresponding to a new employee to be added, to a website of the national employment registration office and, for each detail of the row (age, address, salary for example), fills in the corresponding field in the website, said software being of the RPA type, - a third software module then uses the input spreadsheet to, via an API, add a portion of the users to the user base of a third-party customer relationship management system, based on a job title associated with each row, and - a fourth software module then uses the new entries in the user base of the third-party customer relationship management system to assign customer identifiers in a third-party sales lead database and update the customer relationship management system, this fourth software module requiring user validation of the sales lead assignment.
[0064] In particular embodiments, the method 100 which is the subject of the present invention comprises a step 145 of storage, by the software execution orchestrator, for at least one software module, of authentication information, the step 115 of execution, for said software module, being carried out as a function of the information stored authentication.
[0065] This authentication information can be any type of digital secret, such as a password or a certificate for example.
[0066] This authentication information may further correspond to a data validation key, defined by a user, which is used to authenticate the data transferred between two software modules or between the software module and the orchestrator.
[0067] The receiving step 120 depends on both the output format of the execution error code and the output connector of the execution error code from the software module to the source of the error code. In the example mentioned above, a particular error code may correspond to the inability to connect to the API of the second software module or the inability to assign a sales lead in the fourth software module to a particular user. The connector may be an API or any other output means of the software module.
[0068] The providing step 125 may be performed, for example, using an I / O subsystem 220 of a computing device 205. This I / O subsystem 220 may be, for example, a graphical interface displayed on a computer screen allowing a user to view the software module that is the source of the error code, as well as the error code itself or a representation of said error code, such as a label corresponding to the error code.
[0069] In particular embodiments, such as that illustrated in [Fig.2], at least one software module is further associated with: - a data input format, - a data input connector, - a data output format, - a data output connector, the method further comprising: - a step 130 of buffering data, by the software execution orchestrator, according to a data output format and coming from a data output connector of a software module upstream, in the execution sequence, of a software module from which an error code comes, - a step 135 of detection, by the software execution orchestrator, of the absence of an error code coming from the software module from which an error code came, and - a step 140 of supplying data, by the software execution orchestrator, according to a data input format and to a data input connector of the software module from which the absence of an error code is detected.
[0070] The step 130 of buffering the data is carried out, for example, by using a memory 225 of the computer system 205. The step 130 of buffering buffer memory allows to perform the buffering of jobs by the sequence of remaining software modules that are subject to a particular error.
[0071] The detection step 135 is carried out, for example, by computer software executed by a computer system 205. During this detection step 135, for example, the absence of an error code is detected when an error code-emitting software module stops emitting an error code.
[0072] The data supply step 140 is carried out, for example, by using the data input connector, according to the data input format, of the software module for which an absence of error is detected.
[0073] In particular embodiments, such as that illustrated in [Fig.l], at least one software module is further associated with a set of instructions, at least one instruction being associated with a digital instruction identifier and an error code, the digital instruction identifier being further received during the reception step 120 and this digital instruction identifier being further provided during the provision step 135.
[0074] A set of instructions may be represented as a schematic succession of steps, such as that shown in [Fig. 1], each step corresponding to at least one instruction to be executed by a processor 210 of a computer system 205. Such a set of instructions may correspond to "codeless" programming software, such as Power Automate (registered trademark) from Microsoft (registered trademark). Such instructions may be independently associated with error codes so that, when a software module associated with several instructions issues an error code, this error code may be precisely linked to a particular set of instructions constituting this software module.
[0075] In particular embodiments, at least one software module or at least one software execution automation process is associated with an execution priority indicator, the execution step 115 being carried out as a function of the execution priority indicator of at least one said software module or software execution automation process.
[0076] Such a priority indicator may be set manually or automatically and may correspond to a numerical value that can be compared to other numerical values representative of the execution priority in order to determine which software module or software execution automation process should be executed first. This is particularly useful in the case where the execution of software execution automation processes has been interrupted due to an error and the execution must be resumed in the most optimized manner possible.
[0077] [Fig. 2] shows, schematically, a particular representation of the computer system 200 which is the subject of the present invention. This computer system 200 for monitoring a software execution automation, comprises: - one or more computer systems 205 comprising one or more hardware processors 210 and storage media 215; and - instructions stored in the storage medium and which, when executed by the computer system, cause the computer system to execute: - define, on a computer interface, at least two software modules, each software module being associated with: - a digital software identifier representative of existing software to be executed or of an application interface to be addressed, - a runtime error code output format, and - a runtime error code output connector, - a step 110 of defining, on a computer interface, an execution sequence of at least two software execution automation processes, each software execution automation process being associated with an execution sequence of at least one defined software module, - a step 115 of executing, by a software execution orchestrator executed on the computing device, the execution sequence of at least two software execution automation processes by executing the associated software sequence, - receiving, by the software execution orchestrator, an error code from a software module during execution, and - provide, on a computer interface, an output representative of the error code received and the digital identifier of the software associated with the software module that caused the error code.
[0078] Particular implementations of the features of this computer system 200 are disclosed with respect to [Fig.l].
[0079] [Fig. 3] schematically represents a graphical representation of a sequence of software modules corresponding to a succession of business processes, 301 and 302, of automation. A first automation process 301 comprises a succession of software modules, 305, 310 and 315. One of the software modules 315 further comprises three lower level software modules, 325, 330 and 335. Several software modules, 310, 315 and 325, are executed automatically while a software module 330 requires manual validation of the output or execution, a software module 335 is deferred in its execution and a software module 305 is executed by third-party software. Two software modules, 310 and 335, are associated with an API, as indicated by a 311 flag, while two other software modules, 325 and 300, are associated with a Microsoft Power Automate platform instruction flow. The execution type is indicated by a 306 flag.One of the software modules 310 interacts with a database 320 via an APL One of the . software modules 315 uses an authentication means, such as a password, to access a resource on a computing device. In this case, a software module 315 issues an error code corresponding to an incorrect password blocking the execution of the sequence of software modules.
[0080] A second software automation process 302, executed in series or in parallel to the first second software automation process 301, comprises two automatically executed software modules, 345 and 350. Statement of the invention
[0081] The present invention aims to remedy all or part of the drawbacks mentioned above.
[0082] All embodiments disclosed and claimed herein relate to computer-implemented programmed processes that interact with digital data to provide a practical application of computer technology to the problem of monitoring software automation that can be used to increase the responsiveness of an enterprise's IT department. The disclosure is not intended to encompass techniques for organizing human activity, executing mental processes, or executing a mathematical concept, and any interpretation of the claims to encompass such techniques would be unreasonable based on the disclosure as a whole.
[0083] To this end, according to a first aspect, the present invention aims at a computer-implemented method for monitoring the automation of software execution, comprising: - a step of defining, on a computer interface, at least two software modules, each software module being associated with: - a digital software identifier representative of existing software to be executed or of an application interface to be addressed, - a runtime error code output format, and - a runtime error code output connector, - a step of defining, on a computer interface, an execution sequence of at least two software execution automation processes, each software execution automation process being associated with an execution sequence of at least one defined software module, - a step of executing, by a software execution orchestrator executed on a computing device, the execution sequence of at least two software execution automation processes by executing the associated software sequence, - a step of receiving, by the software execution orchestrator, an error code from a software module during execution, and - a step of providing, on a computer interface, an output representative of the error code received and the digital identifier of the software associated with the software module at the origin of the error code.
[0084] Such arrangements allow users to monitor software execution errors and to be informed of the existence of errors as well as the origin of these errors within the automated process. The advantages of such arrangements are mentioned in the summary of the present invention subsection of this document.
[0085] In particular embodiments, at least one software module is further associated with: - a data input format, - a data input connector, - a data output format, - a data output connector, the method further comprising: - a data buffering step, by the software execution orchestrator, according to a data output format and coming from a data output connector of a software module upstream, in the execution sequence, of a software module from which an error code comes, - a step of detection, by the software execution orchestrator, of the absence of an error code coming from the software module from which an error code came, and - a data supply step, by the software execution orchestrator, according to a data input format and to a data input connector of the software module from which the absence of an error code is detected.
[0086] Such embodiments allow the process to maintain operational efficiency until the error is resolved, without disrupting other software components of the process.
[0087] In particular embodiments, at least one software module is further associated with a set of instructions, at least one instruction being associated with a digital instruction identifier and an error code, the digital instruction identifier being further received during the receiving step and this digital instruction identifier being further provided during the providing step.
[0088] Such embodiments make it possible to accurately determine the origin of the error code, which facilitates maintenance and repairs of the software module responsible for the failure of the process automation.
[0089] In particular embodiments, the method which is the subject of the present invention comprises a step of storing, by the software execution orchestrator, for at least one software module, authentication information, the execution step, for said software module, being carried out as a function of the authentication information. stored.
[0090] Such embodiments allow for on-demand authentication of users implementing the automation of the process without requiring input from the user.
[0091] In particular embodiments, at least one software module is further associated with a validation type, said execution type being at least either manual, deferred, orchestrated, or automatic, the execution step further comprising, if the corresponding software module is associated with a manual validation type, a step of validation by the user of the execution carried out by the software module.
[0092] Such embodiments make it possible to define the automation of autonomous, semi-autonomous or manual processes.
[0093] In particular embodiments, at least one software module or at least one software execution automation process is associated with an execution priority indicator, the execution step being carried out as a function of the execution priority indicator of at least one said software module or software execution automation process.
[0094] Such embodiments make it possible to optimize the allocation of computing resources from the highest execution priorities to the lowest priorities.
[0095] In particular embodiments, at least one software module is a robotic process automation.
[0096] In particular embodiments, at least one software module is an application programming interface.
[0097] According to a second aspect, the present invention aims at a computer system for monitoring software execution automation, comprising: - one or more computer systems (205) comprising one or more hardware processors (210) and storage media (215); and - instructions stored in the storage medium and which, when executed by the computer system, cause the computer system to execute: - a step of defining, on a computer interface, at least two software modules, each software module being associated with: a digital software identifier representative of existing software to be executed or an application interface to be addressed, - a runtime error code output format, and - a runtime error code output connector, - a step of defining, on a computer interface, an execution sequence of at least two software execution automation processes, each software execution automation process being associated with an execution sequence of at least one defined software module, - a step of executing, by a software execution orchestrator executed on a computing device, the execution sequence of at least two software execution automation processes by executing the associated sequence of software, - a step of receiving, by the software execution orchestrator, an error code from a software module during execution, and - a step of providing, on a computer interface, an output representative of the error code received and the digital identifier of the software associated with the software module at the origin of the error code.
Claims
Claims
1. A computer-implemented method (100) for monitoring automation of software execution, comprising: - a step (105) of defining, on a computer interface, at least two software modules, each software module being associated with: - a digital software identifier representative of existing software to be executed or of an application interface to be addressed, - a runtime error code output format, and - a runtime error code output connector, - a step (110) of defining, on a computer interface, an execution sequence of at least two software execution automation processes, each software execution automation process being associated with an execution sequence of at least one defined software module, - a step (115) of executing, by a software execution orchestrator executed on a computing device, the execution sequence of at least two software execution automation processes by executing the associated software sequence, - a step (120) of receiving, by the software execution orchestrator, an error code coming from a software module during execution, and - a step (125) of providing, on a computer interface, an output representative of the error code received and the digital identifier of the software associated with the software module at the origin of the error code.
2. Method (100) according to claim 1, wherein at least one software module is further associated with: - a data input format, - a data input connector, - a data output format, - a data output connector, the method further comprising: - a step (130) of buffering data, by the software execution orchestrator, according to a data output format and coming from a data output connector of a software module upstream, in the execution sequence, of a software module from which an error code comes, - a step (135) of detection, by the execution orchestrator of software, of the absence of an error code coming from the software module from which an error code came, and - a step (140) of feeding data, by the software execution orchestrator, according to a data input format and to a data input connector of the software module from which the absence of an error code is detected.
3. Method (100) according to claim 1, in which at least one software module is further associated with a set of instructions, at least one instruction being associated with a digital instruction identifier and an error code, the digital instruction identifier being further received during the receiving step (120) and this digital instruction identifier being further provided during the providing step (125).
4. Method (100) according to claim 1, which comprises a step (145) of storing, by the software execution orchestrator, for at least one software module, authentication information, the step (115) of execution, for said software module, being carried out according to the stored authentication information.
5. Method (100) according to claim 1, in which at least one software module is further associated with a validation type, said validation type being associated with at least one execution type, either manual, deferred, orchestrated or automatic, the execution step (115) further comprising, if the corresponding software module is associated with a manual validation type, a step (150) of validation by the user of the execution carried out by the software module.
6. Method (100) according to claim 1, wherein at least one software module or at least one software execution automation process is associated with an execution priority indicator, the execution step (115) being carried out according to the execution priority indicator of at least one said software module or software execution automation process.
7. The method (100) of claim 1, wherein at least one software module is robotic process automation software.
8. The method (100) of claim 1, wherein at least one software module is an application programming interface.
9. A computer system (200) for monitoring software execution automation, comprising: - one or more computer systems (205) comprising one or more hardware processors (210) and storage media (215); And - instructions stored in the storage medium and which, when executed by the computer system, cause the computer system to execute: - a step of defining, on a computer interface, at least two software modules, each software module being associated with: - a digital software identifier representative of existing software to be executed or of an application interface to be addressed, - a runtime error code output format, and - a runtime error code output connector, - a step of defining, on a computer interface, an execution sequence of at least two software execution automation processes, each software execution automation process being associated with an execution sequence of at least one defined software module, - a step of executing, by a software execution orchestrator executed on a computing device, the execution sequence of at least two software execution automation processes by executing the associated software sequence, - a step of receiving, by the software execution orchestrator, an error code from a software module during execution, and - a step of providing, on a computer interface, an output representative of the error code received and the digital identifier of the software associated with the software module at the origin of the error code.
