For the complete documentation index, see llms.txt. This page is also available as Markdown.

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 the low-code application. The model serves two functions:

  • a documentation function, providing unambiguous information about the source of each field's value,

  • a technical function, performing the operations necessary to retrieve the value.

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

Each model field has a defined way of obtaining its value (the so-called "data source"). Sources can calculate data locally, based on fixed default values, algorithms implemented in ScriptCode (e.g. PageService, ServiceTask, ...) and data entered manually by users (e.g. in loan application fields or in a credit analyst 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 retrieve the value for each field from the indicated place at the appropriate time. It is therefore a component coordinating data retrieval, not just storing them.

Each low-code application has its own data model definition. There is no need to create a single, shared "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)

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

Last updated

Was this helpful?