Skip to main content

Basic Information

Overview

Basic Information lets you configure frontend agent display, related datasets for model learning, Recommend Dashboard behavior, recommended questions, guided questions, Personalized Memory, and Insight switches.

Basic Configuration

Agent Display Settings

This section shows the basic configuration of the current agent. You can modify the avatar, welcome message, and Agent Description here.

No.Description
1The Q&A avatar defaults to the Guandata logo. Click Upload Image to change the frontend avatar, or click Random to let the system generate one automatically. Clicking the avatar opens a configuration panel where you can quickly choose an icon and background color.

|300
2Click Edit to modify the frontend welcome message. The welcome message supports rich-text editing and references to specific attributes.
  • Rich-text editing: customize text styles and paragraph styles.
  • Hyperlinks: add page links and external links.
  • Specific attribute references: reference User Attributes and dataset update times.
  • Separate title and body: configure the title and body independently.
  • 3Click Edit to modify the Agent Description.

    Dataset Configuration

    Manage Datasets

    • Add Dataset

      Click Add Dataset to add a new dataset to the agent. If the dataset name contains any of the following special characters, the dataset cannot be added because special characters seriously affect the model's ability to generate accurate table names. We recommend renaming BI datasets before adding them to the agent. This does not affect downstream card or ETL references.

      Special character list:

      [" ", "\t", "\n", "\r","-", "+", "*", "/", "%", "^", "&", "|", "~", "=", "<", ">", "!", "?",",", ".", ":", ";", "'", "\"", "`", "(", ")", "[", "]", "{", "}","@", "#", "$","¥", "€", "£", "¢", "¤","「", "」","(",")"]
      Note

      Datasets that have already been added to the agent are not affected.

    • Dataset Quality Validation

      After datasets are added, the system automatically performs quality checks. Datasets that still contain anomalies after validation are marked in the related dataset list.

    • View Dataset Details

      To view dataset details, click a dataset to jump to the Data Preparation > Dataset detail page. For the description of that page, see View Dataset.

    • Switch Dataset

      Click the button to switch datasets. After selecting the target dataset, users can map fields from the current dataset to fields in the target dataset. After confirming the mapping and clicking Confirm, entries in Q&A Sample and the test answer set that reference the current dataset and fields are replaced with the target dataset and mapped fields. The related sample SQL is then revalidated and the SQL validity status is updated.

    • Delete Dataset

      Click the button to remove the related dataset. The delete operation requires a second confirmation to avoid accidental deletion.

    Learn Datasets

    • Automatically Trigger Dataset Learning

      When datasets are created or modified for an agent, the system automatically triggers dataset re-learning. In the list, you can view Latest Learning Completion Time, Trigger Method, and Dataset Learning Status. If learning fails, the failure reason is shown.

      Note

      Automatic learning is triggered once per day.

    • Manually Trigger Dataset Learning

      • Single dataset learning: click Refresh in the action column of a dataset to trigger learning for that dataset only.

      • Batch dataset learning: select multiple datasets, enter batch operation mode, and click Learn Selected to trigger learning for all selected datasets.

      • Learn all datasets: click Learn All in the upper-right corner to trigger re-learning for all datasets.

    • Field Enumeration Learning

      Click Field Learning Configuration in the action column of a dataset. In the dialog, select the fields to learn and click Confirm to trigger enumeration value learning for those fields.

      If you do not want a field to be learned by the model, enable Disabled. Disabled fields are excluded from model-generated queries, which helps reduce interference from irrelevant fields, improve query accuracy, and protect sensitive fields from being queried.

    • View Learning History

      Click Learning History in the dataset action column to view learning records for the past 30 days.

    Metric Summary Table

    Metric Summary Table is used for datasets with a metric-dimension structure. After it is enabled, the system converts the metric dimension in query results from rows to columns, making it easier for users to analyze the data as a standard two-dimensional table.

    Switch Behavior Comparison

    StatusEffect
    Disabled (default)The table is treated as a normal dataset, and SQL query results are displayed directly without transpose logic.
    EnabledThe table is treated as a metric summary table, and the system automatically transposes query results by turning the metric dimension from rows into columns.

    Applicable Scenarios

    Metric Summary Table is mainly used to process EAV (Entity-Attribute-Value) datasets. For example, if the original data stores metric names in one column and metric values in another column, enabling this feature converts each metric name into an independent column and produces a standard two-dimensional table for easier querying by column name.

    Example

    Original data format (EAV):

    CustomerMetric NameMetric Value
    ASales Amount1000
    AProfit200
    BSales Amount1500
    BProfit300

    After transpose (standard 2D table):

    CustomerSales AmountProfit
    A1000200
    B1500300
    Note
    • The Metric Summary Table switch should be configured before dataset learning. For datasets that have already been learned, trigger learning again to ensure the transpose rule takes effect.
    • If the dataset does not contain a metric dimension field, enabling this switch has no actual effect.

    Recommend Dashboard

    Recommend Dashboard intelligently matches user questions with dashboards already associated with the agent. It is disabled by default.

    After the feature is enabled, when an end user completes a question, the system uses the LLM together with the user question and the preconfigured dashboard scope to recommend up to three highly relevant analysis cards. This helps guide users into deeper data exploration.

    Feature Switch

    • After an agent is created, the Recommend Dashboard feature can be enabled or disabled on the Agent Detail Settings > Basic Information page.
    • After it is disabled, related learning tasks can still be triggered, but dashboard card recommendations are no longer shown when users ask questions.

    Set the Recommendation Scope (Related Dashboards)

    • Add dashboards: click Add Dashboard on the right to manually select one or more dashboards from the existing list and include them in the recommendation scope. The system then searches only within that scope for relevant cards.
      • Manage added dashboards:
        • Search: when the list is long, enter keywords in the Search box at the top to quickly locate a dashboard.
        • Remove: find the target dashboard in the list and click the Delete icon (🗑️) under the Actions column to remove it from the recommendation scope.
        • Learn: click the learning icon (♻️) in the list to relearn the current dashboard.
    • Learn all dashboards: click this button to relearn all dashboards in the list. Relearning everything can take a long time and incurs additional model usage, so use it cautiously.
    • Batch operations: available when dashboards are selected
      • Learn Selected: relearn the selected dashboards.
      • Delete Selected: remove the selected dashboards in batch.

    Notes

    1. The currently selectable dashboards are all dashboards the user has permission to access, regardless of whether they were built on datasets added to the current agent. However, for better recommendation quality, we recommend selecting dashboards built on datasets already added to the current agent.
    2. Dashboard learning is triggered only when dashboards are added or manually relearned. If dashboards are updated after being added, relearn them to avoid inaccurate recommendations.

    Display Effect

    After a user gets a direct answer, the system displays three cards related to the question. Clicking a card jumps directly to the corresponding dashboard card. If a recommendation is inaccurate, users can click Not Interested to provide feedback, and the algorithm will continue optimizing based on that feedback.

    Note
    • If the user question is not related to any dashboard cards associated with the current agent, no recommended cards are shown.
    • This feature is currently not supported on mobile.

    Feature Switch Settings

    On the Basic Information page, click the Feature Switch Settings tab to enter the feature switch settings page. The following sections explain each switch in detail.

    Query Analysis Mode

    Query Analysis Mode determines which answer-processing mode is used when frontend users perform query analysis. The following three modes are supported:

    ModeDescription
    FastFastest response speed, suitable for simple query scenarios.

    After Fast mode is enabled, intelligent visualization is disabled by default. Query results are output only as tables, and numbers are displayed with two decimal places and thousand separators.

    If visualization is needed in Fast mode, enable Fast mode visualization on the Agent Management > Management Center > Feature Switch Settings page.
    StandardBalances response speed and answer quality. This is the default mode.
    High AccuracyBest answer quality, suitable for complex analysis scenarios.

    If High Accuracy mode is selected, the system automatically generates multiple SQL statements for each frontend question and cross-validates them with LLM capability, then executes the SQL with the highest confidence to improve accuracy.

    Opening Recommendations

    After it is enabled, recommended questions are displayed when the user opens a new conversation. Different recommendations can be configured separately for L1 Query and L2 Insight.

    Add Recommended Questions

    Click Add below, then select the question type and fill in the question description in the dialog.

    Note

    Up to 20 recommended questions are supported. When the limit is exceeded, the Add entry is no longer displayed.

    Recommend Question

    Choose Whether the Model Can Generalize the Recommended Questions

    Switch StatusQuestion TypeDescriptionDisplay effect
    DisabledFixed QuestionAfter configuration, the frontend directly displays fixed recommended questions when users start a new conversation. The model does not regenerate or rewrite them.Display fixed recommended questions

    EnabledModel-Generalized QuestionAfter configuration, when the user opens a new conversation, the LLM automatically generates three recommended questions based on the configured examples, user history, user attributes, and dataset structures in the current agent.LLM automatically generates 3 recommended questions

    Guess You May Ask

    Administrators can define recommendation logic for Guess You May Ask. After a user question is completed, the system references the current question and the configured strategy to generate follow-up questions that the user may be interested in.

    Note

    Guess You May Ask supports cases where standard Query returns table or chart results. It does not support:

    • analysis results in Insight mode
    • single-value query results, including single values presented as text

    For example, administrators can define a strategy such as "When users analyze sales-related data, recommend questions related to revenue and gross profit metrics." The system will then generate guiding questions according to that strategy.

    Display effect: when a user asks about monthly sales, the system automatically recommends related questions such as revenue and cost after returning the main result.

    Inject User Attributes into the Q&A Process

    After Inject User Attributes into the Q&A Process is enabled, the system passes the current user's attribute values to the model when the user asks a question. The model then uses those attributes to generate SQL more accurately. For example, if a user asks What is my sales amount?, the system can automatically apply the current user's region or store ownership attributes without requiring the user to specify those filters explicitly.

    Prerequisites

    Before using this feature, make sure User Basic Attributes have already been configured in the BI Management Center. These include built-in attributes such as name, email, and mobile phone number, as well as administrator-defined attributes.

    Configuration and Effect

    • On the Feature Switch Settings page, find and enable Inject User Attributes into the Q&A Process.
    • After it is enabled, the system automatically injects the current logged-in user's attribute information into the Q&A workflow.
    • When generating SQL, the LLM automatically applies the related filter conditions based on user attributes, improving personalization and accuracy.
    • If user attributes are not configured or attribute values are empty, this feature does not take effect and Q&A continues using the standard logic.

    Notes

    • User attribute configuration and management must be completed in the BI platform under Management Center > User Management > User and Management Center > User Management > User Basic Attribute Management.
    • This feature depends on the BI platform's user attribute system. If the required user attributes are not configured in BI Management Center, the switch has no effect after being enabled.
    • Before using this feature, verify that target user groups have correct attribute values maintained.

    Automatic Number Units

    After this feature is enabled, the system automatically chooses units such as ten-thousand and hundred-million based on the numeric value. If scaling has already been calculated in the dataset, do not enable this feature.

    Note

    If scaling has already been handled in the dataset, do not enable this feature, or the displayed unit may be converted twice.

    Example: suppose the dataset already uses ten-thousand as the scaling unit, and the original value 200000000 yuan is displayed as 20000 ten-thousand yuan after calculation. If Automatic Numeric Scaling is enabled again, the system will rescale 20000 and display it as 2 ten-thousand ten-thousand yuan, resulting in incorrect output.

    Table Relation Settings

    After this feature is enabled, table relationships between multiple data tables can be defined and configured through a graphical interface to support knowledge for multi-table analysis. See Table Relation.

    Personalized Memory

    After this feature is enabled, the system automatically extracts knowledge mentioned by users during conversations and applies that memory in future Q&A across all agents for the same user. For detail, see Personalized Memory

    Insight

    After this feature is enabled, users can select the current agent on the Insight Agent page for insight analysis. The LLM uses knowledge base information and tools flexibly to perform data queries and analysis, then generates insight results.

    • Supports Search Web. After it is enabled, the system is allowed to access the internet and combine the latest public information into answers.

    • Supports Planning Mode. After it is enabled, the Insight Agent does not directly output a report at first. Instead, it confirms the analysis approach with the user before generating the report.

      664

    • Supports File Upload. After it is enabled, files can be uploaded as analysis input in Insight Analysis. See Upload a File for Analysis.