n-aos Builder, Custom Structure

To make custom object and create customized user interface, n-aos Application Builder uses structured meta data.

Custom structure

Custom structure is descriptive data layer (meta data) that is applied to a functional database object, in order to adapt to the needs of the user interface and implement additional functionality over that object. Programming in n-aos Builder is reduced to minimum. Data-driven philosophy rules all the way, so structured meta data replaces classic coding.

Work with custom structure is realized in n-aos Builder, sub-module Customization.

Custom Structure is organized in three major data sets:

• Database object (presented in Parent section after you click on Custom object in tree view menu on left side),
• Custom object (presented in Main section after you click on Custom object in tree view menu on left side)
• Object fields (presented in Master/Details section after you click on any of record in main grid)

 

Database object carries the information:

1. functional object unique identification - Code, Name
2. database object type and list of database objects - one or more database tables or updatable views of which functional object is built
3. internal operations handling objects for executing CRUD operations over the functional object

Top

 

Custom object record carries the information about itself and custom structure where it is placed:

1. object unique identification - code, name,  order and description
2. link on functional database object that is subject of customization,
3. structural placing, presentation and relations with other objects,
   • group or module where the object belongs,
   • section position on which object appear in the interface, corresponds also with type of functional database object
     • folder or sub module - placeholder and top position in every structure,
     • main, parents, master/details, info, details - positions and relation attribute for recordset like functional database objects
     • action procedure - reserved for stored procedures for processing data, when used, generic functional objects for stored procedures must be selected,
     • ....
   • parent object code - the object in the same structure that drives this object in the interface (folder object drives objects in main section, main section objects drive all other objects from other sections)
   • page size as the number of visible records per page to display
4. functionalities to use in custom object, what operations will be carried out on the object,
5. internationalization, multilingual name and  multilingual description.

Top

Object  fields carries the informations about object columns:

1. custom object to which it belongs
2. column properties that comes from database object 
3. meta data properties that explains column behavior on the user interface

Top

 

 

 

 

---

Builder overviews:   |   DB modeling  |   Linked server  |   Customization  |   Create simple App  |   Share Apps  |   Settings  |   Interface  |   Custom structure  |   Linguist  |  

---