Log In
Home
Support
Demos
Documentation
Blogs
Training
Webinars
[Expand]General Information
[Expand]WinForms Controls
[Expand]ASP.NET Controls and MVC Extensions
[Expand]ASP.NET Bootstrap Controls
[Expand]WPF Controls
[Expand]Xamarin Controls
[Expand]Windows 10 App Controls
[Expand]Document Server
[Expand]Reporting
[Expand]Report Server
[Expand]Dashboard
[Collapse]eXpressApp Framework
 [Expand]Fundamentals
 [Expand]Getting Started
 [Collapse]Concepts
  [Expand]Application Solution Components
  [Expand]Business Model Design
  [Collapse]Application Model
   [Expand]Model Editor
    Application Model Basics
    Business Model in the Application Model
    Application Model Structure
    Access the Application Model in Code
    Extend and Customize the Application Model in Code
    Built-in Nodes Generators
    Convert Application Model Differences
    Model Difference Storages
  [Expand]UI Construction
  [Expand]Extend Functionality
  [Expand]Data Manipulation and Business Logic
  [Expand]Security System
  [Expand]Localization
  [Expand]System Module
  [Expand]Extra Modules
  [Expand]Debugging and Error Handling
  [Expand]Filtering
  [Expand]Application Life Cycle
 [Expand]Design-Time Features
 [Expand]Functional Testing
 [Expand]Deployment
 [Expand]Task-Based Help
 [Expand]Frequently Asked Questions
 [Expand]API Reference
[Expand]CodeRush
[Expand]Cross-Platform Core Libraries
[Expand]Tools and Utilities
 End-User Documentation

Business Model in the Application Model

With the eXpressApp Framework, only the business model has to be implemented when building a business application. Views for each business class from the business model will be generated automatically. For this purpose, special nodes are created in the Application Model: IModelBOModel, IModelDetailView and IModelListView. This topic explains how the information from the business model is used to generate these nodes. This can be helpful when you analyze or edit the Application Model.

The following diagram demonstrates the information flow from the business model through the Application Model:

Note

By default, Lookup List Views contain a single column that corresponds to the property specified by the IModelClass.DefaultProperty property of the IModelClass node.

The Layout Groups and Items are generated according to specific rules. Property Editors for particular data types are related to particular Layout Groups. This relation is explained in the following table:

Property Type

Layout Group

Collection Individual Layout Group (if a Detail View contains a single collection)
Tabbed Group (if a Detail View contains several collections)
Value type Individual Layout Group called SimpleEditors. If there are more than four Property Editors in the current Detail View, they are located in two columns.
Other Individual Layout Group called SizableEditors.
Note

The Property Editors for the base class properties are distributed between individual Layout Groups as well.

Expanded See Also

How would you rate this topic?​​​​​​​