Update from SAP DITA CMS (squashed):

commit bb0b50818141d7e191951d0163d9735369413f0b
Author: REDACTED
Date:   Wed Nov 29 17:10:57 2023 +0000

    Update from SAP DITA CMS 2023-11-29 17:10:57
    Project: dita-all/jjq1673438782153
    Project map: c2f780f61c744155b0bd42b6f38fb70c.ditamap
    Language: en-US

commit 76660ddae429218174d11db53ed027325449038e
Author: REDACTED
Date:   Tue Nov 28 19:34:26 2023 +0000

    Update from SAP DITA CMS 2023-11-28 19:34:26
    Project: dita-all/jjq1673438782153
    Project map: c2f780f61c744155b0bd42b6f38fb70c.ditamap
    Language: en-US

commit f25309bcfe1e46edeaa5fdeb07c80b05c997c774
Author: REDACTED
Date:   Tue Nov 28 19:13:25 2023 +0000

    Update from SAP DITA CMS 2023-11-28 19:13:25
    Project: dita-all/jjq1673438782153
    Project map: c2f780f61c744155b0bd42b6f38fb70c.ditamap
    Language: en-US

commit 2b1f0ad0f6badc9af2c44ea2f6136b73257f7e54
Author: REDACTED
Date:   Tue Nov 28 15:31:45 2023 +0000

    Update from SAP DITA CMS 2023-11-28 15:31:45

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

docs/30-development-neo/defining-mta-extension-descriptors-d32758f.md

@@ -5,12 +5,12 @@
 > ### Tip:  
 > **This documentation refers to SAP Business Technology Platform, Neo environment. If you are looking for documentation about other environments, see [SAP Business Technology Platform](https://help.sap.com/viewer/65de2977205c403bbc107264b8eccf4b/Cloud/en-US/6a2c1ab5a31b4ed9a2ce17a5329e1dd8.html "SAP Business Technology Platform (SAP BTP) is an integrated offering comprised of four technology portfolios: database and data management, application development and integration, analytics, and intelligent technologies. The platform offers users the ability to turn data into business value, compose end-to-end business processes, and build and extend SAP applications quickly.") :arrow_upper_right:.**
 
-The Multitarget Application \(МТА\) extension descriptor is a YAML file that contains data complementary to the deployment descriptor. The data can be environment or deployment specific, for example, credentials depending on the user who performs the deployment. The MTA extension descriptor is a YAML file that has a similar structure to the deployment descriptor, by following the Multitarget Application Model structure with several limitations and differences. Normally, extension descriptor extends deployment descriptor but it is possible to extends other extension descriptor, making extension descriptors chain. It can add or overwrite existing data if necessary.
+The Multitarget Application \(МТА\) extension descriptor is a YAML file that contains data complementary to the deployment descriptor. The data can be environment or deployment specific, for example, credentials depending on the user who performs the deployment. The MTA extension descriptor is a YAML file that has a similar structure to the deployment descriptor, following the Multitarget Application Model structure with several limitations and differences. Normally, the extension descriptor extends the deployment descriptor but it is possible to extend another extension descriptor, making an extension descriptors chain. It can add or overwrite existing data if necessary.
 
 Several extension descriptors can be additionally used after the initial deployment.
 
 > ### Note:  
-> The format and available options within the extension descriptor may change with newer versions of the MTA specification. You must always specify the schema version option when defining an extension descriptor to inform the SAP BTP which MTA specification version should be used. Furthermore, the schema version used within the extension descriptor and the deployment descriptor should always be same.
+> The format and available options within the extension descriptor may change with newer versions of the MTA specification. You must always specify the schema version option when defining an extension descriptor to inform the SAP BTP which MTA specification version should be used. Furthermore, the schema version used within the extension descriptor and the deployment descriptor should always be the same.
 
 In the examples below, we have a deployment descriptor, which has already been defined, and several extension descriptors.
 
@@ -87,9 +87,9 @@ The example above instructs the SAP BTP to:
 
 You can do the following using an extension descriptor:
 
--   Add a new data in properties and parameters on module level, resource level, provided section level and required section level
+-   Add new data in properties and parameters on module level, resource level, provided section level and required section level
 
--   Overwrite an existing data \(in depth\) in modules, resources, parameters, properties, provides, requires sections. This depends on the parameter or property metadata overwritable. See section 9. Metadata for Properties and Parameters
+-   Overwrite an existing data \(in depth\) in modules, resources, parameters, properties, provides, requires sections. This depends on the parameter or property metadata overwritable. See [Metadata for Properties and Parameters](https://help.sap.com/viewer/65de2977205c403bbc107264b8eccf4b/Cloud/en-US/fca2cedcb79649e7a8f51234faea1142.html "It is possible to declare metadata for parameters and properties defined in the MTA deployment description, for example, using the "parameters-metadata:" or "properties-metadata:" keys, respectively; the mapping is based on the keys defined for a parameter or property.") :arrow_upper_right:.
 
 -   As of schema version 3.xx, by default parameters and properties are overwritable and optional. If you want to make a certain parameter or property non-overwritable or required, you need to add specific metadata. See [Metadata for Properties and Parameters](https://help.sap.com/viewer/65de2977205c403bbc107264b8eccf4b/Cloud/en-US/fca2cedcb79649e7a8f51234faea1142.html "It is possible to declare metadata for parameters and properties defined in the MTA deployment description, for example, using the "parameters-metadata:" or "properties-metadata:" keys, respectively; the mapping is based on the keys defined for a parameter or property.") :arrow_upper_right:.
 
@@ -98,6 +98,8 @@ You cannot use an extension descriptor to:
 -   Add new entities such as modules or resources
 -   Change module or resource type
 -   Alter read-only \(system\) parameters
+-   Add new provided or required dependencies
+-   Change the processing order of modules and resources with `deployed-after` and `processed-after` parameters
 
 **Related Information**  
 

docs/30-development-neo/defining-multitarget-application-archives-6a5c888.md

@@ -23,7 +23,7 @@ An MTA archive consists of the following:
 
 > ### Note:  
 > -   The MTA extension descriptor is not part of the MTA archive. During deployment you provide it as a separate file, or as parameters you enter manually when the SAP BTP requests them.
-> -   Using a `resources` directory as in some examples is not mandatory. You can store the necessary resource files on root level of the MTA archive, or in another directory with name of your choice.
+> -   Using a `resources` directory, as shown in some examples, is not mandatory. You can store the necessary resource files on root level of the MTA archive, or in another directory with name of your choice.
 
 The following example shows the basic structure of an MTA archive. It contains a Java application `.war` file and a `META-INF` directory, which contains an MTA deployment descriptor with a module and a `MANIFEST.MF` file.
 
@@ -73,7 +73,7 @@ The example above instructs the SAP BTP to:
 **Related Information**  
 
 
-[https://sap.github.io/cloud-mta-build-tool/](https://sap.github.io/cloud-mta-build-tool/)
+[Cloud MTA Build Tool](https://sap.github.io/cloud-mta-build-tool/)
 
 [The Multitarget Application Model v.2](http://go.sap.com/documents/2016/06/e2f618e4-757c-0010-82c7-eda71af511fa.html)
 

docs/50-administration-and-ops-neo/create-a-subaccount-c48c298.md

@@ -67,7 +67,7 @@ You create subaccounts in your global account. Once you create a new subaccount,
     > 
     > You can change your selection at any time by editing the subaccount properties. Do not select this option if your account is used for non-production purposes, such as development, testing, and demos.
 
-8.  **Optional:** To use beta services and applications in the subaccount, select *Enable beta features*.
+8.  **Optional:** To use beta services and applications in the current subaccount, select *Enable beta features*.
 
     > ### Caution:  
     > You shouldn't use SAP BTP beta features in subaccounts that belong to productive enterprise accounts. For more information, see [Important Disclaimers and Legal Information](https://help.sap.com/viewer/disclaimer).
@@ -157,7 +157,7 @@ You create subaccounts in your global account. Once you create a new subaccount,
     > 
     > You can change your selection at any time by editing the subaccount properties. Do not select this option if your account is used for non-production purposes, such as development, testing, and demos.
 
-9.  **Optional:** To use beta services and applications in the subaccount, under *Advanced*, select *Enable beta features*.
+9.  **Optional:** To use beta services and applications in the current subaccount, under *Advanced*, select *Enable beta features*.
 
     > ### Caution:  
     > You shouldn't use SAP BTP beta features in subaccounts that belong to productive enterprise accounts. For more information, see [Important Disclaimers and Legal Information](https://help.sap.com/viewer/disclaimer).

docs/50-administration-and-ops-neo/download-and-start-using-the-btp-cli-client-8a8f17f.md

@@ -17,13 +17,15 @@ The client is available for 64-bit versions of the following operating systems:
 -   Linux \(amd64 and arm64\)
 
 
-Each released client version is supported for at least a year. If a client is deprecated, you are notified six months before it stops working in the [What's New for SAP Business Technology Platform](https://help.sap.com/whats-new/cf0cb2cb149647329b5d02aa96303f56?Component=SAP%20BTP%20Command%20Line%20Interface&locale=en-US&version=Cloud) page on SAP Help Portal \(filter for *SAP BTP Command Line Interface\)* as well as in the client itself. Most of the updates to the btp CLI don't require a new client installation, but are made available through updates of the btp CLI server, so that you can use them in your installed version of the client.
+Each client version is supported for at least a year and most of the updates to the btp CLI don't require a new client installation, but are made available through the btp CLI server, so that you can use them in your installed version of the client. However, to make sure you don't miss any new features or security updates, we recommend to regularly update the client anyways.
+
+In the [What's New for SAP Business Technology Platform](https://help.sap.com/whats-new/cf0cb2cb149647329b5d02aa96303f56?Component=SAP%20BTP%20Command%20Line%20Interface&locale=en-US&version=Cloud) page on SAP Help Portal \(filtered for *SAP BTP Command Line Interface\)* we inform about new features, client releases, as well about client deprecations and discontinuations.
 
 
 
 ## Procedure
 
-1.  Download the appropriate client for your operating system from [SAP Development Tools](https://tools.hana.ondemand.com/#cloud-btpcli) or use the links in the table below. They are tar.gz archives that contain one executable file.
+1.  Download the appropriate client for your operating system from [SAP Development Tools](https://tools.hana.ondemand.com/#cloud-btpcli) with the links in the able below. If you prefer using the the command line or a script, you can use the curl command from the table below, which downloads and saves the latest client version to your computer and accepts the SAP Developer Agreement \(EULA\).
 
 
     <table>
@@ -35,7 +37,12 @@ Each released client version is supported for at least a year. If a client is de
     </th>
     <th valign="top">
 
-    Link to latest version
+    Link to Latest Version
+
+    </th>
+    <th valign="top">
+
+    curl Command to Download Latest version
 
     </th>
     </tr>
@@ -49,6 +56,15 @@ Each released client version is supported for at least a year. If a client is de
 
     [amd64](https://tools.hana.ondemand.com/additional/btp-cli-windows-amd64-latest.tar.gz) 
 
+    </td>
+    <td valign="top">
+
+    ```
+    curl -LJO https://tools.hana.ondemand.com/additional/btp-cli-windows-amd64-latest.tar.gz --cookie "eula_3_1_agreed=tools.hana.ondemand.com/developer-license-3_1.txt"
+    ```
+
+
+
     </td>
     </tr>
     <tr>
@@ -61,6 +77,19 @@ Each released client version is supported for at least a year. If a client is de
 
     [amd64](https://tools.hana.ondemand.com/additional/btp-cli-darwin-amd64-latest.tar.gz) | [arm64](https://tools.hana.ondemand.com/additional/btp-cli-darwin-arm64-latest.tar.gz) 
 
+    </td>
+    <td valign="top">
+
+    ```
+    curl -LJO https://tools.hana.ondemand.com/additional/btp-cli-darwin-amd64-latest.tar.gz --cookie "eula_3_1_agreed=tools.hana.ondemand.com/developer-license-3_1.txt"
+    ```
+
+    ```
+    curl -LJO https://tools.hana.ondemand.com/additional/btp-cli-darwin-arm64-latest.tar.gz --cookie "eula_3_1_agreed=tools.hana.ondemand.com/developer-license-3_1.txt"
+    ```
+
+
+
     </td>
     </tr>
     <tr>
@@ -73,6 +102,19 @@ Each released client version is supported for at least a year. If a client is de
 
     [amd64](https://tools.hana.ondemand.com/additional/btp-cli-linux-amd64-latest.tar.gz) | [arm64](https://tools.hana.ondemand.com/additional/btp-cli-linux-arm64-latest.tar.gz) 
 
+    </td>
+    <td valign="top">
+
+    ```
+    curl -LJO https://tools.hana.ondemand.com/additional/btp-cli-linux-amd64-latest.tar.gz --cookie "eula_3_1_agreed=tools.hana.ondemand.com/developer-license-3_1.txt"
+    ```
+
+    ```
+    curl -LJO https://tools.hana.ondemand.com/additional/btp-cli-linux-arm64-latest.tar.gz --cookie "eula_3_1_agreed=tools.hana.ondemand.com/developer-license-3_1.txt"
+    ```
+
+
+
     </td>
     </tr>
     </table>

docs/50-administration-and-ops-neo/get-updates-e92aa78.md

@@ -10,15 +10,15 @@ Updating the btp CLI client is essentially replacing the old executable file wit
 
 ## Context
 
-Each btp CLI client version is supported for at least a year after its release. The [What's New for SAP Business Technology Platform](https://help.sap.com/whats-new/cf0cb2cb149647329b5d02aa96303f56?Component=SAP%20BTP%20Command%20Line%20Interface&locale=en-US&version=Cloud) page on SAP Help Portal announces new features and informs you if you need a client update to use them. In addition, the client itself displays a message if you need an update.
+Each btp CLI client version is supported for at least a year after its release, but we recommend to regularly update the client. This way, you ensure not to miss any new features or security updates. The [What's New for SAP Business Technology Platform](https://help.sap.com/whats-new/cf0cb2cb149647329b5d02aa96303f56?Component=SAP%20BTP%20Command%20Line%20Interface&locale=en-US&version=Cloud) page on SAP Help Portal announces new features and informs you if you need a client update to use them. If your client version is deprecated, an update hint is displayed in the client as well.
 
 To find out the version of the CLI client you are using, run `btp --info` or simply `btp`.
 
 
 
 ## Procedure
 
-1.  Get the latest version using the download links at: [https://tools.hana.ondemand.com/\#cloud-cpcli](https://tools.hana.ondemand.com/#cloud-cpcli).
+1.  Get the latest version using the download links in the table in [Download and Start Using the btp CLI Client](download-and-start-using-the-btp-cli-client-8a8f17f.md).
 
 2.  Extract the client file \(for example: `btp.exe`\) and replace the old file with this new one.