Application provision system, application provision method and application provision program

Abstract

To provide a business application to a user, the business application capable of reducing man hours required for setting and occurrence of failure due to a setting error.SOLUTION: An application provision system is configured so that: when control information of a definition management table includes common control of a search type, to the control information, control including at least two of a value specification area of the common control and a dialog display button is added; pull down display command argument information and common control definition of the common control are combined and they are converted into pull down information of the value specification area; in the common control definition with a setting of using the dialog display button, the dialog display command argument information is converted into logic flow information and action information, the created logic flow information is associated with an event of the dialog display button, the common control is deleted from the control information, and according to UI definition of the converted business application, start-up processing of the business application is executed.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention relates to an application providing system, an application providing method, and an application providing program. [Background technology]

[0002] Conventionally, a system for developing applications at low cost is disclosed in, for example, Patent Document 1. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2023-34112 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 forming patterns of frequently used application functions and saving reusable settings for each pattern as an independent common control definition.

[0005] The present invention has been made in consideration of the above, and aims to provide an application providing system, application providing method, and application providing program that can provide users with business applications that can reduce the amount of work required for configuration and prevent problems caused by configuration errors, by providing a mechanism for patterning frequently used application functions and saving reusable settings for each pattern as independent common control definitions. [Means for solving the problem]

[0006] In order to solve the above-mentioned problems and achieve the object, the present invention provides an application providing system comprising a control unit and configured to be capable of data communication with developers and users' clients, the control unit being configured to be able to access a database storing: control information defining a definition ID, a definition name, an ID for each control, an identification name, and a control type; logic flow information defining an ID for each element of a logic flow, a previous action ID, and a next action ID; a definition management table that associates and registers action information defining an ID, name, type, API, argument, and return value for each action element; and a common control definition management table that defines a common control definition common to a plurality of business applications and associates and registers a definition ID, a definition name, a common control type, and setting contents; and the control unit being configured to be able to access a database storing: When an instruction to launch a business application is received from a user, application information of the business application is read from the definition management table, and if the control information of the definition management table includes a search-type common control, a control including at least two of a value specification area of ​​the common control and a dialog display button is added to the control information, pull-down display command argument information of the common control is combined with the common control definition to convert it into pull-down information for the value specification area, and if the common control definition is for a setting that uses a dialog display button, the dialog display command argument information is converted into logic flow information and action information, the created logic flow information is linked to an event of the dialog display button, the common control is deleted from the control information, and the business application launch process is performed in accordance with the UI definition of the converted business application.

[0007] In addition, according to one aspect of the present invention, when the search type is a code search type, the execution means may further convert a property reference portion of a common control of the code search type into a normal control, convert verification API argument information and verification API return value information of the common control into logic flow information and action information, and link the created logic flow information to a text box event.

[0008] According to another aspect of the present invention, the control unit may include a setting unit that creates the common control definition management table in response to an operation by a developer on a setting screen.

[0009] According to another aspect of the present invention, the setting means may add common controls in the common control definition management table to the control information in the definition management table in response to operations by a developer on a setting screen.

[0010] According to another aspect of the present invention, the application providing system 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 an application providing method executed by an information processing device that includes a control unit and is configured to be capable of data communication with a developer and a user client, the control unit being configured to be able to access a database that stores control information that specifies a definition ID, a definition name, an ID for each control, an identification name, and a control type, logic flow information that specifies an ID for each element of a logic flow, a previous action ID, and a next action ID, and action information that specifies an ID, name, type, API, argument, and return value for each action element, in association with each other, a definition management table that specifies a common control definition common to a plurality of business applications, and that associates and registers a definition ID, a definition name, a common control type, and setting contents, and an execution program executed by the control unit that launches a business application when a launch instruction is received from a user. The execution step includes steps, in which, upon receiving an instruction to launch a business application from a user, application information of the business application is read from the definition management table, and if the control information of the definition management table includes a search-type common control, a control including at least two of a value specification area of ​​the common control and a dialog display button is added to the control information, pull-down display command argument information of the common control is combined with the common control definition to convert it into pull-down information for the value specification area, and in the case of a common control definition for a setting that uses a dialog display button, the dialog display command argument information is converted into logic flow information and action information, the created logic flow information is linked to an event of the dialog display button, the common control is deleted from the control information, and the business application launch process is performed in accordance with the UI definition of the converted business application.

[0012] In addition, in order to solve the above-mentioned problems and achieve the object, the present invention provides an application providing program to be executed by an information processing device having a control unit and configured to be capable of data communication with a user and developer client, the control unit comprising: a definition management table that associates and registers control information defining a definition ID, a definition name, an ID for each control, an identification name, and a control type; logic flow information defining an ID for each element of a logic flow, a previous action ID, and a next action ID; and action information defining an ID, name, type, API, argument, and return value for each action element; a common control definition management table that associates and registers a definition ID, definition name, common control type, and setting contents, which defines a common control definition common to multiple business applications; and the control unit is configured to be able to access a database storing therein information about a business application, and the control unit is configured to execute an execution step of starting a business application when a start instruction from a user is received, and in the execution step, when a start instruction from a user is received, application information of the business application is read from the definition management table, and if a search-type common control is included in the control information of the definition management table, a control including at least two of a value specification area and a dialog display button of the common control is added to the control information, pull-down display command argument information of the common control is combined with a common control definition to convert it into pull-down information of a value specification area, and in the case of a common control definition of a setting using a dialog display button, the dialog display command argument information is converted into logic flow information and action information, the created logic flow information is linked to an event of the dialog display button, the common control is deleted from the control information, and a start process of the business application is performed in accordance with the UI definition of the converted business application. Effect of the Invention

[0013] According to the present invention, by providing a mechanism for patterning frequently used application functions and saving reusable settings for each pattern as an independent common control definition, it is possible to provide users with business applications that reduce the amount of work required for configuration and prevent problems caused by configuration errors. [Brief description of the drawings]

[0014] [Figure 1] FIG. 1 is a block diagram showing an example of a configuration of an application providing system according to the present embodiment. [Diagram 2] FIG. 2 is a diagram for explaining a specific example of the processing of the application providing system according to the present embodiment. [Diagram 3] FIG. 3 is a diagram for explaining a specific example of the processing of the application providing system according to the present embodiment. [Figure 4] FIG. 4 is a diagram for explaining a specific example of the processing of the application providing system according to the present embodiment. [Diagram 5] FIG. 5 is a diagram for explaining a specific example of the processing of the application providing system according to the present embodiment. [Figure 6] FIG. 6 is a diagram for explaining a specific example of the processing of the application providing system according to the present embodiment. [Figure 7] FIG. 7 is a diagram for explaining a specific example of the processing of the application providing system according to the present embodiment. [Figure 8] FIG. 8 is a diagram for explaining a specific example of the process of the application providing system according to the present embodiment. [Figure 9] FIG. 9 is a diagram for explaining a specific example of the process of the application providing system according to the present embodiment. [Figure 10] FIG. 10 is a diagram for explaining a specific example of the processing of the application providing system according to the present embodiment. [Figure 11]FIG. 11 is a diagram for explaining a specific example of the processing of the application providing system according to the present embodiment. [Figure 12] FIG. 12 is a diagram for explaining a specific example of the processing of the application providing system according to the present embodiment. [Figure 13] FIG. 13 is a diagram for explaining a specific example of the processing of the application providing system according to the present embodiment. [Figure 14] FIG. 14 is a diagram for explaining a specific example of the processing of the application providing system according to the present embodiment. [Figure 15] FIG. 15 is a diagram for explaining a specific example of the processing of the application providing system according to the present embodiment. [Figure 16] FIG. 16 is a diagram for explaining a specific example of the process of the application providing system according to the present embodiment. [Figure 17] FIG. 17 is a diagram for explaining a specific example of the process of the application providing system according to the present embodiment. [Figure 18] FIG. 18 is a diagram for explaining a specific example of the process of the application providing system according to the present embodiment. [Figure 19] FIG. 19 is a diagram for explaining a specific example of the process of the application providing system according to the present embodiment. [Figure 20] FIG. 20 is a diagram for explaining a specific example of the processing of the application providing system according to the present embodiment. [Figure 21] FIG. 21 is a diagram for explaining a specific example of the processing of the application providing system according to the present embodiment. [Figure 22] FIG. 22 is a diagram for explaining a specific example of the processing of the application providing system according to the present embodiment. [Figure 23] FIG. 23 is a diagram for explaining a specific example of the process of the application providing system according to the present embodiment. [Figure 24]FIG. 24 is a diagram for explaining a specific example of the process of the application providing system according to the present embodiment. [Diagram 25] FIG. 25 is a diagram for explaining a specific example of the processing of the application providing system according to the present embodiment. [Figure 26] FIG. 26 is a diagram for explaining a specific example of the process of the application providing system according to the present embodiment. [Figure 27] FIG. 27 is a diagram for explaining a specific example of the process of the application providing system according to the present embodiment. [Figure 28] FIG. 28 is a diagram for explaining a specific example of the processing of the application providing system according to the present embodiment. [Figure 29] FIG. 29 is a diagram for explaining a specific example of the process of the application providing system according to the present embodiment. [Diagram 30] FIG. 30 is a diagram for explaining a specific example of the process of the application providing system according to the present embodiment. [Diagram 31] FIG. 31 is a diagram for explaining a specific example of the process of the application providing system according to the present embodiment. [Diagram 32] FIG. 32 is a diagram for explaining a specific example of the process of the application providing system according to the present embodiment. [Diagram 33] FIG. 33 is a diagram for explaining a specific example of the process of the application providing system according to the present embodiment. [Diagram 34] FIG. 34 is a diagram for explaining a specific example of the process of the application providing system according to the present embodiment. [Diagram 35] FIG. 35 is a diagram for explaining a specific example of the process of the application providing system according to the present embodiment. [Diagram 36] FIG. 36 is a diagram for explaining a specific example of the process of the application providing system according to the present embodiment. [Figure 37]FIG. 37 is a diagram for explaining a specific example of the process of the application providing system according to the present embodiment. [Figure 38] FIG. 38 is a diagram for explaining a specific example of the process of the application providing system according to the present embodiment. [Figure 39] FIG. 39 is a diagram for explaining a specific example of the process of the application providing system according to the present embodiment. [Diagram 40] FIG. 40 is a diagram for explaining a specific example of the processing of the application providing system according to the present embodiment. [Diagram 41] FIG. 41 is a diagram for explaining a specific example of the processing of the application providing system according to the present embodiment. [Diagram 42] FIG. 42 is a diagram for explaining a specific example of the process of the application providing system according to the present embodiment. [Diagram 43] FIG. 43 is a diagram for explaining a specific example of the process of the application providing system according to the present embodiment. [Diagram 44] FIG. 44 is a diagram for explaining a specific example of the process of the application providing system according to the present embodiment. [Diagram 45] FIG. 45 is a diagram for explaining a specific example of the process of the application providing system according to the present embodiment. [Diagram 46] FIG. 46 is a diagram for explaining a specific example of the processing of the application providing system according to the present embodiment. [Figure 47A] FIG. 47A is a diagram for explaining a specific example of the process of the application providing system according to the present embodiment. [Figure 47B] FIG. 47B is a diagram for explaining a specific example of the process of the application providing system according to the present embodiment. [Figure 48] FIG. 48 is a diagram for explaining the scope of application of the present invention. [Figure 49] FIG. 49 is a diagram for explaining the scope of application of the present invention. [Figure 50]FIG. 50 is a diagram for explaining the scope of application of the present invention. [Figure 51] FIG. 51 is a diagram for explaining the scope of application of the present invention. [Figure 52] FIG. 52 is a diagram for explaining the scope of application of the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0015] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, an embodiment of an application providing system, an application providing method, and an application providing 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 embodiment.

[0016] [1. Overview] The present invention will be outlined in the following order: (1. Background and Problems) and (2. Solution).

[0017] (1.Background / Issues) Previously, there was no mechanism for standardizing application settings, so system developers had to set up each application from scratch. This setting method required checking each time whether the application settings were set correctly, so as the system became larger, the cost of setting and checking increased. It was also difficult to ensure the operability of the system for each setting point, and there was a risk of usability being impaired.

[0018] For example, in low-code development, developers develop a system by placing controls (UI) with drag-and-drop and assigning the required processing (such as API execution) to events related to those controls (for buttons, a click event is common). When an application user clicks a button on the browser (client), the button click event is triggered, and the API is called, thereby interacting with data on the server side. Then, depending on the results of the API processing, the required information is returned from the server side, and the information can be received again on the client side.

[0019] At this time, the information returned from the server is reflected in the controls on the screen, allowing the application user to recognize the server information. Application developers must decide how to display the information returned from the server as a result of click events, etc., on the browser before developing the system. Since such update settings must be set for each event in the system, the larger the system becomes, the more cumbersome it becomes, leading to the issue of reduced maintainability.

[0020] For example, in ERP systems, the same screen components are often used across multiple screens, necessitating multiple settings management during development, which creates the problem of forcing application developers to do redundant development work.

[0021] (2. Solution) In general business applications, there are frequently used functions such as inputting a master code value and retrieving the corresponding master name from the database. System developers need to make appropriate settings for each location where they want to use such functions.

[0022] In this invention, we have devised a mechanism to pattern frequently used application functions and save reusable settings for each pattern as an independent common control definition called common control.By using the common control definition, system developers can reduce the amount of work required for settings that were previously required and prevent problems caused by incorrect settings.

[0023] For example, in low-code development, common functions such as retrieving master information are used in multiple places, and UI information can often be patterned as well. By patterning the UI and logic and reusing the settings as needed, it becomes unnecessary to configure each screen, reducing the cost for the person configuring.

[0024] This invention provides a mechanism for defining search controls (common controls) used in multiple applications and making it possible to reuse the common search control definition. In addition, as controls that application developers can freely set, there are general programming concepts such as user controls and custom controls, but with this function, application developers must set the UI settings and the event handler settings associated with them from the beginning, and although there is a high degree of freedom in the settings, there is an issue that the settings require programming knowledge, making it a high hurdle in system development.

[0025] Taking these points into consideration, the present invention provides a mechanism for reducing the burden on application developers by generalizing the setting of common control definitions to include the setting of UI and event handlers.

[0026] [2. Configuration] An example of the configuration of an application providing system 100 (Web server) according to this embodiment will be described with reference to Fig. 1. The application providing system 100 can be configured, for example, on a low-code platform (low-code development platform / low-code execution platform). It may also be configured on a no-code platform. Fig. 1 is a block diagram showing an example of the configuration of the application providing system 100 according to this embodiment.

[0027] The application providing system 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 application providing system 100 are communicatively connected via any communication path.

[0028] The communication interface unit 104 communicatively connects the application providing system 100 to the network 300 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 the communication line. Here, the network 300 has a function of communicatively connecting the application providing system 100 to Web clients (clients used by developers and clients used by business operators (users)) 400... and business systems (not shown), and is, for example, the Internet or a LAN (Local Area Network). Note that the data stored in the storage unit 106 described later may be stored in a data server (not shown) or the like.

[0029] 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, 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.

[0030] 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.

[0031] The storage unit 106 includes a development application DB 106a that stores various setting information at the development stage, a business application DB 106b in which application information in the development application DB 106a is made public, and the like.

[0032] The development application DB 106a stores a definition management table, a pull-down definition management table, a common control definition management table, an API management table, and the like.

[0033] The definition management table is a table that associates and registers the following: definition ID, definition name, control information that specifies the ID, identification name, and control type for each control, logic flow information that specifies the ID, previous action ID, and next action ID for each logic flow element, action information that specifies the ID, name, type, API, argument, and return value for each action element, and linking information that specifies the control ID, event type, and logic flow ID for each linked element. Common controls from the common control definition management table are added to the definition management table.

[0034] The pull-down definition management table is a table in which an ID, a pull-down name, an API ID for linking with the API management table, a return value, a display item, etc. are registered in association with each other.

[0035] The common control definition management table is used to define common control definitions that are common to a plurality of business applications, and is a table in which definition IDs, definition names, common control types, and setting contents are registered in association with each other.

[0036] The API management table is a table in which IDs, method names, API names, arguments (ID, name, type), return values ​​(ID, name, type), etc. are registered in association with each other.

[0037] The control unit 102 is a CPU or the like that performs overall control of the application providing system 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.

[0038] The control unit 102 conceptually includes a setting unit 102a and an execution unit 102b.

[0039] The setting unit 102a functions as a low-code development platform, creates setting information (definitions) related to the provision of business applications, and registers the information in the development application DB 106a.

[0040] For example, the setting unit 102a provides a common control setting screen in response to a request from a Web client 400 (developer), and creates a common control definition management table in response to operations performed by the developer on the common control setting screen, and registers the table in the development application DB 106a.

[0041] In addition, the setting unit 102a provides a business application creation screen in response to a request from a Web client 400 (developer), and adds (sets) common controls in the common definition management table to the control information in the definition management table in response to operations by the developer on the business application creation screen.

[0042] The execution unit 102b functions as a low-code execution platform, and provides business applications in response to requests from Web clients 400 (users=business operators).

[0043] When the execution unit 102b receives a launch instruction from the Web client 400 (user), it launches a business application. Specifically, it reads application information of the business application from the definition management table, and if the control information in the definition management table includes a search-type common control, it adds a control including at least two of the common control's value specification area and dialog display button to the control information, combines the common control's pull-down display command argument information with the common control definition to convert it into pull-down information for the value specification area, and if the common control definition is set to use the dialog display button, it converts the dialog display command argument information into logic flow information and action information, links the created logic flow information to the dialog display button event, deletes the common control from the control information, and performs the business application launch process in accordance with the UI definition of the converted business application.

[0044] In addition, if the search type is a code search type, the execution unit 102b further converts the property reference points of the common control of the code search type into normal controls, converts the verification API argument information and verification API return value information of the common control into logic flow information and action information, and links the created logic flow information to the text box event.

[0045] [3. Specific examples of processing] A specific example of the processing of the application providing system 100 (Web server) of this embodiment will be described with reference to Fig. 2 to Fig. 47. Fig. 2 to Fig. 47 are diagrams for explaining a specific example of the processing of the application providing system 100 of this embodiment.

[0046] [3-1. About low-code development tools] The following explanation assumes two types of users: developers and business operators of client companies. The explanation is divided into two stages: the development stage, where developers use low-code development tools to create UI settings and business logic for business applications, and the usage stage, where business operators actually use the applications.

[0047] Figure 2 shows an overall view of a low-code development tool. The development stage is when a developer uses a low-code development platform to register configuration information for a business application in a database. The usage stage is when the low-code execution platform analyzes the configuration information registered in the development stage and converts it into an actual business application, allowing a business operator to execute the business. In this specification, the low-code development platform and the low-code execution platform are collectively referred to as the "low-code development tool."

[0048] Here, we will explain how to manage data generated at each stage. From the viewpoint of control, it is necessary to clearly separate the database in which developers manage application settings during development from the database in which business operators manage application settings referenced during business use. This is to prevent developers from directly operating the business database. In the following explanation, the database for managing application settings used by developers is referred to as the "development application DB", and the database for managing application settings used by business operators is referred to as the "business application DB".

[0049] (1) Development Stage As shown in the upper half of Figure 2, the development stage is where developers use low-code development tools (the low-code development platform side) to develop business applications. Low-code development mainly involves setting up the layout of the application screen and the development of a series of event processes (actions, logic flows) that are performed when the layout is operated. Ultimately, the UI part of the business application can be generated by linking the layout and logic flow. The main settings at the development stage are as follows (A) to (C).

[0050] (A) Layout Development Configure the screen layout of the business application.

[0051] (B) Logic flow development and action development This sets up the processing part of the business application. With low-code development tools, the processing in the business application can be set in units called actions (the aforementioned linking of the UI part with the business logic is also done through these actions). Furthermore, by connecting actions with flows, the order in which a series of actions are processed can be set. This setting of the processing order of actions is called a "logic flow."

[0052] This section explains the special action settings for calling business logic. In low-code development, the developer creates only the business logic part through individual programming work, and the UI part is generated by operating the low-code development tool. For this reason, in order to call business logic from the UI side, the developer needs to convert the created business logic into an API and register it in the API master. The business logic can be executed by calling the API registered in the API master from the API call action.

[0053] (C) Combining layout and logic flow Set up the logic flow (B) to be assigned to the layout set up in (A).

[0054] (2) Utilization stage As shown in the lower half of Figure 2, the usage stage is when the low-code development tool (on the low-code execution platform side) analyzes the registered business application settings, converts them into a business application, and then the business operator operates the business application. Operational tests before delivery are also performed on the created business application.

[0055] (3) Setting up low-code development tools This section explains how developers configure low-code development tools. By configuring low-code development tools, developers can generate parts other than business logic without programming themselves. In the following explanation, application configuration using low-code development tools is referred to as "UI definition."

[0056] The registered UI definition is stored in the definition management table (see Figure 3) of the business application DB. The definition management table manages the control information, logic information, and information linking the layout and logic within the definition. The meanings of the terms in the definition management table are as follows: ·Definition ID···A Guid string that is automatically assigned when a UI definition is created. · Definition name · Named by the developer when creating the UI definition. Control Information See “(A) Layout Development” below. Action Information: See “(B) Logic Flow and Action Development” below. · Logic Flow Information · See “(B) Logic Flow and Action Development” below. Linking information: See "(C) Combining Layout and Logic" below.

[0057] (A) Layout Development During the development stage, the developer operates the layout development screen to register control information in the development application DB (see Figure 4). For example, in the example screen in Figure 5, a text box for entering a reference date has been selected from the Date Text menu and placed. By clicking on the placed control, the properties can be set according to the type of control clicked. For example, date text has a required property that indicates whether its input is required by the application. In the example screen in Figure 5, the required property is ON, so the reference date text is a control that must be entered by the application.

[0058] In the usage phase, the application is generated based on the settings. In the example of Figure 5 described in the previous paragraph, the base date is required, so if the business operator attempts to proceed with the process without entering the base date, an error will be displayed as shown in Figure 6.

[0059] (B) Logic flow and action development During the development stage, developers operate the logic flow and action development screen to register logic flow information and action information in the development application DB (see Figure 7). Figure 8 shows an example of the logic flow development screen. It shows an example of an API call action placed in a flow. The initial state of logic flow settings in low-code development tools is that the flow is connected between a start action for starting processing and an end action for ending processing. The settings are made by incorporating the required actions between these two actions as shown in Figure 8.

[0060] In the example logic flow in Figure 8, an API call action is executed. As mentioned above, low-code development tools can only generate the UI portion of a business application, and developers must develop business logic such as retrieving and updating business data through programming. In other words, the business logic itself is external logic independent of the low-code development tool. An API call action is a special action that can link and execute UI information created with a low-code development tool and business logic created by a developer. In preparation, developers turn the business logic they want to call from the UI side generated with the low-code development tool into an API (see the top of Figure 9) and register it in the API master (see the bottom of Figure 9).

[0061] This section explains how to turn business logic into an API. As shown in the upper part of Figure 9, source code that describes processing as an API is created in the module used in the low-code execution platform. In other words, the actual processing of the business logic to be executed and key information that will be required later when calling the API are managed.

[0062] The low-code development platform reads the information required to execute the API (method name, arguments, return value information, etc.) from the low-code execution platform module and registers it in the API management table as shown in the lower part of Figure 9.

[0063] In the upper example of Figure 9, the low-code execution platform registers an API such as a customer data acquisition process that, when a base date (date) is specified as an argument, returns a list of customer information (customer CD and customer name, etc.) registered as of that date.

[0064] Then, on the editing screen for the API call action, as shown in Figure 10, the developer selects the required API from the API master that stores the APIs previously registered by the developer, and sets the arguments and return values ​​for that API.

[0065] The action information will now be explained. As shown in Fig. 11, the action information in the definition management table contains information set for each action (ID, name, action type, and each setting, etc.). In the example of an API call action, the value of the argument (base date) passed to the API is set to the value of the base date text on the screen, and the values ​​of the returned values ​​(client CD and client name, etc.) are set to the client CD text cell and client name text cell on the screen, and information is registered.

[0066] The logic flow information will be explained. As shown in Fig. 12, the logic flow information in the definition management table contains information set for each logic flow (such as ID, name, and flow group that connects actions). The previous action ID is the ID of the action that is processed first, and the next action ID is the ID of the action that is executed after the previous action is executed.

[0067] (C) Combining layout and logic In the development stage, the developer assigns a logic flow to each control on the layout development screen, and registers the linking information in the definition management table of the development application DB (see Figure 13). The controls and flows created in "(A) Layout development" and "(B) Logic flow and action development" are assigned. As shown in Figure 14, the control properties include an event item (click event in the case of a button control), where the flows previously registered are listed in a pull-down list.

[0068] The linking information will now be explained. As shown in Fig. 15, the logic flow information in the definition management table registers three pieces of information linked together: the control (display button) ID, the event type, and the logic flow (logic flow 1) ID. For a control that can be assigned to multiple events, the linking cannot be specified by the control ID alone, so the event type must be included in the linking information (e.g., text box validation processing and exit processing).

[0069] In the usage phase, when a business operator presses the Display button, the low-code execution platform executes the logic flow assigned to the Display button (see Figure 16). In the example of Figure 16, when the Display button is pressed, the API is executed with the base date (2022 / 04 / 01) as an argument. The API call process is started, the configured API (customer data retrieval process) is executed, and the customer information (customer code and customer name) as of the base date is returned as the return value, referencing the customer master.

[0070] [3-2. About the code search function] This section explains the code search function, which is frequently used in ERP systems, etc. This function itself is commonly used in ERP systems, etc., and is a functional requirement that is a prerequisite for the invention.

[0071] The code search function refers to the function that displays the name in an adjacent label after a code is selected for a text box. This type of mechanism is generally provided by a UI such as a "combo box" or "drop-down list." A "drop-down list" is a control that allows the user to display a list of selectable values ​​by clicking on the text portion. Application users cannot directly type into the text portion. A "combo box" is a control that has the functions of both a drop-down list and a text box. Unlike a drop-down list, application users can directly type into the text portion. The following explanation uses a combo box type text box as an example.

[0072] There are three ways to set a value in the text field: (1) Selecting from a list in a text box (2) Direct input without using a list (3) Selecting a value from a dialog box launched by clicking a button

[0073] The following explanation uses the document list as an example. Figure 17 shows an example of the document list screen and the office search dialog. The document list screen is a screen that displays a list of documents registered in the database by narrowing down the conditions. It obtains a list of documents registered in the period from the start date of occurrence to the end date of occurrence for the business establishment specified as the condition. The base date is used to check the existence of the business establishment, and an error is displayed if a business establishment that does not exist as of the base date is specified as a condition. Pressing the office button "···" on the document list screen will launch the business establishment search dialog.

[0074] To specify the establishment as a condition, the application user must specify the establishment from among the establishments registered in the establishment master. The code search function is often used in such cases.

[0075] The code search function is often made up of three controls: a text box, a button, and a label. The text box has the function of displaying a list of selectable data by clicking the ▽ part. The button has the function of calling up a separate screen specialized for the search function. This is because lists are not suitable in some cases, such as when dealing with large amounts of data. The button is often used to display a separate advanced search dialog box when simply selecting a value from the list in the text box is not sufficient for the search function. The label has the function of displaying the name of the master that corresponds to the code entered in the text box.

[0076] The application developer must assign an event to each control of the code search function in advance during development. When the application user performs an operation, the event is fired and the process assigned to the event is executed.

[0077] Figure 18 shows an example of a list of processes related to the code search function. The operations of the application user and their main process contents are as follows: Clicking on the ▽ part of the "1-1:Establishment text box" will execute the establishment acquisition process. When you select "1-2: Select the list in the business establishment text box," the business establishment verification process will be executed. Clicking "2-1: Business Establishment Button" will launch the business establishment search dialog. When you select "2-2: Select a business establishment from the business establishment search dialog", the business establishment validation process will be executed. If you select "3-1: Enter the value in the establishment text box directly," the establishment validation process will be executed.

[0078] Validation processing is a process that commonly occurs when the text value is changed by some means. However, when the value is changed by selecting from a list or dialog (1-2, 2-2 in Figure 18), it is unlikely that data that fails validation will be displayed as an option, so in most cases the validation result will not be an error. Since the only pattern in which an error occurs in validation processing is when validating an error during direct input (3-1), the following explanation will simplify the validation processing of 1-2 and 2-2. The processing in Figure 18 will be explained in detail below.

[0079] "1-1: Click on the ▽ part of the business establishment text box." Figure 19 is a diagram to explain a specific example of the processing that occurs when the ▽ part of the establishment text box is clicked. 1-1-1. Clicking the drop-down list will obtain a list of establishment masters that can be used as of the reference date. 1-1-2. Obtain establishments that exist as of the reference date. 1-1-3. Obtain available establishment information (code, name) from the establishment master and display it on the drop-down list.

[0080] "1-2: Select the list in the business establishment text box" 20 is a diagram for explaining a specific example of the process when the list in the business establishment text box is selected. A verification process is performed on the value (Z001) selected on the list, and the name is displayed in the label.

[0081] "2-1: Click the business button" Figure 21 is a diagram to explain a specific example of processing when the establishment button is clicked. 2-1-1. Clicking the establishment button "···" has a function specialized for establishment searches, and clicking the establishment button "···" launches the establishment search dialog. 2-1-2. Clicking the display button of the establishment search dialog 2-1-3. Retrieves establishments that existed as of the reference date and whose name contains the string "Tokyo". 2-1-4. Sets the establishment code information selected from the establishment search dialog to the establishment text. At this point, it is assumed that the value has been changed, and a verification process is performed to see if the establishment code is valid for the selected value.

[0082] "2-2: Processing after selecting a business establishment from the business establishment search dialog" 22 is a diagram for explaining a specific example of the process after selecting an establishment from the establishment search dialog. A validation process is performed on the value (Z004) selected on the establishment search dialog, and the name is displayed in the label.

[0083] "3-1: Enter the value in the business establishment text box directly" FIG. 23 is a diagram for explaining a specific example of processing when a value is directly entered in the establishment text box. 3-1-1. The application user directly enters a value in the text box, and a verification process is performed to see if the establishment code is valid for the entered value. The following processing is described as a general master verification process. 3-1-2. Based on the base date and establishment code of the arguments, if there is data that matches the establishment code of the argument and satisfies the conditions of start date≦base date and base date≦end date, the name is returned as a return value. If it matches the establishment code of the argument and the base date<start date (in the case of an establishment that will be established in the future) or the end date<base date, the error message "Establishment is outside the validity period" is returned as a return value. If there is no establishment that matches the establishment code of the argument, the error message "Establishment does not exist" is returned as a return value. 3-1-3. If the verification result is NG, the error content is set in the error message property of the text. The error message property is a type of property that can be set in a text box. Unlike a normal value property, when a value is set to this error message property, an error message will be displayed in the text box to notify the user of the error.

[0084] As described above, there are many common operations required when an application user selects a record in the business establishment master. If there are many screens that search for the same master, there are problems with the cost and maintainability of quality control if you develop and configure them one by one. If the number of masters increases, the cost will increase further. For this reason, in this invention, we have developed a mechanism that allows application developers to set up the above code search function in fewer steps.

[0085] [3-3. Code search function realized by common controls] The code search function realized by the common control will be described with reference to Figs. 24 to 47B.

[0086] (I. Development Stage) In this invention, the functional elements required for master searches used on multiple screens are generalized (see "3-2. About the code search function"), and by extracting the commonly required setting elements in the settings of the master search function on each screen, it is possible to save and use them as independent definitions on the low-code development platform. In the following explanation, this definition is referred to as the "common control definition." This common control definition mechanism realizes a mechanism that reduces the setting burden on application developers.

[0087] (A) Registering common control definitions First, the developer sets up the common controls and creates a common control definition. The common control definition is saved in the common control definition management table in the development application database. The common control definition management table manages the type of common control in the definition and the data corresponding to the common control settings.

[0088] Figure 24 shows an example of the menu screen of a low-code development tool. On the menu screen, tabs are displayed on the left side of the screen. If an application is selected, a setting screen for individual screen development is displayed, and if a common control is selected, a common control setting screen is displayed. Here, we will set up common controls, so click the Common Controls tab from the menu screen.

[0089] Figure 25 is a diagram showing an example of a common control setting screen. By selecting the type of common control that can be set from the tabs at the top of the screen, a list of registered common controls is displayed. Pressing the New button will transition to new creation mode of the common control setting screen for the selected type.

[0090] (Common control settings screen) (A-1) Setting the text box part of the common control of code search type The common control setting screen is where you set up the code search type common control. For the search function that needs to be set in the text box, it is assumed that a pull-down definition like the one shown in Figure 26 has been registered beforehand. The pull-down function is an input candidate selection function that assists the operator in entering data. To provide the pull-down function in an application, it is necessary to set elements such as the API that retrieves records, the items to be displayed in the list, and the value to be returned to the text box when a list selection is made.

[0091] The API to retrieve the record is selected from the records registered in the API management table. The API management table has the following fields: ID, method name, API name, arguments (ID, name, type), and return value (ID, name, type).

[0092] The pull-down management table has ID, pull-down name, APIId, return value (ID, name, type), and display item (ID, name, type of each item). The display item and return value to the text box are selected from the API return values.

[0093] 1. APIId is an ID used to obtain the information to be displayed in the pull-down menu from the API management table, and one is selected from the API management table. 2. The API return value is the element that is set in the text box after selecting from the drop-down list, and one of the API return values ​​is selected. 3. Display items are the elements to be displayed on the drop-down list, and one or more items can be selected from the API return values. Display the items (office code, office name) you want to display on the drop-down list in a row.

[0094] The code search function uses text boxes, buttons, and labels, so you need to set the common parts in each setting. There is no common setting for labels, so there is nothing in particular.

[0095] 27 is a diagram showing an example of a common control setting screen (when setting text boxes) and an image of a list display state. The common control setting screen has a field for setting a name, tabs for text boxes, buttons, and labels, and an area for setting the selected tab.

[0096] Application developers can freely set the "Name" field. Depending on the type of common control selected, it is possible to set each component control, and the code search function can be used to set three types of controls: text boxes, buttons, and labels.

[0097] In the text boxes, set the following information: 1. Select the pulldown definition to be used when obtaining the display data for the dropdown list. Obtain the pulldown list information from the pulldown definition management table. The list will display the pulldown definition information obtained from the pulldown management table.

[0098] 2. Select the API to be used when verifying the establishment code. The list will display a list of APIs retrieved from the API management table. Based on the selected verification API information, a list of return values ​​will be retrieved from the API management table.

[0099] 3. Among the obtained verification API return values, set the return value to be returned as the label value (for when verification ends normally). In the list, obtain and display a list of business verification API return values ​​from the API management table. 4. Set the value to be returned as a text error message among the return values ​​of the validation API (for when validation ends with an error). In the list, retrieve and display a list of the business validation API return values ​​from the API management table.

[0100] (A-2) Setting the button part of the code search type common control When setting the button part, it is assumed that a search dialog screen has already been set up in the definition management table. Furthermore, the search dialog screen used in the common control settings has two special actions set up, called screen closing actions, which are executed when the dialog screen itself is closed: when a value is selected and when it is cancelled.

[0101] Figure 28 shows the records registered in the definition management table, and also displays an excerpt of information from the business search dialog screen registered in the definition management table. The definition management table contains logic flows assigned to the select button and the cancel button, and within each logic flow, a special action called a screen close action is executed. When the screen close action is executed, the logic flow processing ends and the dialog screen is closed. This is a mechanism that allows processing to continue on the parent screen side.

[0102] 29 is a diagram showing an example of a common control setting screen (when setting buttons) and an image of a list display state. The following information is set for the buttons. 1. Select the button type. If you select "Use", you can launch a screen with a different UI definition created in the low-code development tool. If you select "Do not use", the button will not be used (it will be composed of only text and labels).

[0103] 2. Select the screen to display when the button is clicked. The list displays definitions retrieved from the definition management table. The list of UI definitions is retrieved by referencing the records registered in the definition management table. In the dialog screen that is launched by clicking a button, it is assumed that the screen will close and return to the screen that was launched by selecting either (1) a selection process or (2) a cancellation process. In order to implement the selection process and the cancellation process, it is necessary to set a special action called a screen closing action (an action that must be set when closing the screen). In the setting of the button part of the common control definition, a list of screen closing actions is referenced from among the actions set in the dialog (business search dialog), and the action information that is called when a value is selected or canceled is stored in the definition. When the action information stored on the dialog screen side is called, the process branches on the screen that was launched from (see the process of converting the business search dialog argument information in (II. Conversion of common control information in the usage phase)).

[0104] 3. From the actions that are executed when the screen is closed, select the process that will be executed when the dialog value is selected. The list shows the screen closing actions retrieved from the action information in the definition management table.

[0105] 4. From the actions that are executed when the screen is closed, select the process that is executed when the dialog is canceled. The list displays a list of screen closing actions obtained from the action information in the definition management table. From the list of controls set on the selected screen (business search dialog), select the process to be executed when a value is selected or when the dialog is canceled.

[0106] 5. Select the value to be updated from the dialog. The list displays the controls for which values ​​can be set, retrieved from the control information in the business search dialog definition.

[0107] After configuring the text boxes and buttons, press the Register button and the common control definition will be registered in the common control definition management table. Information such as the definition name and creation date and time can also be confirmed on the common definition list screen. Figure 30 shows an example of the common definition list screen after registration. Figure 31 shows an example of a registered common control definition management table.

[0108] The common control definition management table includes a definition ID, a definition name, a common control type, and data. Definition ID: Key information that is automatically assigned when creating a UI definition Definition name: Named by the developer when creating the UI definition Common control type: Determined by the type of common control selected: 1 for code search type common control, 2 for optional search type, etc. Data...Common control settings

[0109] In this example, the definition ID is "GlobalControlKey1", definition name is "business code search common control", common control type is "1 (code search)", data is "Text box: pull-down definition (ID "PullDownKey1 (business pull-down definition)", validation process (ID "APIKey2 (business validation API)", return value (value) "KenshouAPIReturnValue1 (business name)", return value (error) "KenshouAPIReturnValue2 (error message)", button: type (1 (use)), target screen (ID "AppDefinitionKey1 (business search dialog)", when selected "SelectActionKey (selection process)", when canceled "CancelActionKey (cancellation process)", return value "ZigyoushoCDCell (business code cell)".

[0110] (B) Use common control definitions in in-application settings Here, we will set up the common control definition (business establishment code search common control) registered earlier so that it can be used within the application. In the following example, we will use the "business establishment code search common control" registered earlier in the settings section related to business establishments in the slip list.

[0111] Fig. 32 is a diagram showing an example of a definition management table. Fig. 33 is a diagram showing an example of a slip list screen. Common controls are placed in the dotted line area of ​​the slip list screen and settings are performed.

[0112] Like normal controls, the Business Code Search Common Control is placed on the document list screen. When using a button, the three controls, text box, button, and label, can be set as a single control called a common control. When not using a button, the two controls, text box and label, can be set as a single control called a common control.

[0113] For common controls, the following three properties can be specified, as shown in Figure 34. Figure 34 shows the setting items and specified contents for common controls. (1) Pull-down definition argument: FROM... Specifies the value to be passed to the API argument used in the pull-down definition (business establishment pull-down definition) (2) Pull-down definition argument: TO... Specify the argument of the business establishment acquisition API to pass the value (reference the argument information of the business establishment acquisition API from the API management table) (3) Verification API Argument: FROM... Specifies the value to be passed to the argument of the business verification API. (4) Verification API arguments: TO... Specify the argument of the business establishment verification API to pass the value (reference the argument information of the business establishment verification API from the API management table) (5) Verification API return value (optional): FROM...Specify the return value of the business establishment verification API (refer to the return value information of the business establishment verification API from the API management table), TO...Specify the control on the screen that will receive the value

[0114] The following specifies the value to be passed to the dialog screen that is called when the button is clicked, only in the case of a common definition that uses a button (values ​​can also be passed to the dialog itself, just like the API). (6) Search dialog arguments: FROM... Specifies the value to be passed to the business search dialog (7) Search dialog arguments: TO... Specifies where to pass the values ​​in the business search dialog

[0115] For each property, select the value (caller) to be passed to the argument and the argument (callee) to pass the value to. When the developer selects a common control placed on the screen, the information of the API and dialog (business establishment acquisition API, business establishment verification API, business establishment search dialog) referenced by the common control is read, and the property title (underlined part on the screen) is replaced (e.g., business establishment acquisition API argument).

[0116] The above (5) is an optional item that can be set. To implement the code search function, it is sufficient to return the label value and error message from the validation API, and the controls that will receive each value are self-evident (the text and label of common controls), so there is no need to set it on this screen.

[0117] In this case, the business establishment validation API returns elements other than the label value and error message (○○ category 1) as return values, so by specifying any control on the screen that will receive the values, the required values ​​can be set on the screen all at once in a single validation process. This increases the extensibility of the code search function.

[0118] Fig. 35 is a diagram showing an example of a common control setting screen. When the business establishment code search common control is placed in the dotted line position on the right side from the common control area by dragging and dropping with the mouse, a screen for setting properties (common controls) as shown in Fig. 36 is displayed, and the above-mentioned properties (common controls) (1) to (7) can be set.

[0119] The information on the registered common control is added as one piece of control information to the definition management table, just like normal controls, as shown in Figure 37. In Figure 37, the common control is added as control X in the control information. The common control definition ID becomes the key of the common control definition management table. The properties of the common control (acquisition API arguments, validation API arguments, validation API return value, and business establishment search dialog arguments) are added.

[0120] In the example shown in the figure, control X has the ID "...", identification name "business code search common control", control type "code search common control", common control definition ID "GlobalControlKey1", acquisition API argument (1: caller (From) "base date text box (value)", callee (To) Reference date (ShutokuAPIArgs1), validation API arguments (1: Caller (From) "Reference date text box (value)", Callee (To) "Reference date (KenshouAPIArgs1)", 2: Caller (From) "Establishment code search common control (value)", Callee (To) "Establishment code (KenshouAPIArgs2)"), validation API return value (1: Caller (From) "○○ category 1 (KenshouAPIReturnValue3)", Callee (To) "※Any item on the screen", Establishment search dialog arguments (1: Caller (From) "Reference date text box (value)", Callee (To) "Reference date text box (value)".

[0121] During the development stage, (A) after the common control definition is registered, the application developer for each screen uses the common control definition to (B) set the common control definition within the application. By reusing information commonly required for the code search function and minimizing the information required for each screen, the productivity and maintainability of the application can be improved.

[0122] When using the developed application, the definition information set in the business application database is published (see "About Low-Code Development Tools"). When the application is executed on the low-code execution platform, the configuration information in (A) and (B) is analyzed and converted into definitions that can be used by the application.

[0123] (II. Conversion of common control information during use) The common control defined in (B) during the development stage in the application settings is a special control that combines text, buttons, and labels. This common control will not function as a control on the application if left unchanged. Therefore, it is necessary to convert the application information using the flowchart below.

[0124] (Flowchart processing overview) Fig. 38 is a flowchart for executing the UI definition of a slip list as an application. This flowchart is executed by the execution unit 102b. In this flowchart, information on the application information to be started is read, and if common control information is included, the definition is dynamically converted. New controls (text, buttons, labels) included in the common control definition are added, and the functions required to realize the code search function are generated and assigned to each control. As a result, it is converted into application information that can finally be used.

[0125] The business application DB contains a definition management table, a common control definition management table, and a pull-down definition management table.

[0126] In Fig. 38, when an application user starts the slip list application (step S1), the execution unit 102b reads the slip list application information from the definition management table (step S2). It is determined whether the control information of the read application information includes a code search type common control (step S3). If the control information does not include a code search type common control ("No" in step S3), the process proceeds to step S13.

[0127] If the control information includes a code search type common control ("Yes" in step S3), 1. Add three controls to the control information: a text box, a button, and a label (step S4). 2. Convert the property reference points of the code search type common control to normal controls (step S5). 3. Combine the acquisition API argument information and the common control definition and convert them into text box pull-down information (step S6). 4. Convert the verification API argument information and verification API return value information into logic flow information and action information (step S7). 5. Link the logic flow created in 4 to the text box event (step S8).

[0128] Next, the execution unit 102b judges whether or not the common control definition is set to use a button (step S9). If the common control definition is not set to use a button ("No" in step S9), the process proceeds to step S13.

[0129] If the common control definition is set to use a button (step S9: "Yes"), 6. Convert the business establishment search dialog argument information into logic flow information and action information (step S10). 7. Link the logic flow created in 6 to the button event (step S11). The execution unit 102b 8. Deletes the common control from the control information (step S12) and proceeds to step S13.

[0130] In step S13, 9. performs processing to start up the slip list in accordance with the UI definition of the converted slip list (step S13).

[0131] Next, the processes 1 to 9 in the above flowchart will be described with reference to FIGS. (1. Add a normal control that corresponds to the common control to the control information) In Fig. 39, if the common control is a code search type that uses a button, a text box, a button, and a label control are added to the definition management table. If the common control is a code search type that does not use a button, a text box and a label control are added.

[0132] In the control information of the definition management table, a common control is set as control X. Add controls X1, X2, and X3 for the text, button, and label that correspond to this control X, in the normal control format (ID, identification name, control type).

[0133] (2. Code search: Convert property references to common controls to normal controls) In the low-code development tool, it was set as the value of a common control (business establishment code search common control), but since it is an element that corresponds to the value of the text box when used in the application, it is converted when the normal control is added in 1. In the example shown in Figure 39, the "business establishment code search common control (value)" is converted to "business establishment text box (value)."

[0134] (3. Combine the obtained API argument information and the common control definition to convert it into pull-down information for the text box) FIG. 40 shows examples of a common control definition management table and a pull-down definition management table, and FIGS. 41 and 42 show examples of definition management tables.

[0135] The information in the pull-down definition management table (APIId, return value, display item) is obtained from the pull-down definition "PullDownKey1" information in the common control definition management table, and the caller's control and the callee's API arguments are identified from the obtained API argument information in the definition management table.

[0136] In FIG. 40, the pull-down definition ID "PullDownKey1" is obtained from the common control definition management table, and the APIId, return value, and display item are obtained from the pull-down definition management table using the obtained pull-down definition ID "PullDownKey1" as a key.

[0137] Acquire API argument information from the definition management table (see FIG. 41). That is, acquire common control information defined in the UI.

[0138] Based on the API ID, return value, and display item obtained from the pull-down definition management table and the obtained API argument obtained from the definition management table, the pull-down setting information (ID, API identifier, argument, return value, display item) required for the text box (to link with the text box) is generated, and the pull-down setting information and pull-down relationship information (control ID, pull-down ID) are added to the definition management table as shown in Fig. 42. The pull-down relationship information links the pull-down to the control, and plays the role of linking the control ID and the pull-down ID.

[0139] (4. Convert the validation API argument information and validation API return value information into logic flow information and action information and link them to the text box) The validation API arguments and validation API return values ​​in the definition management table in the upper left of Figure 43 (an excerpt of the validation API arguments and return value property settings for the common control) are converted into logic flow information and action information, and added to the definition management table as shown in the lower right of Figure 43.

[0140] At that time, a logic flow like that shown in the lower left of Figure 43 is generated internally based on the information in the validation API arguments, and is added as a new logic flow element and action element in the UI definition. Furthermore, when converting to action information, the validation process information in the common control definition management table shown in the upper right of Figure 43 is also used. Note that the return value of the action information element is always the business name returned in a label, and the error message is always returned in a text error message.

[0141] (5.4 Link the logic flow created in the text box event) Figure 44 shows an example of the definition management table (an excerpt of the generated linking information), and adds linking information to link the created logic flow to a text box event. In this example, linking information for the control ID "ZigyoushoTextKey", event type "verification", and logic flow ID "LogicFlowKey1" is added.

[0142] For common control definitions that use buttons, the following conversions are performed: (6. Convert argument information from the business search dialog to logic flow and action information) A logic flow is automatically created that separates the processing when selecting and canceling on the dialog. In Figure 45, the business office search dialog arguments in the definition management table (excerpt of the dialog argument setting part of the common control) and the common control definition management table Based on the button information of the business code search common control, a logic flow such as that shown in the lower left of Figure 45 is generated internally, and logic flow information and action information based on the generated logic flow are generated and added to the definition management table.

[0143] The button information in the common control definition is "SelectActionKey (selection process)" when selected, so when selection processing is performed on the business search dialog side, the flow proceeds to that when selected, and when cancellation is performed is "CancelActionKey (cancellation process)", so when cancellation processing is performed on the business search dialog side, the flow proceeds to that when canceled.

[0144] A supplementary note about logic flow branching: Flow elements 2 and 3 are special flows that, when a screen launch action is set in the previous action ID, branch off subsequent processing depending on the screen close action processing of the child screen launched by the screen launch action.

[0145] In the common control definition, a screen exit action when a dialog value is selected and a screen exit action when the dialog is cancelled are registered, and the subsequent processing is branched depending on each processing.

[0146] For details about the screen end action set on the dialog side, refer to the description in "(A-2) Setting the button part of the code search type common control." In this example, the actions to be taken when a value is selected and when it is canceled are registered in the button defined in the common control, so when the selection process (SelectActionKey) on the business search dialog side is executed, the process branches to flow element 2 and the screen update action on the parent screen is called. When the cancellation process (CancelActionKey) is executed, the process branches to flow element 3 and the end action on the parent screen is called.

[0147] For the buttons defined in the common controls, when selected it is set to "SelectActionKey (selection process)", so when the selection process is performed on the business search dialog side, the flow proceeds to that when selected, and when canceled it is set to "CancelActionKey (cancellation process)", so when the cancellation process is performed on the business search dialog side, the flow proceeds to that when canceled.

[0148] (Link the logic flow created in 7.6 to the button event) Figure 46 shows an example of the definition management table (an excerpt of the generated linking information), and adds linking information to link the created logic flow to a button event. In this example, linking information for the control ID "ZigyoushoButtonKey", event type "click", and logic flow ID "LogicFlowKey2" is added.

[0149] (8. Remove common controls from control information) Delete the common control from the control information in the definition management table. Figures 47A and 47B show examples of the definition management table in which the common control has been deleted from the control information. With control X (the common control portion) deleted, only the text, button, and label portions remain in the control information.

[0150] As a result, the definition of the document list that used the common control has been converted to logic flow and action settings using normal text boxes, buttons, and labels, and can now be used as a normal definition. By performing this conversion work internally, developers do not have to assign logic flow and action settings to each control such as text boxes in the low-code development tool, reducing the developer's burden. By interpreting the registered information at run time and performing the conversion rather than performing the conversion when the common control is placed, even if the common control definition is changed, the changes are reflected in real time at run time, which has the advantage of high maintainability. In the above explanation, we have explained the case where the code search type of common control is used, but even if a different type of common control (with different control combinations and processing contents) is used, the necessary processing for the application can be realized by performing the same conversion process.

[0151] [3-4. Scope and concept of the present invention] In the above embodiment, the common control definition of the code search type has been described, but the present invention is not limited to this, and similar processing can be performed when using common control definitions of other search types such as value search type and arbitrary search type. Fig. 48 shows a table summarizing the applicable scope of the present invention and its higher level, middle level and lower level concepts. Fig. 49 shows the corresponding parts in Fig. 27 of the components A to D of the common control UI definition in Fig. 48, Fig. 50 shows the corresponding parts in Fig. 29 of the components E to I of the common control UI definition in Fig. 48, and Fig. 51 shows the corresponding parts in Fig. 36 of the business application screen side settings (1) to (7) in Fig. 48.

[0152] Fig. 52 shows a flowchart for the case where the UI definition of a business application executed by the execution unit 102b is executed as an application. Fig. 52 shows a flowchart based on a higher concept than the flowchart in Fig. 38. The present invention can be applied to business applications other than the slip list, and can also be applied to search types other than the code search type.

[0153] In Fig. 52, when an application user starts a business application (step S21), application information of the business application is read from the definition management table (step S22). It is determined whether the control information includes a common control of a search type (e.g., a code search type) (step S23). If the control information does not include a common control of a code search type ("No" in step S23), the process proceeds to step S30.

[0154] If the control information includes a search-type common control ("Yes" in step S23), 1. At least two of the following are added to the control information: a value specification area of ​​the common control (e.g., a text box) and a dialog display button. 3. Pull-down display command argument information (e.g., acquisition API argument information) is combined with the common control definition to convert it into pull-down information for the value specification area (step S25). It is determined whether or not the common control definition is for a setting that uses a dialog display button (step S26). If the common control definition is not for a setting that uses a dialog display button ("No" in step S26), proceed to step S30.

[0155] If it is a common control definition with settings that use a dialog display button ("Yes" in step S26), 6. Convert the dialog display command argument information (for example, office search dialog argument information) into logic flow information and action information (step S27). 7. Link the logic flow information created in 6 to the dialog display button event (step S28). 8. Delete the common control from the control information (step S29).

[0156] In step S30, 9. the process of starting up the business application is carried out in accordance with the UI definition of the converted business application.

[0157] As described above, according to this embodiment, there is a definition management table in which a definition ID, a definition name, control information defining an ID, an identification name, and a control type for each control, logic flow information defining an ID, a previous action ID, and a next action ID for each element of a logic flow, and action information defining an ID, a name, a type, an API, an argument, and a return value for each action element are associated and registered, and a common control definition management table in which definition IDs, definition names, common control types, and setting contents are associated and registered for defining common control definitions common to a plurality of business applications, and when an instruction to start a business application is received from a user, application information of the business application is read from the definition management table, and if a search type common control is included in the control information of the definition management table, a value specification area for the common control, a dialog box, a search type common control, and a search type common control are included in the control information. The system further includes an execution unit 102b that adds a control including at least two of the common control pull-down display command and action display buttons, combines the pull-down display command argument information of the common control with the common control definition to convert it into pull-down information for a value specification area, and in the case of a common control definition for a setting that uses a dialog display button, converts the dialog display command argument information into logic flow information and action information, links the created logic flow information to an event of the dialog display button, deletes the common control from the control information, and performs startup processing for the business application in accordance with the UI definition of the converted business application.By providing a mechanism for patterning frequently used application functions and saving reusable settings for each pattern as an independent common control definition, it is possible to provide users with a business application that reduces the amount of work required for configuration and prevents problems caused by configuration errors.

[0158] [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.

[0159] 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.

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

[0161] 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.

[0162] 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.

[0163] 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.

[0164] Furthermore, with regard to the application providing system 100, the components shown in the figures are merely functional concepts, and do not necessarily have to be physically configured as shown in the figures.

[0165] For example, the processing functions of the application providing system 100, particularly the processing functions performed by the control unit 102, 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 application providing system 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 cooperates with the CPU to form a control unit.

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

[0167] 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.

[0168] 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 configuration that is distributed as a plurality of modules or libraries, and a program that achieves its function by cooperating with a separate program, such as an OS. Note that the specific configuration and reading procedure for reading a recording medium in each device shown in this embodiment, as well as the installation procedure after reading, may use well-known configurations and procedures.

[0169] The various databases etc. stored in the memory unit 106 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.

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

[0171] 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. [Explanation of symbols]

[0172] 100 Application provision system 102 Control section 102a Setting section 102b Executive Department 104 Communication interface section 106 Storage section 106a Development application DB 106b Business application database 108 Input / Output Interface Section 112 Input Devices 114 Output Device 200 Servers 300 Network

Claims

1. An application providing system including a control unit and configured to be capable of data communication with developers and users, The control unit is A definition management table in which a definition ID, a definition name, control information defining an ID, an identification name, and a control type for each control, logic flow information defining an ID, a previous action ID, and a next action ID for each logic flow element, and action information defining an ID, a name, a type, an API, an argument, and a return value for each action element are associated and registered. A common control definition management table that specifies common control definitions common to multiple business applications and registers definition IDs, definition names, common control types, and setting contents in association with each other; The system is configured to be able to access a database that stores an execution means for starting a business application when a start instruction is received from a user; The execution means includes: When an instruction to start a business application is received from a user, application information of the business application is read from the definition management table; When the control information in the definition management table includes a search type common control, a control including at least two of a value specification area and a dialog display button of the common control is added to the control information, The pull-down display command argument information of the common control is combined with the common control definition to convert it into pull-down information of the value specification area; In the case of a common control definition that uses a dialog display button, the dialog display command argument information is converted into logic flow information and action information, and the created logic flow information is linked to the dialog display button event, removing the common control from the control information; An application providing system characterized in that it performs start-up processing of a business application in accordance with a UI definition of the converted business application.

2. When the search type is a code search type, the execution means further Convert property references of common controls of code search type to normal controls, Converting the verification API argument information and the verification API return value information of the common control into logic flow information and action information; 2. The application providing system according to claim 1, wherein the created logic flow information is linked to an event of a text box.

3. The control unit is 2. The application providing system according to claim 1, further comprising a setting means for creating the common control definition management table in response to an operation by a developer on a common control setting screen.

4. The application providing system according to claim 3, characterized in that the setting means adds common controls in the common control definition management table to the control information in the definition management table in response to operations by a developer on a business application creation screen.

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

6. An application providing method executed by an information processing device having a control unit and configured to be capable of data communication with a developer's and a user's client, comprising: The control unit is A definition management table in which a definition ID, a definition name, control information defining an ID, an identification name, and a control type for each control, logic flow information defining an ID, a previous action ID, and a next action ID for each logic flow element, and action information defining an ID, a name, a type, an API, an argument, and a return value for each action element are associated and registered. A common control definition management table that specifies common control definitions common to multiple business applications and registers definition IDs, definition names, common control types, and setting contents in association with each other; The system is configured to be able to access a database that stores Executed in the control unit: The method includes an execution step of starting a business application when a start instruction is received from a user, In the execution step, When an instruction to start a business application is received from a user, application information of the business application is read from the definition management table; When the control information in the definition management table includes a search type common control, a control including at least two of a value specification area and a dialog display button of the common control is added to the control information, The pull-down display command argument information of the common control is combined with the common control definition to convert it into pull-down information of the value specification area; In the case of a common control definition that uses a dialog display button, the dialog display command argument information is converted into logic flow information and action information, and the created logic flow information is linked to the dialog display button event, removing the common control from the control information; An application providing method, comprising the steps of: starting up a business application in accordance with a UI definition of the converted business application.

7. An application providing program to be executed by an information processing device having a control unit and configured to be capable of data communication with a user and developer client, The control unit is A definition management table in which a definition ID, a definition name, control information defining an ID, an identification name, and a control type for each control, logic flow information defining an ID, a previous action ID, and a next action ID for each logic flow element, and action information defining an ID, a name, a type, an API, an argument, and a return value for each action element are associated and registered. A common control definition management table that specifies common control definitions common to multiple business applications and registers definition IDs, definition names, common control types, and setting contents in association with each other; The system is configured to be able to access a database that stores In the control unit, an application providing program for executing an execution step for starting a business application when a start instruction is received from a user; In the execution step, When an instruction to start a business application is received from a user, application information of the business application is read from the definition management table; When the control information in the definition management table includes a search type common control, a control including at least two of a value specification area and a dialog display button of the common control is added to the control information, The pull-down display command argument information of the common control is combined with the common control definition to convert it into pull-down information of the value specification area; In the case of a common control definition that uses a dialog display button, the dialog display command argument information is converted into logic flow information and action information, and the created logic flow information is linked to the dialog display button event, removing the common control from the control information; An application providing program that performs a process of starting a business application in accordance with a UI definition of the converted business application.

Images