Recipes

Why Recipes Matter

Ad-hoc analysis provides quick insights, but repeating the same steps manually is inefficient. Recipes capture the entire workflow, datasets, joins, AI enrichments, and visualizations. A saved recipe can be rerun with fresh data, reused internally, or shared through the Marketplace in Public deployments.

What Can Be Done with Recipes

• Save analysis sessions, including datasets, joins, AI enrichments, and outputs

• Assign a descriptive name and purpose

• Store ingredients (datasets metadata) and steps (queries, prompts, enrichments)

• Reuse workflows without retyping instructions

• Publish recipes to the Marketplace for wider adoption

Use Case & Real-Life Scenario

After completing a product returns analysis by joining orders and returns, calculating return rates, categorizing products, and applying sentiment analysis, the workflow was saved for reuse within the company.

Recipe Name: Product Returns & Sentiment Analysis

Description: Analyzes return rates, classifies high-return products, and correlates with customer sentiment

Ingredients: orders, returns, customer_reviews

Steps:

• Join orders and returns on order_id

• Calculate return_rate column

• Classify products into High/Medium/Low return categories

• Apply sentiment analysis on customer reviews (sentiment_label)

• Generate a bar chart of returns vs. sentiment

• The recipe is saved to the Recipe Catalog for future reuse.

Create, Save, and Share Recipes

Store a Thread as a Recipe

In askEdgi, any analytical conversation thread can be converted into a reusable Recipe. This conversion preserves queries, logic, and visualizations in a structured, step-based format. Storing a thread as a recipe enables repeatable analysis, sharing, and publishing in the Marketplace.

Steps to Store a Thread as a Recipe

1. Open the Threads panel.

2. Select the required thread (e.g., Sales Analysis).

3. Click Save as Recipe.

   
4. Provide recipe details:

   1. Recipe Name

   2. Description

   3. Ingredients (datasets/tables)

5. Review automatically captured steps (each query is represented as a step).

6. Add or edit analysis type, question, and source code if required.

7. Save the recipe under My Recipes.

   

Ingredients

Ingredients represent data objects added to the workspace, such as tables or files. Ingredients are optional and can be included in a recipe based on the requirement.

A recipe can run with any data object added to the workspace. Execution requires at least one valid data object in the data catalog or workspace.

Usage

Aspect	Summary
Execution	Requires a data object present in the workspace.
Marketplace	Recipes can be published without predefined ingredients.

Scenarios

Scenario	Ingredient Status
Specific data required, such as service request analysis	Ingredients required.
Flexible logic, such as data quality evaluation	Ingredients optional.

• Execution depends on the availability of at least one data object.

• Optional ingredients enable broader reuse of recipes across data environments.

Recipes (Enterprise Edition)

In the Enterprise (SaaS) Edition of askEdgi, recipes serve as reusable analytical workflows that capture data queries, joins, enrichments, and visualizations. Similar to the Public Edition, users can save analytical threads as recipes. However, Enterprise recipes are governed by organizational access controls and internal sharing policies.

Enterprise users work within a secure environment where recipes can be:

• Created and stored under individual workspaces.

• Shared internally within the organization.

• Listed for reuse by peers through the Organisation section.

Unlike Public Edition, where recipes are published to the open Marketplace, Enterprise Edition enables internal collaboration through Organisation Recipes.

Recipe Workspace

The Recipes section is divided into two tabs:

Tab	Purpose	Contents
My Recipes	Displays recipes created by the logged-in user.	- Recipes created by the user.- Recipes imported from the Public Marketplace (if enabled by admin).
Organisation	Shared internal repository for all enterprise users.	- Recipes listed by the user to the organization.- Recipes created and shared by other internal users.

Listing a Recipe to Organisation

Enterprise users can share their saved recipes with peers by listing them to the Organisation tab.

Steps to List a Recipe

1. Click the Organisation tab.

2. Click List to Organisation.

3. Select a saved recipe.

4. Click Submit.

   

Once listed:

• The recipe becomes visible under Organisation for other users within the same tenant.

• Peers can view, reuse, and run the recipe as per access control.

• Ownership remains with the original creator, but execution is allowed for other authorized roles.

Using Organisation Recipes

The Organisation tab acts as a shared internal Marketplace for enterprise users.

Users can:

• Access internal recipes created by other team members.

• Execute them directly in your workspace.

This ensures consistency in data interpretation, KPI computation, and AI enrichments across teams.

Example Scenario

A business analyst creates a recipe named Customer Retention Dashboard using customer and transaction tables. After validating results, the analyst lists it to Organisation, enabling the marketing and analytics teams to reuse it for their own segments without recreating the workflow.

My Recipes View: Shows the analyst’s saved version. Organisation View: Displays all shared recipes including “Customer Retention Dashboard” for other users to reuse or adapt.

Marketplace Access (Optional)

Enterprise instances can optionally use the recipes from Public Marketplace.

• Users can add recipes from the Public Marketplace into My Recipes.

  • In My recipe tab (default), click on the + Add Recipe from Marketplace button. A pop-up window (Add Recipe from Marketplace) will appear.

  • In the pop-up window, paste the recipe token and click on Save.

  
• Public recipes run within the constraints of the user’s data access and edition (Data Analytics or Metadata Analytics).

• Metadata-only tenants can execute Marketplace recipes limited to the OvalEdge (-1) connector.

Deterministic Recipe Execution Behavior

askEdgi recipes follow deterministic execution principles to ensure reliable, repeatable, and governance aligned outcomes. The execution framework eliminates automated corrections and enforces explicit validation before processing.

Execution Principles

Recipe execution follows these rules:

• Execution proceeds only when required workspace inputs are available • Structural validation occurs before execution begins • Execution stops immediately when an error occurs • Exact error details are displayed to the user • Automatic retries or runtime corrections do not occur

If required inputs are missing, askEdgi transitions to a controlled discovery step that surfaces matching catalog assets for confirmation before execution continues.

Predictability and Governance

Deterministic execution ensures:

• Stable and repeatable outcomes across executions

• Clear visibility into execution failures

• Improved trust in analytical workflows

• Alignment with governance and validation controls

Recipe creation and triggering behavior remain unchanged. Only execution behavior follows the deterministic model.

Listing a Recipe on the Marketplace (Public Only)

Saved recipes can be published as reusable assets in the Marketplace. This transforms private analysis into a reusable community asset.

OvalEdge Public: https://askedgi.ovaledge.cloud/#nav/askEdgi

MARKETPLACE LINK: marketplace.ovaledge.com

Steps to List a Recipe

1. Go to My Recipes in the Recipe Catalog.

2. Select the recipe and choose List to Marketplace.

3. Click the Marketplace Edit link.

   

   
4. Fill in the Marketplace Edit Form with the following details:

   1. Basic Information

      1. Recipe Name* – Enter a clear, descriptive title.

      2. Recipe Slug* – Provide a unique identifier for the recipe URL (auto-generated, editable).

      3. Description* – Add a detailed explanation of the recipe's purpose and insights generated.

      4. Recipe Guide – Include step-by-step instructions or notes for execution.

   2. Seller Information

      1. Seller Support* – Provide your contact details (email or support link).

      2. LinkedIn Profile (Optional) – Add a professional profile link for credibility.

   3. Pricing

      1. Pricing Type* – Select Free or Paid.

      2. Per Execution Price (USD)* – If Paid, specify price per execution.

   4. Categories

      1. Industry* – Select the relevant sector (e.g., Retail, Finance, Healthcare).

      2. Application* – Identify the business application (e.g., Product Returns, Customer Sentiment).

      3. Others – Add additional applicable categories.

   5. Tags

      1. Enter keywords separated by commas (e.g., returns, sentiment, quality) to improve discoverability.

      

Publish Workflow

1. Click Request to Publish.

   
2. The recipe is submitted for review.

3. The OvalEdge admin team verifies the quality, completeness, and compliance of all submissions.

4. Upon approval, the recipe becomes publicly available in the OvalEdge Marketplace for browsing, subscription, and reuse.

   1. Basic Information: Recipe Name, Slug, Description, Guide

   2. Seller Information: Contact details, optional LinkedIn profile

   3. Pricing: Free or Paid, with per-execution price if applicable

   4. Categories: Industry, Application, additional categories

   5. Tags: Keywords to improve discoverability

5. Submit recipe for review.

6. After verification, the recipe is published and becomes available to other users for subscription and reuse.

   

Executing a Recipe in askEdgi

The following steps describe the process of executing a recipe in the askEdgi Public environment.

• Access the Recipe from Marketplace

  • Navigate to the Marketplace section where all published recipes are displayed.

  • Click on a recipe card to open its Recipe Details screen.

  • On this screen, users can view the recipe’s description, verification status, associated tags, and pricing details.

  • Once reviewed, click on the Get Recipe button to proceed. A pop-up window will appear displaying the Recipe Token.

• Copy the Recipe Token

  • Copy the Recipe Token displayed in the pop-up. This token uniquely identifies the selected recipe for execution within askEdgi.

• Open the Execute Recipe Panel

  • In the chat interface, click on the Execute Recipe icon located beside the Send button.

  • Or click on the “+Add Recipe from Markeplace” button in My Recipe tab.

  • The Add Recipe from Marketplace pop-up will appear.

    
• Paste the Recipe Token

  • Paste the copied Recipe Token into the input field within the My Recipe pop-up.

    
• Execute the Recipe

  • Click on the Execute button to run the recipe.

  • askEdgi will process the recipe and display the results directly in the chat interface.

• View Executed Recipe in Threads

  • Once executed, the recipe and its output are automatically saved and can be viewed in the Threads section.

  • This allows users to revisit or reuse the executed recipe as part of their ongoing workspace history.

Recipe Functionality Across Deployment Variants

Recipe functionality in askEdgi varies across deployment variants based on the operational model, governance layer, and analytics scope. Each variant defines how recipes are created, executed, and shared, as well as the level of access granted to the Marketplace.

Public Edition

The Public Edition provides recipe functionality tailored for open exploration and learning. Recipes can be created directly within the workspace using uploaded datasets or publicly available data assets. Once created, recipes can be executed seamlessly on the same datasets to generate insights or analytical outputs.

Full access to the Public Marketplace is enabled in this edition. Recipes can be published, shared, and monetized by contributors, promoting community-driven innovation. Public users can earn through shared recipes and collaborate through Marketplace exchanges.

Supported Scope: This edition supports operations on publicly available data and locally uploaded files. Enterprise connectors and internal data catalog integrations are not included in this variant.

All activities in the Public Edition are governed through secure and temporary workspaces that maintain session isolation and data privacy, even within shared environments.

SaaS - Data Analytics (Insights & Analytics)

The SaaS Data Analytics variant delivers complete recipe functionality for enterprise environments. It enables full recipe creation, execution, and internal sharing among organizational users.

All recipe types—including data analytics recipes and metadata analytics recipes—can be executed within governed environments. This variant ensures secure integration with multiple data sources through available connectors, supporting advanced data and metadata analysis.

Recipes created in this edition can be shared internally within the organization. Access to recipes from the Public Marketplace is permitted but remains configurable based on enterprise policy and governance settings.

Supported Scope: All available connectors, uploaded files, and catalog tables are supported for recipe creation and execution, ensuring comprehensive analytical coverage.

Recipe execution follows enterprise-grade governance protocols and is subject to access control and audit validation through the organization’s RBAC (Role-Based Access Control) structure.

SaaS - Metadata Analytics

The SaaS Metadata Analytics variant focuses primarily on metadata-driven recipe creation and execution. Recipes in this environment are designed to operate on catalog metadata, enabling organizations to generate insights on data assets, lineage, classification, and data quality using metadata-level intelligence.

Recipe creation is limited to internal organizational users, and execution is supported only for metadata-based recipes that operate through the OvalEdge (-1 connector). This ensures a highly governed and metadata-restricted analytics flow.

Recipes created in this environment can be shared internally. Access to the Public Marketplace remains optional and dependent on organizational policy. Marketplace recipes that rely on the OvalEdge -1 connector can also be utilized if permitted by governance settings.

Supported Scope: OvalEdge catalog metadata only.

This edition supports metadata-specific workflows and does not include data-level enrichment or AI-assisted analytics beyond Metadata Analytics.

On-Prem Edition

The On-Prem Edition provides recipe functionality within a locally managed infrastructure, emphasizing data governance and internal control. Recipe creation and execution capabilities are available only for metadata analytics, maintaining strict compliance with on-premises governance frameworks.

Recipes can be created internally for analyzing metadata assets and executed only when configured with the OvalEdge (-1 connector). These recipes remain within the enterprise environment, ensuring no external data movement or Marketplace dependency.

Recipe sharing within the organization is supported; however, access to the Public Marketplace is optional and entirely controlled through internal governance policy. No recipe publishing or monetisation features are available in this edition.

Supported Scope: OvalEdge catalog metadata only.

The On-Prem Edition enforces complete data residency and security compliance, with recipe execution restricted to internal metadata models. External AI enrichment and data analytics features are intentionally disabled to align with enterprise control policies.

Summary

Variant	Recipe Creation	Recipe Execution	Marketplace Access	Supported Scope
Public Edition	Recipes can be created in the workspace.	Executed on uploaded or public datasets.	Full Public Marketplace access for publishing and sharing.	Public data and uploaded files.
SaaS - Data Analytics (Insights & Analytics)	Full internal recipe creation supported.	All recipe types (data and metadata) are executable.	IInternal sharing; Public Marketplace optional by policy.	All connectors, files, and catalog tables.
SaaS - Metadata Analytics	Internal creation of metadata-focused recipes.	Only metadata recipes operating through the OvalEdge (-1 connector) are executable.	Internal sharing supported; Public Marketplace access optional and policy-based.	OvalEdge catalog metadata only.
On-Prem Edition	Internal metadata analytics recipe creation supported.	Execution restricted to metadata recipes using the OvalEdge (-1 connector).	Internal sharing supported; Public Marketplace access optional and governed by internal policy.	OvalEdge catalog metadata only.

Organisation Recipe Management in askEdgi

askEdgi allows users to publish recipes to the Organisation library for broader team access. To prevent accidental content loss, askEdgi now supports removing recipes from the Organisation without deleting the creator’s original recipe.

This enhancement ensures better governance, safer content ownership, and controlled organisational visibility.

Organisation Tab – Recipe Visibility Controls

Within AskEdgi > Recipes > Organisation, users can manage recipes that have been shared with the organisation.

Available Actions in the Organisation Tab

The three-dot (⋮) menu for each recipe now includes:

• Remove from Organisation

• Delete Recipe(s)

Remove from Organisation

The Remove from Organisation option allows a recipe to be revoked from the Organisation library while preserving the creator’s original content.

When Remove from Organisation is Selected

• The recipe is removed only from the Organisation tab

• The recipe remains available in My Recipes

• The Created By metadata remains unchanged

• Other organisation users can no longer view or access the recipe

• No recipe logic, configuration, or history is deleted

This prevents unintended deletion of personal or authored recipes.

Delete Recipe

The Delete Recipe(s) option performs a full deletion.

When Delete Recipe(s) is Selected

• The recipe is deleted from My Recipes

• The recipe is removed from the Organisation tab

• The recipe cannot be recovered

• Execution history and ownership data are removed

This action should be used only when the recipe must be permanently removed.

Permission & Access Controls

Who Can Remove a Recipe from Organisation

• The recipe creator

• Organisation administrators

Restricted Users

• Other users cannot remove recipes they do not own

• Unauthorized users will not see the Remove option

Offline Marketplace Recipe Import in askEdgi

askEdgi supports offline Marketplace Recipe import, enabling on-premise and restricted-network customers to download, transfer, and use recipes without internet connectivity. This ensures organizations operating behind firewalls or compliance boundaries can continue using standard OvalEdge (OE) recipes securely.

This feature supports open recipes, preserves governance controls for monetized or closed recipes, and maintains full local execution independence.

Downloading Recipe JSON from Marketplace

Recipe creators can control whether their recipe is downloadable by enabling a visibility setting during publishing.

Recipe Visibility Setting

• A checkbox is available when editing or publishing a recipe:

  • “Allow others to download Recipe JSON”

Behavior Rules

• If enabled

  • Recipe becomes open-source

  • Code is visible

  • Monetization is disabled

  • A Download JSON button appears in Marketplace

• If disabled

  • Recipe remains closed-source

  • Code is hidden

  • Monetization remains enabled

  • Only Get Recipe is available (no download)

Downloaded JSON Includes

• Recipe metadata (name, description, version, creator)

• Configuration parameters

• Dataset structure

• Recipe logic (SQL / Python / hybrid steps)

• Execution flow instructions

Uploading Recipe JSON in askEdgi

On the My Recipes page, users can import downloaded recipes using the new Upload JSON option.

Upload Flow

1. User clicks Upload JSON

2. Only .json files are accepted

3. System validates recipe schema and required fields

4. If validation passes, the recipe is added under My Recipes

5. The Created By field updates to the importing user

6. The recipe becomes available for execution and editing based on openness

Validation Rules

• Required metadata must exist (name, version, logic)

• Invalid or malformed files trigger error:

• “Invalid recipe structure. Please upload a valid recipe JSON.”

Behavior After Import

Open Recipes (Download Allowed)

• Fully editable

• Users can modify logic, steps, parameters, and metadata

• Saved recipes become new locally owned copies

• Changes do not affect original marketplace version

Closed or Monetized Recipes

• Code remains hidden

• Editing is disabled

• Execution is allowed per purchase or license terms

• View-only mode enforced

Recipe Revocation & Versioning Behavior

If Creator Revokes a Recipe

• Recipe is removed from Marketplace

• No impact on users who already downloaded JSON

• Imported recipes remain fully functional locally

If Creator Republishes a Recipe

• A new version is created (e.g., v2.0)

• Existing imported copies are not auto-updated

• Users may manually download updated versions if needed

Editing Rules Based on Recipe State

Unpublished Recipe

• Fully editable

• No version locking

Published Recipe

• Editing is disabled

• Tooltip shown: “Revoke recipe to edit.”

After Revocation

• Creator can edit locally

• Recipe may be republished as a new version

Ownership & Independence Rules

• Imported recipes become independent local assets

• Ownership transfers to the importing user

• Imported recipes do not sync with Marketplace updates

• No forced deletion occurs if original recipe is revoked

Case Handling

If No Internet Available

• Recipes can still be imported via JSON

• Marketplace access is not required

If Explanation or Validation Fails

• User receives a clear error message

• Upload process stops safely

If Creator Revokes Recipe Later

• Local copies remain unaffected

• No auto-removal or invalidation occurs

---

Copyright © 2025, OvalEdge LLC, Peachtree Corners, GA USA