JP2011243013A - Execution control method for screen operation, server and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a technology for returning to a state before the initial screen operation when an error has occured in executing a plurality of screen operations in a plurality of existing systems indelendelty executing jobs as a sequential work.SOLUTION: A server acquires screen operation information required for executing a sequential job and business procedure information from another computer to register the information in a storage part, and acquires screen operation information for placing the screens of existing systems back to the state before executing jobs from the computer and registers the information in the storage part. When the server receives a start request for the execution of jobs from the computer, the server executes screen operations and registers the execution state in the storage part. If the server detects an error during execution of the screen operations, the server puts the screens of the existing systems back to the state before executing jobs based on the information registered in the storage part.

Description

  The present invention relates to a technique for executing operations on a plurality of screens of a plurality of existing systems that independently execute a task as a series of tasks.

  Conventionally, a mechanism for executing a series of processes for a plurality of systems has been studied. However, they are realized by calling the module processing inside the system, and the module processing cannot be called unless the details of the internal specifications of the system to be executed in a series are known. Therefore, there is a need for a mechanism that can execute a plurality of systems in series if the external specifications of screen operation are known, even if the details of the internal specifications of the system are not known.

  For example, Patent Document 1 discloses a technique for executing a plurality of system processes in series.

JP 2001-34595 A

  As a series of tasks, a person may manually input the same content on multiple screens of an existing system. In some cases, the efficiency of the series of operations can be improved by giving only input data and automatically performing each screen input operation. However, with the existing technology, it is possible to perform a series of input operations on multiple screens by passing input data. However, if an error occurs in the middle of the process, the series of business data ends in an inconsistent state. Therefore, it is necessary to return the data to the state before the execution of the series of processes and re-execute after confirming the error occurrence state through human intervention.

  This means that if an error occurs on an intermediate screen, the screen being processed at the time of the error can be returned to the state before the start by the transaction control function of the screen itself, but it is returned to the state before the start of the already executed screen operation. Caused by the inability to. This is because when one screen process is completed, the processing result data is written in the database and determined. Note that the technique described in Patent Document 1 does not mention a mechanism for executing a process for executing and recovering a series of tasks based on screen processing.

  However, when a series of tasks are completed for the first time by executing all the screens in order, it is necessary to be able to execute and return the multi-screen operation consistently (as one transaction). If it stops in the business state at the time of the error occurrence, the processing result data will be in a half-finished state that is neither the state when the series of business is completed nor the state before the business is executed. For example, when registering product information, out of the product name, business partner, price, and expiration date that are mandatory for product information, “Product name and business partner are registered as data, but the price and expiration date are included. A product may be registered in a state such as “No.”. In this case, there should be only a state where this product is not registered or a state where all information is registered.

  The present invention has been made in view of the above circumstances, and when an error occurs during the execution of a plurality of screen operations of a plurality of existing systems that perform operations independently as a series of operations, the first screen operation is performed. It is an object to provide a technique for returning to the previous state.

  One means for solving the above problem will be described. The present invention is characterized in that a server that executes a plurality of screen operations of a plurality of existing systems that independently execute a task as a series of tasks performs the following processing. The server includes a control unit and a storage unit, and the control unit acquires screen operation information necessary for execution of a series of business operations together with business procedure information from another computer, registers it in the storage unit, and stores the other When the screen operation information for returning the screen of the existing system to the state before the business execution is acquired from the computer and registered in the storage unit, and the business execution start request is received from the other computer, When the operation is executed, the execution state is registered in the storage unit, and an error is detected during the operation of the screen, the screen of the existing system is executed based on the information registered in the storage unit. It is characterized by returning to the previous state.

  According to the present invention, when an error occurs during the operation of a plurality of screens of a plurality of existing systems that independently execute a task as a series of tasks, the state before the first screen operation can be restored.

It is a figure which shows the example of an entire structure of the execution system of a series of work which consists of several screens of the existing system. 2 is a diagram illustrating a hardware configuration example of an execution control server 10. FIG. 3 is a diagram illustrating an example of a hardware configuration of an execution control information registration terminal 11. FIG. It is a figure which shows the hardware structural example of the existing system screen operation | movement terminal 12. FIG. FIG. 3 is a diagram illustrating a hardware configuration example of a series of business execution terminals 13. It is the figure which showed the flow of processing of the execution system of the series of business which consists of several screens of the existing system. It is a figure which shows the example of a data structure of operation target screen DB214 which the execution control server 10 comprises. It is a figure which shows the data structural example of business name registration DB215 which the execution control server 10 comprises. It is a figure which shows the data structural example of operation name registration DB216 which the execution control server 10 comprises. It is a figure which shows the example of a data structure of operation content registration DB217 which the execution control server 10 comprises. It is a figure which shows the example of a data structure of business execution order registration DB218 which the execution control server 10 comprises. It is a figure which shows the data structural example of operation state DB219 which the execution control server 10 comprises. It is a figure which shows the example of the operation target screen object acquisition screen displayed on the display part 403 of the existing system screen operation terminal 12. FIG. It is a figure which shows the example of an operation target screen object acquisition result screen displayed on the display part 403 of the existing system screen operation terminal 12. FIG. It is a figure which shows the example of an operation name registration screen displayed on the display part 303 of the execution control information registration terminal 11. FIG. It is a figure which shows the example of a business screen operation registration screen displayed on the display part 303 of the execution control information registration terminal 11. FIG. It is a figure which shows the example of a business name registration screen displayed on the display part 303 of the execution control information registration terminal 11. FIG. It is a figure which shows the example of a business screen order registration screen displayed on the display part 303 of the execution control information registration terminal 11. FIG. It is a figure which shows the example of a series business execution call screen displayed on the display part 503 of the series business execution terminal 13. FIG. It is a figure which shows the example of a series business execution call result (normal) screen displayed on the display part 503 of the series business execution terminal 13. FIG. It is a figure which shows the example of a series business execution call result (error) screen displayed on the display part 503 of the series business execution terminal 13. FIG. It is a flowchart which shows the detail of the work screen operation execution process (step S511) shown in FIG. 6 among the execution control processes 212 of the execution control server 10. It is a flowchart which shows the detail of the operation execution process at the time of an error shown in FIG. 6 among the execution control processes 212 of the execution control server 10 (step S513).

  Hereinafter, an embodiment of the present invention will be described in detail with reference to the drawings.

  FIG. 1 is a diagram illustrating a configuration example of an entire execution system for a series of tasks including a plurality of screens of an existing system according to the present embodiment.

  The execution system 1 for a series of business operations is configured by an execution control server 10, an execution control information registration terminal 11, an existing system screen operation terminal 12, and a series of business execution terminals 13 connected to a network 14.

  The execution control server 10 manages the screen operation procedure and contents of a series of tasks, and performs execution control of existing system screens based on the contents.

  The execution control information registration terminal 11 is a terminal for inputting the execution order of the existing system screens to be executed as a series of operations and the operation contents / procedures of each screen. The input information is transmitted to the execution control server 10 and stored in the database. be registered.

  The existing system screen operation terminal 12 is a terminal on which an existing system screen executed as a series of operations operates. The existing system screen operation terminal 12 acquires the object information (object ID, object name, etc.) of the existing system screen operating on this terminal and transmits it to the execution control server 10. The transmitted information is registered in the database by the execution control server 10. In the present embodiment, the product information registration work will be described as an example of a series of work. As an example of an existing system operation, product attribute registration and product price registration of an existing system are performed in series. A product attribute registration / deletion process and a product price registration / deletion process on the existing system screen operation terminal 12 are executed from the execution control server 10.

  The series of business execution terminals 13 is a terminal that calls an existing system screen and executes it as a series of business. In the present embodiment, a product information registration operation will be described as an example of a series of operations. When the product information registration job is executed on the product attribute price registration screen from the series of business execution terminals 13, the product attribute registration and product price registration of the existing system are executed in series via the execution control server 10. Also, if an error occurs during the execution of the product attribute registration and product price registration of the existing system, an error is displayed on the error display screen.

  FIG. 2 is a diagram illustrating a hardware configuration example of the execution control server 10.

  The execution control server 10 includes a control unit 200, a storage unit 201, an input unit 202, a display unit 203, and a network interface unit 204. Each unit is connected by a bus (BUS). In the storage unit 201, a program 210 including a control data registration process 211, an execution control process 212, and a screen object registration process 213, an operation target screen database (hereinafter, “database” is referred to as “DB”) 214, business name registration A DB 215, an operation name registration DB 216, an operation content registration DB 217, a business execution order registration DB 218, and an operation state DB 219 are stored. The program 210 is loaded from the storage unit 201 to a memory (not shown) by the control unit 200 and executed.

The control data registration process 211 is called from the business name registration screen function 311, business screen order registration screen function 312, operation name registration screen function 313, business screen operation registration screen function 314 of the execution control information registration terminal 11, and business name registration is performed. DB 215, operation name registration DB 216, operation content registration DB 217, business execution order registration DB 218, product attribute registration screen function 411, product attribute deletion screen function 412, product price registration screen function 413, product price cancellation of existing system screen operation terminal 12 It has a function of registering control information necessary for operating the screen function 414.

  The execution control process 212 is called from the series of business execution call screen functions of the series of business execution terminals 13 and refers to the existing system screen while referring to the business name registration DB 215, operation name registration DB 216, operation content registration DB 217, and business execution order registration DB 218. The product attribute registration screen function 411, the product attribute deletion screen function 412, the product price registration screen function 413, and the product price cancellation screen function 414 of the operating terminal 12 are operated, and the execution result is updated to the operation state DB 219.

  The screen object registration process 213 is called from the operation target screen object acquisition screen function 415 of the existing system screen operation terminal 12, and the product attribute registration screen function 411 and the product attribute deletion screen function which are existing system screens of the existing system screen operation terminal 12. 412, a product price registration screen function 413, and a product price cancellation screen function 414, and a function of registering information necessary for operating an object on the screen in the operation target screen DB 214.

  FIG. 3 is a diagram illustrating a hardware configuration example of the execution control information registration terminal 11.

The execution control information registration terminal 11 includes a control unit 300, a storage unit 301, an input unit 302, a display unit 303, and a network interface unit 304. Each unit is connected by a bus (BUS). The storage unit 301 stores a program 310 including a business name registration screen function 311, a business screen order registration screen function 312, an operation name registration screen function 313, and a business screen operation registration screen function 314. The program 310 is loaded from the storage unit 301 to a memory (not shown) and executed by the control unit 300.

  The business name registration screen function 311 has a function of calling the control data registration processing 211 of the execution control server 10 and registering business names to be executed in series.

  The business screen order registration screen function 312 has a function of calling the control data registration processing 211 of the execution control server 10 and registering the execution order of existing system screens executed in a series of business operations.

  The operation name registration screen function 313 has a function of calling the control data registration processing 211 of the execution control server 10 and registering the name of a series of operations on the existing system 1 screen executed in a series of operations to be executed.

  The business screen operation registration screen function 314 has a function of calling the control data registration processing 211 of the execution control server 10 and registering the contents of a series of operations on the existing system 1 screen executed in a series of business execution.

  FIG. 4 is a diagram illustrating a hardware configuration example of the existing system screen operation terminal 12.

  The existing system screen operation terminal 12 includes a control unit 400, a storage unit 401, an input unit 402, a display unit 403, and a network interface unit 404. Each unit is connected by a bus (BUS). The storage unit 401 stores a product attribute registration screen function 411, a product attribute deletion screen function 412, a product price registration screen function 413, a product price cancellation screen function 414, and an operation target screen object acquisition function 415. Yes. The program 410 is loaded from the storage unit 401 to a memory (not shown) by the control unit 400 and executed.

  The product attribute registration screen function 411 is a screen program of the existing system and has a function of registering attributes of purchased products such as business partners and expiration dates.

  The product attribute deletion screen function 412 is a screen program of the existing system, and has a function of deleting attributes of purchased products such as business partners and expiration dates.

  The product price registration screen function 413 is a screen program of the existing system, and has a function of registering price information of purchased products such as cost and selling price.

  The product price cancellation screen function 414 is a screen program of the existing system and has a function of canceling price information of purchased products such as cost and selling price.

  The operation target screen object acquisition function 415 includes a product attribute registration screen function 411, a product attribute deletion screen function 412, a product price registration screen function 413, and a product price cancellation screen function 414 of an existing system screen operating on the same terminal. It has a function of acquiring information necessary for operating the screen and objects on the screen, and calling and registering the screen object registration processing 213 of the execution control server 10.

  FIG. 5 is a diagram illustrating a hardware configuration example of the series of business execution terminals 13.

  The series of business execution terminals 13 includes a control unit 500, a storage unit 501, an input unit 502, a display unit 503, and a network interface unit 504. Each unit is connected by a bus (BUS). The storage unit 501 stores a program 510 including a series of business execution call screen function 511 and an error display screen function 512. The program 510 is loaded from the storage unit 501 to a memory (not shown) by the control unit 500 and executed.

  FIG. 6 is a diagram showing a flow of processing of the entire execution system for a series of tasks composed of a plurality of screens of the existing system.

  First, information necessary for operating the screen of the existing system is acquired from the existing system screen operating terminal 12 and stored in the DB (steps S501 to 502).

  The operation target screen object acquisition process (step S501) is executed on the existing system screen operation terminal 12. The operation target screen object acquisition process (step S501) is an existing system that operates on the existing system screen operation terminal 12. For example, “product attribute registration screen function 411, product attribute deletion screen function 412, product price registration screen function 413, product price cancellation” All the screen IDs, screen names, object IDs, object names, and operations of screen objects (screens, text boxes, buttons, etc.) necessary for operating the “screen function 414” are acquired, and the operation target screen DB 214 of the execution control server 10 is acquired. Register with.

  The flow of the operation target screen object acquisition process (step S501) will be described. In the state where the existing system screen is activated on the existing system screen operation terminal 12, the “(re) acquire” button is displayed on the operation target screen object acquisition screen shown in FIG. By pressing, a screen object (screen, text box, button, etc.) is acquired, and screen ID, screen name, object ID, object name, and operation are displayed in a list. By checking the items to be registered from the list displayed and pressing the registration button, the input information is stored in the screen ID 701, the screen name 702, the object ID 703, the object name 704, and the operation 705 of the operation target screen DB 214. The The execution control server 10 transmits the registration result to the existing system screen operation terminal 12 based on the screen object registration result (step S502). As a result, the number of registration results and the normal end are displayed on the operation target screen object acquisition screen shown in FIG. Specifically, the screen ID and the object ID can be acquired by acquiring the window ID and name of the screen from the OS. Similarly, with the existing system screen activated, the object ID, object name, and operation are acquired as the operation content from the OS, the object ID and its object name on the window ID of the screen, and the method of the object ID. To do.

  Next, the screen operation contents of the existing system necessary for performing the product information registration work as a series of work are registered in the DB from the execution control information registration terminal 11 (steps S503 to 508). On the execution control information registration terminal 11, a screen object information request (step S503) is executed. The screen object information request (step S503) is performed for all operation target screen object information screen IDs 701, screen names 702, object IDs 703, and object names registered in the operation target screen DB 214 with respect to the operation target screen DB 214 of the execution control server 10. 704, request to obtain the operation 705. The execution control server 10 acquires the screen ID 701, the screen name 702, the object ID 703, the object name 704, and the operation 705 from the operation target screen DB 214, and transmits them to the execution control information registration terminal 11 (step S504).

  Then, the execution control information registration terminal 11 executes a business screen operation registration process (step S505). In this business screen operation registration processing, the operation content necessary for carrying out the business is registered in the operation name registration DB 216 and the operation content registration DB 217 of the execution control server 10 with the operation name registered in units of screens of the existing system. In this processing, first, an operation name is input on the operation name registration screen shown in FIG. 15, and the operation ID 901 automatically assigned and the input operation name 902 are stored in the operation name registration DB 216. Next, an operation ID 901 (hidden) and operation name 902 read from the operation name registration DB 216 on the operation screen operation registration screen shown in FIG. 16 are selected, and a series of screen operations necessary for the operation read from the operation target screen DB 214 ( Screen ID 701 (non-display), screen name 702, object ID 703 (non-display), object name 704, operation 705) are selected and registered in the operation content registration DB 217 in the order of operation execution. At this time, the screen input content is stored in the operation content registration DB 217 using the operation ID 1001 and the operation execution order 1002 as keys. If an error occurs, the existing system performs transaction control in units of screen processing, and if an operation content is registered in the operation content registration DB 217 for each screen of the existing system, an error occurs during the operation. However, it is possible to return to the state before the operation with the function of the existing system. In addition, the screen operation content of the existing system for performing the operation and returning to the operation is registered in the operation content registration DB 217 with the operation name as described above. This operation is used for return processing when an error occurs during the execution of a series of tasks. For example, a product attribute registration operation in the product attribute registration screen function is registered, and a deletion operation in the product attribute deletion screen function is registered as a return process when an error occurs. As a task following product attribute registration, registering the product price registration operation with the product price registration screen function, and registering the cancellation operation with the product price cancellation screen function as the return processing when the error occurs is considered It is done.

  The execution control server 10 transmits the business screen operation registration result to the execution control information registration terminal 11 (step S506).

  Then, the execution control information registration terminal 11 executes a business screen order registration process (step S507). In this business screen order registration process, a series of business names and operations necessary for performing the business are specified and registered in the business name registration DB 215 and the business execution order registration DB 218 of the execution control server 10. The operation necessary to cancel the registered operation and return to the state before the operation is also registered as the return operation. In this process, first, a business name is input on the business name registration screen shown in FIG. 17, and the business ID 801 automatically numbered and the input business name 802 are stored in the business name registration DB 215. Next, the business ID 801 (hidden) and business name 802 read from the business name registration DB 215 on the business screen order registration screen shown in FIG. 18 are selected, and the operation ID 901 (hidden) and operation name read from the operation name registration DB 216 are selected. 902 is selected one by one for a series of operations required for the business and a corresponding return operation (here, “operation” is an operation registered on the business screen operation registration screen shown in FIG. 16), and registered in the order of business execution. To do. At this time, the screen input content is stored in the operation ID 1103 and the return operation ID 1104 in the business execution order registration DB 218 using the business ID 1101 and the business execution order 1102 as keys. The operation registered here is the operation content of the screen unit of the existing system registered in the business screen operation registration process. For example, the product attribute registration operation is registered in the business execution order 1, and the product price registration operation is registered in the business execution order 2. Further, as a return process when an error occurs, a product attribute deletion operation may be registered in the business execution order 1 and a product price cancellation operation may be registered in the business execution order 2. The business screen order registration result is transmitted to the execution control information registration terminal 11 (step S508).

  Finally, product information registration work is performed as a series of work from the series of business execution terminals 13 (steps S509 to S514).

  The series of business execution terminals 13 selects a series of business to be performed, and executes a series of business execution calls (step S509). In response to the execution call, the execution control server 10 executes a business screen operation execution call and a business screen operation (steps S510 and S511). In this process, first, the business ID 801 (not shown) and the business name 802 of the business name registration DB 215 are selected and executed on the series of business execution call screen shown in FIG. As a result, when the series of tasks is completed normally, as shown in FIG. 20, a message “successfully completed” is output, and when an error occurs during the sequence of tasks, the sequence shown in FIG. The message “An error has occurred” is output.

  The business screen operation execution process (step S511) refers to the business name registration DB 215, operation name registration DB 216, operation content registration DB 217, and business execution order registration DB 218 of the execution control server 10, and performs a series of operations on the existing system screen operation terminal 12. Execute screen operations for existing systems registered as business. Details of this process (step S511) are shown in the flowchart of FIG.

  The existing system screen operation terminal 12 executes and controls the execution result of the business screen operation every time the operation registered in the business execution order registration DB 218 is normally completed or when an error occurs during execution on the existing system screen. It transmits to the server 10 (step S512). When the operation is normally completed, the status of the corresponding job execution order in the operation state DB 219 is updated to 1 (executed). The execution control server 10 transmits a series of business execution results to the series of business execution terminals 13 when the execution of all screen operations is completed or when an error occurs during execution on the existing system screen (step S512). When the execution control server 10 receives the execution result indicating that an error has occurred, the execution control server 10 performs the operation execution at the time of error (step S513), the operation state DB 219, the operation content registration DB 217 of the execution control server 10, and the job execution order. Referring to the registration DB 218, the return operation ID of the business execution order registration DB 218 corresponding to the business execution order in which the status of the operation state DB 219 is 1 (executed) is executed in descending order of the business execution order. The content of the return operation refers to the corresponding operation ID in the operation content registration DB 217 and executes the corresponding operation. Details of this process (step S513) are shown in the flowchart of FIG. The error operation execution result is transmitted to the execution control server 10 (step S514).

  FIG. 7 is a diagram illustrating a data configuration example of the operation target screen DB 214 included in the execution control server 10.

  The operation target screen DB 214 is a DB that stores screens necessary for operating the existing system and objects on the screen, and receives screens and object information of the existing system operating on the existing system screen operation terminal 12. It is updated by the control data registration process 211. As illustrated in FIG. 7, the operation target screen DB 214 stores a screen ID 701, a screen name 702, an object ID 703, an object name 704, and an operation 705 in association with each other. Here, the screen ID 701 is a number assigned by the OS in units of screens of the existing system, and one or more object IDs 703 existing in the screen are associated with the screen ID 701. Further, one or more methods are associated with the object ID 703 as the method 705 of the object. Keys of the operation target screen DB 214 are a screen ID 701, an object ID 703, and an operation 705.

  FIG. 8 is a diagram illustrating a data configuration example of the business name registration DB 215 included in the execution control server 10.

  The business name registration DB 215 is a DB that stores names corresponding to business contents that can be realized by operating each screen of the existing system in series, and the business name registration screen function 311 that is running on the execution control information registration terminal 11. Is received by the control data registration process 211 and is updated. As shown in FIG. 8, the business name registration DB 215 stores a business ID 801 and a business name 802 in association with each other. Here, the business ID 801 is a serial number acquired by the system, and the business name 802 is a name corresponding to the business content that can be realized by operating a series of existing system screens. The key of the business name registration DB 215 is a business ID 801.

  FIG. 9 is a diagram illustrating a data configuration example of the operation name registration DB 216 included in the execution control server 10.

  The operation name registration DB 216 is a DB that stores names corresponding to a procedure for operating each screen of the existing system in series, and is a task input from the operation name registration screen function 313 operating on the execution control information registration terminal 11. The name is received and updated by the control data registration process 211. As illustrated in FIG. 9, the operation name registration DB 216 stores an operation ID 901 and an operation name 902 in association with each other. Here, the operation ID 901 is a serial number acquired by the system, and the operation name 902 is a name corresponding to a procedure for operating one screen of the existing system. The key of the operation name registration DB 216 is an operation ID 901.

  FIG. 10 is a diagram illustrating a data configuration example of the operation content registration DB 217 included in the execution control server 10.

  The operation content registration DB 217 is a DB that stores information indicating a procedure for operating each screen of the existing system in a series, and is a screen input by the business screen operation registration screen function 314 operating on the execution control information registration terminal 11. The operation content is received and updated by the control data registration process 211. As illustrated in FIG. 10, the operation content registration DB 217 stores an operation ID 1001, an operation execution order 1002, a screen ID 1003, an object ID 1004, an operation 1005, and input data 1006 in association with each other. Here, the operation ID 1001 is associated with the operation ID 901 registered in the operation name registration DB 216, and the screen ID 1003, the object ID 1004, and the operation 1005 are associated with the screen ID 701, the object ID 703, and the operation 705 of the operation target screen DB 214. The input data 1006 is registered when there is data to be input when the operation 705 is executed. The operation execution order 1002 registers the execution order of each screen operation for operating the screen in series. The keys of the operation content registration DB 217 are an operation ID 1001 and an operation execution order 1002.

  FIG. 11 is a diagram illustrating a data configuration example of the business execution order registration DB 218 included in the execution control server 10.

  The business execution order registration DB 218 is a DB that stores a business execution procedure that can be realized by operating each screen of the existing system in series, and is executed by the business screen order registration screen function 312 running on the execution control information registration terminal 11. The inputted job execution order is received and updated by the control data registration process 211. As illustrated in FIG. 11, the business execution order registration DB 218 stores a business ID 1101, a business execution order 1102, an operation ID 1103, and a return operation ID 1104 in association with each other. Here, the business ID 1101 is associated with the business ID 801 of the business name registration DB 215, and the operation ID 1103 and the return operation ID 1104 are associated with the operation ID 901 of the operation name registration DB 216. The business execution order 1102 registers the execution order of existing system operations for performing a series of business operations. Keys of the business execution order registration DB 218 are a business ID 1101 and a business execution order 1102.

  FIG. 12 is a diagram illustrating a data configuration example of the operation state DB 219 included in the execution control server 10.

  The operation state DB 219 is a DB that stores information indicating the execution state of the business execution procedure that can be realized by operating a series of existing system screens, and is updated by the execution control process 212. As illustrated in FIG. 12, the operation state DB 219 stores a business ID 1201, a business execution order 1202, and a status 1203 in association with each other. Here, the business ID 1201 and the business execution order 1202 are associated with the business ID 1101 and the business execution order 1102 of the business execution order registration DB 218. The status 1203 registers the execution state of the business execution procedure. “1” is registered for the procedure that has been executed, and “0” is registered for the procedure that has not been completed. The keys of the operation state DB 219 are a business ID 1201 and a business execution order 1202.

  FIG. 22 is a flowchart showing details of the business screen operation execution process (step S511) shown in FIG. 6 in the execution control process 212 of the execution control server 10.

  In the business screen operation execution process (step S511), the business ID transmitted from the series of business execution terminals 13 is received (step S5101), and the business execution order 1102 and the operation ID 1103 are received from the business execution order registration DB 218 using the business ID as a key. Read (step S5102).

  Next, the following is repeated until the business execution order 1102 reaches the maximum value in the ascending order of the business execution order 1102 read by the business ID 1101 (steps S5103 and S5111). When the job execution order 1102 reaches the maximum value, a normal end is transmitted to the series of job execution terminals 13 (step S5112). The process to be repeated is the following process.

  First, the screen ID 1003, object ID 1004, operation 1005, and input data 1006 are read from the operation content registration DB 217 using the operation ID 1103 as a key (step S5104), transmitted to the existing system screen operation terminal 12, and the screen corresponding to the screen ID 1003 of the existing system. An operation 1005 (input, click, etc.) is executed for the object (text box, button, etc.) corresponding to the object ID 1004. When the value of the operation 1005 is INPUT (input), the value of the input data 1006 is automatically input (step S5106). The operation execution result is received from the existing system screen operating terminal 12 (step S5107). If the operation execution result is an error, the error-time operation execution (step S513) shown in FIG. 6 is executed. If it is not an error, the operation execution order 1002 is incremented by 1, and the above procedure is executed in the same manner (step S5108). When the current operation ID reaches the maximum value of the operation execution order 1002 registered in the operation content registration DB 217, the execution is completed (steps S5105 and S5109). When the execution is completed, the status 1203 corresponding to the job ID 1201 and the job execution order 1202 in the operation status DB 219 is updated to 1 (“normal end”) (step S5110).

  FIG. 23 is a flowchart showing details of the error operation execution process (step S513) shown in FIG. 6 in the execution control process 212 of the execution control server 10.

  The operation execution upon error (step S513) is called from the business screen operation execution (step S510), and the business execution order 1202 is set to 1 in descending order of the business execution order 1202 from the operation status DB 219 using the current business ID as a key. Until it reaches (steps S5131, S5139), the status 1203 is read (step S5132). If the status 1203 is 0 (step S5133), the job execution order is decremented by 1, and the next status 1203 is read (step S5139).

  If the status 1203 is 1 (step S5133), the return operation ID 1104 is read from the operation execution order registration DB 218 using the business ID 1201 and the business execution order 1202 as keys (step S5134). Next, the screen ID 1003, the object ID 1004, the operation 1005, and the input data 1006 are read from the operation content registration DB 217 by associating the return operation ID 1104 with the operation ID 1001 of the operation content registration DB 217 (step S5135). The operation 1005 (input, click, etc.) is executed for the object (text box, button, etc.) corresponding to the screen object ID 1004 corresponding to the screen ID 1003 of the existing system (step S5137). If the operation 1005 is an input, the value of the input data 1006 is automatically input. When the current operation ID 1001 reaches the maximum value in the operation execution order 1002 registered in the operation content registration DB 217, the execution is completed (steps S5136 and S5138). When the execution is completed, the job execution order 1202 in the operation status DB 219 is decremented by 1, and the next status 1203 is read (steps S5131, S5139).

  When the job execution order 1202 reaches 1, an abnormal end of the job sequence is transmitted to the job sequence execution terminal 13 (step S5140).

  As mentioned above, although one embodiment of the present invention has been described, according to the above-described embodiment, an error has occurred during the operation of a plurality of screens of a plurality of existing systems that independently execute a task as a series of tasks. In this case, it is possible to return to the state before the first screen operation. As a result, it is possible to save the person from having to perform the return processing in consideration of the screen operation execution status until the time of the error occurrence, and the user can immediately re-execute with another input data.

  The present invention is not limited to the above-described embodiments, and various modifications can be made without departing from the scope of the invention.

DESCRIPTION OF SYMBOLS 10 ... Execution control server, 11 ... Execution control information registration terminal, 12 ... Existing system screen operation terminal, 13 ... Series operation execution terminal, 200, 300, 400, 500 ... Control part, 201, 301, 401, 501 ... Storage part 202, 302, 402, 502... Input unit, 203, 303, 403, 503... Display unit, 204, 304, 404, 504.

Claims (5)

A screen operation execution control method in a server that executes a plurality of screen operations of a plurality of existing systems that independently execute a task as a series of tasks,
The server includes a control unit and a storage unit,
By the control unit,
A process for acquiring screen operation information necessary for execution of a series of operations together with business procedure information from another computer and registering it in the storage unit;
A process of acquiring screen operation information for returning the screen of the existing system to the state before the business execution from the other computer and registering it in the storage unit;
When receiving the business execution start request from the other computer, the operation of the screen is executed, and the execution state is registered in the storage unit;
When an error is detected during the operation of the screen, based on the information registered in the storage unit, a process of returning the screen of the existing system to the state before the business execution is performed.
A screen operation execution control method. By the control unit,
Further, from the other computer, an object on the screen necessary for executing the operation of the plurality of screens of the existing system is acquired, and the screen of the existing system is acquired based on the screen operation information required for executing the series of tasks. To execute an operation of the screen by designating an object on the screen,
The screen operation execution control method according to claim 1. A server that executes multiple screen operations of multiple existing systems that execute tasks independently as a series of tasks,
A control unit and a storage unit;
The controller is
From other computers, screen operation information necessary for execution of a series of operations is acquired together with the operation procedure information and registered in the storage unit,
From the other computer, obtain the screen operation information for returning the screen of the existing system to the state before the business execution, and register it in the storage unit,
Upon receiving the business execution start request from the other computer, the operation of the screen is executed and the execution state is registered in the storage unit,
When an error is detected during the operation of the screen, the screen of the existing system is returned to the state before the business execution based on the information registered in the storage unit.
A server characterized by that. The controller is
Further, from the other computer, an object on the screen necessary for executing the operation of the plurality of screens of the existing system is acquired, and the screen of the existing system is acquired based on the screen operation information required for executing the series of tasks. Specify the object on the screen and execute the operation on the screen.
The server according to claim 3.   A program for controlling a computer to execute the screen operation execution control method according to claim 1.

Images