1. Core Technologies
1.1 metadata
Element Data is a general term. From the perspective of software display, forms, tabs, fields, data storage, including tables and columns, and logical processing, including processing and callback, the definition and application of each element are described in detail on the tap development platform.
1.2 function Engine
The function engine is designed for this development framework to facilitate flexible system expansion. The default value definition, dynamic SQL, and processing logic can be referenced, including string parsing. For example, ## org. getleid () ## indicates obtaining the current Logon account number. Function engines can include variables and functions.
1.2.1 server function syntax
In this framework, the function appears in the form of "##+ function body + ##". The function body includes the function name and method name. The method can contain N parameters, n> = 0, and the parameter must be referenced by '', and separated by commas (,). For example:
# System. DQC ('and ad_window_id =' {0} '', '1', 'ad _ window_id ')##.
1.2.2 server Variables
@ Ad_window_id @@
1.2.3 client Variables
@ Ad_window_id @
1.3 Common default values
Organization number: @ adorgid @@
Subsystem ID: @ adsubsystemid @@
1.4 Processing Engine
In order to expand and coordinate the logic and interface interaction between servers and clients, the system basically completes processing through servers or clients. The processing types include table processing, workflow processing, column processing, and form processing, you can also set processing parameters to run on servers or clients.
1.5 workflow engine
The Pam subsystem provided in this framework provides support for Microsoft WWF and visual process settings.
1.6 Data Access Engine
The database access engine of this framework integrates spring. Net ADO and nhib.pdf based on the general development mode features of the platform to provide unified data processing support.