26.4.0.cl docs publication

modules/ROOT/pages/abac-migration-from-jwt-beta.adoc

@@ -175,7 +175,7 @@ Verify that variable values are correctly assigned to users using one of the fol
 * Send a `POST` request to the `/api/rest/2.0/users/search` with user details, and explore the `variable_values` section of the response payload.
 * Send a `POST` request to the `/api/rest/2.0/template/variables/search` API endpoint with variable details. In the request body, specify the `response_content` as `METADATA_AND_VALUES`, and explore the variable values for each user in the response payload.
 
-If you want to update the values of variables, use either `/api/rest/2.0/template/variables/update-values` or `/api/rest/2.0/auth/token/custom` API endpoint.
+If you want to update the values of variables, use either `/api/rest/2.0/template/variables/{identifier}/update-values` or `/api/rest/2.0/auth/token/custom` API endpoint.
 
 == Review the configuration
 Before you begin testing, your setup should have the following JWT ABAC configuration:

modules/ROOT/pages/abac-migration-from-jwt-ga.adoc

@@ -148,7 +148,7 @@ Users with administration and *Can Administer and Bypass RLS* privileges are exe
 +
 [NOTE]
 ====
-To update variable values for a user, use the `/api/rest/2.0/auth/token/custom` or `/api/rest/2.0/template/variables/update-values` API endpoint.
+To update variable values for a user, use the `/api/rest/2.0/auth/token/custom` or `/api/rest/2.0/template/variables/{identifier}/update-values` API endpoint.
 ====
 
 == Expected setup before the testing phase

modules/ROOT/pages/abac_rls-variables.adoc

@@ -162,7 +162,7 @@ The following rule restricts access to rows where the `date_column` is within th
 
 To set or update variable values for a user, use the `POST /api/rest/2.0/auth/token/custom` endpoint when logging in the user.
 
-You can also use the `/api/rest/2.0/template/variables/update-values` endpoint for bulk operations or targeted resets.
+You can also use the `/api/rest/2.0/template/variables/{identifier}/update-values` endpoint for bulk operations or targeted resets.
 
 The variable attributes defined in the token request take effect only if they are referenced in an RLS rule. If the variables are not used in any formula or RLS rule, they have no impact on data access. Before generating the request with variable attributes, ensure that the xref:abac_rls-variables.adoc#_add_or_update_rls_rules_with_variable_references[variables are added to the RLS rules] for the table.
 
@@ -263,7 +263,7 @@ If you don't want to append or replace any attribute values, do not pass any det
 === Resetting a user or a variable
 Passing an empty array along with a formula variable name in the token request *does not reset the attribute values* for that formula variable for that user.
 
-To change formula variable attributes of a user, especially to set entitlements to an empty set, use the `/api/rest/2.0/template/variables/update-values` API endpoint.
+To change formula variable attributes of a user, especially to set entitlements to an empty set, use the `/api/rest/2.0/template/variables/{identifier}/update-values` API endpoint.
 
 [WARNING]
 ====

modules/ROOT/pages/api-changelog.adoc

@@ -97,6 +97,7 @@ If the current period inclusion in rolling date filters feature is enabled on yo
 To disable this feature, use the `isThisPeriodInDateFiltersEnabled` setting. To hide, show, or disable this option in the embed view, use the action ID, `Action.IncludeCurrentPeriod`.
 |====
 
+
 == Version 1.46.x, March 2026
 
 [width="100%" cols="1,4"]
@@ -265,7 +266,7 @@ The `HostEvent.UpdateParameters` event now supports configuring the `isVisibleTo
 
 [width="100%" cols="1,4"]
 |====
-|[tag greenBackground]#NEW FEATURE# a|*Runtime overrides in Spotter embed* 
+|[tag greenBackground]#NEW FEATURE# a|*Runtime overrides in Spotter embed*
 
 The Visual Embed SDK now supports runtime overrides in Spotter embed.
 

modules/ROOT/pages/collections.adoc

@@ -0,0 +1,317 @@
+= Collections [beta betaBackground]^Beta^
+:toc: true
+:toclevels: 1
+:page-title: Collections
+:page-pageid: collections
+:page-description: group different ThoughtSpot objects into Collections to manage them more easily.
+
+
+ThoughtSpot now provides REST APIs that enable developers to organize different ThoughtSpot objects into an organizational container called *Collections*. These objects can be Liveboards, Answers, data models, tables, and even other Collections.
+Collections provide a powerful way to manage your data assets, making discovery and collaboration easier, while ensuring the integrity of embedded workflows.
+
+[NOTE]
+====
+The Collections APIs are in Beta and disabled by default on ThoughtSpot instances. To enable these APIs on your instance, contact ThoughtSpot Support.
+====
+
+== Before you begin
+
+* For REST API v2 operations, the Org context is determined based on the authentication token used in your API requests. Ensure you log in to the appropriate Org context from which you want to send API requests.
+* When enabled on a ThoughtSpot instance, Collections can be created by any user, and need no special user privileges.
+
+
+== Create a Collection
+To create a new Collection, send a `POST` request to the  `POST /api/rest/2.0/collections/create` API endpoint, with the following parameters in the request body.
+
+=== Request parameters
+In your `POST` request body, include the following parameters:
+
+[width="100%" cols="1,4"]
+[options='header']
+|=====
+|Parameter|Description
+
+|`name` a|__String__. Required. Specify a name for the Collection.
+|`description` a|__String__. Optional. A short description for the Collection.
+|`metadata` a|__Array__. Optional. The details for the metadata objects to be added to the Collection.
+
+* `type` +
+Metadata type. Select one of the following values:
+** `LIVEBOARD`
+** `ANSWER`
+** `LOGICAL_TABLE`
+** `COLLECTION`
++
+To create nested collections, assign the `COLLECTION` metadata to a Collection.
+
+* `identifiers` +
+List of unique IDs or names of metadata objects.
+|=====
+
+==== Example request
+[source,CURL]
+----
+curl -X POST \
+  --url 'https://{ThoughtSpot-Host}/api/rest/2.0/collections/create'  \
+  -H 'Accept: application/json' \
+  -H 'Content-Type: application/json' \
+  -H 'Authorization: Bearer {AUTH_TOKEN}' \
+  --data-raw '{
+  "name": "Demo Collection",
+  "metadata": [
+    {
+      "type": "LIVEBOARD",
+      "identifiers": [
+        "Retail sales (Sample)",
+        "fe307a35-5242-445f-b3cb-b84cd1fc339c"
+      ]
+    },
+    {
+      "type": "COLLECTION",
+      "identifiers": [
+        "Collection A"
+      ]
+    }
+  ],
+  "description": "For testing"
+}'
+
+----
+
+==== API response
+
+If the API request is successful, a Collection with the given metadata objects will be created.
+
+== Search for a Collection
+To get a list of Collections, send a  `POST` request to the `POST /api/rest/2.0/collections/search` API endpoint.
+
+If no parameters are specified, the API returns the first 10 collections (or fewer, depending on the total number available).
+
+=== Request parameters
+In your `POST` request body, include the following parameters:
+
+[width="100%" cols="1,4"]
+[options='header']
+|=====
+|Parameter|Description
+
+|`name_pattern` a|__String__. Optional. Specify any case agnostic pattern to match the name of a Collection. Use `%` to perform a wildcard search by name.
+|`record_offset` a|__Number__. Optional. The index of the first record to be included. Default value is 0.
+|`record_size` a|__Number__. Optional. The total number of records to be searched. Default value is 10. Set to -1 to search across all available collections.
+|`collection_identifiers` a|__Array__. Optional. GUID of the Collection(s) to be searched. `name_pattern` takes precedence over the `collection_identifiers`.
+|`created_by_user_identifiers` a|__Array__. Optional. Searches for Collections by the name of the author.
+|`include_metadata` a|__Boolean__. Optional. When set to `true`, includes the metadata objects within each Collection in the response.
+|`sort_options` a|__Array__. Optional. To sort the search results, specify the field to apply the sort on `field_name`, and the sort order `order`.
+|=====
+
+==== Example request
+[source,CURL]
+----
+curl -X POST \
+  --url 'https://{ThoughtSpot-Host}/api/rest/2.0/collections/search'  \
+  -H 'Accept: application/json' \
+  -H 'Content-Type: application/json' \
+  -H 'Authorization: Bearer {AUTH_TOKEN}' \
+  --data-raw '{
+  "record_offset": 2,
+  "record_size": 15,
+  "include_metadata": false,
+  "name_pattern": "%",
+  "sort_options": {
+    "field_name": "NAME",
+    "order": "ASC"
+  }
+}'
+----
+
+==== API response
+
+If the API request is successful, it will return a list of Collection(s) matching the search criteria.
+
+== Update a Collection
+To update an existing Collection, send a  `POST` request to the `POST /api/rest/2.0/collections/{collection_identifier}/update` API endpoint.
+
+=== Request parameters
+In your `POST` request body, include the following parameters:
+
+[width="100%" cols="1,4"]
+[options='header']
+|=====
+|Parameter|Description
+
+|`collection_identifier` a| Required. GUID of the Collection to be updated. `collection_identifier` is passed as a parameter in the API request.
+|`name` a|__String__. Optional. New name for the Collection.
+|`description` a|__String__. Optional. Updated or a newly added description for the Collection.
+|`metadata` a|__Array__. Required. The details for the metadata objects to be added, removed, or replaced in the Collection.
+
+* `type`
+* `identifiers`
+|`operation` a|__Enum__. Required. Specify the nature of the update. Select one of the following values:
+
+* ADD: Adds the specified metadata objects to the existing Collection without removing the current objects.
+* REMOVE: Removes only the specified metadata objects from the Collection.
+* REPLACE. __Default__: This replaces all existing objects in the Collection with the objects specified in this replace request.
+|=====
+
+==== Example request
+[source,CURL]
+----
+curl -X POST \
+  --url 'https://{ThoughtSpot-Host}/api/rest/2.0/collections/0e5fd958-cb2b-43f0-b67f-13ac5c805bad/update'  \
+  -H 'Accept: application/json' \
+  -H 'Content-Type: application/json' \
+  -H 'Authorization: Bearer {AUTH_TOKEN}' \
+  --data-raw '{
+  "operation": "ADD",
+  "metadata": [
+    {
+      "type": "LIVEBOARD",
+      "identifiers": [
+        "6fee1adb-1c50-4c15-8d49-4fe0503d0b34"
+      ]
+    }
+  ]
+}'
+----
+==== API response
+
+If the API request is successful, the object specified in the API request is added to the Collection.
+
+==== Example request
+[source,CURL]
+----
+curl -X POST \
+  --url 'https://{ThoughtSpot-Host}/api/rest/2.0/collections/0e5fd958-cb2b-43f0-b67f-13ac5c805bad/update'  \
+  -H 'Accept: application/json' \
+  -H 'Content-Type: application/json' \
+  -H 'Authorization: Bearer {AUTH_TOKEN}' \
+  --data-raw '{
+  "operation": "REMOVE",
+  "metadata": [
+    {
+      "type": "LIVEBOARD",
+      "identifiers": [
+        "6fee1adb-1c50-4c15-8d49-4fe0503d0b34"
+      ]
+    }
+  ]
+}'
+----
+
+==== API response
+
+If the API request is successful, the object specified in the API request is removed from the Collection.
+
+==== Example request
+[source,CURL]
+----
+curl -X POST \
+  --url 'https://{ThoughtSpot-Host}/api/rest/2.0/collections/0e5fd958-cb2b-43f0-b67f-13ac5c805bad/update'  \
+  -H 'Accept: application/json' \
+  -H 'Content-Type: application/json' \
+  -H 'Authorization: Bearer {AUTH_TOKEN}' \
+  --data-raw '{
+  "operation": "REPLACE",
+  "metadata": [
+    {
+      "type": "LIVEBOARD",
+      "identifiers": [
+        "6fee1adb-1c50-4c15-8d49-4fe0503d0b34",
+        "87328d32-2bf0-4fc4-ac51-a738712d7e79"
+      ]
+    },
+    {
+      "type": "COLLECTION",
+      "identifiers": [
+        "6d85c77c-4822-42ba-8074-6306a90ba8e1"
+      ]
+    }
+  ]
+}'
+----
+
+
+==== API response
+
+If the API request is successful, the objects in the Collection are replaced with the objects in this API request.
+
+== Delete a Collection
+To remove an existing Collection, send a `POST` request to the `POST /api/rest/2.0/collections/delete` API endpoint.
+
+=== Request parameters
+In your `POST` request body, include the following parameters:
+
+[width="100%" cols="1,4"]
+[options='header']
+|=====
+|Parameter|Description
+
+|`collection_identifiers` a|__String__. Required. GUID of the Collection to be deleted.
+|`delete_children` a|__String__. Optional. Set to `true` to delete child objects in the Collection where the user has permission. Any objects without delete access will be ignored.
+|`dry_run` a|__String__. Optional. Set to true to preview the deletion process without removing any objects. The response lists the items that would be deleted, so you can review them before proceeding with actual deletion.
+|=====
+
+==== Example request
+To review your deletion request without actually deleting the Collection and its objects, set `dry_run` to `true` and `delete_children` to `true`.
+
+[source,CURL]
+----
+curl -X POST \
+  --url 'https://{ThoughtSpot-Host}/api/rest/2.0/collections/delete'  \
+  -H 'Accept: application/json' \
+  -H 'Content-Type: application/json' \
+  -H 'Authorization: Bearer {AUTH_TOKEN}' \
+  --data-raw '{
+  "collection_identifiers": [
+    "6996b262-8733-4af6-8f8e-8d7faefb5be0"
+  ],
+  "delete_children": true,
+  "dry_run": true
+}'
+----
+
+==== API response
+
+If the API request is successful, it gives you a preview of the deletion operation without actually deleting anything.
+
+* `metadata_deleted`: List of metadata objects that will be deleted
+* `metadata_skipped`: List of metadata objects that will not be deleted for lack of permissions or other constraints
+
+[source,JSON]
+----
+{"metadata_deleted":[{"type":"COLLECTION","identifiers":[{"id":"6996b262-8733-4af6-8f8e-8d7faefb5be0","name":"Docs Collection"}]},{"type":"LIVEBOARD","identifiers":[{"id":"278d2313-ac3a-44bb-b842-a4c9dff84e68","name":"Demo-lb"},{"id":"1bcdb2c1-e960-4f6b-bbf9-64f3e0cd33b9","name":"Demo-lb1"}]}],"metadata_skipped":[]}
+----
+
+==== Example request
+To delete the Collection and the objects within it, set `dry_run` to `false` and `delete_children` to `true`.
+
+[source,CURL]
+----
+curl -X POST \
+  --url 'https://{ThoughtSpot-Host}/api/rest/2.0/collections/delete'  \
+  -H 'Accept: application/json' \
+  -H 'Content-Type: application/json' \
+  -H 'Authorization: Bearer {AUTH_TOKEN}' \
+  --data-raw '{
+  "collection_identifiers": [
+    "6996b262-8733-4af6-8f8e-8d7faefb5be0"
+  ],
+  "delete_children": true,
+  "dry_run": false
+}'
+----
+
+==== API response
+If the API request is successful, it deletes the Collection and all objects within it for which you have delete permission.
+
+[source,JSON]
+----
+{"metadata_deleted":[{"type":"COLLECTION","identifiers":[{"id":"6996b262-8733-4af6-8f8e-8d7faefb5be0","name":"Docs Collection"}]},{"type":"LIVEBOARD","identifiers":[{"id":"278d2313-ac3a-44bb-b842-a4c9dff84e68","name":"Demo-lb"},{"id":"1bcdb2c1-e960-4f6b-bbf9-64f3e0cd33b9","name":"Demo-lb1"}]}],"metadata_skipped":[]}
+----
+
+== Additional references
+
+
+* For information about creating and managing Collections via ThoughtSpot UI, see link:https://docs.thoughtspot.com/cloud/latest/collections[Collections in ThoughtSpot, window=_blank]
+
+