Application delivery system, application delivery method, and application delivery 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 Art

[0002] Conventionally, as a system for developing applications at low cost, for example, there is Patent Document 1.

Prior Art Document

Patent Document

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] However, Patent Document 1 does not describe anything regarding patterning the functions of frequently used applications and storing reusable settings for each pattern as independent common control definitions.

[0005] The present invention has been made in view of the above, and by providing a mechanism for patterning the functions of frequently used applications and storing reusable settings for each pattern as independent common control definitions, it is possible to reduce the man-hours required for settings and prevent problems due to setting errors, and to provide an application providing system, an application providing method, and an application providing program that can provide users with business applications.

Means for Solving the Problems

[0006] To solve the above-mentioned problems and achieve the objective, the present invention provides an application provision system comprising a control unit and configured to communicate data with developer and user clients, wherein the control unit is configured to access a database storing a definition management table which registers definition IDs, definition names, control information which defines the ID, identification name, and control type for each control, logic flow information which defines the ID, previous action ID, and next action ID for each element of the logic flow, and action information which defines the ID, name, type, API, arguments, and return value for each action element, and a common control definition management table which defines common control definitions common to multiple business applications and registers definition IDs, definition names, common control types, and settings, and the control unit is configured to access a database which stores these, and when it receives a startup command from a user it starts a business application, and the execution means The process is characterized by the following: when a user requests the launch of a business application, the system reads the application information of the business application from the definition management table; if the control information in the definition management table includes a common control of the search type, it adds a control to the control information that includes at least two common control elements: a value specification area and a dialog display button; it 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 the value specification area; if the common control definition is set to use a dialog display button, it converts the dialog display command argument information into logic flow information and action information; it associates the created logic flow information with the event of the dialog display button; it removes the common control from the control information; and it performs the launch process of the business application according to the converted UI definition of the business application.

[0007] Furthermore, according to one aspect of the present invention, if the search type is a code search type, the execution means may further convert the property references of the common control of the code search type into ordinary controls, convert the validation API argument information and validation API return value information of the common control into logic flow information and action information, and associate the created logic flow information with the events of the text box.

[0008] Furthermore, according to one aspect of the present invention, the control unit may also include setting means for creating the common control definition management table in response to the developer's operation on the settings screen.

[0009] Furthermore, according to one aspect of the present invention, the setting means may add common controls from the common control definition management table to the control information of the definition management table in response to the developer's operation on the setting screen.

[0010] Furthermore, according to one aspect of the present invention, the application provisioning system may be configured as a low-code platform or a no-code platform.

[0011] Furthermore, in order to solve the above-mentioned problems and achieve the objective, the present invention provides an application provision method executed by an information processing device equipped with a control unit and configured to communicate data with developer and user clients, wherein the control unit is configured to access a database that stores a definition management table in which a definition ID, a definition name, control information defining an ID, identification name, and control type for each control, logic flow information defining an ID, pre-action ID, and post-action ID for each element of the logic flow, and action information defining an ID, name, type, API, arguments, and return value for each action element is associated and registered, and a common control definition management table that defines common control definitions common to multiple business applications, in which a definition ID, definition name, common control type, and setting content are associated and registered, and the control unit is configured to access a database that stores a definition management table that defines common control definitions common to multiple business applications, and the execution that starts a business application when it receives a start command from a user The execution step includes the following steps: when a user requests the business application to start, the application information of the business application is read from the definition management table; if the control information in the definition management table includes a common control of the search type, a control is added to the control information that includes at least two of the common control's value specification area and dialog display button; the pull-down display command argument information of the common control and the common control definition are combined and converted into pull-down information for the value specification area; if the common control definition is set to use 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 the event of the dialog display button; the common control is removed from the control information; and the business application is started according to the converted UI definition of the business application.

[0012] Furthermore, in order to solve the above-mentioned problems and achieve the objective, the present invention provides an application provision program for execution by an information processing device equipped with a control unit and configured to communicate data with user and developer clients, wherein the control unit registers a definition management table that associates a definition ID, a definition name, control information defining an ID, identification name, and control type for each control, logic flow information defining an ID, previous action ID, and next action ID for each element of the logic flow, and action information defining an ID, name, type, API, arguments, and return value for each action element, and defines common control definitions common to multiple business applications, and registers a common control definition management table that associates a definition ID, definition name, common control type, and setting content, The application provider program is configured to access a database containing the following, and when the control unit receives a startup instruction from a user, it executes an execution step to start the business application. The execution step is characterized by the following: when the user receives a startup instruction for the business application, it reads the application information of the business application from the definition management table, adds a control to the control information that includes at least two of the common control's value specification area and dialog display button if the control information of the definition management table includes a common control of the search type, combines the pull-down display command argument information of the common control with the common control definition and converts it into pull-down information for the value specification area, converts the dialog display command argument information into logic flow information and action information if the common control definition is set to use a dialog display button, associates the created logic flow information with the event of the dialog display button, deletes the common control from the control information, and performs startup processing of the business application according to the converted UI definition of the business application. [Effects of the Invention]

[0013] According to the present invention, by patternizing the functions of frequently used applications and providing a mechanism to save reusable settings for each pattern as independent common control definitions, it becomes possible to provide users with business applications that reduce the effort required for configuration and prevent malfunctions caused by configuration errors. [Brief explanation of the drawing]

[0014] [Figure 1] Figure 1 is a block diagram showing an example of the configuration of the application provisioning system according to this embodiment. [Figure 2] Figure 2 is a diagram illustrating a specific example of the processing of the application provisioning system according to this embodiment. [Figure 3] Figure 3 is a diagram illustrating a specific example of the processing of the application provisioning system according to this embodiment. [Figure 4] Figure 4 is a diagram illustrating a specific example of the processing of the application provisioning system according to this embodiment. [Figure 5] Figure 5 is a diagram illustrating a specific example of the processing of the application provisioning system according to this embodiment. [Figure 6] Figure 6 is a diagram illustrating a specific example of the processing of the application provisioning system according to this embodiment. [Figure 7] Figure 7 is a diagram illustrating a specific example of the processing of the application provisioning system according to this embodiment. [Figure 8] Figure 8 is a diagram illustrating a specific example of the processing of the application provisioning system according to this embodiment. [Figure 9] Figure 9 is a diagram illustrating a specific example of the processing of the application provisioning system according to this embodiment. [Figure 10] Figure 10 is a diagram illustrating a specific example of the processing of the application provisioning system according to this 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 processing of the application providing system according to the present embodiment. [Figure 17] FIG. 17 is a diagram for explaining a specific example of the processing of the application providing system according to the present embodiment. [Figure 18] FIG. 18 is a diagram for explaining a specific example of the processing of the application providing system according to the present embodiment. [Figure 19] FIG. 19 is a diagram for explaining a specific example of the processing 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 processing of the application providing system according to the present embodiment. [Figure 24]Figure 24 is a diagram illustrating a specific example of the processing of the application provisioning system according to this embodiment. [Figure 25] Figure 25 is a diagram illustrating a specific example of the processing of the application provisioning system according to this embodiment. [Figure 26] Figure 26 is a diagram illustrating a specific example of the processing of the application provisioning system according to this embodiment. [Figure 27] Figure 27 is a diagram illustrating a specific example of the processing of the application provisioning system according to this embodiment. [Figure 28] Figure 28 is a diagram illustrating a specific example of the processing of the application provisioning system according to this embodiment. [Figure 29] Figure 29 is a diagram illustrating a specific example of the processing of the application provisioning system according to this embodiment. [Figure 30] Figure 30 is a diagram illustrating a specific example of the processing of the application provisioning system according to this embodiment. [Figure 31] Figure 31 is a diagram illustrating a specific example of the processing of the application provisioning system according to this embodiment. [Figure 32] Figure 32 is a diagram illustrating a specific example of the processing of the application provisioning system according to this embodiment. [Figure 33] Figure 33 is a diagram illustrating a specific example of the processing of the application provisioning system according to this embodiment. [Figure 34] Figure 34 is a diagram illustrating a specific example of the processing of the application provisioning system according to this embodiment. [Figure 35] Figure 35 is a diagram illustrating a specific example of the processing of the application provisioning system according to this embodiment. [Figure 36] Figure 36 is a diagram illustrating a specific example of the processing of the application provisioning system according to this embodiment. [Figure 37]Figure 37 is a diagram illustrating a specific example of the processing of the application provisioning system according to this embodiment. [Figure 38] Figure 38 is a diagram illustrating a specific example of the processing of the application provisioning system according to this embodiment. [Figure 39] Figure 39 is a diagram illustrating a specific example of the processing of the application provisioning system according to this embodiment. [Figure 40] Figure 40 is a diagram illustrating a specific example of the processing of the application provisioning system according to this embodiment. [Figure 41] Figure 41 is a diagram illustrating a specific example of the processing of the application provisioning system according to this embodiment. [Figure 42] Figure 42 is a diagram illustrating a specific example of the processing of the application provisioning system according to this embodiment. [Figure 43] Figure 43 is a diagram illustrating a specific example of the processing of the application provisioning system according to this embodiment. [Figure 44] Figure 44 is a diagram illustrating a specific example of the processing of the application provisioning system according to this embodiment. [Figure 45] Figure 45 is a diagram illustrating a specific example of the processing of the application provisioning system according to this embodiment. [Figure 46] Figure 46 is a diagram illustrating a specific example of the processing of the application provisioning system according to this embodiment. [Figure 47A] Figure 47A is a diagram illustrating a specific example of the processing of the application provisioning system according to this embodiment. [Figure 47B] Figure 47B is a diagram illustrating a specific example of the processing of the application provisioning system according to this embodiment. [Figure 48] Figure 48 is a diagram illustrating the scope of application of the present invention. [Figure 49] Figure 49 is a diagram illustrating the scope of application of the present invention. [Figure 50]Figure 50 is a diagram illustrating the scope of application of the present invention. [Figure 51] Figure 51 is a diagram illustrating the scope of application of the present invention. [Figure 52] Figure 52 is a diagram illustrating the scope of application of the present invention. [Modes for carrying out the invention]

[0015] Embodiments of the application provision system, application provision method, and application provision program according to the present invention will be described in detail below with reference to the drawings. However, the present invention is not limited to these embodiments.

[0016] [1. Overview] The outline of this invention will be explained in the following order: (1. Background and Problems) and (2. Solution).

[0017] (1.Background / Issues) Traditionally, there was no mechanism to standardize application settings, requiring system developers to configure each setting from scratch. This configuration method required checking whether the application settings were correct each time, leading to increased costs for configuration and verification as systems grew larger. Furthermore, it was difficult to ensure system usability at each configuration point, posing a risk of compromising usability.

[0018] For example, in low-code development, developers create systems by dragging and dropping controls (UI elements) and assigning necessary processes (such as API executions) to events associated with those controls (typically click events for buttons). When an application user clicks a button on the browser (client), a button click event is triggered, and APIs are called to interact with data on the server side. Then, depending on the result of the API processing, the server returns the necessary information, which can then be received again on the client side.

[0019] At this time, by reflecting the information returned from the server in the on-screen controls, application users can recognize the server information. Application developers need to decide how to display the information returned from the server as a result of events such as click events in the browser before developing the system. Since such update settings need to be configured for each system event, this becomes more complicated as the system grows larger, leading to a problem of reduced maintainability.

[0020] For example, in ERP systems, the same screen elements are very often used across multiple screens, which necessitates redundant configuration management during development. This creates a problem where application developers are forced to perform redundant development work.

[0021] (2. Solution) In typical business applications, there are frequently used functions such as retrieving the name of a corresponding master data entry from a database when a master data code value is entered. System developers need to configure the system appropriately for each location where they want to use such a function.

[0022] This invention devised a mechanism that patterns frequently used application functions and saves reusable settings for each pattern as independent common control definitions. By using these common control definitions, system developers can reduce the time and effort required for configuration and prevent malfunctions caused by configuration errors.

[0023] For example, in low-code development, common functions such as retrieving master data are used in multiple places, and UI information can often be standardized. By standardizing the UI and logic and reusing those settings as needed, screen-by-screen configuration becomes unnecessary, reducing the cost for the person configuring the system.

[0024] This invention provides a mechanism to define a search control (common control) used by multiple applications and to make the definition of this common search control reusable. While there are general programming concepts such as user controls and custom controls that allow application developers to freely configure such controls, this functionality requires application developers to configure the UI settings and associated event handlers from the beginning. Although it offers a high degree of freedom in configuration, it requires programming knowledge to configure, which presents a challenge in system development.

[0025] In this invention, taking these points into consideration, the setting of common control definitions is generalized to include the setting of UI and event handlers, thereby providing a mechanism to reduce the burden on application developers.

[0026] [2. Structure] An example of the configuration of the application provisioning system 100 (Web server) according to this embodiment will be described with reference to Figure 1. The application provisioning system 100 can be configured, for example, with a low-code platform (a low-code development platform and a low-code execution platform). Alternatively, it may be configured with a no-code platform. Figure 1 is a block diagram showing an example of the configuration of the application provisioning system 100 according to this embodiment.

[0027] The application provisioning system 100 comprises a control unit 102, a communication interface unit 104, a storage unit 106, and an input / output interface unit 108. Each part of the application provisioning system 100 is connected to communicate via any communication path.

[0028] The communication interface unit 104 connects the application provisioning system 100 to the network 300 via communication devices such as routers and wired or wireless communication lines such as dedicated lines. The communication interface unit 104 has the function of communicating data with other devices via communication lines. Here, the network 300 has the function of connecting the application provisioning system 100 with Web clients (clients used by developers and clients used by business operators (users)) 400... and business systems not shown, enabling them to communicate with each other, and is, for example, the Internet or a LAN (Local Area Network). The data stored in the storage unit 106, which will be described later, may be stored in a data server not shown, etc.

[0029] The input / output interface unit 108 is connected to an input device 112 and an output device 114. The output device 114 can be a monitor (including a home television), a speaker, or a printer. The input device 112 can be a keyboard, mouse, microphone, or a monitor that works in conjunction with a mouse to provide pointing device functionality. 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 mouse 112.

[0030] The memory unit 106 stores various databases, tables, and files. The memory unit 106 also stores computer programs that work in cooperation with the OS (Operating System) to give instructions to the CPU (Central Processing Unit) to perform various processes. As the memory 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.

[0031] The memory unit 106 includes a development application DB 106a for storing various setting information during the development stage, a business application DB 106b to which the application information of the development application DB 106a is made public, and the like.

[0032] The development application DB106a stores definition management tables, pull-down definition management tables, common control definition management tables, API management tables, etc.

[0033] The definition management table is a table that registers and associates control information, which defines the definition ID, definition name, ID, identifier name, and control type for each control; logic flow information, which defines the ID, previous action ID, and next action ID for each element of the logic flow; action information, which defines the ID, name, type, API, arguments, and return value for each action element; and linking information, which defines the control ID, event type, and logic flow ID for each linked element. The common controls from the common control definition management table are added to the definition management table.

[0034] The dropdown definition management table is a table where information such as ID, dropdown name, API ID for linking to the API management table, return value, and display items are registered and associated.

[0035] The common control definition management table is used to define common control definitions that are shared across multiple business applications. It is a table that stores definition IDs, definition names, common control types, and configuration details in an associated manner.

[0036] The API management table is a table that stores information such as ID, method name, API name, arguments (ID, name, type), and return value (ID, name, type) in association with each other.

[0037] The control unit 102 is a CPU or similar component that comprehensively controls the application provisioning system 100. The control unit 102 has internal memory for storing control programs such as the OS, programs that define various processing procedures, and required data, and executes various information processing based on these stored programs.

[0038] Functionally, the control unit 102 comprises a setting unit 102a and an execution unit 102b.

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

[0040] For example, the configuration unit 102a provides a common control configuration screen in response to a request from a Web client 400 (developer), and creates a common control definition management table and registers it in the development application DB 106a based on the developer's actions on the common control configuration screen.

[0041] Furthermore, the configuration unit 102a provides a business application creation screen in response to a request from the Web client 400 (developer), and adds (configures) common controls from the common definition management table to the control information of the definition management table in response to the developer's operations 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 startup command from the Web client 400 (user), it starts the business application. Specifically, it reads the application information of the business application from the definition management table, and if the control information in the definition management table includes a common control of the search type, it adds a control to the control information that includes at least two common control elements: a value specification area and a dialog display button. It combines the pull-down display command argument information of the common control with the common control definition and converts it into pull-down information for the value specification area. If the common control definition is set to use a dialog display button, it converts the dialog display command argument information into logic flow information and action information. It associates the created logic flow information with the event of the dialog display button, removes the common control from the control information, and performs the startup process of the business application according to the converted UI definition of the business application.

[0044] Furthermore, if the search type is a code search type, the execution unit 102b further converts the property references of the common control for the code search type into regular controls, converts the validation API argument information and validation API return value information of the common control into logic flow information and action information, and associates the created logic flow information with the event of the text box.

[0045] [3. Specific examples of processing] A specific example of the processing of the application provisioning system 100 (Web server) of this embodiment will be described with reference to Figures 2 to 47. Figures 2 to 47 are diagrams illustrating a specific example of the processing of the application provisioning 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 at client companies. The explanation will be divided into two stages: the development stage, where developers configure the UI and create the business logic of the business application using low-code development tools, and the usage stage, where business operators actually use the application.

[0047] Figure 2 shows an overall diagram of the low-code development tool. The development phase is the stage in which developers use the low-code development platform to register configuration information for business applications in a database. The utilization phase is the stage in which the low-code execution platform analyzes the configuration information registered in the development phase and converts it into an actual business application, allowing business operators to execute their tasks. 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] This section explains the data management methods used at each stage. From a control perspective, it is necessary to clearly separate the database used by developers to manage application settings during development from the database used by business operators to manage application settings during business operations. This is to prevent developers from directly manipulating the business database. In the following explanation, the database used by developers for managing application settings will be referred to as the "development application DB," and the database used by business operators for managing application settings will be referred to as the "business application DB."

[0049] (1) Development stage The development phase, as shown in the upper half of Figure 2, is the stage in which developers develop business applications using low-code development tools (low-code development platform). Low-code development mainly involves setting up the layout of the application screen and the series of event processing (actions, logic flows) that occur when the layout is manipulated. Finally, by linking the layout and logic flows, the UI portion of the business application can be generated. The main settings during the development phase 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 involves configuring the processing part of a business application. Low-code development tools allow you to configure the processing in a business application in units called actions (the linking of the UI and business logic mentioned earlier is also done through these actions). Furthermore, by connecting actions with flows, you can set the order in which a series of actions are processed. This setting of the processing order of actions is called a "logic flow".

[0052] This section explains the special action settings required to invoke business logic. In low-code development, developers create only the business logic through individual programming tasks, while the UI is generated by operating the low-code development tool. Therefore, in order to invoke business logic from the UI side, developers need to convert the created business logic into an API and register it in the API master. By calling the API registered in the API master from the API call action, the business logic can be executed.

[0053] (C) Combining layout and logic flow Configure the settings to assign the logic flow in (B) to the layout set in (A).

[0054] (2) Usage stage As shown in the lower half of Figure 2, the usage phase involves the low-code development tool (low-code execution platform) analyzing the registered business application settings and converting them into business applications, allowing business operators to operate the applications. The operational tests conducted before delivery are also performed on the created business applications.

[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 of the application other than the business logic without having to write the code themselves. In the following explanation, the application configuration using low-code development tools will be referred to as "UI definition."

[0056] Registered UI definitions are stored in the definition management table (see Figure 3) of the business application database. The definition management table manages control information, logic information, and layout-to-logic linkage information within the definition. The meanings of terms used in the definition management table are as follows: • Definition ID: A GUID string automatically assigned when creating a UI definition. • 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) Linking Layout and Logic" below.

[0057] (A) Layout development During the development phase, developers register control information in the development application database by manipulating the layout development screen (see Figure 4). For example, in the example screen in Figure 5, a text box for entering a reference date is selected from the date text options and placed. Clicking on a placed control allows you to set properties according to the type of control clicked. For example, the date text control has a required property that indicates whether its input is mandatory in the application. In the example screen in Figure 5, the required property is ON, so the reference date text control is a required input control in the application.

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

[0059] (B) Logic flow and action development During the development phase, developers register logic flow information and action information in the development application database by operating the logic flow and action development screens (see Figure 7). Figure 8 shows an example of the logic flow development screen. It shows an example where an API call action is placed in the flow. In low-code development tools, the initial state of logic flow settings is a state where the flow is connected between a start action to start processing and an end action to end processing. Settings are made by incorporating the necessary actions between these two actions, as shown in Figure 8.

[0060] In the logic flow example in Figure 8, an API call action is executed. As mentioned earlier, low-code development tools can only generate the UI portion of a business application; the business logic, such as retrieving and updating business data, must be developed by the developer 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 allows the UI information created with the low-code development tool to be linked with the business logic created by the developer and executed accordingly. As preparation, the developer converts the business logic they want to call from the UI generated by the low-code development tool into an API (see upper part of Figure 9) and registers it in the API master (see lower part of Figure 9).

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

[0062] The low-code development platform reads the information necessary for API execution (such as method names, arguments, and return value information) from the modules of the low-code execution platform 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 that retrieves customer data, which, when given a reference date (date) as an argument, returns a list of customer information (customer code, customer name, etc.) registered as of that date.

[0064] Subsequently, on the API call action editing screen, as shown in Figure 10, the developer selects the necessary API from the API master containing pre-registered APIs and sets the arguments and return values ​​for that API.

[0065] This section explains action information. As shown in Figure 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 (reference date) passed to the API is set to the value of the reference date text on the screen, and the return value (customer code and customer name, etc.) returned as a result is set to the customer code text cell and customer name text cell on the screen.

[0066] This section explains logic flow information. As shown in Figure 12, the logic flow information in the definition management table contains information set for each logic flow (ID, name, and the flow group connecting the actions, etc.). 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 During the development phase, developers assign logic flows to each control on the layout development screen, registering the linking information in the definition management table of the development application database (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 have an event item (click event in the case of a button control), where the flows registered earlier are displayed in a dropdown list.

[0068] Let's explain the linking information. As shown in Figure 15, the logic flow information in the definition management table is registered with three pieces of information linked: the control (display button) ID, the event type, and the logic flow (logic flow 1) ID. For controls that can be assigned to multiple events, the linking cannot be identified by the control ID alone, so the event type must be included in the linking information (e.g., validation processing and exit processing for text boxes).

[0069] During 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 in Figure 16, when the display button is pressed, an API is executed with the reference date (2022 / 04 / 01) as an argument. The API call process is initiated, the configured API (customer data retrieval process) is executed, and the customer information (customer code and customer name) as of the reference date is returned as a return value after referencing the customer master.

[0070] [3-2. About the code search function] This section describes the code search function, which is frequently used in ERP systems and similar applications. This function itself is a commonly used feature in ERP systems and is a functional requirement that forms the basis of the invention.

[0071] A code search function refers to a feature that displays the name of a code in an adjacent label after the user selects a code in a text box. This type of mechanism is generally provided using UI elements such as "combo boxes" or "dropdown lists." A "dropdown list" is a control that displays a list of selectable values ​​when the user clicks on the text area. The application user cannot directly input text into the text area. A "combo box" is a control that combines the functions of both a dropdown list and a text box. Unlike a dropdown list, the application user can directly input text into the text area. The following explanation will use a combo box-type text box as an example.

[0072] We will consider the following three methods for setting values ​​in the text portion. (1) Cases where you select from a list in a text box (2) Cases where input is done directly without using a list (3) Cases where a value is selected from a dialog box launched by clicking a button.

[0073] The following explanation uses the voucher list as an example. Figure 17 shows an example of the voucher list screen and the office search dialog. The voucher list screen displays a list of vouchers registered in the database, filtered by specific criteria. It retrieves a list of vouchers registered within the specified business establishments for the period from the start date to the end date of the occurrence date. The reference date is used to check the existence of the business establishment; if a business establishment that does not exist as of the reference date is specified as a condition, an error will be displayed. On the voucher list screen, pressing the office button "..." will launch the office search dialog.

[0074] To specify a business location that meets the criteria, application users need to select a business location from those registered in the business location master. The code search function is a frequently used feature in such cases.

[0075] A code search function is often composed of three controls: a text box, a button, and a label. The text box has the function of displaying a list of selectable data when the ▼ icon is clicked. The button has the function of calling up a separate screen specifically for the search function. This is because a list may not be 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 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 corresponding to the code entered in the text box.

[0076] Each control in the code search function requires the application developer to pre-assign events during development. When an application user interacts with it, an event is triggered, and the process assigned to that event is executed.

[0077] Figure 18 shows an example of a list of processes related to the code search function, and the operations performed by the application user and their main processing contents are as follows: Clicking the ▼ in the "1-1: Business Establishment Text Box" will execute the business establishment acquisition process. When you select "1-2: Select from the list of business location text boxes," the business location verification process will be executed. Clicking the "2-1: Business Office" button will launch the business office search dialog. When you select "2-2: Select a business from the business search dialog," the business verification process will be executed. If you "3-1: Directly enter a value in the business establishment text box," the business establishment verification process will be executed.

[0078] Validation processing is a common process that occurs when a text value is changed by any means. However, when the value is changed by selecting from a list or dialog (Figure 18, 1-2, 2-2), it is unlikely that data that would fail validation will be displayed as an option, so in most cases the validation result will not be an error. The only pattern in which errors occur during validation is, in effect, when errors occur during direct input (3-1), so in the following explanation, the validation processes of 1-2 and 2-2 will be described in a simplified manner. The process in Figure 18 will be explained in detail below.

[0079] "1-1: Click the ▽ in the business name text box." Figure 19 illustrates a specific example of the process when the ▽ portion of the business establishment text box is clicked. 1-1-1. Clicking the dropdown list retrieves a list of business establishment masters available as of the reference date. 1-1-2. Retrieves business establishments that exist as of the reference date. 1-1-3. Retrieves available business establishment information (code, name) from the business establishment master and displays it on the dropdown list.

[0080] "1-2: Select from the list of business names in the text box" Figure 20 illustrates a specific example of the process when a list item is selected in the business name text box. The selected value (Z001) is validated, and the name is displayed in the label.

[0081] "2-1: Click the Business Office button" Figure 21 is a diagram illustrating a specific example of the process when the business location button is clicked. 2-1-1. Clicking the business location button "..." has a function specifically for business location searches. When the business location button "..." is clicked, the business location search dialog is launched. 2-1-2. When the display button of the business location search dialog is clicked, 2-1-3. business locations that exist as of the reference date and whose names contain the string "Tokyo" are retrieved. 2-1-4. The information of the business location code selected from the business location search dialog is set in the business location text. At this point, it is assumed that the value has been changed, and a verification process is performed to check whether the business location code is valid for the selected value.

[0082] "2-2: Processing after selecting a business from the business search dialog" Figure 22 illustrates a specific example of the process after selecting a business location from the business location search dialog. The value selected in the business location search dialog (Z004) is validated, and the name is displayed as a label.

[0083] "3-1: Directly enter the value in the business name text box" Figure 23 is a diagram illustrating a specific example of processing when a value is directly entered into the business establishment text box. 3-1-1. When an application user directly enters a value into the text box, the system performs a verification process to determine if the entered value is valid for the business establishment code. The following process is described as a general master verification process. 3-1-2. Based on the argument base date and business establishment code, if data exists that matches the argument business establishment code and satisfies the conditions start date ≤ base date and base date ≤ end date, the name is returned as the return value. If the argument business establishment code matches and base date < start date (in the case of a business establishment to be established in the future), or end date < base date, the error message "Business establishment is outside its valid period" is returned as the return value. If no business establishment matches the argument business establishment code, the error message "No business establishment exists" is returned as the return value. 3-1-3. If the verification result is NG, the error content is set in the error message property of the text box. The error message property is a type of property that can be set in a text box. Unlike regular value properties, when a value is set for this error message property, an error message is displayed in the text box to notify the user of the error.

[0084] As described above, a wide range of common actions are required when application users select records from the business establishment master database. When there are many screens that search the same master database, developing and configuring each one individually presents problems in terms of cost and maintainability of quality control. As the number of master databases increases, costs will increase even further. For this reason, the present invention has developed a mechanism that allows application developers to configure the above code search function with fewer steps.

[0085] [3-3. Code search function implemented with common controls] Refer to Figures 24 to 47B to explain the code search function implemented using common controls.

[0086] (I. Development Phase) In this invention, the functional elements required for master search used across multiple screens are generalized (see "3-2. About the Code Search Function"), and the commonly required setting elements for the master search function on each screen are extracted, allowing them to be saved and used as independent definitions on the low-code development platform. In the following explanation, these definitions will be referred to as "common control definitions." This common control definition mechanism reduces the configuration burden on application developers.

[0087] (A) Registration of common control definitions Developers first configure common controls and create common control definitions. These common control definitions are stored in the common control definition management table in the development application database. The common control definition management table manages data such as the type of common control and the settings of the common control within the definition.

[0088] Figure 24 shows an example of the menu screen of a low-code development tool. Tabs are displayed on the left side of the menu screen. If you select an application, the settings screen for developing individual screens will be displayed; if you select a common control, the common control settings screen will be displayed. Here, we will configure the common controls, so click the Common Controls tab from the menu screen.

[0089] Figure 25 shows an example of the common control settings screen. By selecting the type of common control that can be configured using the tabs at the top of the screen, a list of registered common controls will be displayed. Pressing the "Create New" button will switch to the new creation mode of the common control settings screen for the selected type.

[0090] (Common control settings screen) (A-1) Setting the text box portion of the common control for code search type The common control settings screen is where you configure common controls of the code search type. For the search function that needs to be set in the text box, it is assumed that a dropdown definition like the one shown in Figure 26 has been registered in advance. A dropdown function refers to an input candidate selection function that assists the operator's input. In order to provide a dropdown function in the application, it is necessary to configure elements such as the API for retrieving records, the items to be displayed in the list, and the value to be returned to the text box when an item is selected from the list.

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

[0092] The dropdown management table includes fields for ID, dropdown name, API ID, return value (ID, name, type), and display items (ID, name, type for each item). The display items and return values ​​for the text boxes are selected from the API return values.

[0093] 1. The APIId is an ID used to retrieve information to be displayed in the dropdown menu from the API management table; select one from the API management table. 2. The API return value is the element that will be set in the text box after selecting from the dropdown list; choose one from the API return values. 3. Display items are elements to be displayed on the dropdown list, and one or more items must be selected from the API's return values. The items you want to display on the dropdown list (office code, office name) should be listed side by side.

[0094] The code search function uses text boxes, buttons, and labels, so it's necessary to configure the common elements in each of these settings. Labels don't have any common settings, so there's nothing specific to configure there.

[0095] Figure 27 shows an example of the common control settings screen (when a text box is configured) and an image of the list view. The common control settings screen includes a field for setting the name, tabs for text boxes, buttons, and labels, and an area for configuring the selected tab.

[0096] The "Name" field allows application developers to freely set a name. Depending on the type of common control selected, it is possible to configure each control that makes up the control, and the code search function allows you to configure three types of controls: text boxes, buttons, and labels.

[0097] The following information should be set in the text box. 1. Select the dropdown definition to use when retrieving the data to display in the dropdown list. Retrieve the list of dropdowns from the dropdown definition management table. The list will display the dropdown definition information retrieved from the dropdown management table.

[0098] 2. Select the API to use when verifying the business 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. Set the return value to be returned as the label value from the obtained verification API return value (for when verification is completed successfully). The list will display a list of business verification API return values ​​obtained from the API management table. 4. Set a value to be returned as a text error message within the return value of the validation API (for when validation fails). The list will display a list of return values ​​for the business validation API, retrieved from the API management table.

[0100] (A-2) Settings for the button portion of the code search type common control When configuring the button section, it is assumed that a search dialog screen is already configured in the definition management table. Furthermore, the search dialog screen used in the common control settings is assumed to have two special actions, a screen exit action, which is executed when closing its own dialog screen, one for when a value is selected and one for when it is canceled.

[0101] Figure 28 shows the records registered in the definition management table, and further displays an excerpt of information from the business search dialog screen registered in the definition management table. The definition management table has logic flows assigned to the select button and the cancel button, and a special action called a screen exit action is executed within each logic flow. When the screen exit action is executed, the logic flow processing ends and the dialog screen is closed. Processing continues on the parent screen side.

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

[0103] 2. Select the screen to display when a button is clicked. The list displays definitions retrieved from the definition management table. It retrieves a list of UI definitions by referring to the records registered in the definition management table. The dialog screen launched by clicking a button is expected to close and return to the original screen when either (1) selection or (2) cancellation is selected. To implement selection and cancellation, a special action called a screen exit action (an action that must be set when closing the screen) must be set for each. In the settings for the button part of the common control definition, the list of screen exit actions is referred to from the actions set in the dialog (business search dialog), and the action information to be called when a value is selected or canceled is stored in the definition. When the stored action information on the dialog screen side is called, the processing on the original screen side is branched (see the process of converting business search dialog argument information in (II. Conversion of common control information at the usage stage)).

[0104] 3. Select the action to be executed when a value is selected in the dialog box from the actions that are executed when the screen is closed. The list displays a list of screen closing actions retrieved from the action information in the definition management table.

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

[0106] 5. Select the value to be updated from the dialog. The list displays a list of controls from the control information within the business search dialog definition that can have values ​​set.

[0107] After configuring the text boxes and buttons and pressing the register button, the common control definitions are registered in the common control definition management table. Information such as the definition name and creation date can also be viewed 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 the registered common control definition management table.

[0108] The common control definition management table contains definition ID, definition name, common control type, and data. Definition ID: Key information automatically assigned when creating a UI definition. Definition name: Named by the developer when creating the UI definition. Common control type... The type of common control you select is determined by the type of common control you choose: code search type is 1, arbitrary search type is 2, and so on. Data... Common control settings

[0109] In this example, the definition ID is "GlobalControlKey1", the definition name is "Business Office Code Search Common Control", the common control type is "1 (Code Search)", the data is "Text Box: Dropdown Definition (ID "PullDownKey1 (Business Office Dropdown Definition)", validation process (ID "APIKey2 (Business Office Validation API)", return value (value) "KenshouAPIReturnValue1 (Business Office Name)", return value (error) "KenshouAPIReturnValue2 (Error Message)", button: type (1 (Use)), target screen (ID "AppDefinitionKey1 (Business Office Search Dialog)", when selected "SelectActionKey (Selection Process)", when canceled "CancelActionKey (Cancel Process)", return value "ZigyoushoCDCell (Business Office Code Cell)".

[0110] (B) Use common control definitions in application settings Here, we configure the application to use the common control definition (business establishment code search common control) that we registered earlier. In the following example, we will use the "business establishment code search common control" that we registered earlier in the business establishment settings section of the slip list.

[0111] Figure 32 shows an example of a definition management table. Figure 33 shows an example of a slip list screen. Common controls are placed and configured in the dotted line area of ​​the slip list screen.

[0112] Similar to regular controls, the common business code search control is placed on the document list screen. If buttons are used, three controls—a text box, a button, and a label—can be configured as a single common control. If buttons are not used, two controls—a text box and a label—can be configured as a single common control.

[0113] As shown in Figure 34, the following three properties can be specified for the common control. Figure 34 shows the settings and specifications for the common control. (1) Dropdown definition argument: FROM... Specifies the value to pass to the API argument used in the dropdown definition (business dropdown definition). (2) Pull-down definition argument: TO... Specifies the argument for the business location acquisition API to pass the value to (references the argument information for the business location acquisition API from the API management table) (3) Verification API Arguments: FROM... Specifies the values ​​to be passed as arguments to the business verification API. (4) Verification API Arguments: TO... Specifies the arguments for the business establishment verification API to which values ​​are passed (references the business establishment verification API argument information from the API management table) (5) Verification API Return Value (Optional): FROM... Specifies the return value of the business establishment verification API (refers the return value information of the business establishment verification API from the API management table), TO... Specifies the control on the screen that receives the value.

[0114] The following specifies the values ​​to pass to the dialog screen that is called when a button is clicked, but only for common definitions that use buttons (values ​​can also be passed to the dialog itself, just like with the API). (6) Search dialog arguments: FROM... Specifies the value to pass to the business search dialog. (7) Search dialog argument: TO... Specifies the destination to pass values ​​to the business search dialog.

[0115] For each property, you select the value to pass as an argument (caller) and the argument to pass the value to (callee). When a developer selects a common control placed on the screen, the system reads information from the APIs and dialogs (business location acquisition API, business location verification API, business location search dialog) that the common control references, and replaces the property title (underlined part on the screen) (for example, business location acquisition API arguments).

[0116] The above (5) is an optional item that can be set. When implementing the code search function, it is sufficient to simply return the label value and error message from the verification API, and the controls that receive these values ​​are self-evident (the common control's text and label), so there is no need to set them on this screen.

[0117] Here, the business verification API returns elements other than the label value and error message (○○ Category 1) as return values. By specifying any control on the screen to receive these values, all the necessary values ​​can be set on the screen in a single verification process. This enhances the extensibility of the code search function.

[0118] Figure 35 shows an example of the common control settings screen. When you drag and drop the business office code search common control from the common control area to the position indicated by the dashed line on the right, a screen like the one shown in Figure 36 will appear for setting the properties (common control), and you can set the properties (common control) described in (1) to (7) above.

[0119] The information for registered common controls is added as one of the control information in the definition management table, just like regular 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 in the common control definition management table. The properties of the common control (retrieval API arguments, validation API arguments, validation API return value, business search dialog arguments) are added.

[0120] In the example shown in the figure, control X has the ID "...", identification name "Business Office Code Search Common Control", control type "Code Search Common Control", common control definition ID "GlobalControlKey1", and retrieve API arguments (1: Caller (From) "Reference Date Text Box (Value)", Called (To) The API has the following parameters: Reference Date (ShutokuAPIArgs1), Validation API Arguments (1: Caller (From) "Reference Date Textbox (Value)", Called Destination (To) "Reference Date (KenshouAPIArgs1)", 2: Caller (From) "Business Office Code Search Common Control (Value)", Called Destination (To) "Business Office Code (KenshouAPIArgs2)"), Validation API Return Value (1: Caller (From) "○○ Category 1 (KenshouAPIReturnValue3)", Called Destination (To) "*Any item on the screen", Business Office Search Dialog Arguments (1: Caller (From) "Reference Date Textbox (Value)", Called Destination (To) "Reference Date Textbox (Value)".

[0121] During the development phase, (A) after registering the common control definition, application developers for each screen use the common control definition to (B) set the common control definition within their application. By reusing information commonly needed for the code search function and minimizing the information needed for each screen, the productivity and maintainability of the application can be improved.

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

[0123] (II. Conversion of common control information during the usage phase) The common control defined in (B) during the development phase, which is set in the application settings, is a special control that integrates text, buttons, and labels. As is, this common control will not function as a control in the application, so it is necessary to convert the application information through the following flowchart.

[0124] (Flowchart Processing Overview) Figure 38 is a flowchart showing how to execute the UI definition of the slip list as an application. This flowchart is executed by the execution unit 102b. This flowchart reads the information of the application to be launched and dynamically converts the definition if it contains common control information. New controls (text, buttons, labels) included in the common control definition are added, and the necessary functions to realize the code search function are generated and assigned to each control. As a result, it is converted into application information that can be used in the end.

[0125] The business application database contains definition management tables, common control definition management tables, and pull-down definition management tables.

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

[0127] If the control information includes a common control of the code search type ("Yes" in step S3), then: 1. Add three controls to the control information: a text box, a button, and a label (step S4). 2. Convert the property references of the common control of the code search type to regular controls (step S5). 3. Combine the retrieved API argument information and the common control definition and convert it into the dropdown information for the text box (step S6). 4. Convert the validation API argument information and validation API return value information into logic flow information and action information (step S7). 5. Link the logic flow created in step 4 to the event of the text box (step S8).

[0128] Next, the execution unit 102b determines whether or not it is a common control definition for settings that use buttons (step S9). If it is not a common control definition for settings that use buttons (No in step S9), the program proceeds to step S13.

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

[0130] In step S13, the process of launching the voucher list is performed according to the UI definition of the converted voucher list (step S13).

[0131] Next, the processes 1 to 9 in the flowchart above will be explained with reference to Figures 39 to 46. (1. Add the regular controls corresponding to the common controls to the control information.) In Figure 39, if a code search type uses buttons, the following controls are added to the definition management table: a text box, a button, and a label. If a code search type does not use buttons, the following controls are added: a text box and a label.

[0132] In the control information of the definition management table, the common control is set as control X. Controls X1, X2, and X3 for text, buttons, and labels, respectively, corresponding to this control X, are added in the usual control format (ID, identifier name, control type).

[0133] (2. Convert the property references of the common control in the code search to regular controls.) In the low-code development tool settings, it was set as the value of a common control (common control for business office code search), but when used as an application, it is the element corresponding to the value of the text box, so the conversion is performed when the regular control is added in step 1. In the example shown in Figure 39, "common control for business office code search (value)" is converted to "business office text box (value)".

[0134] (3. Combine the retrieved API argument information and common control definitions to convert them into dropdown information for the text box.) Figure 40 shows examples of a common control definition management table and a pull-down definition management table, while Figures 41 and 42 show examples of definition management tables.

[0135] The information (APIId, return value, display items) from the "PullDownKey1" dropdown definition in the common control definition management table is retrieved, and the calling control and the called API arguments are identified from the retrieved API argument information in the definition management table.

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

[0137] The API argument information is retrieved from the definition management table (see Figure 41). In other words, the common control information defined in the UI is retrieved.

[0138] Based on the API ID, return value, and display items obtained from the dropdown definition management table, and the retrieved API arguments obtained from the definition management table, the dropdown setting information (ID, API identifier, arguments, return value, display items) required for the text box (to link with the text box) is generated, and the dropdown setting information and dropdown relation information (control ID, dropdown ID) are added to the definition management table as shown in Figure 42. The dropdown relation information is information that links the dropdown to the control, and it plays the role of linking the control ID and the dropdown 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 boxes.) The validation API arguments and validation API return values ​​from the definition management table in the upper left of Figure 43 (an excerpt showing the settings for the validation API arguments and return value properties of 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, based on the information of the validation API arguments, a logic flow as shown in the lower left of Figure 43 is generated internally and added as a new logic flow element and action element in the UI definition. Furthermore, when converting to action information, the validation process information from 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 elements is always a label for the business name and always a text error message.

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

[0142] For common control definitions that use buttons, perform the following conversion. (6. Convert the argument information of the business search dialog into logic flow and action information.) The system automatically creates a logic flow that separates processing for selection and cancellation on the dialog box. In Figure 45, the business search dialog arguments in the definition management table (excerpt of the setting part of the dialog arguments for common controls) and the common control definition management table are shown. Based on the information from the buttons in the common control for searching business office codes, a logic flow like the one shown in the lower left of Figure 45 is generated internally. Based on the generated logic flow, logic flow information and action information are generated and added to the definition management table.

[0143] The button information in the common control definition is set to "SelectActionKey(Selection Process)" when selected, so when a selection process is performed on the business search dialog side, the process proceeds to the selection flow. When canceled, it is set to "CancelActionKey(Cancellation Process)", so when a cancellation process is performed on the business search dialog side, the process proceeds to the cancellation flow.

[0144] Let me add some details about logic flow branching. Flow elements 2 and 3 are special flows that, when the previous action ID is set to a screen launch action, branch the subsequent processing according to the screen end action processing on the child screen launched by the screen launch action.

[0145] In the common control definition, the screen exit action when a value is selected in the dialog and the screen exit action when the dialog is canceled are registered, so the subsequent processing is branched according to each of these actions.

[0146] For information on the screen exit action set on the dialog side, please refer to the description in "(A-2) Settings for the button portion of the code search type common control". In this example, since the buttons in the common control definition have processing for when a value is selected and when it is canceled, 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 side is called. When the cancellation process (CancelActionKey) is executed, the process branches to flow element 3, and the exit action on the parent screen side is called.

[0147] For buttons in the common control definition, the selection action key is set to "SelectActionKey(Selection Process)" when selected, so when a selection is made in the business search dialog, the process proceeds to the selection flow. For cancellation, the action key is set to "CancelActionKey(Cancellation Process)" so when a cancellation is made in the business search dialog, the process proceeds to the cancellation flow.

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

[0149] (8. Remove common controls from control information) Remove the common control from the control information in the definition management table. Figures 47A and 47B show an example of the definition management table with the common control removed from the control information. With control X (the common control portion) removed, only the text, button, and label portions remain in the control information.

[0150] As a result, the definition of the document list, which previously used common controls, has been converted to a standard definition using regular text boxes, buttons, and labels, allowing it to be used as a regular definition. Performing this conversion internally reduces the workload on developers, as they do not need to assign logic flows and action settings to each control such as text boxes using low-code development tools. Performing the conversion by interpreting the registered information at runtime, rather than when the common controls are placed, means that changes to the common control definition are reflected in real time at runtime, resulting in high maintainability. The above explanation described the case when using the code search type of common controls, but the same conversion process can be performed when using different types of common controls (different combinations of controls and processing content) to achieve the processing required by the application.

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

[0152] Figure 52 shows a flowchart of the case where the UI definition of a business application executed by the execution unit 102b is executed as an application. Figure 52 shows a flowchart of the higher-level concept of the flowchart in Figure 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 Figure 52, when an application user launches a business application (step S21), the application information for the business application is read from the definition management table (step S22). It is determined whether the control information includes a common control of the search type (for example, a code search type) (step S23). If the control information does not include a common control of the code search type (No in step S23), the process proceeds to step S30.

[0154] If the control information includes a common control of the search type ("Yes" in step S23), 1. Add at least two common control values ​​to the control information: a value specification area (e.g., a text box) and a dialog display button. 3. Combine the pull-down display command argument information (e.g., acquisition API argument information) with the common control definition and convert it into pull-down information for the value specification area (step S25). Determine whether the common control definition is set to use the dialog display button (step S26). If it is not a common control definition set to use the dialog display button ("No" in step S26), proceed to step S30.

[0155] If the setting is a common control definition that uses the dialog display button (Yes in step S26), then 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 step 6 to the event of the dialog display button (step S28). 8. Remove the common control from the control information (step S29).

[0156] In step S30, the startup process for the business application is performed according to the UI definition of the converted business application.

[0157] As described above, according to this embodiment, a definition management table is registered that associates a definition ID, a definition name, control information defining the ID, identification name, and control type for each control, logic flow information defining the ID, previous action ID, and next action ID for each element of the logic flow, and action information defining the ID, name, type, API, arguments, and return value for each action element. A common control definition management table is registered that associates a common control definition common to multiple business applications, with the definition ID, definition name, common control type, and setting details associated. When a user sends a command to start a business application, the application information of the business application is read from the definition management table, and if the control information in the definition management table includes a common control of the search type, the control information includes the value specification area and dialog box for the common control. The system includes an execution unit 102b that adds a control containing at least two 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 the value selection area, converts the dialog display command argument information into logic flow information and action information if the common control definition is set to use a dialog display button, links the created logic flow information to the event of the dialog display button, removes the common control from the control information, and performs startup processing of the business application according to the converted UI definition of the business application. By providing a mechanism to pattern frequently used application functions and save reusable settings for each pattern as independent common control definitions, it becomes possible to provide users with business applications that reduce the man-hours required for settings and prevent malfunctions due to incorrect settings.

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

[0159] Furthermore, this embodiment can contribute to reducing waste and promoting paperless and digital processes, thereby contributing to SDGs Goals 12, 13, and 15.

[0160] Furthermore, this embodiment can contribute to strengthening control and governance, thereby enabling contributions to SDG Goal 16.

[0161] [5. Other Embodiments] In addition to the embodiments described above, the present invention may be implemented in various different embodiments within the scope of the technical idea described 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 by known methods.

[0163] Furthermore, the processing procedures, control procedures, specific names, information including parameters such as registration data and search conditions for each process, screen examples, and database configuration shown in this specification and in the drawings may be changed at will unless otherwise specified.

[0164] Furthermore, with respect to the application provisioning system 100, each component shown in the diagram is a functional concept and does not necessarily need to be physically configured as shown.

[0165] For example, the processing functions of the application provisioning system 100, particularly those performed by the control unit 102, may be implemented in whole or in part by a CPU and a program interpreted and executed by the CPU, or they may be implemented as wired logic hardware. The program is recorded on a non-temporary computer-readable recording medium containing programmed instructions for causing the information processing device to execute the processing described in this embodiment, and is mechanically read by the application provisioning system 100 as needed. That is, a storage unit such as ROM or HDD (Hard Disk Drive) records a computer program that works in cooperation with the OS to give instructions to the CPU and perform various processing tasks. This computer program is executed by being loaded into RAM and works in cooperation with the CPU to constitute the control unit.

[0166] Furthermore, this computer program may be stored on an application program server connected to the application provisioning system 100 via any network, and it is possible to download all or part of it as needed.

[0167] Furthermore, the program for executing the processing described in this embodiment may be stored on a non-temporary computer-readable recording medium, or it may be configured as a program product. Here, "recording medium" includes any "portable physical medium" such as memory cards, USB (Universal Serial Bus) memory, SD (Secure Digital) cards, flexible disks, magneto-optical disks, ROMs, EPROMs (Erasable Programmable Read Only Memory), EEPROMs (Registered Trademark) (Electrically Erasable and Programmable Read Only Memory), CD-ROMs (Compact Disk Read Only Memory), MOs (Magneto-Optical disks), DVDs (Digital Versatile Disks), and Blu-ray (Registered Trademark) Discs.

[0168] Furthermore, "program" refers to a data processing method described in any language or writing method, regardless of its format, such as source code or binary code. Note that "program" is not necessarily limited to a single, monolithic structure; it also includes distributed structures consisting of multiple modules or libraries, and those that work in cooperation with other programs, such as an operating system, to achieve their functions. Regarding the specific configuration and reading procedures for reading the recording medium in each device shown in this embodiment, as well as the installation procedures after reading, well-known configurations and procedures can be used.

[0169] The various databases stored in the memory unit 106 include memory devices such as RAM and ROM, fixed disk devices such as hard disks, flexible disks, and optical disks, and store various programs, tables, databases, and web page files used for various processes and website provision.

[0170] Furthermore, the application provisioning system 100 may be configured as a known personal computer or workstation or other information processing device, or as an information processing device to which any peripheral devices are connected. Alternatively, the application provisioning system 100 may be implemented by installing software (including programs or data, etc.) on the device that enables the processing described in this embodiment.

[0171] Furthermore, the specific forms of distribution and integration of the devices are not limited to those shown in the figures, and all or part of them can be configured by functionally or physically distributing and integrating them in any unit according to various additions or functional loads. In other words, the embodiments described above may be implemented in any combination, or the embodiments may be implemented selectively. [Explanation of Symbols]

[0172] 100 Application Delivery Systems 102 Control Unit 102a Setting section 102b Execution Unit 104 Communication Interface Section 106 Storage section 106a Development application database 106b Business Application Database 108 Input / Output Interface Section 112 Input device 114 Output device 200 servers 300 Networks

Claims

1. An application provisioning system equipped with a control unit and configured to communicate data with developer and user clients, The control unit, A definition management table is registered by associating the definition ID, definition name, control information which defines the ID, identifier name, and control type for each control, logic flow information which defines the ID, previous action ID, and next action ID for each element of the logic flow, and action information which defines the ID, name, type, API, arguments, and return value for each action element. This defines common control definitions that are shared across multiple business applications, and registers them in a common control definition management table, associating definition ID, definition name, common control type, and settings. It is configured to be able to access the database that stores it, The system is equipped with an execution mechanism that launches a business application upon receiving a startup command from a user. The aforementioned execution means is When a user requests the launch of a business application, the application information of the business application is read from the definition management table. If the control information in the definition management table includes a common control of the search type, add a control to the control information that includes at least two common control values ​​and a dialog display button. The pull-down display command argument information of the aforementioned common control and the common control definition are combined and converted into pull-down information for 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 event of the dialog display button. The common control is removed from the control information, An application provisioning system characterized by performing the startup process of a business application according to the UI definition of the converted business application.

2. If the search type is a code search type, the execution means further: Convert the property references of common controls in code search type controls to regular controls. The validation API argument information and validation API return value information of the aforementioned common control are converted into logic flow information and action information. The application provision system according to claim 1, characterized in that it associates the created logic flow information with the events of a text box.

3. The control unit, The application provision system according to claim 1, characterized in that it includes a setting means for creating the common control definition management table in response to the developer's operations on the common control settings screen.

4. The application provision system according to claim 3, characterized in that the setting means adds common controls from the common control definition management table to the control information of the definition management table in accordance with the developer's operation on the business application creation screen.

5. The application provision system according to any one of claims 1 to 4, characterized in that the application provision system is composed of a low-code platform or a no-code platform.

6. An application provision method executed by an information processing device equipped with a control unit and configured to communicate data with developer and user clients, The control unit, A definition management table is registered by associating the definition ID, definition name, control information which defines the ID, identifier name, and control type for each control, logic flow information which defines the ID, previous action ID, and next action ID for each element of the logic flow, and action information which defines the ID, name, type, API, arguments, and return value for each action element. This defines common control definitions that are shared across multiple business applications, and registers them in a common control definition management table, associating definition ID, definition name, common control type, and settings. It is configured to be able to access the database that stores it, The control unit is executed as follows: Upon receiving a startup command from the user, the system includes an execution step that starts the business application. In the execution step described above, When a user requests the launch of a business application, the application information of the business application is read from the definition management table. If the control information in the definition management table includes a common control of the search type, add a control to the control information that includes at least two common control values ​​and a dialog display button. The pull-down display command argument information of the aforementioned common control and the common control definition are combined and converted into pull-down information for 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 event of the dialog display button. The common control is removed from the control information, An application provision method characterized by performing a startup process for a business application according to the UI definition of the converted business application.

7. An application provision program for an information processing device, which includes a control unit and is configured to communicate data with user and developer clients, to be executed by the device, The control unit, A definition management table is registered by associating the definition ID, definition name, control information which defines the ID, identifier name, and control type for each control, logic flow information which defines the ID, previous action ID, and next action ID for each element of the logic flow, and action information which defines the ID, name, type, API, arguments, and return value for each action element. This defines common control definitions that are shared across multiple business applications, and registers them in a common control definition management table, associating definition ID, definition name, common control type, and settings. It is configured to be able to access the database that stores it, In the control unit, This is an application provider program that, upon receiving a startup command from a user, executes an execution step to start a business application. In the execution step described above, When a user requests the launch of a business application, the application information of the business application is read from the definition management table. If the control information in the definition management table includes a common control of the search type, add a control to the control information that includes at least two common control values ​​and a dialog display button. The pull-down display command argument information of the aforementioned common control and the common control definition are combined and converted into pull-down information for 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 event of the dialog display button. The common control is removed from the control information, An application provider program characterized by performing a startup process for a business application according to the UI definition of the converted business application.

Images