1. Defining the Action in UI Design

• Open your project on the Kuika platform.
• Go to the UI Design module.
• Select the screen where the attribute deletion will be performed.
• For example, create a button named “Delete Field.”

• To make it work when this button is clicked:+ ADD ACTION > OnClick > EAV > Attribute > Delete Attribute select the action.

2. Configure the Action Parameter

• Id: Symbol Picker > Component > Select Box or Text Input, Fixed or Action Result can be determined from sources such as these.

3. Removing the Attribute from the System

The attribute with the specified ID is permanently deleted from the system. As a result of this operation, the relevant attribute no longer exists in the application or database. If there is data associated with the attribute, system behavior may vary depending on the version and configuration (e.g., data cleanup or dependency checking).

In an e-commerce platform, product managers can customize product cards in the system according to their needs. For example, a field (attribute) named “Warranty Period” may have been defined for products in the electronics category. However, it is later decided that this information is sourced from an external source or business rules change.

In this case, the product manager sees the “Warranty Period” attribute in the list of fields in the management panel and clicks the “Delete” button next to it to remove this field from the system.

Id: 123e4567-e89b-12d3-a456-426614174000

As a result of this action, the relevant attribute is completely deleted from the system, and forms, data entries, or interface elements associated with this field are automatically updated. This ensures data integrity in the live system while removing unnecessary fields.

• Conditional Deletion: The attribute deletion process can be performed for specific user roles (e.g., only admin) or after approval is received.
• Approval Dialog: Since the deletion process cannot be undone, a modal or alert window can be displayed to request approval from the user.
• Dependency Check: If there is data dependent on the attribute to be deleted, a pre-check can be performed or the user can be notified.

Technical Risks

• Invalid or Missing ID: The system may encounter an error or the expected action may not be performed if an incorrect or empty ID value is entered.
• Data Loss: Historical data linked to the deleted attribute may be permanently lost from the system. Therefore, the results of the deletion action must be clearly indicated to the user.
• Beta Version Risk: The action is still in beta; it may produce unexpected results in some system scenarios.

The Delete Attribute action is a practical tool used to manage dynamic data models in a clean and controlled manner on the Kuika platform. The management of user-defined fields is important for the sustainability of the application. In live environments, it offers a structure that can be managed by end users. The EAV model allows new fields to be defined and existing structures to be flexibly adjusted without developer intervention, even while the system is in production. This enables users to define data fields specific to their business processes via the interface, enrich their forms, and customize their structures without system downtime.