Update from SAP DITA CMS (squashed):

ditaccms-bot · ditaccms-bot · commit 222f7c1fd317 · 2026-06-03T15:31:38.000Z
commit 3093f3780c387c09a47c3df9a861dbd9912caaba
Author: REDACTED
Date:   Wed Jun 3 12:17:35 2026 +0000

    Update from SAP DITA CMS 2026-06-03 12:17:35

    Project: dita-all/grn1511860087951
    Project map: e9e9831a77584ae78e36b24cbb8b61b0.ditamap
    Output: loiof0e21557a271447d9a5e573ebee60dd8
    Language: en-US
    Builddable map: 6aec3039f79c49eb81ea503f014e59bd.ditamap

commit cd0206fd0196f0c7bdd3a7d9d86587050f45eb9e
Author: REDACTED
Date:   Wed Jun 3 12:05:55 2026 +0000

    Update from SAP DITA CMS 2026-06-03 12:05:55

    Project: dita-all/grn1511860087951
    Project map: e9e9831a77584ae78e36b24cbb8b61b0.ditamap
    Output: loiof0e21557a271447d9a5e573ebee60dd8
    Language: en-US
    Builddable map: 6aec3039f79c49eb81ea503f014e59bd.ditamap

commit d42464323ad09105c875f367eb51d0462d8c3313
Author: REDACTED
Date:   Wed Jun 3 12:04:50 2026 +0000

    Update from SAP DITA CMS 2026-06-03 12:04:50

    Project: dita-all/grn1511860087951
    Project map: e9e9831a77584ae78e36b24cbb8b61b0.ditamap

##################################################
[Remaining squash message was removed before commit...]
diff --git a/docs/10-initial-setup/integrating-sap-cloud-transport-management-with-other-sap-cloud-solutions-ddaa000.md b/docs/10-initial-setup/integrating-sap-cloud-transport-management-with-other-sap-cloud-solutions-ddaa000.md
@@ -364,6 +364,26 @@ To set up the integration of SAP Cloud Transport Management for the content type
 
 
     
+    </td>
+    </tr>
+    <tr>
+    <td valign="top">
+    
+    SAP Document AI
+    
+    </td>
+    <td valign="top">
+    
+    Documentation of the SAP cloud solution:
+
+    -   [SAP Document AI](https://help.sap.com/docs/document-ai)
+
+    Documentation of the integration with SAP Cloud Transport Management:
+
+    -   [Transports](https://help.sap.com/docs/SAP_DOCUMENT_AI/5fa7265b9ff64d73bac7cec61ee55ae6/5ffeda1162ae4c53941aa31723973036.html)
+
+
+    
     </td>
     </tr>
     <tr>
diff --git a/docs/20-configure-landscape/create-transport-nodes-f71a4d5.md b/docs/20-configure-landscape/create-transport-nodes-f71a4d5.md
@@ -86,7 +86,10 @@ Create transport nodes as representations of the source and target end points of
     </td>
     <td valign="top">
     
-    Use tags to categorize transport nodes by providing additional information, such as project details, or system characteristics.
+    Use tags in the following situations:
+
+    -   To categorize transport nodes by providing additional information, such as project details or system characteristics.
+    -   To group transport nodes visually in the Transport Landscape Visualization.
 
     You have the following options:
 
diff --git a/docs/30-using-import-queue/options-to-display-information-about-transport-requests-a90d808.md b/docs/30-using-import-queue/options-to-display-information-about-transport-requests-a90d808.md
@@ -61,7 +61,7 @@ For `.mtar` files, you can display additional information about the content of t
 </td>
 <td valign="top">
 
-You can display the *Log of Transport Request <Request ID\>*. It displays the actions for the transport request in the current transport node.
+You can display the *Log of Transport Request *<Transport Description\>**. It displays the actions for the transport request in the current transport node.
 
 > ### Note:  
 > For MTA deployment on Cloud Foundry, the log of the transport request contains a link to the MTA operation logs for the deploy operation. Like this, you can obtain these logs without using the Cloud Foundry command-line interface \(`cf cli`\).
diff --git a/docs/30-using-import-queue/upload-deployment-configuration-for-application-content-6dd1466.md b/docs/30-using-import-queue/upload-deployment-configuration-for-application-content-6dd1466.md
@@ -0,0 +1,110 @@
+<!-- loio6dd14665fa654e8eaa13d883e8f8ec8e -->
+
+<link rel="stylesheet" type="text/css" href="../css/sap-icons.css"/>
+
+# Upload Deployment Configuration for Application Content
+
+If the deploying application supports a deployment configuration, you can upload it for transport nodes of content type *Application Content*.
+
+
+
+## Prerequisites
+
+-   To upload or delete deployment configurations, you need the *TransportOperator* role assigned. For more information, see [Security](../60-security/security-51939a4.md).
+-   The deployment tool or application supports deployment configurations. Consult the relevant documentation for more information.
+-   You are in the import queue of a transport node for the Content Type *Application Content*. For more information, see [Prerequisites for Using the Import Queue](prerequisites-for-using-the-import-queue-dd661c7.md).
+
+
+
+## Context
+
+A deployment configuration is a JSON file that contains data to control aspects of the deployment process, such as target spaces, subfolders, or other deployment tool-specific settings. You can upload it for transport nodes for the Content Type *Application Content*. The supported configuration options and their structure are defined by the deployment tool.
+
+The deployment configuration is stored per transport node. It's passed to the deployment tool in every import triggered for that node, for as long as it remains configured. Only one deployment configuration can be active for a node at a time.
+
+Note the following:
+
+-   The configuration file content isn't logged. Only the upload or deletion actions of configuration files are recorded as transport actions.
+-   The transport request log displays the name of the configuration file that was active for the node when the import started.
+-   The deployment configuration isn't forwarded to target transport nodes. If you use deployment configurations in multiple nodes in your landscape, you must configure each node separately.
+
+    > ### Note:  
+    > Deployment configuration isn't supported for transport nodes with the *Multitarget Application \(MTA\)* content type. For MTA deployments, use MTA extension descriptors instead. For more information, see [Upload MTA Extension Descriptors](upload-mta-extension-descriptors-0c7a672.md).
+
+
+
+
+## Procedure
+
+1.  Choose <span class="SAP-icons-V5"></span> Deployment Configuration in the header action bar.
+
+    The *Deployment Configuration* dialog opens.
+
+2.  In the *Configuration File \(JSON\)* field, click in the *Upload \*.json file* field, and select a JSON file that contains the deployment configuration you want to use for deployment in the current transport node.
+
+    > ### Note:  
+    > The file must be a valid JSON file.
+
+    The content of the file is displayed in the *Configuration* preview area.
+
+    The *Description* field is automatically populated with the JSON file name.
+
+3.  Choose *Submit Configuration*.
+
+    The *Description* field is updated with the timestamp of the submission.
+
+4.  In the *Deployment Configuration* dialog, you have the following additional options:
+
+
+    <table>
+    <tr>
+    <th valign="top">
+
+    Task
+    
+    </th>
+    <th valign="top">
+
+    How To
+    
+    </th>
+    </tr>
+    <tr>
+    <td valign="top">
+    
+    Replace the deployment configuration.
+    
+    </td>
+    <td valign="top">
+    
+    Open the *Deployment Configuration* dialog, upload a new file, and choose *Submit Configuration*. The existing configuration is replaced immediately.
+    
+    </td>
+    </tr>
+    <tr>
+    <td valign="top">
+    
+    Delete the deployment configuration.
+    
+    </td>
+    <td valign="top">
+    
+    Open the *Deployment Configuration* dialog and choose *Delete Configuration*. The deletion is recorded as a transport action.
+    
+    </td>
+    </tr>
+    </table>
+    
+
+
+
+<a name="loio6dd14665fa654e8eaa13d883e8f8ec8e__result"/>
+
+## Results
+
+The deployment configuration is saved for the transport node. It's passed to the deployment tool at every subsequent import for this node.
+
+Uploading and deleting deployment configurations are reflected as *File Upload* and *File Delete* actions in the transport action logs.
+
+When you import a transport request in a node that uses a deployment configuration, the *Log of Transport Request *<Transport Description\>** contains an entry *Deployment configuration: *<file name\>* *. To view this log: In the import queue, in the line of the imported transport request, choose <span class="SAP-icons-V5"></span> \(Display the logs for queue entry\).
+
diff --git a/docs/30-using-import-queue/upload-mta-extension-descriptors-0c7a672.md b/docs/30-using-import-queue/upload-mta-extension-descriptors-0c7a672.md
@@ -116,7 +116,7 @@ For more information about how to define MTA extension descriptors, see [Definin
 
     The MTA extension descriptor that you uploaded is now available in the import queue. It is used when the transport request with the matching MTA version is imported.
 
-3.  In addition, in the *MTA Extension Descriptors* dialog window, you have the following options:
+3.  In the *MTA Extension Descriptors* dialog, you have the following additional options:
 
 
     <table>
diff --git a/docs/30-using-import-queue/using-the-import-queue-3c4b6f3.md b/docs/30-using-import-queue/using-the-import-queue-3c4b6f3.md
@@ -70,4 +70,7 @@ To run imports of all transport requests in a transport node on a regular basis,
 			Cloud Foundry
                                 environment.")**  
 If an extension descriptor file exists for a Multitarget Application \(MTA\) that you want to import, you can upload it in the import queue of the corresponding transport node of Cloud Foundry environment.
+-   **[Upload Deployment Configuration for Application Content](upload-deployment-configuration-for-application-content-6dd1466.md "If the deploying application supports a deployment configuration, you can upload it
+        for transport nodes of content type Application Content.")**  
+If the deploying application supports a deployment configuration, you can upload it for transport nodes of content type *Application Content*.
 
diff --git a/docs/grouping-transport-nodes-by-tags-b5aadd7.md b/docs/grouping-transport-nodes-by-tags-b5aadd7.md
@@ -0,0 +1,69 @@
+<!-- loiob5aadd72d88f408490d2078150b5e866 -->
+
+# Grouping Transport Nodes by Tags
+
+Group transport nodes visually based on their assigned tags enabling you to organize and identify related nodes at a glance using your own custom categories, such as regions, environments, projects, or other meaningful classifications.
+
+
+
+## Prerequisites
+
+-   Transport nodes have tags assigned to them. For more information, see [Create Transport Nodes](20-configure-landscape/create-transport-nodes-f71a4d5.md).
+-   You have one of the roles *Administrator* or *LandscapeOperator* assigned to your user. For more information, see [Security](60-security/security-51939a4.md).
+
+
+
+## Context
+
+Tag-based grouping visually groups all transport nodes that share a given tag, making it easier to navigate and understand large landscapes. You can apply multiple tags as grouping criteria. Each additional tag introduces a separate group on the canvas.
+
+Note the following points about grouping behavior:
+
+-   Each transport node belongs to exactly one group based on the first matching tag in your selection order.
+
+-   You can adjust the tag order to change the grouping perspective.
+
+-   Transport nodes that don't match any of the selected tags remain ungrouped.
+
+-   Your grouping selection is saved locally and persists across sessions, but isn't shared or stored on the server.
+
+
+
+
+## Procedure
+
+1.  On the SAP Cloud Transport Management home screen, choose *Landscape Visualization* from the navigation pane.
+
+2.  In the *View* toolbar, use the *Group by Tag* selection box to select one or more tags.
+
+    -   1.  Select the dropdown arrow.
+
+    A dropdown menu of all tags that are currently assigned to at least one transport node appears.
+
+2.  Select one or more tags to use as grouping criteria.
+
+
+    -   Start typing the tag name and choose [Enter\] to confirm your selection.
+
+
+
+
+<a name="loiob5aadd72d88f408490d2078150b5e866__result"/>
+
+## Results
+
+The canvas updates immediately. Transport nodes that share a selected tag are enclosed in a labeled group frame.
+
+If a transport node has multiple tags and more than one of those tags is selected, the node is assigned to the group of the **first matching tag** in the order in which you selected the tags.
+
+The grouping persists across page refreshes for your user session on the current device.
+
+You have the following options:
+
+-   To change the group assignment of such a node, deselect and reselect the tags in the desired order.
+
+-   To remove a grouping, deselect the corresponding tag in the *Group by Tag* dropdown.
+
+    The group frame is removed from the canvas. Nodes that were part of this group revert to their ungrouped position, or are reassigned to another group if they match a remaining selected tag.
+
+
diff --git a/docs/index.md b/docs/index.md
@@ -35,6 +35,7 @@
     -   [Create Destinations to SAP Cloud Transport Management Service](20-configure-landscape/create-destinations-to-sap-cloud-transport-management-service-795f733.md#loio795f7337e5d943df98c961303b02678b)
         -   [Example: Destination to SAP Cloud Transport Management](20-configure-landscape/create-destinations-to-sap-cloud-transport-management-service-795f733.md#loio75fe5d4b4fa3492c87ef6be32ea0b819)
 -   [Using the Landscape Visualization](using-the-landscape-visualization-9fea4f2.md)
+    -   [Grouping Transport Nodes by Tags](grouping-transport-nodes-by-tags-b5aadd7.md)
 -   [Using the Import Queue](30-using-import-queue/using-the-import-queue-3c4b6f3.md)
     -   [Prerequisites for Using the Import Queue](30-using-import-queue/prerequisites-for-using-the-import-queue-dd661c7.md)
     -   [Search and Filter Options in an Import Queue](30-using-import-queue/search-and-filter-options-in-an-import-queue-3228b4c.md)
@@ -48,6 +49,7 @@
     -   [Enable Automatic Import](30-using-import-queue/enable-automatic-import-9171d39.md)
     -   [Schedule Imports](30-using-import-queue/schedule-imports-110a7a4.md)
     -   [Upload MTA Extension Descriptors](30-using-import-queue/upload-mta-extension-descriptors-0c7a672.md)
+    -   [Upload Deployment Configuration for Application Content](30-using-import-queue/upload-deployment-configuration-for-application-content-6dd1466.md)
 -   [Managing Transport Requests](40-using-request-overview/managing-transport-requests-d088caa.md)
     -   [Displaying Details of Transport Requests](40-using-request-overview/displaying-details-of-transport-requests-0415f2f.md)
     -   [Processing Modifiable Transport Requests](40-using-request-overview/processing-modifiable-transport-requests-b541b09.md)
diff --git a/docs/supported-content-types-8961dcb.md b/docs/supported-content-types-8961dcb.md
@@ -951,6 +951,58 @@ No
 <tr>
 <td valign="top">
 
+SAP Document AI
+
+</td>
+<td valign="top">
+
+Multiple objects, such as channels, schemas, and workflows. For the full list, see [Supported Objects](https://help.sap.com/docs/SAP_DOCUMENT_AI/5fa7265b9ff64d73bac7cec61ee55ae6/f605fd01abb548c380f4cf54db579d56.html).
+
+</td>
+<td valign="top">
+
+Application Content
+
+</td>
+<td valign="top">
+
+Cloud Foundry
+
+</td>
+<td valign="top">
+
+Yes
+
+</td>
+<td valign="top">
+
+No
+
+</td>
+<td valign="top">
+
+n/a
+
+</td>
+<td valign="top">
+
+No
+
+</td>
+<td valign="top">
+
+The integration covers the SAP Document AI workspace. You can select the objects that you want to transport in the workspace UI.
+
+</td>
+<td valign="top">
+
+[SAP Document AI](10-initial-setup/integrating-sap-cloud-transport-management-with-other-sap-cloud-solutions-ddaa000.md#loioddaa000bc92c43d8bd09f4e2c8ca05eb__dai)
+
+</td>
+</tr>
+<tr>
+<td valign="top">
+
 SAP Entitlement Management
 
 </td>
diff --git a/docs/using-the-landscape-visualization-9fea4f2.md b/docs/using-the-landscape-visualization-9fea4f2.md
diff --git a/docs/what-s-new-for-sap-cloud-transport-management-85b6ac3.md b/docs/what-s-new-for-sap-cloud-transport-management-85b6ac3.md
