TABLE OF CONTENTS

• Sending Data to the App vs Keeping It in the Sequence
• Overriding Data Set Input Parameters
  • Example: Evaluating Data Sets in Parallel API Calls 

When you use the Evaluate a data set step in an action sequence, you can choose whether the result is sent to the App for use elsewhere or kept within the Action Sequence. This behavior is managed through the Make result available to app toggle.

Sending Data to the App vs Keeping It in the Sequence

When the Make result available to app toggle is enabled (default):

• The result of the evaluation updates the App's Data Set, allowing other Data Sets and Components to use it.
• The result is visible in both the Data evaluations and Data sets tabs in the console.
• The data set can be referenced anywhere in the App using its name.
• Any data sets that depend on this one will automatically re-evaluate, if configured to do so.

When the toggle is disabled, meaning the result of the data set evaluation can only be used within the current Action Sequence:

• The evaluated result is not made available to the rest of the App.
• The result does not appear in the Data sets tab but is visible in the Data evaluations tab for that action sequence.
• The current evaluation result cannot be referenced by name elsewhere in the App. Any references will display the most recent app-level data for that data set instead.
• Dependent data sets will not run automatically, even if configured to.
• The result is still available for use within the Action Sequence using the step name: {{stepName.result}}.

Additionally, when multiple Action Sequences run simultaneously and evaluate data sets, data set evaluations are processed sequentially. However, if the toggle is disabled, the data set is evaluated immediately within the sequence without waiting for other sequences’ data set evaluations to complete. 

Overriding Data Set Input Parameters

When you evaluate a data set in an Action Sequence, you can override the input parameter values defined in the data set’s configuration. 

Overrides can use:

• Values from Action Sequence input variables.
• The results of other steps in the sequence (including those with Make result available to app turned off).
• Other data expressions.

Example: Evaluating Data Sets in Parallel API Calls 

This example shows how to configure an Action Sequence that makes two parallel API calls: one to fetch users and one to fetch posts without sending the results to the App. Then, a third step combines the results from each sequence and stores the combined data for use throughout the App.

In this sequence:

• getUsers and getPosts run in parallel inside a group. Both have Make result available to app set to Off, so their outputs remain within the sequence.
• The combineUsersAndPosts step runs after the group. It combines the getUsers and getPosts outputs into a single data set for use later in the sequence.
• The combineUsersAndPosts step has Make result available to app set to On, which means its combined result is made available to the App and can be referenced anywhere.
• This step uses input parameter overrides to pass in the outputs from the first two steps:
  • users → {{getUsers.result}}
  • posts → {{getPosts.result}}
    
    Important: Here, getUsers and getPosts are the names of the previous steps, not the data set names. 

Because the first two steps do not make their results available to the App, they do not update data accessible throughout the App or trigger dependent data sets. The combined result from the third step, however, is available to other components or data sets across the App.