Update from SAP DITA CMS (squashed):

commit 62f4b882dafcdc55bf4c2e3cdb01cedbf938db1f
Author: REDACTED
Date:   Wed Dec 18 09:40:08 2024 +0000

    Update from SAP DITA CMS 2024-12-18 09:40:08

    Project: dita-all/nih1586262997200
    Project map: baa817af5a7c4aa798ad5d2792ae0111.ditamap
    Output: loio0f341afe0f5e4107ad982c53bfc412dc
    Language: en-US
    Builddable map: 6dd68ae2cfea4cdf8ba6b96497472829.ditamap

commit 937fadec1ce1bf744224a725de8b2df9bf552e4f
Author: REDACTED
Date:   Wed Dec 18 08:46:24 2024 +0000

    Update from SAP DITA CMS 2024-12-18 08:46:24

    Project: dita-all/nih1586262997200
    Project map: baa817af5a7c4aa798ad5d2792ae0111.ditamap
    Output: loio0f341afe0f5e4107ad982c53bfc412dc
    Language: en-US
    Builddable map: 6dd68ae2cfea4cdf8ba6b96497472829.ditamap

commit f6d34c92989e30366a77a22ae0a591c88879537e
Author: REDACTED
Date:   Tue Dec 17 14:54:48 2024 +0000

    Update from SAP DITA CMS 2024-12-17 14:54:48

    Project: dita-all/nih1586262997200
    Project map: baa817af5a7c4aa798ad5d2792ae0111.ditamap

##################################################
[Remaining squash message was removed before commit...]

Author: ditaccms-bot

docs/01_required_setup/role-collections-e1915af.md

@@ -4,11 +4,15 @@
 
 Role collections in SAP Cloud ALM are delivered predefined and ready to use.
 
-Each application role in SAP Cloud ALM represents a role collection in your SAP BTP subaccount, which in turn corresponds 1:1 to the respective role template \(with the exception of the *Cross Global Administrator*, the *User & Access Management Administrator*, and the *Deployment Manager*\). This means that you don't have to configure any role collections yourself. Instead, you can simply assign the relevant role collections to the users based on their tasks and requirements.
+Each application role in SAP Cloud ALM represents a role collection in your SAP BTP subaccount. Most SAP Cloud ALM role collections correspond 1:1 to the respective role template and can be assigned to users without any further configuration.
 
 Each application role contains all the necessary authorizations that are required for all tasks that belong to a certain business role, rather than being confined to a single task. For example, the role *Health Monitoring Administrator* also contains authorizations in apps other than *Health Monitoring* because someone in that role also needs to be able to configure events and set up notifications.
 
-The following role collections are available for each application area in SAP Cloud ALM:
+
+
+<a name="loioe1915af019da48cc8b8e58399e8ea235__section_nrl_qlc_pdc"/>
+
+## Available Role Collections
 
 ****
 

docs/01_required_setup/services-d5f36cc.md

@@ -4,7 +4,7 @@
 
 # Services
 
-The import method of services in SAP Cloud ALM depends on the service type of your solution.
+The import method of services in SAP Cloud ALM depends on the service type of your [solution](../supported-solutions-3ebab44.md).
 
 
 

docs/01_required_setup/step-3-set-up-landscape-management-23f1c49.md

@@ -6,6 +6,8 @@ As the last step of the required setup, services and systems need to be set up i
 
 Landscape management in SAP Cloud ALM helps you manage information about your services, systems, and business services. This information is the basis for all SAP Cloud ALM apps.
 
+To see which services and systems are supported by SAP Cloud ALM, refer to [Supported Solutions](../supported-solutions-3ebab44.md).
+
 
 
 <a name="loio23f1c49b224b4f17b2d959e01ae9c930__section_is1_q55_fzb"/>
@@ -54,9 +56,8 @@ For more information, see [Access Control](https://help.sap.com/viewer/877c96cf9
 
 If you encounter issues while working with the *Landscape Management* app, take a look at [Landscape Management – Troubleshooting and Customer Support](https://support.sap.com/en/alm/sap-cloud-alm/operations/expert-portal/landscape-management.html?anchorId=section_667953570_co) on SAP Support Portal.
 
--   **[Services](services-d5f36cc.md "The import method of services in SAP Cloud ALM depends on the service type of your
-		solution.")**  
-The import method of services in SAP Cloud ALM depends on the service type of your solution.
+-   **[Services](services-d5f36cc.md "The import method of services in SAP Cloud ALM depends on the service type of your solution.")**  
+The import method of services in SAP Cloud ALM depends on the service type of your [solution](../supported-solutions-3ebab44.md).
 -   **[Systems](systems-d9d672a.md "Most systems can be registered with an ABAP report.")**  
 Most systems can be registered with an ABAP report.
 

docs/02_integration_and_config_options/connecting-sap-document-management-service-b788f20.md

@@ -0,0 +1,131 @@
+<!-- loiob788f20e1d71444eb5568b3c2153087b -->
+
+# Connecting SAP Document Management Service
+
+You can integrate and activate the SAP Document Management service for document storage in SAP Cloud ALM.
+
+If you want to upload [External Files](https://help.sap.com/docs/cloud-alm/applicationhelp/external-files) in the *Documents* app of SAP Cloud ALM, first establish a connection between your SAP Document Management service \(SAP BTP DMS\) and your SAP Cloud ALM tenant.
+
+> ### Note:  
+> Make sure you use both the [SAP Document Management Service, Integration Option](https://help.sap.com/docs/document-management-service/sap-document-management-service/initial-setup-for-document-management-service-integration-option?version=Cloud) and the [SAP Document Management Service, Repository Option](https://help.sap.com/docs/document-management-service/sap-document-management-service/document-management-service-repository-option).
+
+
+
+<a name="loiob788f20e1d71444eb5568b3c2153087b__section_cxr_43g_jdc"/>
+
+## Prerequisites
+
+-   You need to provide your own SAP Document Management service instance and establish a connection to SAP Cloud ALM. For more information, see [Initial Setup for Document Management Service, Integration Option](https://help.sap.com/docs/document-management-service/sap-document-management-service/initial-setup-for-document-management-service-integration-option?version=Cloud). You can use an existing service instance for SAP Cloud ALM use.
+
+-   You've done the initial setup for the SAP Document Management integration option and you've obtained all the necessary login data.
+
+-   You're familiar with the [SAP Business Technology Platform \(SAP BTP\)](https://help.sap.com/docs/btp?version=Cloud) cockpit, and the  [Account Administration](https://help.sap.com/docs/btp/sap-business-technology-platform/account-administration?version=Cloud) concepts.
+
+-   You've got the role *Subaccount Administrator* for your SAP BTP subaccount of SAP Cloud ALM and SAP Document Management service.
+
+
+
+
+<a name="loiob788f20e1d71444eb5568b3c2153087b__section_p1b_kqg_jdc"/>
+
+## Procedure 
+
+1.  Set up the HTTP destination.
+
+    In the SAP BTP subaccount, where your SAP Cloud ALM is hosted, create a destination targeted at your SAP BTP DMS instance.
+
+    > ### Note:  
+    > If you have several SAP Cloud ALM tenants, you can onboard a separate SAP BTP DMS for each tenant. You can also reuse the same SAP BTP DMS for all your tenants. SAP Cloud ALM automatically creates a unique repository for each SAP Cloud ALM tenant to store the external files.
+    > 
+    > Here's what we recommend:
+    > 
+    > -   Only connect your productively used SAP BTP DMS instance to your productive SAP Cloud ALM instance.
+    > 
+    > -   Don't connect your productive SAP BTP DMS environment to SAP Cloud ALM instances for non-productive usage.
+    > 
+    > -   Only connect the demo and sandbox SAP BTP DMS instances to your test SAP Cloud ALM instance.
+
+    1.  Go to your SAP BTP subaccount and choose *Connectivity* \> *Destinations* \> *Create Destination*.
+
+    2.  Under *Destination Configuration*, fill in the required fields. Enter the following information:
+
+        -   *Name*:`CALM_SD_DMS_INTEGRATION`
+
+        -   *Type*: HTTP
+
+        -   *Description* \(optional\): enter a description for your reference
+
+        -   *URL*: value of `uri` from the service key of your SAP BTP DMS instance
+
+        -   *Proxy Type*: Internet
+
+        -   *Authentication*: `OAuth2ClientCredentials`
+
+        -   *Client ID*: value of `clientid` \(`uaa` section\) from the service key of your SAP BTP DMS instance
+
+        -   *Client Secret*: value of `clientsecret` \(`uaa` section\) from the service key of your SAP BTP DMS instance
+
+        -   *Token Service URL*: value of `URL` \(`uaa` section\) from the service key of your SAP BTP DMS instance
+
+            Append `/oauth/token` to the `URL` retrieved from the service key.
+
+
+
+    You can choose *Check Connection*. When the check is successful, you can ignore the `401: Unauthorized` warning.
+
+2.  When you've established the connection, it can take up to 5 minutes before you can start uploading external files with the *Documents* app in SAP Cloud ALM. Choose *External File* on the object page of a document, and you see the following:
+
+    ![](images/External_File_d05b6c9.jpg)
+
+
+You can now start to use the [External Files](https://help.sap.com/docs/cloud-alm/applicationhelp/external-files) feature in the *Documents* app of SAP Cloud ALM.
+
+
+
+<a name="loiob788f20e1d71444eb5568b3c2153087b__section_fl1_gv1_qdc"/>
+
+## Repository Handling
+
+During the initial communication between SAP Cloud ALM and the SAP Document Management service, the *Documents* app automatically creates a new repository in the SAP Document Management service.
+
+> ### Caution:  
+> Do **not** change this repository or any other repositories created by the *Documents* app. The property external ID of a repository is always identical with the tenant ID of the tenant that created it. With this information, the user can always trace which repository belongs to which tenant.
+> 
+> Changes done in the repository directly aren't reflected in SAP Cloud ALM and they disrupt the integration.
+
+The repository has the following characteristics, which you can't change:
+
+-   External ID: SAP Cloud ALM tenant UUID \(unique\)
+
+    The external ID is always identical to the tenant ID of the tenant that created it. With this information, you can always trace which repository belongs to which tenant.
+
+-   Name: SAP Cloud ALM for Implementation
+-   Description: Internal Repository for SAP Cloud ALM for Implementation
+-   Encryption enabled
+-   Virus scan enabled
+-   Versioning enabled
+-   Thumbnail disabled \(not possible with enabled encryption\)
+
+Files in this repository are automatically managed as follows:
+
+-   All files are stored in the `ROOT` folder. No new folders are created.
+-   For the file name \(`cmis:name`\), a UUID from the SAP database table is used.
+-   The `cmis:name` only contains a technical ID. The real file name is stored in the property `cmis:contentStreamFileName`.
+-   SAP Cloud ALM doesn't replicate any additional metadata, for example, the extension field `sap:owner` and other extension fields aren't filled.
+-   With every upload of an external file, SAP Cloud ALM creates a new major version in SAP BTP DMS: 1.0, 2.0, … X.0. No minor versions are created.
+-   The maximum size for files to upload is 10 MB.
+-   Which file types are supported, you can see in [External Files](https://help.sap.com/docs/cloud-alm/applicationhelp/external-files).
+
+
+
+
+<a name="loiob788f20e1d71444eb5568b3c2153087b__section_tml_34s_pdc"/>
+
+## Disabling the External File Feature
+
+There's no process to discontinue the external file feature in the *Documents* app.
+
+If you no longer want to use the feature, you need to manually delete the external files in the *Documents* app.
+
+After that, you can delete the SAP BTP DMS repository and disconnect the configured destination.
+

docs/02_integration_and_config_options/enabling-sap-cloud-alm-api-704b5dc.md

@@ -121,6 +121,9 @@ To consume the selected service plan, you need to create a service instance.
 
 2.  Enter a name for your binding.
 
+    > ### Caution:  
+    > To avoid conflicts with automatically created service credentials, use a name that differs from the naming convention `<system ID>_<client number>_<system number>`.
+
 3.  Choose *Create*.
 
 4.  Next to the created binding, choose <span class="SAP-icons-V5"></span> \(Actions\) and select *View*.

docs/02_integration_and_config_options/enabling-sap-cloud-alm-api-in-cloud-foundry-7d4c180.md

@@ -150,6 +150,9 @@ With service keys, you can manually generate service credentials to enable exter
 
 2.  Enter a name for your service key.
 
+    > ### Caution:  
+    > To avoid conflicts with automatically created service keys, use a name that differs from the naming convention `<system ID>_<client number>_<system number>`.
+
 3.  Choose *Create*.
 
 4.  Next to your newly created service key, choose <span class="SAP-icons-V5"></span> \(Actions\) and select *View*.

docs/02_integration_and_config_options/enabling-service-delivery-a1b2494.md

@@ -39,7 +39,7 @@ In addition, SAP synchronizes changes that you make to the following service-rel
 
 ## Activating and Deactivating the Data Transfer
 
-This data transfer is automatically activated when your SAP Cloud ALM tenant was provisioned. If you don't want service information to be transferred into your SAP Cloud ALM tenant, you can request to deactivate the data transfer by creating an incident on component SV-CLM-SD. Please provide the following information in the incident:
+This data transfer is automatically activated when your SAP Cloud ALM tenant was provisioned. If you don't want service information to be transferred into your SAP Cloud ALM tenant, you can request to deactivate the data transfer by creating a case on component SV-CLM-SD. Please provide the following information in the case:
 
 -   Your customer number
 

docs/02_integration_and_config_options/images/External_File_d05b6c9.jpg

@@ -21,8 +21,7 @@ SAP Cloud ALM currently supports the integration with the following automation p
 
 [Automated Test Cases – SAP Help Portal](https://help.sap.com/docs/cloud-alm/applicationhelp/automated-test-cases)
 
--   **[Integrating the Test Automation Tool for SAP S/4HANA Cloud Public Edition](integrating-the-test-automation-tool-for-sap-s-4hana-cloud-public-edition-0712254.md "You can integrate automated test cases from the test automation tool for SAP
-            S/4HANA Cloud Public Edition for use in test
+-   **[Integrating the Test Automation Tool for SAP S/4HANA Cloud Public Edition](integrating-the-test-automation-tool-for-sap-s-4hana-cloud-public-edition-0712254.md "You can integrate automated test cases from the test automation tool for SAP S/4HANA Cloud Public Edition for use in test
 		orchestration in SAP Cloud ALM.")**  
 You can integrate automated test cases from the test automation tool for SAP S/4HANA Cloud Public Edition for use in test orchestration in SAP Cloud ALM.
 -   **[Setting Up Tricentis Test Automation for SAP Integrated with SAP Cloud ALM](setting-up-tricentis-test-automation-for-sap-integrated-with-sap-cloud-alm-2bddb58.md "Tricentis Test Automation for SAP integrated with SAP Cloud ALM is a joint cloud-based