What You Will Learn

Oracle Analytics Cloud — From Dashboards to Decisions

Oracle Analytics Cloud empowers organizations with modern, AI-powered analytics — delivering dynamic visualizations, interactive dashboards, and real-time insights at enterprise scale. Building on that foundation, OAC now introduces the Agentic User Experience, redefining analytics as a conversational, intelligent, and always-available decision platform.

For years, business intelligence followed a familiar routine: dashboards were built, reports were published, and insights depended on someone finding and interpreting them correctly. Analysts became intermediaries — translating data into explanations rather than driving outcomes. That approach no longer keeps pace with how decisions are made today.

This guide shows you what changes when the analytics experience itself becomes agentic — when every user can ask, explore, and act in plain language, guided by your own business rules.

🎓

Stop waiting for reports. Start getting answers.

Today, getting insights from data means filing requests, waiting for analysts, and hoping the report answers the right question. By the end of this guide, every person on your team will be able to open Oracle Analytics, ask a question in plain English, and get a visual answer in seconds — no SQL, no pivot tables, no waiting.

You will gain three new skills: asking data questions conversationally inside workbooks, generating complete dashboards from a single homepage prompt, and building an AI Agent that applies your own business rules to every answer.

Before This Guide

  • “Can someone pull last quarter’s numbers?”
  • Days waiting for an analyst to build a report
  • Insights arrive too late to act on
  • Only power users can explore data

After This Guide

  • “I already have the answer.”
  • Ask questions → get charts instantly
  • One prompt → a full dashboard
  • AI Agent that knows your business rules
Three AI capabilities, one seamless analytics experience

✨ Workbook AI Assistant

Ask questions in natural language directly inside any workbook. The AI creates and modifies visualizations, surfaces trends, and lets you iteratively refine charts — just by talking to it. Save insights to workbooks or your Watchlist instantly.

🏠 Homepage AI Assistant

Build a complete dashboard from a single prompt — no workbook setup needed. Context-aware dialogue retains your intent across follow-ups, and smart search combines catalog discovery with semantic understanding.

🤖 AI Agents

Go beyond generic answers. AI Agents blend your datasets with uploaded policy documents, apply your business rules and KPI definitions, and explain trends with organizational context. Your analytics co-pilot, speaking your company’s language.

RoleWhat You Will Be Able to DoHands-On Activities
Author
Analyst, workbook designer
Build and deploy a complete AI-powered analytics experience — from raw data to a conversational interface your team can use on day one Upload data, configure indexing & synonyms, test AI prompts, create an AI Agent with business rules and RAG knowledge documents, then publish for consumers
Consumer
Business user, decision maker
Get instant, trustworthy answers by typing questions in everyday language — no training, no SQL, no dependencies Open a shared workbook, ask questions through the AI Assistant, interact with AI Agents that know your business context, and save insights to your Watchlist
Admin
Platform or security owner
Ensure the environment is ready so your team can hit the ground running Verify GenAI service settings, confirm application roles, and enable the Use Assistant in Workbooks permission
The bottom line: This guide takes your team from “Can someone pull this data?” to “I already have the answer” — in about 90 minutes of self-paced work. Every business user becomes self-sufficient. Every analyst gets time back. And your organization moves at the speed of questions, not reports.
Recommended session flow: Start with the Admin Pre-Check, then complete Author Labs 1–5 (Foundation + AI Assistant + AI Agents), switch to the Consumer Lab (6) to experience the end-user perspective, and finish with the Homepage AI Assistant (7) to see single-prompt dashboards in action.
🔧

Admin Pre-Check~10 min

Admin Reference

This section is for administrators. It covers the GenAI console settings (which come pre-configured) and the steps to create a consumer role with AI Assistant permissions. These steps are typically completed before anyone begins the hands-on labs.

What you will achieve in this lab

Verify GenAI service settings, application roles, and the Use Assistant in Workbooks permission so the hands-on labs run smoothly.

Admin A.1

Verify Generative AI Settings (Pre-Configured)

The Generative AI page comes pre-configured and active by default. No action is needed, but it is useful to verify what is available and which LLM model is in use.

  1. Navigate to Console → Generative AI (under Extensions and Enrichments)
  2. You will see two sections:
    • Registered Gen AI Services — shows the Oracle Analytics service. The Model column shows which LLM is active.
    • Oracle Analytics AI Assistant Features — five features, all active by default: Workbook Assistant, Catalog Descriptions, Dataset Assistant, Semantic Modeler Assistant, Language Narratives.
Screenshot: Generative AI console page
Built-In Knowledge: On this page you can also enable Built-In Knowledge, which lets the Assistant supplement your data with public knowledge (holidays, populations, etc.).
Admin A.2

Create a Consumer Role with AI Assistant Permissions

To give consumers access to the AI Assistant, create a dedicated application role.

Step 1 — Create the Role

  1. Navigate to Console → Roles and Permissions → Application Roles
  2. Click Create Application Role
  3. Name: AI Assistant Consumer
  4. Click Create

Step 2 — Add Base Consumer Privileges

  1. In the new role, go to the Memberships tab
  2. Click Add Application Roles → select DV Consumer

Step 3 — Add the Assistant Permission

  1. Go to the Permissions tab → Add Permissions
  2. Search for and select Use Assistant in Workbooks

Step 4 — Assign Users or Groups

  1. Go to the Members tab
  2. Click Add Users or Groups to assign consumers
Screenshot: Consumer Role setup
Admin A.3

Allow Users to Create AI Agents

By default, the Create and Edit AI Agents permission is already enabled for users with the DV Content Author application role. This means any user assigned the DV Content Author role can create and configure AI Agents without additional setup.

When is this step needed? If your organization needs users other than DV Content Authors to create or edit AI Agents, the administrator must create a custom application role with the Create and Edit AI Agents permission and assign the appropriate users or groups to that role.

Granting AI Agent Permissions to Additional Users

  1. On the Oracle Analytics home page, click Navigator , then click Console.
  2. Navigate to Roles and Permissions under the Application Roles tab.
  3. Click Create Application Role to define a new custom role (for example, AI Agent Creators).
  4. Open the new role and go to the Permissions tab.
  5. Click Add Permissions and assign the Create and Edit AI Agents permission to this role.
  6. Switch to the Members or Memberships tab and add the required users or groups who need AI Agent authoring capabilities.
Screenshot: AI Agent Consumer role with Create and Edit AI Agents permission
Key takeaway: DV Content Authors already have this permission by default. Only create a custom role if you need to extend AI Agent authoring to users who are not DV Content Authors — such as BI Consumers or users with specialized roles in your organization.
Reference: Allow Users to Create AI Agents in Oracle Analytics (Oracle Documentation)
Key Takeaway

Admin setup is a one-time gate: enable Generative AI in Console, then assign the right permissions. Once done, every author and consumer benefits automatically.

Quick Check — Test Your Understanding
What consumer-facing permission must be enabled for users to interact with the AI Assistant in published workbooks?
Use Assistant in Workbooks must be toggled ON in the user's role. Without this, the Insights Panel won't appear — even if the workbook is shared and the AI Assistant is configured. This is found under Console → Roles → (role name) → toggle 'Use Assistant in Workbooks'.
Why does the DV Content Author role already include 'Create and Edit AI Agents' by default?
Oracle treats AI Agent creation as a content authoring activity — just like building workbooks or data flows. Since DV Content Authors already design analytics content, giving them Agent creation rights keeps everything in a single author workflow. No extra admin step is needed for authors.
📥

Download & Upload the Dataset~5 min

Author Track

Before diving in, ensure you have Author access (for example, assigned to the DV Content Author role or an equivalent custom role). Authors can create datasets, build workbooks, configure indexing, enable Workbook AI Assistant for consumers, and create AI Agents.

What you will achieve in this lab

Upload the SampleSales_Dataset into Oracle Analytics Cloud so it is available for indexing, AI Assistant queries, and AI Agent configuration in the labs that follow.

Step 1.1

Download the Sample Dataset

📥
Download SampleSales_Data.xlsx XLSX

18,090 sales transactions • 27 columns • Jan 2020 – Apr 2026

  1. Click the download button above to save SampleSales_Data.xlsx to your computer
  2. Verify the file downloaded successfully — it should be approximately 2–3 MB
File name may vary: Your instructor may provide the file as SampleSales_Data.xlsx or SampleSales_Dataset.xlsx. Either name is fine — the column structure is identical.
What’s in this dataset: The file contains 18,090 sales transactions spanning January 2020 through April 15, 2026. It includes 3 customer segments (Consumer, Corporate, Home Office), 3 product categories (Furniture, Office Supplies, Technology), 17 sub-categories, 6 regions (Central, East, S.East, South, West, Western), and 4 shipping modes. Measures include Sales, Quantity, Discount, and Profit. The dataset has 27 columns.
Step 1.2

Upload to OAC and Create a Dataset

  1. Log in to your OAC instance
  2. On the Home page, click Create (top-right) — a menu appears showing Workbook, AI Agent, Dataset, Data Flow, Sequence, Connection, and Semantic Model
  3. Click Dataset
Click Create → Dataset
Create menu showing Dataset option
Drop data file here or click to browse
Create Dataset dialog with file upload area
  1. The Create Dataset dialog opens, showing “From a File, Subject Area, or Connection”
  2. Click Drop data file here or click to browse (the dashed-border area on the left) and select the SampleSales_Dataset.xlsx file from your computer
  3. OAC will preview the data — you should see columns like Row ID, Order ID, Order Date, Ship Date, Ship Mode, Customer Name, Segment, Category, Sub-Category, Product Name, Sales, Quantity, Discount, Profit, and more
  4. Review the column data types — OAC should auto-detect dates, numbers, and text correctly
  5. Click Save — name the dataset SampleSales_Dataset
File requirements: OAC supports Excel (.xlsx, .xls), CSV, and TXT files up to 250 MB with a maximum of 250 columns per sheet. Tables must start in Row 1, Column 1 with no gaps or pivoted data.
Step 1.3

Cleanse the Data — Set the Right Column Types

When OAC auto-detects column types from an Excel file, a few columns come in as plain numbers even though they aren’t measures you want to sum. Fix these before indexing so the AI Assistant treats them correctly.

Open the dataset for prep

  1. From the Home page, click the SampleSales_Dataset to open a new workbook.
  2. At the top of the workbook, click the Data tab (next to Visualize and Present).
  3. In the Data Diagram canvas, double-click the dataset tile (the box labelled SampleSale...) to enter the dataset editor, where you can change column data types and cleanse values for accuracy.
Workbook → Data tab → double-click the dataset tile to open the prep editor
New Workbook Data tab with SampleSales_Dataset tile highlighted in the Data Diagram

Columns to fix

ColumnDetected asChange toWhy
YearMeasure (Number)AttributeYou want to group by year, not sum it
LatitudeMeasure (Number)AttributeLocation (Latitude)Enables map visualizations
LongitudeMeasure (Number)AttributeLocation (Longitude)Enables map visualizations
Postal CodeMeasure (Number)AttributePostal codes are identifiers, not values to aggregate
Row IDMeasure (Number)Attribute (or hide)Row IDs aren’t business data

How to change a column type in OAC

  1. In the dataset view, locate the column in the grid or column list on the left.
  2. Click the small icon next to the column name (it shows # for number, A for attribute, calendar for date).
  3. In the column properties panel, change Treat As from Measure to Attribute for Year, Postal Code, and Row ID.
  4. For Latitude and Longitude, first set Treat As = Attribute, then assign the Location semantic (the 📍 pin icon appears next to the column name once OAC recognises it as a coordinate).
  5. Click Save to commit the dataset changes.

Clean nulls and invalid values — accuracy matters

AI answers are only as accurate as the data behind them. Before indexing, sweep each column for missing (null) or out-of-range values so the Assistant doesn’t average in zeros, mis-plot coordinates, or return misleading counts.

  1. Scan each column's value profile — the miniature bar chart at the top of every column shows a coloured breakdown. A red sliver indicates invalid or out-of-range rows; a grey sliver indicates null / empty cells.
  2. Filter out invalid rows — right-click the column header and choose Filter by Valid Values. This is especially important for Latitude and Longitude: a single 0/0 coordinate will stretch a map to the Gulf of Guinea and hide real customers.
  3. Handle nulls explicitly — don’t let them silently pass through. Depending on the column:
    • Measures (Sales, Profit, Quantity, Discount): replace nulls with 0 using the column’s Replace transform, only if a missing value truly means zero. If not, filter the row out instead — averaging in fake zeros skews every KPI.
    • Attributes (Segment, Category, Region, Customer Name): replace nulls with a literal label such as Unknown or Unassigned so the Assistant can still group by them instead of dropping those rows.
    • Dates (Order Date, Ship Date): never fabricate dates. Filter out rows where the date is null — time-series charts break otherwise.
  4. Remove duplicates and junk rows — if the preview shows header rows repeated mid-sheet, rows with all-null measures, or test records, add a filter step or use Remove Rows with Nulls from the column menu.
  5. Validate text consistency — use the Convert to Uppercase / Trim transforms on key join columns (e.g., Region, Segment) so “west”, “West”, and “WEST ” don’t end up as three separate values in AI answers.
  6. Re-check the value profile after each transform and only save once every column’s bar is solid green (no red or grey slivers for columns the AI will be asked about).
Dataset editor — Treat As = Attribute for Latitude and the Location Details option on the column context menu
Dataset editor showing Treat As = Attribute for Latitude/Longitude/Year/Postal Code/Row ID and the Location Details context menu
Year → Treat As: Attribute, Aggregation: None
Year column properties panel showing Treat As = Attribute, Data Type = Number, Aggregation = None
Latitude / Longitude → right-click → Filter by Valid Values
Latitude and Longitude column headers with the Filter by Valid Values menu option highlighted
Why this matters for AI: If Year stays a measure, the Assistant may try to sum it (e.g., “Total Year = 4,051,298”) instead of using it as a time dimension. If Latitude/Longitude stay as numbers, the Assistant can’t render a map. And if nulls or invalid rows slip through, the model will happily quote them back as facts — “Average Profit = $12.47” when half the rows were blank and got counted as zero. Getting column types, nulls, and invalid values right before indexing is what makes the AI Assistant accurate, not just confident.
Good news for Quick Start users: If you imported the SampleSales.dva from the Quick Start section, these type changes are already baked in — skip ahead.
Key Takeaway

A clean, well-structured dataset is the foundation of every AI interaction. Column names become the vocabulary your AI Assistant speaks — name them clearly, set the right types so numbers behave like numbers and dimensions behave like dimensions, and sweep out nulls and invalid values before indexing. Accuracy is earned at prep time — no amount of clever prompting can rescue a chart built on dirty data.

Quick Check — Test Your Understanding
Why do we upload a dataset rather than connect to a live database in this guide?
A dataset upload (.xlsx) gives every reader an identical, self-contained copy of the data — no database credentials, no network dependencies, and no risk of one person's query affecting another. It also makes this guide portable: you can follow along on any OAC instance, even a free trial.
Can the AI Assistant work with Subject Areas in addition to uploaded datasets?
Yes. The AI Assistant supports both datasets and Subject Areas. Subject Areas connect to live database sources and are often used in production. However, they require additional indexing configuration through the Data Model tab. For this guide, a dataset keeps things simple and focused on AI features.
🔍

Index the Dataset & Add Synonyms~15 min

Author Track

Indexing teaches the AI Assistant which columns exist and what values they contain. Synonyms map business terms to column names so the LLM understands your language. This is the most important setup step.

What you will achieve in this lab

Index your dataset and add synonyms so the AI Assistant understands your data columns, business terms, and common abbreviations — enabling accurate natural-language responses.

Step 2.1

Navigate to the Dataset and Open the Inspector

  1. From the Home page Navigator, click Data (in the bottom navigation bar)
Navigator → Data page
OAC Data page showing Navigator with Data selected
Right-click the dataset → select Inspect
Right-click context menu showing Inspect option
  1. Navigate to the SampleSales_Dataset you uploaded, then right-click on the dataset and select Inspect
  2. The Dataset Inspector opens, showing tabs on the left: General, Aliases, Data Elements, Search, Access, and Developer
  3. Click the Search tab
The Search tab has two sub-tabs: Settings and Scope. Settings is where you choose what to index for and set the schedule. Scope is where you select which columns to index, set Index Types, and add Synonyms.
Step 2.2

Configure Index Settings

On the Settings sub-tab of the Search tab:

  1. In the Index Dataset For dropdown, select Assistants and Homepage Search
  2. Under Languages, leave as English
  3. Under Indexing Schedule, leave the defaults for this exercise (you can choose “When Dataset is refreshed” or set a specific start time and repeat interval)
  4. Click Save (top-right) — do not close the Inspector
Search tab → Settings: Select “Assistants and Homepage Search”
Search Settings tab showing Index Dataset For dropdown
What “Assistants and Homepage Search” means: This enables the dataset for both the in-workbook AI Assistant and the Homepage search bar. If you only need the workbook Assistant, you can select “Assistants” alone. In this guide, we enable both so you can try Homepage queries in Lab 4.
Step 2.3

Configure Index Scope — Select Columns and Add Synonyms

Now click the Scope sub-tab. This is where the real tuning happens.

You will see a table listing all 27 columns with these columns:

ColumnWhat It Controls
AttributeThe column name from your dataset
Index (checkbox)Whether this column is included in the index — check to include
Sensitive Data (checkbox)If checked, restricts visibility to authorized users only (adds runtime overhead)
Index TypeName = LLM knows the column exists. Name & values = LLM also knows the actual data values (e.g., “Furniture”, “California”)
SynonymsAlternative business terms for this column — the most powerful tuning lever
    Search tab → Scope: Select columns to index, set Index Type, and add Synonyms
    Search Scope tab showing columns with Index, Index Type, and Synonyms
    1. Click Use Recommended Index Settings — this auto-selects the appropriate columns and sets Index Types
    1. Deselect columns that users won’t ask about in natural language: Row ID, Postal Code, Latitude, Longitude, Employee Phone Number
    2. Add synonyms for key columns (click the Synonyms field next to each column):
    Column NameRecommended SynonymsWhy
    SalesRevenue, Income, Total Sales, EarningsUsers may say “revenue” instead of “sales”
    QuantityUnits, Volume, Units Sold, QtyCommon shorthand
    DiscountDiscounts, Discount Amount, SavingsBusiness term flexibility
    CategoryProduct Type, Product CategorySome users think in product types
    Sub-CategorySubcategory, Product LineNaming variations
    Order DateDate, Sales Date, Transaction DateResolves date ambiguity
    SegmentCustomer Segment, Customer TypeMultiple ways to say it
    RegionTerritory, Area, Sales RegionConversational language
    Ship ModeShipping Method, Delivery ModeBusiness context
    1. Click Save
    2. Click Run Now to start indexing
    3. You should see a success message. You can click Check (top-right) at any time to verify the index status
    4. Click Close to exit the Inspector
    What just happened: The LLM now knows your dataset’s schema, column names, data values, and synonyms. When a user asks a question, the LLM maps their natural language to the correct columns. The index counter (e.g., “24/2000”) shows how many columns are indexed out of the maximum allowed.
    Sensitive Data warning: The Scope tab shows a yellow banner: “Indexed data is visible to all users with access to that column. For sensitive columns, enable Sensitive Data to restrict visibility.” This sample dataset has no sensitive data, so leave all Sensitive Data checkboxes unchecked.
Reference — Subject Areas

Indexing Subject Areas (Production Use)

In production, most enterprise customers use Subject Areas instead of file-based datasets. The indexing workflow is different:

  1. Navigate to ConsoleSearch Index
  2. Click Enable Data Model Crawl
  3. Select which subject areas, folders, and columns to index
  4. Set Crawl Status to Index (name & values) or Index Metadata Only (name only)
  5. Add synonyms in the Search Index configuration
  6. Set a crawl schedule (start date, time, frequency)
Local Subject Areas: If a subject area is too broad, create a Local Subject Area — a curated subset. This gives focused AI Assistant responses. Local subject areas are indexed via the InspectSearch tab, same as datasets.
Key Takeaway

Indexing teaches the AI what your data looks like; synonyms teach it how your team talks about that data. Both are essential for natural conversations.

Quick Check — Test Your Understanding
What does 'indexing' a dataset actually do for the AI Assistant?
Indexing scans every column and builds a metadata catalogue that the AI Assistant uses to understand your data's structure. It maps column names, data types, and sample values so the assistant can translate natural-language questions into accurate analytics queries. Without indexing, the AI Assistant has no idea what columns exist or what they mean.
Why are synonyms important, and what happens if you skip them?
Synonyms bridge the gap between business language and technical column names. If your column is called 'COGS' but users ask about 'cost of goods sold', the assistant won't match them without a synonym. Skipping synonyms means the AI can only understand questions that use the exact column names — which rarely matches how real users talk about data.
🚀

Quick Start — Skip the Setup, Jump to Asking~10 min

Shortcut Path — Optional

Eager to start asking questions? Skip Labs 1 & 2 and get to the fun part fast. Download the pre-built SampleSales.dva project from GitHub and import it into your own OAC instance — it ships with the dataset (already indexed), a ready-made workbook, and a starter Sales Agent. Add the small policy document to the Agent and you’re ready to ask.

What you’ll get once you import the .dva

After you import SampleSales.dva into your OAC instance (steps in QS.1 below), the following artefacts land in My Folders:

  • SampleSales_Dataset — the retail sales dataset, with synonyms such as Sales = Revenue pre-configured
  • A folder named SampleSales containing:
    • An existing Sample Sales workbook — open it and ask questions right from the Workbook AI Assistant
    • A pre-built Sales Agent — open it, attach the policy text file (QS.2), save, and ask questions

What you still need to do after import: add the small business-policy text file to the Sales Agent so it can answer questions about targets, KPIs, and regional strategy. Indexing is already enabled on the dataset for both AI Assistant and Homepage — only re-run it if the prompt window doesn’t return answers in your instance.

Quick Start · QS.1

Download the SampleSales.dva and Import it into Your OAC Instance

  1. Download the pre-built project from GitHub:
    ⬇️ Download SampleSales.dva
    ∼3.6 MB · Oracle Analytics portable project archive — bundles the dataset, workbook, synonyms, and a starter AI Agent in one file
  2. Open your own OAC instance and sign in. You’ll import the .dva here so you can run, edit, and ask questions against it.
  3. From the Home page (or Navigator → Catalog), click the Page Menu — the three dots beside the Create button in the top-right — and choose Import Workbook/Flow…
    OAC Page Menu showing the three-dot menu beside the Create button with Import Workbook/Flow option
    Page Menu (3 dots, top-right) → Import Workbook/Flow…
  4. In the Import Workbook/Flow dialog, click Change File, pick the SampleSales.dva you just downloaded, then click Import.
  5. By default, OAC imports everything into My Folders. After a successful import you’ll see:
    • SampleSales_Dataset — the dataset
    • A folder called SampleSales containing the Sample Sales workbook and the Sales Agent
  6. Check Indexing on SampleSales_Dataset. The imported .dva already ships with indexing configured for Assistants and Homepage Search, so in most cases you can skip straight to asking questions. You can confirm this from Inspect → Search → Settings — the top-right of the panel shows Last Run: Success with a date.
    Only re-run indexing if… the AI prompt window doesn’t return answers for this dataset in your own instance. To re-run it: right-click SampleSales_DatasetInspectSearch tab → on the Settings sub-tab make sure Index Dataset For is set to Assistants and Homepage Search, then click Run Now (or Check Now top-right) and wait for the run to complete. (Full walkthrough: Lab 2 — Indexing & Synonyms.)
    Prompt window disabled or not accepting input? This is almost always a permissions issue in your OAC instance. Open the dataset’s Inspect → Permissions (Access) panel and make sure your user (or the role you’re signed in as) has the right access — typically Author or Consumer — then reload the workbook or Agent.
  7. You now have two ways to start asking questions:

    Path 1 — Workbook AI Assistant

    Open the Sample Sales workbook inside the SampleSales folder and ask questions directly from the Workbook AI Assistant.

    Path 2 — Sales Agent

    Open the Sales Agent, upload the policy .txt file (see QS.2), Save, and start asking.

Tip: A .dva is Oracle Analytics’ portable project archive — it bundles datasets, workbooks, data-flows, and AI Agents into one file so they travel together between instances.
Quick Start · QS.2

Add the Policies Document to the Agent

The AI Agent uses this document as its knowledge source — it’s how the Agent learns your targets, KPIs, and business rules. You have two options:

Option A — Download

Grab the ready-made file from GitHub and use it as-is.

⬇️ Download sales_policies_targets.txt

Option B — Copy & Save

Copy the text below and save it locally as a .txt or .pdf file.

Any filename works — sales_policies_targets.txt is recommended.

Policy content (for Option B)

SALES DISCOUNT POLICY
  - Discounts above 30% require VP approval
  - Standard Class shipping default for orders under $500
  - Volume discounts: 5% for >50 units, 10% for >200 units

QUARTERLY TARGETS (2025)
  - Q1: $2.0M
  - Q2: $1.5M
  - Q3: $600K
  - Q4: $500K
  - Full Year Target: $4.5M

REGIONAL STRATEGY
  - East: Focus on Technology products
  - West: Expand Office Supplies distribution
  - Central: Grow Consumer segment penetration
  - South: Increase Furniture market share

KEY PERFORMANCE INDICATORS
- Primary KPI: Sales (also referred to as Revenue)
- Profitability KPI: Profit Ratio % = Profit / Sales × 100
- High-Value Customer Threshold: Sales > $35,000
- Default Ranking: Top 10 (unless user specifies otherwise)

QUARTERLY TARGETS (2026)
  - Q1: $2.4M
  - Q2: $1.8M
  - Q3: $700K
  - Q4: $600K
  - Full Year Target: $5.3M

FISCAL CALENDAR
- Fiscal Year: January 1 to December 31
- Quarters: Q1 = Jan–Mar, Q2 = Apr–Jun, Q3 = Jul–Sep, Q4 = Oct–Dec
- Dataset contains data through April 15, 2026

Save it anywhere convenient on your computer — Desktop is fine.

Upload it to the pre-built Agent and save

  1. Click the Navigator icon — the 9-dot grid in the top-left corner of Oracle Analytics — then choose Catalog.
  2. In the Catalog, locate the starter Agent that was imported with the .dva (named something like SampleSales Agent) and click to open it.
  3. Go to the Knowledge (Documents) tab → Upload Document.
  4. Select the file you downloaded or created (.txt or .pdf) and click Open.
  5. Click Save to commit the Agent with the new knowledge document.
Navigator icon (top-left 9-dot grid) → Catalog
Navigator menu opened from the 9-dot grid icon in the top-left, showing the Catalog section selected
Why this matters: The Agent now combines the indexed data (from the dataset) with your business context (from the .txt) — that’s what turns generic answers into decisions.
Quick Start · QS.3

Start Asking Questions

You’re ready. Two entry points — pick whichever matches your question:

  1. AI Assistant (data questions): Open the SampleSales_Dataset, then click the ✨ Sparkle icon in the workbook toolbar. Ask questions about what’s in the data — sales, profit, regions, customers.
  2. AI Agent (business-context questions): From the Navigator (9-dot grid, top-left) open Catalog, then click the starter Agent that came with the .dva and start prompting directly on the dataset. Ask questions that reference your policies or targets — the Agent pulls answers from both the data and your uploaded document.
Reference

About the Sample Data

Think of yourself as a regional sales analyst at a fictional US office-supplies & technology retailer. You’re responsible for tracking how the business is performing across the country, spotting what’s working and what isn’t, and reporting back against the company’s quarterly targets and regional strategy.

The SampleSales dataset is your full book of business. It captures every product sold on every order across the last several years — just over seven years of sales history, from January 2020 through mid-April 2026. That’s roughly $21M in total sales, ~$914K in profit, and about 18,000 order lines to explore.

The business sells across the entire United States, organized into six regions — East, West, Central, South, plus two sub-regions called S.East and Western. Customers fall into three segments: everyday Consumer shoppers, larger Corporate accounts, and independent Home Office buyers.

The product catalog spans three categoriesFurniture (bookcases, chairs, tables), Office Supplies (binders, paper, storage, art), and Technology (phones, accessories, machines, copiers) — broken down into 17 sub-categories in total. Every order has a customer, a shipping method, a location, a sales rep, and the usual measures you’d expect: sales, quantity, discount, and profit.

On top of the raw data, the AI Agent also knows your business context: quarterly revenue targets for 2025 and 2026, the regional focus strategy (East → Technology, West → Office Supplies, Central → Consumer, South → Furniture), KPI definitions (Profit Ratio, high-value customer threshold), and the discount-approval policy. That’s the layer the sales_policies_targets.txt file adds.

What you’ll be working on: answering the kinds of questions a sales leader asks on a Monday morning — Are we on track against target? Which region is over- or under-performing? Who are our top customers? Is the right category growing in the right region? Are we giving away too much in discounts? The AI Assistant answers from the data; the AI Agent answers in the context of your business.
Starter Questions

Try These First

Warm up with data-only questions in the AI Assistant, then switch to the AI Agent to see how the policy document changes the answers.

Ask the AI Assistant (data-only)

Top 10 customers by sales in 2025
Profit ratio by region for the Technology category
Show sales trend by year across all segments
Which sub-categories have the lowest profit margin?

Ask the AI Agent (data + policies)

Am I on track against my Q1 2026 target?
Which region should focus on Furniture, and how are we performing there?
List our high-value customers for 2025 (uses the >$35,000 threshold from the policy doc)
How did full-year 2025 compare to our $4.5M target?
Notice the difference: The Assistant answers what the data shows. The Agent answers what the data shows in the context of your business rules — targets, thresholds, and regional strategy.

Workbook AI Assistant~15 min

Author Track

Your dataset is now indexed and ready for AI. In Lab 2 you taught the LLM which columns exist, what values they contain, and how your business refers to them (synonyms). With that foundation in place, it’s time to put the AI Assistant to work — ask natural-language questions, build visualizations from a single prompt, and explore the automated insights the LLM generates from your data. The AI Assistant lives inside the workbook; it opens in a panel on the right side when you click the ✨ Sparkle icon.

What you will achieve in this lab

Use the Workbook AI Assistant to ask natural-language questions, generate visualizations, and validate that your indexed data responds accurately — all from the author perspective.

Step 3.1

Open a Workbook and Launch the Assistant

  1. From the Home page, double-click the SampleSales_Dataset dataset to create a new workbook
  2. In the workbook toolbar (top-right), click the ✨ Sparkle icon
  3. A panel opens on the right side of the workbook with three tabs:
Screenshot: Opening the Workbook AI Assistant
TabWhat It Does
WatchlistsSaved insights you’ve starred for ongoing monitoring
InsightsML-powered automated insights — patterns, drivers, anomalies
AssistantConversational AI — type questions, get visualizations
  1. Click the Assistant tab
  2. If indexing completed successfully, you will see a welcome message and a text box to type questions
Indexing in progress? If you open the Assistant immediately after triggering an index in Lab 2, you may see the message: “Unavailable Datasets: SampleSales_Dataset: Indexing in progress.” along with a Check Status button. This is normal — simply wait a few minutes and click Check Status until the dataset becomes available.
Screenshot: Indexing in progress status message
Hands-On Exercises

Step 3.2 — Ask Questions

Type the following prompts into the Assistant tab. Each demonstrates a different capability.

Exercise 1 — Basic Query
Show me sales by category
What happens: The Assistant generates a bar chart showing Furniture, Office Supplies, and Technology with their total sales.
Exercise 2 — Multi-Measure with Filter
Show me sales and profit by city for California
What happens: The LLM identifies Sales and Profit, uses “California” as a filter on State, and breaks down by City.
Exercise 3 — Time Trend
What is the monthly sales trend for 2025?
Exercise 4 — Follow-Up (Incremental)
Now break that down by region
What happens: The Assistant retains context and adds Region as a dimension. This is incremental conversation — build on previous answers without restating the full question.
Exercise 5 — Smart Modifier
Change it to a stacked bar chart
Exercise 6 — Top-N
What are the top 5 customers by sales?
Exercise 7 — Comparison
Compare sales across regions as a percentage
Exercise 8 — Built-In Knowledge
Show sales on US public holidays by city for year 2024
What happens: The LLM uses its public training data to identify US public holidays — information not in your dataset — and combines it with your Sales and City columns.
Screenshot: Exercise 8 result — US Public Holiday Sales by City in 2024 map visualization
Step 3.3

Add Visualizations to Your Workbook

  1. Hover over any visualization generated by the Assistant
  2. Click + Add to Canvas
  3. Click Additional Insights to see related insights
  4. Repeat to build a complete dashboard
  5. Click Save — name it AI Assistant Guide — Sales Dashboard
Screenshot: Add to Canvas button on AI-generated visualization Screenshot: Adding a visualization to the Watchlist — Daily watchlist and New Watchlist options
Watchlist: Click the watchlist icon on any AI-generated visualization to save it. You can add it to a Daily watchlist or create a New Watchlist. Watchlist items appear on your Home page and in the Watchlists tab for quick access.
Key Takeaway

The Workbook AI Assistant turns every visualization into a conversation. Ask, refine, pin to Canvas or Watch List — analytics becomes as natural as chatting.

Quick Check — Test Your Understanding
What is 'Built-In Knowledge' and how is it different from an AI Agent's knowledge documents?
Built-In Knowledge is the AI Assistant's understanding of your indexed dataset — column names, data types, and relationships. It answers questions purely from the data. An AI Agent's knowledge documents (RAG) add business context like policies, targets, and definitions that don't exist in the dataset. Together, they combine data literacy with business intelligence.
What is the difference between adding a result to the Canvas versus the Watch List?
Add to Canvas places the AI-generated visualization directly onto a workbook page as a permanent tile you can resize, filter, and interact with — it becomes part of the workbook. Add to Watch List saves it as a monitored insight in the Insights Panel's Watch List tab, where you can track it over time without cluttering your canvas layout.
🤖

Create and Configure an AI Agent~15 min

Author Track

This is a required author lab. In Labs 2–3 you used the AI Assistant — a generic LLM with access to your data. It answered questions, but it didn’t know your business rules, KPI formulas, fiscal calendar, or policies. AI Agents change that. By adding Supplemental Instructions and Knowledge Documents (RAG), you transform a generic brain into a governed, domain-expert brain that interprets questions exactly the way your organization expects. Authors create the Agent; consumers access it through the workbook in Present / consumer mode after the author attaches it.

What you will achieve in this lab

Create an AI Agent that applies your business rules, KPI definitions, and domain knowledge — transforming a generic AI into an expert that answers questions the way your organization thinks.

Generic Brain vs. Governed Brain — why accuracy matters:
Without instructions: “Show me performance by segment” → Agent shows a raw record count by segment.
With instructions: “Show me performance by segment” → Agent shows Revenue by segment, sorted descending, highlights growth vs. decline, uses your fiscal calendar.

The difference is Supplemental Instructions. They are the soul of your Agent — they close the gap between what the LLM guesses and what your business actually means.
Step 4.1

Create the Agent Shell

  1. From the Home page, click CreateAI Agent. If you are already in the AI Agents area, click Create Agent.
  2. Name the agent Sample Sales Analyst.
  3. Save the agent once so the configuration is created.
Screenshot: Create menu showing AI Agent option
Author requirement: Create the Agent using an author-capable account. Oracle lists AI Agent authoring under Oracle Analytics permissions, and the workbook connection step later also assumes author access.
Step 4.2

Connect the Agent to Its Data Source

  1. Open the new agent and click Add Data Source.
  2. Select DatasetSampleSales_Dataset. Oracle Analytics also supports Subject Area and Local Subject Area as Agent sources.
  3. Confirm the dataset is already indexed from Lab 2 before you continue. Oracle documents one dataset per AI Agent.
  4. Use the Agent editor to review indexed columns, activate only the fields you want the Agent to reference, and define any Agent Filters that should always apply to every question.
  5. The Agent inherits the indexing and synonyms already defined on that source.
Screenshot: Add Data dialog showing SampleSales_Dataset selected
No separate synonyms inside the Agent: Do not look for a second synonyms screen in AI Agents. Synonyms are maintained on the indexed dataset or subject area and then reused by the Agent. If the Agent misinterprets a term, go back to Lab 2 and add/refine synonyms there.
Step 4.3

Add Supplemental Instructions (R.T.C.C.O.E. Framework)

Supplemental Instructions encode your business logic, vocabulary, output guidance, and default behaviors (up to 6,000 characters). Use the R.T.C.C.O.E. framework to structure them for maximum accuracy:

LetterComponentPurpose
RRoleWho the Agent is — define persona and domain expertise
TTaskWhat it does — core analytical workflow and responsibilities
CContextBusiness rules — fiscal calendar, KPI formulas, terminology
CConstraintsHard limits — non-negotiable rules the Agent must always follow
OOutputResponse format — chart types, visualization preferences
EExamplesFew-shot query → response pairs — the single biggest quality multiplier

Paste the following instructions into the Instructions field:

Sample Instructions (R.T.C.C.O.E.) — Copy & Paste Ready
ROLE: You are a Senior Sales Analytics Expert specializing in revenue analysis and customer segmentation for our retail business. TASK: Answer questions with accurate data visualizations. Provide metric → insight → recommendation patterns. Highlight anomalies. CONTEXT (Business Rules): - Fiscal year: January 1 to December 31 - The dataset contains data through April 15, 2026. When users ask about “current year” or “this quarter”, use the latest available data. - Profit Ratio % = Profit / Sales × 100 - “High-value customers” = Sales > $35,000 - When comparing regions, include Sales AND Profit CONSTRAINTS (Hard Rules): - Default KPI for “performance” = Sales - Default ranking = Top 10 (unless user specifies) - Never fabricate data if a column doesn’t exist - Always show applied filters in response OUTPUT (Visualization Preferences): - “Sales Dashboard” = Top 10 Products by Sales, Horizontal Bar chart - Category comparisons → Table - Time trends → Area Chart - Single KPI → Card with comparison context EXAMPLES (Accuracy Anchors): User: “Revenue this quarter” Filter: Q2 2025, metric = Sum(Sales), chart = Table with summary card User: “Top customers by margin” Rank by Profit Ratio %, limit Top 5, chart = Horizontal Bar
Why Examples matter most: The E (Examples) component is the single biggest factor for accuracy improvement. When you give the LLM concrete query → response pairs, it learns exactly which filters to apply, which metrics to use, and which chart type to produce. Even 2–3 well-crafted examples dramatically reduce misinterpretation.
Step 4.4

Add the Welcome Message and Save the Agent

  1. Enter a clear welcome message: “Welcome! I’m your Sales Analytics Expert. Ask me about sales performance, products, regions, customer segments, and trends. Try: ‘Show me the Sales Dashboard’ or ‘Who are our high-value customers?’”
  2. Add 2–4 starter examples so users know what kinds of questions the Agent is designed to answer.
  3. Click Save to save the Agent.
Tip: Include 2–3 sample questions in your Welcome Message. Users often don’t know what to ask first — examples anchor expectations and give them an instant starting point.
Why save now? You must save the Agent first to activate the Knowledge Documents upload button. Without saving, the upload option remains disabled.
Step 4.5

Upload Knowledge Documents (RAG)

Knowledge Documents extend the Agent’s knowledge beyond the dataset. Upload up to 10 PDF or TXT files (each file must be under 5 MB). In newer OAC releases you can also assign document priority levels such as High, Regular, or Low.

InstructionsKnowledge Documents
How to interpret and respondWhat to know (facts, policies, targets)
Up to 6,000 charactersUp to 10 files (PDF or TXT)
Define formulas, defaults, chart preferencesContain policies, targets, strategies, glossaries
Always active for every queryRetrieved on demand when relevant to a query (RAG)

Create a file like this to use with your Agent:

Example: sales_policies_targets.txt — Copy & Paste Ready
SALES DISCOUNT POLICY - Discounts above 30% require VP approval - Standard Class shipping default for orders under $500 - Volume discounts: 5% for >50 units, 10% for >200 units QUARTERLY TARGETS (2025) - Q1: $2.0M - Q2: $1.5M - Q3: $600K - Q4: $500K - Full Year Target: $4.5M REGIONAL STRATEGY - East: Focus on Technology products - West: Expand Office Supplies distribution - Central: Grow Consumer segment penetration - South: Increase Furniture market share KEY PERFORMANCE INDICATORS - Primary KPI: Sales (also referred to as Revenue) - Profitability KPI: Profit Ratio % = Profit / Sales × 100 - High-Value Customer Threshold: Sales > $35,000 - Default Ranking: Top 10 (unless user specifies otherwise) QUARTERLY TARGETS (2026) - Q1: $2.4M - Q2: $1.8M - Q3: $700K - Q4: $600K - Full Year Target: $5.3M FISCAL CALENDAR - Fiscal Year: January 1 to December 31 - Quarters: Q1 = Jan–Mar, Q2 = Apr–Jun, Q3 = Jul–Sep, Q4 = Oct–Dec - Dataset contains data through April 15, 2026
Step 4.6

Save the Agent

  1. Review all the sections you have configured — Data Source, Instructions, Welcome Message, and Knowledge Documents.
  2. Click Save to save the final Agent configuration.
Screenshot: Saved Sales Agent showing Instructions, Welcome Message, and uploaded Knowledge Document
Checkpoint: At this point your Agent has a data source, instructions, a welcome message, and a knowledge document. You are ready to choose how to deliver it and test for accuracy.
Step 4.7

Associate the Agent to a Workbook

Now that the Agent is built, let’s connect it to a workbook so users can get AI-powered insights. Open the workbook you saved in Lab 3 and associate the Agent:

  1. Open the workbook and click the Present tab in the top menu
  2. In the left panel, expand Insights Panel and toggle it to On. Make sure Watchlists and Workbook Assistant are both set to On.
  3. Under Workbook Assistant, click the + button next to Agents
  4. In the Select an AI Agent dialog, navigate to your folder and select Sales Agent
  5. Click OK to associate the Agent to the workbook
  6. Save the workbook
Screenshot: Associating the Sales Agent to the workbook via Present tab — Insights Panel, Workbook Assistant, and Select an AI Agent dialog
Step 4.8

Use the Agent — Two Ways

Now that the Agent is built and associated to a workbook, there are two ways to interact with it:

Path 1 — Standalone (Author / Direct): As an author, you can open and test the Agent directly from the AI Agents area. Consumers with the appropriate permissions (see Admin Pre-Check) can also run the Agent directly as a standalone experience.
Path 2 — Workbook (Consumer Mode): Consumers open the published workbook in Present / consumer mode and interact with the Agent through the Workbook Assistant panel. This is the primary delivery path for end users.
Hands-On Exercises

Step 4.9 — Test the Agent for Accuracy

Before publishing an Agent to users, you must systematically test for accuracy. Use the following test plan, which covers five dimensions:

📋 Accuracy Test Plan — 5 Dimensions
1⃣ Terminology — Does the Agent understand business terms? (synonyms, aliases)
2⃣ Business Logic — Does it apply formulas and thresholds correctly?
3⃣ RAG Retrieval — Does it find and cite knowledge documents?
4⃣ Output Format — Does it produce the right chart type and layout?
5⃣ Edge Cases — How does it handle ambiguity, missing data, or multi-part questions?
Test 1 — Default Metric
Show me performance by region
✅ Expected: The Agent should default to Sales (not a random metric). Validates the Constraint: “Default KPI for performance = Sales.”
Test 2 — Terminology
Show me revenue by region
✅ Expected: Uses the Sales column (mapped from the synonym “Revenue” in Lab 2). If it fails, refine synonyms in the dataset Inspector.
Test 3 — Business Logic
Who are our high-value customers?
✅ Expected: Applies the $35K threshold from instructions and returns customers with Sales > $35,000. Verify the filter is shown in the response.
Test 4 — RAG Document Retrieval
Are we on track for our Q2 target?
✅ Expected: Retrieves the $1.4M target from the knowledge document, compares to actual Q2 Sales, and provides context (ahead/behind target, by how much).
Test 5 — Output Format (Dashboard Shortcut)
Show me the Sales Dashboard
✅ Expected: Generates a Top 10 Products by Sales horizontal bar chart per the instructions. Verify chart type matches the “Output” section of R.T.C.C.O.E.
Test 6 — Combined / Multi-Part
What is our regional strategy for Central and how is the Consumer segment performing there?
✅ Expected: Combines RAG retrieval (Central strategy = “Grow Consumer segment penetration”) with data query (Consumer segment Sales in Central region). Both knowledge and data should appear.
Test 7 — Edge Case
What is our revenue in Antarctica?
✅ Expected: Gracefully reports no data found — not fabricated numbers. Validates the constraint: “Never fabricate data.”
Author takeaway: Do not publish an Agent until you test at least one prompt for default metric, terminology, time logic, RAG retrieval, output format, and one edge case. That is the fastest way to verify whether the Agent will behave consistently for consumers.
Step 4.8

Iterate — The Accuracy Improvement Cycle

Agent accuracy is not a one-time setup. Use this continuous cycle after each round of testing:

  1. Test — Run sample queries covering all 5 accuracy dimensions
  2. Identify gaps — Which questions produce wrong metrics, wrong charts, or fabricated data?
  3. Diagnose the root cause:
SymptomRoot CauseFix
Wrong column usedMissing synonymAdd synonym in dataset Inspector (Lab 2)
Wrong formula / thresholdInstruction not specific enoughRefine the Context or Constraints section
Policy not citedKnowledge doc not retrievedUse clearer section headings in the TXT/PDF file
Wrong chart typeMissing Output ruleAdd a specific “query → chart type” rule in Output section
Data fabricatedMissing constraintAdd “Never fabricate data” to Constraints
Ambiguous responseNo example providedAdd a few-shot Example for that query pattern
  1. Update — Modify instructions, add synonyms, or improve knowledge documents
  2. Re-test — Validate the fix with the original failing query and existing passing queries (regression check)
  3. Expand — Once accuracy is validated, publish to broader user base and collect thumbs up/down feedback
Reference

Pre-Deployment Accuracy Checklist

Before publishing your Agent to users, validate every category. An Agent that passes this checklist will perform reliably and maintain user trust.

CategoryValidation
📊 Data IntegrityDataset fully indexed • Agent Filters configured (if needed) • Column subsetting exposing only relevant columns • Sample queries return accurate results
📚 Logic LimitsInstructions under 6,000 chars • Structured using R.T.C.C.O.E. • All KPI formulas tested against business definitions • No contradictory rules
💡 Knowledge BoundsKnowledge documents uploaded and retrievable • Documents have clear section headings • No outdated or conflicting information
⚙️ Default BehaviorsDefault metric, default ranking, default time period all defined • “Never fabricate” constraint in place • “Always show filters” constraint in place
🎯 Examples IncludedAt least 2–3 few-shot examples covering your most common queries • Examples tested and producing correct results
✅ Testing CompleteTested terminology, business logic, RAG retrieval, output format, and edge cases • Alternative terms tested • Multi-part queries tested
Key Takeaway

An AI Agent is more than a chatbot — it combines structured instructions (R.T.C.C.O.E.), business knowledge (RAG documents), and data access into an intelligent analytics partner.

Quick Check — Test Your Understanding
What does R.T.C.C.O.E. stand for and why does this framework matter for AI Agent instructions?
R.T.C.C.O.E. stands for Role, Task, Context, Constraints, Output, Examples. It matters because LLMs perform dramatically better with structured prompts. Role sets the persona, Task defines the mission, Context gives background, Constraints set boundaries (like thresholds), Output specifies format, and Examples show the expected pattern. Without this structure, agent responses tend to be generic and inconsistent.
What is the difference between Supplemental Instructions and Knowledge Documents?
Supplemental Instructions (up to 6,000 characters) are always active — they guide every single response the agent produces. Think of them as the agent's personality and rules. Knowledge Documents (up to 10 files, 5 MB each) are retrieved on demand via RAG — the agent searches them only when a question requires business context like targets or policies. Use instructions for behavior; use knowledge docs for reference data.
Why must you save the Agent before uploading Knowledge Documents?
The Knowledge Documents upload button is disabled until the Agent is saved. This is by design — Oracle needs a persisted Agent object to attach files to. Think of it as creating a folder before you can put files in it. Always: name → configure → save → then upload documents.
🚀

Publish the Consumer Experience

Author Track

This is the handoff step between the author experience and the consumer experience. You have already built the workbook. Now you will turn on the workbook features that let end users open it in consumer mode and interact with AI. This requires admin permissions from Lab 8 plus workbook-level enablement by the author.

What you will achieve in this lab

Enable the AI experience for consumers by turning on the Insights Panel, attaching your AI Agent to the workbook, and sharing it — so anyone on your team can start asking questions immediately.

Prerequisite — Admin / Author

Enable AI Assistant for Consumer Role Users

Before consumers can use the AI Assistant inside workbooks, an administrator must create an application role with the correct permission and assign users to it. This is a one-time setup.

Step 1 — Create an Application Role

  1. Navigate to NavigatorConsoleRoles and PermissionsApplication Roles.
  2. Click Create Application Role.
  3. Enter a name (e.g. Consumer Assistant Role) and a description.
  4. Click Create.

Step 2 — Add Memberships

  1. Open the new role and go to the Memberships tab.
  2. Click Add Application Roles.
  3. Select DV Consumer (to inherit base consumer capabilities).
  4. Click Add Selected.

Step 3 — Add the Permission

  1. Go to the Permissions tab.
  2. Click Add Permissions.
  3. Search for and select Use Assistant in Workbooks.
  4. Click Add Selected.

Step 4 — Assign Users

  1. Go to the Members tab.
  2. Click Add Users to assign individual users, or click Groups to assign an entire group at once.
  3. Search for the desired users/groups, select them, and click Add Selected.
Step 5.1

Turn On Workbook Assistant in the Present Tab

  1. Open the workbook you saved in Lab 3 (AI Assistant Guide — Sales Dashboard)
  2. Click the Present tab in the top menu
  3. In the left-hand menu, locate Insights Panel
  4. Toggle Insights Panel to On
  5. Select which tabs to display to consumers:
    • Watch List — allows consumers to see and track saved metrics
    • Workbook Assistant — enables AI Assistant queries on this workbook’s dataset
    Turn on both for the full experience.
  6. Save the workbook
Screenshot: Insights Panel toggle enabled in the Present tab with Watch List and Workbook Assistant options
What you just did: You enabled the AI experience for this specific workbook in consumer mode. This is a workbook-level setting — you must repeat it for each workbook you want consumers to open with AI. This same Insights Panel entry point is also how consumers access the author-attached Agent inside the workbook when they open it in Present / consumer mode.
Consumer access requires three things:
(1) The admin has created a role with the Use Assistant in Workbooks permission and assigned the consumer to it (see Lab 8).
(2) The author (you) has indexed the dataset and added synonyms (Lab 2).
(3) The author (you) has enabled the Insights Panel in the Present tab (this step).
If any of these is missing, the consumer will not see the Assistant.
Step 5.2

Save and Share the Workbook with Consumers

  1. Save the workbook in a shared folder.
  2. Grant the appropriate workbook access to the consumer users or roles who need access.
  3. Share the workbook URL or direct consumers to the shared folder location.
  4. If you want consumers to use the Agent from the workbook, make sure you completed Lab 4 and selected the Agent in the Workbook Assistant settings before consumers begin Lab 6.
Practical handoff: Consumer mode only helps if the workbook is actually shared and reachable by the audience you assigned in the admin role step.
Key Takeaway

Publishing is the bridge between author and consumer. Three things must align: role permissions, Insights Panel toggle, and indexed data. Miss one and the AI stays hidden.

Quick Check — Test Your Understanding
What are the three requirements for consumers to see the AI Assistant in a published workbook?
All three must be true: 1) The consumer's role has 'Use Assistant in Workbooks' enabled. 2) The workbook is published with Present tab → Insights Panel → On. 3) The workbook has at least one indexed dataset (or an associated AI Agent). If any one is missing, the Insights Panel simply won't appear for the consumer.
Why is the Insights Panel a per-workbook setting rather than a global toggle?
Making it per-workbook gives authors fine-grained control. Some workbooks may contain sensitive data where AI-generated insights aren't appropriate, or the data may not be indexed yet. A per-workbook toggle lets authors enable AI only on workbooks that are ready for it — rather than forcing it everywhere or nowhere.
👤

Consumer Experience

Consumer Track

This lab is for consumer users. Consumers do not upload data, configure indexing, define synonyms, or create Agents. Instead, they use the AI experience that the author has already prepared and shared. Your job is to open the shared workbook in consumer mode and interact with AI through the workbook Insights Panel. If the author attached an AI Agent to this workbook, you access that Agent through the same workbook entry point. In other words, consumers can use AI Agents — they just use the version that the author already created and published. This matches Oracle’s intended model: authors design and publish the experience, while consumers interact with it in context.

What you will achieve in this lab

Experience Oracle Analytics AI from the consumer perspective — open a shared workbook, ask questions in plain English, interact with the AI Agent, and save insights to your Watchlist.

Prerequisites

Before You Begin

To use the AI Assistant as a consumer, the following must already be in place:

  1. An administrator has assigned you to a role with the Use Assistant in Workbooks permission (for example, a custom “AI Assistant Consumer” role — see Lab 8)
  2. An author has created a workbook, indexed the dataset, and enabled the Insights Panel in the Present tab
  3. The author has shared the workbook with you
Quick check: If you open a shared workbook and do not see the ✨ Sparkle icon, the most likely cause is a missing Use Assistant in Workbooks permission on your role. Ask your administrator to verify Lab A (Admin Pre-Check) is complete.
If you cannot see the Assistant: The most common reason is that one of the three prerequisites above is missing. Contact your administrator or the workbook author.
Step 6.1

Open the Shared Workbook

  1. Log in to your OAC instance
  2. From the Home page, find the workbook that has been shared with you (e.g., AI Assistant Guide — Sales Dashboard)
  3. Click to open it — it opens in consumer/view mode
Step 6.2

Launch the AI Assistant

  1. In the workbook toolbar, click the ✨ Sparkle icon.
  2. The Insights panel opens on the right. Depending on what the author published, you may see:
    • Watchlists — saved insights
    • Assistant — the default workbook conversational experience
    • An attached Agent experience — if the author connected an AI Agent to this workbook in the Present tab
  3. Use the standard Assistant tab for the default workbook AI experience, or switch to the configured Agent if one is available. In the workbook scenario, the Agent uses the same workbook entry point; consumers do not have to open a separate design screen to use it.
Hands-On Exercises

Step 6.3 — Ask Questions as a Consumer

Type these prompts and see the results:

Consumer Exercise 1
Which region has the highest sales growth?
Consumer Exercise 2
Show me bottom 5 products by quantity sold
Consumer Exercise 3
What is the profit trend by quarter for 2025?
Consumer Exercise 4 — Follow-up
Break that down by segment
Step 6.4

Save Insights to Your Watchlist

  1. Hover over any visualization generated by the Assistant
  2. Click ☆ Add to Watchlist
  3. Switch to the Watchlists tab to see your saved insights
  4. These also appear on your OAC Home page for quick access
Important Limitation: Canvas-level filters on the dashboard (e.g., a region dropdown) do not automatically carry over to the AI Assistant. You must include filter values in your question — say “sales for the East region” rather than relying on a dashboard filter.
Key Takeaway

Consumers see the same AI power without the complexity. They interact through the Insights Panel — asking questions, getting agent-enhanced answers, and building Watch Lists.

Quick Check — Test Your Understanding
How do consumers access the AI Agent in a published workbook?
Consumers open the published workbook and click the Insights Panel icon (or it appears automatically if configured). Inside, they see two tabs: Watch List (for saved insights) and Workbook Assistant (for asking questions). The Agent's welcome message and knowledge-powered responses appear here. Consumers never see the Agent configuration — only its outputs.
If the AI Agent returns an incorrect threshold (e.g., $50K instead of $35K for high-value customers), what would you fix?
Update the Supplemental Instructions where the high-value customer threshold is defined. Since instructions are always active, the agent references them for every response. Change Sales > $50,000 to Sales > $35,000 and save. You may also check the Knowledge Document if the threshold appears there. The fix is always in the agent's configuration — never in the data itself.
🏠

Homepage AI Assistant~10 min

All Users

The Homepage AI Assistant is your fastest path from login to insight. The moment you sign in to Oracle Analytics, you can type a single prompt and get a complete, multi-visualization dashboard — no workbook setup needed. Think of it as the front door to AI-powered analytics: start broad on the Home page, then dive deep into workbooks and Agents when you need more.

The Homepage AI Flow
Login → Ask (Shift+Enter) → Dashboard → Refine → Deep Dive

1. Login & Ask: Sign in to OAC. In the Home page search bar, type a single data-related question and press Shift + Enter — the AI builds a dashboard with an insights summary, up to five visualizations, and related-content links.
2. Follow-Up: Type a follow-up (e.g., “Can you add the city?”) and press Enter to update the existing dashboard. Toggle between questions using the breadcrumbs on the left.
3. Explore or Modify: Click Data to swap the dataset, or Explore as Workbook to open the result as a new workbook you can edit.
4. Invoke AI Assistant: Inside the workbook, click the Sparkle icon to open the AI Assistant for deeper, dataset-specific Q&A.
5. Use the Agent: If an AI Agent is attached to the workbook, the Agent’s business rules, KPI definitions, and knowledge documents enhance every answer.
Prerequisites — what must be true before Homepage queries work:
  • Index your datasets for Assistants and Homepage Search. A dataset won’t surface in Home page results until it’s indexed — see Lab 2 — Indexing & Synonyms.
  • Certify datasets you want to rank high in search results. Certified datasets are the ones the Homepage AI prefers when multiple options could answer a question.
  • Assign synonyms on dataset columns using terms familiar to your users — this is what makes natural-language prompts reliable.
Step 7.1

Build a Complete Dashboard from a Single Prompt

  1. Navigate to the OAC Home page.
  2. Click the Search bar at the top.
  3. Type a single data-related question and press Shift + Enter to have the Homepage AI Assistant build a visualization or dashboard:
Homepage Prompt 1 — Location Dashboard
Give me a comprehensive location-based performance dashboard from SampleSales
Homepage Prompt 2 — Executive Dashboard
Build an executive profitability dashboard showing margins by category and region
What the AI returns: The resulting dashboard displays an LLM-created insights summary section, up to five visualizations, and links to related content — all from one prompt.
Enter vs. Shift+Enter: Shift + Enter tells OAC to build a dashboard from your question. Plain Enter simply runs a catalog search. For Homepage AI, always use Shift + Enter on the first prompt.
Threads on the left: Every dashboard you generate is saved as a thread on the left side of the page, so you can toggle between results without losing any of them.
Step 7.2

Refine with Follow-Up Questions

The Homepage AI maintains conversational context. After the initial dashboard is generated, type a follow-up question in the same prompt bar and press Enter — the existing visualizations update in place.

Follow-Up 1 — Add a Field
Can you add the city?
Follow-Up 2 — Time Filter
Can you only show information for this fiscal year?
Follow-Up 3 — Region Filter
Now filter this to show only the East region
Follow-Up 4 — Add Breakdown
Add a breakdown by customer segment
Breadcrumbs on the left: On the left side of the page, click the breadcrumbs to toggle through previously asked questions in the thread — each one restores the dashboard state at that step.
Conversational refinement: Each follow-up adjusts the existing dashboard rather than creating a new one. To start fresh with a new dashboard, press Shift + Enter again — OAC will create a new thread for it.
Step 7.3

Explore or Modify Your Results

From the generated dashboard you have two main levers to reshape the output:

  • Click Data (next to the dataset or subject-area name) to point the same question at a different dataset or subject area.
  • Click Explore as Workbook to open the visualization in a new workbook — from there you can edit, rearrange, add charts, and continue in the Workbook AI Assistant.

Deep-dive in the Workbook AI Assistant

Once the dashboard is open as a workbook:

  1. The workbook opens in Visualize mode — you can now edit, rearrange, and add your own visualizations.
  2. Click the ✨ Sparkle icon (top-right) to open the AI Assistant panel.
  3. Now ask dataset-specific questions just like in Lab 3:
Deep Dive 1
Who are our high-value customers in the East region?
Deep Dive 2
What is the profit ratio trend for Technology products?
  1. If an AI Agent has been attached to this workbook (Lab 4), the Agent’s business rules and knowledge documents will automatically enhance every response.
The complete AI journey: You started from the Home page with a broad intent, refined it with follow-ups, opened it as a workbook, and now you’re doing deep exploration with the AI Assistant and Agent — all without writing a single formula or building a single chart manually.
Key Takeaway

The Homepage AI is your zero-to-dashboard express lane. Start with intent, refine with follow-ups, then dive deep in the workbook — a complete AI-powered analytics journey.

Quick Check — Test Your Understanding
How is the Homepage AI Assistant different from the Workbook AI Assistant?
The Homepage AI is your starting point — you describe an intent in natural language and it builds a complete visualization from scratch, even creating a new workbook. The Workbook AI works within an existing workbook, answering questions about the data already on the canvas. Think of Homepage AI as 'create from nothing' and Workbook AI as 'explore what's here'.
Describe the complete AI journey from Homepage to deep workbook analysis.
The full journey flows like this: 1) Start on the Homepage and type a broad intent (e.g., 'Show me regional sales trends'). 2) The AI builds a complete dashboard instantly. 3) Ask follow-up questions to refine it. 4) Save the result as a workbook. 5) Open that workbook, invoke the Workbook AI Assistant and AI Agent for deep exploration with business context — all without writing a single formula or manually building a chart.