Ask AI
Skip to main content

Store list in scope

Function: Store list in scope

This action allows you to save a collection of items (a "list") into your application's memory, making it accessible for use in subsequent steps or actions. Think of it as giving a name to a specific list of data so you can easily refer to it later.

Input,

  • List: The collection of items you want to save. This can be a list of text, numbers, dates, or any other type of data.
    • Type: ARRAY
  • Result: The unique name you want to give to this list. This name will be used to retrieve the list later in your application. For example, you might name it "ProductIDs" or "CustomerEmails".
    • Type: VARIABLE (Text)

Output,

  • The provided List is stored and accessible throughout your application under the Result variable name.

Execution Flow,

Real-Life Examples,

Here are some practical ways you can use the "Store list in scope" action:

Example 1: Saving a list of selected product IDs

Imagine you have an e-commerce application where users can select multiple products to add to their cart. Before processing the cart, you want to store the IDs of these selected products.

  • Inputs:
    • List: ["P101", "P105", "P203"] (This list comes from the user's selections)
    • Result: "SelectedProductIDs"
  • Result: The list ["P101", "P105", "P203"] is now stored in your application under the name SelectedProductIDs. You can then use this variable in a subsequent action to fetch product details or add them to an order.

Example 2: Storing a list of email addresses for a newsletter

You have a form where users can enter multiple email addresses to subscribe to different newsletters. You want to collect all these emails into a single list for further processing.

Example 3: Keeping track of completed tasks

In a project management application, you might have a process that identifies all tasks that have been marked as "Completed" today. You want to store these tasks for a daily summary report.

  • Inputs:
    • List: ["Task A - Completed", "Task C - Completed", "Task F - Completed"] (This list is generated by another action that filters tasks)
    • Result: "DailyCompletedTasks"
  • Result: The list ["Task A - Completed", "Task C - Completed", "Task F - Completed"] is now stored as DailyCompletedTasks. This variable can then be used to display a summary on a dashboard or send out a daily progress report.