1. Define the Action in UI Design

• Open your project on the Kuika platform.
• Go to the UI Design module.
• Select the screen where you want to create a new attribute.
• For example, create a button named “Create Field.”

• To make it work when clicked: + ADD ACTION > OnClick > EAV > Attribute > Create Attribute.

2. Configuring Action Parameters

Action parameters can be defined dynamically or statically using the Symbol Picker tool. Below are example definition methods and usage purposes for each parameter:

• Name (Required):The text field where the user writes the attribute name via the form.
  
  • Symbol Picker > Form Component > Text Input
  • Example: “reference_number”
• DataType (Required): This parameter determines the data type of the attribute. It must be assigned a fixed value.
  
  • Symbol Picker > Fixed > ‘String’ (or “Integer,” “Decimal,” “Boolean,” etc., depending on the supported data types)
  • Example: “Integer”
• Description (Optional): Text field where the user can enter a description about the attribute.
  
  • Symbol Picker > Form Component > Text Input
  • Example: “Specifies the number of references for the person”
• CategoryId (Optional): The category ID to which the attribute belongs can be a fixed value or the user can make a selection.
  
  • Symbol Picker > Fixed > Guid or Symbol Picker > Component > SelectBox
  • Example: “cd253d3b-6a9a-48d2-afe7-e8303f2e9094”
• IsRequired (Optional): This field determines whether the attribute is required.
  
  • It can be set to true/false or the user can select a key.
  • Symbol Picker > Fixed > true/false or Component > Switch
  • Example: true
• DefaultValue (Optional): The default value of the attribute. It can be set to a fixed value or taken from user input.
  
  • Symbol Picker > Fixed or Component > Text/Number Input
  • Example: 0 (for Integer) or “Unknown” (for String)

3. Creating an Attribute in the System

Based on the defined parameters, a new attribute record is created in the system. This process allows customized data entry without changing the database schema.

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:

• Name: reference_number
• DataType: Integer
• IsRequired: true
• DefaultValue: 0

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.

• Conditional Creation: The attribute creation process can be made conditional based on specific user roles or screen statuses.
• Validation: If an attribute with the same name already exists, the system can display an error message.
• Automatic Category Assignment: CategoryId can be automatically determined based on specific screens.

Technical Risks

• Duplicate Names: Multiple Attributes with the same Name value should not be defined in the system. Technically, the system may not always prevent this directly with a conflict error, but it can lead to inconsistencies in the data model and administrative complexity. Therefore, it is important to define a unique and meaningful Name value for each Attribute. On the other hand, an Attribute defined once can be associated with multiple Entities (entities). For example, an Attribute named “screen_size” can be used for both Phone and Computer Entities. This reflects the reusability of features offered by the EAV model. Rather than redefining the same property in different entity types, defining it centrally once and mapping it to different Entities preserves consistency in the system and reduces maintenance costs. Therefore, when determining the Name field, it is necessary to consider not only the technical name of the Attribute in the system, but also its reusability.
• Invalid Data Type: Only data types supported by the system should be entered as DataType.
• Missing Required Fields: The Name and DataType fields must not be left blank.
• Beta Version Risk: The feature is still in beta; some behaviors may be unstable.

The Create Attribute action is an important component that enhances the dynamic data modeling capabilities of the Kuika platform. In live environments, it provides a structure that can be managed by end users. The EAV model allows new fields to be defined and existing structures to be flexibly modified without developer intervention, even while the system is in production. This enables users to define data fields specific to their business processes through the interface, enrich their forms, and customize their structures without system downtime.