JPH11102289A - Screen generating method for operation process - Google Patents

Abstract

PROBLEM TO BE SOLVED: To shorten the wait time up to the start of operation processing irrelevantly the complexity of the operation processing and the number of screens by analyzing the screen defined in screen definition information by an analyzing function, generating components in the screen according to the analytic result by a screen generating function, and displaying them on the display screen. SOLUTION: An applet registered in a class file 102 is equipped with an acquiring function for screen definition information, the analyzing function for the obtained screen definition information, the screen generating function based upon the analytic result, and an acquiring function for screen index information. This applet is downloaded previously to a client device 106 by a browser 116 before the operation processing and used to download screen definition information needed for the operation processing, screen by screen, in order as the screen transition advances, thereby generating the display contents of the screens according to the downloaded screen definition information.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a business process screen generation method for generating a screen used for various business processes such as payroll calculation using a program running on a WWW browser such as a Java applet. .

[0002]

2. Description of the Related Art An applet is a WWW (World Wide
Web) A small program that runs on a browser, and is read from a WWW server via the Internet by a WWW browser mounted on a client device,
Run on client device. This applet is made up of bytecode class files, and a programming language called Java is provided for its programming.

[0003] The Java language is an object thinking language and has features such as being operable on multiple platforms. If this feature is utilized, even if the client device has a different architecture, for example, an applet for calculating payroll is prepared in the WWW server,
When the payroll processing becomes necessary in each client device, the payroll applet is read (downloaded) from the WWW server and executed to obtain a calculation result of exactly the same specifications. Necessary operations can be performed without making the user aware of the difference. For this reason, applications to business processes have become active in companies and the like using various client devices having different architectures.

[0004] When business processes are realized by an applet on the Internet or an intranet, a class file of an applet describing screens and processing contents required for the business processes is placed on a WWW server, and the class files are required for the business processes. In general, when it becomes unnecessary, it is configured to download and execute the program on the client side.

FIG. 10 shows a system configuration including a server device 1001 and a client device 1003, in which Ja
FIG. 4 is a diagram for explaining an execution operation of a va applet. A server device 1001 includes an applet class file 1002.
Is created in advance, and when the browser 1005 is executed on the client device 1003 side and the page on which the applet is pasted is opened, the applet class file 1002 is transmitted from the server device 1001 side to the client device 1003 side via the network. The screen is downloaded, and the screen / process 1004 on the client device 1003 performs processing such as generation of a screen.
The process described in the applet is advanced, such as displaying 006.

Screens and processes required by the applet are created as a class file 1002. When the applet is executed, the class file is interpreted to display a screen and execute a process.

However, when the applet is applied to various business processes used in a company or the like, the number of screens used in the business process is large, and the processing content in each screen is often complicated. If the number of screens increases and the processing content becomes more complicated, the size of the applet increases in proportion to the number of screens and the complexity of the processing content, the download time from the server device 1001 becomes longer, and the business process is actually performed. There is a problem that you have to wait for a long time to start.

Therefore, the applet class file 10
There is an example in which a method of shortening the download time is implemented by compressing and downloading 02.

[0009]

However, when the present invention is applied to business processing, the size of the applet is quite large, so even if it is compressed, the download time is reduced only slightly. The problem of waiting for a time proportional to the complexity of the business process content or the number of screens (proportional to the size of the applet) has not been basically solved.

On the other hand, a number of tools for creating an applet and the like have been developed. When a component such as a button is added to or deleted from a certain screen during a business process, the applet is updated each time. There is a problem that work such as re-creation and testing of the file occurs, and it is not possible to flexibly cope with a change in business processing.

A first object of the present invention is to provide a business processing screen generation method capable of shortening the waiting time until the start of business processing regardless of the complexity of business processing and the number of screens.

A second object of the present invention is to provide a business processing screen generation method capable of flexibly coping with a change in a business processing screen or processing content.

[0013]

In order to achieve the first object, according to the present invention, a server device is provided with definition information of a screen used in a business process, a function for acquiring the screen definition information, and a screen. A class file of an applet having a definition information analysis function and a screen generation function is provided, and an applet having the screen definition information acquisition function, the screen definition information analysis function, and the screen generation function is provided before the start of the business process. Downloaded from the device to the client device, the screen definition information acquisition function of the downloaded applet downloads and acquires the screen definition information of the desired screen used in the business process from the server device in screen units, and obtains the screen definition information by the screen definition information. The defined screen is analyzed by the analysis function, and the parts in the screen are displayed on the screen according to the analysis result. Produced by forming function, characterized in that so as to be displayed on the display screen of the client device.

Further, in order to achieve the second object, a list of screens used in each of a plurality of business processes is prepared as index information on the server device side, and before starting the business process, a desired list is prepared. The business process name index information is downloaded from the server device to the client device, and the screen definition information of the screen defined by the downloaded index information is downloaded and obtained from the server device in screen units, and is defined by the screen definition information. The screen is analyzed by the analysis function, components in the screen are generated by the screen generation function according to the analysis result, and are displayed on the display screen of the client device.

That is, according to the present invention, when starting a business process, all the screens and processes prepared on the server device side are not downloaded all at once to the client device side, but the screens prepared on the server device side. First, download only the applet that has the screen definition information that defines each of the above, the generation function that generates the screen according to the screen definition information, the acquisition function of the screen definition information, and the analysis function, and the screen that becomes necessary as the business process progresses. Is downloaded each time, and the waiting time until the start of business processing is limited to only the download time of the screen definition information and the screen generation function, the acquisition function of the screen definition information, and the analysis function. .

[0016]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS One embodiment of the present invention will be described below with reference to the drawings. FIG. 1 is a system configuration diagram showing an embodiment of a business processing screen generation system to which the present invention is applied. The system of this embodiment is basically a client-server system including a server device 101 and a client device 106.

In FIG. 1, reference numeral 102 denotes a class file which forms an applet. When a browser of the client device 106 requests the applet, the server device 10
1 is downloaded to the client 106 via the network. The applet registered in the class file 102 is based on the function of obtaining screen index information prepared for each business process, the function of obtaining screen definition information used in business processing, the function of analyzing the obtained screen definition information, and the analysis result. It has a screen generation function. Screen index information acquisition function, if there is one business process,
It is not necessary because the screen index information is not required. The applet registered in the class file 102 according to the present embodiment includes the above four functions, namely, a function of acquiring screen definition information, a function of analyzing acquired screen definition information, a function of generating a screen based on an analysis result, and acquisition of screen index information. Has functions.

Reference numeral 103 denotes screen information that defines a list of various screens used in a plurality of business processes, and includes screen index information 104 and screen definition information 105. The screen definition information 105 is information that defines the contents of a screen displayed using an applet, and is stored for each screen. The screen index information 104 is information describing a list of the screen definition information 105.

On the other hand, the client device 106 is provided with a browser 116 for downloading applets required for various business processes from the server device 101.
The applet registered in is downloaded via the network. The applet registered in the class file 102 is downloaded in advance to the client device 106 by the browser 116 before performing the business process, and the downloaded applet is used to provide screen definition information necessary for the business process on a screen-by-screen basis. The contents are sequentially downloaded in accordance with the progress of the transition, and the display contents of the screen are generated based on the downloaded screen definition information.

Therefore, when the applet 120 having the above-described function is downloaded by the browser 116, the client device 106 can execute the screen index information acquisition unit 107, the screen definition information acquisition unit 109, and the screen It has a machine called a definition information analysis unit 110, a screen generation unit 111, and an event processing unit 114.

Hereinafter, the configuration and operation of each of these units will be described. 107 is screen index information 104
Is a screen index information acquisition unit that is a means for acquiring the information via a network. Reference numeral 108 denotes a screen list table storage unit for managing the screen index information 104 and the state of each screen. The screen index information acquisition unit 107 acquires the screen index information 104 from the server apparatus 101 via the network, and sets the screen index information 104 in the screen list table storage unit 108.

Reference numeral 109 denotes a screen definition information acquisition unit which is a means for acquiring the screen definition information 105 via a network. The screen definition information acquisition unit 109 searches the screen list table storage unit 108 for the screen definition information 105 to be generated and displayed. To obtain the screen definition information 105 via the network. 1
10 is the screen definition information 1 acquired by the screen definition acquisition unit 109
A screen definition information analysis unit that analyzes the contents of step 05, determines whether the information obtained by the analysis is part information or event information, and performs a corresponding process.

Reference numeral 111 denotes a screen generation unit for performing a component generation process when the information obtained by the screen definition information analysis unit 110 is component information. The screen generation unit 111 includes a component attribute analysis unit 112 and a component generation unit 113. It consists of. If the information obtained by the screen definition information analysis unit 110 is component information, the screen generation unit 111 is called, and the component attribute analysis unit 112
Analyzes the attribute part of the component information, and the component generation unit 113 generates a component based on the content of the obtained information.

An event processing unit 114 performs an event registration process when the information obtained by the screen definition information analysis unit 110 is event information. Event processing unit 1
Reference numeral 14 determines and processes an event when the event occurs on the screen.

An event registration unit 115 stores events on the screen. If the information obtained by the screen definition information analysis unit 110 is event information, the event processing unit 1
14 is called and is set in the event registration unit 115 as an event on the screen.

When the processing of all the component information and event information of the screen definition information 105 in the screen definition information analysis unit 110 is completed, the screen information is displayed as a screen 117 on an applet executed by the browser 116.

Reference numeral 118 denotes a button generated on the screen 117. When the button 118 is pressed, an event occurs. The event processing unit 114 determines and processes the event that has occurred, searches the event registration unit 115 for a process of the event, and executes the process. If the event is a screen transition, a process of generating and displaying the next screen is performed. In this process, the screen definition information acquisition unit 109 is called, the screen definition information 105 specified as the next screen is acquired, the same processing is performed thereafter, and the processing of generating the next screen is performed.

FIG. 2 is a diagram showing the configuration of the screen definition information 105 which defines information such as parts to be displayed on one screen. In FIG. 2, reference numeral 201 denotes a field for storing a key indicating a type of a component to be displayed. The component key 201 designates a label, a text, a button, and the like. A part key 201 corresponding to a necessary part constituting the screen is registered in the screen generation unit 111.

Reference numeral 202 denotes a component ID for specifying a component in a process performed on the screen. Reference numerals 203 to 205 denote component attribute information for the component key 201.
The attribute information includes a display character string, a display position, a size, a state, a process, and the like, and a plurality of pieces of attribute information are sequentially specified. Thereafter, the same definition information is stored for the number of components to be displayed on the screen.

Reference numeral 206 denotes an event name used when processing is performed on the screen. The screen definition information analysis unit 110 identifies an item that does not correspond to the component key 201 as an event name 206. Reference numeral 207 denotes the content of the event processing for the event name 206. When an event occurs on the screen,
The event processing unit 114 searches the event contents 207 using the event name 206 as a keyword,
The event content 207 corresponding to No. 6 is processed.

FIG. 3 is a diagram showing the contents of the component attributes 203, 204, and 205, which are the contents of the screen definition information 105. A field 301 stores a key indicating the type of the attribute of the component to be displayed. Is a part for designating the attribute content for the attribute key 301. In the attribute key 301, the display character string, the display position of the component, the size, the color, the state, the name of the event to be processed, and the like are specified. For example, when the process 208 which is the attribute of the button component is set to “screen transition”, the attribute key 301 for the process 208 is set to “process”, and the attribute content is set to “screen transition”.

FIG. 4 is a diagram showing the configuration contents of the screen index information 104 which stores screens necessary for various business processes such as salary calculation and work management as a screen list in the order of screen transition or in any order. In FIG. 4, reference numeral 401 denotes a field for storing the number of screens stored in the screen index information of one business process. 402
Is a field for storing a screen name for designating the name of each screen. For example, if the number of screens required from the start of work to the end of work is m in the business process of performing payroll calculation, m is stored in the number of screens 401, and m screens are stored in the screen name 402. The name is stored. Reference numeral 403 denotes a portion for designating a screen to be used for initial display of business processing from a list of screen names 402, and one of the screen names 402 is selected and stored. A field 404 stores information that specifies the storage location of the screen definition information corresponding to the screen name 402. Specifically, the field 404 stores the screen definition information corresponding to the screen name 402 in the server 1
01 is a field for storing a screen definition information name indicating a location where the information is actually stored. Screen name 402
And the number of lists of screen definition information names 404 are set in the number of screens 401.

One set of the screen index information 104 configured as described above exists for one business type. That is, when there are two types of business processing, payroll and work management, two sets of screen index information 104 are provided.

FIG. 5 is a diagram showing the contents of the screen list table created in the screen list table storage unit 108 by acquiring the contents of the screen index information 104. In FIG. 5, a field 501 stores a screen name 402 which is a configuration content of the screen index information 104. Reference numeral 502 denotes a field in which a screen definition information name 404 corresponding to the screen name 402 is stored. 503 and 504
Is a field for managing the state of the screen.
Reference numeral 3 denotes a flag indicating whether or not a necessary screen has already been generated on the applet 120. In the initial setting, "FALSE" indicating that the required screen has not been generated is set.
A field 504 stores the character string of the text on the screen and the selected state of the check box in association with the component ID 202 assigned to the component, and indicates that nothing has been input or selected by default. "NULL" is set.

FIG. 6 is a diagram showing the configuration of screen index information 104 and screen definition information 105 for two business processes. Here, the relationship between screen index information and screen definition information used for two types of business processes is shown. ing. In FIG. 6, reference numeral 601 denotes screen index information that defines salary calculation business processing, and reference numeral 602 denotes screen index information that defines work management business processing. Either of these is used as the screen index information acquisition unit 107
Thus, the business process defined by the acquired screen index information can be executed. Reference numeral 603 denotes a screen definition information group in which some screen definition information is defined. Here, screen definition information described in screen index information 601 and 602 defining business processes of payroll and work management is downloaded. is there. These pieces of screen definition information can be downloaded by sharing a start screen common to the two business processes, for example, the password input screen 604, and specifying one of the screen index information 601 and 602. When it is necessary to change the screen configuration of the business process of payroll calculation, the screen index information 601 and screen definition information of payroll are changed, and the changed screen index information 601 and screen definition information are downloaded. As a result, it is possible to perform the salary calculation business with the changed screen configuration. That is, in the past, when it was necessary to change the configuration of the screen used for the business, the applet itself used for the business was changed, but in the present embodiment, only the screen definition information is used. It only needs to be changed, and it is possible to flexibly cope with changes in the screen configuration and processing contents.

FIG. 7 shows a screen index information acquiring unit 10.
9 is a flowchart showing the flow of the process of FIG. Hereinafter, the screen index information 104 will be described with reference to FIG.
The operation of creating a screen list table in the screen list table storage unit 108 obtained from the 01 side via the network will be described.

The screen index information acquisition unit 107 is called when the applet (the applet 120 downloaded from the class file 102 before starting the business) is started. First, the name of the screen index information 104 specified as the business process to be executed on the applet is obtained (step 701). For example, the name of the screen index information 104 corresponding to the business process of “payroll calculation” is acquired. The name of the screen index information 104 is input from a password input screen as a parameter when the applet is executed, and is passed.

Thereafter, the contents of the screen index information 104 having the designated name are obtained from the server 101 via the network (step 702). Next, the number of screens 401 is acquired from the acquired screen index information 104 (step 703), the size of the screen list table is determined based on the acquired screen number 401, and the area of the table is stored in the screen list table storage unit 108. Secure (step 704).

Next, the screen name 402 of the initial screen 403 to be displayed first in the applet is displayed in the screen index information 10.
4 (step 705). Then, the screen definition information name 40 corresponding to the screen name 403 of the initial screen 403
4 is acquired from the screen index information 104 (step 706), and is set in the screen list table of FIG. 5 in an initial state (step 707). As an initial state, the screen generation flag 503 indicates that a screen has not been generated yet. "
"FALSE" is set, and "NULL" is set in the input data 504 to indicate that data has not yet been input or selected on the screen.

The screen index information acquiring unit 107 checks whether or not the unregistered screen name 402 and screen definition information name 404 still remain in the screen list table (step 708). If so, the process from step 706 is repeated, and if not, the process ends. Number of screens 401 as contents of screen index information 104
It is necessary to specify the same number as the screen name 402 and the screen definition information name 404 or a larger number. This allows
The screen definition information name 502, the screen generation flag 503, and the input data 50 constituting the number of screens designated by the screen number 401
4 is registered in the screen list table of FIG. in this case,
Screen generation flag 503 and input data 5 of each screen name
04 is FALSE and NULL because it is the initial state
Is set.

FIG. 8 is a flowchart showing the flow of processing of the screen definition information acquisition unit 109, the screen definition information analysis unit 110, the screen generation unit 111, and the event processing unit 114.

The operation of generating the screen 117 of the browser 116 using the applet 120 will be described below with reference to FIG. The screen definition information acquisition unit 109 acquires the screen definition information 105 from the server device 101 via a network. The screen definition information analysis unit 110 is called each time one piece of component information or event information, which is the content of the screen definition information 105 acquired by the screen definition information acquisition unit 109, is input. The screen name to be generated is set each time the screen definition information acquisition unit 109 generates a screen transition event.
It is passed from the event processing unit 114 when called from the event processing unit 114.

First, the screen definition information acquisition unit 109 searches the screen list table of the screen list table storage unit 108 for a screen definition information name 502 corresponding to the screen name 501 (step 801). Then, the screen definition information 105 indicated by the screen definition information name 502 obtained by the search is downloaded and obtained from the server apparatus 101 via the network (step 802). Next, component or event information is acquired from the content of the acquired screen definition information 105 (step 803).

The screen definition information analysis unit 110 extracts the head of the information acquired by the screen definition information acquisition unit 109 and checks whether the acquired information is component information or event information (step 804). If it is component information, the screen generation unit 111 is called. The screen generation unit 111 extracts the component key 201 from the component information and determines the type. Then, attributes 203, 204, and 205 for the component are cut out by the component attribute analysis unit 112, and the attribute key 3
01 and its attribute contents 302 are analyzed (step 80).
5).

The component generation unit 113 assigns the component corresponding to the component key 201 analyzed in step 805 to the attribute 203,
04 and 205 (step 806).

On the other hand, if the information acquired by the screen definition information acquisition unit 109 is event information, the event content is registered in the event registration unit 115 by the event processing unit 114 (step 807).

When the above-described component generation or event registration is completed, the screen definition information analysis unit 110
It is checked whether or not there is information on the next part or event in the contents (step 808). If so, the processing steps from step 803 are repeated. If not, it is determined that all component generation and event registration on the screen have been completed.

Next, "TRUE" is set in the corresponding screen generation flag 503 of the screen list table, and a flag indicating that this screen has been generated is set (step 80).
9). Then, the generated screen is added to the applet by adding a screen name (step 810). By checking the corresponding screen generation flag 503 in the screen list table before calling this screen processing for the already generated screen next time, it is possible to prevent the same screen from being repeatedly generated. If the screen has already been generated, the corresponding screen is displayed by the screen name.

FIG. 9 is a flowchart showing the flow of the processing of the event processing unit 114. Hereinafter, the operation of transitioning the screen in the business process will be described with reference to FIG. The event processing unit 114 determines an event that has occurred and performs a corresponding process. For example, the screen 117 of the browser 116
Suppose there is a button 118 at the top, which is selected by a mouse or keyboard attached to the client device 106. Then, an event indicating that the button 118 has been selected occurs (step 901). The event processing unit 114 determines what this event does. For example, an event name processed by the button is specified as the attribute 208 of the component of the button 118. The event name 206 registered in the event registration unit 115 is searched from the event name 208, and it is checked whether or not the event content 207 corresponding to the event name 206 is an event that causes a screen transition (step 902). If the event is not an event for changing the screen, the corresponding event registered in the event registration unit 115 is processed, and the process ends (step 903).

For example, if the process registered in the event registration unit 115 is a process for acquiring data on the screen, the data and selection status input to each component on the screen are acquired and attached to each component. The input data 504 of the screen list table is stored together with the obtained component ID 202. If the event is a screen transition, the transition destination screen name 5
01 is acquired from the screen list table of the screen list table storage unit 108 (step 904). When the corresponding screen name 501 is searched from the screen list table, the screen generation flag 503 is checked to determine whether or not this screen has already been generated (step 905). If not generated, the screen generation unit 111 is called using the screen name 501 as a parameter (step 906). If the screen has already been generated, the screen already added to the applet is determined by the screen name and displayed. If a screen is generated, it is displayed as it is (step 907).

As described above, by providing a mechanism for reusing the already generated screen, it is not necessary to download the screen definition information 105 of the necessary screen from the server apparatus 101 every time the screen is changed. Can be prevented from increasing.

It should be noted that the present invention is not limited to the above-described embodiment, and is executed by being dynamically or statically connected to another application program or another applet incorporated in the client device 106 and executed. Is also good.

[0053]

As described above, according to the present invention, when starting a business process, all screens and processes prepared in the server device are not downloaded to the client device at once, but are downloaded to the server device. First, download only the screen definition information that defines each of the screens provided in, and the generation function that generates the screen according to the screen definition information, the acquisition function of the screen definition information, and the applet that has the analysis function. Information such as screens that are required according to is downloaded each time, so the waiting time until the start of business processing is reduced by screen definition information and screen generation function,
It is limited only to the download time of the screen definition information acquisition function and the analysis function, and the waiting time until the start of business processing is shortened regardless of the complexity of business processing and the number of screens, and various business processing can be efficiently advanced It becomes possible.

A list of screens used in each of a plurality of business processes is prepared as index information on the server device side, and before the start of the business process, the index information of a desired business process name is transmitted from the server device. It is downloaded to the client device, the screen definition information of the screen defined by the downloaded index information is downloaded and obtained from the server device in screen units, and the screen defined by the screen definition information is analyzed by the analysis function. Then, according to the analysis result, the components in the screen are generated by the screen generation function and displayed on the display screen of the client device, thereby changing the screen index information and the screen definition information when changing the screen used for business processing. Can be dealt with simply by changing It is possible to flexibly deal.

Further, the screen definition information can be used not only from an applet but also from one programmed in a language other than the Java language, so that portability from multiple languages can be easily achieved.

[Brief description of the drawings]

FIG. 1 is a system configuration diagram showing an embodiment of a business processing screen generation system to which the present invention is applied.

FIG. 2 is a diagram illustrating a configuration example of screen definition information.

FIG. 3 is a diagram illustrating a configuration example of an attribute for a component which is the content of screen definition information.

FIG. 4 is a diagram showing a configuration example of screen index information.

FIG. 5 is a diagram illustrating a configuration example of a screen list table created in a screen list table storage unit.

FIG. 6 is a diagram showing a configuration example of screen index information and screen definition information in different business processes.

FIG. 7 is a flowchart showing a flow of processing for creating a screen list table from screen index information.

FIG. 8 is a flowchart illustrating a flow of a process of extracting component information from the screen definition information and generating a component on the screen.

FIG. 9 is a flowchart illustrating a process flow of an event processing unit that determines a generated event and performs a screen generation process if a screen transition occurs.

FIG. 10 is a diagram illustrating an execution operation of an applet.

[Explanation of symbols]

101: server device, 102: class file, 103
... screen information, 104 ... screen index information, 105 ...
Screen definition information, 106: Client device, 107: Screen index information acquisition unit, 108: Screen list table storage unit, 109: Screen definition information acquisition unit, 110: Screen definition information analysis unit, 111: Screen generation unit, 112: Parts Attribute analysis unit, 113: component generation unit, 114: event processing unit, 115: event registration unit, 116: browser.

Claims (5)

[Claims] 1. A method of downloading an applet described in a predetermined programming language from a server device to a client device, and generating a screen used in various business processes using the applet, comprising: In addition to providing the definition information of the screen used in the business process, the class file of the applet that has the function of acquiring the screen definition information, the function of analyzing the screen definition information, and the function of generating the screen is provided. Prior to this, an applet having the screen definition information acquisition function, the screen definition information analysis function, and the screen generation function is downloaded from the server device to the client device, and the downloaded applet is used in business processing by the screen definition information acquisition function. The screen definition information of the desired screen is Downloaded and obtained from the device, the screen defined by the screen definition information analyzed by the analysis function,
A business process screen generation method, characterized in that parts in a screen are generated by the screen generation function according to the analysis result and displayed on a display screen of a client device. 2. A server device stores index information of screen definition information relating to a plurality of business processes, downloads index information corresponding to a desired business process name from the server device to a client device, and defines the index information defined by the index information. 2. The method according to claim 1, wherein the screen definition information is downloaded in units of screens. 3. The business process screen generation method according to claim 1, wherein the screen definition information includes parts on the screen to be displayed, their attributes, and details of event processing on the screen. . 4. When an event occurs on a generated screen, it is determined whether the event is a screen transition, and if the event is a transition to the next screen, screen definition information corresponding to the next screen is searched for. 4. The business process screen generation method according to claim 3, wherein if the event is not an event to be executed, the corresponding event is executed. 5. The downloaded screen index information is stored in a screen list table, a plurality of screens indicated by the index information are discriminated by a flag as to whether or not the screen has already been generated, and the already generated screen is stored. 3. The method according to claim 2, wherein the generated screen is displayed.