Data model

What is a data model?

Data model in the Eximee platform is a central element that describes the business data structure used in a low-code application. The model serves two functions

  • documentary, providing unambiguous information about the source of each field's value

  • technical, performing operations necessary to obtain values

The data model allows modeling the data structure in a tree structure. Each node of the tree represents a business domain object of the application, e.g., applicant, loan, or correspondence address. Each leaf of the tree denotes a single field that stores a specific value.

Each field of the model has a specified method of obtaining the value (so-called "data source"). Sources can compute data locally, based on default constant values, algorithms implemented in ScriptCode (e.g., PageService, ServiceTask, ...) and data entered manually by users (e.g., on fields of a loan application or in a credit analyst's task). Values can also be obtained remotely from services via REST API.

The data described in the model is stored in many places, not necessarily in Eximee platform components. The task of the data model is to fetch the values for each field from the indicated location at the appropriate time. Thus it is a component coordinating data acquisition, not only storing it.

Each low-code application has its own definition of the data model. There is no need to create a single, common "mega-model" covering all areas of the institution. The data model exists only in the context of the running application and is not global for the entire platform. This means that a separate instance of the data model is created for each running application (see Storing data in the model)

circle-info

A good data model can significantly facilitate the maintenance and development of the application. The ability to quickly verify the source of a given value is crucial when analyzing problems and when planning development changes in the application. Remember to use clear names for objects and fields, specific documentation in descriptions, and to update the model definition!

Last updated

Was this helpful?