JP2015005241A - Screen creation support program, screen creation support device and screen creation support method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To generate a screen for confirmation capable of confirming that each button is correctly made to correspond to data assigned to each button concerning a screen creation support program, device and method for supporting the creation of a screen.SOLUTION: A Web page of a confirmation screen is transmitted to a client terminal 102 by a Web program generated by a generator 210, and arranged at a confirmation screen execution control part 211 in response to the test display request of a screen from the client terminal 102. When a user depresses a button in the confirmation screen on the client terminal 102, a Java Script for confirmation screen display embedded in the data of the confirmation screen is executed by, for example, the Web program so that call definition information corresponding to the depressed button is displayed.

Description

  The present invention relates to a screen creation support program, apparatus, and method for supporting screen creation.

  For example, in a system composed of a Web (web) server and an AP (application) server, or a system in which a database is added to this configuration, a screen to be displayed on a client terminal may be created.

  For example, the developer creates a Web program that dynamically generates a Web page on a Web server using JSP (Java Server Pages) (registered trademark of Oracle Corporation and its subsidiaries and affiliates in the United States and other countries). Alternatively, the developer creates a skeleton that is a basis for creating a business processing program used in the AP server.

  Further, the developer creates a screen layout used in the Web program or the business processing program. Define a business processing program to be executed when a button placed on the screen is pressed when creating a screen layout. Further, the developer creates a business processing program as necessary and generates a final screen.

  However, after performing a series of operations related to screen generation as described above, if it becomes necessary to modify the settings of the buttons arranged on the finally generated screen, it is necessary to perform a series of operations again and time There was a problem of such.

  On the other hand, only by displaying the created screen layout, the data assigned to each button is unknown, so it is unclear what happens after the button on the screen is pressed. It had the problem that.

  The following is known as a prior art regarding an operation when a button is pressed (for example, Patent Document 1). The general system tool assigns a process name to the button based on the information in the initialization file read from the server and displays the initial screen. Then, when the button displayed on the initial screen is input, the processing of this button The program corresponding to the name is read from the server and executed.

  As another conventional technique, the following is known (for example, Patent Document 2). (1) When a start operation command is received when the modify key in the input means is first pressed by the user, the user can understand the operation guide information and the specific input button and the content of the command to be executed. Is displayed in an area where the image data represented by is not displayed. (2) When receiving an end operation command due to the release of all the modify keys pressed by the user, the display of the operation guide information is ended. (3) The fact that a specific input button included in the button operation information of the storage means has been pressed through the input means from the time when the start action command is received until the end action command corresponding to the start action command is received. When the command is received, the command associated with the information representing the specific input button that has been pressed is read from the storage means.

  However, any of the above prior arts has a problem in that an appropriate display cannot be performed when a button on the screen is pressed when the data assigned to each button is unknown.

JP 2001-160036 A International Publication No. WO2008 / 029472 A1 Publication

  An object of the present invention is to generate a confirmation screen capable of confirming that each button and data assigned to each button correspond correctly.

  In one example, a screen creation support program for supporting creation of a screen including a button associated with an execution program to be started, and when a test display request for the screen is detected, execution associated with the button on the screen From the storage unit that stores the execution program name information indicating the program and the placement information of the button on the screen, the placement information of the button on the screen is read out, placed on the screen, and associated with the button from the storage unit The execution program name information is read out, and when it is detected that the button arranged on the screen is pressed, the computer is caused to execute a process of performing control to display the execution program name corresponding to the button.

  According to the present invention, it is possible to generate a confirmation screen capable of confirming that each button and the data assigned to each button correspond correctly.

It is a system configuration figure of this embodiment. It is a block diagram of a 1st embodiment. 5 is a flowchart illustrating a confirmation screen display process executed by a Web server and a client terminal in the first embodiment. It is a figure which shows the example of a display of the development screen used by a confirmation screen display process, and a confirmation screen. It is a figure which shows the example of a display of error information. 6 is a flowchart illustrating a call definition information display process executed by a client terminal when a button on a confirmation screen is pressed in the first embodiment. It is a figure which shows the example of a display of call definition information. It is a block diagram of a 2nd embodiment. 12 is a flowchart illustrating a confirmation screen display process executed by a Web server and a client terminal in the second embodiment. 10 is a flowchart illustrating a call definition information display process executed by a client terminal when a button on a confirmation screen is pressed in the second embodiment. It is a figure which shows the structural example of the hardware system which can implement | achieve 1st or 2nd embodiment.

Hereinafter, embodiments for carrying out the present invention will be described in detail with reference to the drawings.
FIG. 1 is a system configuration diagram of this embodiment.

  In response to a specific business process display request from the client terminal 102, the Web server 101 that provides a Web service based on HTTP (Hypertext Transfer Protocol) communication performs the following operation. First, the dialogue unit 105 receives a display request from the client terminal 102. Next, for example, a Web program 104 created by JSP dynamically generates a Web page and transmits the data to the client terminal 102. The client terminal 102 displays a screen 107 corresponding to the Web page on a display device in the client terminal 102.

  Here, the user of the client terminal 102 presses one of the search button 108a, the print button 108b, the XML output button 108c, and the end button 108d on the screen 107. As a result, information regarding the business processing program associated with the pressed button is transmitted to the Web server 101. The dialogue unit 105 in the Web server 101 receives the information and requests the corresponding business processing program 106 in the AP server 103 to perform processing. The business processing program 106 returns the processing result to the dialogue unit 105 in the Web server 101. The dialogue unit 105 activates the web program 104 to generate a web page corresponding to the processing result. The Web page is transmitted to the client terminal 102, and a processing result screen is displayed.

  When developing a system that executes the operation as described above, first, a screen 107 to be displayed on the client terminal 102 is designed, and a Web program 104 for generating the screen 107 is developed. Thereafter, a business processing program 106 corresponding to each button 108 (a, b, c, d) on the screen 107 is developed.

  Here, it is often desired to check the layout of the screen 107 and the behavior of each button 108 (a, b, c, d) at the development stage of the screen 107 and the Web program 104 for generating it. Therefore, in many cases, a preview function for confirming the layout of the screen 107 is provided on the development tool of the screen 107 and the Web program 104.

  For example, the preview is executed when a Web program 104 that dynamically generates a screen 107 (Web page) is created by the Web server 101 using JSP. However, in general, when there is no business processing program 106 to be used in the AP server 103, a part for calling the business processing program 106 by pressing a button 108 (a, b, c, d) on the screen 107 displayed on the client terminal 102. Cannot confirm operation. In this state, even if the button 108 (a, b, c, d) on the screen 107 is pressed, no response or error occurs, and it is unknown how the subsequent operation will be performed when the button is pressed. is there.

  On the other hand, when the operation check is performed after developing a series of business processing programs 106 necessary for the operation of the screen 107, those programs are deployed in the execution environment and all the buttons 108 (a, b, c, d) are arranged. ) To confirm the operation. When there is a malfunction in the operation and it is necessary to correct the buttons 108 (a, b, c, d) arranged on the screen 107, it is necessary to perform a series of operations again after the correction, which takes time. .

  Therefore, in the present embodiment, the buttons 108 (a, b, c, d) on the screen 107 and the business processing program 106 assigned to them correspond correctly by the configuration and operation described in detail below. Can be generated.

  FIG. 2 is a block diagram of the first embodiment that provides a function of developing the screen 107 in the system configuration of FIG.

  The Web server 101 (see FIG. 1) includes a screen creation support device 208. The screen creation support apparatus 208 includes a screen editing unit 209, a generator 210, a screen data storage unit 215 (storage unit), and a confirmation screen execution control unit 211. Furthermore, the confirmation screen execution control unit 211 includes a dialogue unit 212 (corresponding to the dialogue unit 105 in FIG. 1) and a screen control unit 213.

  The client terminal 102 (see FIG. 1) includes a display device 201 and a processing device 202. Further, the processing device 202 includes a screen creation control unit 205, a display control unit 206, and a pseudo communication control unit 207. A keyboard 203 and a mouse 204 are connected to the processing device 202.

  The client terminal 102 and the Web server 101 are connected by a network 214 such as the Internet or an in-house LAN (local area network).

  The screen creation support device 208 in the Web server 101 is connected to the processing device 202 in the client terminal 102 via the network 214. The designer creates screen data of the business processing screen by accessing the screen creation support device 208 from the processing device 202 and stores it in the screen data storage unit 215.

  The Web server 101 reads the screen data created by the screen creation support device 208 from the screen data storage unit 215, performs screen display using the read screen data, and executes business processing based on an instruction from the user.

  The screen data storage unit 215 stores the screen data created by the screen creation support device 208 for each screen. The screen data includes, for example, a screen ID, a screen name, a JSP program, a Java (registered trademark in the United States and other countries of Oracle Corporation and its subsidiaries, and affiliates).

  The screen ID is an identifier for identifying the screen, and the screen name is the name of the screen. The JSP program is an HTML (HyperText Markup Language) file embedded with a Java program, and is executed in response to a request from the processing device 202 in the client terminal 102. The execution result of the JSP program is transmitted from the Web server 101 to the processing device 202 in the HTML format. A Web browser that operates as the processing device 202 displays a screen based on the execution result in the HTML format.

  The screen creation support device 208 includes a screen editing unit 209 and a generator 210. The screen editing unit 209 creates a business screen based on an instruction from a designer who uses the processing device 202. The screen editing unit 209 is realized as, for example, a Servlet program. The generator 210 generates the above-described screen data based on the business screen created by the screen editing unit 209 and writes it in the screen data storage unit 215.

  FIG. 3 is a flowchart showing a confirmation screen display process executed by the Web server 101 and the client terminal 102 of FIG. Hereinafter, reference will be made to each part of FIG.

  First, in the client terminal 102, the screen creation control unit 205 in the processing device 202 detects a confirmation screen display request generated when the user presses a preview button in the development screen, for example, with the mouse 204 or the like. The screen creation control unit 205 transmits a screen generation request to the screen editing unit 209 in the Web server 101 (step S301 in FIG. 3).

  When the screen editing unit 209 receives the screen generation request, the screen editing unit 209 activates the generator 210, which is a subprogram, to cause the generator 210 to generate the Web program 104 (see FIG. 1) using JSP (step S302 in FIG. 3). The Web program 104 stores each execution program name information indicating an execution program associated with each button 108 (a, b, c, d) on the screen 107 and arrangement information on each screen 107 as screen data. Reference is made to the screen data storage unit 215 which is a unit. Then, the Web program 104 reads out the arrangement information on the screen 107 of each button 108 (a, b, c, d) from the screen data storage unit 215 and arranges it on the screen 107. Further, the Web program 104 extracts call definition information associated with each button 108 (a, b, c, d) on the screen 107 (see FIG. 1) with reference to the storage unit. To do. Here, the call definition information is an execution program name of the business processing program 106 (see FIG. 1) activated by each button 108 (a, b, c, d), and when the user develops the screen 107. Are assigned to each button 108 (a, b, c, d). The Web program 104 is a program code for displaying corresponding call definition information when the user presses each button 108 (a, b, c, d) after the screen 107 is displayed on the display device 201 of the client terminal 102. And the call definition information are embedded in the data of the screen 107. This program code may be written in, for example, JavaScript (registered trademark of Oracle Corporation and its subsidiaries and affiliates in the United States and other countries).

  The generator 210 checks whether all the call definition information is associated with each button 108 (a, b, c, d) on the screen 107 (see FIG. 1) generated by the Web program 104 (step S303 in FIG. 3). .

  If there is a button with no call definition information and the determination in step S303 is NG, the generator 210 creates error information listing the button names (step S304 in FIG. 3).

  After the web program 104 is generated by the generator 210, the screen editing unit 209 deploys the generated web program 104 to the confirmation screen execution control unit 211 (step S305 in FIG. 3).

  After the above deployment, the screen editing unit 209 notifies the screen creation control unit 205 of the client terminal 102 of the end of the deployment. If error information has been created in step S304, the error information is also notified (step S306 in FIG. 3).

  The screen creation control unit 205 that has received the deployment end notification requests the dialog unit 212 in the confirmation screen execution control unit 211 of the Web server 101 to display a screen. The dialog unit 212 that has received the request uses the screen control unit 213 in the confirmation screen execution control unit 211 to display a screen 107 (Web page) that is a confirmation screen from the Web program 104 (hereinafter referred to as “confirmation screen 107”). Is transmitted to the client terminal 102. In the client terminal 102, the display control unit 206 in the processing device 202 receives the confirmation screen 107 and displays the confirmation screen 107 on the display device 201. When the error information is also notified from the Web server 101 (see step S306), the display control unit 206 also displays the error information (step S307 in FIG. 3).

  FIG. 4 is a diagram illustrating a display example of the development screen 401 and the confirmation screen 107 used by the above-described confirmation screen display processing. In the area of the development screen 401, a button group to which functions necessary for screen development are assigned is arranged, and the user of the client terminal 102 develops on the screen of FIG. 4 displayed on the display device 201 of FIG. Each button group in the screen 401 can be used to design the screen. When the user presses the preview button 402 on the development screen 401 with the mouse 204 (FIG. 2) or the like, the confirmation screen display processing shown in the flowchart of FIG. 3 is executed. As a result, the confirmation screen 107 is displayed on the development screen 401. Displayed below. The confirmation screen 107 is the same as the screen described in FIG.

  FIG. 5 is a diagram illustrating a display example of error information. As described above in the description of steps S304, S306, and S307 in FIG. 3, when all the buttons 108 (a, b, c, d) and the call definition information are not associated with each other, the display screen in FIG. The error information is displayed, for example, in the form of a dialog box so as to overlap. In the example of FIG. 5, a dialog box 501 indicating that the call definition information is not yet associated with the XML output button 108c and the end button 108d is displayed. Thereby, the user can recognize that the call definition information must be associated with these buttons.

  FIG. 6 is a flowchart showing a call definition information display process executed by the client terminal 102 when a button on the confirmation screen 107 (see FIG. 4) is pressed.

  The user presses one of the buttons 108 (a, b, c, d) on the confirmation screen 107 (see FIG. 4) using the keyboard 203 or the mouse 204 (see FIG. 2). As a result, the operation is detected by the display control unit 206 in the processing device 202 in FIG. 2 (step S601 in FIG. 3).

  The display control unit 206 acquires call definition information associated with the pressed button (hereinafter referred to as “button 108”) via the pseudo communication control unit 207. As described above, in the data of the confirmation screen 107, call definition information and a program code written in, for example, the JavaScript language for displaying it are embedded. The pseudo communication control unit 207 interprets and executes a program code in, for example, the JavaScript language associated with the pressed button 108 notified from the display control unit 206, and executes the call definition information corresponding to the button 108. Is acquired (step S602 in FIG. 6).

  The display control unit 206 displays the message of the call definition information acquired via the pseudo communication control unit 207, for example, in the form of a dialog box 701 shown in FIG. 7 so as to overlap the confirmation screen 107 illustrated in FIG. (Step S603 in FIG. 6).

  In this way, in the first embodiment, it is confirmed on the confirmation screen 107 which business processing program 106 (see FIG. 1) is associated with each button 108 (a, b, c, d). It becomes possible.

  FIG. 8 is a block diagram of a second embodiment that provides a function of developing the screen 107 in the system configuration of FIG.

  The Web browser application of the client terminal 102 is used as a development environment and an execution environment for the screen 107 (see FIG. 1).

  The Web server 101 includes an intermediate file generation tool 801 that generates an intermediate file 802 and an execution asset generation tool 803 that generates an execution asset 804 as functions of the development environment. The intermediate file generation tool 801 and the execution asset generation tool 803 are parts that embody the screen editing unit 209 and the generator 210 in the first embodiment shown in FIG. The execution asset 804 generated by the execution asset generation tool 803 corresponds to the Web program 104 in the first embodiment shown in FIG. The execution asset 804 includes a JSP program 805 and a Java program 806.

  When the user edits the screen from the Web browser of the client terminal 102, the intermediate file generation tool 801 in the development environment of the Web server 101 uses an XML (Extensible Markup Language) format intermediate file corresponding to the edited screen layout. 802 is generated.

  Further, in the development environment of the Web server 101, the execution asset generation tool 803 reads the intermediate file 802 based on a user instruction or at a predetermined timing. The execution asset generation tool 803 generates an execution asset 804 including a JSP program 805 and a Java program 806 corresponding to the intermediate file 802.

  The Web server 101 includes a Web layer 807 as a function of the execution environment. The Web layer 807 is provided with an execution resource 804 in the development environment, a JSP program 805, and a Java (Facelet) program 806a and a Java (Handler) program 806b that are part of the Java program 806. This deployment is executed based on a user instruction or at a predetermined timing (for example, when a preview is executed). The Web layer 807 includes a confirmation screen display servlet program 808 and a confirmation screen display Java (TagHandler) program 809.

  The confirmation screen 107, which is a Web page generated by the JSP program 805, includes an HTML file 810 and a confirmation screen display JavaScript 811.

  FIG. 9 is a flowchart showing a confirmation screen display process executed by the Web server 101 and the client terminal 102 (see FIG. 1) in the second embodiment of the screen development function shown in FIG.

  On the Web browser of the client terminal 102, the user presses the preview button 402 (see FIG. 4) in the development screen, for example, with the mouse 204 or the like. As a result, the client terminal 102 shifts to the execution environment, and a confirmation screen display request corresponding to the pressing of the preview button 402 is detected in the Web browser (step S901 in FIG. 9).

  Next, the Web browser of the client terminal 102 transmits the screen ID including the pressed preview button 402 to the confirmation screen display servlet program 808 in the Web layer 807 in the execution environment of the Web server 101 (FIG. 9). Step S902).

  Next, in the Web layer 807 in the Web server 101, the Java (Handler) program 806b sets dummy data for the Java (Facelet) program 806a (step S903 in FIG. 9). This dummy data is the call definition information associated with each button 108 (a, b, c, d) on the generated screen 107 (see FIG. 1) described in the first embodiment. It is.

  Subsequently, the process is transferred from the confirmation screen display servlet program 808 to the JSP program 805 in the web layer 807 in the web server 101 (step S904 in FIG. 9).

  Then, the JSP program 805 generates an HTML file 810. At that time, a Java (TagHandler) program 809 in the Web layer 807 dynamically generates a partial display content in the generated screen 107. This includes display contents when the button 108 (a, b, c, d) (see FIG. 1) is pressed. The Java (Handler) program 806b sets the above-described dummy data from the Java (Facelet) program 806a as the confirmation screen display JavaScript 811 via the Java (Handler) program 806b (step S905 in FIG. 9).

  The Web server 101 transmits the generated HTML file 810 and the confirmation screen display JavaScript 811 to the client terminal 102 (step S906 in FIG. 9).

  The Web browser of the client terminal 102 displays the confirmation screen 107 described above in the first embodiment corresponding to the received HTML file 810 and confirmation screen display JavaScript 811 (step S907 in FIG. 9).

  FIG. 10 is a flowchart showing call definition information display processing executed on the client terminal 102 when a button on the confirmation screen 107 is pressed in the second embodiment of the screen development function shown in FIG.

  The user presses one of the buttons 108 (a, b, c, d) on the confirmation screen 107 (see FIG. 4) displayed on the Web browser with a keyboard or a mouse (hereinafter, the button is pressed). Button is described as “button 108”). As a result, an event corresponding to the depression is detected by the web browser (step S1001 in FIG. 10).

  The Web browser acquires the job processing program name information, which is call definition information corresponding to the button 108, by executing the confirmation screen display JavaScript 811 associated with the button 108 notified of the event (step of FIG. 10). S1002).

  The Web browser displays the business processing program name information acquired in step S1002 as a message in the above-described dialog box 701 exemplified in FIG. 7 (step S1003 in FIG. 10).

  As described above, in the second embodiment, which business processing program 106 (see FIG. 1) is associated with each button 108 (a, b, c, d) in the development environment of the Java-based screen 107. It can be confirmed on the confirmation screen 107.

  FIG. 11 is a diagram illustrating a hardware configuration example of the Web server 101 capable of realizing the first or second embodiment.

  This hardware includes a CPU 1101, a memory 1102, an input device 1103, an output device 1104, an external storage device 1105, a portable recording medium drive device 1106 into which a portable recording medium 1109 is inserted, and a communication interface 1107. These components are connected to each other via a bus 1108. The configuration shown in FIG. 11 is an example of a computer that can realize the above system, and such a computer is not limited to this configuration.

  The CPU 1101 controls the entire computer. The memory 1102 is a memory such as a RAM that temporarily stores a program or data stored in the external storage device 1105 (or the portable recording medium 1109) when executing a program, updating data, or the like. The CUP 1101 performs overall control by reading the program into the memory 1102 and executing it.

  The input / output device 1103 detects an input operation by a user using a keyboard, a mouse, or the like, notifies the CPU 1101 of the detection result, and outputs data transmitted under the control of the CPU 1101 to a display device or a printing device.

  The external storage device 1105 is, for example, a hard disk storage device. Mainly used for storing various data and programs.

  The portable recording medium driving device 1106 accommodates a portable recording medium 1109 such as an optical disk, SDRAM, or CompactFlash (registered trademark), and has an auxiliary role for the external storage device 1105.

  The communication interface 1107 is a device for connecting, for example, a LAN (local area network) or WAN (wide area network) communication line.

  The system according to the first or second embodiment is realized by the CPU 1101 executing a program having functions realized by the flowcharts of FIGS. 3, 6, 9, or 10. For example, the program may be recorded and distributed in the external storage device 1105 or the portable recording medium 1109, or may be acquired from the network by the network connection device 1107.

  In each embodiment described above, the generation of the screen 107 is performed on the Web server 101 in response to a request from the client terminal 102. Also, the Web program 104 (FIG. 1) that generates the screen 107 embeds, for example, a JavaScript code for displaying the corresponding call definition information when the button on the screen 107 is pressed and the call definition information, in the data of the screen 107. The call definition information display process when the user presses a button on the screen 107 is executed on the client terminal 102 by executing the JavaScript code or the like in the pseudo communication control unit 207 on the client terminal 102. Only done.

  In contrast, when the user presses a button on the screen 107, the call definition information is inquired from the client terminal 102 to the Web server 101, and the call definition information is transmitted to the client terminal 102 and displayed. You may comprise.

  In addition, the creation support of the screen 107 is performed only on the client terminal 102, and the display processing of the call definition information when the button on the screen 107 is pressed by the user is performed only on the client terminal 102. Also good. In this case, the functions of the screen creation support device 208 including the screen data storage unit 215 and the confirmation screen execution control unit 211 described in FIG. 2 are implemented in the processing device 202 of the client terminal 102. As a procedure in this case, a test display request for the screen 107 is detected on the client terminal 102. In response to this, the processing device 202 of the client terminal 102 stores the execution program name information indicating the execution program 106 associated with the button 108 on the screen 107 and the arrangement information of the button 108 on the screen 107. Information on the screen 1007 of the button 108 is read out from the storage unit and placed on the screen 107. Thereafter, the processing device 202 of the client terminal 102 detects that the user has pressed the button 108 on the screen 107 displayed on the display device 201. As a result, the processing device 202 reads out the execution program name information associated with the button 108 from the storage unit, and displays it on the display device 201, for example, in the form of a dialog box.

  As mentioned above, although embodiment of this invention was described, this invention is not limited to embodiment mentioned above, Various other changes are possible.

In addition, the following additional remarks are disclosed regarding the embodiment described above.
(Appendix 1)
A screen creation support program for supporting creation of a screen including a button associated with an execution program to be started,
When a test display request for the screen is detected, an execution program name information indicating an execution program associated with the button of the screen and an arrangement information of the button on the screen are stored on the screen. Read the placement information and place it on the screen,
Control for reading execution program name information associated with the button from the storage unit and displaying the execution program name corresponding to the button when it is detected that the button arranged on the screen is pressed. Do,
A screen creation support program for causing a computer to execute processing.
(Appendix 2)
The control is a program code for causing a computer that displays the screen to execute a process of displaying the execution program name corresponding to the button when it is detected that the button arranged on the screen is pressed. Is embedded in the data of the screen,
The screen creation support program according to Supplementary Note 1, wherein
(Appendix 3)
A test display request for the screen is transmitted to the computer by a client terminal connected to the computer via a network, and the computer returns screen data in which the program code is embedded to the client terminal. When the client terminal detects that the button placed on the received and displayed screen is pressed, the client terminal corresponds to the pressed button and is embedded in the data of the screen By executing the program code, the call definition information corresponding to the pressed button is acquired and displayed.
The screen creation support program according to Supplementary Note 2, wherein
(Appendix 4)
When it is detected that the button arranged on the screen is pressed, the execution program name corresponding to the button is displayed when the button is not associated with the execution program name. The screen creation support program according to any one of supplementary notes 1 to 3, which further causes the computer to execute a process for performing the control.
(Appendix 5)
A screen creation support apparatus for supporting creation of a screen including a button associated with an execution program to be started,
When a test display request for the screen is detected, an execution program name information indicating an execution program associated with the button of the screen and an arrangement information of the button on the screen are stored on the screen. A button arrangement unit for reading out arrangement information and arranging it on the screen;
Control for reading execution program name information associated with the button from the storage unit and displaying the execution program name corresponding to the button when it is detected that the button arranged on the screen is pressed. An execution program name display control unit to be performed;
A screen creation support apparatus comprising:
(Appendix 6)
The control is a program code for causing a computer that displays the screen to execute a process of displaying the execution program name corresponding to the button when it is detected that the button arranged on the screen is pressed. Is embedded in the data of the screen,
The screen creation support apparatus according to Supplementary Note 5, wherein
(Appendix 7)
The test display request for the screen is transmitted to the computer by a client terminal connected to the computer via a network, and the computer returns the screen data in which the program code is embedded to the client terminal, and the client terminal When the client terminal detects that the button arranged on the screen received and displayed at is pressed, the client terminal is embedded in the data of the screen corresponding to the pressed button. By executing the program code, the call definition information corresponding to the pressed button is acquired and displayed.
The screen creation support apparatus according to Supplementary Note 6, wherein
(Appendix 8)
The execution program name display control unit further detects the execution button corresponding to the button when the execution program name is not associated with the button when detecting that the button arranged on the screen is pressed. Control that the program name is undefined,
The screen creation support apparatus according to any one of appendices 5 to 7, characterized in that:
(Appendix 9)
A screen creation support method for supporting creation of a screen including a button associated with an execution program to be started,
When a test display request for the screen is detected, an execution program name information indicating an execution program associated with the button of the screen and an arrangement information of the button on the screen are stored on the screen. Read the placement information and place it on the screen,
Control for reading execution program name information associated with the button from the storage unit and displaying the execution program name corresponding to the button when it is detected that the button arranged on the screen is pressed. Do,
A screen creation support method characterized by that.
(Appendix 10)
The control is a program code for causing a computer that displays the screen to execute a process of displaying the execution program name corresponding to the button when it is detected that the button arranged on the screen is pressed. Is embedded in the data of the screen,
The screen creation support method according to Supplementary Note 9, wherein
(Appendix 11)
A test display request for the screen is transmitted to the computer by a client terminal connected to the computer via a network, and the computer returns screen data in which the program code is embedded to the client terminal. When the client terminal detects that the button placed on the received and displayed screen is pressed, the client terminal corresponds to the pressed button and is embedded in the data of the screen By executing the program code, the call definition information corresponding to the pressed button is acquired and displayed.
The screen creation support method according to Supplementary Note 10, wherein
(Appendix 12)
When it is detected that the button arranged on the screen is pressed, the execution program name corresponding to the button is displayed when the button is not associated with the execution program name. The screen creation support method according to any one of appendices 9 to 11, further causing the computer to execute a process of performing the control.

DESCRIPTION OF SYMBOLS 101 Web server 102 Client terminal 103 AP server 104 Web program 105, 212 Dialogue part 106 Business processing program 107 Screen, confirmation screen 108 Button 108a Search button 108b Print button 108c XML output button 108d End button 201 Display device 202 Processing device 203 Keyboard 204 Mouse 205 Screen creation control unit 206 Display control unit 207 Pseudo communication control unit 208 Screen creation support device 209 Screen editing unit 210 Generator 211 Confirmation screen execution control unit 213 Screen control unit 214 Network 215 Screen data storage unit 401 Development screen 402 Preview button 501 , 701 Dialog box 801 Intermediate file generation tool 802 Intermediate file 803 Execution asset generation tool 804 Execution Assets 805 JSP Program 806 Java Program 807 Web Layer 808 Confirmation Screen Display Servlet Program 809 Confirmation Screen Display Java (TagHandler) Program 810 HTML File 811 Confirmation Screen Display JavaScript

Claims (6)

A screen creation support program for supporting creation of a screen including a button associated with an execution program to be started,
When a test display request for the screen is detected, an execution program name information indicating an execution program associated with the button of the screen and an arrangement information of the button on the screen are stored on the screen. Read the placement information and place it on the screen,
Control for reading execution program name information associated with the button from the storage unit and displaying the execution program name corresponding to the button when it is detected that the button arranged on the screen is pressed. Do,
A screen creation support program for causing a computer to execute processing. The control is a program code for causing a computer that displays the screen to execute a process of displaying the execution program name corresponding to the button when it is detected that the button arranged on the screen is pressed. Is embedded in the data of the screen,
The screen creation support program according to claim 1. A test display request for the screen is transmitted to the computer by a client terminal connected to the computer via a network, and the computer returns screen data in which the program code is embedded to the client terminal. When the client terminal detects that the button placed on the received and displayed screen is pressed, the client terminal corresponds to the pressed button and is embedded in the data of the screen By executing the program code, the call definition information corresponding to the pressed button is acquired and displayed.
The screen creation support program according to claim 2.   When it is detected that the button arranged on the screen is pressed, when the execution program name is not associated with the button, it is displayed that the execution program name corresponding to the button is undefined. The screen creation support program according to any one of claims 1 to 3, further causing the computer to execute a process of performing the control. A screen creation support apparatus for supporting creation of a screen including a button associated with an execution program to be started,
When a test display request for the screen is detected, an execution program name information indicating an execution program associated with the button of the screen and an arrangement information of the button on the screen are stored on the screen. A button arrangement unit for reading out arrangement information and arranging it on the screen;
Control for reading execution program name information associated with the button from the storage unit and displaying the execution program name corresponding to the button when it is detected that the button arranged on the screen is pressed. An execution program name display control unit to be performed;
A screen creation support apparatus comprising: A screen creation support method for supporting creation of a screen including a button associated with an execution program to be started,
When a test display request for the screen is detected, an execution program name information indicating an execution program associated with the button of the screen and an arrangement information of the button on the screen are stored on the screen. Read the placement information and place it on the screen,
Control for reading execution program name information associated with the button from the storage unit and displaying the execution program name corresponding to the button when it is detected that the button arranged on the screen is pressed. Do,
A screen creation support method characterized by that.