JP7532964B2 - Information processing device, control program, and control method - Google Patents

Description

Embodiments of the present invention relate to an information processing device, a control program, and a control method.

In recent years, with the spread of RPA (Robotic Process Automation) and other technologies, interest has been growing in automating and streamlining input processing for mainframes. Regarding the streamlining of data input into mainframes, a conventional technology is known that improves operability by generating programs that customize business screens.

JP 2004-355392 A JP 2008-97466 A JP 2010-108388 A

However, with the above-mentioned conventional technology, the creation of a program to customize a business screen requires a person with extensive knowledge of the business to create the program in accordance with the business operations, which is a difficult task, and there is a problem in that it is not easy to reduce the labor required for input processing.

In one aspect, the object is to provide an information processing device, a control program, and a control method that can help reduce the labor required for input processing.

In one proposal, the information processing device has a storage unit, a customization program creation unit, and an output unit. The storage unit stores, for the display screen, input operations involving screen transitions and transition information for the destination display screen resulting from the input operations, based on the display screen and a history of input operations on the display screen. The customization program creation unit creates a customization program that performs a screen transition from the source display screen to the destination display screen, based on the stored transition information. The output unit outputs, for the input display screen, a customization screen in which a display component is arranged that instructs the execution of a customization program with the input display screen as the source of the transition, in the created customization program.

It can help reduce the labor required for input processing.

FIG. 1 is an explanatory diagram for explaining an outline of an embodiment. FIG. 2 is an explanatory diagram for explaining a conventional example. FIG. 3 is a diagram illustrating an example of a system configuration according to the embodiment. FIG. 4 is a diagram showing an example of a user operation history. FIG. 5 is a diagram illustrating an example of the management information table. FIG. 6 is a diagram illustrating an example of the transition information table. FIG. 7 is a diagram illustrating an example of a customization program. FIG. 8 is a flowchart showing an example of a process related to the creation of a transition information table. FIG. 9A is an explanatory diagram for explaining a case where transition data is added. FIG. 9B is an explanatory diagram illustrating a case where the transition data is not changed. FIG. 9C is an explanatory diagram for explaining a case where transition data is changed. FIG. 10A is a flowchart showing an example of a process related to the creation of a customized program. FIG. 10B is a flowchart illustrating an example of a transition data process. FIG. 11 is a diagram showing a specific example of the transition information table. FIG. 12 is a block diagram showing an example of a computer configuration.

The information processing device, control program, and control method according to the embodiments will be described below with reference to the drawings. Components having the same functions in the embodiments will be given the same reference numerals, and duplicated descriptions will be omitted. Note that the information processing device, control program, and control method described in the following embodiments are merely examples, and do not limit the embodiments. In addition, the following embodiments may be combined as appropriate within a range that does not cause contradictions.

Figure 1 is an explanatory diagram outlining an embodiment. As shown in Figure 1, in this embodiment, a business screen G1a is output in which display components BT1 to BT3 are arranged for screen transition to a display screen for data input, etc., for a display screen such as a business screen G1 related to business processing provided by a mainframe. In other words, the business screen G1a is an example of a customized screen. The display components BT1 to BT3 are, for example, pull-down menus, operation buttons, etc., and instruct the execution of a customized program for screen transition to a business screen for data input, etc.

The customization program for the display components BT1 to BT3 is, for example, a script language that describes the operation content, and is created based on the input operations that accompany screen transitions on the business screen G1, and the transition information for the display screen to which the input operations lead. Specifically, transition information is accumulated from the user's operation history on the business screen G1, and based on this accumulated transition information, the program is created by combining input operations for screen transitions from the source business screen G1 to a display screen for data input, etc.

By outputting the business screen G1a with the display components BT1 to BT3 arranged in this way, the user can easily perform screen transitions to business screens for data entry, etc. by operating the display components BT1 to BT3.

FIG. 2 is an explanatory diagram for explaining a conventional example. As shown in FIG. 2, when performing a task such as data input by transitioning from business screen G1 to business screen G8, the screen transition is not easy because the key input for screen transition is different for each screen. In addition, to transition from business screen G1 to business screen G3 where data input is performed, first, the "Enter key" is operated on business screen G1 to transition to business screen G2. Next, the "2+Enter key" is operated on business screen G2 to transition to business screen G3. In this way, the screen transition from business screen G1 to business screen G3 cannot be performed directly, and the operation is complicated. Similarly, when transitioning from business screen G3 to business screen G7 where data input is performed next, the operation is complicated because the screen transition goes through business screens G4, G5, and G6 in order.

In contrast, in this embodiment, the business screen G1a, which has display components BT1 to BT3 arranged on it, improves operability when the user switches between display screens to input data, helping to reduce the labor required for input processing.

In this embodiment, an example is shown of customizing the business screen G1 provided by the mainframe, but the display screen to be customized is not limited to the business screen G1. For example, the display screen to be customized may be one that involves a screen transition due to an input operation. As an example, it may be applied to a guidance screen from which a transition is made that displays various kinds of guidance by providing guidance information on the display screen to which the transition is made.

Figure 3 is a diagram showing an example of a system configuration according to an embodiment. As shown in Figure 3, the system according to the embodiment has a mainframe 1, a server 2, and a client PC 3 (PC: Personal Computer). The mainframe 1, the server 2, and the client PC 3 are each connected to each other so as to be able to communicate with each other via a communication network such as a LAN (Local Area Network).

In this system, a display screen provided by an application program related to various business processes executed on the mainframe 1 is output to the client PC 3 via the server 2. An emulator 30 of the application program of the mainframe 1 runs on the client PC 3. The emulator 30 displays the display screen output from the mainframe 1 via the server 2 on a display or the like, and accepts input operations from the user. The emulator 30 also transmits input information related to the input operations received from the user to the mainframe 1 via the server 2. Furthermore, when the emulator 30 is instructed to execute a customization part 31 such as a customization program arranged on the display screen output from the server 2 in response to an input operation, it transmits input information corresponding to the execution to the mainframe 1 via the server 2.

The server 2 records the display screen from the mainframe 1 and input information related to the input operation accepted by the client PC 3 on the display screen as a user operation history D1. Next, the server 2 stores the input operation with screen transition and the transition information (transition data) of the display screen to which the input operation leads, for the display screen from the mainframe 1, in a transition information table D3 based on the user operation history D1. Next, the server 2 creates a customization program D4 by combining the input operation of the screen transition from the display screen of the transition source to the display screen for data input, etc., based on the transition data stored in the transition information table D3. As a result, the server 2 outputs a customization screen (Fig. 1, business screen G1a) in which display parts BT1 to BT3 are arranged to instruct the execution of a customization program with the display screen entered in the customization program D4 as the transition source, for the display screen entered from the mainframe 1 (Fig. 1, business screen G1). In other words, the server 2 is an example of an information processing device.

Specifically, the server 2 has a screen receiving unit 20, a screen recognition unit 21, a customized screen generation unit 22, a screen transmission unit 23, an input operation detection unit 24, a key input information transmission unit 25, a management information creation unit 26, a transition information creation unit 27, and a customized program creation unit 28.

The screen receiving unit 20 receives information (screen data) about the display screen provided by the mainframe 1 when it executes application programs related to various business processes. This screen data includes, for example, identification information (screen ID) that identifies the screen, as well as field information included in the screen and screen format information related to the screen format. The screen receiving unit 20 outputs the received screen data to the screen recognition unit 21 and registers it in the user operation history D1.

The screen recognition unit 21 performs a screen identification process based on the screen data received from the mainframe 1, and recognizes the display screen. Specifically, the screen recognition unit 21 recognizes the display screen based on the identification information included in the screen data. The screen recognition unit 21 outputs the screen data received from the mainframe 1 and the recognition result of the display screen to the customized screen generation unit 22.

The customized screen generating unit 22 generates a customized screen in which display components are arranged to instruct the execution of a customized program that uses the display screen input in the customized program D4 as the transition source for the display screen received and input from the mainframe 1. Next, the customized screen generating unit 22 outputs screen data of the generated customized screen to the screen transmitting unit 23. In other words, the customized screen generating unit 22 is an example of an output unit.

Specifically, the customization screen generation unit 22 identifies the input display screen, i.e., the source display screen, based on the display screen identification result in the screen recognition unit 21. Next, the customization screen generation unit 22 reads out a customization program in the customization program D4 that uses the identified display screen as the source, and embeds a display component that instructs execution of the read customization program in a field position that does not have data to display in the field information included in the screen data received from the mainframe 1. Next, the customization screen generation unit 22 outputs the screen data in which the display component is embedded to the screen transmission unit 23. Note that if there is no customization program in the customization program D4 that uses the identified display screen as the source, the customization screen generation unit 22 outputs the screen data received from the mainframe 1 as is to the customization screen generation unit 22.

The screen transmission unit 23 transmits the screen data output by the customized screen generation unit 22, i.e., the display screen from the mainframe 1, to the client PC 3.

The input operation detection unit 24 detects input operations on the client PC 3 by receiving information indicating an input operation performed by a user, which is sent from the emulator 30 of the client PC 3 together with a user name indicating the user and the group name of the group to which the user belongs. The input operations detected by the input operation detection unit 24 include key input performed by the user on the display screen from the mainframe 1, operations on display components arranged on the display screen, etc. For example, input operations include input operations for data input and input operations accompanied by a screen transition that instructs a transition to another display screen.

The key input information transmission unit 25 identifies key input information corresponding to the input operation detected by the input operation detection unit 24, and transmits transmission data including the identified key input information to the mainframe 1. The key input information identified by the key input information transmission unit 25 includes the key type, the key input position on the display screen, input data indicating the input content, etc.

The key input information transmitting unit 25 also stores the user name of the user related to the input operation, the group name of the group to which the user belongs, the screen data received by the screen receiving unit 20, and the date and time in the user operation history D1 together with the transmission data including the key input information. At this time, the key input information transmitting unit 25 assigns a sequence ID, such as assigning the same number to a series of input operations by the same user, in order to identify a series of input operations by one user.

Figure 4 is a diagram showing an example of user operation history D1. As shown in Figure 4, the user operation history D1 stores the operation history of each user in the emulator 30 of the client PC 3. Specifically, the user operation history D1 stores the user name, group name, screen data, transmission data, date and time, and sequence ID.

The user name is the name of the user related to the input operation in the emulator 30 of the client PC 3. The group name is the name of the group to which the user belongs. The screen data has screen information including field information (1) to (n) related to each of the fields included in the display screen.

Field information includes, for example, the field position (such as the row or column position to display), field attributes (such as display color, border attributes), and field data (such as display characters).

The transmission data has key input information corresponding to input operations including key type, key input position, and input data (1) to (n). The input data includes, for example, a field position and input data (such as a key operation) at the field position.

Returning to FIG. 3, the management information creation unit 26 generates data for the management information table D2 in response to input operations from the emulator 30 of the client PC 3. The management information table D2 is a table in which key input information and the like is set, which indicates the correlation between screen transitions between each display screen in the application program of the mainframe 1 and the contents of the input operations (such as key inputs) that realize the screen transitions between each display screen. In the customization program D4, the relevant information regarding multiple screen transitions is sequentially set as a screen transition history using a known method such as that disclosed in JP 2016-38693 A.

FIG. 5 is a diagram showing an example of the management information table D2. As shown in FIG. 5, the management information table D2 includes items of screen name, screen information, branch possibility flag, sub possibility flag, child screen, parent screen, screen transition key, and transition destination screen. The screen name is an identifier automatically assigned to each screen. The screen information includes, for example, the number of fields included in the screen and a list of position information of each field, and can be used to uniquely identify the screen (determine whether it is the same as the screen previously received). The branch possibility flag is a flag indicating whether the screen is a parent screen, that is, whether there is a possibility that it has a child screen. The sub possibility flag is a flag indicating whether the screen is a sub-screen that is a plurality of screens that have the same screen format and only the data to be displayed is different (for example, a screen that displays a detail line). The child screen indicates the screen name of the child screen when the screen is a parent screen. The parent screen indicates the screen name of the parent screen when the screen is a child screen. The transition destination screen is the screen to which the screen transitions next, and the screen transition key is key input information for transitioning to the transition destination screen. The data contents set in the branch possibility flag, sub possibility flag, child screen, parent screen, and transition destination screen items are examples of the correlation of screen transitions between each screen. Also, the data contents set in the child screen and parent screen items are examples of data indicating a parent-child hierarchical relationship in which a parent screen branches and transitions to multiple child screens.

Returning to FIG. 3, the transition information creation unit 27 accumulates, in a transition information table D3, transition information (transition data) for input operations involving screen transitions and the display screen to which the input operations lead, for the display screen from the mainframe 1, based on the display screen of the mainframe 1 and the user operation history D1 of input operations on the display screen. Specifically, the transition information creation unit 27 acquires a series of operation histories using a sequence ID for the operation history of the user/group to be processed in the user operation history D1. Next, based on the acquired operation history, the transition information creation unit 27 stores the transition data from a specific display screen to the display screen where data is entered, in the transition information table D3.

Figure 6 is a diagram showing an example of the transition information table D3. As shown in Figure 6, the transition information table D3 includes a transition start screen name indicating the display screen from which the transition occurs, and transition data D31 up to the display screen where data is input. The transition data D31 includes a transition destination screen which is the next transition destination display screen, and a screen transition key indicating an input operation involving a transition to the transition destination display screen. This transition data D31 is data connected so that it can be referenced sequentially up to the display screens where data is input (in the illustrated example, "Screen 7" and "Screen 4"). In addition, in the transition data D31, an end flag is set at the end indicating the screen transition to the display screen where data is input.

Returning to FIG. 3, the customization program creation unit 28 creates a customization program D4 that performs a screen transition from the source display screen to the destination display screen by combining input operations for screen transition from the source display screen to a display screen for data input, etc., based on the transition data in the transition information table D3.

Figure 7 is a diagram showing an example of a customization program D4. The example of customization program D4 shown in Figure 7 shows program code for performing a screen transition from "screen 1" that is the transition source to "screen 3" where data input, etc. is performed. As shown in Figure 7, the customization program creation unit 28 creates the customization program D4 by including in the program code an operation corresponding to the operation of the operation button of "screen 3" arranged on "screen 1". Specifically, in customization program D4, after transitioning to "screen 2" by operating "2" + "Enter", the program waits (Wait) until "screen 2" is displayed. Next, the customization program D4 shows an operation of transitioning to "screen 3" by operating "PF6" on "screen 2" and waiting (Wait) until "screen 3" is displayed.

Here, we will explain the details of the process for storing (creating) the transition information table D3. Figure 8 is a flowchart showing an example of the process for creating the transition information table D3.

As shown in FIG. 8, when processing starts, the transition information creation unit 27 performs a loop of processing related to the sequence ID until the target operation history is no longer present in the user operation history D1 (S1 to S14).

Specifically, when loop processing for a sequence ID is started (S1), the transition information creation unit 27 acquires operation history data for a series of input operations using the same sequence ID from the user operation history D1 (S2). Next, the transition information creation unit 27 acquires the screen name by referring to the management information table D2 (S3).

Next, the transition information creation unit 27 designates the screen name of the first operation history data as the start screen name of the reference destination in the transition information table D3, and designates the first operation history data as the start screen (S4). Next, the transition information creation unit 27 performs loop processing on the operation history data acquired in S2 until there is no more operation history data (S5 to S13).

Specifically, when loop processing of the operation history data is started, the transition information creation unit 27 determines whether the current transition destination screen name has already been stored in the transition data D31 of the transition information table D3 (S6).

If the current operation history data has not been stored in the transition data D31 (S6: No), the transition information creation unit 27 adds the current operation history data to the transition information table D3 (S7). Specifically, the transition information creation unit 27 adds transition data D31 to the transition information table D3, with the transmission data included in the operation history data as the screen transition key and the next screen name as the transition destination screen name. Next, the transition information creation unit 27 moves the reference position of the transition information table D3 to the target transition data D31 (S8), and moves the loop processing to the next operation history data.

If the data has already been stored in the transition data D31 (S6: Yes), the transition information creation unit 27 determines whether the transmission data in the current operation history data is different from the screen transition key included in the transition data D31 (S9). If the transmission data in the operation history data is the same as the screen transition key included in the transition data D31 (S9: No), the transition information creation unit 27 proceeds to S8.

If the transmission data and the screen transition key included in the transition data D31 are different (S9: Yes), the transition information creation unit 27 changes the screen transition key of the transition data D31 to the common part with the transmission data (S10). Next, the transition information creation unit 27 converts the target transition data D31 to a starting screen by setting the transition destination screen name of the target transition data D31 as the starting screen name (S11). In this way, the transition information creation unit 27 replaces the subsequent transition data D31, and then processes the next operation history data as the target (S12), and proceeds to S4. At this time, the transition information creation unit 27 assigns a terminal flag to the current transition data D31 indicating that it is a display screen for data input.

Figure 9A is an explanatory diagram for explaining a case where transition data D31 is added. Specifically, Figure 9A shows an example of a case where transition data D31 is added because the current transition destination screen name has not yet been stored in the transition data D31 of the transition information table D3. As shown in Figure 9A, in a series of operation history data, the display screen transitions from "Screen 1" to "Screen 2" by the input operation of "2 + Enter key".

At this time, the transition information creation unit 27 refers to the transition data D31 in the transition information table D3 (S21) and compares the transition destination screen name "Screen 7" with the screen name "Screen 2" in the operation history data (S22). In this case, since transition data D31 with the same screen name has not been stored, the transition information creation unit 27 adds new transition data D31 to the transition information table D3, with "Screen 2" as the transition destination screen name and the transmitted data of "2 + Enter key" as the screen transition key (S23). Next, the transition information creation unit 27 moves the reference destination in the transition information table D3 to the target transition data D31 (S24).

Figure 9B is an explanatory diagram illustrating a case where the transition data D31 is not changed. Specifically, Figure 9B shows an example of a case where the transition data D31 is not added because the current transition destination screen name and transmission data (screen transition key) are already stored in the transition data D31 of the transition information table D3. As shown in Figure 9B, in a series of operation history data, the display screen transitions from "Screen 1" to "Screen 7" with the input operation of "2 + Enter key".

At this time, the transition information creation unit 27 refers to the transition data D31 in the transition information table D3 (S31) and compares the transition destination screen name "Screen 7" with the screen name "Screen 7" in the operation history data (S32). In this case, because transition data D31 with the same screen name and screen transition key (transmission data) has already been stored (S33), the transition information creation unit 27 refers to the next transition data D31 in the transition information table D3 (S34).

Figure 9C is an explanatory diagram for explaining a case where transition data D31 is changed. Specifically, Figure 9C shows an example of a case where the current transition destination screen name is already stored in transition data D31 in transition information table D3, but the transmission data (screen transition key) is different, so the transition data D31 is changed. As shown in Figure 9C, in a series of operation history data, the display screen transitions from "Screen 1" to "Screen 11" by inputting "LOGON + Enter keys".

At this time, the transition information creation unit 27 refers to the transition data D31 in the transition information table D3 (S41) and compares the transition destination screen name "Screen 11" with the screen name "Screen 11" in the operation history data (S42). In this case, they are the same screen name. However, since the screen transition key and the transmission data are not the same (S43), the transition information creation unit 27 changes the screen transition key of the current transition data D31 to a common key input (S44). Specifically, the transition information creation unit 27 changes the "LOGON+Enter key" in the transmission data and the "2+Enter key" in the screen transition key of the current transition data D31 to the "Enter key" which is common to both. In addition, the transition information creation unit 27 assigns a terminal flag to the current transition data D31 as a data input screen. Next, the transition information creation unit 27 moves the reference destination of the transition information table D3 to the target transition data D31 (S45).

Next, the process for creating the customized program D4 will be described in detail. Figure 10A is a flowchart showing an example of the process for creating a customized program.

As shown in FIG. 10A, when processing starts, the customized program creation unit 28 reads the transition information table D3 (S50) and searches for the start screen name (S51). Next, the customized program creation unit 28 performs a loop process that repeats the number of times equal to the number of start screen names obtained from the transition information table D3 (S52 to S57).

Specifically, the customize program creation unit 28 searches for transition data D31 indicating the transition destination from the display screen of the start screen name to the display screen where data input, etc. is performed for the target start screen name (S53). Next, the customize program creation unit 28 determines whether or not there is transition data D31 of the transition destination by the search (S54), and if there is not (S54: No), the process returns to S52.

If there is transition data D31 for the transition destination (S54: Yes), the customize program creation unit 28 creates a process for when the customize program D4 to be created is pressed (S55), and executes transition data processing for data up to the transition data D31 to which the terminal flag has been added (S56). Next, the customize program creation unit 28 returns the process to S52 by repeating the loop process (S57), and after the loop process, ends the process related to the creation of the customize program D4.

Figure 10B is a flowchart showing an example of transition data processing. As shown in Figure 10B, when transition data processing is started, the customized program creation unit 28 replicates the process at the time of pressing the button a number of times equal to the number of transition data D31 (S60).

Next, the customized program creation unit 28 executes a loop process that repeats the number of times equal to the number of duplicated transition data D31 (S61 to S69), and ends the process.

Specifically, the customization program creation unit 28 adds a "screen transition key input" process (an action corresponding to the input operation of the screen transition key) to the processing when the key is pressed (S62). Next, the customization program creation unit 28 adds a "waiting for the transition destination screen name" process (a waiting action until the display screen appears in response to the input operation of the screen transition key) to the processing when the key is pressed (S63).

Next, the customize program creation unit 28 searches for the transition data D31 of the next transition destination (S64) and determines whether or not there is transition data D31 of the next transition destination (S65). If the end flag is not set and there is transition data D31 of the next transition destination (S65: Yes), the customize program creation unit 28 executes the same transition data processing for the transition data D31 of the next transition destination (S66).

If there is no transition data D31 for the next transition destination (S65: No), the customize program creation unit 28 adds a button creation process to the customize program D4 to be created, and stores the process to be performed when the button is pressed (S67). Next, the customize program creation unit 28 sets the display name of the button as the transition destination screen name for the customize program D4 to be created (S68), and returns the process to S61 by repeating the loop process (S69).

Figure 11 is a diagram showing a specific example of a transition information table. In the transition information table D3 illustrated in Figure 11, transition data D31 for a starting screen name of "Screen 1" includes "Screen 1" → "Screen 2" → "Screen 3" and "Screen 1" → "Screen 2" → "Screen 4". Here, we will explain a case where the customize program creation unit 28 creates a customize program D4 with "Screen 1" as the transition source.

First, the customize program creation unit 28 creates one process because there is one transition data D31 for "Screen 1". Next, the customize program creation unit 28 adds a process of inputting "2+Enter key" and waiting for "Screen 2" to the process when the customize program D4 to be created is pressed. Next, the customize program creation unit 28 continues the process because there is the next transition data D31.

Next, since there are two next transition data D31, the customize program creation unit 28 duplicates the process (the customize program D4 to be created) into two. First, for the transition data D31 of "Screen 3", the customize program creation unit 28 inputs the "F6 key" as the process to be performed when pressed, and adds a process to wait for "Screen 3" to the customize program D4 to be processed. Here, since there is no next transition data D31, the customize program creation unit 28 creates a "Screen 3" button and stores the process to be performed when pressed in the customize program D4 to be processed. In this way, the customize program creation unit 28 creates a customize program D4 that transitions the display screen from "Screen 1" → "Screen 2" → "Screen 3" by operating the "Screen 3" button.

Similarly, for the transition data D31 for "Screen 4," the customize program creation unit 28 inputs the "Enter key" as the process to be performed when the button is pressed, and adds a process to wait for "Screen 4" to the customize program D4 to be processed. Here, since there is no next transition data D31, the customize program creation unit 28 creates a "Screen 4" button and stores the process to be performed when the button is pressed in the customize program D4 to be processed. In this way, the customize program creation unit 28 creates a customize program D4 that transitions the display screen from "Screen 1" → "Screen 2" → "Screen 4" by operating the "Screen 4" button.

As described above, the server 2 has a transition information creation unit 27, a customization program creation unit 28, and a customization screen generation unit 22. The transition information creation unit 27 accumulates, in a transition information table D3, input operations involving screen transitions for the display screen and transition information for the destination display screen resulting from the input operations, based on the display screen of the mainframe 1 and the user operation history D1 of input operations on the display screen. The customization program creation unit 28 creates a customization program D4 that performs a screen transition from the source display screen to the destination display screen, based on the transition information in the transition information table D3. The customization screen generation unit 22 outputs, for the input display screen (G1), a customization screen (G1a) in which display components (BT1 to BT3) that instruct the execution of a customization program with the input display screen in the customization program D4 as the source of the transition are arranged.

As a result, the user can easily perform screen transitions by operating the display components (BT1-BT3) arranged on the customization screen (G1a). Furthermore, since the server 2 generates the customization program D4 based on the transition information in the transition information table D3, it is possible to eliminate the need for a person familiar with the business to generate the customization program D4 in accordance with the operations of the business. In this way, the server 2 can help reduce the labor required for input processing on the display screen of the mainframe 1.

The transition information creation unit 27 also accumulates transition information regarding the screen transition from the first display screen to the second display screen for data input. This allows the server 2 to create a customization program D4 that performs a screen transition from the first display screen to the second display screen for data input, and easily realizes a screen transition to the second display screen for data input.

The customization program creation unit 28 also creates a customization program D4 that performs input operations associated with screen transitions from the first display screen to the second display screen, thereby performing screen transitions. This allows the server 2 to perform screen transitions to the second display screen for data input by operating display components without performing other input operations. This allows the user to quickly input data.

The display screen customized by the server 2 is a business screen related to business processing provided by the mainframe 1. This allows the server 2 to help reduce the labor required for input processing on the business screen provided by the mainframe 1.

Note that each component of each device shown in the figure does not necessarily have to be physically configured as shown in the figure. In other words, the specific form of distribution and integration of each device is not limited to that shown in the figure, and all or part of the devices can be functionally or physically distributed and integrated in any unit depending on various loads, usage conditions, etc.

For example, in this embodiment, a client-server configuration in which the server 2 and the client PC 3 are separate is illustrated, but the server 2 and the client PC 3 may be realized as a single information processing device such as a PC (Personal Computer).

Furthermore, the various processing functions performed by the server 2 and the client PC 3 may be executed in whole or in part on a CPU (or a microcomputer such as an MPU or MCU (Micro Controller Unit)). Needless to say, the various processing functions may be executed in whole or in part on a program that is analyzed and executed by the CPU (or a microcomputer such as an MPU or MCU), or on hardware using wired logic. Furthermore, the various processing functions performed by the server 2 and the client PC 3 may be executed by multiple computers working together using cloud computing.

The various processes described in the above embodiment can be realized by executing a prepared program on a computer. Therefore, an example of a computer configuration (hardware) that executes a program having the same functions as the above embodiment will be described below. Figure 12 is a block diagram showing an example of a computer configuration.

As shown in FIG. 12, the computer 200 has a CPU 201 that executes various arithmetic processes, an input device 202 that accepts data input, a monitor 203, and a speaker 204. The computer 200 also has a medium reading device 205 that reads programs and the like from a storage medium, an interface device 206 for connecting to various devices, and a communication device 207 for connecting to external devices via wired or wireless communication. The mainframe 1 also has a RAM 208 that temporarily stores various information, and a hard disk device 209. Each section (201 to 209) in the computer 200 is connected to a bus 210.

The hard disk drive 209 stores a program 211 for executing various processes in the functional configuration described in the above embodiment (e.g., the screen receiving unit 20, the screen recognition unit 21, the customized screen generating unit 22, the screen transmitting unit 23, the input operation detecting unit 24, the key input information transmitting unit 25, the management information creating unit 26, the transition information creating unit 27, and the customized program creating unit 28). The hard disk drive 209 also stores various data 212 referenced by the program 211. The input device 202, for example, accepts input of operation information from an operator. The monitor 203, for example, displays various screens operated by the operator. The interface device 206 is connected to, for example, a printing device. The communication device 207 is connected to a communication network such as a LAN (Local Area Network) and exchanges various information with external devices via the communication network.

The CPU 201 reads out the program 211 stored in the hard disk drive 209, expands it in the RAM 208, and executes it to perform various processes related to the above-mentioned functional configuration (e.g., the screen receiving unit 20, the screen recognition unit 21, the customized screen generating unit 22, the screen transmitting unit 23, the input operation detecting unit 24, the key input information transmitting unit 25, the management information creating unit 26, the transition information creating unit 27, and the customized program creating unit 28). The program 211 does not have to be stored in the hard disk drive 209. For example, the program 211 stored in a storage medium readable by the computer 200 may be read out and executed. Examples of storage media readable by the computer 200 include portable storage media such as CD-ROMs, DVD disks, USB (Universal Serial Bus) memories, semiconductor memories such as flash memories, and hard disk drives. The program 211 may also be stored in a device connected to a public line, the Internet, a LAN, etc., and the computer 200 may read and execute the program 211 from the device.

The following notes are further provided with respect to the above embodiment.

(Additional Note 1) A storage unit that stores, for the display screen, input operations involving screen transitions and transition information of a display screen to which the input operations have been performed, based on a display screen and a history of input operations on the display screen;
a customize program creating unit that creates a customize program for performing a screen transition from a source display screen to a destination display screen based on the stored transition information;
an output unit that outputs a customized screen in which display components are arranged for instructing execution of a customized program in which the input display screen is a transition source in the customized program that has been created, for the input display screen;
13. An information processing device comprising:

(Additional Note 2) The storage unit stores the transition information regarding screen transitions from a first display screen to a second display screen for data input.
2. The information processing device according to claim 1 .

(Additional Note 3) The customization program creation unit creates a customization program that performs an input operation associated with a screen transition from the first display screen to the second display screen, and performs the screen transition.
3. The information processing device according to claim 2.

(Additional Note 4) The display screen is a business screen related to business processing provided by a mainframe.
4. The information processing device according to claim 1,

(Additional Note 5) Based on a display screen and a history of input operations on the display screen, for the display screen, information on the input operations on the display screen and transition information on a transition destination display screen associated with the input operations is accumulated;
creating a customization program for performing a screen transition from a source display screen to a destination display screen based on the stored transition information;
outputting a customized screen in which display components are arranged for instructing execution of a customized program in which the input display screen is used as a transition source in the customized program created for the input display screen;
A control program that causes a computer to execute a process.

(Additional Note 6) The storing process stores the transition information regarding a screen transition from a first display screen to a second display screen for data input.
6. The control program according to claim 5,

(Additional Note 7) The process of creating a customization program for performing an input operation associated with a screen transition from the first display screen to the second display screen and for performing the screen transition.
7. The control program according to claim 6,

(Additional Note 8) The display screen is a business screen related to business processing provided by a mainframe.
8. The control program according to claim 5,

(Additional Note 9) Based on a display screen and a history of input operations on the display screen, for the display screen, information on the input operations on the display screen and transition information on a transition destination display screen associated with the input operations is accumulated;
creating a customization program for performing a screen transition from a source display screen to a destination display screen based on the stored transition information;
outputting a customized screen in which display components are arranged for instructing execution of a customized program in which the input display screen is used as a transition source in the customized program created for the input display screen;
A control method characterized in that processing is executed by a computer.

(Additional Note 10) The accumulating process accumulates the transition information regarding a screen transition from a first display screen to a second display screen for data input.
10. The control method according to claim 9,

(Additional Note 11) The process of creating a customization program for performing an input operation associated with a screen transition from the first display screen to the second display screen and for performing the screen transition.
11. The control method according to claim 10.

(Additional Note 12) The display screen is a business screen related to business processing provided by a mainframe.
12. The control method according to any one of claims 9 to 11.

1... Mainframe 2... Server 3... Client PC
20...screen receiving unit 21...screen recognition unit 22...customized screen generation unit 23...screen transmission unit 24...input operation detection unit 25...key input information transmission unit 26...management information creation unit 27...transition information creation unit 28...customized program creation unit 30...emulator 31...customized part 200...computer 201...CPU
202: Input device 203: Monitor 204: Speaker 205: Media reader 206: Interface device 207: Communication device 208: RAM
209...Hard disk device 210...Bus 211...Program 212...Various data BT1 to BT3...Display components D1...User operation history D2...Management information table D3...Transition information table D4...Customization program D31...Transition data G1, G1a, G2 to G8...Business screen

Claims (6)

a storage unit that stores, for the display screen, information on an input operation involving a screen transition and transition information on a display screen to which the screen transition is to be made by the input operation, based on a display screen and a history of input operations on the display screen;
a customize program creating unit that creates a customize program for performing a screen transition from a source display screen to a destination display screen based on the stored transition information;
an output unit that outputs a customized screen in which display components are arranged for instructing execution of a customized program whose transition source is the input display screen in the customized program that has been created, in response to the input display screen;
13. An information processing device comprising: the storage unit stores the transition information regarding screen transitions from a first display screen to a second display screen for data input;
2. The information processing apparatus according to claim 1, the customization program creation unit creates a customization program that performs an input operation associated with a screen transition from the first display screen to the second display screen, and performs the screen transition.
3. The information processing apparatus according to claim 2. The display screen is a business screen related to business processing provided by a mainframe.
4. The information processing apparatus according to claim 1, wherein the information processing apparatus is a computer. accumulating, for the display screen, transition information of the input operation on the display screen and a transition information of a destination display screen associated with the input operation, based on the display screen and a history of the input operation on the display screen;
creating a customization program for performing a screen transition from a source display screen to a destination display screen based on the stored transition information;
outputting a customized screen in which display components are arranged for instructing execution of a customized program in which the input display screen is used as a transition source in the customized program created for the input display screen;
A control program that causes a computer to execute a process. accumulating, for the display screen, transition information of the input operation on the display screen and a transition information of a destination display screen associated with the input operation, based on the display screen and a history of the input operation on the display screen;
creating a customization program for performing a screen transition from a source display screen to a destination display screen based on the stored transition information;
outputting a customized screen in which display components are arranged for instructing execution of a customized program in which the input display screen is used as a transition source in the customized program created for the input display screen;
A control method characterized in that processing is executed by a computer.

Images