
Kuika's Auto Complete element allows users to quickly receive suggestions during text entry. When users start typing text, they are automatically presented with appropriate suggestions from a predefined list of data. In this guide, you will learn how to use the Auto Complete element and how to configure the list of suggestions.

You can configure the following settings in the Properties panel:

The Auto Complete element supports the definition of event-based actions based on user interactions. Actions are not linked to the element itself, but to events triggered by user inputs and selections.
Actions for the Auto Complete element can be added via the Properties > Add Action area using the following events.
Supported Action Triggers
onSearch: Triggered when the user performs a search. Also works when the search text is cleared.
Purposes:
Example scenario: As the user types a city name, matching cities are retrieved from the API and displayed in a list.
onSelect: Triggered whenever the user makes a selection.
Uses:
Example scenario: When the user selects a product, the product details are automatically written to the relevant fields.
onChange: Triggered only when the selected item changes.
Uses:
onBlur: Triggered when the user loses focus from the Auto Complete field.
Uses:
getTextFromValue: Used to obtain the text to be displayed from the selected value.
Purpose:
Example scenario: Displaying the First Name and Last Name information as text with user_id as the Value.
Basic Rules Regarding Actions
The Auto Complete element provides a powerful and flexible user experience when used with actions, especially in scenarios involving search, filtering, and selection from large data sets.

By following this guide, you can use the Auto Complete element effectively in your application.
Authorization

To manage access control at the element level, you can use the Authorization section in the Properties panel.
Access Types
Anonymous
Allows all users to view the element without logging in.
Restricted
Restricts access to only verified users or specific roles.
Unauthorized Behavior (Hide / Disable)
If the user does not have the required role, you can specify how the element should behave in the Choose field:
This setting is used to manage how unauthorized users encounter the element.
Visibility

Always Visible: The element is always visible.
Hidden: The element is hidden.
Sometimes Visible: The element becomes visible based on specific conditions.
When Sometimes Visible is used, AND / OR groups can be added directly, allowing visibility rules to be grouped and more complex scenarios to be managed easily.
To configure the setting:


By customizing your elements with the Styling Panel, you can create impressive interfaces for your web and mobile applications. In this section, you can configure the following settings:
By following these steps, you can configure the Area Chart element to suit your needs.