Focus control apparatus, focus control method, and focus control program

JP2025026399AActive Publication Date: 2025-02-21OBIC CO LTD
View PDF 11 Cites 0 Cited by

Patent Information

Application Number
JP2024130914
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-08-10
Filing Date
2024-08-07
Publication Date
2025-02-21
Estimated Expiration
2044-08-07

Smart Images

  • Figure 2025026399000001_ABST
    Figure 2025026399000001_ABST
Patent Text Reader

Abstract

To manage focus control and verification processing for input items on a screen, based on separate settings without defining them as settings for a single process, thereby reducing branching processes and preventing missing implementation or implementation error, resulting in improved quality.SOLUTION: A focus control apparatus is configured to: (1) when an item pullout event occurs in a screen of a client, on receipt of a request including a target control, an input value, whether to modify a value, and a key for item pullout, execute verification processing if the value is modified; and (2) when the key for item pullout is a predetermined key, execute focus control, determine whether a transition condition is satisfied or not by referring to a focus flow definition, using the target control as a control before focus transition, acquire a control of a transition destination when the transition condition is satisfied, and shift the focus on the screen of the client to the control of the transition destination.SELECTED DRAWING: Figure 6
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present invention relates to a focus control device, a focus control method, and a focus control program. [Background technology]

[0002] For example, in the field of screen operation, focus display is often set on the screen for the purpose of improving the user's visibility. Focus refers to an object on the screen, such as a window, an input box, an icon, a button, or an image, being in an active (selected) state in which it can be operated. Conventionally, an apparatus for performing focus control is disclosed, for example, in Patent Document 1. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2007-156980 A Summary of the Invention [Problem to be solved by the invention]

[0004] However, the above-mentioned Patent Document 1 does not disclose anything about managing the verification process and focus control of input items on the screen as two separate settings, rather than defining them as a single process setting.

[0005] The present invention has been made in consideration of the above, and aims to provide a focus control device, a focus control method, and a focus control program that can reduce branching processing, prevent implementation omissions and errors, and improve quality by managing the verification processing and focus control of screen input items as two settings rather than defining them as a single processing setting. [Means for solving the problem]

[0006] In order to solve the above-mentioned problems and achieve the object, a focus control device according to the present invention is a focus control device that includes a control unit and is configured to be capable of data communication with a client, the control unit being configured to be capable of accessing a storage area that stores an event allocation definition that assigns a verification process to a control that is an element constituting a screen, an API for acquiring data in the verification process, an individual definition that sets an argument and a return value, and a focus flow definition that sets a control before focus transition, a transition condition, and a control to which focus transition is to be made, and when an item exit event occurs on a client screen and a request is received from the client that includes a target control, an input value, whether or not the value has changed, and a key at the time of item exit, (1) if the value has changed, the control unit executes the verification process, The present invention is characterized in that it comprises a processing means for determining whether the target control exists in the event assignment definition, and if it exists, referring to the individual definition, and obtaining a corresponding return value from the API using the input value of the target control as an argument, and if the return value is not an error, displaying the value contained in the return value in the control contained in the return value on the client screen, and (2) if the key used to exit the item is a specified key, executing focus control, referring to the focus flow definition with the target control as the control before the focus transition, determining whether the transition condition is satisfied, and if the transition condition is satisfied, obtaining the control of the transition destination, and moving the focus of the client screen to the obtained control of the transition destination.

[0007] Also, according to this embodiment, the focus control device may be a Web server, the client may be a Web client, the focus control device may provide a Web page including a screen to be displayed on the client and a program for causing the client to execute a predetermined operation, and the client may execute the Web page provided in a Web browser.

[0008] In addition, according to one aspect of the present invention, the control unit may further include a verification process setting means for creating the event assignment definition and the individual definition and registering them in the memory area in response to a developer's operation on a setting screen, and a focus control setting means for creating the focus flow definition and registering them in the memory area in response to a developer's operation on the setting screen.

[0009] Furthermore, according to one aspect of the present invention, when the processing means receives a request from the client, it may send a response to the client including a control, a value to be displayed in the control, and a next focus control, and the client may perform processing in accordance with the received response.

[0010] According to another aspect of the present invention, the focus control device may be configured on a low-code or no-code basis.

[0011] In order to solve the above-mentioned problems and achieve the object, the present invention provides a focus control method executed by an information processing device that includes a control unit and is configured to be capable of data communication with a client, the control unit being configured to be able to access a storage area that stores an event assignment definition that assigns a verification process to a control that is an element that constitutes a screen, an API for acquiring data in the verification process, an individual definition that sets an argument and a return value, and a focus flow definition that sets a control before a focus transition, a transition condition, and a control to which the focus transition is to be made, the focus control method executed by the control unit being configured to be able to access a storage area that stores an event assignment definition that assigns a verification process to a control that is an element that constitutes a screen, an API for acquiring data in the verification process, an individual definition that sets an argument and a return value, and a focus flow definition that sets a control before a focus transition, a transition condition, and a control to which the focus transition is to be made, the focus control method being ... The method includes a processing step of: (1) executing a verification process to determine whether the target control exists in the event assignment definition; if the target control exists, referring to the individual definition, and obtaining a corresponding return value from the API using the input value of the target control as an argument; if the return value is not an error, displaying the value contained in the return value in the control contained in the return value on the client screen; (2) if the key used to exit the item is a specified key, executing focus control, referring to the focus flow definition with the target control as the control before the focus transition, determining whether the transition condition is satisfied; if the transition condition is satisfied, obtaining the control of the transition destination, and moving the focus of the client screen to the obtained control of the transition destination.

[0012] In order to solve the above-mentioned problems and achieve the object, the present invention provides a focus control program to be executed by an information processing device that has a control unit and is configured to be capable of data communication with a client, the control unit being configured to be able to access a storage area that stores an event allocation definition that assigns a verification process to a control that is an element constituting a screen, an API for acquiring data in the verification process, an individual definition that sets an argument and a return value, and a focus flow definition that sets a control before the focus transition, a transition condition, and a control to which the focus transition is to be made, the control unit, when an event of exiting an item occurs on a client screen and a request is received from the client that includes the target control, an input value, whether or not the value has been changed, and a key at the time of exiting the item, (1) if the value has been changed, executes the verification process, and The present invention is characterized in that it is a focus control program for executing a processing step of: (1) determining whether the target control exists in the event assignment definition; if it exists, referring to the individual definition, and obtaining a corresponding return value from the API using the input value of the target control as an argument; if the return value is not an error, displaying the value contained in the return value in the control contained in the return value on the client screen; (2) if the key used to exit the item is a specified key, executing focus control, referring to the focus flow definition with the target control as the control before the focus transition, determining whether the transition condition is satisfied; if the transition condition is satisfied, obtaining the control of the transition destination, and moving the focus of the client screen to the obtained control of the transition destination. Effect of the Invention

[0013] According to the present invention, by managing the verification process and focus control of input items on a screen as two separate settings rather than defining them as a single process setting, it is possible to reduce branching processes, prevent implementation omissions and errors, and improve quality. [Brief description of the drawings]

[0014] [Figure 1] FIG. 1 is a diagram for explaining the problem of implementing focus control during item verification. [Diagram 2] FIG. 2 is a diagram for explaining the problem of implementing focus control during item verification. [Diagram 3] FIG. 3 is a diagram for explaining the problem of implementing focus control during item verification. [Figure 4] FIG. 4 is a diagram for explaining an outline of the mechanism of the present invention. [Diagram 5] FIG. 5 is a diagram for explaining an outline of the mechanism of the present invention. [Figure 6] FIG. 6 is a block diagram showing an example of the configuration of the focus control device according to the present embodiment. [Figure 7] FIG. 7 is a diagram for explaining a specific example of the process of the focus control device according to the present embodiment. [Figure 8] FIG. 8 is a diagram for explaining a specific example of the process of the focus control device according to the present embodiment. [Figure 9] FIG. 9 is a diagram for explaining a specific example of the process of the focus control device according to the present embodiment. [Figure 10] FIG. 10 is a diagram for explaining a specific example of the process of the focus control device according to the present embodiment. [Figure 11] FIG. 11 is a diagram for explaining a specific example of the process of the focus control device according to the present embodiment. [Figure 12] FIG. 12 is a diagram for explaining a specific example of the process of the focus control device according to the present embodiment. [Figure 13] FIG. 13 is a diagram for explaining a specific example of the process of the focus control device according to the present embodiment. [Figure 14] FIG. 14 is a diagram for explaining a specific example of the process of the focus control device according to the present embodiment. [Figure 15] FIG. 15 is a diagram for explaining a specific example of the process of the focus control device according to the present embodiment. [Figure 16]FIG. 16 is a diagram for explaining a specific example of the process of the focus control device according to the present embodiment. [Figure 17] FIG. 17 is a diagram for explaining a specific example of the process of the focus control device according to the present embodiment. [Figure 18] FIG. 18 is a diagram for explaining a specific example of the process of the focus control device according to the present embodiment. [Figure 19] FIG. 19 is a diagram for explaining a specific example of the process of the focus control device according to the present embodiment. [Figure 20] FIG. 20 is a diagram for explaining a specific example of the process of the focus control device according to the present embodiment. [Figure 21] FIG. 21 is a diagram for explaining a specific example of the process of the focus control device according to the present embodiment. [Figure 22] FIG. 22 is a diagram for explaining a specific example of the process of the focus control device according to the present embodiment. [Diagram 23] FIG. 23 is a diagram for explaining a specific example of the process of the focus control device according to the present embodiment. [Figure 24] FIG. 24 is a diagram for explaining a specific example of the process of the focus control device according to the present embodiment. [Diagram 25] FIG. 25 is a diagram for explaining a specific example of the process of the focus control device according to the present embodiment. [Figure 26] FIG. 26 is a diagram for explaining a specific example of the process of the focus control device according to the present embodiment. [Figure 27] FIG. 27 is a diagram for explaining a specific example of the process of the focus control device according to the present embodiment. [Figure 28] FIG. 28 is a diagram for explaining a specific example of the process of the focus control device according to the present embodiment. [Figure 29] FIG. 29 is a diagram for explaining a specific example of the process of the focus control device according to the present embodiment. [Diagram 30]FIG. 30 is a diagram for explaining a specific example of the process of the focus control device according to the present embodiment. [Diagram 31] FIG. 31 is a diagram for explaining a specific example of the process of the focus control device according to the present embodiment. [Diagram 32] FIG. 32 is a diagram for explaining a specific example of the process of the focus control device according to the present embodiment. [Diagram 33] FIG. 33 is a diagram for explaining a specific example of the process of the focus control device according to the present embodiment. [Diagram 34] FIG. 34 is a diagram for explaining a specific example of the process of the focus control device according to the present embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0015] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, preferred embodiments of a focus control device, a focus control method, and a focus control program according to the present invention will be described in detail with reference to the accompanying drawings. Note that the present invention is not limited to the preferred embodiments.

[0016] [1. Overview] The present invention will be outlined in the following order: (Background and Problems), (Solution), and (Outline of the Mechanism of the Invention).

[0017] (Background / Issues) Previously, complex branching processing related to validation processing and focus control was written in the item exit event of each item on the screen. For example, when developing a large-scale application such as ERP (Enterprise Resource Planning), there was a possibility of quality risks such as implementation omissions or implementation errors. Specifically, there are many situations in which validation processing is implemented in the item exit event of each item on the screen. In some cases, focus control is implemented according to the input value or validation result. In such cases, it was necessary to implement validation processing and focus control while considering several conditions such as the following from the perspective of UI and processing efficiency.

[0018] -Whether there are any changes to the input value Are there any errors during validation? Whether the user is about to confirm the value by pressing Enter

[0019] When developers implemented the item escape processing, they were taking the above three factors into consideration, which resulted in implementation omissions and implementation errors.

[0020] The issues involved in implementing focus control during item validation will be described with reference to Figures 1 to 3. In order to improve the UI of an application, there are operations that control whether or not to execute a validation process according to input conditions, etc., and control the focus position of an item.

[0021] Fig. 1 is a diagram for explaining whether or not to execute a verification process. In Fig. 1, for example, if a value has been changed in a text box on the screen (in the example shown in the figure, the text box for customer), the verification process is executed and the process moves to the next item. On the other hand, if the value has not been changed, the verification process is not executed and the process moves to the next item.

[0022] Fig. 2 is a diagram for explaining the control of the focus position. In Fig. 2, for example, if the customer entered in the customer text box on the screen is not "general supplier", the focus is placed on the supplier text box, whereas if the customer entered is "general supplier", the focus is placed on the details button.

[0023] The above controls also differ depending on the key operation and verification result when escaping from an item. Figure 3 is a diagram showing a table showing whether to execute verification processing and focus control. In the example shown in the figure, the conditions (when the value has been changed, when the value has not been changed, when Enter is pressed, when Tab is pressed), verification processing (execute, do not execute), verification error (yes, no), and focus control (perform arbitrary control, perform default operation) are listed.

[0024] Previously, processing to satisfy such a table (specification) was written in the item exit event of each item. This specification was an element that made control complex during development, and when developing large-scale applications such as ERP, there was a possibility of quality risks such as implementation omissions or implementation errors.

[0025] (Solution) In this embodiment, the verification process and focus control are set as separate domains, which reduces the number of branch settings. As a result, issues such as consistency in behavior and quality risks for the entire ERP are resolved.

[0026] (Overview of the mechanism of the present invention) An overview of the mechanism of the present invention will be described with reference to Figures 4 and 5. In the present invention, the verification process and focus control are managed on a low-code platform by dividing them into two settings: 1. Verification process settings and 2. Focus control settings. As a result, in the present invention, it is possible to control the verification process and focus control without requiring the developer to be aware of complex branching conditions.

[0027] Fig. 4 is a diagram for explaining the settings of the validation process. The validation API and the like are set in the validation process event. This setting is processed when the execution conditions of the validation process are met. The execution condition is, for example, when there is a change in the value of an item.

[0028] Figure 5 is a diagram for explaining focus control settings. Transition conditions and transition destinations are specified for text boxes and other items incorporating focus control. This setting is processed when the execution conditions for focus control are met. For example, the setting is such that processing is performed when Enter is pressed to exit an item and there are no validation errors.

[0029] [2. Configuration] An example of the configuration of the focus control device 100 (Web server) according to this embodiment will be described with reference to Fig. 6. The focus control device 100 can be configured, for example, on a low-code platform. It may also be configured on a no-code platform. Fig. 6 is a block diagram showing an example of the configuration of the focus control device 100.

[0030] The focus control device 100 includes a control unit 102, a communication interface unit 104, a storage unit 106, and an input / output interface unit 108. The units included in the focus control device 100 are connected to each other so as to be able to communicate with each other via any communication path.

[0031] The communication interface unit 104 connects the focus control device 100 to the network 300 so as to be able to communicate with each other via a communication device such as a router and a wired or wireless communication line such as a dedicated line. The communication interface unit 104 has a function of communicating data with other devices via a communication line. Here, the network 300 has a function of connecting the focus control device 100 to Web clients (clients used by developers or clients used by business operators) 400, etc., and a business system (not shown) so as to be able to communicate with each other, and is, for example, the Internet or a LAN (Local Area Network). The focus control device 100, which is a Web server, provides the Web client 400 with a Web page including a screen (information) and a program for causing the Web client 400 to execute a predetermined operation, and the Web client 400 executes the Web page with a Web browser. Here, the program is, for example, JavaScript. Note that the data stored in the storage unit 106 described later may be stored in a data server (not shown) or the like. An input device 112 and an output device 114 are connected to the input / output interface unit 108. The output device 114 may be a monitor (including a home television), a speaker, or a printer. The input device 112 may be a keyboard, a mouse, a microphone, or a monitor that cooperates with a mouse to realize a pointing device function. In the following description, the output device 114 may be referred to as the monitor 114, and the input device 112 may be referred to as the keyboard 112 or the mouse 112.

[0032] Various databases, tables, files, etc. are stored in the storage unit 106. Computer programs for cooperating with an OS (Operating System) to give instructions to a CPU (Central Processing Unit) to perform various processes are recorded in the storage unit 106. For example, memory devices such as RAM (Random Access Memory) and ROM (Read Only Memory), fixed disk devices such as hard disks, flexible disks, and optical disks can be used as the storage unit 106.

[0033] The storage unit 106 includes a setting information database 106a in which various setting information is registered. In the setting information database 106a, for example, a layout definition, a screen variable definition, an event allocation definition, an individual definition, a condition definition, a focus flow definition, and the like are registered.

[0034] The layout definition sets information on the layout in which the elements that make up the screen, such as the layout definition, screen variable definition, event assignment definition, individual definition, condition definition, and focus flow definition controls, are arranged on the screen. As shown in Figure 10, the layout definition includes the control ID, which is the ID of the control, the name, the type, a list of child element IDs, etc.

[0035] The screen variable definition is assigned to a variable that temporarily stores information on the screen. As shown in Figure 12, the screen variable definition includes a variable ID, name, type, etc.

[0036] In the event assignment definition, an event is assigned to a control, which is an element that constitutes a screen. As shown in Fig. 14, the event assignment definition includes, for example, a control ID for the control to which the event is set, the type of the event (e.g., verification process), a logic flow ID, etc. In the example shown in the figure, the control ID "ID1-2", the type of the event "verification process", and the logic flow ID "LID0" are set.

[0037] As shown in FIG. 16, the individual definition includes an API to be called to obtain data from a business system, an argument (control value, etc.), and a return value (control value, error message, etc.).

[0038] In the example shown in the figure, the API to be called "Customer verification API", the arguments "Customer text value, Customer CD", and the return values ​​"Customer text error message, Customer name label value, Customer miscellaneous" are set.

[0039] For example, the "Customer Verification API" is an API that uses the customer CD as a key from the business system's customer master (a master that registers customer CD, customer name, and miscellaneous category) to obtain the customer name and miscellaneous category as the return value, and if no data is found, an error message is returned.

[0040] The condition definition is set with an expression that is a focus transition condition. As shown in FIG. 20, the condition definition includes, for example, information for identifying a given condition (condition ID and name), the given condition (expression), etc.

[0041] In the example shown in the same figure, the first line has the condition ID "CID01", the name "Customer is miscellaneous", and the formula "Customer miscellaneous category = fixed value (True)", and the second line has the condition ID "CID02", the name "Supplier is miscellaneous", and the formula "Supplier miscellaneous category = fixed value (True)".

[0042] The focus flow definition specifies the destination of focus when a certain condition (transition condition) in the condition definition is satisfied. As shown in Fig. 24, the focus flow definition includes the control ID before the focus transition, the transition condition (specified by the condition ID in the condition definition), a condition conjunction, and the control ID of the focus transition destination.

[0043] For the transition source, select the control from which the focus will be transferred. In this example, it is "Customer Text". For the transition settings, it is possible to set multiple pairs of transition conditions and transition destinations. If multiple conditions are set, they are evaluated from top to bottom in the order they are set, and the transition ends when the condition is met. If none of the conditions are met, the default focus movement will occur. The transition condition is set from the condition defined. Multiple conditions can be specified (OR or AND conditions can be selected). For the transition destination, specify the control to transition to when the condition is met.

[0044] In the example shown in the figure, the first one has the control ID before the focus transition "1-2 (customer text)," the transition condition "CID01," the condition conjunction "AND," and the control ID of the focus transition destination "1-4 (customer details button)." Using "CID01" as the key, the transition condition "Customer miscellaneous category = fixed value (True)" is obtained from the condition definition.

[0045] The control unit 102 is a CPU or the like that performs overall control of the focus control device 100. The control unit 102 has an internal memory for storing control programs such as an OS, programs that define various processing procedures, and required data, and executes various information processing based on these stored programs.

[0046] The control unit 102 conceptually includes a screen layout setting unit 102a, a verification process setting unit 102b, a focus control setting unit 102c, and a processing unit 102d.

[0047] The screen layout setting unit 102a creates setting information (definition) relating to the screen layout and registers it in the setting information database 106a.

[0048] Specifically, for example, the screen layout setting unit 102a provides a layout editing screen (see FIG. 9) in response to a request from a Web client 400 (developer), and creates a layout definition (see FIG. 10) in response to operations performed by the developer on the layout editing screen, and registers the layout definition in the setting information database 106a.

[0049] In addition, the screen layout setting unit 102a provides a screen variable editing screen (see FIG. 11) in response to a request from a Web client 400 (developer), and creates a screen variable definition (see FIG. 12) in response to operations performed by the developer on the screen variable editing screen, and registers the definition in the setting information database 106a.

[0050] The verification process setting unit 102b creates setting information (definition) related to the verification process, and registers it in the setting information database 106a.

[0051] Specifically, for example, the verification process setting unit 102b provides a logic flow setting screen (see FIG. 13) in response to a request from a Web client 400 (developer), and creates an event allocation definition (see FIG. 14) in response to the developer's operations on the logic flow setting screen, and registers it in the setting information database 106a.

[0052] In addition, the verification process setting unit 102b provides an action setting screen (see FIG. 15) in response to a request from a Web client 400 (developer), and creates an individual definition (see FIG. 16) in response to the developer's operations on the action setting screen, and registers it in the setting information database 106a.

[0053] The focus control setting unit 102c creates setting information (definition) related to focus control and registers it in the setting information database 106a.

[0054] Specifically, for example, the focus control setting unit 102c provides a condition setting screen (see FIG. 19) in response to a request from a Web client 400 (developer), and creates a condition setting definition (see FIG. 20) in response to operations performed by the developer on the condition setting screen, and registers the condition setting definition in the setting information database 106a.

[0055] In addition, the focus control setting unit 102c provides a focus flow setting screen (see Figure 23) in response to a request from a Web client 400 (developer), and creates a focus flow definition (see Figure 24) in response to the developer's operations on the focus flow setting screen, and registers it in the setting information database 106a.

[0056] When an item exit event occurs on the screen of a Web client 400 (business operator) and processing unit 102d receives a request from the Web client including the target control, the input value, whether the value has been changed, and the key at the time of item exit, (1) if there is a value change, processing unit 102d executes a verification process to determine whether the target control exists in the event assignment definition, and if it does, refers to the individual definition and obtains a corresponding return value using the input value of the target control as an argument from the API, and if the return value is not an error, displays the value contained in the return value in the control included in the return value on the screen of Web client 400, and (2) if the key at the time of item exit is a specified key, processing unit 102d executes focus control, refers to the focus flow definition with the target control as the control before the focus transition, and determines whether the transition condition is satisfied, and if the transition condition is satisfied, obtains the control to be the transition destination, sends the response to the Web client, and moves the focus of the screen to the obtained control to be the transition destination.

[0057] When the processing unit 102d receives a request from a Web client, it may send a response to the client including the control, the value to be displayed in the control, and the next focus control, and the Web client may perform processing according to the received response.

[0058] [3. Specific examples of processing] A specific example of the processing of the focus control device 100 (Web server) of this embodiment will be described with reference to Fig. 7 to Fig. 34. Fig. 7 to Fig. 34 are diagrams for explaining a specific example of the processing of the focus control device 100 of this embodiment.

[0059] [3-1. Overview of low-code infrastructure] The low-code platform has a settings screen operated by developers and an execution screen operated by business operators.

[0060] An example of the setting screen is shown in Fig. 7. The developer sets the screen layout and event processing by GUI operations on the setting screen. The information on the setting screen is stored in the setting information database 106a.

[0061] An example of the execution screen is shown in FIG. 8. When the setting information set on the setting screen is read and expanded in the memory on the Web server, the business operator executes the application on the execution screen. The execution screen allows the low-code platform to read the setting information set on the setting screen, expand the setting information in the memory on the Web server, and execute it as a server application and a client Web page (screen + program). A Web page executed on a client's Web browser is called a "client Web page". The client Web page (screen + program) can be configured to be sent from the Web server to the Web client and executed by being read into the Web browser on the Web client. The program of the client Web page can be realized, for example, by a well-known Web application technology (for example, a format including commands and runtime variables written in JavaScript, etc.). The Web server sends the client a Web page (screen and program) to be executed by the client based on the definition information of the application. In the Web client, the Web browser reads and executes the sent Web page, and the client Web page (screen + program) and the server application of the Web server communicate with each other, and the focus control process of the present invention operates cooperatively.

[0062] [3-2. Setting screen] The method of setting on the setting screen will now be specifically described.

[0063] (1) Layout editing screen 9 is a diagram for explaining the layout editing screen. The screen layout setting unit 102a creates a layout definition in response to an operation by a developer on the layout editing screen, and registers the layout definition in the setting information database 106a.

[0064] First, the developer places controls on the layout editing screen shown in Figure 9 with the mouse. Then, using the "+" button, set the item validation event (customer validation process in the example shown in the figure). The generated layout definition (control list) is shown in Figure 10. The layout definition has items for control ID, name, type, and child element ID list.

[0065] (2) Screen variable editing screen 11 is a diagram for explaining the screen variable editing screen. The screen layout setting unit 102a creates screen variable definitions in response to operations performed by the developer on the screen variable editing screen, and registers them in the setting information database 106a.

[0066] The developer sets variables to be temporarily held on the screen on the screen variable edit screen shown in Fig. 11. Fig. 12 is a diagram showing an example of a created screen variable definition. The screen variable definition has items such as variable ID, name, and type.

[0067] (3) Logic flow setting screen 13 is a diagram for explaining the logic flow setting screen. The verification process setting unit 102b creates an event allocation definition in response to an operation by the developer on the logic flow setting screen, and registers the event allocation definition in the setting information database 106a.

[0068] The developer sets the validation process for the item on the logic flow setting screen shown in Figure 13. By setting the API call action as circled in Figure 13, the developer is directed to the action setting screen described in the next paragraph. The event assignment definition that is created is shown in Figure 14.

[0069] (4) Action setting screen 15 is a diagram for explaining the action setting screen. The verification process setting unit 102b creates individual definitions in response to operations performed by a developer on the action setting screen, and registers the definitions in the setting information database 106a.

[0070] The developer sets up the API call on the action setting screen shown in Figure 15. Specifically, the developer selects the API, sets the arguments, and sets the allocation of the return value to the control / screen variable. Figure 16 shows an example of an individual definition of the created customer verification API. Note that the call API is an API for retrieving data from the business system, and the customer verification API receives the customer CD, checks for existence in the customer master in the business system, and retrieves the name.

[0071] Figure 17 shows examples of properties that can be used to get and set the values ​​of each control. Figure 18 shows the definitions when getting and setting values ​​for screen elements. Note that if the API return value is set in a control, it is returned to the client, but if the return value is set in a screen variable, the return value is not returned to the client.

[0072] (5) Condition setting screen 19 is a diagram for explaining the condition setting screen. The focus control setting unit 102c creates a condition definition in response to an operation by a developer on the condition setting screen, and registers the condition definition in the setting information database 106a.

[0073] The developer sets an expression that will be the focus transition condition on the condition setting screen shown in Figure 19. In the example of Figure 19, the condition "if customer account category is TRUE" is set on the condition setting screen. The created condition definition is shown in Figure 20.

[0074] Another example of condition setting is shown in Fig. 21. Also, Fig. 22 shows a table summarizing the items that can be specified on the left and right sides, and a table summarizing the operators.

[0075] (6) Focus flow setting screen 23 is a diagram for explaining the focus flow setting screen. The focus control setting unit 102c creates a focus flow definition in response to an operation by a developer on the focus flow setting screen, and registers the focus flow definition in the setting information database 106a.

[0076] In the focus flow setting screen shown in Fig. 23, the developer sets the transition (setting the transition source, transition setting, transition condition, and transition destination) for the control using the condition definition set in (5). In the example in Fig. 23, the focus is set to transition from the transition source "Customer Text" to the transition destination "Customer Details Button" as the process to be executed when the condition "if Customer Miscellaneous Category is TRUE" is met. The focus flow definition to be created (business rule setting table 106d) is shown in Fig. 24.

[0077] [3-3. Processing flow and internal data when an item is exited] 25 to 34, the processing of the Web server and the Web client when an item exit event occurs on the start screen of the Web client (operator) will be described.

[0078] (1) Processing when the Web server screen is started When the Web server receives a screen launch request from a client, it reads the setting information and saves it in memory (step S1), returns the HTML of the screen and part of the setting information to the client, and causes the client to display the screen (step S2).

[0079] The following two setting information is returned to the client. (A) A list of control IDs to which the event is assigned (for example, event assignment information [1-2,1-6]). (B) A list of controls for which focus transition settings have been made (for example, focus transition information [1-2, 1-6]).

[0080] Fig. 26 is a diagram showing an example of a display of a start-up screen. The example screen in Fig. 26 includes items such as a customer caption, customer text (box), customer name label, customer details button, supplier caption, supplier text (box), supplier name label, and supplier details button.

[0081] (2) Processing when exiting a field in the Web client FIG. 27 is a diagram showing a process flow of a Web client. The process contents (flow) of the Web client shown in FIG. 27 are a part of a process in which a Web browser reads and executes a Web page (screen + program) sent from a Web server when a screen is started. FIG. 28 is a diagram showing a case where a value of a customer text is changed and an Enter key is pressed on a start-up screen. FIG. 29 is a diagram showing an example of a request parameter sent from a Web client to a Web server and a response returned from the Web server, where (A) shows an example of a request parameter, (B) shows an example of a response to the request parameter of (A), and (C) shows an example of a response when an error occurs (reference). FIG. 30 is a diagram for explaining a determination of whether an error occurs. FIG. 31 is a diagram for explaining a determination of whether a next focus destination exists. FIG. 32 is a diagram for explaining an example of a default focus movement. FIG. 33 is a diagram showing an example of a movement to a specified focus destination on a start-up screen.

[0082] In this example, when the customer text "A001" and customer name label "Customer A" are displayed on the startup screen shown in Figure 28 and the focus is on the "Customer Text," if the business operator changes the value of the customer text from "A001" to "A003" and presses the Enter key, the customer name label will display "Customer C" as shown in Figure 33, and the focus will move to the Customer Details button. This is an example of this case.

[0083] In FIG. 27, when an operation is performed on the start screen, it is determined whether the event or focus transition is set for the control (step S11). The method of determining whether a value has changed is that if the value entered in the text box is different from the previous value held, it is determined that the value has changed. The event key can be determined by acquiring which key caused the event to be fired from the event argument that can be acquired when escaping from an item in the text box. More specifically, whether an event or focus transition is set can be determined by whether the event control ID of the text box at the time of escaping from the item exists in the list of control IDs of the event allocation information and focus transition information returned from the Web server to the Web client in the request for the start process of the screen (see FIG. 25). If the event control ID exists in the event allocation information, it is determined that an event has been set, and if the event control ID exists in the focus transition information, it is determined that a focus transition has been set. In this way, the Web client obtains event allocation information and focus transition information in advance when the screen is launched and makes a judgment when an item is exited, eliminating the need to generate a request to the Web server for an inquiry every time. It is possible to make requests to the Web server only when necessary for focus judgment, thereby achieving the effects of the focus control of the present invention while reducing communication load and maintaining operability on the Web client side.

[0084] In step S11, if the control is not set (step S1: No), a default focus movement is performed (step S12). If the control is set (step S11: Yes), a request is made by sending a request parameter to the item exit process (processing unit 102d) of the Web server (step S13).

[0085] The request parameters include the event control ID, event type, input value, value change, and item exit key, as shown in Fig. 29(A). In this example, the request parameters are the event control ID "1-2", event type "verification process", input value "A003", value change "TRUE", and item exit key "Enter".

[0086] When a request is made to the Web server's item exit process, a response is received from the Web server. The Web server processing is explained in Figure 34. As shown in Figure 29(B), the response includes the control ID, property, value, and next focus ID. In this example, the response, as shown in Figure 29(B), is control ID "1-3", property "Value", value "Customer C", and next focus ID "1-4". Note that an example of a response when an error occurs is shown in Figure 29(C). For example, the response is control ID "1-2", property "ErrorMessage", value "Not registered in master", and next focus ID " ".

[0087] When the Web client receives a response from the Web server (see S24 in FIG. 34), it reflects the response result on the screen (step S14). In this example, as shown in FIG. 33, "Customer C" is displayed in the customer name label. Then, the Web server determines whether or not there is an error in the response (step S15).

[0088] The determination of whether or not there is an error is made by checking whether an error message is set in the response control property. In this example, there is no error, as shown in Figure 29(B).

[0089] For example, as shown in Figure 30, if characters are set in the properties of a text box, it is determined to be an error. For example, if the customer text (box) is "A001", it is determined that there is no error. On the other hand, if the customer text (box) is "A004", it is determined that there is an error, and the error message "Not registered in master" is displayed (this is because "A004" is not registered in the reference data (customer master) in Figure 34, which will be described later).

[0090] If there is an error in the response, the process ends (step S17), and if there is no error in the response, it is determined whether the next focus destination is specified in the response (step S16). If the next focus destination is specified, the focus moves to the specified destination (step S18), and if the next focus destination is not specified, the default focus movement is performed (step S12).

[0091] For example, as shown in Fig. 31, whether or not a focus destination has been specified is determined by whether or not the control ID of the next focus in the response has been set. In this example, the control ID of the next focus is "1-4 (Customer details button)," and it is determined that the next focus destination has been specified. In this example, as shown in Fig. 33, the focus on the screen is moved from the Customer text to the Customer details button.

[0092] For example, as shown in FIG. 32, when the value of the Customer text is changed from A001 to A002, if Enter is pressed, the focus moves to the next input-enabled control, and if Tab is pressed, the focus moves to the next control that can receive focus.

[0093] (3) Processing when an item is exited from the Web server Fig. 34 is a diagram showing the process flow of the Web server. In this example, a case will be described as an example in which the request parameters shown in Fig. 29(A) are received from the Web client and the response shown in Fig. 29(B) is returned.

[0094] In Fig. 34, when the Web server receives a request parameter from a Web client (see S13 in Fig. 27), it determines whether the value has changed (step S21). If the value has not changed (step S21: No), it proceeds to step S22. If the value has changed (step S21: Yes), it performs processing according to the verification process settings (step S25).

[0095] The validation process checks whether the event control ID of the request parameter exists in the event assignment definition (Figure 14), and if it does, refers to the individual definition (Figure 16), and uses the input value of the control of the request parameter as an argument to obtain the corresponding return value from the master of the referenced business system via the call API. If the return value cannot be obtained from the master (if it is not registered in the master), an error occurs.

[0096] Next, it is determined whether or not there is an error in the verification process (step S26), and if there is an error, the process is terminated and a response is returned (step S27).If there is no error (step S26 "NO"), the process proceeds to step S22.

[0097] Next, in step S22, it is determined whether the key used to exit the item of the request parameters is the Enter key or not, and if it is anything other than the Enter key, the process is terminated and a response is returned (step S28).

[0098] In the case of the Enter key, processing is performed according to the focus control settings (step S23). Specifically, the focus flow definition (FIG. 24) is referenced, and the event control ID of the request parameter is set as the transition source, and it is determined whether or not the transition condition is met. If the condition is met, the transition destination control ID is obtained and a response is returned to the Web client (step S24).

[0099] In this example, the request parameters shown in Figure 29 (A) indicate a value change and are determined to be "True," and the control ID "1-2 (Customer Text)" is present in the event assignment definition (Figure 14). By referring to the individual definition (Figure 16), the customer verification API obtains the corresponding return values ​​"Customer C" and "Miscellaneous category = TRUE" from the customer master (reference data) of the referenced business system, using the value "A0003" entered in the customer text as an argument.

[0100] As the key used to exit the item is the "Enter key", the event control ID is used as the transition source, and the focus flow definition (Figure 24) is referenced to determine whether the transition condition "CID01" is met. The condition setting for "CID01" is Customer miscellaneous category = fixed value (True) according to the condition definition (Figure 20), and A003 in the customer master is in the miscellaneous category "True", so the transition destination control "1-4 (Customer details button)" is obtained, and the response shown in Figure 29 (B) is returned to the Web client.

[0101] As described above, the focus control device of this embodiment includes an event assignment definition that assigns a verification process to a control that is an element constituting a screen, an API for acquiring data in the verification process, an individual definition that sets arguments and return values, a focus flow definition that sets a control before focus transition, a transition condition, and a control to which focus transition is to be made, and when an item exit event occurs on a client screen and a request is received from the client that includes the target control, input value, whether or not the value has changed, and a key at the time of item exit, (1) if the value has changed, executes a verification process and determines whether or not the target control exists in the event assignment definition, and if the target control exists, references the individual definition and retrieves the corresponding return value from the API using the input value of the target control as an argument. and (2) if the key used to exit the item is a specified key, executes focus control, refers to the focus flow definition with the target control as the control before the focus transition, and determines whether or not the transition condition is satisfied. If the transition condition is satisfied, obtains a control of the transition destination, and moves the focus of the client screen to the obtained control of the transition destination. Therefore, by managing the verification process and focus control of the input items on the screen as two separate settings rather than defining them as a single process setting, it is possible to reduce branching processes, prevent implementation omissions and implementation errors, and improve quality.

[0102] [4. Contribution to the United Nations-led Sustainable Development Goals (SDGs)] This embodiment can contribute to improving business efficiency and promoting appropriate management decisions by companies, thereby contributing to goals 8 and 9 of the SDGs.

[0103] Furthermore, this embodiment can contribute to reducing waste and promoting paperless and electronic systems, thereby contributing to the achievement of SDGs Goals 12, 13, and 15.

[0104] Furthermore, this embodiment can contribute to strengthening control and governance, making it possible to contribute to Goal 16 of the SDGs.

[0105] 5. Other embodiments The present invention may be embodied in various different embodiments other than those described above within the scope of the technical concept set forth in the claims.

[0106] For example, among the processes described in the embodiments, all or part of the processes described as being performed automatically can be performed manually, or all or part of the processes described as being performed manually can be performed automatically using known methods.

[0107] In addition, the processing procedures, control procedures, specific names, information including parameters such as registered data and search conditions for each process, screen examples, and database configurations shown in this specification and drawings may be changed as desired unless otherwise specified.

[0108] Moreover, with regard to the focus control device 100, the components shown in the figures are merely conceptual functional elements, and the components do not necessarily have to be physically configured as shown in the figures.

[0109] For example, the processing functions of the focus control device 100, particularly the processing functions performed by the control unit, may be realized in whole or in part by a CPU and a program interpreted and executed by the CPU, or may be realized as hardware using wired logic. The program is recorded in a non-transient computer-readable recording medium including programmed instructions for causing the information processing device to execute the processes described in this embodiment, and is mechanically read by the focus control device 100 as necessary. That is, a computer program for giving instructions to the CPU in cooperation with the OS and performing various processes is recorded in a storage unit such as a ROM or HDD (Hard Disk Drive). This computer program is executed by being loaded into a RAM, and constitutes a control unit in cooperation with the CPU.

[0110] In addition, this computer program may be stored in an application program server connected to the focus control device 100 via any network, and it is also possible to download all or a part of it as necessary.

[0111] In addition, the program for executing the process described in this embodiment may be stored in a non-transient computer-readable recording medium, or may be configured as a program product. Here, the "recording medium" includes any "portable physical medium" such as a memory card, a Universal Serial Bus (USB) memory, a Secure Digital (SD) card, a flexible disk, a magneto-optical disk, a ROM, an Erasable Programmable Read Only Memory (EPROM), an Electrically Erasable and Programmable Read Only Memory (EEPROM (registered trademark)), a Compact Disk Read Only Memory (CD-ROM), a Magneto-Optical disk (MO), a Digital Versatile Disk (DVD), and a Blu-ray (registered trademark) Disc.

[0112] Moreover, a "program" is a data processing method written in any language or description method, and may be in any form, such as source code or binary code. Note that a "program" is not necessarily limited to a single configuration, but also includes a distributed configuration as multiple modules or libraries, and a program that works with a separate program, such as an OS, to achieve its function. Note that the specific configuration and reading procedure for reading a recording medium in each device shown in the embodiments, as well as the installation procedure after reading, may use well-known configurations and procedures.

[0113] The various databases etc. stored in the memory unit are storage means such as memory devices such as RAM and ROM, fixed disk devices such as hard disks, flexible disks, and optical disks, and store various programs, tables, databases, and web page files etc. used for various processes and providing websites.

[0114] The focus control device 100 may be configured as an information processing device such as a known personal computer or a workstation, or may be configured as the information processing device to which any peripheral device is connected. The focus control device 100 may be realized by installing software (including programs, data, etc.) that causes the device to realize the processing described in this embodiment.

[0115] Furthermore, the specific form of distribution and integration of the devices is not limited to that shown in the drawings, and all or part of them can be functionally or physically distributed and integrated in any unit according to various additions or functional loads. In other words, the above-mentioned embodiments can be implemented in any combination, or the embodiments can be implemented selectively. [Industrial Applicability]

[0116] The present invention is useful, for example, in fields where a screen display is required. [Explanation of symbols]

[0117] 100 Focus control device (Web server) 102 Control section 102a Screen layout setting section 102b Verification process setting section 102c Focus control setting section 102d Processing section 104 Communication interface section 106 Storage section 106a Configuration information database 108 Input / Output Interface Section 112 Input Devices 114 Output Device 300 Network 400 Web Client

Claims

1. A focus control device including a control unit and configured to be capable of data communication with a client, The control unit is An event assignment definition that assigns validation processing to the controls that are the elements that make up the screen, An API for acquiring data in a verification process, and individual definitions in which arguments and return values ​​are set; A focus flow definition that sets the control before the focus transition, the transition condition, and the control to which the focus transition is to be made. The storage area storing the A focus control device characterized by comprising: when an item exit event occurs on a client screen and a request is received from the client including a target control, an input value, whether or not the value has been changed, and a key at the time of item exit, (1) if the value has been changed, the device executes a verification process to determine whether the target control exists in the event assignment definition, and if so, refers to the individual definition and obtains a corresponding return value from the API using the input value of the target control as an argument, and if the return value is not an error, displays the value contained in the return value in the control contained in the return value on the client screen; and (2) if the key at the time of item exit is a specified key, the device executes focus control, refers to the focus flow definition with the target control as the control before focus transition, and determines whether the transition condition is satisfied, and if the transition condition is satisfied, obtains the control of the transition destination, and moves the focus of the client screen to the obtained control of the transition destination.

2. The focus control device is a Web server, and the client is a Web client; 2. The focus control device according to claim 1, wherein the focus control device provides a Web page including a screen to be displayed on the client and a program for causing the client to execute a predetermined operation, and the client executes the Web page provided by a Web browser.

3. The control unit further includes: a verification process setting means for creating the event allocation definition and the individual definition in response to an operation by a developer on a setting screen and registering them in the storage area; a focus control setting means for creating the focus flow definition and registering it in the storage area in response to an operation by a developer on a setting screen; 2. The focus control device according to claim 1, further comprising:

4. 2. The focus control device according to claim 1, wherein when the processing means receives a request from the client, the processing means transmits a response to the client including a control, a value to be displayed in the control, and a control for the next focus, and the client performs processing according to the received response.

5. The focus control device according to any one of claims 1 to 4, characterized in that the focus control device is configured on a low-code basis or a no-code basis.

6. A focus control method executed by an information processing device including a control unit and configured to be capable of data communication with a client, comprising: The control unit is An event assignment definition that assigns validation processing to the controls that are the elements that make up the screen, An API for acquiring data in a verification process, and individual definitions in which arguments and return values ​​are set; A focus flow definition that sets the control before the focus transition, the transition condition, and the control to which the focus transition is to be made. The storage area storing the Executed in the control unit: A focus control method characterized by comprising the steps of: (1) if an item exit event occurs on a client screen and a request is received from the client including a target control, an input value, whether or not the value has been changed, and a key at the time of item exit, (1) if the value has been changed, executing a verification process to determine whether the target control exists in the event assignment definition, and if so, referring to the individual definition and using the input value of the target control as an argument from the API to obtain a corresponding return value, and if the return value is not an error, displaying the value contained in the return value in a control included in the return value on the client screen; and (2) if the key at the time of item exit is a specified key, executing focus control, referring to the focus flow definition with the target control as the control before focus transition, determining whether the transition condition is satisfied, and if the transition condition is satisfied, obtaining the control of the transition destination, and moving the focus of the client screen to the obtained control of the transition destination.

7. A focus control program to be executed by an information processing device having a control unit and configured to be capable of data communication with a client, The control unit is An event assignment definition that assigns validation processing to the controls that are the elements that make up the screen, An API for acquiring data in a verification process, and individual definitions in which arguments and return values ​​are set; A focus flow definition that sets the control before the focus transition, the transition condition, and the control to which the focus transition is to be made. The storage area storing the In the control unit, A focus control program for executing a processing step in which, when an item exit event occurs on a client screen and a request is received from the client including a target control, an input value, whether or not the value has been changed, and a key at the time of item exit, (1) if the value has been changed, a verification process is executed, and it is determined whether or not the target control exists in the event assignment definition, and if it does exist, it refers to the individual definition and uses the input value of the target control as an argument from the API to obtain a corresponding return value, and if the return value is not an error, it causes the value contained in the return value to be displayed in the control contained in the return value on the client screen, and (2) if the key at the time of item exit is a specified key, it executes focus control, refers to the focus flow definition with the target control as the control before focus transition, and determines whether the transition condition is satisfied, and if the transition condition is satisfied, it obtains the control to be the transition destination, and moves the focus of the client screen to the obtained transition destination control.

Citation Information

Patent Citations

  • Window input / Output device

    JP1995281880A

  • Input supporting method, input supporting program, recording medium and data processing system

    JP2003058290A

  • Data processor and data processing program

    JP2007156980A

  • GUI component display device and GUI component display method

    JP2008191993A

  • Information processing system, method for controlling information processing system, and program

    JP2015111413A