Get answer list from template ui element

Function: Get Answer List from Template UI Element

This action helps you extract a list of answers or values from a specific part of a UI element that was created using a template. It's useful when you need to collect data entered by users within a complex form, survey, or any other interactive component built with reusable template parts.

Input

• UI element: The main visual component on your page (like a form, a section, or a custom widget) that was built using a template. You need to specify which of these template-based components you want to work with.
• Sub UI element: A specific part or field inside the main UI element (e.g., a text box, a dropdown, a checkbox group, or a list of items) from which you want to retrieve the answers. You'll identify this by its unique code or name, which is typically set when the template component is designed.

Output

• Answer: A list of text values collected from the specified "Sub UI element". This list will be stored in a variable you define, ready for further use in your application, such as saving to a database, displaying elsewhere, or using in calculations.

Execution Flow

Real-Life Examples

Here are some real-life scenarios demonstrating how to use the "Get Answer List from Template UI Element" action:

Example 1: Collecting Multiple Choices from a Survey

Imagine you have a customer feedback survey built using a template, and one question asks users to select multiple features they like from a list of checkboxes.

• Inputs:
  • UI element: Customer Feedback Form (This refers to the entire survey form on your page.)
  • Sub UI element: Preferred_Features_Checkbox_Group (This is the specific group of checkboxes within the survey form.)
• Result: A list of selected feature names (e.g., ["Feature A", "Feature C", "Feature E"]) is stored in a variable named selectedFeatures. You can then save this list to your database.

Example 2: Gathering Items from a Dynamic Order List

Suppose you have an order entry screen where users can add multiple products, and each product entry is a sub-component of a larger "Order Details" template. You want to get a list of all product IDs entered.

• Inputs:
  • UI element: Order Details Section (This is the main section on your page where all product entries are listed.)
  • Sub UI element: Product_ID_Input_Fields (This refers to all the individual input fields for product IDs within the order details section.)
• Result: A list of product IDs (e.g., ["PROD001", "PROD005", "PROD012"]) is stored in a variable named orderedProductIDs. This list can be used to process the order.

Example 3: Retrieving Selected Tags from a Content Editor

You're building a content management system, and users can add multiple tags to an article using a template-based tag selector component. You need to retrieve all the tags they've chosen.

• Inputs:
  • UI element: Article Editor Template (This is the overall template used for editing an article.)
  • Sub UI element: Article_Tags_MultiSelect (This is the specific multi-select dropdown or tag input field within the editor.)
• Result: A list of selected tags (e.g., ["Marketing", "SEO", "Content Strategy"]) is stored in a variable named articleTags. This list can then be associated with the article when it's saved.