Skip to main content
An analysis lets you build interactive dashboards on top of your pipelines. Choose how you want to create your analysis:
  • Use the Agent for a faster, automated workflow
  • Create manually for full control over the dashboard

Overview

Use the Agent to automatically generate a pipeline and analysis from a prompt.

Add source data

Add a dataset to your pipeline:
  1. Open the Source/Target gem category.
  2. Click Table.
  3. Open the gem and select + New Table.
  4. Choose Seed as the type.
  5. Name the dataset home_tech_transactions.
  6. Paste your data and click Load Data.
  7. Click Save.

Generate an analysis

In the Chat interface, enter a prompt:
Visualize sales performance per product category in @home_tech_transactions
The Agent will:
  • Transform the data
  • Create a visualization
  • Generate a pipeline
  • Create a linked analysis dashboard

Continue building

You can continue prompting the Agent to:
  • Add new visualizations
  • Modify transformations
  • Expand the dashboard

Add interactive components

To add interactive components to the analysis, you’ll need to embed a pipeline parameter in the pipeline. Pipeline parameters enable dynamic behavior in pipelines by allowing values to be set at runtime. In this case, pipeline parameter values are set by the end user when they run the analysis.

Create a pipeline parameter

In this section, you’ll define a pipeline parameter called region. The parameter will capture the region that the user selects, allowing the pipeline to filter transactions based on the region the user wants to see.
  1. Open the pipeline tied to the analysis.
  2. Click default in the project header to open the parameter settings.
  3. Open the Pipeline Parameters tab.
  4. In the default parameter set, click + Add Parameter.
  5. Name the parameter region.
  6. Set the parameter type to String.
  7. Click Select expression > Value.
  8. Enter North as the default value to be used during interactive pipeline runs.
  9. Click Save.

Add a filter

Next, add a Filter gem to the pipeline. To make the filter condition dynamic, you’ll use the pipeline parameter in the gem.
  1. Add a Filter gem directly after the Source gem and before the next gem (generated by the Agent).
  2. Open the Filter gem configuration.
  3. For the filter condition:
    • Click Select expression > Column and select the Region column.
    • Click Select operator and select equals.
    • Click Select expression > Configuration Variable and select the region parameter.
    Configure visual expression to use
parameter
    This expression is equivalent to Region = {{ var('region') }} in the Code view.
  4. Click Save.

Add a Text Input component

Add a Text Input component to allow the end user to enter the region they want to see.
  1. Open the analysis dashboard that the Agent created.
  2. Click Edit.
  3. Open the Interactive dropdown and select Text Input.
  4. In the Inspect tab, for the Configuration field, select the region parameter.
  5. For the Label, enter Region.
  6. Drag the Text Input component above the bar chart visualization.
For full configuration options, see Analysis components.

Run the analysis

Let’s return to the analysis preview so we can test the new component.
  1. From the analysis, click Back to Preview.
  2. In the Region field, enter West.
  3. Click the Run button.
  4. Review the bar chart to see the total sales by product category for the West region.
When the analysis runs, Prophecy always executes the entire underlying pipeline. This means any additional transformations, tables, or other components included in the pipeline will also run, even if they’re not exposed in the dashboard. Be mindful of how you design the pipeline to ensure your dashboard triggers only the intended logic.

Share the dashboard

Access to analyses is controlled by Prophecy’s team-based permission model. If your team owns a project, you have full edit access. This means that you can build, edit, and delete analyses in the project. If a project is shared with your team, you cannot edit any pipeline’s or analysis’s structure. However, you can run analyses from the shared project. This ensures that your data engineering team can share pipelines they developed without exposing them to changes.
To learn more, reference the documentation on team-based access.

What’s next

To address your specific business requirements, leverage more complex components to construct robust analysis dashboards. To learn about the end user experience, see consume analyses.