Models describe the second or child level in the record structure of tables and table types. The configuration entries in a Model Configuration relate to Service and Collection records in many ways. You will find sections entitled Common, Fields, the Service used by this Model (such as a datagrid or calendar), definitions for forms, views and reports.

All of this refers to the fact that the Class → Model takes three arguments for Model→stdModel(service, table, tabletype = ‘’) and that as the cascading takes place, Model overwrites Collection overwrites Service. As a matter of selection we have chosen Javascript utilities such as Gijgo (grid and tree), jqTree and Datatables where the options sent to the Javascript utility can ignore or throwaway, option keys and values that it does not need.

Models equate to tabletypes for a given table. Thus they are displayed as Bootstrap cards as they tend to have longer references and descriptions.

All that has been explained in the pages for Services and Collections, apply to Models. Only the way that the database records are displayed on the screen is different in that it uses one of the two native Bootstrap 4 mechanisms for displaying lists (list or card) and in this case a Datacard.

Lists and Datacard show off the way that Cliqon utilises the Vue javascript framework. Cliqon does not use or push Vue to the limit of what can be achieved with Vue. Datacard and Datalist are examples of the hybrid template approach that is used throughout much of Cliqon administration and will probably be used for web site presentation.

Created with the Personal Edition of HelpNDoc: Free HTML Help documentation generator