From 1c79595f20af0c854a5c32d1266e4adfd8185c59 Mon Sep 17 00:00:00 2001 From: ShashiSubramanya Date: Thu, 12 Feb 2026 07:32:23 +0530 Subject: [PATCH 1/8] minor edits to table format --- modules/ROOT/pages/spotter-apis.adoc | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/modules/ROOT/pages/spotter-apis.adoc b/modules/ROOT/pages/spotter-apis.adoc index 991583d84..cfcd7b5a2 100644 --- a/modules/ROOT/pages/spotter-apis.adoc +++ b/modules/ROOT/pages/spotter-apis.adoc @@ -990,7 +990,7 @@ The following example shows the response text contents for the `answer` message The session ID and generation number serve as the data context for the Answer. You can use this information to create a new conversation session using `/api/rest/2.0/ai/agent/conversation/create`, or download the answer via the `/api/rest/2.0/report/answer` API endpoint. [#process_results] -== Process results generated from Spotter APIs +== Processing results generated from Spotter APIs To export or download the Answer data generated by the Spotter APIs, use the xref:data-report-v2-api.adoc#exportSpotterData[Answer report] API. [NOTE] @@ -1009,7 +1009,7 @@ The `POST /api/rest/2.0/ai/data-source-suggestions` API provides relevant data s [width="100%" cols="2,4"] [options='header'] -|===== +|==== |Parameter| Description |`metadata_context` a| Required. Specify one of the following attributes to set the metadata context: @@ -1029,6 +1029,7 @@ __Optional__ | __Integer__. Sets a limit on the number of sub-questions to retur __Optional__| __Boolean__. When set to `true`, disables cache and forces fresh computation. |`ai_context` + __Optional__. a| Additional context to guide the response. Define the following attributes as needed: +|==== ==== Example request From 92ef623ed13c10c29334f50d3f1284868d831c35 Mon Sep 17 00:00:00 2001 From: ShashiSubramanya Date: Fri, 13 Feb 2026 08:05:31 +0530 Subject: [PATCH 2/8] auto mode flag update --- modules/ROOT/pages/api-changelog.adoc | 2 +- modules/ROOT/pages/embed-ai-analytics.adoc | 2 +- modules/ROOT/pages/embed-spotter.adoc | 4 ++-- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/modules/ROOT/pages/api-changelog.adoc b/modules/ROOT/pages/api-changelog.adoc index 9792b332c..29fb0471f 100644 --- a/modules/ROOT/pages/api-changelog.adoc +++ b/modules/ROOT/pages/api-changelog.adoc @@ -17,7 +17,7 @@ This changelog lists only the changes introduced in the Visual Embed SDK. For in You can now embed the Spotter 3 experience in your application and use features such as Auto mode for automatic data model selection, Chat history, and a new chat prompt interface. * To enable the new chat prompt interface, set `updatedSpotterChatPrompt` to `true`. -* To use Auto mode, set the `worksheetId` to `_spotter_data_source_discovery_id`. +* To use Auto mode, set the `worksheetId` to `auto_mode`. * To enable Chat history, set `enablePastConversationsSidebar` to `true`. For more information, see xref:embed-spotter.adoc[Embedding Spotter] and xref:embed-ai-analytics.adoc#_feature_status_and_availability_in_embed_mode[Features available with Spotter 3 experience]. diff --git a/modules/ROOT/pages/embed-ai-analytics.adoc b/modules/ROOT/pages/embed-ai-analytics.adoc index 3454144ac..c2abb742c 100644 --- a/modules/ROOT/pages/embed-ai-analytics.adoc +++ b/modules/ROOT/pages/embed-ai-analytics.adoc @@ -245,7 +245,7 @@ Automatic data source discovery and model selection by Spotter. **Embed SDK component**: Use `SpotterEmbed`. + -**Default state in embed**: Disabled by default. To enable this feature, set the `worksheetId` attribute to `_spotter_data_source_discovery_id` in the SDK. When the Auto mode is enabled, the *Preview data* option in the conversation panel is hidden. +**Default state in embed**: Disabled by default. To enable this feature, set the `worksheetId` attribute to `auto_mode` in the SDK. When the Auto mode is enabled, the *Preview data* option in the conversation panel is hidden. |link:https://docs.thoughtspot.com/cloud/latest/spotter-conversation-history[Chat history, window=_blank] + diff --git a/modules/ROOT/pages/embed-spotter.adoc b/modules/ROOT/pages/embed-spotter.adoc index 746388e69..4a17680a9 100644 --- a/modules/ROOT/pages/embed-spotter.adoc +++ b/modules/ROOT/pages/embed-spotter.adoc @@ -83,7 +83,7 @@ const spotterEmbed = new SpotterEmbed(document.getElementById('ts-embed'), { width: '100%', height: '100%', }, - worksheetId: '<%=datasourceGUID%>', // ID of the data source object. To use the Auto mode, set the ID to '_spotter_data_source_discovery_id', + worksheetId: '<%=datasourceGUID%>', // ID of the data source object. To use the Auto mode, set the ID to 'auto_mode', //... other attributes }); ---- @@ -457,7 +457,7 @@ if (container) { height: '100%', // Set the height of the embedded frame width: '100%', // Set the width of the embedded frame }, - worksheetId: 'your-worksheet-id', // ID of the data source object to query data from. For automatic model discovery and selection (Auto mode), specify '_spotter_data_source_discovery_id' + worksheetId: 'your-worksheet-id', // ID of the data source object to query data from. For automatic model discovery and selection (Auto mode), specify 'auto_mode' updatedSpotterChatPrompt: true, // Enable new chat interface enablePastConversationsSidebar: true, // Enable chat history //... other configuration attributes From e8d95b28dd083c5fa49b001e458d35471d742502 Mon Sep 17 00:00:00 2001 From: ShashiSubramanya Date: Fri, 13 Feb 2026 18:07:50 +0530 Subject: [PATCH 3/8] changelog update --- modules/ROOT/pages/api-changelog.adoc | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/modules/ROOT/pages/api-changelog.adoc b/modules/ROOT/pages/api-changelog.adoc index 29fb0471f..5840406b4 100644 --- a/modules/ROOT/pages/api-changelog.adoc +++ b/modules/ROOT/pages/api-changelog.adoc @@ -28,6 +28,11 @@ Events:: * `HostEvent.AddToCoaching` to trigger the *Add to coaching* action in a Spotter conversation session. * `HostEvent.StartNewSpotterConversation` to trigger the action to start a new chat session with Spotter. +[NOTE] +==== +On Spotter embed deployments running version 26.2.0.cl or later, the *Add to Coaching* feature is enabled by default. To disable or hide the **Add to Coaching** button, use the xref:Action.adoc#_inconversationtraining[InConversationTraining] action ID. +==== + |[tag greenBackground]#NEW FEATURE# a| **Liveboard experience enhancements** + Styling and grouping:: From a3e2d9d7a72c78e9db43d9e335582899a2565fff Mon Sep 17 00:00:00 2001 From: Rani Gangwar Date: Tue, 17 Feb 2026 20:42:28 +0530 Subject: [PATCH 4/8] edits to flag --- modules/ROOT/pages/embed-pinboard.adoc | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/modules/ROOT/pages/embed-pinboard.adoc b/modules/ROOT/pages/embed-pinboard.adoc index 455283606..452730976 100644 --- a/modules/ROOT/pages/embed-pinboard.adoc +++ b/modules/ROOT/pages/embed-pinboard.adoc @@ -503,7 +503,8 @@ liveboardEmbed.trigger(HostEvent.UpdateFilters, { === Liveboard grouping and styling [earlyAccess eaBackground]#Early Access# You can now create a visual group of Answers and note tiles together in the Liveboard. You can select multiple Answers and notes in the Liveboard editor. You can also style parts of the Liveboard, groups and Answers with the new styling panel. -To enable this feature, set `isLiveboardStylingAndGroupingEnabled` to `true`. It is important to note the following changes which happen in the Liveboard UI and layout when this feature is active. +To enable this feature, set `isLiveboardMasterpiecesEnabled` to `true`. +It is important to note the following changes which happen in the Liveboard UI and layout when this feature is active. * All tiles on the Liveboard will now have a default border and an increased border-radius, resulting in more pronounced curved corners. This is part of the broader visualization tile customization options done to enhance the visual appearance of charts and tables. * For Note tiles, the default scrollbar is now hidden for long content. Users must scroll within the tile area itself, and if the tile is not sized appropriately for its content, it may appear clipped due to the new container styles. This change emphasizes the importance of properly sizing Note tiles to avoid content being visually cut off. @@ -515,7 +516,7 @@ To enable this feature, set `isLiveboardStylingAndGroupingEnabled` to `true`. It image::./images/lb-grp-styling-error.png[Liveboard with groups styling error] -- + -To embed a Liveboard that uses Groups, you must set `isLiveboardStylingAndGroupingEnabled` to `true` in your embedding configuration. This is required for compatibility with the new grouping and styling features; otherwise, the embedded Liveboard will not render correctly. +To embed a Liveboard that uses Groups, you must set `isLiveboardMasterpiecesEnabled` to `true` in your embedding configuration. This is required for compatibility with the new grouping and styling features; otherwise, the embedded Liveboard will not render correctly. For more information, see link:https://docs.thoughtspot.com/cloud/latest/liveboard-grouping-styling[Liveboard grouping and styling, window=_blank]. From e4e1ed8036d36351857b7f10635d8d0582fe2726 Mon Sep 17 00:00:00 2001 From: ShashiSubramanya Date: Wed, 18 Feb 2026 15:37:59 +0530 Subject: [PATCH 5/8] url ref removed --- modules/ROOT/pages/api-intercept.adoc | 19 +++---------------- 1 file changed, 3 insertions(+), 16 deletions(-) diff --git a/modules/ROOT/pages/api-intercept.adoc b/modules/ROOT/pages/api-intercept.adoc index a3ba7e5e5..c10332b87 100644 --- a/modules/ROOT/pages/api-intercept.adoc +++ b/modules/ROOT/pages/api-intercept.adoc @@ -11,7 +11,7 @@ Developers can intercept data fetch and other API requests initiated by the embe * Intercept data fetch requests: + To enable interception of search execution requests by search embed or full application embed, use the `isOnBeforeGetVizDataInterceptEnabled` attribute. When enabled, you can implement custom logic using the `OnBeforeGetVizDataIntercept` embed event, allow or block search requests, and show custom messages to users. -* Intercept a specific API call or all requests: + +* Intercept a specific API call or all API requests: + If you want to intercept other API calls initiated by the embedded application, define the URLs that you want to intercept in the `interceptUrls` attribute and handle interception using the `ApiIntercept` embed event. Developers can use these interception features for: @@ -80,21 +80,6 @@ embed.on(EmbedEvent.OnBeforeGetVizDataIntercept, The API intercept feature lets you intercept API calls made by the embedded application, modify or block requests, and provide custom responses before they are sent to the backend. -//// -=== Enable API interception - -To enable this feature on your embed, you must set the `enableApiIntercept` flag to `true` in the SDK. - -[source,JavaScript] ----- -const embed = new LiveboardEmbed('#embed', { - //...viewConfig, - enableApiIntercept: true, - //... -}); ----- -//// - To intercept API requests from specific URLs, define the URLs in the `interceptUrls` array: Valid values for `interceptUrls` are: @@ -103,6 +88,7 @@ Valid values for `interceptUrls` are: ** `AnswerData` - Allows intercepting APIs that fetch data for a search query or visualization. + ** `LiveboardData` - Allows intercepting APIs requesting data for the embedded Liveboard. +//// You can also set a specific URL that you want to intercept by specifying the array in the following format: `interceptUrls: [Type.AnswerData, '{URL-to-intercept}']` @@ -111,6 +97,7 @@ You can also set a specific URL that you want to intercept by specifying the arr ==== You must specify at least one API type or URL in the array for interception to be effective. If `interceptUrls` is set as an empty array, no URLs will be intercepted. ==== +//// === Intercept timeout threshold To set a threshold for the interception handling, configure the `interceptTimeout` value in milliseconds. The default value is 30000. If the interception is not handled within the configured threshold, the API returns an error. From c5e77a13b578f9fd7278900ec654d9a2f4fb98e5 Mon Sep 17 00:00:00 2001 From: ShashiSubramanya Date: Wed, 18 Feb 2026 15:53:54 +0530 Subject: [PATCH 6/8] api intercept updates --- modules/ROOT/pages/api-intercept.adoc | 17 ++++++++--------- 1 file changed, 8 insertions(+), 9 deletions(-) diff --git a/modules/ROOT/pages/api-intercept.adoc b/modules/ROOT/pages/api-intercept.adoc index c10332b87..85153b063 100644 --- a/modules/ROOT/pages/api-intercept.adoc +++ b/modules/ROOT/pages/api-intercept.adoc @@ -12,7 +12,7 @@ Developers can intercept data fetch and other API requests initiated by the embe To enable interception of search execution requests by search embed or full application embed, use the `isOnBeforeGetVizDataInterceptEnabled` attribute. When enabled, you can implement custom logic using the `OnBeforeGetVizDataIntercept` embed event, allow or block search requests, and show custom messages to users. * Intercept a specific API call or all API requests: + -If you want to intercept other API calls initiated by the embedded application, define the URLs that you want to intercept in the `interceptUrls` attribute and handle interception using the `ApiIntercept` embed event. +If you want to intercept other API calls initiated by the embedded application, define the requests that you want to intercept in the `interceptUrls` attribute and handle interception using the `ApiIntercept` embed event. Developers can use these interception features for: @@ -34,7 +34,7 @@ const embed = new LiveboardEmbed('#embed', { }); ---- -When enabled, you can intercept and control search execution and data fetch requests, and implement a custom logic to trigger a response when the `EmbedEvent.OnBeforeGetVizDataIntercept` event is emitted. +When enabled, you can intercept and control search execution and data fetch requests, and implement custom logic to trigger a response when the `EmbedEvent.OnBeforeGetVizDataIntercept` event is emitted. The following example blocks the search request and returns a custom error message. @@ -76,28 +76,27 @@ embed.on(EmbedEvent.OnBeforeGetVizDataIntercept, }) ---- -== Intercept specific URLs or all API calls +== Intercept specific requests or all API calls The API intercept feature lets you intercept API calls made by the embedded application, modify or block requests, and provide custom responses before they are sent to the backend. -To intercept API requests from specific URLs, define the URLs in the `interceptUrls` array: - -Valid values for `interceptUrls` are: +To intercept API requests from specific URLs, specify one of the following values in the `interceptUrls` array: ** `ALL` - Allows intercepting all API requests + ** `AnswerData` - Allows intercepting APIs that fetch data for a search query or visualization. + -** `LiveboardData` - Allows intercepting APIs requesting data for the embedded Liveboard. +** `LiveboardData` - Allows intercepting APIs requesting data for an embedded Liveboard. //// You can also set a specific URL that you want to intercept by specifying the array in the following format: `interceptUrls: [Type.AnswerData, '{URL-to-intercept}']` +//// [NOTE] ==== -You must specify at least one API type or URL in the array for interception to be effective. If `interceptUrls` is set as an empty array, no URLs will be intercepted. +You must specify at least one API type in the array for interception to be effective. If `interceptUrls` is set as an empty array, no API requests will be intercepted. ==== -//// + === Intercept timeout threshold To set a threshold for the interception handling, configure the `interceptTimeout` value in milliseconds. The default value is 30000. If the interception is not handled within the configured threshold, the API returns an error. From 938d69322473397b703c704bbc0c0470c9671e85 Mon Sep 17 00:00:00 2001 From: Rani Gangwar Date: Thu, 19 Feb 2026 09:31:06 +0530 Subject: [PATCH 7/8] deprecation for Sage privilege --- modules/ROOT/pages/deprecated-features.adoc | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/modules/ROOT/pages/deprecated-features.adoc b/modules/ROOT/pages/deprecated-features.adoc index b64e3d751..864127933 100644 --- a/modules/ROOT/pages/deprecated-features.adoc +++ b/modules/ROOT/pages/deprecated-features.adoc @@ -14,6 +14,7 @@ As ThoughtSpot applications evolve, some existing features will be deprecated an [options='header'] |===== |Feature|Impacted interface and release versions|Deprecation date |End of Support / removal from the product +a|xref:deprecated-features.adoc#SagePrivilegeDeprecation[`PREVIEW_THOUGHTSPOT_SAGE` privilege deprecation] a|ThoughtSpot Cloud 26.3.0.cl and later | March 2026 | May 2026 a|xref:deprecated-features.adoc#_answer_data_panel_classic_experience_deprecation[Answer Data panel classic experience] |ThoughtSpot Cloud 26.4.0.cl and later | April 2026 | August 2026 a|xref:deprecated-features.adoc#_worksheet_deprecation_and_removal[Worksheets] a| ThoughtSpot Cloud 10.4.0.cl and later |November 2024 | September 2025 @@ -80,6 +81,12 @@ a|xref:deprecated-features.adoc#_deprecated_parameter_in_rest_api_v2_0_authentic |||| |===== +[#SagePrivilegeDeprecation] +== `PREVIEW_THOUGHTSPOT_SAGE` privilege deprecation +The `PREVIEW_THOUGHTSPOT_SAGE` privilege is renamed to `CAN_USE_SPOTTER` with the ThoughtSpot 26.3.0.cl release version. The API calls will continue to support both these privileges until ThoughtSpot 26.5.0.cl release version, after which the `PREVIEW_THOUGHTSPOT_SAGE` privilege will be removed. +For ThoughtSpot instances which have enabled RBAC before the 26.3.0.cl release, there will be no automatic changes to the roles created using the `PREVIEW_THOUGHTSPOT_SAGE` privilege. However, the underlying privilege associated with such roles will be appropriately renamed to `CAN_USE_SPOTTER`. The admins for these clusters will be notified to rename the role in accordance with the newer privilege name. + + == Answer Data panel classic experience deprecation The classic Data panel experience in Search and Answer pages will be deprecated in ThoughtSpot 26.4.0.cl release version. The new data panel experience, which provides a more intuitive layout with improved organization of data elements and features such as query sets and custom groups, will be the default data panel experience on all ThoughtSpot Embedded instances using Visual Embed SDK v1.41.1 or later. From 1226c8424b138ca584426299bb1dbda1fc97a7d0 Mon Sep 17 00:00:00 2001 From: Rani Gangwar Date: Thu, 19 Feb 2026 09:46:33 +0530 Subject: [PATCH 8/8] reverted commit due to merge conflicts --- modules/ROOT/pages/deprecated-features.adoc | 7 ------- 1 file changed, 7 deletions(-) diff --git a/modules/ROOT/pages/deprecated-features.adoc b/modules/ROOT/pages/deprecated-features.adoc index 864127933..b64e3d751 100644 --- a/modules/ROOT/pages/deprecated-features.adoc +++ b/modules/ROOT/pages/deprecated-features.adoc @@ -14,7 +14,6 @@ As ThoughtSpot applications evolve, some existing features will be deprecated an [options='header'] |===== |Feature|Impacted interface and release versions|Deprecation date |End of Support / removal from the product -a|xref:deprecated-features.adoc#SagePrivilegeDeprecation[`PREVIEW_THOUGHTSPOT_SAGE` privilege deprecation] a|ThoughtSpot Cloud 26.3.0.cl and later | March 2026 | May 2026 a|xref:deprecated-features.adoc#_answer_data_panel_classic_experience_deprecation[Answer Data panel classic experience] |ThoughtSpot Cloud 26.4.0.cl and later | April 2026 | August 2026 a|xref:deprecated-features.adoc#_worksheet_deprecation_and_removal[Worksheets] a| ThoughtSpot Cloud 10.4.0.cl and later |November 2024 | September 2025 @@ -81,12 +80,6 @@ a|xref:deprecated-features.adoc#_deprecated_parameter_in_rest_api_v2_0_authentic |||| |===== -[#SagePrivilegeDeprecation] -== `PREVIEW_THOUGHTSPOT_SAGE` privilege deprecation -The `PREVIEW_THOUGHTSPOT_SAGE` privilege is renamed to `CAN_USE_SPOTTER` with the ThoughtSpot 26.3.0.cl release version. The API calls will continue to support both these privileges until ThoughtSpot 26.5.0.cl release version, after which the `PREVIEW_THOUGHTSPOT_SAGE` privilege will be removed. -For ThoughtSpot instances which have enabled RBAC before the 26.3.0.cl release, there will be no automatic changes to the roles created using the `PREVIEW_THOUGHTSPOT_SAGE` privilege. However, the underlying privilege associated with such roles will be appropriately renamed to `CAN_USE_SPOTTER`. The admins for these clusters will be notified to rename the role in accordance with the newer privilege name. - - == Answer Data panel classic experience deprecation The classic Data panel experience in Search and Answer pages will be deprecated in ThoughtSpot 26.4.0.cl release version. The new data panel experience, which provides a more intuitive layout with improved organization of data elements and features such as query sets and custom groups, will be the default data panel experience on all ThoughtSpot Embedded instances using Visual Embed SDK v1.41.1 or later.