Update from SAP DITA CMS (squashed):

commit a5e29938f55194cd4c8798ad7f615dce09193fd4
Author: REDACTED
Date:   Wed Oct 29 08:03:35 2025 +0000

    Update from SAP DITA CMS 2025-10-29 08:03:35

    Project: dita-all/jjq1673438782153
    Project map: c2f780f61c744155b0bd42b6f38fb70c.ditamap
    Output: loio2080d0faf9d84ce6aa14caa4caa32935
    Language: en-US
    Builddable map: 0fcfe38e11674227bb0a8d014337319b.ditamap

commit 678b81cc9e73333e4396328ceb0ce085ba966c89
Author: REDACTED
Date:   Tue Oct 28 16:17:32 2025 +0000

    Update from SAP DITA CMS 2025-10-28 16:17:32

    Project: dita-all/jjq1673438782153
    Project map: c2f780f61c744155b0bd42b6f38fb70c.ditamap
    Output: loio2080d0faf9d84ce6aa14caa4caa32935
    Language: en-US
    Builddable map: 0fcfe38e11674227bb0a8d014337319b.ditamap

commit 7f0c257abad171c9e7871701b789a13c9f320e3d
Author: REDACTED
Date:   Tue Oct 28 15:50:36 2025 +0000

    Update from SAP DITA CMS 2025-10-28 15:50:35

    Project: dita-all/jjq1673438782153
    Project map: c2f780f61c744155b0bd42b6f38fb70c.ditamap

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

Author: ditaccms-bot

docs/10-concepts/regions-and-api-endpoints-available-for-the-cloud-foundry-environment-f344a57.md

@@ -5,9 +5,14 @@
 
 
 > ### Note:  
-> If you are using the Cloud Connector for on-premise connections between SAP BTP applications and your local network, and you restrict network access by allowlisting IP addresses in your local firewall rules, you must add connectivity-specific IPs to these rules for the respective SAP BTP region\(s\).
+> If you are using the Cloud Connector and/or the Destination service for connections between your SAP BTP applications and your local network or another \(web-based\) target system, and you restrict access by allowlisting IP addresses in your firewall rules, you must add connectivity-specific IPs to these rules for the respective SAP BTP region\(s\).
 > 
-> For more information, see [Prerequisites: Network](https://help.sap.com/docs/connectivity/sap-btp-connectivity-cf/prerequisites#network) \(Cloud Connector documentation\).
+> For the Destination service, both the egress and ingress IPs \(NAT and LB IPs\) may be relevant.
+> 
+> For more information, see:
+> 
+> -   [Prerequisites: Network](https://help.sap.com/docs/connectivity/sap-btp-connectivity-cf/prerequisites#network) \(Cloud Connector\)
+> -   [Configure Destination Service IPs in Firewall Rules](https://help.sap.com/docs/connectivity/sap-btp-connectivity-cf/destination-service-nat-ips) \(Destination service\)
 
 **Regions for Enterprise Accounts**
 
@@ -1105,6 +1110,58 @@ Amazon Web Services
 </td>
 <td valign="top">
 
+eu13
+
+</td>
+<td valign="top">
+
+Europe \(Milan\)
+
+</td>
+<td valign="top">
+
+cf-us13
+
+</td>
+<td valign="top">
+
+eu-south-1
+
+</td>
+<td valign="top">
+
+15.161.87.249, 15.161.194.156, 18.99.209.0/27, 35.152.224.143
+
+</td>
+<td valign="top">
+
+15.161.2.170, 18.102.32.205, 18.102.85.10
+
+</td>
+<td valign="top">
+
+api.cf.eu13.hana.ondemand.com
+
+</td>
+<td valign="top">
+
+eu13.hana.ondemand.com
+
+</td>
+<td valign="top">
+
+[Open Cockpit](https://cockpit.btp.cloud.sap/) 
+
+</td>
+</tr>
+<tr>
+<td valign="top">
+
+Amazon Web Services
+
+</td>
+<td valign="top">
+
 us10
 
 </td>
@@ -1127,7 +1184,7 @@ us-east-1
 
 **cf-us10:**
 
-52.200.16.71, 52.23.123.125, 52.202.170.155, 18.210.47.160, 18.211.235.11, 54.156.172.106, 34.234.191.59, 34.192.134.47, 18.204.173.15, 3.213.197.54, 184.73.43.82, 52.20.242.182, 3.216.16.207, 34.225.190.250, 52.2.110.230, 54.234.93.200, 35.153.88.132, 52.204.111.138, 3.88.250.160, 54.221.30.91, 52.71.83.110, 52.200.165.163, 54.208.119.130, 34.202.136.35, 34.192.100.96, 54.85.65.82, 54.205.71.200,18.97.43.224/27
+52.200.16.71, 52.23.123.125, 52.202.170.155, 18.97.43.224/27
 
 **cf-us10-001:**
 
@@ -1142,7 +1199,7 @@ us-east-1
 
 **cf-us10:**
 
-52.4.101.240, 52.23.1.211, 52.23.189.23, 18.213.242.208, 3.214.110.153, 34.205.56.51
+18.213.242.208, 3.214.110.153, 34.205.56.51
 
 **cf-us10-001:**
 

docs/10-concepts/regions-for-the-kyma-environment-557ec3a.md

@@ -89,6 +89,8 @@ Singapore
 
 `trial`
 
+`build-runtime-azure`
+
 </td>
 </tr>
 <tr>
@@ -125,6 +127,8 @@ US West \(WA\)
 
 `azure_lite`
 
+`build-runtime-azure`
+
 </td>
 </tr>
 <tr>
@@ -161,6 +165,8 @@ Japan \(Tokyo\)
 
 `azure_lite`
 
+`build-runtime-azure`
+
 </td>
 </tr>
 <tr>
@@ -273,6 +279,8 @@ Australia \(Sydney\)
 
 `azure_lite`
 
+`build-runtime-azure`
+
 </td>
 </tr>
 <tr>
@@ -309,6 +317,8 @@ Brazil \(São Paulo\)
 
 `azure_lite`
 
+`build-runtime-azure`
+
 </td>
 </tr>
 <tr>
@@ -547,7 +557,9 @@ Brazil \(São Paulo\)
 </td>
 <td valign="top">
 
-`aws` 
+`aws`
+
+`build-runtime-aws`
 
 </td>
 </tr>
@@ -579,7 +591,9 @@ Japan \(Tokyo\)
 </td>
 <td valign="top">
 
-`aws` 
+`aws`
+
+`build-runtime-aws`
 
 </td>
 </tr>
@@ -611,7 +625,9 @@ Canada \(Montreal\)
 </td>
 <td valign="top">
 
-`aws` 
+`aws`
+
+`build-runtime-aws`
 
 </td>
 </tr>
@@ -709,7 +725,9 @@ Singapore
 </td>
 <td valign="top">
 
-`aws` 
+`aws`
+
+`build-runtime-aws`
 
 </td>
 </tr>
@@ -1099,7 +1117,9 @@ Australia \(Sydney\)
 </td>
 <td valign="top">
 
-`gcp` 
+`gcp`
+
+`build-runtime-gcp`
 
 </td>
 </tr>

docs/20-getting-started/assigning-the-abap-developer-user-to-the-abap-developer-role-13b2cfb.md

@@ -6,34 +6,19 @@ Add the developer user as business user to the ABAP instance.
 
 
 
-<a name="loio13b2cfb49c8046d8a031e137b6142127__prereq_p5l_vvq_p2b"/>
-
-## Prerequisites
-
 You have created an employee record for the new developer user \(see [Creating an Employee Record for a New Developer](creating-an-employee-record-for-a-new-developer-a66fdc5.md)\).
 
-You have created an ABAP developer role based on the business role template `SAP_BR_DEVELOPER`, which provides developers with unrestricted read and write access in the ABAP environment. Alternatively, you have created a business role based on a development-related business catalog \(see [Business Catalogs for Development Tasks](../50-administration-and-ops/business-catalogs-for-development-tasks-a9f4278.md)\).
-
-
+> ### Caution:  
+> The `SAP_BR_ADMINISTRATOR` role is pre-defined by SAP and only intended for the initial set-up of a system. Please create your own business roles based on the required business role template.
 
-<a name="loio13b2cfb49c8046d8a031e137b6142127__steps_yzb_fnm_q2b"/>
-
-## Procedure
+For information about creating a business role based on a development-related business catalog, see [Business Catalogs for Development Tasks](../50-administration-and-ops/business-catalogs-for-development-tasks-a9f4278.md).
 
 1.  Log on to the administration launchpad of the ABAP environment as administrator \(see [Logging on to the Administration Launchpad of the ABAP Environment](logging-on-to-the-administration-launchpad-of-the-abap-environment-11e765e.md)\).
-
 2.  On the SAP Fiori launchpad, choose the *Maintain Business Users* tile.
-
 3.  Choose *New*.
-
 4.  In the following dialog, choose the employee record of the new developer user from the list.
-
 5.  Confirm the system message that you want to create a new user.
-
 6.  On the *Assigned Business Roles* tab, choose *Add*.
-
 7.  Select the checkbox for the ABAP developer role that you have created before \(see *Prerequisites*\).
-
 8.  Choose *OK* and save your entries.
 
-

docs/20-getting-started/assigning-the-abap-environment-administrator-role-to-the-new-administrator-user-ad888b0.md

@@ -6,34 +6,18 @@ Add the new administration user as administrator to the ABAP instance.
 
 
 
-<a name="loioad888b0ab0a74665a22e0a58ef9e9100__prereq_p5l_vvq_p2b"/>
-
-## Prerequisites
-
 You have logged on to the administration launchpad of the ABAP environment as administrator \(see [Logging on to the Administration Launchpad of the ABAP Environment](logging-on-to-the-administration-launchpad-of-the-abap-environment-11e765e.md)\). You have created an employee record for another, new administrator.
 
 
 
-## Procedure
-
 1.  On the SAP Fiori launchpad, choose the *Maintain Business Users* tile.
-
 2.  Choose *New*.
-
 3.  In the following dialog, choose the employee record of the new administrator from the list.
-
 4.  Confirm the system message that you want to create a new user.
-
 5.  Add the time zone to the business user data.
-
 6.  On the *Assigned Business Roles* tab, choose *Add*.
-
 7.  Select the checkbox for the predefined administrator business role `SAP_BR_ADMINISTRATOR`.
-
 8.  Select the checkbox for other administrator roles that are available for your organization and choose *OK*.
-
 9.  Choose *OK*.
-
 10. Choose *Save*.
 
-

docs/20-getting-started/creating-an-abap-system-50b32f1.md

@@ -225,7 +225,7 @@ For more information about creating service instances, see [Create Service Insta
     </td>
     <td valign="top">
 
-    The **HANA Cloud disk size** refers to the disk size in GB of the SAP HANA Cloud database used by the ABAP environment service instance. If the parameter is set to `auto`, the SAP HANA Cloud storage size is set to the minimal value `40 * size_of_persistence + 40`. The maximum allowed value is `240 * size_of_persistence + 40`. If you set a higher value, it will consume 0.002 HANA compute units \(HCU\) for any GB exceeding the minimal default size of the persistence disk. Therefore, the HCU ratio of additional storage disk to RAM is 1 : 31.25 per GB \(as 1 HCU = 16 GB\).
+    The **HANA Cloud disk size** refers to the disk size in GB of the SAP HANA Cloud database used by the ABAP environment service instance. If the parameter is set to `auto`, the SAP HANA Cloud storage size is set to the minimal value `40 * size_of_persistence + 40`. The maximum allowed value is `120 * size_of_persistence + 40`. If you set a higher value, it will consume 0.002 HANA compute units \(HCU\) for any GB exceeding the minimal default size of the persistence disk. Therefore, the HCU ratio of additional storage disk to RAM is 1 : 31.25 per GB \(as 1 HCU = 16 GB\).
 
     </td>
     </tr>

docs/30-development/apirule-migration-f8df238.md

@@ -35,20 +35,25 @@ For more information about APIRule `v2`, see also [APIRule `v2` Custom Resource]
 
 ## APIRule `v1beta1` Migration Timeline
 
-The following timeline outlines the steps we will take to phase out version `v1beta1`:
+The APIRule `v1beta1` deletion process is divided into three steps. See the following timeline:
 
-1.  Kyma dashboard won't display APIRule CRs in version v1beta1. All APIRules `v1beta1` will be fully operational from the command line, and you will still be able to manage them using kubectl. This change will not affect any pipelines that manage APIRules using Kubernetes utilities such as kubectl or helm.
-    -   Fast channel release date: **August 18, 2025**
-    -   Regular channel release date: **September 1, 2025**
+**Step 1: Completed with API Gateway 3.2**
 
-2.  You won't be able to create APIRule CRs `v1beta1` in new clusters. In existing clusters, you will still be able to create and modify APIRule CRs `v1beta1`.
-    -   Fast channel release date: **End of October, 2025**
-    -   Regular channel release date: **Mid-November, 2025**
+Kyma dashboard doesn’t display APIRule CRs in version `v1beta1`. All APIRules `v1beta1` are fully operational from the command line, and you are still able to manage them using kubectl. This change does not affect any pipelines that manage APIRules using Kubernetes utilities such as kubectl or helm.
 
-3.  You won't be able to create APIRule CRs `v1beta1` in new and existing clusters, modify existing APIRule CRs `v1beta1`, or delete them. All APIRule `v1beta1` configurations set up prior to this restriction will remain active and continue to function as expected. The API Gateway module will manage and reconcile resources based on the existing APIRule settings.
-    -   Fast channel release date: **Mid-November, 2025**
-    -   Regular channel release date: **End of the year 2025**
+**Step 2: Planned for API Gateway 3.3**
 
+You won't be able to create APIRule CRs `v1beta1` in new clusters. In existing clusters, you will still be able to create and modify APIRule CRs `v1beta1`.
+
+-   Fast channel release date: 27 October, 2025
+-   Regular channel release date: 18 November, 2025
+
+**Step 3: Planned for API Gateway 3.4**
+
+You won't be able to create APIRule CRs `v1beta1` in new and existing clusters, modify existing APIRule CRs `v1beta1`, or delete them. All APIRule `v1beta1` configurations set up prior to this restriction will remain active and continue to function as expected. The API Gateway module will manage and reconcile resources based on the existing APIRule settings.
+
+-   Fast channel release date: Mid-November, 2025
+-   Regular channel release date: End of the year 2025
 
 ![](images/APIRule_Migration_Timeline_-_External_f1ce3d8.png)
 

docs/30-development/application-routes-and-destinations-3cc788e.md

@@ -278,6 +278,18 @@ HTML5.ForwardAuthCertificates
 
 If `true`, the certificates and key of the authentication service are added to the HTTP connection to the destination. The default value is `false`. For more information see: [Mutual TLS Authentication \(mTLS\) and Certificates Handling](mutual-tls-authentication-mtls-and-certificates-handling-46b8b85.md).
 
+</td>
+</tr>
+<tr>
+<td valign="top">
+
+URL.headers.<header-name\>
+
+</td>
+<td valign="top">
+
+If you provide this property, the application router propagates the specified attribute as a header in the destination.The application router retrieves the list of headers from the destination API. Existing request headers are not overwritten.
+
 </td>
 </tr>
 </table>

docs/30-development/automate-the-software-lifecycle-management-process-e342c24.md

@@ -2,11 +2,11 @@
 
 # Automate the Software Lifecycle Management Process
 
-To facilitate your software lifecycle management process, you can automate it by using communication scenario `SAP_COM_0510` and `SAP_COM_0735`. See [Pulling Git Repositories to an ABAP Environment System](pulling-git-repositories-to-an-abap-environment-system-80a8d52.md) and [Running ABAP Unit Test Runs](running-abap-unit-test-runs-cdd19e3.md).
+To facilitate your software lifecycle management process, you can automate it by using communication scenario `SAP_COM_0948` and `SAP_COM_0735`. See [API for Managing Software Components](../50-administration-and-ops/api-for-managing-software-components-61f4d47.md) and [Running ABAP Unit Test Runs](running-abap-unit-test-runs-cdd19e3.md).
 
 These communication scenarios contain several tools that can be used to craft a continuous integration process.
 
-To make the setup of continuous integration pipelines as easy as possible, the open source project "Piper" was created. In general, there are various functions \(Library steps\) as well as whole pipelines available for reuse. You can find various steps that implement the functionality of the APIs of `SAP_COM_0510` and `SAP_COM_0735`.
+To make the setup of continuous integration pipelines as easy as possible, the open source project "Piper" was created. In general, there are various functions \(Library steps\) as well as whole pipelines available for reuse. You can find various steps that implement the functionality of the APIs of `SAP_COM_0948` and `SAP_COM_0735`.
 
 The reusable continuous integration pipeline contains the following steps: