Database-based enterprise-level intelligent form system design (Asp.net)-Architecture

In the last article, the database-based enterprise-level intelligent form system design (Asp.net)-Architecture

Here we only discuss the architecture related to the form, and the workflow and system infrastructure is not included in this article.

The smart form system consists of the following parts:

• Form Designer
• Form Engine
• Data Engine
• Statistics Engine
• ProjectSource code
• Basic Database

 

As shown in:

 

 

 

2.1 function of Form Designer:

L provides a WYSIWYG Visual Form Designer based on the web method.

L provides various built-in controls, such as text boxes, drop-down boxes, and subtables.

L field attribute settings are provided.

L provides form attribute settings.

L provides permission configuration.

L provides a style designer.

 

 

2.2 role of the Data Engine:

L automatically generate the corresponding background database table based on the forms designed by the Form Designer (including the implementation of multiple databases)

L modifications made by the user through the Form Designer are synchronized to the background database.

L used as a data provider for Database Exchange with databases.

 

2.3 functions of the form engine:

L convert user-designed forms into Asp.net sourcesCodeSave the file.

L convert the Form file in Asp.net format into a format that can be read by the Form Designer, and then display it to the customer in Web mode for design modification.

L in vs.net, the form engine converts controls into formats that vs.net can understand, so that customers can perform secondary development in vs.net. Greatly reduces learning costs and provides work efficiency.

L when a user accesses a smart form through a browser, the form engine performs parsing and generates HTML code to return it to the customer.

L control form permissions.

L records form operation logs.

2.4 unified entrance

The unified portal provides users with a simple way to access system forms, and puts complex operations to the background system for automatic processing. For user access, you only need to provide parameters for a form. There are two main parameters:

L form ID. It is used to determine the form that a user accesses. It is the unique value of a system that the user saves after designing the policy.

L record ID. Used to uniquely identify the data to be accessed.

There are several access modes for smart forms:

L access list: to access the data list of a form, you only need to pass the parameter of a form ID, the system will return records of this form (the form engine will judge and filter data based on permissions ).

L new record: the user needs to pass the Form ID and a record ID with a null value. The system will return the interface for adding a record to the form.

L modify record: You need to pass the Form ID and record ID. The system will return the interface of the form modification record.

2.5 basic database

The basic database provides users with information about form configuration and saves user form records. It mainly includes the following parts:

L form configuration information table: This table is used to save information about the user-designed form, including the form name, database table name, and permission information.

L field configuration information table: This table is used to save information about the control you designed, including the control name, the field name of the control in the database, and verification information.

L control type table: describes the types and functions of each control.

L data type table: the data type description of an abstract field. It is used to automatically generate the field data types of each database when mapped to different databases.

2.6 project source code

The source code is a vs.net project and is a secondary development framework of the entire system. One part is the form source code file designed by the user. You can perform secondary development on the form source code file in vs.net. The project source code file is a standard Asp.net file, which has the following advantages:

L using vs.net as a secondary development tool rather than using the tools provided by myself is a very familiar development environment for users, and vs.net provides very powerful functions, far from ordinary companies can develop.

L use the standard Asp.net file as the storage medium for form source code files, so that users can use various technologies they are familiar with, including HTML, Asp.net, JavaScript, and CSS for secondary development, this greatly reduces users' learning costs.

L because source code files are generated, there are basically no restrictions on Secondary Development of smart forms.

(To be continued)