JP7772677B2 - Information processing device, information processing method, and information processing program - Google Patents

Description

The present invention relates to an information processing device, an information processing method, and an information processing program.

Technologies for preventing data tampering are known today. For example, the form printing control device disclosed in Patent Document 1 (JP 2004-094818 A) extracts distribution-related information embedded in a file that combines forms and embedded data and is distributed from a server, and stores the extracted distribution-related information in a history. It then determines whether the file can be printed based on the stored history information. It also re-executes processing for the same distributed file depending on the processing status. It also deletes the distributed file when it is no longer needed. This prevents tampering with forms and embedded data.

Japanese Patent Application Laid-Open No. 2004-094818

However, in the past, it was necessary to consider from the design stage that request data values should not be used as is. This required individual implementation on every screen of the application program, making it difficult to easily prevent data tampering.

The present invention was made in consideration of the above-mentioned problems, and aims to provide an information processing device, information processing method, and information processing program that can easily prevent data tampering.

To solve the above-mentioned problems and achieve the objectives, the information processing device of the present invention has a display control unit that displays an input screen on a display unit; a determination unit that, when input is made into an item included in the input screen, references setting information stored in a memory unit indicating whether the value of each item on the input screen can be changed and determines whether the value of the item input via the input screen is a changeable item; and an information processing unit that, if the determination result indicates that the value of the item input via the input screen can be changed, supplies an information processing result corresponding to the value of the input item to the display control unit; and, if the determination result indicates that the value of the item input via the input screen cannot be changed, discards the value of the input item, maintains the previous value, and supplies an information processing result corresponding to the previous value to the display control unit.

In order to solve the above-mentioned problems and achieve the objectives, the information processing method of the present invention includes a display control step in which a display control unit displays an input screen on a display unit; a determination step in which, when input is made into an item included in the input screen, a determination unit references setting information stored in a storage unit indicating whether the value of each item on the input screen can be changed and determines whether the value of the item input via the input screen is a changeable item; and an information processing step in which, if a determination result indicating that the value of the item input via the input screen can be changed is obtained, the information processing unit supplies an information processing result corresponding to the value of the input item to the display control unit, and, if a determination result indicating that the value of the item input via the input screen cannot be changed is obtained, the information processing unit discards the value of the input item, maintains the previous value, and supplies the information processing result corresponding to the previous value to the display control unit.

In order to solve the above-mentioned problems and achieve the objective, the information processing program of the present invention causes a computer to function as a display control unit that displays an input screen on a display unit; a discrimination unit that, when input is made into an item included in the input screen, references setting information stored in a memory unit indicating whether the value of each item on the input screen can be changed and determines whether the value of the item input via the input screen is a changeable item; and an information processing unit that, if a discrimination result indicating that the value of the item input via the input screen can be changed is obtained, supplies an information processing result corresponding to the value of the input item to the display control unit; and, if a discrimination result indicating that the value of the item input via the input screen cannot be changed is obtained, discards the value of the input item, maintains the previous value, and supplies the information processing result corresponding to the previous value to the display control unit.

This invention makes it easy to prevent data tampering.

FIG. 1 is a block diagram showing the system configuration of a Web application system and the hardware configuration of a server device according to a first embodiment. FIG. 2 is a diagram showing a typical usage pattern of a Web application system. FIG. 3 is another diagram showing a typical usage pattern of a Web application system. FIG. 4 is a diagram for explaining an illegal use pattern due to data tampering in a Web application system. FIG. 5 is a diagram showing an outline of the operation for preventing data tampering in the Web application system according to the first embodiment. FIG. 6 is a diagram for explaining how the Web application system of the first embodiment responds to a data change based on business rules. FIG. 7 is a diagram showing an example of set business rules. FIG. 8 is another diagram showing an outline of the operation for preventing data tampering in the Web application system according to the first embodiment. FIG. 9 is a diagram showing an outline of the operation for preventing unauthorized button operations in the Web application system according to the first embodiment. FIG. 10 is a diagram showing an example of a panel configuration of an input screen. FIG. 11 is a diagram for explaining the hierarchical structure of each piece of data corresponding to the panel configuration of the input screen in the Web application system according to the first embodiment. FIG. 12 is a diagram showing a development form of an information processing program used in a Web application system. FIG. 13 is a diagram showing how an information processing program developed in a Web application system is used. FIG. 14 is a diagram showing a development form of an information processing program used in a Web application system. FIG. 15 is a diagram showing an example of a layout definition (control list). FIG. 16 is a diagram for explaining the setting of the logic flow. FIG. 17 is a diagram showing an example of various definitions used to set a logic flow. FIG. 18 is a diagram for explaining action settings. FIG. 19 is a diagram showing an example of setting an API for acquiring data from a business database as an action setting. FIG. 20 is a diagram for explaining the allocation of events to buttons. FIG. 21 is a diagram for explaining the setting of business rules. FIG. 22 is a diagram showing an example of a layout definition. FIG. 23 is a diagram showing an example of a conditional expression indicating a condition of a business rule. FIG. 24 is a diagram showing an example of the correspondence between each condition and a conditional expression. FIG. 25 is a diagram showing conditional expressions corresponding to the respective conditions. FIG. 26 is a diagram showing another example of a conditional expression indicating a condition of a business rule. FIG. 27 is a diagram showing the relationship between items and values used in a conditional expression. FIG. 28 is a diagram showing an example of operators used in a conditional expression. FIG. 29 is a diagram showing an example of setting business rules for each control. FIG. 30 is a diagram showing an example of setting information of a business rule. FIG. 31 is a flowchart showing the first half of the flow of processing a request from a user terminal device by a server device of a Web application system. FIG. 32 is a flowchart showing the latter half of the flow of processing a request from a user terminal device by a server device of a Web application system. FIG. 33 is a diagram showing various definitions and business rules that the server device refers to when it receives a request from a user terminal device. FIG. 34 is a diagram illustrating an example of session management data. FIG. 35 shows a list of business rules and a list of conditions that are referred to when evaluating business rules. FIG. 36 is a diagram showing an example of session management data after evaluation of the business rules. FIG. 37 shows an example of a request made by changing values on an input screen displayed based on session management data after evaluation of a business rule. FIG. 38 shows session management data in a state where a request has been accepted as a result of fraudulent determination. FIG. 39 shows a list of business rules and a list of conditions that are referred to when evaluating business rules. FIG. 40 is a diagram showing an example of session management data generated based on the evaluation results of the business rules. FIG. 41 shows an example of a request in which the tax-inclusive price value on the input screen displayed based on the session management data after evaluation of the business rules has been fraudulently changed. FIG. 42 shows session management data in a state where the previous value is maintained because the request was not accepted as a result of the fraud determination. FIG. 43 is a diagram showing an example of various definitions that are referenced when the registration button is operated. FIG. 44 shows a list of business rules and a list of conditions that are referred to when evaluating business rules. FIG. 45 is a diagram showing an example of session management data after evaluation of the business rules. FIG. 46 is a diagram showing an example of an input screen displayed based on the session management data after the evaluation of the business rules. FIG. 47 is a block diagram showing the hardware configuration of a user terminal device according to the second embodiment.

Below, a web application system and user terminal device that are embodiments of the present invention will be described in detail with reference to the drawings. However, the present invention is not limited to such embodiments.

[First embodiment]
First, a Web application system will be described as a first embodiment to which the present invention is applied.

(System and hardware configuration)
1 is a block diagram showing the system configuration of a Web application system according to a first embodiment, and the hardware configuration of a server device 1 provided in the Web application system. As shown in Fig. 1, the Web application system is configured by interconnecting the server device 1, a developer terminal device 30, and a user terminal device 40 via a network 5, which may be a wide area network such as the Internet or a private network such as a LAN (Local Area Network). The server device 1, the developer terminal device 30, and the user terminal device 40 can be realized using general personal computers, and communicate with each other mainly via Web browsers 13, 31, and 41.

The developer develops an information processing program that prevents data tampering by evaluating requests from user terminal devices 40 on the developer terminal device 30 based on the business rules described below, and transmitting data processed based on the evaluation results to the user terminal device. In this first embodiment, the information processing program is a so-called web application program. Therefore, the information processing program is stored in the memory unit 2 of the server device 1 and executed by the control unit 3.

The server device 1 also has a database (DB) 11 in the storage unit 2. The server device 1 executes an information processing program in response to a request from the user terminal device 40. The server device 1 then reads data corresponding to this information processing from the database (DB) 11 and provides (transmits) it to the user terminal device 40 via the communication interface unit 4 and the network 55.

(Hardware configuration of server device)
The server device 1 includes a storage unit 2, a control unit 3, and a communication interface unit 4. The communication interface unit 4 is connected to the above-mentioned network 55, which is, for example, a wide area network such as the Internet or a private network such as a LAN (Local Area Network).

The storage unit 2 can be, for example, a storage device such as ROM (Read Only Memory), RAM (Random Access Memory), HDD (Hard Disk Drive), or SSD (Solid State Drive). The storage unit 2 stores the information processing program developed by the developer terminal device 30, and also includes a database (DB) 11, which is a storage area for storing data provided to the user terminal device 40. The storage unit 2 also stores various data that are referenced or generated based on the information processing program, such as layout definitions, event assignment definitions, logic flow definitions, action definitions, flow definitions, individual settings, condition settings, and business rule settings.

(Functional configuration of the server device)
Next, the control unit 3 of the server device 1 executes the information processing program stored in the memory unit 2, and thereby functions as a display control unit 21, a discrimination unit 22, an information processing unit 23, and a communication control unit 24, as shown in FIG. 1.

In this first embodiment, the display control unit 21 and communication control unit 24 together constitute an example of a display control unit. The display control unit 21 generates an input screen to be displayed on the display unit of the user terminal device 40 and supplies it to the communication control unit 24. The communication control unit 24 controls the communication of the communication interface unit 4, which is an example of a communication unit, so as to transmit the generated input screen to the user terminal device 40 via the network 55. The user terminal device 40 displays the transmitted input screen on the display unit via the web browser 41.

When input is made into items included in the input screen via the user terminal device 40, the determination unit 22 references the setting information (business rule settings, described below) stored in the memory unit 2 that indicates whether the value of each item on the input screen can be changed, and determines whether the value of the item entered via the input screen is a changeable item.

When the discrimination unit 22 obtains a discrimination result indicating that the value of the item entered via the input screen can be changed, the information processing unit 23 reads (or processes) data corresponding to the input item value from the database 11, which is the result of information processing, and supplies this data to the display control unit 21. The display control unit 21 generates an input screen including the data read from the database 11 (or the processed data). The communication control unit 24 transmits the generated input screen to the user terminal device 40. As a result, an input screen corresponding to the user's input operation is displayed on the display unit of the user terminal device 40.

Furthermore, if the discrimination unit 22 obtains a judgment result indicating that the value of an item entered by the user via the input screen cannot be changed, the information processing unit 23 discards the entered value of the item and maintains the previous value. In this case, the information processing unit 23 reads (or processes) data corresponding to the previous value from the database 11, which is the result of information processing, and supplies this data to the display control unit 21. The display control unit 21 generates an input screen including the data read from the database 11 (or the processed data). The communication control unit 24 transmits the generated input screen to the user terminal device 40. As a result, the value entered by the user's unauthorized input operation is discarded, and the input screen corresponding to the previous value is displayed on the display unit of the user terminal device 40. This prevents data tampering.

Furthermore, when the discrimination unit 22 provides a discrimination result indicating that the value of an item entered by the user via the input screen cannot be changed, the display control unit 21 generates an error screen that displays a predetermined error. The communication control unit 24 transmits the generated error screen to the user terminal device 40. This allows the user to recognize that the entered value cannot be accepted.

In addition, the above-mentioned setting information (business rule settings, described below) can be set to prohibit changes to items or buttons in the main panel, which corresponds to the entire input screen, or to prohibit changes to items or buttons included in a partial panel, which corresponds to a portion of the input screen.

If the setting prohibits changing items or buttons in the main panel, the discrimination unit 22 determines that all items or buttons in the main panel cannot be changed. Furthermore, if the setting prohibits changing items or buttons in a partial panel, the discrimination unit 22 determines that all items or buttons in the partial panel cannot be changed.

In other words, the setting information described above has a hierarchical structure in which items are in the lower hierarchy, partial panels and buttons are in the middle hierarchy, and the main panel is in the upper hierarchy. Therefore, the discrimination unit 22 determines whether or not there is a setting that prohibits changes in the lower hierarchy, middle hierarchy, and upper hierarchy, in that order. If the discrimination unit 22 detects a setting that prohibits changes in the upper hierarchy, it determines that all items and buttons included in the main panel cannot be changed; if the discrimination unit 22 detects a setting that prohibits changes in the middle hierarchy, it determines that all items and buttons included in the partial panel cannot be changed. Furthermore, if the discrimination unit 22 detects a setting that prohibits changes in the lower hierarchy, it determines that items that are set to prohibit changes cannot be changed.

In addition, when the conditions of a specified conditional expression are met, one of the following processes can be set for each item as the setting information: a process to lock the item, which makes the item's value unchangeable, or a process to hide the item. This will be described in more detail later.

(The flow from request to response in a typical web application system)
Here, we will explain the flow from request to response in a typical web application system. Figures 2(a) to 2(c) show an example of a typical web application system in which a general user at Tokyo Store No. 2 (TKY002) makes a request to "launch a sales list" via a web browser on a user terminal device (Figure 2(a)). In this case, because the user making the request (i.e., the logged-in user) is a "general user," the server device generates an input screen based on session management data in which the store values for Tokyo Store No. 2 (TKY002) are initially set and locked (unchangeable), and sends the input screen to the user terminal device (Figure 2(b)). Note that if the logged-in user is an "administrator," the store will not be locked. As a result, an input screen with the store information for Tokyo Store No. 2 (TKY002) locked is displayed on the user terminal device, as shown in Figure 2(c).

Next, as shown in Figure 3(a), the user of the user terminal device inputs the sales period (sales dates) they wish to view, such as "July 1, 2021 to July 31, 2021," into the input screen and makes a request to the server device. As shown in Figure 3(b), the server device retrieves sales data for Tokyo Store No. 2 (TKY002) from the database for the period from July 1, 2021 to July 31, 2021, and sends it to the user terminal device. As a result, sales information for Tokyo Store No. 2 (TKY002) is displayed in a list for each sales date, as shown in Figure 3(a).

(If store information is changed fraudulently)
Next, in such a typical web application system, as shown in FIG. 4(a), assume that the value of a control (item) for Tokyo Store No. 2 (TKY002) is fraudulently changed to "NULL data," and a request is made to the server device to obtain sales data for the period from July 1, 2021, to July 31, 2021. If no countermeasures are taken to prevent this fraud, the server device will retrieve sales data for all stores from the database for the period from July 1, 2021, to July 31, 2021, and transmit it to the user terminal device, due to the store information being changed to "NULL data." This creates the inconvenience of allowing a general user of Tokyo Store No. 2 (TKY002) to fraudulently view sales data for all stores on the user terminal device, as shown in FIG. 4.

To prevent this kind of fraud, it was necessary to implement a control for each and every screen in the web application system that would use the store value for a sales data retrieval request if the currently logged-in user was a general user, using the store to which the user belonged (the value would be re-obtained from cache memory or a database at startup, for example), and use the value of the control (the field where store information was entered) if the currently logged-in user was an administrator. This required a lot of effort to prevent data tampering.

(Outline of the Web Application System According to the Embodiment)
Therefore, in the first Web application system, when the store information that is in a locked state as shown in Figure 5(a) is illegally changed to "NULL data" and a request is made from the user terminal device 40, the server device 1 determines whether the user who made the request has the authority to change the store information based on the business rule setting described later. In this example, if the logged-in user is a general user, the server device 1 determines that the user does not have the authority to change the store information, discards the value of the request (in this case, the changed store information), and processes the request with the previous store information (before the illegal change).

Even if the lock is released on the user terminal device 40 side and the value is changed illegally (including illegal execution using JavaScript (registered trademark)), if the status on the user terminal device 40 side and the server device 1 side do not match, the data is considered to have been tampered with and the requested value is not accepted.

The web application system of the first embodiment also supports dynamic locking or hiding state control based on business rule settings, selecting the parameters to accept depending on the state. Furthermore, in the web application system of the first embodiment, all changes to values that are the starting point for business rule settings (for example, tax category items) generate server requests to manage the state (locking or hiding).

Figure 6(a) shows an example in which the "Tax Category" item has been changed from "2: Tax Included" to "1: Tax Excluded" by the user terminal device 40. Each time the server device 1 receives such a request, it performs the following steps: "Check the value of the invalid request" → "Execute the logic flow associated with the control (item)" → "Evaluate the business rules."

Specifically, for the "tax category", the user can select, for example, "0: tax exempt", "1: tax excluded" or "2: tax included", as shown in Fig. 7. In addition, as a business rule to be described later, as shown in Fig. 7,
- Amount excluding tax If tax category = (2), lock
・Consumption tax amount If tax category = (0), lock
・Amount including tax If tax category = (0) or tax category = (1), lock.
It is assumed that the following settings have been made.

In this case, the server device 1 accepts a request to change the "Tax Category" item from "2: Tax Included" to "1: Tax Excluded" because the item is not locked, and changes the tax category in the session management data from "2" to "1" as shown in Figure 6(b). Note that no event is set for when the tax category value is changed, so the server device 1 does nothing.

The server device 1 also changes the tax category in the session management data from "2" to "1," unlocks the tax-excluded amount, as shown in FIG. 6(b), and generates an input screen in which the tax-inclusive amount is locked, and sends it to the user terminal device 40. As a result, an input screen in which the tax category is set to "1: Tax Excluded" is displayed on the user terminal device 40, as shown in FIG. 8(a).

Next, as shown in Figure 8(a), assume that a user of user terminal device 40 fraudulently changes the tax-inclusive price of "33,000 yen" to "100 yen" and makes a request. In this case, server device 1 also performs the following steps: "Check the value of the fraudulent request" → "Execute the logic flow associated with the control (item)" → "Evaluate the business rules."

However, as shown in Figure 7, the business rule is set to lock the tax-inclusive amount when tax category = (0) or tax category = (1). In this example, the tax category has been changed from "2" to "1," so the tax-inclusive amount is locked. Therefore, when the server device 1 "checks the value of the invalid request," it does not accept the tax-inclusive amount because it is currently locked. The server device 1 also executes the processing of the registration button in "executing the logic flow associated with the control (item)."

In addition, in this example, the server device 1 does nothing in "Evaluating Business Rules" because the set business rule value (tax category) has not changed. Then, because the evaluation of the business rules indicates that the tax-inclusive amount is currently locked, the server device 1 does not accept a request to change the tax-inclusive amount to "100 yen." Instead, it generates an input screen with the tax-inclusive amount locked at "33,000 yen" as shown in Figure 8(b) and sends it to the user terminal device 40. As a result, even if the user fraudulently changes the tax-inclusive amount to "100 yen," it is possible to send and display an input screen with the tax-inclusive amount locked at the previous "33,000 yen" as shown in Figure 8(c) to the user terminal device 40 (easily preventing data tampering).

Next, the Web application system of the first embodiment can prevent the tampering of the above-mentioned values, as well as the execution of unauthorized events. For example, suppose that the Register button is locked due to business rule settings, and a user illegally unlocks the Register button and operates it, as shown in Figure 9(a). In this case, a request is made to the server device 1 to register the values of each item on the input screen, such as the tax category (1: excluding tax) and tax amount (30,000 yen).

In this case, the server device 1 performs the following sequence, as described above: "Check the value of the invalid request" → "Execute the logic flow associated with the control (item)" → "Evaluate the business rules." In "Check the value of the invalid request," it determines that the values of each item have not changed. In "Execute the logic flow associated with the control," because the registration button is locked, the server device 1 does not execute the event that registers the values of each item in the database, as shown in Figure 9(b), and returns a response to the user terminal device 40 indicating a system error. Subsequent business rules are not evaluated. As a result, a system error (illegal execution) is displayed on the display unit via the web browser 41 of the user terminal device 40, as shown in Figure 9(c).

As described above, in the Web application system of the first embodiment, when an item is controlled by locking or hiding it on the server device 1 side, the parameters (values of each item) sent in a request from the user terminal device 40 are not reflected in the session management data managed by the server device 1. In addition, in the Web application system of the first embodiment, even if the parent panel of a control (item or button) placed on a panel is locked or hidden, the parameters of the control in that locked panel are not accepted.

That is, as shown in FIG. 10, the panels provided are a main panel 61, which corresponds to the entire input screen, and an input panel 60, which is an example of a partial panel that corresponds to a portion of the input screen. The main panel 61 includes the input panel 60, each item in the input panel 60, and various buttons such as a register button 62. The input panel 60 includes each item.

That is, the data for the main panel 61, input panel 60, each item, and registration button 62 has a hierarchical structure as shown in FIG. 11. The data for the main panel 61, input panel 60, each item, and registration button 62 has a hierarchical structure as shown in FIG. 11, with the root data at the top level, the main panel 61 data at the top level, the input panel 60 and registration button 62 data at the middle level, and the data for each item at the bottom level.

The server device 1 checks whether each control (item or button in a lower hierarchy) is locked or hidden in order up to the root (top hierarchy), and when it detects that a control is locked or hidden, it stops checking and controls itself so as not to accept requests from the user terminal device 40.

In other words, the server device 1 checks items in the lower hierarchy, for example, in the order of the tax category item (select box) → input panel 60 → main panel 61 → root. As an example, if the input panel 60 is locked, as can be seen from Figure 10, the tax category item (select box) provided within the input panel 60 will also be locked. Therefore, the server device 1 terminates the check process when it detects that the input panel 60 is locked, and determines that the tax category item (select box) is locked. The server device 1 then controls so as not to accept requests from the user terminal device 40 for the locked tax category item (select box).

(Development form of information processing program)
Next, the development operation of an information processing program will be described. The development of this information processing program is performed on a developer terminal device 30, as shown in Figure 12. A developer operating the developer terminal device 30 develops an information processing program based on, for example, a low-code development platform, and the developed program is stored in the database 11 via the web browser 13 of the server device 1.

Information processing programs may also be developed using no-code development or full-scratch development. However, with low-code development, as described below, information processing programs can be developed relatively easily by combining screen components or logic components through visual operations based on a GUI (graphical user interface), and more detailed settings and control can be made than with no-code development.

(Use of information processing programs)
13 shows a usage form in which an information processing program stored in server device 1 is used as a so-called web application program on user terminal device 40. As shown in FIG. 13, a request from user terminal device 40 is sent to server device 1 via web browser 41. Server device 1 acquires the request via web browser 13, acquires data corresponding to this request from database 11, and transmits it to user terminal device 40 via web browser 13. As a result, data provided from the database of server device 1 (= data requested by user terminal device 40) can be displayed on the display unit via web browser 41 of user terminal device 40 and used.

(Information processing program development operation)
Next, we will explain the development operations of an information processing program performed by a developer via the developer terminal device 30. As an example, by using low-code, a developer develops an information processing program by combining screen components or logic components through visual operations based on a GUI (Graphical User Interface), as shown in FIG. 14. FIG. 14 shows an example of developing (designing and editing) an input screen. In this example, the desired control is selected from a list of controls and placed on the input screen. This allows for easy editing of the input screen layout.

Figure 15 is an example of a layout definition (control list) corresponding to the input screen of Figure 14. The layout definition stores the control identification number (control ID), name, type, and child element IDs of child elements in association with each other. For example, for a "page" with a control ID of "ID0," a "command bar" with "ID1" and a "main panel" with "ID2" are associated as child elements.

Furthermore, the "Main Panel" with "ID2" has the "Header Panel" with "ID3" and the "Detail Panel" with "ID12" associated as child elements. Furthermore, the "Detail Control" with "ID13" has the "Grid Panel (Column)" with "ID14" and the "Grid Panel (Data Row)" with "ID19" associated as child elements.

Once the layout of the input screen has been defined in this way, the developer then sets the processing (action) to be performed when the display button is clicked from the list of actions on the logic flow setting screen shown in Figure 16. In the example in Figure 16, the action "Call API" has been set for "Get sales data."

Next, the developer sets the arguments and return values for the "API call" action, as shown in Figure 18. The example in Figure 16 shows an example in which the arguments "Store Code," "Start of Sales Date," and "End of Sales Date" are set for the "API call" of "Get Sales Data," and the return values are "Sales Date," "Sales Number," "Customer Name," and "Product."

Next, the developer selects the desired control on the layout editing screen shown in Figure 20 and assigns an event. Figure 20 shows an example in which the "Get Sales Data" event is assigned to the click of the "Display Button." The type of event varies depending on the control; a "Verification Event" can be assigned to a "Text Box" control, a "Value Change Event" can be assigned to a "Select Box" control, and "Row Selection" or "Row Double-Click" can be assigned to a "Details Control" control.

By editing the layout (Figure 14), setting the logic flow (Figure 16), setting the actions (Figure 18), and allocating events (Figure 20) in this way, the event allocation definition shown in Figure 17(a), the logic flow definition shown in Figure 17(b), the action definition shown in Figure 17(c), and the flow definition shown in Figure 17(d) are stored in the memory unit 2 of the server device 1. Figure 17 shows a setting where "Sales Data Acquisition" is performed by "clicking" the display button. It also shows that the "Sales Data Acquisition" event shown in Figure 19 is assigned to the "API Call" shown in Figure 17(c).

(Setting business rules)
Next, the developer sets business rules for each control (item) on the input screen that indicate whether or not values can be changed in response to a request from the user terminal device 40. Figure 21 shows an example of an input screen for setting business rules. In this example, the controls for tax category, amount excluding tax, consumption tax amount, and amount including tax are laid out. Figure 22 shows the layout definition corresponding to the input screen of Figure 21.

When setting a business rule, a conditional expression for the business rule is set for each control. When setting this conditional expression for the business rule, the developer first selects the desired condition for setting the conditional expression for the business rule from among the conditions (conditions) for example, "Amount excluding tax_control," "Consumption tax_control," and "Amount including tax_control" on the condition setting screen shown in Figure 23 by entering or adding the condition name as necessary. The example in Figure 23 shows the "Amount including tax_control" condition selected.

Next, the developer selects a conjunction (AND or OR) for the multiple conditional expressions. In the example in Figure 23, the conjunction "OR" is selected. As shown in Figure 23, a conditional expression consists of an left-hand side value, an operator, and a right-hand side value. As shown in Figure 27, the left-hand side value and right-hand side value can be specified by selecting the desired value from among "control," "variable," "row variable (variable that can be held for each row)," constants (character, numeric, boolean), or system variables (provided initially). Furthermore, as shown in Figure 28, inequality signs such as "equal to," "not equal to," "greater than," and "less than," as well as "is NULL," "is not NULL," can be specified as an operator.

In the example in Figure 23, the conditional expression in the top row is "Tax Category = (0)", and the conditional expression in the bottom row is "Tax Category = (1)". In the example in Figure 23, the conjunction "OR" has been selected, which indicates that a business rule has been set that allows the "Amount including tax" to be changed when "Tax Category = (0)" or "Tax Category = (1)" is true.

In addition, Figure 26(a) shows a conditional expression that tests whether there is an error in the control. Figure 26(b) shows a conditional expression that tests whether the value of a variable defined on the screen is greater than the value of the control (the variable is defined on the screen in advance, just like the control).

Such conditions and conditional expressions are stored in the memory unit 2 as condition setting information, in which a condition ID, name, and expression (conditional expression) are associated with each other, as shown in Figure 24. The "Second Expression" shown in Figure 24 is a conditional expression in which "Tax Category Select Box (Value) = Fixed Value (2)" using "AND" as a conjunction, as shown in Figure 25(a). The "Third Expression" shown in Figure 24 is a conditional expression in which "Tax Category Select Box (Value) = Fixed Value (0)" using "AND" as a conjunction, as shown in Figure 25(b). The "Fourth Expression" shown in Figure 24 is a conditional expression in which "Tax Category Select Box (Value) = Fixed Value (0)" or "Tax Category Select Box (Value) = Fixed Value (1)" using "OR" as a conjunction, as shown in Figure 25(c).

Next, as shown in Figure 29, the developer selects the action to be taken when the condition is met for each control, and the control to which the action will be applied. The desired action to be taken when the condition is met can be selected from among "Lock item," "Make item required," and "Hide item." The example in Figure 23 shows the "Lock item" action selected.

In addition, the example in Figure 23 shows that the "Amount excluding tax text box," "Consumption tax amount text box," and "Amount including tax text box" are selected as the controls to which the process will be applied.

By performing this selection operation, business rule setting information including the business rule ID, processing content, control ID, and condition ID is generated and stored in the memory unit 2, as shown in Figure 30.

(Web application operation)
Next, the operation of the server device 1 returning a response in response to a request received from the user terminal device 40 will be described using the flowcharts of Figures 31 and 32. Figure 31 is a flowchart showing the flow of the first half of the operation of such a web application, and Figure 32 is a flowchart showing the flow of the second half of the operation of the web application. The operation of the flowcharts of Figures 31 and 32 is executed by the control unit 3 functioning as the display control unit 21, discrimination unit 22, information processing unit 23, and communication control unit 24 shown in Figure 1 based on the information processing program stored in the storage unit 2.

First, in step S1 of the flowchart in Figure 31, the communication control unit 24 of the server device 1 receives a request sent from the user terminal device 40, and the process proceeds to step S2. In step S2, the determination unit 22 determines whether the request received from the user terminal device 40 is for the start-up of the Web application system. If the request is for the start-up of the Web application system (step S2: Yes), the information processing unit 23 performs the above-mentioned
Layout definition of the input screen shown in FIG. 33(a),
The event allocation definition shown in FIG. 33(b)
The logic flow definition shown in FIG. 33(c)
The action definition shown in FIG. 33(d)
The flow definition shown in FIG.
The condition list shown in FIG. 33(f)
A list of business rules shown in FIG. 33(g)
The API called by the API call shown in FIG. 33(h),
is read from the storage unit 2 and temporarily stored in a storage device such as a RAM (Random Access Memory).

In addition, based on the various information read out in this way, the information processing unit 23 sets the values of each control for ID3 (tax category), ID5 (amount excluding tax), ID7 (amount including consumption tax), and ID9 (amount including tax) to fixed values such as "2: tax included," "30,000 yen," "3,000 yen," and "33,000 yen," and generates session management data in which all lock states are set to "OFF," as shown in FIG. 34.

Next, in this case, since it is startup time of the web application system, the discrimination unit 22 does not perform a fraud check, and processing proceeds to step S4 via step S8. Also, since it is startup time in this case, the discrimination unit 22 determines in step S4 that there is no event to execute (step S4: No), and processing proceeds to step S5 of the flowchart in Figure 32 via step S11.

In step S5, the discrimination unit 22 determines whether the application is currently starting up or whether a request has been made via button operation. In this case, since the application is currently starting up (step S5: Yes), the discrimination unit 22 evaluates the business rules in step S12 and supplies the evaluation results to the information processing unit 23. If the tax category is "2: tax included," the information processing unit 23 changes the tax-excluded amount for "ID5" in the session management data from "OFF" to "ON (locked state)," as shown in Figures 35(a), 35(b), and 36. The display control unit 21 generates the input screen shown in Figure 37 based on this session management data.

In step S7, the communication control unit 24 transmits an input screen equivalent to the initial screen generated by the display control unit 21 to the user terminal device 40. The user terminal device 40 acquires the input screen received from the server device 1 via the web browser 41 and displays it on the display unit.

Next, suppose that the user makes a request via the user terminal device 40 to change the tax category for ID3, which was previously set to "2: tax included" as shown in Figure 38(a), to "1: tax excluded." This request is acquired by the information processing unit 23 in step S1 of the flowchart shown in Figure 31. In this case, since it is not startup, processing proceeds to step S3 via step S2, where the determination unit 22 references the session management data and determines whether the requested information is in a "locked state."

In this case, since the "Tax Category" is not locked (OFF), the discrimination unit 22 performs a discrimination operation to accept this request (step S3: No). Based on the discrimination result that the request is accepted, the information processing unit 23 changes the value of the tax category of ID3 from "2: Tax Included" to "1: Tax Excluded" in step S9, as shown in FIG. 38(b). This causes processing to proceed to step S4. At this point, since there are no events to be executed, processing proceeds to step S5 of the flowchart in FIG. 32 via steps S4 and S11.

In this case, since the request is made by button operation (step S5: Yes), processing proceeds from step S5 to step S12, where the discrimination unit 22 evaluates the business rules as shown in Figures 39(a) and 39(b) and supplies the evaluation results to the information processing unit 23. In this case, since the tax category has been changed to "1: tax excluded," the information processing unit 23 updates the session management data to set the lock status of ID5 "Amount excluding tax" to "OFF (unlocked)" and ID9 "Amount including tax" to "ON (locked)," as shown in Figure 40.

In step S7, the display control unit 21 and the communication control unit 24 send partial display data for the updated "Amount excluding tax" for ID5 and the amount including tax for ID9 to the user terminal device 40. Based on the display data received from the server device 1, the user terminal device 40 updates the lock status of the "Amount excluding tax" for ID5 and the amount including tax for ID9 on the input screen.

Next, let's assume that the user makes a request via the user terminal device 40 to fraudulently change the tax-inclusive amount, which was "33,000 yen," to "100 yen," as shown in Figure 41. This request is acquired by the information processing unit 23 in step S1 of the flowchart shown in Figure 31. In this case, since it is not startup, processing proceeds to step S3 via step S2, where the determination unit 22 references the session management data and determines whether the requested information is in a "locked state."

In this case, as shown in Figure 40, the "tax-inclusive amount" of "33,000 yen" for ID9 is locked (step S3: Yes), so the discrimination unit 22 determines not to accept this request (discards the request).

Next, in step S4, the determination unit 22 references the event allocation definition shown in Figure 43(a), the logic flow definition shown in Figure 43(b), the action definition shown in Figure 43(c), and the flow definition shown in Figure 43(d) to determine the process corresponding to the click operation of the registration button with ID 10. In this case, the process corresponding to the click operation of the registration button with ID 10 is determined to be the "data registration process" as shown in Figure 43(b). In step S10, the information processing unit 23 executes the logic flow of the "data registration process" based on the result of this determination.

Next, processing proceeds to step S5 of the flowchart in Figure 32, where the discrimination unit 22 evaluates the business rules as shown in Figures 44(a) and 44(b) and supplies the evaluation result to the information processing unit 23. In this case, since the fraudulent request to change the tax-inclusive price to "100 yen" was discarded, the information processing unit 23 does not update the session management data as shown in Figure 45. The display control unit 21 generates the previous input screen shown in Figure 46 based on the session management data as shown in Figure 45. The communication control unit 24 transmits this input screen to the user terminal device 40. This discards the fraudulent request and maintains the input screen based on the previous session management data, thereby preventing fraudulent data tampering.

Note that if it is determined in step S5 of the flowchart in FIG. 32 that the request is not a request made at startup or by button operation (step S5: No), processing proceeds to step S6, where the discrimination unit 22 determines whether the request is to change the value of a control included in the condition formula. If it is determined that the request is to change the value of a control included in the condition formula (step S6: Yes), the discrimination unit 22 evaluates the business rules in step S12. On the other hand, if it is determined that the request is not to change the value of a control included in the condition formula (step S6: No), no processing is performed in step S13, and processing proceeds to step S7.

(Effects of the first embodiment)
As is clear from the above explanation, in the Web application system of the first embodiment, the server device 1 manages all the states of the control, such as the data to be displayed and whether the control is locked or hidden. Therefore, it is possible to evaluate whether a request can be accepted at the timing of processing the request from the user terminal device 40. Then, by processing the request based on this evaluation result, it is possible to easily prevent data tampering.

Second Embodiment
Next, a user terminal device 40 according to a second embodiment will be described. The Web application system according to the first embodiment described above is an example in which the server device 1 manages data provided to the user terminal device 40 based on an information processing program developed by the developer terminal device 30, thereby preventing unauthorized data tampering. In contrast, the user terminal device 40 according to the second embodiment is a so-called standalone terminal device, and is an example in which the user terminal device 40 alone prevents the aforementioned unauthorized data tampering.

Note that this is the only difference between the first and second embodiments. Therefore, below we will only explain the differences between the two and omit redundant explanations.

Figure 47 is a block diagram showing the hardware configuration of a user terminal device 40 according to a second embodiment. In this second embodiment, the user terminal device 40 is a standalone terminal device, and includes a memory unit 42, a control unit 43, a communication interface unit 44, and an input/output interface unit 45. An input device 46 and an output device 47 are connected to the input/output interface unit 45. The output device 47 can be a display unit such as a monitor device (including a home television). The input device 46 can be a keyboard device, a mouse device, a microphone device, or a monitor device that cooperates with a mouse device to provide a pointing device function.

The communication interface unit 44 is connected to a wide area network such as the Internet or a private network such as a local area network (LAN).

The storage unit 42 may be, for example, a storage device such as a ROM (Read Only Memory), RAM (Random Access Memory), HDD (Hard Disk Drive), or SSD (Solid State Drive). The storage unit 42 stores information processing programs similar to those described above, as well as a database (DB) 11 that stores data requested via the input device 46.

The memory unit also stores the above-mentioned layout definitions, event allocation definitions, logic flow definitions, action definitions, flow definitions, individual settings, condition settings, business rule settings, etc.

The control unit 43 includes the display control unit 21, discrimination unit 22, and information processing unit 23 described above, which are realized by executing the information processing program stored in the memory unit 42.

In the user terminal device 40 of this second embodiment, the display control unit 21 displays the input screen via the output device 47, which is an example of a display unit. The user performs desired input operations via the input device 46, entering desired values or operating buttons on the input screen.

The determination unit 22 evaluates the request generated by the user entering a desired value or operating a button based on the business rules as described above. If the information processing unit 23 obtains a determination result indicating that the value entered via the input screen can be changed, it supplies the information processing result corresponding to the entered value to the display control unit 21. The display control unit 21 displays the information processing result corresponding to the entered value on the output device 47.

On the other hand, if a determination result is obtained indicating that the value of the item entered via the input screen cannot be changed, the information processing device 23 discards the value of the entered item and maintains the previous value, and supplies the information processing result corresponding to the previous value to the display control unit. The display control unit 21 displays the information processing result corresponding to the previous value on the output device 47.

(Effects of the second embodiment)
This makes it possible to easily prevent data tampering in the same way as in the first embodiment, and also to obtain the same effects as in the first embodiment.

[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 the achievement of SDGs Goals 8 and 9.

Furthermore, this embodiment can contribute to reducing waste and promoting paperless and electronic systems, thereby contributing to SDGs Goals 12, 13, and 15.

Furthermore, this embodiment can contribute to strengthening control and governance, thereby contributing to Goal 16 of the SDGs.

Other Embodiments
The present invention may be implemented in various different embodiments other than those described above within the scope of the technical concept set forth in the claims.

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.

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

Furthermore, with regard to the server device 1 and user terminal device 40 of the web application system, the components shown are functional concepts and do not necessarily have to be physically configured as shown.

For example, the processing functions of the server device 1, particularly the control unit 3 and the various processing functions performed by the control unit 3, and the processing functions of the user terminal device 40, particularly the control unit 43 and the various processing functions performed by the control unit 43, may be implemented in whole or in part by a CPU (Central Processing Unit) and a program interpreted and executed by the CPU, or may be implemented as hardware using wired logic. The program is recorded on a non-transitory computer-readable recording medium containing programmed instructions for causing the information processing device to execute the processes described in this embodiment, and is mechanically read by the server device 1 or the user terminal device 40 as needed. That is, a computer program is recorded in a storage unit such as a ROM or HDD for working with the OS to issue commands to the CPU and perform various processes. The computer program is executed by being loaded into RAM, and works with the CPU to form the control unit 3.

In addition, the information processing program of the server device 1 or the user terminal device 40 may be stored in another server device connected to the server device 1 or the user terminal device 40 via any network, and all or part of it may be downloaded as needed.

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

A "program" is a data processing method written in any language or description method, and may be in any format, such as source code or binary code. A "program" is not necessarily limited to a single structure, but also includes a distributed structure consisting of multiple modules or libraries, or a structure that achieves its function by working in conjunction with a separate program, such as an OS. In the server device 1 or user terminal device 40 shown in the embodiments, well-known structures and procedures can be used for the specific structure and reading procedure for reading a recording medium, as well as the installation procedure after reading.

Memory unit 2 and memory unit 42 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 used for various processes and website provision.

Furthermore, the server device 1 or the user terminal device 40 may be configured as an information processing device such as a known personal computer device or workstation, or may be configured as an information processing device to which any peripheral device is connected. Furthermore, the information processing device may be realized by implementing software (including programs, data, etc.) that realizes the processing described in this embodiment.

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

This invention is suitable for application in industries such as application program development.

REFERENCE SIGNS LIST 1 Server device 2 Storage unit 3 Control unit 4 Communication interface unit 11 Database 13 Web browser 21 Display control unit 22 Discrimination unit 23 Information processing unit 24 Communication control unit 30 Developer terminal device 31 Web browser 40 User terminal device 41 Web browser 42 Storage unit 43 Control unit 44 Communication interface unit 45 Input/output interface unit 46 Input device 47 Output device 55 Network

Claims (8)

a display control unit that displays an input screen on a display unit;
a determination unit that, when an input is made to an item included in the input screen, references setting information stored in a storage unit that indicates whether or not the value of each item on the input screen can be changed, and determines whether or not the value of the item input via the input screen is a changeable item;
an information processing unit that, when a determination result indicating that the value of the item input via the input screen is changeable is obtained, supplies an information processing result corresponding to the value of the input item to the display control unit, and, when a determination result indicating that the value of the item input via the input screen is not changeable is obtained, discards the value of the input item, maintains the previous value, and supplies an information processing result corresponding to the previous value to the display control unit;
An information processing device having the above. the display control unit, when obtaining a determination result from the determination unit indicating that the value of the item input via the input screen cannot be changed, displays a predetermined error on the display unit;
2. The information processing device according to claim 1, The setting information can be set to prohibit changes to items or buttons in a main panel corresponding to the entire input screen, or can be set to prohibit changes to items or buttons included in a partial panel corresponding to a part of the input screen,
the determination unit determines that all items or all buttons in the main panel are unchangeable when the setting is such that items or buttons in the main panel are unchangeable, and determines that all items or all buttons in the partial panel are unchangeable when the setting is such that items or buttons in the partial panel are unchangeable;
3. The information processing device according to claim 2, wherein: the setting information has a hierarchical structure in which the items or buttons are in a lower hierarchical level, the partial panel is in a middle hierarchical level, and the main panel is in a higher hierarchical level,
the determination unit determines whether or not there is a setting that prohibits changes in the order of the lower hierarchy, the middle hierarchy, and the upper hierarchy, and if a setting that prohibits changes is detected in the upper hierarchy, determines that all items and buttons included in the main panel cannot be changed; if a setting that prohibits changes is detected in the middle hierarchy, determines that all items and buttons included in the partial panel cannot be changed; and if a setting that prohibits changes is detected in the lower hierarchy, determines that the items for which a setting that prohibits changes is set cannot be changed;
4. The information processing device according to claim 3, As a process to be performed when a condition of a predetermined conditional expression is satisfied, one of a process of locking the item, which is a process of making the value of the item unchangeable, and a process of hiding the item can be set for each item as the setting information;
5. The information processing device according to claim 4, a communication control unit that controls communication of a communication unit so that the input screen generated by the display control unit and the information processing result supplied to the display control unit are transmitted to a client terminal device via a network, and a value input to the input screen via the client terminal device is received via the network ;
6. The information processing device according to claim 5, a display control step in which a display control unit displays an input screen on a display unit;
a determination step in which, when an input is made to an item included in the input screen, a determination unit refers to setting information stored in a storage unit that indicates whether or not the value of each item on the input screen can be changed, and determines whether or not the value of the item input via the input screen is a changeable item;
an information processing step in which, when a determination result is obtained by the information processing unit indicating that the value of the item input via the input screen is changeable, the information processing unit supplies the display control unit with an information processing result corresponding to the value of the input item, and, when a determination result is obtained by the information processing unit indicating that the value of the item input via the input screen is not changeable, the information processing unit discards the value of the input item, maintains the previous value, and supplies the display control unit with an information processing result corresponding to the previous value;
An information processing method comprising: Computer,
a display control unit that displays an input screen on a display unit;
a determination unit that, when an input is made to an item included in the input screen, references setting information stored in a storage unit that indicates whether or not the value of each item on the input screen can be changed, and determines whether or not the value of the item input via the input screen is a changeable item;
when a determination result indicating that the value of the item input via the input screen is changeable is obtained, an information processing unit supplies an information processing result corresponding to the value of the input item to the display control unit, and when a determination result indicating that the value of the item input via the input screen is not changeable is obtained, an information processing unit discards the value of the input item, maintains the previous value, and supplies an information processing result corresponding to the previous value to the display control unit;
An information processing program characterized by: