1. Entity Selection in the UI

• An area (e.g. a Select Box element) is added to allow the user to select an entity.

2. Action Definition

• Defined as follows to run when a button is clicked or the screen loads:
  
  • + ADD ACTION > OnClick > EAV > Entity Attribute Value > Get Entity Attribute Values

• Parameters are set:

• EntityId: Symbol Picker > Select Box, Component, or Action Result

On a customer details screen, you want to dynamically display all custom fields (e.g., ‘Membership Start Date,’ ‘Contact Preference,’ ‘Segment’) for that customer.

1. When a customer (entity) is selected, Get Entity Attribute Values runs.
2. The result is loaded into the dynamic form element.
3. The user sees all the information on a single screen and can edit it as needed.

‍

• Use with Dynamic Forms: This action usually works in conjunction with Get Entity Attributes. First, the attribute structure is retrieved, then the values.
• Caching/Storage: The retrieved values are stored in an Object Variable with Set Value and can be reused within the application.
• Conditional Display: The visibility or access of certain components can be controlled based on the retrieved values (If).

Technical Risks

• Missing EntityId: The action does not work if the parameter is empty or incorrect.
• Empty Result: If the entity does not yet contain an attribute value, the returned JSON may be empty.
• Data Type Mismatch: Ensure that the form elements of the retrieved values are compatible (e.g., linking a boolean value to a checkbox).
• Performance: The loading time of this action should be carefully tested for entities with a large number of attributes.

The Get Entity Attribute Values action is an effective tool in the Kuika platform for quickly and collectively retrieving entity-based data. It offers ideal solutions, especially in dynamic form scenarios or data detail screens where all attribute values need to be managed together.

‍