1. Defining Actions in UI Design
   
   • Log in to the Kuika platform.
   • Open the project you want to work on from the Apps screen.
   • Go to the UI Design module and select the relevant screen.
2. Adding Actions

• Add the List Collections action from the ADD ACTION menu according to the triggering event (Initial Actions, OnClick, OnBlur, etc.).

Scenario 1: Listing All Collections with SelectBox

• Purpose: To add all collection names in the Qdrant system to the Select Box list so that the user can select them.
• Steps:
  
  1. Add a SelectBox element to your project screen in UI Design.
  2. Then, add the List Collections action from the Add Action button on the right panel and select the Select Box data source (collectionsList) as the Target Variable.
  3. When the action is triggered, all collection names in Qdrant are automatically transferred to the dropdown.
• Expected Result: The user can select one of the existing collections from the Select Box.

Scenario 2: Collection-based search with dynamic search action

• Objective: Perform a dynamic search based on the collection selected by the user from the Select Box.
• Steps:
  
  1. The user selects a collection from the Select Box (filled with the List Collections action).
  2. The selected collection value is transferred to the Search action as a parameter.
  3. The Search action performs a search only in the selected collection and displays the results on the screen.
• Expected Result: The user can search only in the collection they are interested in; the system does not load unnecessary data.

Scenario 3: Dynamic Dropdown in Mobile Application

• Purpose: To give the user the right to select all collections in the mobile application.
• Steps:
  
  1. The List Collections action is triggered for the mobile screen (e.g., when the page loads).
  2. The collection list is presented to the user on mobile devices as a scrollable Select Box element.
  3. After the user makes a selection, other actions (Search, filtering, etc.) are performed on the selected collection.
• Expected Result: The mobile user experience is consistent with the web and interactive.

• Dynamic Action Chain: Listed collections can be automatically used in subsequent actions (e.g., Search action).
• Mobile Usage: The list can also be displayed to the user as a dropdown or selection list in mobile applications.

Technical Risks

• Empty Collection: If there is no collection in the Qdrant system, the action returns an empty list.
• Incorrect Target Variable: If the target variable is not defined correctly, the list transfer fails.