Update Attribute

1. Creating the Required Form in UI Design

• A Dynamic Form screen is prepared to display and edit the attribute data to be updated.
• Required elements:
  
  • Text Input → Name
  • Select Box → DataType
  • Text Input → Description (optional)
  • Switch / Checkbox → IsRequired
  • Text / Number Input → DefaultValue
  • SelectBox (or fixed) → CategoryId
  • Button → ‘Update’

2. Filling the Form with the Get Attribute Action

• When the page loads or an attribute is selected, the Get Attribute action is executed.
• The returned information is distributed to the Dynamic Form element (binding is performed).

3. Adding the Update Attribute Action

• When the ‘Update’ button is clicked:
  
  • + ADD ACTION > OnClick > EAV > Attribute > Update Attribute action is selected.
  • Parameters are taken from the Dynamic Form element:
    
    • Id → Symbol Picker > Action Result > Get Attribute > Id
    • Name → Symbol Picker > Form Component > Text Input
    • DataType → Symbol Picker > Form Component > SelectBox
    • Description → (optional)
    • IsRequired → (optional)
    • DefaultValue → (optional)
    • CategoryId → (optional)

4. Processing the Update Result

• After a successful operation, a notification can be displayed to the user via toast or modal.
• The Dynamic Form can be automatically cleared or the list can be updated.

An administrator wants to change the name, data type, or default value of an attribute previously defined in the system.

1. The admin selects an attribute from the attribute list.
2. The system displays the current information in the form using the Get Attribute action.
3. The admin makes the necessary changes (for example, changes the name from reference_count to reference_number and leaves it as Integer).
4. When the ‘Update’ button is clicked, the Update Attribute action runs and the attribute is updated in the system with its new values.

• Change Control: Only fields that are different between the old and new values can be updated.
• Validations: Checks such as empty fields, invalid data types, or conflicting names can be performed before the action.
• Conditional Updates: Update permissions can be granted based on specific user roles.

Technical Risks

• Missing Required Fields: The system does not perform the operation if Id, Name or DataType are not entered.
• Invalid Data Type: The system may return an error if an unsupported DataType is entered.
• Conflicting Names: The system may reject the update if there is another attribute with the same name under the same category.
• Beta Version Risk: The feature is in beta; unexpected behaviour may occur in some edge cases.

The Update Attribute action is used to ensure the sustainability of dynamic data structures on the Kuika platform. It allows users to quickly and securely edit attributes in the system. Although it is in beta, it offers powerful flexibility and manageability when configured correctly.