- 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.
