A method and system for generating digital business based on dynamic model

Generating dynamic business page templates through static data modeling and page modeling templates solves the problem of repeated development in the existing technology, improves development efficiency and business logic consistency, and reduces development costs.

CN118626089BActive Publication Date: 2024-11-12BEIJING NEUSOFT HUIJU INFORMATION TECH HLDG CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411096335.8
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2024-08-12
Publication Date
2024-11-12
Estimated Expiration
2044-08-12

AI Technical Summary

Technical Problem

The prior art needs to be repeatedly developed when facing similar business functions, resulting in inefficiency and error-proneness, and consumes a lot of development resources.

Method used

Through static data modeling and page modeling templates, dynamic business page templates are generated, manual coding is reduced, and development efficiency and business logic are improved.

Benefits of technology

It realizes rapid replication and construction of regular and model-compliant businesses, reduces development costs, and improves development efficiency and reliability of business logic.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118626089B_ABST
    Figure CN118626089B_ABST
Patent Text Reader

Abstract

The present invention discloses a method and system for generating digital business based on dynamic model, which belongs to the technical field of computer technology. The method includes: step S1, static data modeling of business fields in a database to obtain a static model; step S2, page configuration of page layout, component configuration and interaction logic based on the static model; step S3, generating a dynamic business page template based on the static model and the content of the page configuration; step S4, obtaining the dynamic business page template of the back end according to the business type, dynamically integrating the page with the front end page to form a new page content, performing page rendering, and generating dynamic digital business. Through the present invention, there are scenarios with extremely similar business functions in actual product scenarios, and a dynamic model is formed through the idea of ​​static data modeling + page modeling template, which can quickly copy and build regular and model-compliant businesses.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and in particular to a method and system for generating digital services based on a dynamic model. Background Art

[0002] With the development of Internet technology and the maturity of application software, users use visual modeling methods such as data modeling and page modeling to quickly build businesses in a low-code or zero-code manner, which has become the latest trend in the development of software technology. By using data modeling and page modeling, multiple pages are combined into business scenarios. Data models can be reused by multiple pages, and component models can also be reused by multiple pages, so that corresponding scenarios can be quickly built.

[0003] However, existing technical solutions require repeated development when faced with similar business functions, consume a lot of development resources, are inefficient and prone to errors. Summary of the invention

[0004] In order to solve the problem of repeated development in business scenarios, the present invention provides a method for generating digital business based on a dynamic model, which improves development efficiency and reduces development costs in a templated manner. The method includes:

[0005] Step S1, performing static data modeling on the business fields of the database to obtain a static model;

[0006] Step S2: configuring the page layout, component configuration and interaction logic based on the static model;

[0007] Step S3: Generate a dynamic business page template based on the static model and the content of the page configuration;

[0008] Step S4: Obtain the dynamic business page template of the backend according to the business type, dynamically merge the page with the front-end page to form new page content, perform page rendering, and generate dynamic digital business.

[0009] Optionally, in step S1, the business field content includes: field code, which is used to identify the field code and is a unique identifier; field name; data type, which is used to mark the data type of the field; whether it is required is used to identify whether it is a required field; remarks, which is used to fill in the remarks information of the prefabricated field, and the prefabricated field is a preset number of fields without business meaning.

[0010] Optionally, in step S2, the content of the page configuration specifically includes:

[0011] Template code, used to configure the code that identifies the page template and is a unique identifier; template name; template details, used to configure the detailed information of the displayed page template; remarks, used to configure the description of the page template; field group, used to configure the fields in the organization page; field list, used to configure all field information in the field group.

[0012] Optionally, in step S3, the page template uses the business type as the template identifier, and generates a dynamic business page template based on the static model and the content of the page configuration.

[0013] The present invention also discloses a system for generating digital services based on dynamic models, the system comprising: a static data modeling module, a page configuration module, a template generation module and a service generation module;

[0014] The static data modeling module is used to perform static data modeling on the business fields of the database to obtain a static model;

[0015] The page configuration module is used to configure the page layout, component configuration and interaction logic based on the static model;

[0016] The template generation module is used to generate a dynamic business page template based on the static model and the content of the page configuration;

[0017] The business generation module is used to obtain the dynamic business page template of the back end according to the business type, dynamically merge the page with the front-end page, form new page content, perform page rendering, and generate dynamic digital business.

[0018] Optionally, the business field content includes: field code, which is used to identify the field code and is a unique identifier; field name; data type, which is used to mark the data type of the field; whether it is required is used to identify whether it is a required field; remarks, which is used to fill in the remarks information of the prefabricated field, and the prefabricated field is a preset number of fields without business meaning.

[0019] Optionally, the content of the page configuration specifically includes:

[0020] Template code, used to configure the code that identifies the page template and is a unique identifier; template name; template details, used to configure the detailed information of the displayed page template; remarks, used to configure the description of the page template; field group, used to configure the fields in the organization page; field list, used to configure all field information in the field group.

[0021] Optionally, the page template uses the business type as the template identifier, and generates a dynamic business page template based on the static model and the content of the page configuration.

[0022] Compared with the prior art, the present invention has the following beneficial effects:

[0023] The present invention enables scenarios with extremely similar business functions to exist in actual product scenarios. By forming a dynamic model through the idea of ​​static data modeling + page modeling template, regular businesses that conform to the model can be quickly replicated and constructed. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] In order to more clearly illustrate the technical solution of the present invention, the following briefly introduces the drawings required for use in the embodiments. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative labor.

[0025] Figure 1 A step diagram of a method for generating digital services according to an embodiment of the present invention. DETAILED DESCRIPTION

[0026] In order to make the above-mentioned objects, features and advantages of the present invention more obvious and easy to understand, the present invention is further described in detail below with reference to the accompanying drawings and specific embodiments.

[0027] Embodiment 1

[0028] The present invention provides a method for generating digital services based on a dynamic model, such as Figure 1 As shown, the method includes:

[0029] Step S1: Perform static data modeling on the business fields of the database to obtain a static model.

[0030] In step S1, the business field content includes: field code, which is used to identify the field code and is a unique identifier; field name; data type, which is used to mark the data type of the field; whether it is required is used to identify whether it is a required field; remarks, which is used to fill in the remarks information of the prefabricated field.

[0031] Specifically, first, static data modeling is performed in the database, and a set of commonly used fields are predefined. These fields include field codes, field names, data types, and whether they are required. Through the predefined field set, the standardization and consistency of the data model can be ensured, and the efficiency and flexibility of data modeling can be improved. In this embodiment, a fixed number of fields without business meanings are pre-set. As an implementation method of this embodiment, the fixed number set is 50, and this field is a prefabricated field.

[0032] Static data modeling is to expand the definition of fields and their uses in the database and build a data model. This method allows a set of fields to be predefined in the database so that they can be quickly used and expanded when needed. These predefined fields include column names, data types, lengths, and whether they are required. By predefining fields, you can improve the efficiency of data modeling, reduce duplication of work, and ensure the standardization and consistency of the data model.

[0033] Specifically, the fields for static data modeling are defined as follows:

[0034] Column name: A code used to uniquely identify a field. For example, "ext01". Data type, length: The data type of the field, such as string ("String"), integer ("Integer"), etc. Required: Indicates whether the field is required, true means required, false means not required. Remarks: Remarks for pre-made fields. In order to better support business needs, the system pre-defines a number of commonly used fields in the database. The codes, names, data types, and other information of these fields are shown in Table 1:

[0035] Table 1

[0036] Field encoding Data Types Is this field required? Remark ext001 varchar(50) NULL Preset field 001 ext002 varchar(50) NULL Preset field 002 ext003 varchar(50) NULL Preset field 003 ext004 varchar(50) NULL Preset field 004 ext005 varchar(50) NULL Preset field 005 ext006 varchar(50) NULL Preset field 006 ext007 varchar(50) NULL Preset field 007 …

[0037] Step S2: Configure the page layout, component configuration and interaction logic based on the static model.

[0038] In step S2, the content of the page configuration specifically includes: template code, which is used to configure the code that identifies the page template and is a unique identifier; template name; template details, which are used to configure the detailed information of the display page template; notes, which are used to configure the description of the page template; field group, which is used to configure the fields in the organization page; field list, which is used to configure all field information in the field group.

[0039] Next, define the user interface through page modeling. Page modeling includes creating page templates, field groups, and field attributes. Each page template contains multiple field groups, and each field group contains multiple fields. In this way, you can flexibly configure the page display content to meet the needs of different business scenarios.

[0040] templateCode: A code that uniquely identifies a page template. For example, "TEMP001". templateName: A name for the template that describes the purpose of the template. For example, "Sample Template". details: Contains detailed information about the page template, such as the applicable terminal (WEB, APP) and whether it is a default template. terminal: Indicates which terminal the page template is applicable to, such as WEB or APP. isDefault: Indicates whether the template is a default template, true indicates default, and false indicates non-default. remark: A brief description of the template. For example, "This is a sample template". groups: Used to organize fields on a page, including the field group code, name, visibility, and other information. groupCode: A code that uniquely identifies a field group. groupName: A name for the field group that describes the purpose of the field group. viewVisiable: Indicates whether the field group is visible in view mode. addEditVisiable: Indicates whether the field group is visible in add or edit mode. fields: Contains information about all fields in a field group. code (field code): the code of the field, which is consistent with the field code in the data model. name (field name): the name of the field, which is consistent with the field name in the data model. dataType (data type): the data type of the field, which is consistent with the data type in the data model. required (required): indicates whether the field is a required field.

[0041] Step S3: Generate a dynamic business page template based on the static model and the content of the page configuration.

[0042] In step S3, the page template uses the business type as the template identifier, and generates a dynamic business page template based on the static model and the content of the page configuration. In this embodiment, the fusion logic is mainly to obtain the field code according to the configured content, find the content of the corresponding field of the static page according to the configured field code, replace the content of the corresponding field of the front end with the rules of the back-end field configuration, form a new page content, perform page rendering, and generate dynamic digital business.

[0043] Step S4: Obtain the dynamic business page template of the backend according to the business type, dynamically merge the page with the front-end page to form new page content, perform page rendering, and generate dynamic digital business.

[0044] In step S4, the data model and the page model are combined through the front-end display step to realize the visual display of the user interface. The front-end display dynamically loads data into the front-end page based on the defined page template and field group to provide a user-friendly interactive interface. Generate the front-end page according to the data model and page template to display the business functions. otemplate (template container): contains the overall layout of the page template. ogroup (field group container): contains all field components of a field group. olabel (label): used to display the name of the field. input (input box): used for users to enter the value of the field, and the type is determined according to the data type of the field.

[0045] In the dynamic model generation step, the system automatically generates business logic and data processing flow based on the static data model and page model. The generation of dynamic models reduces the workload of manual coding, improves development efficiency, and ensures the consistency and reliability of business logic. 4. In actual product scenarios, through the idea of ​​static data modeling and page modeling templates, a dynamic model is formed to quickly copy and build regular and model-compliant businesses. odynamicModel (dynamic model): Contains dynamically generated business model information. modelCode (model code): A code used to uniquely identify a dynamic model. modelName (model name): The name of the model, used to describe the purpose of the model. dataModel (data model): Contains data field information in the dynamic model. ofields (field list): Contains all field information in the data model. fieldCode (field code): The code of the field, which is consistent with the field code in the data model. fieldName (field name): The name of the field, which is consistent with the field name in the data model. dataType (data type): The data type of the field, which is consistent with the data type in the data model. isRequired (is it required): Indicates whether the field is a required field. opageModel (page model): Contains page template information in the dynamic model. templateCode (template code): the code of the template, which is consistent with the template code in the page template. templateName (template name): the name of the template, which is consistent with the template name in the page template. details (template details): contains detailed information of the page template, such as the applicable terminal and whether it is the default template. groups (field groups): contains all the field group information in the page template. groupCode (field group code): the code of the field group, which is consistent with the field group code in the page template. groupName (field group name): the name of the field group, which is consistent with the field group name in the page template. viewVisiable (view visible): indicates whether the field group is visible in view mode. addEditVisiable (add / edit visible): indicates whether the field group is visible in add or edit mode. fields (field list): contains all the field information in the field group. code (field code): the code of the field, which is consistent with the field code in the data model. name (field name): the name of the field, which is consistent with the field name in the data model. dataType (data type): the data type of the field, which is consistent with the data type in the data model. required (whether required): indicates whether the field is a required field.

[0046] The system provides template management functions, supporting the creation, modification, deletion and version control of data models and page templates. Template management can be used to easily maintain and update templates to ensure the flexibility and scalability of the business system. otemplateManagement (template management): Contains functions related to template management. createTemplate (create template): Information used to create a new template. templateCode (template code): A code used to uniquely identify a page template. templateName (template name): The name of the template, used to describe the purpose of the template. details (template details): Contains detailed information about the page template, such as the applicable terminal and whether it is the default template. groups (field groups): Contains information about all field groups in the page template. groupCode (field group code): The code of the field group. groupName (field group name): The name of the field group. viewVisiable (view visible): Indicates whether the field group is visible in view mode. addEditVisiable (add / edit visible): Indicates whether the field group is visible in add or edit mode. fields (field list): Contains information about all fields in the field group. code (field code): The code of the field. name (field name): The name of the field. dataType (data type): The data type of the field. required: Indicates whether the field is required.

[0047] Configure business rules according to different business needs, including data validation rules, page display rules and business process rules. Business rule configuration ensures that the system can run correctly in different scenarios and improves the intelligence and automation of the system. obusinessRules (business rules): Contains relevant information about business rules. validationRules (validation rules): Defines validation rules for fields. fieldCode (field code): The code of the field to be validated. rule (validation rules): Validation rules, such as notEmpty, which means that the field cannot be empty. message (error message): The error message displayed when validation fails. displayRules (display rules): Defines display rules for fields. fieldCode (field code): The code of the field to be displayed. rule (display rules): Display rules, such as visibleIf, which means that the field is visible under certain conditions. condition (condition): The condition that controls the display, such as field005 != null, which means that the field is visible when field005 is not empty. workflowRules (workflow rules): Defines rules for business processes. stepCode (step code): The code of the workflow step. stepName (step name): The name of the workflow step. conditions (condition list): Contains the conditions for step execution. fieldCode: The field code corresponding to the condition. condition: The content of the condition, for example, notEmpty means that the field cannot be empty. actions: Contains the actions to be performed by the step. actionCode: The code of the action. actionName: The name of the action. arameters: The parameters of the action, for example, the email address to send notifications to.

[0048] The dynamic business page template of the backend is obtained according to the business type, and the page is dynamically integrated with the frontend page. The integration logic is mainly to obtain the field code based on the configured content, find the content of the corresponding field code of the static page according to the configured field code, replace the content of the corresponding field on the frontend with the rules of the backend field configuration, form a new page content, render the page, and generate dynamic digital business.

[0049] Embodiment 2

[0050] A system for generating digital business based on a dynamic model, the system comprising: a static data modeling module, a page configuration module, a template generation module and a business generation module;

[0051] The static data modeling module is used to perform static data modeling on the business fields of the database to obtain a static model. The business field content includes: field code, which is used to identify the field code and is a unique identifier; field name; data type, which is used to mark the data type of the field; whether it is required to identify whether it is a required field; remarks, which is used to fill in the remarks information of the prefabricated field.

[0052] Specifically, first, static data modeling is performed in the database, and a set of commonly used fields are predefined. These fields include field codes, field names, data types, and whether they are required. The predefined field set can ensure the standardization and consistency of the data model and improve the efficiency and flexibility of data modeling.

[0053] Static data modeling is to expand the definition of fields and their uses in the database and build a data model. This method allows a set of fields to be predefined in the database so that they can be quickly used and expanded when needed. These predefined fields include column names, data types, lengths, and whether they are required. By predefining fields, you can improve the efficiency of data modeling, reduce duplication of work, and ensure the standardization and consistency of the data model.

[0054] Specifically, the fields for static data modeling are defined as follows:

[0055] Column name: A code used to uniquely identify a field. For example, "ext01". Data type, length: The data type of the field, such as string ("String"), integer ("Integer"), etc. Required: Indicates whether the field is required, true means required, false means not required. Remarks: Remarks for pre-made fields. In order to better support business needs, the system pre-defines a number of commonly used fields in the database. The codes, names, data types, and other information of these fields are shown in Table 2:

[0056] Table 2

[0057] Field Name Data Types Is it empty? default value Notes vendorid bigint UNSIGNED NOT NULL Supplier ID clientcode varchar(50) NOT NULL Client Encoding vendorcode varchar(50) NULL NULL Supplier Code vendorname varchar(100) NULL NULL Supplier Name vendorerpcode varchar(50) NULL NULL Supplier ERP Code accountgroupname varchar(100) NULL NULL Supplier Coding Rules vendoraccountgroup varchar(50) NULL NULL Supplier Coding Rules Coding stopflag tinyint UNSIGNED NULL NULL Freeze flag (0: enable, 1: freeze) erpsynstate tinyint NULL NULL Synchronize to ERP status (0: Not synchronized, 1: Synchronizing, 2: Partially synchronized, 3: Synchronized, 4: Synchronization failed, 5: Not synchronized) erpreturnmsg longtext NULL NULL ERP return information createtime datetime NULL NULL Creation time createuserid bigint UNSIGNED NULL NULL Creator ID createusername varchar(100) NULL NULL Creator Name modifyuserid bigint UNSIGNED NULL NULL Modifier ID modifyusername varchar(100) NULL NULL Modifier Name modifytime datetime NULL NULL Modification time Salesman varchar(100) NULL NULL Salesperson salesmanmobile varchar(100) NULL NULL Salesperson Mobile Phone salesmanemail varchar(200) NULL NULL Salesperson Email vendortype varchar(50) NULL NULL Supplier Type vendortypename varchar(100) NULL NULL Supplier Type Name uniqueidentifierno varchar(40) NULL NULL Supplier invitation code filegroupid bigint NULL NULL Accessory Group remark longtext NULL NULL Remark shortname varchar(50) NULL NULL Abbreviation ext001 varchar(50) NULL NULL Preset field 001 ext002 varchar(50) NULL NULL Preset field 002 ext003 varchar(50) NULL NULL Preset field 003 ext004 varchar(50) NULL NULL Preset field 004 ext005 varchar(50) NULL NULL Preset field 005 ext006 varchar(50) NULL NULL Preset field 006 ext007 varchar(50) NULL NULL Preset field 007 ext008 varchar(50) NULL NULL Preset field 008 ext009 varchar(50) NULL NULL Preset field 009 ext010 varchar(50) NULL NULL Preset field 010 ext011 varchar(50) NULL NULL Preset field 011 ext012 varchar(50) NULL NULL Preset field 012 ext013 varchar(50) NULL NULL Preset field 013 ext014 varchar(50) NULL NULL Preset field 014 ext015 varchar(50) NULL NULL Preset field 015 ext016 varchar(50) NULL NULL Preset field 016 ext017 varchar(50) NULL NULL Preset field 017 ext018 varchar(50) NULL NULL Preset field 018 ext019 varchar(50) NULL NULL Preset field 019 ext020 varchar(50) NULL NULL Preset field 020 ext021 varchar(50) NULL NULL Preset field 021 ext022 varchar(50) NULL NULL Preset field 022 ext023 varchar(50) NULL NULL Preset field 023 ext024 varchar(50) NULL NULL Preset field 024 ext025 varchar(50) NULL NULL Preset field 025 ext026 varchar(50) NULL NULL Preset field 026 ext027 varchar(50) NULL NULL Preset field 027 ext028 varchar(50) NULL NULL Preset field 028 ext029 varchar(50) NULL NULL Preset field 029 ext030 varchar(50) NULL NULL Preset field 030 ext031 varchar(50) NULL NULL Preset field 031 ext032 varchar(50) NULL NULL Preset field 032 ext033 varchar(50) NULL NULL Preset field 033 ext034 varchar(50) NULL NULL Preset field 034 ext035 varchar(50) NULL NULL Preset field 035 ext036 varchar(50) NULL NULL Preset field 036 ext037 varchar(50) NULL NULL Preset field 037 ext038 varchar(50) NULL NULL Preset field 038 ext039 varchar(50) NULL NULL Preset field 039 ext040 varchar(50) NULL NULL Preset field 040 ext041 varchar(50) NULL NULL Preset field 041 ext042 varchar(50) NULL NULL Preset field 042 ext043 varchar(50) NULL NULL Preset field 043 ext044 varchar(50) NULL NULL Preset field 044 ext045 varchar(50) NULL NULL Preset field 045 ext046 varchar(50) NULL NULL Preset field 046 ext047 varchar(50) NULL NULL Preset field 047 ext048 varchar(50) NULL NULL Preset field 048 ext049 varchar(50) NULL NULL Preset field 049 ext050 varchar(50) NULL NULL Preset field 050 ext051 varchar(200) NULL NULL Preset field 051 ext052 varchar(200) NULL NULL Preset field 052 ext053 varchar(200) NULL NULL Preset field 053 ext054 varchar(200) NULL NULL Preset field 054 ext055 varchar(200) NULL NULL Preset field 055 ext056 varchar(200) NULL NULL Preset field 056 …

[0058] The page configuration module is used to configure page layout, component configuration and interaction logic based on the static model.

[0059] The contents of page configuration including page layout, component configuration and interaction logic include: the contents of page layout include; template code, which is used to configure the code that identifies the page template and is the only identifier; template name; template details, which are used to configure the detailed information of the display page template; notes, which are used to configure the description of the page template; field group, which is used to configure the fields in the organization page; field list, which is used to configure all field information in the field group.

[0060] Next, define the user interface through page modeling. Page modeling includes creating page templates, field groups, and field attributes. Each page template contains multiple field groups, and each field group contains multiple fields. In this way, you can flexibly configure the page display content to meet the needs of different business scenarios.

[0061] templateCode: A code that uniquely identifies a page template. For example, "TEMP001". templateName: The name of the template, used to describe the purpose of the template. For example, "Sample Template". details: Contains detailed information about the page template, such as the applicable terminal (WEB, APP) and whether it is a default template. terminal: Indicates which terminal the page template is applicable to, such as WEB or APP. isDefault: Indicates whether the template is a default template, true indicates default, false indicates non-default. remark: A brief description of the template. For example, "This is a sample template". groups: Used to organize fields on a page, including the field group code, name, visibility, and other information. groupCode: A code that uniquely identifies a field group. groupName: The name of the field group, used to describe the purpose of the field group. viewVisiable: Indicates whether the field group is visible in view mode. addEditVisiable: Indicates whether the field group is visible in add or edit mode. fields (field list): contains all the field information in the field group. code (field code): the code of the field, which is consistent with the field code in the data model. name (field name): the name of the field, which is consistent with the field name in the data model. dataType (data type): the data type of the field, which is consistent with the data type in the data model. required (whether required): indicates whether the field is a required field.

[0062] The template generation module is used to generate a dynamic business page template based on the static model and the content of the page configuration.

[0063] The business generation module is used to obtain the dynamic business page template of the backend according to the business type, dynamically merge the page with the front-end page, form new page content, render the page, and generate dynamic digital business.

[0064] Through the front-end display step, the data model and the page model are combined to realize the visual display of the user interface. The front-end display is based on the defined page template and field group, and the data is dynamically loaded into the front-end page to provide a user-friendly interactive interface. The front-end page is generated according to the data model and page template to display the business functions. otemplate (template container): contains the overall layout of the page template. ogroup (field group container): contains all field components of a field group. olabel (label): used to display the name of the field. input (input box): used for users to enter the value of the field, the type is determined by the data type of the field.

[0065] In the dynamic model generation step, the system automatically generates business logic and data processing flow based on the static data model and page model. The generation of dynamic models reduces the workload of manual coding, improves development efficiency, and ensures the consistency and reliability of business logic. 4. In actual product scenarios, through the idea of ​​static data modeling and page modeling templates, a dynamic model is formed to quickly copy and build regular and model-compliant businesses. odynamicModel (dynamic model): Contains dynamically generated business model information. modelCode (model code): A code used to uniquely identify a dynamic model. modelName (model name): The name of the model, used to describe the purpose of the model. dataModel (data model): Contains data field information in the dynamic model. ofields (field list): Contains all field information in the data model. fieldCode (field code): The code of the field, which is consistent with the field code in the data model. fieldName (field name): The name of the field, which is consistent with the field name in the data model. dataType (data type): The data type of the field, which is consistent with the data type in the data model. isRequired (is it required): Indicates whether the field is a required field. opageModel (page model): Contains page template information in the dynamic model. templateCode (template code): the code of the template, which is consistent with the template code in the page template. templateName (template name): the name of the template, which is consistent with the template name in the page template. details (template details): contains detailed information of the page template, such as the applicable terminal and whether it is the default template. groups (field groups): contains all the field group information in the page template. groupCode (field group code): the code of the field group, which is consistent with the field group code in the page template. groupName (field group name): the name of the field group, which is consistent with the field group name in the page template. viewVisiable (view visible): indicates whether the field group is visible in view mode. addEditVisiable (add / edit visible): indicates whether the field group is visible in add or edit mode. fields (field list): contains all the field information in the field group. code (field code): the code of the field, which is consistent with the field code in the data model. name (field name): the name of the field, which is consistent with the field name in the data model. dataType (data type): the data type of the field, which is consistent with the data type in the data model. required (whether required): indicates whether the field is a required field.

[0066] The system provides template management functions, supporting the creation, modification, deletion and version control of data models and page templates. Template management can be used to easily maintain and update templates to ensure the flexibility and scalability of the business system. otemplateManagement (template management): Contains functions related to template management. createTemplate (create template): Information used to create a new template. templateCode (template code): A code used to uniquely identify a page template. templateName (template name): The name of the template, used to describe the purpose of the template. details (template details): Contains detailed information about the page template, such as the applicable terminal and whether it is the default template. groups (field groups): Contains all field group information in the page template. groupCode (field group code): The code of the field group. groupName (field group name): The name of the field group. viewVisiable (view visible): Indicates whether the field group is visible in view mode. addEditVisiable (add / edit visible): Indicates whether the field group is visible in add or edit mode. fields (field list): Contains all field information in the field group. code (field code): The code of the field. name (field name): The name of the field. dataType (data type): The data type of the field. required: Indicates whether the field is required.

[0067] Configure business rules according to different business needs, including data validation rules, page display rules and business process rules. Business rule configuration ensures that the system can run correctly in different scenarios and improves the intelligence and automation of the system. obusinessRules (business rules): Contains relevant information about business rules. validationRules (validation rules): Defines validation rules for fields. fieldCode (field code): The code of the field to be validated. rule (validation rules): Validation rules, such as notEmpty, which means that the field cannot be empty. message (error message): The error message displayed when validation fails. displayRules (display rules): Defines display rules for fields. fieldCode (field code): The code of the field to be displayed. rule (display rules): Display rules, such as visibleIf, which means that the field is visible under certain conditions. condition (condition): The condition that controls the display, such as field005 != null, which means that the field is visible when field005 is not empty. workflowRules (workflow rules): Defines rules for business processes. stepCode (step code): The code of the workflow step. stepName (step name): The name of the workflow step. conditions (condition list): Contains the conditions for step execution. fieldCode (field code): the field code corresponding to the condition. condition (condition): the content of the condition, for example, notEmpty means that the field cannot be empty. actions (operation list): contains the operations to be performed by the steps. actionCode (operation code): the code of the operation. actionName (operation name): the name of the operation. arameters (parameters): the parameters of the operation, such as the email address to which the notification is sent. The above-described embodiments are only descriptions of the preferred embodiments of the present invention, and are not intended to limit the scope of the present invention. Without departing from the design spirit of the present invention, various modifications and improvements made to the technical solution of the present invention by ordinary technicians in this field should fall within the scope of protection determined by the claims of the present invention.

Claims

1. A method for generating digital business based on dynamic model, It is characterized in that The method comprises: Step S1, static data modeling is performed on the business fields of the database to obtain a static model; in step S1, the business field content includes: field code, which is used to identify the field code and is a unique identifier; field name; data type, which is used to mark the data type of the field; whether it is required is used to identify whether it is a required field; remarks, which is used to fill in the remarks information of the prefabricated field, and the prefabricated field is a preset number of fields without business meaning; Step S2: configuring the page layout, component configuration and interaction logic based on the static model; Step S3, generating a dynamic business page template based on the static model and the content of the page configuration; In step S3, the page template uses the business type as the template identifier, and generates the dynamic business page template based on the static model and the content of the page configuration; Step S4: According to the business type, the dynamic business page template of the backend is obtained, and the page is dynamically integrated with the frontend page to form a new page content, and the page is rendered to generate a dynamic digital business; the integration logic is to obtain the field code according to the configured content, find the content of the corresponding field of the static page according to the configured field code, replace the content of the corresponding field of the frontend with the rules of the backend field configuration, form a new page content, render the page, and generate a dynamic digital business; In step S4, the data model and the page model are combined through the front-end display step to realize the visual display of the user interface; the front-end display is based on the defined page template and field group, and the data is dynamically loaded into the front-end page to provide a user-friendly interactive interface; the front-end page is generated according to the data model and the page template to display the business function; otemplate is a template container: it contains the overall layout of the page template; ogroup is a field group container: it contains all field components of a field group; olabel is a label: it is used to display the name of the field; input is an input box: it is used for users to enter the value of the field, and the type is determined according to the data type of the field; In the dynamic model generation step, business logic and data processing flow are automatically generated according to the static data model and page model; through the generation of dynamic models, the workload of manual coding is reduced, the development efficiency is improved, and the consistency and reliability of business logic are ensured; in actual product scenarios, dynamic models are formed through the ideas of static data modeling and page modeling templates, and regular and model-compliant businesses are quickly copied and built; odynamicModel is a dynamic model: it contains dynamically generated business model information; modelCode is the model code: a code used to uniquely identify a dynamic model; modelName is the model name: the name of the model, used to describe the purpose of the model; dataModel is a data model: it contains data field information in the dynamic model; ofields is a field list: it contains all field information in the data model; fieldCode is the field code: the code of the field, which is consistent with the field code in the data model; fieldName is the field name: the name of the field, which is consistent with the field name in the data model; dataType is the data type: the data type of the field, which is consistent with the data type in the data model; isRequired is whether it is required: it indicates whether the field is required segment; opageModel is the page model: contains the page template information in the dynamic model; templateCode is the template code: the template code, which is consistent with the template code in the page template; templateName is the template name: the name of the template, which is consistent with the template name in the page template; details is the template details: contains the detailed information of the page template; groups is the field group: contains all the field group information in the page template; groupCode is the field group code: the field group code, which is consistent with the field group code in the page template; groupName is the field group name: the name of the field group, which is consistent with the field group name in the page template; viewVisiable is view visible: identifies whether the field group is visible in view mode; addEditVisiable is add / edit visible: identifies whether the field group is visible in add or edit mode; fields is the field list: contains all the field information in the field group; code is the field code: the field code, which is consistent with the field code in the data model; name is the field name: the name of the field, which is consistent with the field name in the data model; required is whether it is required: identifies whether the field is a required field; Provides template management functions, supporting the creation, modification, deletion and version control of data models and page templates; Configure business rules according to different business needs, including data verification rules, page display rules and business process rules.

2. The method for generating digital services based on a dynamic model according to claim 1, It is characterized in that In step S2, the content of the page configuration specifically includes: Template code, used to configure the code that identifies the page template and is a unique identifier; template name; template details, used to configure the detailed information of the displayed page template; remarks, used to configure the description of the page template; field group, used to configure the fields in the organization page; field list, used to configure all field information in the field group.

3. The method for generating digital services based on a dynamic model according to claim 2, It is characterized in that In the step S3, the page template uses the business type as the template identifier, and generates a dynamic business page template based on the static model and the content of the page configuration.

4. A system for generating digital services based on a dynamic model, the system being used to implement the method according to any one of claims 1 to 3, It is characterized in that The system includes: static data modeling module, page configuration module, template generation module and business generation module; The static data modeling module is used to perform static data modeling on the business fields of the database to obtain a static model; The page configuration module is used to configure the page layout, component configuration and interaction logic based on the static model; The template generation module is used to generate a dynamic business page template based on the static model and the content of the page configuration; The business generation module is used to obtain the dynamic business page template of the back end according to the business type, dynamically merge the page with the front-end page, form new page content, perform page rendering, and generate dynamic digital business.

5. The system for generating digital services based on dynamic models according to claim 4, It is characterized in that The business field content includes: field code, which is used to identify the field code and is a unique identifier; field name; data type, which is used to mark the data type of the field; whether it is required is used to identify whether it is a required field; remarks, which is used to fill in the remarks information of the pre-made field, and the pre-made field is a preset number of fields without business meaning.

6. The system for generating digital services based on dynamic models according to claim 4, It is characterized in that The content of the page configuration specifically includes: Template code, used to configure the code that identifies the page template and is a unique identifier; template name; template details, used to configure the detailed information of the displayed page template; remarks, used to configure the description of the page template; field group, used to configure the fields in the organization page; field list, used to configure all field information in the field group.

7. The system for generating digital services based on dynamic models according to claim 6, It is characterized in that The page template uses the business type as the template identifier and generates a dynamic business page template based on the static model and the content of the page configuration.