After an entity is defined in Kuika, all attributes that may belong to this entity are defined with the Create Attribute action. Attributes are one of the building blocks of the EAV (Entity-Attribute-Value) model and enable the system to be dynamically extended.
For each attribute, a name, data type (e.g., String, Integer, Boolean), optional description, default value, and requirement status (IsRequired) can be defined.
For example, you are developing a CRM application and want users to be able to add custom fields to their customer cards. The user can create an attribute like the one below by clicking the “Add New Field” button:
As a result of this process, a mandatory (*) symbol is automatically added to the relevant dynamic form field in the user interface. The user cannot submit the form without filling in this field. This ensures data integrity and allows end users to define data fields suitable for their business processes while the system is running.
This example directly reflects the configurability feature provided by the EAV model in a live environment. A scenario that would require intervention in the database schema in traditional data structures can be resolved with a single action using Kuika's EAV-supported system, without the need for system downtime.
In conclusion, defining attributes in Kuika is not just about creating a feature, but also about giving end users the ability to build customized data structures. This is one of the most important elements supporting Kuika's dynamic, scalable, and sustainable application infrastructure.
