> For the complete documentation index, see [llms.txt](https://docs.ovaledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ovaledge.com/release8.2/askedgi/user-guides/recipe-user-guide.md). # Recipe User Guide This article explains how to create, manage, execute, and share recipes in askEdgi. It describes how to convert chat-based analyses into reusable recipes, build recipes from scratch, configure parameters, execute workflows, share recipes within the organization, publish recipes to the Marketplace, and manage recipes throughout their lifecycle. The article also explains recipe execution, collaboration, publication workflows, and best practices for managing recipes effectively. ## Recipes Recipes enable users to save, reuse, share, and publish analytical workflows in askEdgi. The My Recipes page provides a centralized location for managing all recipe-related activities, including recipe creation, execution, sharing, publishing, and subscription management. All the Recipes are displayed in a card-based format, allowing users to view personal, organization, and Marketplace recipes in a single location and perform common actions directly from the recipe details panel.
### Recipe Card View The My Recipes page displays recipes as individual cards. Each card provides a summary of the recipe and helps users quickly identify its purpose and ownership without opening it. Each recipe card displays: * Recipe Name * Recipe Description * Recipe Owner * Creation Information * Recipe Status Recipe ownership information helps users distinguish among personal, organization-shared, and Marketplace recipes. **Examples include:** * Created by Me * Created by \ * Marketplace Recipe In addition to the recipe information, visual status indicators appear on the recipe card to help users quickly identify the recipe's current state. Depending on the deployment type and recipe lifecycle, the card may display indicators for: Enterprise Instance * Shared with Organization * Subscribed from Marketplace Public Instance * Draft * Requested * Published * Rejected * Imported from Marketplace Recipe indicators help users quickly identify recipe ownership and publication status in both Enterprise and Public Instances. Example: * Organization icon: Indicates that the recipe is shared within the organization. * Marketplace icon: Indicates that the recipe was imported from Marketplace. These indicators provide immediate visibility into the availability, sharing status, and publication status of the recipe without requiring users to open the recipe details. Selecting a recipe card opens a detailed recipe summary panel where users can view recipe information and perform available actions.
### Creating Recipes Users can create reusable recipes using the Create Recipe option available on the My Recipes page. The Create Recipe menu provides two options: * Create from Scratch * Create from Chats #### Create from Scratch Create from Scratch allows users to build a new reusable recipe by defining recipe details, execution parameters, and workflow logic. The Recipe Builder guides users through three configuration stages: 1. Basic Information 2. Configure Parameters 3. Steps Builder Users can navigate between these sections to configure and refine the recipe before saving it. ### Basic Information The Basic Information section defines the recipe's identity and purpose. This information helps users understand the objective of the recipe and determines which datasets can be used during execution.
The following fields are available:
FieldDescription
Recipe NameEnter a unique and meaningful name for the recipe. The name should clearly indicate the purpose of the recipe and help users identify it in the My Recipes page.
IngredientsSelect one or more datasets that will be used by the recipe. Ingredients represent the data sources available to the recipe during execution. Only selected ingredients can be referenced in parameters and workflow steps.
DescriptionProvides a summary of the recipe's purpose and expected outcome. The description is automatically generated by AI based on the configured workflow and can be modified manually if required.
RegenerateGenerates a new AI-generated description based on the current recipe configuration. Users can use this option when the existing description does not accurately reflect the intended functionality.
The generated description helps users understand the recipe's purpose without having to review the workflow logic. ### Configure Parameters The Configure Parameters section allows users to create reusable inputs that can be supplied during recipe execution. Parameters eliminate the need to hardcode values directly into a recipe and allow the same recipe to be executed with different user-provided inputs. Parameterized recipes improve reusability by allowing users to provide execution-specific values rather than modifying the underlying recipe logic. For example, a recipe that analyzes customer information can use parameters to allow users to select a Customer ID, Region, Department, Product Category, or Reporting Date at execution time. When no parameters are configured, the Recipe Builder displays an option to add a new parameter.
Select Add Parameter to create a parameter configuration. The following fields are available:
FieldDescription
Input TypeDefines the type of input users will provide during recipe execution. Examples include dropdown selections, multi-select lists, text values, dates, or numeric inputs.
Parameter NameInternal name used by the recipe logic to reference the parameter. This value is used during parameter binding and execution.
Display LabelUser-friendly name displayed when users execute the recipe. This label should clearly describe the information users are expected to provide.
IngredientSpecifies the dataset that will provide values for the parameter. Only ingredients selected in the Basic Information section are available for selection.
Ingredient ColumnSpecifies the column from the selected ingredient that will be used to populate parameter values.
Save ConfigurationSaves the parameter and makes it available for use within recipe steps.
**Supported Input Types** The Input Type field determines how users provide values during recipe execution. The following input types are available:
Input TypeDescriptionExample
Dropdown (Single Select)Allows users to select a single value from a predefined list retrieved from an ingredient column. This option is useful when users must choose only one value.A sales analysis recipe prompts users to select a single Region (North, South, East, or West).
Dropdown (Multi Select)Allows users to select one or more values from a predefined list retrieved from an ingredient column. This option is useful when multiple selections are allowed.An inventory analysis recipe prompts users to select multiple Product Categories, such as Electronics, Furniture, and Clothing.
TextAllows users to manually enter a text value during recipe execution. This option is useful when the input value is dynamic and not available in a predefined list.A customer search recipe prompts users to enter a Customer Name or Department Name.
NumberAllows users to enter a numeric value during recipe execution. This option is useful for thresholds, limits, or identifiers.A monitoring recipe prompts users to enter a Minimum Sales Amount or Top N Records value.
DateAllows users to select a date value during recipe execution. This option is useful for filtering or generating time-based reports.A reporting recipe prompts users to select a Report Date or Order Date.
{% hint style="info" %} Dropdown input types require both Ingredient and Ingredient Column to populate the available values. {% endhint %} **Example Scenario** Consider a sales analysis recipe that needs different inputs each time it runs. Instead of creating multiple recipes, parameters can be configured as follows:
ParameterInput TypeExample Value
RegionDropdown (Single Select)South
Product CategoryDropdown (Multi Select)Electronics, Furniture
Customer NameTextABC Retail
Minimum Sales AmountNumber10000
Report DateDate15-Jun-2026
When the recipe is executed, askEdgi prompts users to provide these values and then uses them throughout the recipe execution workflow. After configuring the parameter details, select Save Configuration to save the parameter. The saved parameter becomes available for use within the recipe workflow and can be referenced in the recipe logic. Once the parameter configuration is saved, users can proceed to the Steps Builder section to define the recipe's execution logic. If additional parameters are required, select Add Parameter and repeat the configuration process. Multiple parameters can be configured within the same recipe and are presented to users during recipe execution. During recipe execution, users are prompted to provide values for all configured parameters before execution begins. The selected values are then used throughout the recipe execution workflow.
#### Steps Builder The Steps Builder defines the workflow logic that the recipe executes. A recipe can contain one or more steps, and each step performs a specific operation such as querying data, applying transformations, generating insights, or creating output datasets. Steps are executed sequentially in the order they are configured.
Each step contains the following components:
FieldDescription
Visible During ExecutionControls whether the step and its output are displayed during recipe execution. When enabled, users can view the step and its results as the recipe runs.
Execution OverviewProvides a business-friendly explanation of the step. This description is automatically generated by AI and summarizes the purpose of the step.
RegenerateGenerates a new AI-generated execution overview based on the configured prompt and logic.
PromptDefines the instruction or analytical requirement for the step. The prompt describes the action that askEdgi should perform.
Code TypeSpecifies the execution language used by the step. Supported options include SQL and Python.
CodeDisplays the executable logic generated for the step. Users can review and modify the code when required.
**Managing Recipe Steps** Recipes can contain multiple steps. Users can: 1. Add new steps using Add Step. 2. Review individual steps from the step list. 3. Modify step logic. 4. Reorder workflow execution by updating step configurations. 5. Save changes after completing the workflow design. Each step can operate independently or build upon the results of previous steps, enabling users to create complex multi-step analytical workflows. After completing the configuration, select Save to create the recipe and make it available in My Recipes for future execution and sharing. ### Importing Recipes Recipes can be imported into askEdgi from external sources. #### Upload Recipe The Upload Recipe allows users to import previously exported recipes into askEdgi. This capability is useful when moving recipes between environments, restoring backup copies, or sharing recipes across teams. **To upload a recipe:** 1. Select Upload Recipe from the My Recipes page. 2. Drag and drop a recipe file or select Choose Files. 3. Select Upload. 4. Review the imported recipe details. 5. Save the recipe.
**Supported File Format** Recipe uploads support JSON files. The uploaded file must be a valid recipe export generated from askEdgi. Generic JSON files that do not follow the recipe structure are not supported. * Supported file type: JSON (.json) * Maximum file size: Up to 1 GB **What Information Is Included in the Recipe File** A recipe export file typically contains: * Recipe Name * Recipe Description * Ingredients * Parameters * Recipe Steps * Prompts * Generated SQL or Python Logic * Execution Configuration When the recipe is imported, askEdgi automatically reconstructs the recipe and makes it available in the My Recipes page. **Example Recipe Structure** The following example illustrates a simplified recipe export structure: ``` { "recipeName": "Customer Churn Analysis", "description": "Analyzes customer churn trends by region.", "ingredients": [ "Customer Dataset", "Subscription Dataset" ], "parameters": [ { "parameterName": "Region", "inputType": "Dropdown" } ], "steps": [ { "stepName": "Analyze Customer Churn", "prompt": "Analyze customer churn by region", "codeType": "SQL" } ] } ``` {% hint style="info" %} The actual recipe export structure may contain additional fields and metadata generated by askEdgi. {% endhint %} If the uploaded file contains invalid or unsupported content, askEdgi displays a validation message and prevents the recipe from being imported. #### Add Recipe from Marketplace Add Recipe from Marketplace allows users to import recipes published in Marketplace. This capability enables users to quickly add reusable workflows created by other users, teams, or organizations without having to manually recreate the recipe. To import a Marketplace recipe: 1. Select Add Recipe from Marketplace. 2. Select Explore the Marketplace to browse available recipes. 3. Locate the recipe that needs to be imported. 4. Copy the provided recipe token. 5. Paste the token into the Marketplace import dialog. 6. Select Save.
**What Is a Recipe Token?** A recipe token is a unique identifier generated for a Marketplace recipe. The token allows askEdgi to retrieve the recipe definition and import it into the user's environment. Each Marketplace recipe has a unique token that represents a specific published version of the recipe. **Example Recipe Token** The following example illustrates a representative recipe token: RCP-8F7A21D4-9C3B-45E8-A7D2-123456789ABC {% hint style="info" %} The actual token format may vary depending on the Marketplace implementation and recipe version. {% endhint %} **Import Behavior** When a valid recipe token is provided: 1. askEdgi retrieves the recipe definition from Marketplace. 2. Recipe metadata is validated. 3. Recipe configuration is imported. 4. Recipe steps and parameters are reconstructed. 5. The recipe is added to the My Recipes page. After the import is complete, users can: 1. View recipe details. 2. Execute the recipe. 3. Edit the recipe, if permitted. 4. Use the recipe as a starting point for additional workflows **Marketplace Recipe Identification** Imported Marketplace recipes are displayed in the My Recipes page and can be identified using Marketplace indicators and filters. Users can use Marketplace filters to quickly locate imported recipes and distinguish them from personal or organization-shared recipes. **Validation** If the token is invalid, expired, or no longer associated with an available Marketplace recipe, askEdgi displays a validation message and prevents the recipe from being imported. Users should verify that the token was copied correctly and that the recipe is still available in Marketplace before attempting the import again. ### Prompt Discovery and Recipe Creation askEdgi enables users to discover and reuse prompts generated across chat interactions through a centralized prompt discovery interface. This capability allows analytical workflows created during exploration to be efficiently converted into reusable recipes without manual reconstruction. #### Prompt Discovery Users can access prompts from all chats through the Chat History entry point on the Ask screen. Prompts are presented as a unified list, independent of chat grouping, and ordered by execution time (latest first). Each prompt is displayed along with its source chat and execution timestamp, providing sufficient context for identification and reuse. * Prompts are displayed as the primary entity. * The interface follows a flat list model, where prompts are not grouped by chat. * Each prompt is displayed independently, with associated metadata for context.
**Search and Filtering** The interface supports prompt-level search and filtering to enable efficient navigation across large volumes of prompt history. * Search is applied strictly on prompt text. * Filters allow selection based on source chats with multi-select capability. * Chat options are presented based on recent activity. * Applied filters are summarized without impacting the main view. **Prompt Actions and Selection** Each prompt supports contextual actions for reuse and traceability: * Copy prompt text * View associated generated code (SQL/Python) * Navigate to the originating chat and corresponding result Users can select multiple prompts across different chats and execution timelines. There are no restrictions on combining prompts, allowing flexible construction of analytical workflows.
### Parameterized Recipe Creation Users can create recipe in two ways: 1. Create Recipe from Chat 2. Create Recipe from Scratch ### **Create Recipe from Chat** A user performs an analysis in askEdgi by interacting with data through prompts and refining the results until the desired outcome is achieved. Once the analysis is complete, the user can save the conversation as a recipe in two ways: **My Chats** * In the My Chats section, hover over the required chat. * Click the Create a Recipe icon displayed next to the chat. * askEdgi opens the **Recipe Builder** and guides you through the recipe creation process.
**Prompt History** * Navigate to Prompt History. * Select one or more prompts that you want to include in the recipe. * Click Create a Recipe. * askEdgi opens the **Recipe Builder** and generates the recipe workflow based on the selected prompts.
The Recipe Builder consists of three sections:
* Basic Information * Configure Parameters * Steps Builder #### Basic Information The Basic Information section defines the recipe and its purpose. #### Configure Parameters The Configure Parameters section allows recipe authors to define inputs that users provide when executing a recipe. These inputs make the recipe reusable by allowing different values to be supplied at runtime without modifying the recipe logic. **Steps Builder** The Steps Builder defines the workflow that runs when the recipe is executed. When a recipe is created from an askEdgi chat, askEdgi automatically generates the recipe steps based on the selected analysis. Each step includes: * Execution Overview * Prompt * SQL or Python Code For more details refer to [Creating Recipes ](#creating-recipes) **Detect and Bind Parameters** The Detect & Bind Parameters option helps convert static workflows in the recipe into reusable parameters. When selected, the system scans the step prompts and code to identify fixed values that match the parameters configured in the Configure Parameters section.
After reviewing the detected parameters, users can: * Accept the suggested parameter mappings. * Reject unwanted parameter mappings. After reviewing the detected parameters, users must select Inject into Code to replace the dynamic values with the accepted parameters. Once injected, the step uses the parameter value provided during recipe execution instead of the original dynamic value. This enables the recipe to run with different inputs without modifying the underlying logic. Users can repeat this process for multiple steps to create a fully parameterized recipe and save. **Example** Before parameterization: Credit date = '14-03-2026' After parameterization: Credit date = {{Customer Credit date}} Once the parameter is created, users provide the Credit date during execution instead of modifying the recipe logic. **Executing a Parameterized Recipe** After a recipe is saved, users can execute the recipe in one of the following ways: * From askEdgi Prompt – Open the Recipe Executor from the prompt area and select the required recipe.
* From the Recipes Page – Navigate to the Recipes page, select the required recipe.
**Recipe Execution Flow** * Select the recipe to execute. * Click Execute.
* If the recipe contains configured parameters, the execution screen displays all required input fields and user can click on Execute button. * Now in the askEdgi Chat window, Users can review the parameters and provide the required values based on the analysis requirements.
After providing the required inputs, run the analysis on the recipe. The same recipe can be executed multiple times with different parameter values without modifying the underlying recipe logic. ### **Searching and Filtering Recipes** The My Recipes page provides search and filtering capabilities that help users quickly find recipes by ownership, publication status, Marketplace subscriptions, and creation date. These capabilities become especially useful when managing a large collection of personal, organizational, and Marketplace recipes. #### Search Recipes The search bar allows users to quickly locate recipes without manually browsing through recipe cards. Users can search recipes using: * Recipe Name * Recipe Description * Recipe Creator * Created Date As users enter search criteria, the recipe list is automatically updated to display matching results. The search functionality helps users quickly locate specific recipes, identify recipes created by a particular user, or find recipes associated with a specific business process. For example, users can search for: * Customer Churn Analysis * Revenue Dashboard * Created by John Smith * Recipes created during a specific period #### Filter Recipes The Filter By option allows users to narrow the displayed recipes by recipe ownership, publication status, Marketplace subscriptions, and creation date. Multiple filters can be selected simultaneously to refine search results. After selecting the required filters, select Apply Filters to update the recipe list. **Enterprise Instance Filters** In Enterprise deployments, users can filter recipes based on ownership and availability. Available filters include:
FilterDescription
My RecipesDisplays recipes created by the current user.
Recipes Shared within the OrganizationDisplays recipes shared by other users within the organization.
Subscribed from MarketplaceDisplays recipes imported from Marketplace.
These filters help users distinguish among personal, organization-shared, and Marketplace recipes.
#### Public Instance Filters In Public deployments, users can filter recipes by publication lifecycle. Available filters include:
FilterDescription
DraftDisplays recipes that have been saved but not submitted for publication.
RequestedDisplays recipes that have been submitted for publication and are awaiting approval.
PublishedDisplays recipes that have been approved and published to Marketplace.
RejectedDisplays recipes whose publication requests were rejected during review.
Subscribed from MarketplaceDisplays recipes imported from Marketplace.
These filters provide visibility into the publication status of recipes and help users manage Marketplace submissions more efficiently.
#### Filter by Date Range Users can also filter recipes based on their creation date. The date range filter allows users to select a custom date range to identify recipes created within that period. Users can combine the date filter with other search and filter options to further refine the displayed results. For example, users can: * View Marketplace recipes imported during a specific period. * View organization recipes created within a selected date range. Using search and filters together helps users quickly locate relevant recipes and manage large recipe collections more efficiently. ### Viewing Recipe Details Selecting a recipe card opens the Recipe Details panel, which provides a consolidated view of recipe information, execution activity, and available recipe actions. The Recipe Details panel is the primary place to review recipe content, monitor execution results, and manage the recipe throughout its lifecycle.
#### Recipe Information The header section displays key information about the recipe, including: * Recipe Name * Recipe Description * Recipe Status * Available Recipe Actions The description summarizes the workflow and helps users understand the recipe's purpose and expected outcome. Depending on the recipe status and user permissions, users may perform actions such as Edit Recipe, Share with Organization, Remove from Organization, List to Marketplace, Execute Recipe, and Execute in askEdgi. #### Recipe Execution Summary The Recipe Details panel displays the most recent execution of the recipe. This section provides visibility into: * Execution progress * Completed steps * Execution status * Generated outputs * Execution results Each completed step is displayed in the order in which it was executed, allowing users to understand how the workflow progressed and which actions were performed. For multi-step recipes, execution details are displayed for each configured step. **Reviewing Recipe Outputs** When a recipe execution generates results, the output is displayed directly within the execution summary. Depending on the recipe logic, outputs may include: * Data tables * Analytical results * Data quality findings * Aggregated metrics * Generated datasets Users can review the results without leaving the Recipe Details panel. For tabular results, the output displays the records returned by the recipe along with the associated columns and values. #### Viewing Past Executions The Recipe Details panel provides access to previously executed runs through the View Past Executions option.
Users can review historical executions to: * Verify previous results. * Compare execution outcomes. * Investigate execution behavior. * Review execution history for troubleshooting purposes. This capability helps users track recipe activity over time and validate the consistency of execution. #### Recipe Actions The Recipe Details panel provides quick access to commonly used recipe actions. Depending on the deployment type, recipe ownership, and publication status, available actions may include: 1. Edit Recipe 2. Share with Organization 3. Remove from Organization 4. List to Marketplace 5. Execute Recipe 6. Execute in askEdgi 7. Run Again These actions allow users to manage and execute recipes without returning to the My Recipes page. #### Executing a Recipe Again Users can rerun a recipe directly from the Recipe Details panel by selecting Run Again. When the recipe contains parameters, users may be prompted to provide updated values before execution begins. The new execution is added to the execution history, and the latest results are displayed in the execution summary. #### Executing in askEdgi The Execute in askEdgi option opens the recipe within the askEdgi conversational workspace. This allows users to: * Continue interacting with the results. * Ask follow-up questions. * Refine the analysis using natural language. * Perform additional exploration based on the generated output. The conversational experience helps users extend the recipe analysis beyond the predefined workflow. Before performing actions such as editing, sharing, publishing, or executing a recipe, users can review the recipe information, execution history, and the latest results in the Recipe Details panel to ensure the recipe meets their requirements. #### Editing Recipes Users can modify existing recipes from the Recipe Details panel. To edit a recipe: 1. Navigate to the My Recipes page. 2. Select the desired recipe card. 3. Review the recipe details in the Recipe Details panel. 4. Select Edit Recipe. The Recipe Builder opens with the existing recipe configuration pre-populated, allowing users to review and update it without creating a new one.
**Basic Information** Modify the general details of the recipe, including: * Recipe Name * Ingredients * Recipe Description The Regenerate option can be used to create a new AI-generated description based on the updated recipe configuration. **Configure Parameters** Modify existing parameters or add new parameters to support additional execution scenarios. Users can: * Add parameters * Update parameter names * Modify display labels * Change input types * Update ingredient mappings * Remove unnecessary parameters Parameter changes automatically affect how users provide inputs during recipe execution. **Steps Builder** Modify the workflow logic that the recipe executes. Users can: * Update step descriptions * Modify prompts * Review generated SQL or Python code * Add new steps * Remove existing steps * Update execution visibility settings Changes made in the Steps Builder affect the behavior and output of future recipe executions. **Saving Recipe Changes** After completing the required updates: 1. Review the modified recipe configuration. 2. Select Save Changes. 3. Verify the success confirmation message. The updated recipe becomes immediately available for future executions and retains its existing execution history, sharing configuration, and publication information where applicable. **Recipe Edit Eligibility** The ability to edit a recipe depends on recipe ownership and publication status. **Enterprise Instance** Users can edit: * Recipes they created. * Recipes shared with the organization, if edit permissions are available. Users cannot edit: * Organization recipes for which they do not have edit permissions. * Recipes owned by other users without the required access. **Public Instance** Users can edit recipes in the following states: * Draft * Rejected These states allow users to modify recipe content, update Marketplace information, and make corrections before publication. Users can also edit Published recipes after revoking the Marketplace listing and returning the recipe to the Draft state. **Requested Recipes** Recipes in the Requested state are pending approval and should not be modified during the review process. If changes are required: 1. Withdraw the publication request. 2. Return the recipe to the Draft state. 3. Make the required updates. 4. Submit the recipe again for approval. {% hint style="info" %} Marketplace-subscribed recipes and recipes owned by other users may be subject to access restrictions. Available actions depend on recipe ownership, permissions, and publication status. {% endhint %} #### Enterprise Recipe Management Enterprise deployments support recipe collaboration and sharing across the organization. The My Recipes page provides a centralized location for users to manage their personal recipes, discover recipes shared within the organization, and access recipes imported from Marketplace. This unified experience simplifies recipe management by bringing all recipe categories into a single interface. #### Unified Recipe View The My Recipes page displays all available recipes in a unified card-based layout. Users can access: * Personal Recipes * Organization Recipes * Marketplace Recipes This eliminates the need to switch between multiple pages or tabs to locate recipes. Each recipe card provides a summary of the recipe, including: * Recipe Name * Recipe Description * Recipe Owner * Creation Date * Recipe Status Indicators
#### Sharing Recipes with the Organization Enterprise deployments allow users to share recipes with other members of the organization. Sharing a recipe makes the workflow reusable across teams and promotes consistency in data analysis, reporting, and business processes. Users can share recipes directly from the Recipe Details page. To share a recipe: 1. Navigate to My Recipes. 2. Select the desired recipe card to open the Recipe Details page. 3. Review the recipe information and execution details. 4. Select Share with Organization. 5. Review the confirmation message. 6. Select Yes to confirm the action.
After the recipe is shared: * The recipe becomes available to authorized users within the organization. * Organization users can view the recipe details. * Organization users can execute the recipe. * The recipe remains owned and managed by the original creator. * A Shared with Organization indicator is displayed on the Recipe Details page. * A shared status indicator appears on the recipe card, helping users quickly identify organization-shared recipes.
Sharing recipes enables teams to reuse proven workflows, reduce duplicate effort, and maintain consistency across analytical processes. {% hint style="info" %} Only recipe owners or users with the required permissions can share recipes with the organization. {% endhint %} ### Removing Recipes from the Organization Recipe owners can remove previously shared recipes from the organization when updates, corrections, or workflow changes are required. Removing a recipe from the organization revokes organization-wide visibility while preserving the recipe for the owner. To remove a shared recipe: 1. Navigate to My Recipes. 2. Open the shared recipe from the Recipe Details page. 3. Select Remove from Organization. 4. Review the confirmation message. 5. Select Okay to confirm the action.
After the recipe is removed: * The recipe is removed from the organization's shared recipe list. * Organization users can no longer view the recipe. * Organization users can no longer execute the recipe. * The recipe remains available to its owner in My Recipes. * The shared status indicator is removed. This capability allows recipe owners to temporarily or permanently withdraw recipes from organization-wide use while retaining ownership and control of the workflow. {% hint style="info" %} Removing a recipe from the organization does not delete the recipe. The recipe remains available to its owner and can be shared again at any time. {% endhint %} ### Executing Recipes Recipes can be executed directly from the Recipe Details page. Recipe execution runs the configured workflow, processes each step in sequence, and displays the results within the execution view. Before executing a recipe, users can review the recipe description, ingredients, and configured steps to verify that the workflow meets their requirements.
**Execute Recipe** The Execute option runs the recipe using the standard recipe execution process. To execute a recipe: 1. Navigate to My Recipes. 2. Open the desired recipe. 3. Review the recipe details. 4. Select Execute. If the recipe contains configured parameters, users are prompted to provide the required input values before execution begins. Examples of parameter values include: * Product IDs * Date ranges * Departments * Regions * Business units * Customer categories After all required inputs are provided, the recipe execution starts. **Execution Validation** Before execution begins, askEdgi validates: * Availability of recipe ingredients. * User access permissions to required datasets. * Parameter values provided during execution. * Dependencies required by the recipe. If a required dataset is unavailable or a validation check fails, the system displays the appropriate error message and prevents execution until the issue is resolved. **Execution Progress** During execution, askEdgi processes each configured step sequentially. The execution view displays: * Current execution status. * Completed steps. * Active step being processed. * Execution progress indicators. * Generated outputs. As each step completes successfully, a completion indicator is displayed. The step currently being executed is highlighted to help users track workflow progress.
**Viewing Step Outputs** Recipe outputs are displayed as each step completes. Users can select View Step Output to review the results generated by a specific step. Depending on the recipe logic, step outputs may include: * Data tables * Aggregated results * Data quality findings * Analytical summaries * Generated datasets This visibility helps users understand how data is processed throughout the workflow. **Viewing Execution Results** When execution completes successfully, the generated output is displayed directly within the Recipe Details page. For tabular outputs, users can: * Review returned records. * Scroll through results. * Expand the output view. * Download the generated results. For multi-step recipes, results may be displayed separately for each step.
**Re-executing a Recipe** After execution completes, users can select Run Again to execute the recipe again. This option is useful when: * Input parameter values change. * Source data has been updated. * Results need to be regenerated. * Additional validation is required. The new execution is added to the recipe execution history. **Viewing Execution History** Users can review previous executions by selecting View Past Executions. Execution history helps users: * Review previous results. * Compare outputs across runs. * Validate workflow behavior. * Troubleshoot execution issues. Each execution retains its associated steps, status information, and generated outputs. {% hint style="info" %} Users must have access to all recipe ingredients before execution. If access to one or more ingredients is unavailable, the recipe cannot be executed until the required permissions are granted. {% endhint %} #### Execute in askEdgi Execute in askEdgi opens the recipe in the askEdgi conversational workspace and executes it within the chat experience. This option allows users to continue interacting with the results using natural language prompts and follow-up questions. To execute a recipe in askEdgi: 1. Navigate to My Recipes. 2. Open the desired recipe. 3. Review the recipe details and configured steps. 4. Select Execute in askEdgi. If the recipe contains parameters, users may be prompted to provide the required input values before execution begins. After validation is completed, askEdgi opens the conversational workspace and starts the recipe execution process. ### Recipe Execution in the Chat Workspace When the recipe starts running, askEdgi displays the execution progress directly within the conversation. Users can monitor: * Current execution status * Completed steps * Active step being processed * Generated outputs * Execution progress indicators Each step is executed sequentially and displayed in the chat as it progresses through the workflow.
**Monitoring Multi-Step Execution** For recipes containing multiple steps, askEdgi displays each step individually within the conversation. Users can see: * Step number * Execution description * Processing status * Step output As each step completes successfully, a completion indicator is displayed. The currently executing step is highlighted so users can track workflow progress in real time.
**Viewing Step Outputs** The output generated by each recipe step is displayed directly within the chat workspace. Users can: * Review step-level results. * Expand output tables. * Download generated results. * View outputs produced by previous steps. This visibility helps users understand how data is processed throughout the workflow and how each step contributes to the final result.
**Continuing the Analysis** After the recipe completes, users can continue working with the results using natural language prompts. This allows users to: * Ask follow-up questions about the results. * Refine the analysis. * Request additional calculations. * Explore related datasets. * Perform further data investigation without creating a new recipe. For example, after executing a product analysis recipe, users can ask questions such as: * Show only discontinued products. * Group results by category. * Calculate the average unit price. * Display products with low inventory levels. The conversational interface allows users to build on the recipe output rather than start a new analysis from scratch. **Workspace Context Preservation** The execution results remain available within the active askEdgi conversation. This enables users to: * Review previous outputs. * Reference earlier execution steps. * Continue the analysis using the same context. * Maintain a complete audit trail of recipe execution and follow-up interactions. **When to Use Execute in askEdgi** Use Execute in askEdgi when: * Additional analysis is required after recipe execution. * Users want to ask follow-up questions about the results. * Interactive exploration of the output is needed. * Results must be refined using natural language instructions. * The recipe serves as a starting point for deeper investigation. Use the standard Execute option when only the recipe output is required without additional conversational analysis. {% hint style="info" %} Execute in askEdgi uses the same recipe logic and produces the same output as the standard execution process. The primary difference is that execution occurs within the askEdgi conversational workspace, allowing users to continue interacting with the results after the recipe completes. {% endhint %} ### Deleting Recipes Users can delete recipes they no longer need from the My Recipes page. The delete option is available only for recipes that the user owns or has imported from the Marketplace. When a user hovers over an eligible recipe card, a Delete icon appears in the upper-right corner of the card.
**Recipes That Can Be Deleted** Users can delete: * Recipes they created. * Recipes imported from the Marketplace. * Draft recipes. * Recipes they shared with the organization, after unsharing or removing them from the organization. **Recipes That Cannot Be Deleted** Users cannot delete: * Recipes created by other users. * Recipes shared by other members of the organization. * Recipes for which they do not have ownership permissions. **Deleting a Recipe** To delete a recipe: 1. Navigate to My Recipes. 2. Locate the recipe to delete. 3. Hover over the recipe card. 4. Select the Delete icon. 5. Review the confirmation message. 6. Select Yes to permanently delete the recipe. **Delete Confirmation** Before the recipe is removed, the system displays a confirmation dialog to prevent accidental deletion. The confirmation message informs the user that the recipe will be deleted from the system.
Users can: * Select Yes to proceed with the deletion. * Select No to cancel the operation and retain the recipe. After confirmation: * The recipe is permanently removed from My Recipes. * The recipe definition, configuration, and execution workflow are deleted. * The recipe is no longer available for execution. * The recipe no longer appears in search results or recipe listings. If the deleted recipe was previously shared with the organization, it is also removed from the shared recipe list and becomes inaccessible to other users. {% hint style="info" %} Note: Recipe deletion is a permanent action and cannot be undone. Ensure that the recipe is no longer required before confirming the deletion. {% endhint %} **Example** A user creates a recipe named ProductID Detail Extraction Workflow for a temporary analysis project. After the project is completed, the recipe is no longer needed. The user hovers over the recipe card, selects the Delete icon, confirms the action, and the recipe is permanently removed from the environment. ### Marketplace Recipe Management The Marketplace enables users to publish reusable recipes for discovery, execution, and collaboration. Public deployment users can create, manage, track, and publish recipes directly from askEdgi without leaving the application. Published recipes can be offered as free or paid assets and categorized to improve discoverability within the Marketplace. #### Listing a Recipe in Marketplace Users can publish any saved recipe from the My Recipes section. To publish a recipe: 1. Open the required recipe from My Recipes.
2. Click List to Marketplace. The Marketplace Listing form opens. 3. Enter all required recipe information. 4. Choose one of the following actions: 5. Save as Draft to save the recipe and continue editing later. 6. Request to Publish to submit the recipe for Marketplace review. 7. After submission, the recipe enters the review process. 8. Upon approval, the recipe becomes available in the Marketplace. {% hint style="info" %} The Marketplace listing form is fully integrated into askEdgi. Users can complete the entire publication process without accessing external systems or forms. {% endhint %} #### Marketplace Listing Information The Marketplace listing form captures information that helps users understand the recipe, its purpose, ownership, pricing model, and intended use cases. **Basic Information** Provide information that describes the recipe and its business value. | Field | Description | | ------------ | ----------------------------------------------------------------- | | Recipe Name | Unique name displayed in the Marketplace. | | Description | Detailed explanation of the recipe and the insights it generates. | | Recipe Guide | Instructions explaining how to use and execute the recipe. | This information is displayed on the recipe details page and helps users determine whether the recipe meets their requirements. **Seller Information** Seller information identifies the recipe owner and provides contact details for support and questions. | Field | Description | | ---------------- | ----------------------------------------------------------- | | Seller Name | Name of the recipe publisher or organization. | | Seller Support | Email address used for user inquiries and support requests. | | LinkedIn Profile | Optional professional profile link. | Providing accurate seller information improves trust and enables direct communication between recipe consumers and publishers. **Pricing Information** Pricing settings determine how the recipe is offered in the Marketplace. **Recipe Types** Users can select one of the following recipe types: * Free – Available to all eligible users without charge. * Paid – Requires payment before execution or subscription. **Pricing Models** For paid recipes, users can configure: **Subscription Pricing** Users pay a recurring subscription fee to access and execute the recipe. **Typical use cases:** * Industry benchmark recipes * Governance assessment recipes * Data quality monitoring frameworks **Per Execution Pricing** Users are charged each time the recipe is executed. **Typical use cases:** * One-time assessments * Specialized analytical workflows * AI-intensive processing **Per 1,000 Rows Pricing** Charges are calculated based on the number of rows processed during execution. **Typical use cases:** * Data profiling * Data quality analysis * Large-scale enrichment recipes **Price Configuration** **Provide:** * Pricing Type * Price in USD * Minimum Charge (if applicable) The configured pricing is displayed on the Marketplace recipe page before purchase or execution. **Categories and Tags** Categories help users discover recipes relevant to their industry and business use case. **Industry** Select the industry most closely aligned with the recipe. **Examples:** * Finance * Healthcare * Retail * Manufacturing * Technology * Education * Transportation * Energy * Telecommunications * Real Estate * Others **Application** Select the primary business application. **Examples:** * Azure DevOps * HubSpot * NetSuite CRM * SalesForce * WorkDay * ServiceNow * JIRA * Oracle Service Cloud * SAP SuccessFactors * ADP * Microsoft Dynamics 365 Reports * Maximo * Others **Tags** Provide keywords that describe the recipe. **Examples:** * data-quality * governance * sentiment-analysis * lineage * metadata * stewardship * customer-retention Proper tagging improves search relevance and increases recipe visibility within Marketplace results. **Draft and Publication Workflow** Save as Draft Use Save as Draft when: * Recipe details are incomplete. * Pricing requires review. * Supporting documentation is still being prepared. * Internal validation is pending. Draft recipes remain editable and are not visible in the Marketplace. **Request to Publish** Use Request to Publish when all required information is complete. After submission: 1. The recipe is marked as Pending Review. 2. Approvers review the request through the Service Desk approval workflow. : 3. Recipe quality 4. Documentation completeness 5. Pricing configuration 6. Policy compliance 7. Execution validation 8. Approved recipes become available in the Marketplace. 9. Rejected recipes are returned with feedback for correction and resubmission. ### Recipe Publication Lifecycle Recipes follow a structured publication workflow before they become available in the Marketplace. This process ensures that submitted recipes are reviewed, approved, and governed before being shared with a broader audience. Throughout the lifecycle, the recipe status and associated Service Request provide visibility into the current stage of the publication process.
{% hint style="info" %} The Service Request Number remains associated with the publication process and provides traceability throughout the review, approval, rejection, and publication lifecycle. {% endhint %} #### **Publication States** A recipe can exist in one of the following publication states: * Draft * Requested * Published * Rejected Each state controls the actions available to the recipe owner and determines whether the recipe is visible in the Marketplace. #### Draft The Draft status indicates that the recipe has not yet been submitted for Marketplace approval. A recipe enters the Draft state when: * A new recipe is created. * Marketplace information is saved as a draft. * A publication request is withdrawn. * A published recipe is revoked. * A rejected request is reopened. When a recipe is in Draft status, a Draft badge is displayed on the Recipe Details page.
Working with Draft Recipes To prepare a recipe for publication: 1. Open the recipe from the My Recipes page. 2. Select List to Marketplace. 3. Complete the Marketplace information, including: 4. Recipe Name 5. Description 6. Recipe Guide 7. Seller Information 8. Recipe Type 9. Pricing Information 10. Select Save as Draft to save the information without submitting it. The draft can be reopened at any time, and all previously entered Marketplace information remains available. Actions Available in Draft Status Users can: * Edit Marketplace information. * Save changes as a draft. * Review publication details. * Submit the recipe for approval. * Continue updating the recipe before publication. Requesting Publication When the recipe is ready for publication, users can submit it for review. To Request Publication 1. Open the recipe. 2. Select List to Marketplace. 3. Complete all required Marketplace fields. 4. Select Request to Publish. The system creates a publication request and automatically routes it through the configured approval workflow. After submission: * A Service Request is generated. * The recipe status changes from Draft to Requested. * A Service Request Number (SR ID) is displayed on the Recipe Details page. * The request enters the approval workflow for review. The Service Request Number acts as a tracking reference throughout the approval process. #### Requested The Requested status indicates that the recipe has been submitted and is awaiting review and approval. When a recipe is in this state: * A Requested badge is displayed. * The generated Service Request Number appears beside the status. * The recipe cannot be published until all approval stages are completed. * Users can monitor approval progress through the associated Service Request. Viewing the Publication Request To view request details: 1. Open the recipe. 2. Select the displayed Service Request Number.
The Service Request page opens and displays: * Request details * Request status * Approval workflow * Reviewer comments * Approval history * Current approvers Approvers can review the request and perform actions such as: * Review * Approve * Reject {% hint style="info" %} These actions are performed by authorized approvers within the Service Desk.
{% endhint %}
#### Withdrawing a Publication Request A recipe owner can withdraw a publication request while it is still pending approval. To Withdraw a Request 1. Open the recipe in Requested status. 2. Select Withdraw Request. After withdrawal: * The approval process stops. * The publication request is canceled. * The recipe returns to Draft status. * All Marketplace information is retained. * Additional modifications can be made before submitting again. This option is useful when updates or corrections are required before publication. #### Published The Published status indicates that the recipe has successfully completed the approval workflow and has been approved for Marketplace publication. After approval: * The recipe becomes available in the Marketplace. * Other users can discover the recipe. * Marketplace users can review recipe information. * The recipe can be installed and used according to Marketplace permissions. A Published badge and the associated Service Request Number are displayed on the Recipe Details page. Additional Actions for Published Recipes Published recipes provide the following actions: * View in Marketplace: Opens the Marketplace listing for the published recipe and allows users to review how the recipe appears to Marketplace consumers. * Revoke: Removes the recipe from the Marketplace and returns it to an editable state. Approval Workflow When a publication request is submitted: 1. A Service Request is generated. 2. The request is routed through the configured approval workflow. 3. Approvers review the recipe details. 4. Approvers can: 5. Approve the request. 6. Reject the request. 7. After all required approvals are completed, the request status changes to Approved by All. 8. The recipe status automatically changes to Published. The Service Request remains available for audit and tracking purposes after publication. #### Revoking a Published Recipe Recipe owners can remove a published recipe from the Marketplace when modifications are required. To Revoke a Published Recipe 1. Open a published recipe. 2. Select Revoke. 3. Confirm the action when prompted.
After revocation: * The recipe is removed from the Marketplace. * Marketplace users can no longer discover or install it. * The recipe returns to Draft status. * Marketplace information remains intact. * The recipe can be edited and resubmitted for approval. {% hint style="info" %} Revoking a recipe does not delete the recipe. It only removes the Marketplace listing. {% endhint %} #### Rejected If reviewers determine that a recipe does not meet publication requirements, the publication request is rejected. When a recipe is rejected: * The recipe status changes to Rejected. * A Rejected badge is displayed.
* The Service Request ID remains available and can be used to review publication details.
* Users can review rejection details and comments through the Service Request. Common Reasons for Rejection A publication request may be rejected due to: * Incomplete Marketplace information. * Insufficient documentation. * Missing business context. * Validation issues. * Governance or compliance concerns. #### Reopening a Rejected Request Recipe owners can reopen a rejected recipe, make corrections, and resubmit it for review. To Reopen a Rejected Recipe 1. Open the rejected recipe. 2. Select Reopen. 3. Review the rejection feedback. 4. Update the recipe or Marketplace information as required. 5. Save the changes. 6. Submit the recipe again using Request to Publish. After reopening: * The recipe returns to Draft status. * Marketplace information remains available. * Users can make additional modifications. * A new publication request can be submitted for approval. The publication lifecycle then restarts from the Draft stage. ### Recipe execution: Common failure reasons * Required datasets are missing from the workspace * Insufficient permissions to access catalog objects * Column names or structures differ from the recipe's expectations * Workspace compute limits exceeded ## Best Practices **Naming Conventions** Use clear, descriptive names that explain what the recipe does. Avoid generic names like "Analysis 1" or "Report." **Good examples:** * "Monthly Sales Summary by Region" * "Customer Sentiment Analysis with Risk Classification" * "Data Quality Check for Orders Table" **Documentation:** Write descriptions that help others understand the recipe's purpose, required inputs, and expected outputs. Include guidance on when to use the recipe and what insights it provides. **Testing Before Sharing** Execute the recipe on test data before sharing it with your organization or publishing to the Marketplace. Verify that all steps produce correct results and that visualizations are accurate. **Version Control** If you modify a recipe significantly, save it as a new recipe with a version indicator in the name (example: "Customer Analysis v2"). This preserves the original workflow while allowing experimentation. **Metadata Recipes** When creating metadata recipes, document which catalog objects or metadata domains the recipe targets. This helps users understand whether the recipe applies to their governance needs. ### Troubleshooting Recipe Execution **The recipe fails immediately** * Cause: Required datasets are not in the workspace * Solution: Add the necessary catalog objects or files to your workspace before executing the recipe **The recipe produces unexpected results** * Cause: Column names or structures differ from the original analysis * Solution: Review the recipe steps and verify that the datasets in your workspace match the expected schema **Recipe times out or exceeds limits** * Cause: Large datasets or complex joins exceed workspace capacity * Solution: Upgrade the workspace container or simplify the recipe by breaking it into smaller steps **The recipe cannot be executed in my edition** * Cause: The recipe requires connectors or features not available in your edition. * Solution: Verify that the recipe is compatible with your deployment model (Public, SaaS Data Analytics, SaaS Metadata Analytics, or On-Prem) ## Example of Recipe ### Creating a Recipe with a Real Use Case #### Example Scenario **Business Question:** “How are customers feeling about our support tickets, and which issues need immediate attention?” This example walks through creating a Customer Support Sentiment Analysis recipe using a real dataset and AI enrichment. #### Step 1: Start with an Analysis (Chat-Based) Assume you already have a table in your workspace: Table: support\_tickets\ Columns: * ticket\_id * created\_date * customer\_comment * priority * category You run the following steps in a chat. #### Step 2: Basic Data Selection ``` SELECT ticket_id, created_date, customer_comment, priority, category FROM support_tickets WHERE created_date >= current_date - INTERVAL '30 days'; ``` This filters tickets from the last 30 days. #### Step 3: AI Enrichment – Sentiment Analysis Apply Sentiment Analysis on the customer\_comment column. **AI Function**: Sentiment Analysis **Input Column**: customer\_comment **Output Column**: sentiment **Values**: Positive / Neutral / Negative #### Step 4: AI Enrichment – Intent Classification Add an **Intent Analysis** step to understand why customers raised tickets. **AI Function**: Intent Analysis **Input Column**: customer\_comment **Output Column**: intent **Example Values:** * Complaint * Support Request * Feature Request * Billing Issue #### Step 5: Derived Insight (Optional) Create a calculated column to flag **high-risk tickets.** ``` CASE WHEN sentiment = 'Negative' AND priority = 'High' THEN 'High Risk' ELSE 'Normal' END AS risk_flag ``` #### Step 6: Save the Chat as a Recipe Click **Save as Recipe** and fill in: * **Recipe Name**:\ Customer Support Sentiment & Risk Analysis * **Description**:\ Analyzes customer support tickets from the last 30 days, classifies sentiment and intent using AI, and highlights high-risk tickets requiring immediate attention. #### Step 7: Define Ingredients **Ingredients (Included):** * support\_tickets (table) **Why include ingredients?** This recipe depends on a specific table structure and should only run when that dataset is available. #### Step 8: Review Recipe Components When saved, the recipe contains:
ComponentCaptured Value
Ingredientssupport_tickets
StepsSQL query + Sentiment Analysis + Intent Analysis + Risk flag
Analysis TypeData Analytics
OutputsTable + charts (sentiment distribution, risk count)
#### Step 9: Execute the Recipe Later Next month, a user can simply: 1. Add support\_tickets to their workspace 2. Open **Recipes** → **My Recipes** 3. Click **Execute** on Customer Support Sentiment & Risk Analysis **askEdgi:** * Re-runs the same logic * Applies AI enrichments again * Generates a new chat with updated insights No manual rework required. ## Frequently Asked Questions
Can I delete a recipe? Yes. Recipes can be deleted from My Recipes. Deletion does not affect chats or analyses that used the recipe.
Do recipes update automatically when I change the original chat? No. Recipes are static snapshots. Changes to the original chat do not affect saved recipes.
Can I share recipes with external users? Only in Public Edition via the Marketplace. SaaS and On-Prem editions support internal sharing only.
What happens if I cancel my subscription after publishing a recipe? In Public Edition, your published recipes remain active in the Marketplace even if you cancel your subscription. Earnings continue to accrue.
Can I import a recipe from the Marketplace into my enterprise environment? Yes, if your organization permits Public Marketplace access. Marketplace recipes run within your edition's constraints and connector availability.
*** Copyright © 2026, OvalEdge LLC, Peachtree Corners, GA USA --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.ovaledge.com/release8.2/askedgi/user-guides/recipe-user-guide.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.