Parameter management method and apparatus, electronic device, and storage medium
By generating parameter fields and configuring parameter views, the problem of large development workload and long development cycle when adding new parameter data in the cloud platform system is solved, realizing the sharing of parameter information and user convenience.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- CHINA CONSTRUCTION BANK
- Filing Date
- 2022-09-16
- Publication Date
- 2026-06-09
AI Technical Summary
When adding new parameter data to a cloud platform system, existing technologies require developers to redevelop external interfaces, resulting in a large workload, long timeframe, and inconvenience for users.
By receiving business scenario requirements from clients, generating parameter fields, and configuring parameter views based on parameter models, parameter information sharing between subsystems is achieved, supporting users to design parameter models and views online, and providing a unified parameter interface.
It reduces the workload of developers, shortens the production time, and improves user convenience and system collaborative development efficiency.
Smart Images
Figure CN115438113B_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of platform development technology, and in particular to a parameter management method, apparatus, electronic device and storage medium. Background Technology
[0002] Parameters are ubiquitous in various cloud platform systems. During operation, cloud platform systems can read relevant parameters according to the characteristics and processing requirements of various businesses. Different combinations of parameters can guide and control the business processing flow.
[0003] Existing technologies allow for the development of a parameter management system, such as a Configuration Management Database (CMDB), based on the parameters required by each system. This system provides query interfaces and removable files. When other systems need to access parameter data, they can use the query interfaces provided by the CMDB or load the data from the files to update the parameter data for use in other systems.
[0004] However, after adding certain types of parameter data, the above method requires developers to redevelop the external interface for other systems to call the parameters, which increases the workload of developers and takes a long time from development to production use, making it inconvenient for users. Summary of the Invention
[0005] This application provides a parameter management method, device, electronic device, and storage medium, which can realize parameter information sharing between subsystems based on parameter models, reduce the development workload of developers when adding new parameters to the system, and support users to design parameter models and configure parameter views online, thereby improving convenience.
[0006] Firstly, this application provides a parameter management method applied to a cloud platform system, wherein the cloud platform system includes multiple subsystems that share a common external interface and achieve parameter sharing based on parameter fields; the method includes:
[0007] Receive business scenario requirements sent by the client, and generate at least one parameter field based on the business scenario requirements;
[0008] In response to a user's touch operation selecting the parameter field, a parameter model that meets the user's needs is generated; the parameter model is used to define the structure of the parameter field.
[0009] The parameter view is configured based on the parameter model and then visualized. The parameter view displays the callable parameter fields and the display rules of the parameter model, so that the client can call the parameters of any subsystem in the cloud platform system based on the external interface.
[0010] Optionally, at least one parameter field is generated based on the business scenario requirements, including:
[0011] Based on the business scenario requirements, the corresponding fixed parameter fields are searched from the predefined parameter library; the fixed parameter fields include: parameter identification number ID, client name, parameter modification record, and the name of the subsystem where the parameter is located;
[0012] In response to a user's search operation, the system searches for newly added custom parameter fields in the predefined parameter library and generates at least one parameter field based on the fixed parameter fields and the custom parameter fields.
[0013] Optionally, the method further includes:
[0014] After generating a parameter model that meets user requirements, the index entry of the parameter model is retrieved from the index table based on the type of the parameter model; the index entry is used to find a subsystem that meets the requirements of the business scenario.
[0015] In response to a user's touch operation to select an index item, an index page that meets the user's needs is generated, which allows the client to search for any subsystem in the cloud platform system.
[0016] Optionally, a parameter view is configured based on the parameter model, including:
[0017] Obtain the data source and database of the cloud platform system. The data source is used to store the data corresponding to the parameters in the subsystem, and the database is used to store the relationship between the data and the subsystem.
[0018] Determine the correspondence between the parameter fields corresponding to the parameter model and the database, and configure a parameter view based on the correspondence and the data source so that data in the data source can be called based on the parameter model in the parameter view.
[0019] Optionally, the parameter view can be visualized, including:
[0020] Based on the type of the parameter model, the corresponding display rules are obtained from a predefined rule base; the display rules include field sorting rules, field layout rules, and field design rules;
[0021] Determine whether the display rules meet user needs;
[0022] If so, the parameter view is visualized using the defined display rules;
[0023] If not, then in response to the user's operation of creating display rules, a display rule that meets the user's needs is generated, and the predefined rule library is updated based on the type and the created display rule.
[0024] Optionally, the method further includes:
[0025] Obtain user input parameters and target behaviors, including query behavior, add behavior, delete behavior and modify behavior;
[0026] Based on the target behavior, the corresponding execution code is invoked, and a behavior instruction is generated based on the parameters and the execution code;
[0027] The behavior command is used to call the external interface to obtain the corresponding data from the subsystem for processing; the external interface is based on the parameter view definition.
[0028] Optionally, the behavior instruction can be used to call an external interface to obtain corresponding data from the subsystem for processing, including:
[0029] The behavioral instructions are parsed to obtain the quantity of the required data.
[0030] Determine whether the quantity is greater than a preset threshold;
[0031] If not, the corresponding data is retrieved from the subsystem and processed by sequentially calling the external interface in a synchronous manner;
[0032] If so, the corresponding data will be retrieved from the subsystem and processed by asynchronously calling the external interface.
[0033] Secondly, this application provides a parameter management device applied to a cloud platform system, the cloud platform system comprising multiple subsystems sharing a common external interface and achieving parameter sharing based on parameter fields; the device includes:
[0034] The receiving module is used to receive business scenario requirements sent by the client and generate at least one parameter field based on the business scenario requirements;
[0035] A generation module is used to generate a parameter model that meets the user's requirements in response to the user's touch operation of selecting the parameter field; the parameter model is used to define the structure of the parameter field.
[0036] The configuration module is used to configure a parameter view based on the parameter model and to visualize the parameter view. The parameter view displays the callable parameter fields and the display rules of the parameter model, so that the client can call the parameters of any subsystem in the cloud platform system based on the external interface.
[0037] Thirdly, this application provides an electronic device, including: a processor, and a memory communicatively connected to the processor;
[0038] The memory stores computer-executed instructions;
[0039] The processor executes computer execution instructions stored in the memory to implement the method as described in any one of the first aspects.
[0040] Fourthly, this application provides a computer-readable storage medium storing computer-executable instructions that, when executed by a processor, are used to implement the method as described in any one of the first aspects.
[0041] Fifthly, this application provides a computer program product, including program code, which, when a computer runs the computer program, performs the method as described in any one of the first aspects.
[0042] In summary, this application provides a parameter management method, apparatus, electronic device, and storage medium. It can receive business scenario requirements sent by a client and generate at least one parameter field based on those requirements. Furthermore, in response to a user's touch operation selecting a parameter field, it generates a parameter model that meets the user's needs. This parameter model defines the structure of the parameter fields. Then, it configures a parameter view based on the parameter model and displays the parameter view visually, showing the callable parameter fields and the display rules of the parameter model. This allows the client to call parameters from any subsystem within the cloud platform system via an external interface. This enables parameter information sharing between subsystems based on the parameter model, reducing the development workload for developers when adding parameters to the cloud platform system. It also supports users designing parameter models and configuring parameter views online, improving user convenience. Attached Figure Description
[0043] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.
[0044] Figure 1 This is a schematic diagram of an application scenario provided by an embodiment of this application;
[0045] Figure 2 A flowchart illustrating a parameter management method provided in an embodiment of this application;
[0046] Figure 3 A schematic diagram of an interface for displaying parameter fields provided in an embodiment of this application;
[0047] Figure 4 A schematic diagram of an index page provided in an embodiment of this application;
[0048] Figure 5This application provides a schematic diagram of the structure of a data source and a database according to an embodiment of the present application.
[0049] Figure 6 A schematic diagram of a view design provided for an embodiment of this application;
[0050] Figure 7 This is a schematic diagram of a data query structure provided in an embodiment of this application;
[0051] Figure 8 This is a schematic diagram of the structure of a parameter management device provided in an embodiment of this application;
[0052] Figure 9 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application.
[0053] The accompanying drawings illustrate specific embodiments of this application, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concept of this application to those skilled in the art through reference to particular embodiments. Detailed Implementation
[0054] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.
[0055] To facilitate a clear description of the technical solutions in the embodiments of this application, the terms "first" and "second" are used in the embodiments of this application to distinguish identical or similar items with essentially the same function and purpose. For example, "first device" and "second device" are merely used to distinguish different devices and do not limit their order of execution. Those skilled in the art will understand that the terms "first" and "second" do not limit the quantity or execution order, and that "first" and "second" do not necessarily imply that they are different.
[0056] It should be noted that, in this application, the terms "exemplary" or "for example" are used to indicate that something is being described as an example, illustration, or illustration. Any embodiment or design described as "exemplary" or "for example" in this application should not be construed as being more preferred or advantageous than other embodiments or design solutions. Specifically, the use of terms such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner.
[0057] In this application, "at least one" means one or more, and "more than one" means two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can mean: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can mean: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple.
[0058] The following is an explanation of the technical terms used in the application:
[0059] System parameters refer to variables related to system state, function, and behavior. In computer science, a variable can refer to a name that represents a value existing in memory, while system parameters are generally dynamic and change depending on the system's current needs.
[0060] Physical subsystem: refers to the multiple subsystems into which the cloud platform system is decomposed. In the analysis phase, the subsystem can be called a conceptual subsystem; in the design and development phase, the subsystem can be called a logical subsystem; and in the deployment and operation phase, the subsystem can be called a physical subsystem.
[0061] Parameter entity: refers to a data element in the parameter management system.
[0062] Parametric model: refers to the abstract representation of the characteristics of a parameter entity, describing the structure and storage method of the parameter entity in the database. A physical subsystem is equivalent to a parametric model.
[0063] Parameter view: refers to the view used to describe how parameter entities are organized in the parameter management system, and defines the presentation of parameter entities in the system.
[0064] Parameter interface: refers to some predefined functions that define how external systems access or manipulate parameter entities without needing to access the source code.
[0065] In cloud platform systems, there are often problems such as inconsistent parameter data sources, redundant design and development of parameter management, lack of unified standards, and significant differences in parameter quality. Taking the physical subsystem as an example, the project management subsystem, code management subsystem, and production management subsystem all use system parameters. However, the project management subsystem, code management subsystem, and production management subsystem are three independent subsystems. Data is stored in each subsystem through manual entry or acquisition from third parties. The data sources and update frequencies are usually inconsistent. Moreover, when each subsystem acquires and stores system parameters, the parameter field names and types used are usually inconsistent, requiring developers to perform additional development work. When the three systems collaborate on development or use the physical subsystem as an associated attribute for interaction, data inconsistencies may occur.
[0066] One possible implementation is to develop a parameter management system, such as a CMDB system, based on the parameters required by each subsystem. This system would provide query interfaces and unloadable files. When other systems need to access parameter data, they can use the query interfaces provided by the CMDB or load the data from the files to update the parameter data for use in other systems.
[0067] While the above methods address the issues of inconsistent data sources and parameter quality to some extent, they also require developers to redevelop external interfaces for other systems to call parameters after adding certain types of parameter data, increasing the workload of developers and resulting in a long time cycle from development completion to production use, which is inconvenient for users.
[0068] To address the aforementioned issues, this application provides a parameter management method that allows users to select parameter fields, i.e., customize the parameter fields included in the parameter model, enabling the cloud platform system to automatically generate a parameter model. The cloud platform system then uses the generated parameter model to create a parameter view. Users can then directly access parameters from subsystems by manipulating this parameter view. The cloud platform system comprises multiple subsystems that share a single parameter interface and achieve parameter sharing based on parameter fields. This application reduces the workload for developers when adding new parameter models to the system, supports online parameter model design and parameter view configuration, provides a unified parameter interface, enables parameter information sharing between subsystems, and improves the efficiency of collaborative development between subsystems.
[0069] For example, Figure 1 This is a schematic diagram illustrating an application scenario provided by an embodiment of this application. The parameter management method provided in this application can be applied to, for example... Figure 1The application scenario shown includes: terminal device 101, cloud platform system 102, and display device 103; wherein, cloud platform system 102 includes multiple subsystems, such as first subsystem 1021, second subsystem 1022, and third subsystem 1023; specifically, taking first subsystem 1021 as a project management subsystem, second subsystem 1022 as a code management subsystem, and third subsystem 1023 as a production management subsystem as an example, although these three subsystems are three independent subsystems, they share a single parameter interface, enabling parameter information sharing between subsystems. Furthermore, cloud platform system 102, upon receiving... After the terminal device 101 sends the business scenario requirements, it generates multiple parameter fields. The user operates the terminal device 101 to select the required parameter fields. Then, the cloud platform system 102 can customize and generate parameter models and dynamically generate parameter interfaces. Furthermore, the cloud platform system 102 dynamically generates parameter views by customizing the attributes, sorting fields, sorting rules, and other display rules corresponding to the parameter models. These views are then displayed on the corresponding display device 103 of the cloud platform system 102, allowing the terminal device 101 to use the parameter interface to call parameters from any of the first subsystem 1021, the second subsystem 1022, and the third subsystem 1023.
[0070] It should be noted that the generated parameter view can also be displayed on the terminal device 101 with a display screen. This application embodiment does not specifically limit this, and this application embodiment does not specifically limit the number of subsystems included in the cloud platform system or the custom generated parameter model. The above are just examples.
[0071] The technical solutions of this application will be described in detail below with reference to specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of this application will be described below with reference to the accompanying drawings.
[0072] Figure 2 This is a flowchart illustrating a parameter management method provided in an embodiment of this application, applied to a cloud platform system. The cloud platform system includes multiple subsystems that share a common external interface and achieve parameter sharing based on parameter fields, such as... Figure 2 As shown, the parameter management method includes the following steps:
[0073] S201. Receive the business scenario requirements sent by the client, and generate at least one parameter field based on the business scenario requirements.
[0074] In this embodiment, the parameter field can refer to the parameter entity that is formatted in the cloud platform system. Each parameter field has attributes such as parameter type, whether it is a primary key, whether it is a symbol, whether it has a default value, and whether it is deleted, which can be selected by the user. For example, the parameter field Identity Document (ID) can have the following attributes after selection: parameter type is NUMBER (10), primary key, unsigned, etc. This embodiment does not specifically limit the category and number of operable attributes carried by each parameter field. The above is just an example.
[0075] In this step, after receiving the business scenario requirements sent by the client, the business scenario requirements are analyzed to obtain parameter requirements. Based on the parameter requirements, multiple parameter fields are generated, such as parameter field ID, client name, and the time when the parameter field is generated. The parameter fields are used to call the parameter data corresponding to the parameter field. For example, if the parameter field is student ID, then the student IDs corresponding to all students in a certain subsystem can be called based on the parameter field.
[0076] S202. In response to the user's touch operation of selecting the parameter field, a parameter model that meets the user's needs is generated; the parameter model is used to define the structure of the parameter field.
[0077] In this step, in response to the user's touch operation of selecting parameter fields, modeling is performed using the selected parameter fields to generate a parameter model that meets the user's needs. That is, the parameter fields are used to define the structure of the parameter model. When designing the parameter model, the user can also select preset reserved fields to standardize the quality of the parameter model. The preset reserved fields can be designed by the user. This application embodiment does not specifically limit this.
[0078] S203. Configure a parameter view based on the parameter model and visualize the parameter view. The parameter view displays the callable parameter fields and the display rules of the parameter model, so that the client can call the parameters of any subsystem in the cloud platform system based on the external interface.
[0079] In this embodiment, the external interface refers to a unified parameter interface provided to facilitate data access by other subsystems. The external interface can be used to call parameter entities in a subsystem or to call parameter data in various subsystems. All subsystems in the cloud platform share a single external interface, i.e., a function is defined and its execution program is written in advance. When using it, only the parameter field values of the function need to be modified. The parameter field values may include service name, interface name, parameter field name, input parameter value, and output parameter value, etc. This embodiment does not specifically limit this.
[0080] In this step, when configuring the parameter view based on the parameter model, the relationships between parameter models can also be defined. Furthermore, the parameter view is configured online according to the parameter model and the relationships between them. The system dynamically generates the display view and provides a unified Application Programming Interface (API) or Remote Procedure Call (RPC) interface for each subsystem, allowing clients to call parameters from any subsystem in the cloud platform system based on the interface. The parameter view displays the callable parameter fields, the display rules of the parameter models, etc. The display rules include sorting rules, layout rules, and design rules for the parameter fields, etc., which are not specifically limited in this embodiment.
[0081] Therefore, this application provides a parameter management method that can receive business scenario requirements sent by a client and generate at least one parameter field based on those requirements. Furthermore, in response to a user's touch operation selecting a parameter field, a parameter model conforming to the user's requirements is generated. This parameter model defines the structure of the parameter fields. A parameter view is then configured based on the parameter model and displayed visually, showing the callable parameter fields and the display rules of the parameter model. This allows the client to call parameters from any subsystem within the cloud platform system via an external interface. This enables parameter information sharing between subsystems based on the parameter model, reducing the development workload for developers when adding parameters to the cloud platform system. It also supports users designing parameter models and configuring parameter views online, improving user convenience.
[0082] Optionally, at least one parameter field is generated based on the business scenario requirements, including:
[0083] Based on the business scenario requirements, the corresponding fixed parameter fields are searched from the predefined parameter library; the fixed parameter fields include: parameter identification number ID, client name, parameter modification record, and the name of the subsystem where the parameter is located;
[0084] In response to a user's search operation, the system searches for newly added custom parameter fields in the predefined parameter library and generates at least one parameter field based on the fixed parameter fields and the custom parameter fields.
[0085] In this embodiment, a predefined parameter library is used to store parameter fields under different business scenarios. Each business scenario corresponds to a certain number and type of parameter fields. The parameter fields include fixed parameter fields and custom parameter fields. The fixed parameter fields are parameter fields that cannot be deleted and are required in each business scenario, such as parameter ID, client name (creator), parameter creation time, parameter modification record (modifier and modification time), and the name of the subsystem where the parameter is located. The custom parameter fields are parameter fields that users can add, such as the abbreviation of the subsystem where the parameter is located. This embodiment does not specifically limit the custom parameter fields, which can be determined according to the specific situation.
[0086] For example, Figure 3 This application provides a schematic diagram of an interface for displaying parameter fields; as shown in the embodiment of the present application. Figure 3 As shown, the parameter field page of the design parameter model includes the design of the name and description, to... Figure 3 As shown in the example, the interface includes the design of parameter ID, creator, parameter creation time, modifier, parameter modification time, name of the subsystem where the parameter is located, and abbreviation of the subsystem where the parameter is located. Each parameter field has corresponding optional attributes, including the parameter field name, parameter type, primary key, NOT NULL, symbol, default value, operation, etc., for users to select. Correspondingly, in response to the user's search operation, parameter fields can also be added based on this interface, thereby generating parameter fields that meet the requirements of the business scenario.
[0087] Therefore, in this embodiment of the application, users can also customize the online design selection parameter fields, which improves flexibility and reduces the workload of developers.
[0088] Optionally, the method further includes:
[0089] After generating a parameter model that meets user requirements, the index entry of the parameter model is retrieved from the index table based on the type of the parameter model; the index entry is used to find a subsystem that meets the requirements of the business scenario.
[0090] In response to a user's touch operation to select an index item, an index page that meets the user's needs is generated, which allows the client to search for any subsystem in the cloud platform system.
[0091] In this embodiment of the application, the index table is used to store index items of the parameter model. Each type of parameter model corresponds to one index item. The index item is used to quickly query the subsystem corresponding to the parameter model. Each index item can correspond to an index name, index type, and operable options for the user to select.
[0092] For example, Figure 4This is a schematic diagram of an index page provided in an embodiment of this application, such as... Figure 4 As shown, the design of the index page includes the design of the names and descriptions, in order to... Figure 4 As shown in the example, the interface includes the design of index name, index type and operable options. Correspondingly, in response to the user's touch operation of selecting an index item and the operation of adding an index item, the interface generates an index page that meets the user's needs, which is used by the client to find any subsystem in the cloud platform system.
[0093] Therefore, embodiments of this application can also be designed to search for any subsystem in the cloud platform system using index items, thereby improving query speed.
[0094] Optionally, a parameter view is configured based on the parameter model, including:
[0095] Obtain the data source and database of the cloud platform system. The data source is used to store the data corresponding to the parameters in the subsystem, and the database is used to store the relationship between the data and the subsystem.
[0096] Determine the correspondence between the parameter fields corresponding to the parameter model and the database, and configure a parameter view based on the correspondence and the data source so that data in the data source can be called based on the parameter model in the parameter view.
[0097] In this step, the correspondence between the parameter fields corresponding to the parameter model and the database is determined, that is, the correspondence between where the stored data is stored. Further, a parameter view is configured based on the correspondence and the data source. That is, operations are performed in the parameter view. Based on the correspondence recorded in the database, data can be searched in the data source. The data source stores the data corresponding to the parameters in the subsystem. Each piece of data corresponds to a parameter field of what type. For example, if the parameter field is student ID, it corresponds to the ID numbers ID1-ID20 of all students in the subsystem.
[0098] For example, Figure 5 This is a schematic diagram of the structure of a data source and database provided in an embodiment of this application, such as... Figure 5As shown, the data source and database include parameter fields used to implement parameter and parameter data calls. When creating a tenant's parameter model, the data source and database models need to be designed. The parameter fields corresponding to the tenant are id and name, i.e., primary key ID and tenant name. The parameter fields corresponding to the data source model (physical database sharding) are id, name, description, url, ip, port, username, password, and tenant_id, which correspond to primary key ID, tenant name, description, data source Uniform Resource Locator (URL), Internet Protocol (IP) address, interface, username, password, and tenant ID, respectively. The parameter fields corresponding to the database model are id, name, datasource_id, and tenant_id, which correspond to primary key ID, tenant name, data source, and tenant ID, respectively.
[0099] Therefore, the embodiments of this application can standardize the parameter fields in the underlying cloud platform system, configure parameter views corresponding to the parameter fields of the user-selected parameter model, and improve the data quality of parameter entities.
[0100] Optionally, the parameter view can be visualized, including:
[0101] Based on the type of the parameter model, the corresponding display rules are obtained from a predefined rule base; the display rules include field sorting rules, field layout rules, and field design rules;
[0102] Determine whether the display rules meet user needs;
[0103] If so, the parameter view is visualized using the defined display rules;
[0104] If not, then in response to the user's operation of creating display rules, a display rule that meets the user's needs is generated, and the predefined rule library is updated based on the type and the created display rule.
[0105] In this embodiment of the application, the display rules include field sorting rules, field layout rules, and field design rules. The field sorting rules are used to specify the arrangement order of parameter fields in the parameter view. The field layout rules are used to specify the display position and size of parameter fields in the parameter view. The field layout rules are used to specify the personalized design of parameter fields in the parameter view, such as font color, pattern, etc. This embodiment of the application does not make specific limitations on these.
[0106] For example, Figure 6 A schematic diagram of a view design provided for an embodiment of this application, such as... Figure 6 As shown, the design parameter view page includes designs with names and descriptions, to... Figure 6 As shown in the example, the interface includes settings for query fields and display fields. The query field settings are used to obtain the corresponding display rules from the predefined rule base based on the type of the parameter model. The display field settings include the design of parameter number, parameter subsystem name, parameter subsystem code, creator, and creation time. Correspondingly, in response to the user's addition operation, query parameter fields and display parameter fields can also be added based on this interface. Then, display rules that meet the user's needs are generated on this interface. This application embodiment does not specifically limit the content of query field and display field settings. The above is only an example illustration.
[0107] It should be noted that, in this embodiment of the application, the display rules of the view design engine can also be customized based on the user's touch operation. Furthermore, the display rules of the created view design engine can be updated and stored in a predefined rule base.
[0108] Specifically, the execution code for this display rule is pre-written. When users modify the display rule, they only need to change the parameter values, such as the service name, input parameters, and output parameters, and then obtain the output results. For example, C-API-Status: 00 indicates that the status is normal; C-Response-Desc indicates that the description information is returned; C-Response-Code: 000000000000 indicates success, and others are listed in the error code status; C-Response-Body indicates the returned message body.
[0109] Therefore, embodiments of this application can customize the parameter view based on the display rules, so that the parameter view generated based on the parameter model can meet the needs of different users and different scenarios, thereby improving user satisfaction.
[0110] Optionally, the method further includes:
[0111] Obtain user input parameters and target behaviors, including query behavior, add behavior, delete behavior and modify behavior;
[0112] Based on the target behavior, the corresponding execution code is invoked, and a behavior instruction is generated based on the parameters and the execution code;
[0113] The behavior command is used to call the external interface to obtain the corresponding data from the subsystem for processing; the external interface is based on the parameter view definition.
[0114] The external interface of the parameter model is dynamically generated based on the parameter model. After configuring the parameter view based on the parameter model, it provides the external interface corresponding to the parameter view, which is used for the system to call parameters and access parameter data.
[0115] In this embodiment of the application, the query behavior includes querying the target data source name, querying the content of the target data source, querying the target database name, querying the target table in the target database, querying the target field in the target table, and querying all data in the tables under the target database. The target data source is a data source that the tenant has permission to access, the target database is a database that the tenant has permission to access, the target table is all tables under the specified database of the specified tenant, and the target field is all fields in the tables under the specified database of the specified tenant.
[0116] Specifically, query behaviors can be pre-written into a unified query code framework. When performing a query, only the parameter values in the query code framework need to be modified to achieve any query behavior. For example, to query all data in a table under a specified database for a specified tenant, the unified external interface is called by specifying the service name to be queried, the input parameters, and the output parameters, and the output results are obtained. Among them, C-API-Status: 00 indicates a normal status; C-Response-Desc indicates the return of descriptive information; C-Response-Code: 000000000000 indicates success, and other codes are listed in the error code status; C-Response-Body indicates the returned message body.
[0117] For example, the execution logic of the query behavior is implemented based on the parameter fields in the query code framework. Figure 7 This is a schematic diagram of a data query structure provided in an embodiment of this application, such as... Figure 7As shown, data can be queried based on SQL statements. The query code framework includes parameter fields corresponding to query records and parameter fields corresponding to query results. The parameter fields corresponding to query records are: id, sql_text, datasource_id, db, status, creator_account, creator_name, creat_time, and update_time, which correspond to primary key ID, SQL text, data source ID, database, status (1 executing, 2 completed), creator, creator name, creation time, and update time, respectively. The parameter fields corresponding to query records are: id, sql_exe_record, sql_text, result, creat_time, update_time, status, syntax_error_type, ... The syntax_error_sql, creator_account, creator_name, sql_option_type, datasource_name, datasource_type, db, datasource_id, tenant_id, tenant_name, and table_name_list correspond to the primary key ID, SQL record ID, SQL text, SQL execution result, creation time, update time, status (1 executing, 2 completed), syntax error type, syntax error SQL, creator, creator name, 1: Data Query Language (DQL), 2: Data Manipulation Language (DML), 3: Data Definition Language (DDL), 4: C language EXEC, data source name, data source type, database, data source ID, tenant ID, tenant name, and the name of the table being operated on.
[0118] It should be noted that the actions of adding, deleting, and modifying are similar to those of querying, that is, adding, deleting, and modifying the corresponding data. The embodiments of this application will not be described in detail here, but please refer to the description of querying for details.
[0119] Therefore, the embodiments of this application can use a unified interface to perform different behavioral operations. Only the parameters need to be modified to realize query behavior, add behavior, delete behavior and modify behavior, thus improving convenience.
[0120] Optionally, the behavior instruction can be used to call an external interface to obtain corresponding data from the subsystem for processing, including:
[0121] The behavioral instructions are parsed to obtain the quantity of the required data.
[0122] Determine whether the quantity is greater than a preset threshold;
[0123] If not, the corresponding data is retrieved from the subsystem and processed by sequentially calling the external interface in a synchronous manner;
[0124] If so, the corresponding data will be retrieved from the subsystem and processed by asynchronously calling the external interface.
[0125] In this embodiment, the preset threshold may refer to the threshold corresponding to a large number of data in the subsystem being called. When the number of data obtained from the subsystem or the number of data called from the subsystem exceeds the preset threshold, the corresponding data can be obtained from the subsystem by asynchronously executing SQL statements and calling the external interface. This embodiment does not limit the specific value corresponding to the preset threshold.
[0126] Specifically, the asynchronous execution code framework is pre-numbered. When the number is determined to be greater than a preset threshold, the parameter values in the code framework, such as service name, input parameters, and output parameters, can be modified to asynchronously call the external interface to obtain the corresponding data from the subsystem for processing and to obtain the output result. When the number is determined to be less than the preset threshold, the default step method is directly used to sequentially call the external interface to obtain the corresponding data from the subsystem for processing and to obtain the output result.
[0127] It should be noted that the embodiments of this application can also query asynchronous task results. The querying of asynchronous task results and the asynchronous execution of SQL statements are similar to the query behavior described above. For details, please refer to the description of the query behavior, which will not be repeated here.
[0128] Therefore, the embodiments of this application can perform different processing based on the quantity of query data. Synchronous calls can save resources, while asynchronous calls can improve efficiency.
[0129] In summary, the parameter management design method provided in this application belongs to the field of cloud technology. In this design method, the parameter model in the cloud platform system can be dynamically designed according to requirements. The parameter model is designed with reserved fields to standardize the quality of the parameter model. It also dynamically configures the parameter view based on the parameter model, thereby dynamically generating parameter interfaces to realize parameter information sharing between subsystems. This reduces the development work of developers when adding new parameter models, greatly reduces the digitalization cost of enterprises, and shortens the production time.
[0130] In the foregoing embodiments, the parameter management method provided by the embodiments of this application has been described. To implement the functions of the methods provided by the embodiments of this application, the electronic device serving as the execution subject may include hardware structures and / or software modules, implementing the above functions in the form of hardware structures, software modules, or a combination of hardware structures and software modules. Whether a particular function is executed in the form of hardware structures, software modules, or a combination of hardware structures and software modules depends on the specific application and design constraints of the technical solution.
[0131] For example, Figure 8 This application provides a schematic diagram of the structure of a parameter management device, applied to a cloud platform system. The cloud platform system includes multiple subsystems that share a single external interface and achieve parameter sharing based on parameter fields. Figure 8 As shown, the device includes: a receiving module 810, a generating module 820, and a configuration module 830; wherein, the receiving module 810 is used to receive business scenario requirements sent by the client, and generate at least one parameter field based on the business scenario requirements;
[0132] The generation module 820 is used to generate a parameter model that meets the user's needs in response to the user's touch operation of selecting the parameter field; the parameter model is used to define the structure of the parameter field.
[0133] The configuration module 830 is used to configure a parameter view based on the parameter model and to visualize the parameter view. The parameter view displays the parameter fields that can be called and the display rules of the parameter model, so that the client can call the parameters of any subsystem in the cloud platform system based on the external interface.
[0134] Optionally, the receiving module 810 is specifically used for:
[0135] Based on the business scenario requirements, the corresponding fixed parameter fields are searched from the predefined parameter library; the fixed parameter fields include: parameter identification number ID, client name, parameter modification record, and the name of the subsystem where the parameter is located;
[0136] In response to a user's search operation, the system searches for newly added custom parameter fields in the predefined parameter library and generates at least one parameter field based on the fixed parameter fields and the custom parameter fields.
[0137] Optionally, the device further includes an index module, the index module being used for:
[0138] After generating a parameter model that meets user requirements, the index entry of the parameter model is retrieved from the index table based on the type of the parameter model; the index entry is used to find a subsystem that meets the requirements of the business scenario.
[0139] In response to a user's touch operation to select an index item, an index page that meets the user's needs is generated, which allows the client to search for any subsystem in the cloud platform system.
[0140] Optionally, the configuration module 830 includes a configuration unit and a display unit; wherein, the configuration unit is used for:
[0141] Obtain the data source and database of the cloud platform system. The data source is used to store the data corresponding to the parameters in the subsystem, and the database is used to store the relationship between the data and the subsystem.
[0142] Determine the correspondence between the parameter fields corresponding to the parameter model and the database, and configure a parameter view based on the correspondence and the data source so that data in the data source can be called based on the parameter model in the parameter view.
[0143] Optionally, the display unit is used for:
[0144] Based on the type of the parameter model, the corresponding display rules are obtained from a predefined rule base; the display rules include field sorting rules, field layout rules, and field design rules;
[0145] Determine whether the display rules meet user needs;
[0146] If so, the parameter view is visualized using the defined display rules;
[0147] If not, then in response to the user's operation of creating display rules, a display rule that meets the user's needs is generated, and the predefined rule library is updated based on the type and the created display rule.
[0148] Optionally, the device further includes an operation module; the operation module includes an acquisition unit, a calling unit, and a processing unit;
[0149] Specifically, the acquisition unit is used to acquire parameters input by the user and the target behavior, the target behavior including query behavior, add behavior, delete behavior and modify behavior;
[0150] The invocation unit is used to invoke the corresponding execution code based on the target behavior, and to generate behavior instructions based on the parameters and the execution code;
[0151] The processing unit is used to call the external interface using the behavior instruction to obtain corresponding data from the subsystem for processing; the external interface is based on the parameter view definition.
[0152] Optionally, the processing unit is specifically used for:
[0153] The behavioral instructions are parsed to obtain the quantity of the required data.
[0154] Determine whether the quantity is greater than a preset threshold;
[0155] If not, the corresponding data is retrieved from the subsystem and processed by sequentially calling the external interface in a synchronous manner;
[0156] If so, the corresponding data will be retrieved from the subsystem and processed by asynchronously calling the external interface.
[0157] The specific implementation principle and effects of the parameter management device provided in this application embodiment can be found in the relevant descriptions and effects of the above embodiments, and will not be elaborated further here.
[0158] This application also provides a schematic diagram of the structure of an electronic device. Figure 9 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application, such as... Figure 9 As shown, the electronic device may include: a processor 901 and a memory 902 communicatively connected to the processor; the memory 902 stores a computer program; the processor 901 executes the computer program stored in the memory 902, causing the processor 901 to perform the method described in any of the above embodiments.
[0159] The memory 902 and the processor 901 can be connected via bus 903.
[0160] This application also provides a computer-readable storage medium storing computer program execution instructions, which, when executed by a processor, are used to implement the methods described in any of the foregoing embodiments of this application.
[0161] This application also provides a chip for executing instructions, which is used to perform the methods described in any of the foregoing embodiments executed by an electronic device as described in any of the foregoing embodiments of this application.
[0162] This application also provides a computer program product, which includes program code. When a computer runs the computer program, the program code executes the method described in any of the foregoing embodiments of this application as executed by an electronic device.
[0163] The collection, storage, use, processing, transmission, provision, and disclosure of financial data or user data involved in the technical solution of this application all comply with the provisions of relevant laws and regulations and do not violate public order and good morals.
[0164] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of modules is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple modules or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or modules may be electrical, mechanical, or other forms.
[0165] The modules described as separate components may or may not be physically separate. The components shown as modules may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to implement the solution of this embodiment according to actual needs.
[0166] Furthermore, the functional modules in the various embodiments of this application can be integrated into one processing unit, or each module can exist physically separately, or two or more modules can be integrated into one unit. The unit composed of the above modules can be implemented in hardware or in the form of hardware plus software functional units.
[0167] The integrated modules implemented as software functional modules described above can be stored in a computer-readable storage medium. These software functional modules, stored in a storage medium, include several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute some steps of the methods described in the various embodiments of this application.
[0168] It should be understood that the aforementioned processor can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), etc. A general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in the application can be directly manifested as being executed by a hardware processor, or executed by a combination of hardware and software modules within the processor.
[0169] The memory may include high-speed random access memory (RAM) or non-volatile memory (NVM), such as at least one disk storage device, and may also be a USB flash drive, external hard drive, read-only memory, disk or optical disc, etc.
[0170] The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc. For ease of illustration, the buses shown in the accompanying drawings are not limited to a single bus or a single type of bus.
[0171] The aforementioned storage media can be implemented from any type of volatile or non-volatile storage device or a combination thereof, such as Static Random-Access Memory (SRAM), Electrically Erasable Programmable Read-Only Memory (EEPROM), Erasable Programmable Read-Only Memory (EPROM), Programmable Read-Only Memory (PROM), Read-Only Memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk. The storage media can be any available medium accessible to general-purpose or special-purpose computers.
[0172] An exemplary storage medium is coupled to a processor, enabling the processor to read information from and write information to the storage medium. Alternatively, the storage medium can be an integral part of the processor. Both the processor and the storage medium can reside in an Application Specific Integrated Circuit (ASIC). Alternatively, the processor and storage medium can exist as discrete components in an electronic device or host device.
[0173] The above description is merely a specific implementation of the embodiments of this application, but the protection scope of the embodiments of this application is not limited thereto. Any changes or substitutions within the technical scope disclosed in the embodiments of this application should be covered within the protection scope of the embodiments of this application. Therefore, the protection scope of the embodiments of this application should be determined by the protection scope of the claims.
Claims
1. A parameter management method, characterized in that, The method is applied to a cloud platform system, which includes multiple subsystems that share a single external interface and achieve parameter sharing based on parameter fields. Receive business scenario requirements sent by the client, and generate at least one parameter field based on the business scenario requirements; the parameter field is used to call the parameter data corresponding to the parameter field; In response to a user's touch operation selecting the parameter field, a parameter model that meets the user's needs is generated; the parameter model is used to define the structure of the parameter field. Obtain the data source and database of the cloud platform system. The data source is used to store the data corresponding to the parameters in the subsystem, and the database is used to store the relationship between the data and the subsystem. The correspondence between the parameter fields corresponding to the parameter model and the database is determined, and a parameter view is configured based on the correspondence and the data source so that data in the data source can be called based on the parameter model on the parameter view. The parameter view is then visualized, displaying the available parameter fields and the display rules of the parameter model, so that the client can call parameters in any subsystem of the cloud platform system based on the external interface. The display rules include field sorting rules, field layout rules, and field design rules.
2. The method according to claim 1, characterized in that, At least one parameter field is generated based on the business scenario requirements, including: Based on the business scenario requirements, the corresponding fixed parameter fields are searched from the predefined parameter library; the fixed parameter fields include: parameter identification number ID, client name, parameter modification record, and the name of the subsystem where the parameter is located; In response to a user's search operation, the system searches for newly added custom parameter fields in the predefined parameter library and generates at least one parameter field based on the fixed parameter fields and the custom parameter fields.
3. The method according to claim 1, characterized in that, The method further includes: After generating a parameter model that meets user requirements, the index entry of the parameter model is retrieved from the index table based on the type of the parameter model; the index entry is used to find a subsystem that meets the requirements of the business scenario. In response to a user's touch operation to select an index item, an index page that meets the user's needs is generated, which allows the client to search for any subsystem in the cloud platform system.
4. The method according to claim 1, characterized in that, Visualizing the parameter view includes: Based on the type of the parameter model, the corresponding display rules are obtained from the predefined rule base; Determine whether the display rules meet user needs; If so, the parameter view is visualized using the defined display rules; If not, then in response to the user's operation of creating display rules, a display rule that meets the user's needs is generated, and the predefined rule library is updated based on the type and the created display rule.
5. The method according to any one of claims 1-4, characterized in that, The method further includes: Obtain user input parameters and target behaviors, including query behavior, add behavior, delete behavior and modify behavior; Based on the target behavior, the corresponding execution code is invoked, and a behavior instruction is generated based on the parameters and the execution code; The behavior command is used to call the external interface to obtain the corresponding data from the subsystem for processing; the external interface is based on the parameter view definition.
6. The method according to claim 5, characterized in that, Using the aforementioned behavioral instructions to invoke an external interface to retrieve corresponding data from the subsystem for processing includes: The behavioral instructions are parsed to obtain the quantity of the required data. Determine whether the quantity is greater than a preset threshold; If not, the corresponding data is retrieved from the subsystem and processed by sequentially calling the external interface in a synchronous manner; If so, the corresponding data will be retrieved from the subsystem and processed by asynchronously calling the external interface.
7. A parameter management device, characterized in that, The device is applied to a cloud platform system, which includes multiple subsystems that share a single external interface and achieve parameter sharing based on parameter fields; the device includes: A receiving module is used to receive business scenario requirements sent by a client and generate at least one parameter field based on the business scenario requirements; the parameter field is used to call parameter data corresponding to the parameter field. A generation module is used to generate a parameter model that meets the user's requirements in response to the user's touch operation of selecting the parameter field; the parameter model is used to define the structure of the parameter field. The configuration module is used to obtain the data source and database in the cloud platform system. The data source is used to store the data corresponding to the parameters in the subsystem, and the database is used to store the relationship between the data and the subsystem. The correspondence between the parameter fields corresponding to the parameter model and the database is determined, and a parameter view is configured based on the correspondence and the data source so that data in the data source can be called based on the parameter model on the parameter view. The parameter view is then visualized, displaying the available parameter fields and the display rules of the parameter model, so that the client can call parameters in any subsystem of the cloud platform system based on the external interface. The display rules include field sorting rules, field layout rules, and field design rules.
8. An electronic device, characterized in that, include: A processor, and a memory communicatively connected to the processor; The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory to implement the method as described in any one of claims 1-6.
9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the method as described in any one of claims 1-6.
10. A computer program product, characterized in that, Includes program code that, when the computer runs the computer program, performs the method as described in any one of claims 1-6.