OpenUI5 Documentation Update 24.04.2025

Author: openui5bot

docs/02_Read-Me-First/deprecated-themes-and-libraries-a87ca84.md

@@ -49,7 +49,7 @@ Recommendation\(\*\)
 </td>
 <td valign="top">
 
- 
+1.136
 
 </td>
 <td valign="top">
@@ -71,7 +71,7 @@ Switch to `sap_horizon`.
 </td>
 <td valign="top">
 
- 
+1.136
 
 </td>
 <td valign="top">
@@ -93,7 +93,7 @@ Switch to `sap_horizon_hcb`.
 </td>
 <td valign="top">
 
- 
+1.136
 
 </td>
 <td valign="top">

docs/02_Read-Me-First/supported-combinations-of-themes-and-libraries-38ff8c2.md

@@ -8,7 +8,7 @@ This chapter gives an overview of the possible combinations of themes and librar
 
 ### Active Libraries
 
-The following table shows the [Available Themes](../04_Essentials/available-themes-da0d2e7.md) for the active OpenUI5 libraries.Even though the `sap_belize`, `sap_bluecrystal`, and the `sap_hcb` themes are now deprecated, they currently are still available, but will not be maintained. We recommend that you migrate your existing apps to the supported themes.
+The following table shows the [Available Themes](../04_Essentials/available-themes-da0d2e7.md) for the active OpenUI5 libraries.
 
 > ### Note:  
 > For more information about the *Quartz Dark* theme, see SAP Note [2982978](https://me.sap.com/notes/2982978).
@@ -607,11 +607,7 @@ n/a
 
 ### Deprecated Libraries
 
-Should you decide to ignore the deprecation of libraries and continue, for example, using `sap.ui.commons` and `sap.ui.ux3`, we recommend you use the `sap_bluecrystal` or `sap_belize` theme.
-
-The `sap_bluecrystal` theme is also no longer supported, but offers full coverage of the `sap.ui.commons` and the `sap.ui.ux3` library. It is currently still shipped, **but will be removed in one of the next versions.**
-
-The `sap_belize` theme offers an initial implementation for the `sap.ui.commons` and the `sap.ui.ux3` libraries to allow for a smoother transition, but it is not supported for this library and will not be maintained. We recommend that you consider migrating your existing apps to actively developed libraries, such as `sap.m`, and use the most current theme as the default theme going forward.
+If you are, for example, still using `sap.ui.commons` and `sap.ui.ux3`, we recommend that you migrate your existing apps to actively developed libraries, such as `sap.m`, and use the most current theme as the default theme going forward.
 
 The following table shows how the available themes interact with the `sap.ui.commons` and the `sap.ui.ux3` libraries:
 
@@ -674,6 +670,11 @@ The following table shows how the available themes interact with the `sap.ui.com
 
 1.120
 
+</th>
+<th valign="top">
+
+1.136
+
 </th>
 </tr>
 <tr>
@@ -731,6 +732,11 @@ n/a
 
 ![Not Supported](images/loiod355123503654aae97106b021020b7be_LowRes.png)
 
+</td>
+<td valign="top">
+
+![Not Supported](images/loiod355123503654aae97106b021020b7be_LowRes.png)
+
 </td>
 </tr>
 <tr>
@@ -788,6 +794,11 @@ n/a
 
 ![Not Supported](images/loiod355123503654aae97106b021020b7be_LowRes.png)
 
+</td>
+<td valign="top">
+
+![Not Supported](images/loiod355123503654aae97106b021020b7be_LowRes.png)
+
 </td>
 </tr>
 <tr>
@@ -847,6 +858,11 @@ n/a
 
 ![Not Supported](images/loiod355123503654aae97106b021020b7be_LowRes.png)
 
+</td>
+<td valign="top">
+
+![Not Supported](images/loiod355123503654aae97106b021020b7be_LowRes.png)
+
 </td>
 </tr>
 <tr>
@@ -904,6 +920,11 @@ n/a
 
 ![Not Supported](images/loiod355123503654aae97106b021020b7be_LowRes.png)
 
+</td>
+<td valign="top">
+
+![Not Supported](images/loiod355123503654aae97106b021020b7be_LowRes.png)
+
 </td>
 </tr>
 <tr>
@@ -961,6 +982,11 @@ n/a
 
 ![Not Supported](images/loiod355123503654aae97106b021020b7be_LowRes.png)
 
+</td>
+<td valign="top">
+
+![Not Supported](images/loiod355123503654aae97106b021020b7be_LowRes.png)
+
 </td>
 </tr>
 <tr>
@@ -1020,6 +1046,11 @@ n/a
 
 ![Not Supported](images/loiod355123503654aae97106b021020b7be_LowRes.png)
 
+</td>
+<td valign="top">
+
+![Not Supported](images/loiod355123503654aae97106b021020b7be_LowRes.png)
+
 </td>
 </tr>
 <tr>
@@ -1079,6 +1110,11 @@ n/a
 
 ![Deprecated](images/loio3ea53dcd3acc4783a7a4b83e10c8f1aa_LowRes.gif)
 
+</td>
+<td valign="top">
+
+![Removed](images/loio5befb5af20ed42fd9052a99014d953a3_LowRes.gif)
+
 </td>
 </tr>
 <tr>
@@ -1138,6 +1174,11 @@ n/a
 
 ![Deprecated](images/loio3ea53dcd3acc4783a7a4b83e10c8f1aa_LowRes.gif)
 
+</td>
+<td valign="top">
+
+![Removed](images/loio5befb5af20ed42fd9052a99014d953a3_LowRes.gif)
+
 </td>
 </tr>
 <tr>
@@ -1195,6 +1236,11 @@ n/a
 
 ![Deprecated](images/loio3ea53dcd3acc4783a7a4b83e10c8f1aa_LowRes.gif)
 
+</td>
+<td valign="top">
+
+![Removed](images/loio5befb5af20ed42fd9052a99014d953a3_LowRes.gif)
+
 </td>
 </tr>
 <tr>
@@ -1252,6 +1298,11 @@ n/a
 
 ![Deprecated](images/loio3ea53dcd3acc4783a7a4b83e10c8f1aa_LowRes.gif)
 
+</td>
+<td valign="top">
+
+![Removed](images/loio5befb5af20ed42fd9052a99014d953a3_LowRes.gif)
+
 </td>
 </tr>
 <tr>
@@ -1309,6 +1360,11 @@ n/a
 
 ![Removed](images/loio5befb5af20ed42fd9052a99014d953a3_LowRes.gif)
 
+</td>
+<td valign="top">
+
+![Removed](images/loio5befb5af20ed42fd9052a99014d953a3_LowRes.gif)
+
 </td>
 </tr>
 <tr>
@@ -1366,6 +1422,11 @@ n/a
 
 ![Removed](images/loio5befb5af20ed42fd9052a99014d953a3_LowRes.gif)
 
+</td>
+<td valign="top">
+
+![Removed](images/loio5befb5af20ed42fd9052a99014d953a3_LowRes.gif)
+
 </td>
 </tr>
 <tr>
@@ -1423,6 +1484,11 @@ n/a
 
 ![Removed](images/loio5befb5af20ed42fd9052a99014d953a3_LowRes.gif)
 
+</td>
+<td valign="top">
+
+![Removed](images/loio5befb5af20ed42fd9052a99014d953a3_LowRes.gif)
+
 </td>
 </tr>
 </table>

docs/03_Get-Started/images/loio016d473029e04ec9be5ed43fa897e69b_HiRes.png

@@ -14,7 +14,7 @@ In this step, we set up the initial app.
 
 **The worklist app**
 
-![](images/loio60e42c87d9494360a64017fc16d8bbcb_HiRes.png "The worklist app")
+![](images/loio60e42c87d9494360a64017fc16d8bbcb_LowRes.png "The worklist app")
 
 
 
@@ -43,7 +43,7 @@ With the downloaded code from the Demo Kit, you have an initial app structure wi
 
 **Folder structure of the initial project**
 
-![](images/loio7f6899e87d8240d5bd3fc8594e148714_HiRes.png "Folder structure of the initial project")
+![](images/loio7f6899e87d8240d5bd3fc8594e148714_LowRes.png "Folder structure of the initial project")
 
 -   **Home Page** \(`webapp/view/Worklist.view.xml` file\)
 

docs/03_Get-Started/images/loio016d473029e04ec9be5ed43fa897e69b_LowRes.png

@@ -12,13 +12,13 @@ In this step, we want to change the mock data of the initial app.
 
 **The product list of the initial app with custom mock data**
 
-![](images/loiob150a14f277b4d5398442829edc83217_HiRes.png "The product list of the initial app with custom mock data")
+![](images/loiob150a14f277b4d5398442829edc83217_LowRes.png "The product list of the initial app with custom mock data")
 
 
 
 **Folder structure for this step including custom mock data**
 
-![](images/loiofa4aba84cedc4fefbf345c26eed8bc97_HiRes.png " Folder structure for this step including custom mock data")
+![](images/loiofa4aba84cedc4fefbf345c26eed8bc97_LowRes.png " Folder structure for this step including custom mock data")
 
 The service metadata only contains a description of the service entities. The mock server that is part of the app will auto-generate random mock data based on the data types defined in the metadata file. To have a more realistic development environment we will now add additional sample data.
 

docs/03_Get-Started/images/loio2def9d9de16f4b4a87dd4342486c70f7_HiRes.png

@@ -12,7 +12,7 @@ In this step, we will edit the worklist table to include additional columns for
 
 **The improved worklist table with new columns and formatting**
 
-![](images/loio2def9d9de16f4b4a87dd4342486c70f7_HiRes.png "The improved worklist table with new columns and formatting")
+![](images/loio2def9d9de16f4b4a87dd4342486c70f7_LowRes.png "The improved worklist table with new columns and formatting")
 
 
 

docs/03_Get-Started/images/loio2def9d9de16f4b4a87dd4342486c70f7_LowRes.png

@@ -12,7 +12,7 @@ For easily detecting and managing product shortages in our app, we will add a qu
 
 **A quick filter allows filtering the product table**
 
-![](images/loio395f8acac5fd4fbc9a1c52c615fa07d3_HiRes.png "A quick filter allows filtering the product table")
+![](images/loio395f8acac5fd4fbc9a1c52c615fa07d3_LowRes.png "A quick filter allows filtering the product table")
 
 
 

docs/03_Get-Started/images/loio395f8acac5fd4fbc9a1c52c615fa07d3_HiRes.png

@@ -12,7 +12,7 @@ Now we can easily spot shortages on our stock, but we would also like to take ac
 
 **Actions are now available in the footer bar**
 
-![](images/loio016d473029e04ec9be5ed43fa897e69b_HiRes.png "Actions are now available in the footer bar")
+![](images/loio016d473029e04ec9be5ed43fa897e69b_LowRes.png "Actions are now available in the footer bar")
 
 
 

docs/03_Get-Started/images/loio395f8acac5fd4fbc9a1c52c615fa07d3_LowRes.png

@@ -12,7 +12,7 @@ In this step, we will extend the detail page of our app to show more information
 
 **Detail page with more product information**
 
-![](images/loio49780e41de4e4766b41cdf65acf81ea2_HiRes.png "Detail page with more product information")
+![](images/loio49780e41de4e4766b41cdf65acf81ea2_LowRes.png "Detail page with more product information")
 
 
 

docs/03_Get-Started/images/loio49780e41de4e4766b41cdf65acf81ea2_HiRes.png

@@ -12,7 +12,7 @@ In this step, we extend the product detail view by adding a feature allowing to
 
 **Comments section added to the detail page**
 
-![](images/loioa517fe596aa04b4d8d080fbf6168cf40_HiRes.png "Comments section added to the detail page")
+![](images/loioa517fe596aa04b4d8d080fbf6168cf40_LowRes.png "Comments section added to the detail page")
 
 
 

docs/03_Get-Started/images/loio49780e41de4e4766b41cdf65acf81ea2_LowRes.png

@@ -25,13 +25,13 @@ We will use the worklist template as a starting point for this tutorial and add
 
 **Start page of the app with list of products and actions**
 
-![](images/loio016d473029e04ec9be5ed43fa897e69b_HiRes.png "Start page of the app with list of products and actions")
+![](images/loio016d473029e04ec9be5ed43fa897e69b_LowRes.png "Start page of the app with list of products and actions")
 
 
 
 **Product detail page of the app**
 
-![](images/loioa517fe596aa04b4d8d080fbf6168cf40_HiRes.png "Product detail page of the app")
+![](images/loioa517fe596aa04b4d8d080fbf6168cf40_LowRes.png "Product detail page of the app")
 
 
 

docs/03_Get-Started/images/loio60e42c87d9494360a64017fc16d8bbcb_HiRes.png

@@ -178,13 +178,13 @@ The check function has three main and one optional parameters. The main ones are
 
 -   `oCoreFacade` - gives you access to the different elements provided by the OpenUI5 core framework:
 
-    -   <code><a href="https://ui5.sap.com/#/api/sap.ui.base.Object/methods/getMetadata">getMetadata()</a></code>
+    -   <code><a href="https://ui5.sap.com/#/api/sap.ui.support.CoreFacade%23methods/getMetadata">getMetadata()</a></code>
 
-    -   <code><a href="https://ui5.sap.com/#/api/sap.ui.core.Core/methods/getUIArea">getUIAreas()</a></code>
+    -   <code><a href="https://ui5.sap.com/#/api/sap.ui.support.CoreFacade%23methods/getUIAreas">getUIAreas()</a></code>
 
-    -   <code><a href="https://ui5.sap.com/#/api/sap.ui.core.Core/methods/getComponent">getComponents()</a></code>
+    -   <code><a href="https://ui5.sap.com/#/api/sap.ui.support.CoreFacade%23methods/getComponents">getComponents()</a></code>
 
-    -   <code><a href="https://ui5.sap.com/#/api/sap.ui.core.Core/methods/getModel">getModels()</a></code>
+    -   <code><a href="https://ui5.sap.com/#/api/sap.ui.support.CoreFacade%23methods/getModels">getModels()</a></code>
 
 
 -   `oScope` - retrieves elements in the scope with the following methods:
@@ -223,24 +223,25 @@ The check function has three main and one optional parameters. The main ones are
     ```js
     
     function(issueManager, oCoreFacade, oScope) {
-      var mElements = oScope.getElements({
-        type: "sap.m.Input",
-        public: true,
-        cloned: false
-      });
-      for (var n in mElements) {
-        var oElement = mElements[n];
-        if (!oElement.getParent()) {
-          issueManager.addIssue({
-            severity: sap.ui.support.Severity.Medium,
-            details: "The element " + oElement.getId() + " has no parent.",
-            context: {
-              id: oElement.getId()
-            }
-          });
+        var mElements = oScope.getElements({
+            type: "sap.m.Input",
+            public: true,
+            cloned: false
+        });
+    
+        for (var n in mElements) {
+            var oElement = mElements[n];
     
+            if (!oElement.getParent()) {
+                issueManager.addIssue({
+                    severity: Severity.Medium, // Severity enum is taken from "sap/ui/support/library" import
+                    details: "The element " + oElement.getId() + " has no parent.",
+                    context: {
+                        id: oElement.getId()
+                    }
+                });
+            }
         }
-      }
     }
     
     ```

docs/03_Get-Started/images/loio60e42c87d9494360a64017fc16d8bbcb_LowRes.png

@@ -1,14 +1,14 @@
 <!-- loio0635156f3950494885ca314a13e15e29 -->
 
-## Enabling the Automatic Header Adaptation in the Manifest
+## Enabling the Automatic Header Adaptation for Legacy Applications
 
 Application developers can enable automatic adaptation of legacy applications from the `manifest.json` file also known as descriptor for applications, components and libraries.
 
 
 
 ### The Automatic Header Adapter
 
-The SAP Fiori design guidelines require changes with regards to the headers of applications and the SAP Fiori launchpad. If your application has a header, it needs to be merged into the standardized SAP Fiori header.
+The SAP Fiori design guidelines provide recommendations with regards to the headers of applications and the SAP Fiori launchpad. If your application has a header, it needs to be merged into the standardized SAP Fiori header.
 
 Legacy applications using the `sap.m.Page`, including the back button, can use the header adapter to align their header layout with SAP Fiori design guidelines. The header adapter specifically prevents duplicate headers and back buttons when displaying these legacy applications in the SAP Fiori launchpad.
 

docs/03_Get-Started/images/loio7f6899e87d8240d5bd3fc8594e148714_HiRes.png

@@ -5,7 +5,7 @@
 The `sap.ui.model.odata.v4.ODataModel` is the model implementation for consuming an OData V4 service.
 
 > ### Note:  
-> Instead of smart controls \(`sap.ui.comp` library\) or `sap.ui.table.AnalyticalTable` \(or analytical table scenarios\) the SAP Fiori elements building blocks \(`sap.fe.macros`\) have to be used with the OpenUI5 OData V4 model. The `TreeTable` is not supported together with the OpenUI5 OData V4 model.
+> Instead of smart controls \(`sap.ui.comp` library\) or `sap.ui.table.AnalyticalTable` \(or analytical table scenarios\) the SAP Fiori elements building blocks \(`sap.fe.macros`\) have to be used with the OpenUI5 OData V4 model.
 > 
 > The interface for applications has been changed for an easier and more efficient use of the model. For a summary of these changes, see [Changes Compared to OData V2 Model](changes-compared-to-odata-v2-model-abd4d7c.md).