-Enable "Include Item In Selection" for tables.
+Enable *Include Item In Selection* for tables.
By setting this property to true, the item selection is displayed even if a user navigates away from a table.
diff --git a/docs/06_SAP_Fiori_Elements/adding-a-section-to-an-object-page-a357047.md b/docs/06_SAP_Fiori_Elements/adding-a-section-to-an-object-page-a357047.md
index 1ba7b698..357c68d7 100644
--- a/docs/06_SAP_Fiori_Elements/adding-a-section-to-an-object-page-a357047.md
+++ b/docs/06_SAP_Fiori_Elements/adding-a-section-to-an-object-page-a357047.md
@@ -18,7 +18,7 @@ You can add an additional section to your object page, as described below.
For this example, you want to add a section called *Product Description* to the object page of the *Manage Products* app.
> ### Note:
-> This documentation describes how to manually define extensions. The following video provides an example for how to create a section extension on the object page using the extension wizard:
+> We've removed videos showing step-by-step procedures using SAP Web IDE, which SAP no longer actively supports. You can still access the video using an older version of this document.
diff --git a/docs/06_SAP_Fiori_Elements/adding-actions-to-tables-b623e0b.md b/docs/06_SAP_Fiori_Elements/adding-actions-to-tables-b623e0b.md
index 646b99cf..ab330e01 100644
--- a/docs/06_SAP_Fiori_Elements/adding-actions-to-tables-b623e0b.md
+++ b/docs/06_SAP_Fiori_Elements/adding-actions-to-tables-b623e0b.md
@@ -114,7 +114,7 @@ The system gives priority to the `Org.OData.Capabilities.V1.NavigationRestrictio
> );
> ```
-For more information, see [Enabling Inline Creation Mode or Empty Rows Mode for Table Entries](enabling-inline-creation-mode-or-empty-rows-mode-for-table-entries-cfb04f0.md).
+For more information, see [Enabling Inline Creation Mode or Empty Row Mode for Table Entries](enabling-inline-creation-mode-or-empty-row-mode-for-table-entries-cfb04f0.md).
@@ -560,6 +560,133 @@ The following code sample shows you how to hide or show the *Delete* button, dep
+### Defining the Order of Standard Actions
+
+Application developers can define the order of standard actions in the table toolbar. The developer must define the properties, `anchor` and `position` for each action corresponding to the action key in the manifest. The following table shows the keys and the corresponding standard actions:
+
+
+
+
+|
+
+Key
+
+
+
+ |
+
+
+Standard Action
+
+
+
+ |
+
+
+|
+
+`Create`
+
+
+
+ |
+
+
+`StandardAction::Create`
+
+
+
+ |
+
+
+|
+
+`Delete`
+
+
+
+ |
+
+
+`StandardAction::Delete`
+
+
+
+ |
+
+
+|
+
+`MassEdit`
+
+
+
+ |
+
+
+`StandardAction::MassEdit`
+
+
+
+ |
+
+
+|
+
+`Delete`
+
+
+
+ |
+
+
+`StandardAction::'Insights'`
+
+
+
+ |
+
+
+
+> ### Sample Code:
+> ```
+> { "sap.ui5": {
+> "routing": {
+> "targets": {
+> "SalesOrderManageList": {
+> "options": {
+> "settings": {
+> "controlConfiguration": {
+> "@com.sap.vocabularies.UI.v1.LineItem": {
+> "actions": { "StandardAction::Delete": {
+> "visible": false,
+> "position": {
+> "anchor": "StandardAction::Create",
+> "placement": "Before"
+> }
+> },
+> "CustomAction": {
+> "press": "SalesOrder.custom.CustomActions.CustomAction1",
+> "enabled": true, "text": "Custom Action",
+> "command": "COMMON", "position": {
+> "anchor": "StandardAction::Create",
+> "placement": "After"
+> }
+> }
+> }
+> }
+> }
+> }
+> }
+> }
+> }
+> }
+> }
+> }
+> ```
+
+
+
### Enabling the `Update` or `Delete` Feature for the Table
Application developers can control the editability of table fields using `UpdateRestrictions`.
diff --git a/docs/06_SAP_Fiori_Elements/building-an-app-9834a0a.md b/docs/06_SAP_Fiori_Elements/building-an-app-9834a0a.md
index f0f8333c..a6e3e87d 100644
--- a/docs/06_SAP_Fiori_Elements/building-an-app-9834a0a.md
+++ b/docs/06_SAP_Fiori_Elements/building-an-app-9834a0a.md
@@ -4,7 +4,7 @@
You now have an option to build UI applications by using SAP Fiori elements.
-You can use [SAP Fiori tools](https://help.sap.com/viewer/product/SAP_FIORI_tools/Latest/en-US), which is a set of extensions for SAP Business Application Studio and Visual Studio Code, to build your apps.
+You can build your apps using [SAP Fiori tools](https://help.sap.com/viewer/product/SAP_FIORI_tools/Latest/en-US), which is a set of extensions for SAP Business Application Studio and Visual Studio Code.
-For more information about creating apps using SAP Fiori tools, see the detailed procedure mentioned in the following section.
+For more information on creating apps using SAP Fiori tools, see the detailed procedures mentioned in this section.
diff --git a/docs/06_SAP_Fiori_Elements/changing-navigation-to-object-page-8bd546e.md b/docs/06_SAP_Fiori_Elements/changing-navigation-to-object-page-8bd546e.md
index a93dd8ea..87eb6850 100644
--- a/docs/06_SAP_Fiori_Elements/changing-navigation-to-object-page-8bd546e.md
+++ b/docs/06_SAP_Fiori_Elements/changing-navigation-to-object-page-8bd546e.md
@@ -113,16 +113,17 @@ You can define an external navigation using intent-based navigation in the `mani
> ```json
> {
> …
-> "sap.app": {
-> "crossNavigation": {
-> "outbounds": {
-> "ProductDetails": {
-> "semanticObject": "ProductDetails",
-> "action": "manage"
-> }
-> }
-> }
-> },
+> …
+> "sap.app": {
+> "crossNavigation": {
+> "outbounds": {
+> "ProductDetails": {
+> "semanticObject": "ProductDetails",
+> "action": "manage"
+> }
+> }
+> }
+> },
> "sap.ui5": {
> ....
> ....
diff --git a/docs/06_SAP_Fiori_Elements/checking-folder-structure-and-project-artifacts-f7abd1b.md b/docs/06_SAP_Fiori_Elements/checking-folder-structure-and-project-artifacts-f7abd1b.md
index 799af619..df2ca343 100644
--- a/docs/06_SAP_Fiori_Elements/checking-folder-structure-and-project-artifacts-f7abd1b.md
+++ b/docs/06_SAP_Fiori_Elements/checking-folder-structure-and-project-artifacts-f7abd1b.md
@@ -2,9 +2,14 @@
# Checking Folder Structure and Project Artifacts
-Once you've applied the template, the generated application is ready to run.
+Once the generation is complete and the node modules have been installed, the application is ready to run.
-The new app or component reuses the views and controllers from `sap.suite.ui.generic.template`. You can find the destinations in the `neo-app.json` file. The resource links and route definitions for navigation are in the app descriptor file \(`manifest.json`\).
+> ### Note:
+> This topic is currently only applicable to SAP Fiori elements for OData V2.
+
+The new app or component reuses the views and controllers from `sap.suite.ui.generic.template`. The resource links and route definitions for navigation are in the app descriptor file \(`manifest.json`\). You can find the destination configuration for preview in the `ui5*.yaml` files.
+
+You can use the run configurations \(palette command `Fiori: Open Run Configurations`\) to adapt the destinations for preview
The following artifacts are generated:
@@ -12,7 +17,9 @@ The following artifacts are generated:
**Folder Structure for List Report and Object Page**
- 
+ 
+
+For more information on generated files, see the **Projects** section of [https://help.sap.com/docs/SAP\_FIORI\_tools/17d50220bcd848aa854c9c182d65b699/db44d45051794d778f1dd50def0fa267.html](https://help.sap.com/docs/SAP_FIORI_tools/17d50220bcd848aa854c9c182d65b699/db44d45051794d778f1dd50def0fa267.html)
@@ -23,8 +30,6 @@ After you generate the application, the SAPUI5 component `Component.js` that rep
> ### Caution:
> Don't edit or change this file.
-The generated app uses the reuse component controller by referencing a template that uses transactional processing including draft-save. Similarly, the generated app uses the generic view in the template's folder, which is based on the [XML templating](../04_Essentials/xml-templating-5ee619f.md) approach.
-
## manifest.json
@@ -35,49 +40,10 @@ Here, the annotations are read using the catalog service of SAP Gateway. This is
The local resources `localService/metadata.xml` and `localService/SEPMRA_PROD_MAN_ANNO_MDL.xml` are generated for local tests that want to simulate back-end access.
-Besides, the annotations that are retrieved from the back-end system, the local resource `annotations.xml` plays a role at runtime, as this file contains the facet descriptions for the object page. This is where you've to maintain the labels for the different facets.
+If the local `annotations.xml` is defined, it takes the precedence over the annotations from back-end.
We recommend that you use i18n properties, for example, to maintain the texts in the related `i18n` resource file. For more information, see [Localization of UI Texts](localization-of-ui-texts-b8cb649.md).
> ### Note:
-> - You can use the annotation modeler to maintain `UI.facets`.
->
-> For more information, search for *Annotation Modeler* in the documentation for SAP Web IDE on the SAP Help Portal at [https://help.sap.com/viewer/p/SAP\_Web\_IDE](https://help.sap.com/viewer/p/SAP_Web_IDE).
->
-> We recommend that you use only the manifest properties specified there.
->
-> - You can define the subtitle and the application icon to display on the shell bar navigation menu in the `manifest.json` file. For more information, see [Descriptor for Applications, Components, and Libraries \(manifest.json\)](../04_Essentials/descriptor-for-applications-components-and-libraries-manifest-json-be0cf40.md).
-
-
-
-## Neo-app.json
-
-You can find the routing information in the `neoapp.json` file that is based on the destination you've chosen:
-
-```
-{
- "welcomeFile": "index.html",
- "routes": [
- {
- "path": "/sap/opu/odata",
- "target": {
- "type": "destination",
- "name": "",
- "entryPath": "/sap/opu/odata"
- },
- "description": ""
- },
- {
- "path": "/sap/bc/lrep",
- "target": {
- "type": "destination",
- "name": "",
- "entryPath": "/sap/bc/lrep"
- },
- "description": ""
- },
-
-```
-
-You can adapt the destinations in order to address a different back-end system. This option is also available under *Run Configurations* \> *Advanced Settings*.
+> You can define the subtitle and the application icon to display on the shell bar navigation menu in the `manifest.json` file. For more information, see [Descriptor for Applications, Components, and Libraries \(manifest.json\)](../04_Essentials/descriptor-for-applications-components-and-libraries-manifest-json-be0cf40.md).
diff --git a/docs/06_SAP_Fiori_Elements/configuring-charts-c7c5a82.md b/docs/06_SAP_Fiori_Elements/configuring-charts-c7c5a82.md
index ad826a64..37e5135d 100644
--- a/docs/06_SAP_Fiori_Elements/configuring-charts-c7c5a82.md
+++ b/docs/06_SAP_Fiori_Elements/configuring-charts-c7c5a82.md
@@ -491,7 +491,7 @@ Every object in the `colorPalette` map has two properties `color` \(a color valu
You can configure an analytical card with column stack chart to map the dimension values to specific colors. You can use the configuration mentioned below:
-1. In the card manifest setting, set `bEnableStableColoring` to true.
+1. In the card manifest setting, set `bEnableStableColors` to true.
2. Define the color palette for the dimension. Follow the structure mentioned below:
diff --git a/docs/06_SAP_Fiori_Elements/configuring-filter-fields-f5dcb29.md b/docs/06_SAP_Fiori_Elements/configuring-filter-fields-f5dcb29.md
index 5119527f..96cac739 100644
--- a/docs/06_SAP_Fiori_Elements/configuring-filter-fields-f5dcb29.md
+++ b/docs/06_SAP_Fiori_Elements/configuring-filter-fields-f5dcb29.md
@@ -6,6 +6,30 @@ Application developers can configure filter fields to ensure they only accept ei
+
+
+## Copying and Pasting Multiple Values in the Filter Bar
+
+As an end user, you can copy and paste multiple values in the filter bar in the following use cases:
+
+- From one filter field to another filter field that has the same data type.
+
+- From one filter field to the value help dialog of another field that has the same data type.
+
+- From a spreadsheet to a filter field that has the same data type.
+
+
+For example, you can copy the values from the *Sales Order No.:* field and paste them either to another filter field or a value help that has the same data type. In the value help dialog, paste to the *equal to* field.
+
+ 
+
+> ### Restriction:
+> - Copying and pasting a large number of values into the filter fields can cause performance issues.
+>
+> - For apps with custom filters, the application developers must define the copy event and paste event for the custom filters.
+
+
+
## Additional Features in SAP Fiori Elements for OData V2
@@ -541,7 +565,7 @@ If the annotation holds more than one of these approaches, the filter restrictio
>
> - CityName - MultiValue field since higher priority annotation wins
>
-> - PartnerAddress - MultiValue field. Since this wasn’t defined via a higher priority approach, the lower priority approach persists
+> - PartnerAddress - MultiValue field. Since this wasn’t defined via a higher priority approach, the lower priority approach persists.
diff --git a/docs/06_SAP_Fiori_Elements/copying-and-pasting-from-spreadsheet-applications-to-tables-f6a8fd2.md b/docs/06_SAP_Fiori_Elements/copying-and-pasting-from-spreadsheet-applications-to-tables-f6a8fd2.md
index ebeaf17b..692018de 100644
--- a/docs/06_SAP_Fiori_Elements/copying-and-pasting-from-spreadsheet-applications-to-tables-f6a8fd2.md
+++ b/docs/06_SAP_Fiori_Elements/copying-and-pasting-from-spreadsheet-applications-to-tables-f6a8fd2.md
@@ -61,7 +61,7 @@ In SAP Fiori elements for OData V2, you need to fulfill these prerequisites to u
- The app is draft-enabled.
-- Inline creation is enabled for the object page table. For more information, see [Enabling Inline Creation Mode or Empty Rows Mode for Table Entries](enabling-inline-creation-mode-or-empty-rows-mode-for-table-entries-cfb04f0.md).
+- Inline creation is enabled for the object page table. For more information, see [Enabling Inline Creation Mode or Empty Row Mode for Table Entries](enabling-inline-creation-mode-or-empty-row-mode-for-table-entries-cfb04f0.md).
- The create action is supported in the object page table.
@@ -83,7 +83,7 @@ Sample data:
## Additional Features in SAP Fiori Elements for OData V4
-The paste function is enabled by default on the object page if the creation mode is set to inline or empty rows. For more information, see [Enabling Inline Creation Mode or Empty Rows Mode for Table Entries](enabling-inline-creation-mode-or-empty-rows-mode-for-table-entries-cfb04f0.md).
+The paste function is enabled by default on the object page if the creation mode is set to inline or empty row. For more information, see [Enabling Inline Creation Mode or Empty Row Mode for Table Entries](enabling-inline-creation-mode-or-empty-row-mode-for-table-entries-cfb04f0.md).
diff --git a/docs/06_SAP_Fiori_Elements/creating-cards-for-the-insights-section-of-my-home-in-sap-s-4hana-cloud-9b13559.md b/docs/06_SAP_Fiori_Elements/creating-cards-for-the-insights-section-of-my-home-in-sap-s-4hana-cloud-9b13559.md
index 74d1259b..801e6f11 100644
--- a/docs/06_SAP_Fiori_Elements/creating-cards-for-the-insights-section-of-my-home-in-sap-s-4hana-cloud-9b13559.md
+++ b/docs/06_SAP_Fiori_Elements/creating-cards-for-the-insights-section-of-my-home-in-sap-s-4hana-cloud-9b13559.md
@@ -25,7 +25,9 @@ Once you have enabled *My Home* in SAP S/4HANA Cloud, the *Add Card to Insights*
> ### Note:
> - This feature supports only single view cases that have responsive tables in list report applications.
>
-> - The card creation dialog shows only those columns that are supported for a card.
+> - The card creation dialog shows only those columns that are supported for a card. The card supports single-valued `DataField` based columns. It also supports columns with field values displayed as links such as `DataFieldWithUrl`, semantic links, and `DataField` with `QuickViewFacets`. In addition, SAP Fiori elements for OData V4 also supports `DataFieldWithIntentBasedNavigation` and `DataFieldWithNavigationPath` columns.
+>
+> The excluded columns are image, multi-valued based columns, `FieldGroup` based columns, columns with inline action, columns with navigation button, `DataFieldForAnnotation` based columns \(for contact or address fields\), and custom columns.
Application developers can switch off the option to add cards to *Insights* of *My Home* using the manifest setting.
@@ -110,7 +112,7 @@ To disable the *Add Card to Insights* option in the chart toolbar, add the follo
> ```
> ### Restriction:
-> - When creating an integration card from the list report table, the following changes will not be retained when navigating back from the card: position or visibility of the filter fields, position or visibility of the table columns, and width of the columns.
+> - When creating an integration card from the list report table, the following changes will not be retained when navigating back from the card: the filter fields or table columns that were removed, and change in the position of filter field or table column.
>
> - *Add Card to Insights* option is not available if the list report applications are configured against a parameterized entity.
>
diff --git a/docs/06_SAP_Fiori_Elements/data-points-c2a389a.md b/docs/06_SAP_Fiori_Elements/data-points-c2a389a.md
index a768762a..816861ae 100644
--- a/docs/06_SAP_Fiori_Elements/data-points-c2a389a.md
+++ b/docs/06_SAP_Fiori_Elements/data-points-c2a389a.md
@@ -8,15 +8,14 @@ A data point represents a single point of data. It is typically a number but can
The image below shows the data points *Price* and *Availability* in the object page header.
-
+
**Object Page: DataPoints**
-This video shows the step-by-step procedure for adding a data point header to an object page:
-
-
+> ### Note:
+> We've removed videos showing step-by-step procedures using SAP Web IDE, which SAP no longer actively supports. You can still access the video using an older version of this document.
diff --git a/docs/06_SAP_Fiori_Elements/defining-and-adapting-sections-facfea0.md b/docs/06_SAP_Fiori_Elements/defining-and-adapting-sections-facfea0.md
index 247f36e8..58f57292 100644
--- a/docs/06_SAP_Fiori_Elements/defining-and-adapting-sections-facfea0.md
+++ b/docs/06_SAP_Fiori_Elements/defining-and-adapting-sections-facfea0.md
@@ -168,7 +168,8 @@ You can hide and display sections based on properties.
## Adding a Field Group to a Section
-This video shows the step-by-step procedure for adding a field group to a section on the object page:
+> ### Note:
+> We've removed videos showing step-by-step procedures using SAP Web IDE, which SAP no longer actively supports. You can still access the video using an older version of this document.
For more information, see [Grouping of Fields](grouping-of-fields-7d7a0c4.md).
@@ -185,7 +186,7 @@ To render a table in a section, here's what you do:
2. To render a *Create* button, set `Org.OData.Capabilities.V1.InsertRestrictions/Insertable/Bool` to `true` for the entity set. For more information, see the section **Generic Actions** in [Adding Actions to Tables](adding-actions-to-tables-b623e0b.md).
-See also [Enabling Inline Creation Mode or Empty Rows Mode for Table Entries](enabling-inline-creation-mode-or-empty-rows-mode-for-table-entries-cfb04f0.md).
+See also [Enabling Inline Creation Mode or Empty Row Mode for Table Entries](enabling-inline-creation-mode-or-empty-row-mode-for-table-entries-cfb04f0.md).
diff --git a/docs/06_SAP_Fiori_Elements/descriptor-configuration-for-the-overview-page-f194b41.md b/docs/06_SAP_Fiori_Elements/descriptor-configuration-for-the-overview-page-f194b41.md
index 77036316..d1950cba 100644
--- a/docs/06_SAP_Fiori_Elements/descriptor-configuration-for-the-overview-page-f194b41.md
+++ b/docs/06_SAP_Fiori_Elements/descriptor-configuration-for-the-overview-page-f194b41.md
@@ -12,7 +12,7 @@ The `manifest.json` file defines static information about the application, such
> Descriptor Sample Settings
>
> ```
-> "sap.ovp":
+> "sap.ovp":
> {//section for ovp-specific app descriptor settings
> "globalFilterModel": "ZModelName", //OData model that contains entity definitions relevant for global filters
> "globalFilterEntityType": "ZFilterEntityType", //Represents the entity to use as a global filter in the smart filter bar control
@@ -25,14 +25,13 @@ The `manifest.json` file defines static information about the application, such
> "considerAnalyticalParameters": true, //Flag to enable/disable analytical parameter support for smart filter bar
> "refreshIntervalInMinutes": 2, //Time interval in minutes to auto refresh the card models
> "useDateRangeType": true, //Flag to enable or disable semantic date range control for the Smart filter bar. The default value is false.
->
-> "cards": { //An object of cards
+>
> "card01": { //each card will contain the following
> "model": "ZCard1Model", //Model for the card
> "template": "sap.ovp.cards.list",//Card component path to use for this card
> "settings": {
> "title": "card title", //Language-dependent title of the card - used in the card header
-> "ubTitle": "sub title", //Language-dependent subtitle of the card - used in the card header
+> "subTitle": "sub title", //Language-dependent subtitle of the card - used in the card header
> "entitySet": "zCard1EntitySet", //Entity set displayed in this card
> "valueSelectionInfo": "text for KPI Header", //Additional information relevant for the KPI Header
> "listFlavor": "Standard", //Represents the flavor of the list to use in this card. The flavor can be bar or standard.
@@ -44,16 +43,16 @@ The `manifest.json` file defines static information about the application, such
> "annotationPath": "", // Represents the annotation path
> "kpiAnnotationPath":"com.sap.vocabularies.UI.v1.KPI#AllActualCosts", // Represents the KPI annotation path"selectionAnnotationPath": "", // Represents the selection annotation path
> "chartAnnotationPath": "",//Represents the chart annotation path
-> "presentationAnnotationPath": "", //Represents the presentation annotation path
+> "presentationAnnotationPath": "", //Represents the presentation annotation path
> "dataPointAnnotationPath": "", //Represents the data point annotation path
-> "identificationAnnotationPath": "", //Represents the identification annotation path
-> "dynamicSubtitleAnnotationPath": "dynamicSubtitle", //Represents the dynamic subtitle annotation path
+> "identificationAnnotationPath": "", //Represents the identification annotation path
+> "dynamicSubtitleAnnotationPath": "dynamicSubtitle", //Represents the dynamic subtitle annotation path
> "requireAppAuthorization": "", //Represents the cards for which authorization is required
> "chartAnnotationPath": "com.sap.vocabularies.UI.v1.Chart#SalesShareBubble",
-> "presentationAnnotationPath": "com.sap.vocabularies.UI.v1.PresentationVariant#SalesShareBubble",
-> "identificationAnnotationPath": "com.sap.vocabularies.UI.v1.Identification#Eval_by_Currency_Scatter",
-> "selectionAnnotationPath" : "com.sap.vocabularies.UI.v1.SelectionVariant#Eval_by_Currency_ColumnStacked",
-> "navigation": "noHeaderNav" //Allows you to disable navigation from the analytical list card header area
+> "presentationAnnotationPath": "com.sap.vocabularies.UI.v1.PresentationVariant#SalesShareBubble",
+> "identificationAnnotationPath": "com.sap.vocabularies.UI.v1.Identification#Eval_by_Currency_Scatter",
+> "selectionAnnotationPath" : "com.sap.vocabularies.UI.v1.SelectionVariant#Eval_by_Currency_ColumnStacked",
+> "navigation": "noHeaderNav" //Allows you to disable navigation from the analytical list card header area
> }
> }
> }
diff --git a/docs/06_SAP_Fiori_Elements/displaying-actions-on-the-object-page-f65e8b1.md b/docs/06_SAP_Fiori_Elements/displaying-actions-on-the-object-page-f65e8b1.md
index 7c87d338..2fbccea2 100644
--- a/docs/06_SAP_Fiori_Elements/displaying-actions-on-the-object-page-f65e8b1.md
+++ b/docs/06_SAP_Fiori_Elements/displaying-actions-on-the-object-page-f65e8b1.md
@@ -8,7 +8,7 @@ Specific rules apply when displaying actions on the object page.
## Order of Actions
-The default display of order of actions in the object page header is as follows:
+The default display order of actions in the object page header is as follows:
1. Generic actions
@@ -37,7 +37,7 @@ The display of actions depends on which mode the user is in:
- In *Display* mode, the relevant actions are displayed in the header toolbar \(see [Object Page Elements](object-page-elements-645e27a.md)\).
-- In *Edit* or *Create* mode, the footer bar contains the relevant actions, for example, *Save* and *Cancel* in *Edit* mode \(see figure below\), and *Create* and *Cancel* in *Create* mode.
+- In *Edit* or *Create* mode, the footer bar contains the relevant actions, for example, *Save* and *Cancel* in *Edit* mode \(see the mentioned figure\), and *Create* and *Cancel* in *Create* mode.
diff --git a/docs/06_SAP_Fiori_Elements/enabling-inline-creation-mode-or-empty-rows-mode-for-table-entries-cfb04f0.md b/docs/06_SAP_Fiori_Elements/enabling-inline-creation-mode-or-empty-row-mode-for-table-entries-cfb04f0.md
similarity index 78%
rename from docs/06_SAP_Fiori_Elements/enabling-inline-creation-mode-or-empty-rows-mode-for-table-entries-cfb04f0.md
rename to docs/06_SAP_Fiori_Elements/enabling-inline-creation-mode-or-empty-row-mode-for-table-entries-cfb04f0.md
index 6e827851..1c1ee915 100644
--- a/docs/06_SAP_Fiori_Elements/enabling-inline-creation-mode-or-empty-rows-mode-for-table-entries-cfb04f0.md
+++ b/docs/06_SAP_Fiori_Elements/enabling-inline-creation-mode-or-empty-row-mode-for-table-entries-cfb04f0.md
@@ -1,32 +1,32 @@
-# Enabling Inline Creation Mode or Empty Rows Mode for Table Entries
+# Enabling Inline Creation Mode or Empty Row Mode for Table Entries
-In apps that use draft handling, you can enable the inline creation mode or empty rows mode for table entries.
+In apps that use draft handling, you can enable the inline creation mode or empty row mode for table entries.
> ### Tip:
-> We recommend that you use the inline creation mode or empty rows mode only for tables that don't have a large number of columns. For complex tables, use create page instead.
+> We recommend that you use the inline creation mode or empty row mode only for tables that don't have a large number of columns. For complex tables, use create page instead.
The behavior of the available modes is as follows:
- **Inline Creation Mode**: In create or edit mode, users can choose *Create Entry* to add new entries to a section in a table. By default, a new entry is created and the system automatically navigates to the item's object page. You can enable inline creation of entries, that is, a new line is created and the fields can be modified inline but automatic navigation isn't triggered. When a new entry is created, the line is highlighted in blue. This highlight disappears once the data is saved.
-- **Empty Rows Mode**: In create or edit mode, two new empty rows are added to the table. In a responsive table, the empty rows are added at the top. In a grid table, the empty rows are added at the bottom. There are no corresponding entries in the draft table for these empty rows. When you modify a field in an empty row and move the focus away from that field, a new row is added automatically to the draft table. Since the empty rows mode always provides two new empty rows, another empty row is added below after the current row in the table.
+- **Empty Row Mode**: In create or edit mode, one new empty row is added to the table. In a responsive table, the empty row is added at the top. In a grid table, the empty row is added at the bottom. There is no corresponding entry in the draft table for the empty row. When you begin to add data to a field in an empty row, a new empty row is automatically added .However, the current row is converted to draft only when the focus is moved away from the input field. The automatically added empty row is removed if the user doesn't add any data. It isn't required to manually remove the empty row.
- The empty rows mode has the following features:
+ The empty row mode has the following features:
- - The row actions, such as the navigation indicator using a chevron, and inline deletion, are hidden in the empty rows.
+ - The row actions, such as the navigation indicator using a chevron, and inline deletion, are hidden in the empty row.
- - Sorting and grouping isn't applicable for the empty rows, as they don’t exist in a back-end table.
+ - Sorting and grouping isn't applicable for the empty row, as it doesn't exist in a back-end table.
- In a responsive table, the *Create* button is hidden.
- - In a grid table, the *Create* button is visible. When you click *Create* in the grid table toolbar, the table scrolls to the bottom of the table to display the empty rows, and automatically sets the focus on the first editable field of the first empty row.
+ - In a grid table, the *Create* button is visible. When you click *Create* in the grid table toolbar, the table scrolls to the bottom of the table to display the empty row, and automatically sets the focus on the first editable field of the empty row.
> ### Restriction:
-> The empty rows mode isn't supported when immutable properties are required.
+> The empty row mode isn't supported when immutable properties are required.
> ### Note:
> - You can make the object page tables insertable or not insertable using the `InsertRestrictions` annotation. For more information, see [Adding Actions to Tables](adding-actions-to-tables-b623e0b.md).
@@ -34,6 +34,8 @@ The behavior of the available modes is as follows:
> - If you've defined an ID for the reference facet of your table, use this ID instead of the generated one, for example, to\_ProductText::com.sap.vocabularies.UI.v1.LineItem. For more information, see [Defining and Adapting Sections](defining-and-adapting-sections-facfea0.md).
>
> - For apps based on releases below SAP NetWeaver 7.51 SP01, the following restriction applies: If a user sets a filter in a table that is enabled for inline creation, the filter conditions may not be evaluated correctly. This can result in data being displayed incorrectly and not according to the filter criteria that has been entered. This is relevant only for apps that use draft handling.
+>
+> - The empty row is prefilled with default values when the `com.sap.vocabularies.Common.v1.DefaultValuesFunction` annotation is defined in the entity set that belongs to the table with which it's configured. For more information, see [Prefilling Fields Using the DefaultValuesFunction](prefilling-fields-using-the-defaultvaluesfunction-5ada91c.md).
@@ -87,12 +89,9 @@ To enable inline creation, in the `pages` section within `manifest.json` of your
A section ID defined in the annotation must match the section ID defined in the manifest configuration, where the `createMode` setting is defined. For example, ``.
-Similarly, to enable empty rows mode, set `"createMode"` as `"creationRows"`. With this configuration, the table behaves as described in the Empty Rows Mode section..
-
-Users can explicitly hide empty rows in the edit mode and make the empty rows available only in the create mode. To hide empty rows in edit mode, set `"createMode"` as `"creationRowsHiddenInEditMode"`. The table doesn't contain any empty rows upon loading with this configuration. Empty rows are added to the table only when you click the *Create* button.
+Similarly, to enable empty row mode, set `"createMode"` as `"creationRows"`. With this configuration, the table behaves as described in the Empty Row Mode section..
-> ### Note:
-> The empty rows are prefilled with default values when the `com.sap.vocabularies.Common.v1.DefaultValuesFunction` annotation is defined in the entity set that belongs to the table with which it's configured. For more information, see [Prefilling Fields Using the DefaultValuesFunction](prefilling-fields-using-the-defaultvaluesfunction-5ada91c.md).
+Users can explicitly hide the empty row in the edit mode and make the empty row available only in the create mode. To hide the empty row in edit mode, set `"createMode"` as `"creationRowsHiddenInEditMode"`. The table doesn't contain an empty row upon loading with this configuration. An empty row is added to the table only when you click the *Create* button.
@@ -170,18 +169,18 @@ To enable inline creation mode in an object page per table, set `"creationMode"`
-### Enabling and Disabling Empty Rows Mode
+### Enabling and Disabling Empty Row Mode
-To enable the empty rows mode, set `"creationMode"` to `"InlineCreationRows"`.
+To enable the empty row mode, set `"creationMode"` to `"InlineCreationRows"`.
-The default behavior of the empty rows mode is as follows:
+The default behavior of the empty row mode is as follows:
-- The empty rows are visible on grid and responsive tables when a new object is created.
+- The empty row is visible on grid and responsive tables when a new object is created.
-- The empty rows are visible on grid and responsive tables when an existing object is edited.
+- The empty row is visible on grid and responsive tables when an existing object is edited.
-To change this behavior, you can use the parameter `inlineCreationRowsHiddenInEditMode`. Its default value is `'false'`. If it is set to `'true'`, the empty rows will be hidden when editing an existing object. Selecting the table's *Create* button will display the empty rows.
+To change this behavior, you can use the parameter `inlineCreationRowsHiddenInEditMode`. Its default value is `'false'`. If it is set to `'true'`, the empty row will be hidden when editing an existing object. Selecting the table's *Create* button will display the empty row.
> ### Sample Code:
> `manifest.json`
@@ -214,9 +213,9 @@ To change this behavior, you can use the parameter `inlineCreationRowsHiddenInEd
-### Disabling Fields in the Empty Rows Mode
+### Disabling Fields in the Empty Row Mode
-Certain fields in the `inlineCreationRows` may become relevant only after the row has been created. They can be disabled so that they appear as read-only in the empty rows.
+Certain fields in the `inlineCreationRows` may become relevant only after the row has been created. They can be disabled so that they appear as read-only in the empty row.
To disable a field, use the `Capabilities.InsertRestrictions.NonInsertableProperties` annotation.
diff --git a/docs/06_SAP_Fiori_Elements/enabling-quick-views-for-link-navigation-307ced1.md b/docs/06_SAP_Fiori_Elements/enabling-quick-views-for-link-navigation-307ced1.md
index 875c47ed..5485c2a8 100644
--- a/docs/06_SAP_Fiori_Elements/enabling-quick-views-for-link-navigation-307ced1.md
+++ b/docs/06_SAP_Fiori_Elements/enabling-quick-views-for-link-navigation-307ced1.md
@@ -31,7 +31,7 @@ To do so, perform the following steps:
## Procedure
-1. Identify the property that has been annotated as a semantic object.
+1. Identify the property that has been annotated as a semantic object. In this case, the field is shown as a link. For more information, see [Navigation from an App \(Outbound Navigation\)](navigation-from-an-app-outbound-navigation-d782acf.md).
> ### Sample Code:
> XML Annotation
diff --git a/docs/06_SAP_Fiori_Elements/enabling-table-personalization-3e2b4d2.md b/docs/06_SAP_Fiori_Elements/enabling-table-personalization-3e2b4d2.md
index fc8c00a8..d94527d7 100644
--- a/docs/06_SAP_Fiori_Elements/enabling-table-personalization-3e2b4d2.md
+++ b/docs/06_SAP_Fiori_Elements/enabling-table-personalization-3e2b4d2.md
@@ -102,8 +102,6 @@ In the list report, you can set the variant management to `"Page"` level or to `
- Sorting
- Users can sort tables by choosing individual columns or multiple columns \(unless sorting is disabled\). Users can sort each column in ascending or descending order.
-
You can use the `@.OData.Capabilities.V1.SortRestrictions` annotation to exclude those columns you don’t want to be sortable. You can use the `@.OData.Capabilities.V1.NavigationRestrictions` annotation to exclude navigation properties.
@@ -111,7 +109,7 @@ In the list report, you can set the variant management to `"Page"` level or to `
> ### Note:
> Defining sort restrictions is currently only possible for first-level navigation entities.
- You can use `SortRestrictions` to define your desired `RestrictedProperty` in the `NavigationRestrictions`. Use `SortRestrictions` to either restrict all properties of an entity by setting `Sortable` to `false`, or to disable sorting of individual properties using `NonSortableProperties`.
+ You can use `SortRestrictions` to define your desired `RestrictedProperty` in the `NavigationRestrictions`. Use `SortRestrictions` to either restrict all properties of an entity by setting `Sortable` to `false`, or to disable sorting of individual properties using `NonSortableProperties`. To add sort retrictions for navigation properties, the list of `NonSortableProperties` must be prefixed with the `NavigationPropertyPath`.
> ### Sample Code:
> XML Annotation for `SortRestrictions` in `NavigationRestrictions`
@@ -127,7 +125,7 @@ In the list report, you can set the variant management to `"Page"` level or to `
>
>
>
- > OverallSDProcessStatus_Text
+ > _OverallSDProcessStatus/OverallSDProcessStatus_Text
>
>
>
@@ -164,7 +162,7 @@ In the list report, you can set the variant management to `"Page"` level or to `
> RestrictedProperties : [
> {
> NavigationProperty: _OverallSDProcessStatus,
- > SortRestrictions: {NonSortableProperties: [OverallSDProcessStatus_Text]}
+ > SortRestrictions: {NonSortableProperties: [_OverallSDProcessStatus.OverallSDProcessStatus_Text]}
> },
> {
> NavigationProperty: _SalesOrderType,
@@ -179,7 +177,7 @@ In the list report, you can set the variant management to `"Page"` level or to `
- Adding or removing columns
- Users can add or remove all properties of the root entity of a given table and its 1:1 navigation entities. Selected properties are shown at the top of the list. For all properties of navigation entities, the name of the navigation entity is shown below the name of the property using a gray font, as shown in the following screenshot:
+ Users can add or remove all properties of the root entity of a given table and its 1:1 navigation entities. Selected properties are shown at the top of the list. For all properties of navigation entities, the name of the navigation entity is shown below the name of the property using a gray font, as shown in the following screenshot:Users can sort tables by choosing individual columns or multiple columns \(unless sorting is disabled\). Users can sort each column in ascending or descending order.
@@ -201,7 +199,7 @@ Variant management on control level enables filtering, sorting, adding/removing
> Using the `"personalization"` setting
>
> ```
-> "BusinessPartnersList": {
+> Users can sort tables by choosing individual columns or"BusinessPartnersList": {
> "type": "Component",
> "id": "BusinessPartnersList",
> "name": "sap.fe.templates.ListReport",
@@ -237,3 +235,12 @@ You can use the following values for the `"personalization"` setting:
- object: If you use the value 'object', you must also define the values `"column"`, `"sort"` and `"filter"`. If the table is an analytical table, you can also configure the `"group"`. In this case omitting a setting is treated as false, which prevents apps from getting new features in upcoming releases. You can see this in the sample code above, where the object is used as a value for an analytical table.
+> ### Note:
+> - Sorting, grouping, and filtering applies to the properties visible in a column. For example, for properties with text arrangement set as `#TextFirst`, the property itself or its text can be sorted, grouped, or filtered. For properties with text arrangement set as `#TextOnly`, sorting and grouping applies to the text. .
+>
+> - If a label is defined for a column within the `LineItem`, then the label is used in the Sort, Group, and Filter menus if the column displays a single property. For example, a property with a text annotation `#TextOnly`,
+>
+> - For properties with text arrangement set as `#TextOnly`, if its text is annotated as `UI.Hidden = true`, then the annotation is ignored. This text property can still be sorted and grouped.
+>
+> - If a `sortOrder` is set via a presentation variant on a property with text arrangement set as `#TextOnly`, the sorting is applied on the property and not the text. The sort indicator will not appear in the header column containing the property as the property is not visible on the table. This also applies for the sort and group tabs on the table personalisation dialog.
+
diff --git a/docs/06_SAP_Fiori_Elements/extending-delivered-apps-using-adaptation-extensions-52fc48b.md b/docs/06_SAP_Fiori_Elements/extending-delivered-apps-using-adaptation-extensions-52fc48b.md
index c187f0b6..e1b83462 100644
--- a/docs/06_SAP_Fiori_Elements/extending-delivered-apps-using-adaptation-extensions-52fc48b.md
+++ b/docs/06_SAP_Fiori_Elements/extending-delivered-apps-using-adaptation-extensions-52fc48b.md
@@ -16,9 +16,9 @@ You can implement extension functions as part of a UI adaptation project by usin
> ### Note:
> This procedure is relevant only for list reports, object pages, overview pages, and analytical list pages.
>
-> The flexible column layout is not supported by the SAP Business Application Studio.
+> The flexible column layout is not supported by the Visual Editor.
-You can try the adaptation extensions by creating an adaptation projects described in [Extending an SAP Fiori Application](https://help.sap.com/docs/bas/developing-sap-fiori-app-in-sap-business-application-studio/extending-sap-fiori-application).
+You can try the adaptation extensions by creating an adaptation project described in [Extending an SAP Fiori Application](https://help.sap.com/docs/bas/developing-sap-fiori-app-in-sap-business-application-studio/extending-sap-fiori-application).
You can use adaptation extensions for these extension points:
diff --git a/docs/06_SAP_Fiori_Elements/extending-list-reports-and-object-pages-using-app-extensions-a892eb8.md b/docs/06_SAP_Fiori_Elements/extending-list-reports-and-object-pages-using-app-extensions-a892eb8.md
index da8bfcf2..70b073cd 100644
--- a/docs/06_SAP_Fiori_Elements/extending-list-reports-and-object-pages-using-app-extensions-a892eb8.md
+++ b/docs/06_SAP_Fiori_Elements/extending-list-reports-and-object-pages-using-app-extensions-a892eb8.md
@@ -17,14 +17,11 @@ Make sure you have read the following information: [Read Before Extending a Gene
## Additional Features in SAP Fiori Elements for OData V2
-You can either use the extension wizard in the SAP Web IDE to create extensions or you can create them manually.
+You can either use [SAP Fiori tools](https://help.sap.com/viewer/product/SAP_FIORI_tools/Latest/en-US), which is a set of extensions for SAP Business Application Studio and Visual Studio Code to create extensions, or you can create them manually.
-> ### Caution:
-> SAP Web IDE is no longer available via SAP Business Technology Platform trial accounts. Any references to SAP Web IDE in this documentation are only relevant for you if you have access to SAP Web IDE through a productive SAP BTP account. Please consider SAP Business Application Studio as an alternative. See [App Development Using SAP Business Application Studio](../05_Developing_Apps/app-development-using-sap-business-application-studio-6bbad66.md).
-
-For more information about SAP Web IDE, see the documentation for SAP Web IDE on the SAP Help Portal at [https://help.sap.com/viewer/p/SAP\_Web\_IDE](https://help.sap.com/viewer/p/SAP_Web_IDE).
+For more information, see [Configure Page Elements](https://help.sap.com/docs/SAP_FIORI_tools/17d50220bcd848aa854c9c182d65b699/047507c86afa4e96bb3d284adb9f4726.html).
-In list reports and object pages, you can use SAP Web IDE to add the following extensions:
+In list reports and object pages, you can use [SAP Fiori tools](https://help.sap.com/viewer/product/SAP_FIORI_tools/Latest/en-US) to add the following extensions:
- List report
@@ -48,7 +45,8 @@ In list reports and object pages, you can use SAP Web IDE to add the following e
-While this documentation describes how to manually define app extensions, the following how-to video shows you how to create a section extension on the object page using the extension wizard: .
+> ### Note:
+> We've removed videos showing step-by-step procedures using SAP Web IDE, which SAP no longer actively supports. You can still access the video using an older version of this document.
**Related Information**
diff --git a/docs/06_SAP_Fiori_Elements/extending-sap-fiori-elements-based-apps-358cf25.md b/docs/06_SAP_Fiori_Elements/extending-sap-fiori-elements-based-apps-358cf25.md
index 74e08feb..79964ef0 100644
--- a/docs/06_SAP_Fiori_Elements/extending-sap-fiori-elements-based-apps-358cf25.md
+++ b/docs/06_SAP_Fiori_Elements/extending-sap-fiori-elements-based-apps-358cf25.md
@@ -2,7 +2,7 @@
# Extending SAP Fiori Elements-Based Apps
-You can use app extensions to extend your app.
+App extensions can be used to extend your app.
These are made by developers during the creation of an SAP Fiori elements-based app, using framework extension points provided by SAP Fiori elements. The extensions are made, for example, using manifest changes or SAPUI5 extension points, depending on the floorplan. For more information, see [Extending Generated Apps Using App Extensions](extending-generated-apps-using-app-extensions-340cdb2.md).
diff --git a/docs/06_SAP_Fiori_Elements/extending-the-delivered-apps-manifest-using-an-adaptation-project-a2b24a6.md b/docs/06_SAP_Fiori_Elements/extending-the-delivered-apps-manifest-using-an-adaptation-project-a2b24a6.md
index 3829f70a..36d7c7f7 100644
--- a/docs/06_SAP_Fiori_Elements/extending-the-delivered-apps-manifest-using-an-adaptation-project-a2b24a6.md
+++ b/docs/06_SAP_Fiori_Elements/extending-the-delivered-apps-manifest-using-an-adaptation-project-a2b24a6.md
@@ -613,7 +613,7 @@ The following parameters have to be included as `headerWhiteList` in the consumi
>
> ```
-These changes are to be added to `manifest.appdescr_variant` file in the adaptation project. For more details on the mergers, see [Descriptor Change Types](https://wiki.wdf.sap.corp/wiki/display/UI/Descriptor+Change+Types#b0f58371-dfbf-460f-b9d7-fdb3c0edaad1-1884226546).
+These changes are to be added to `manifest.appdescr_variant` file in the adaptation project
> ### Sample Code:
> ```
diff --git a/docs/06_SAP_Fiori_Elements/header-facets-17dbd5b.md b/docs/06_SAP_Fiori_Elements/header-facets-17dbd5b.md
index f22b5f8c..816bac5d 100644
--- a/docs/06_SAP_Fiori_Elements/header-facets-17dbd5b.md
+++ b/docs/06_SAP_Fiori_Elements/header-facets-17dbd5b.md
@@ -57,7 +57,7 @@ You can use the annotation term `UI.HeaderFacets` to define which information is
> $Type : 'UI.ReferenceFacet',
> Label : 'Price',
> ID : 'Price',
-> Target : '@UI.DataPoint#Price
+> Target : '@UI.DataPoint#Price'
> },
> {
> $Type : 'UI.ReferenceFacet',
diff --git a/docs/06_SAP_Fiori_Elements/highlighting-line-items-based-on-criticality-0d501b1.md b/docs/06_SAP_Fiori_Elements/highlighting-line-items-based-on-criticality-0d501b1.md
index 642c843c..f3d612a6 100644
--- a/docs/06_SAP_Fiori_Elements/highlighting-line-items-based-on-criticality-0d501b1.md
+++ b/docs/06_SAP_Fiori_Elements/highlighting-line-items-based-on-criticality-0d501b1.md
@@ -23,7 +23,7 @@ The property containing the criticality can have the following values \(derived
> ### Note:
> - By default, SAP Fiori elements assumes that the `DataField` is also marked with "CriticalityRepresentationType/WithIcon" and sets the icon of the `ObjectStatus` appropriately \(for example, for fields marked with "com.sap.vocabularies.UI.v1.CriticalityType/Negative", SAP Fiori elements sets the 'sap-icon://status-negative'\).
>
- > - If the field is marked with "CriticalityRepresentationType/WithoutIcon", then the `` is rendered without the icon.
+ > - If the field is marked with "CriticalityRepresentationType/WithoutIcon", then it is rendered without the icon.
diff --git a/docs/06_SAP_Fiori_Elements/how-to-use-sap-fiori-elements-20de950.md b/docs/06_SAP_Fiori_Elements/how-to-use-sap-fiori-elements-20de950.md
index eab32d4d..e1ad31a5 100644
--- a/docs/06_SAP_Fiori_Elements/how-to-use-sap-fiori-elements-20de950.md
+++ b/docs/06_SAP_Fiori_Elements/how-to-use-sap-fiori-elements-20de950.md
@@ -18,7 +18,7 @@ Creating an app with SAP Fiori elements generally consists of the following step
- Build UI applications
- You can use [SAP Fiori tools](https://help.sap.com/viewer/product/SAP_FIORI_tools/Latest/en-US), which is a set of extensions for SAP Business Application Studio and Visual Studio Code, to build your apps. For more information about SAP Business Application Studio, see the documentation on the SAP Help Portal at [SAP Business Application Studio](https://help.sap.com/viewer/product/SAP%20Business%20Application%20Studio/Cloud/en-US).
+ You can build your apps using [SAP Fiori tools](https://help.sap.com/viewer/product/SAP_FIORI_tools/Latest/en-US), which is a set of extensions for SAP Business Application Studio and Visual Studio Code. For more information about SAP Business Application Studio, see the documentation on the SAP Help Portal at [SAP Business Application Studio](https://help.sap.com/viewer/product/SAP%20Business%20Application%20Studio/Cloud/en-US).
- Extend SAP Fiori elements-based apps
diff --git a/docs/06_SAP_Fiori_Elements/hybrid-view-6615668.md b/docs/06_SAP_Fiori_Elements/hybrid-view-6615668.md
index 9bc56f91..59e0ebbf 100644
--- a/docs/06_SAP_Fiori_Elements/hybrid-view-6615668.md
+++ b/docs/06_SAP_Fiori_Elements/hybrid-view-6615668.md
@@ -27,10 +27,8 @@ Make the following setting:
>
> ```
-The *Auto-hide*
-
> ### Note:
-> Ensure that the chart context dimensions are set as visible columns in the table for optimal accuracy of highlights. feature is displayed in the hybrid view \(chart and table\). When the feature is turned off, the table records that are not affected by the chart selection are also displayed in the table. If the feature is turned on, then only the records that are affected by the chart selection \(for example, only the highlighted records\) are displayed in the table. In this case, chart selection acts as an additional filter. The table records that match the selected chart context are highlighted.
+> Ensure that the chart context dimensions are set as visible columns in the table for optimal accuracy of highlights. The *auto-hide* feature is displayed in the hybrid view \(chart and table\). When the feature is turned off, the table records that are not affected by the chart selection are also displayed in the table. If the feature is turned on, then only the records that are affected by the chart selection \(for example, only the highlighted records\) are displayed in the table. In this case, chart selection acts as an additional filter. The table records that match the selected chart context are highlighted.
> ### Tip:
> Note that the hybrid view is available in laptops with a screen height that is larger than 900px.
diff --git a/docs/06_SAP_Fiori_Elements/images/Folder_Structure_for_List_Report_and_Object_Page_c33e8a1.png b/docs/06_SAP_Fiori_Elements/images/Folder_Structure_for_List_Report_and_Object_Page_c33e8a1.png
new file mode 100644
index 00000000..fb5b79e2
Binary files /dev/null and b/docs/06_SAP_Fiori_Elements/images/Folder_Structure_for_List_Report_and_Object_Page_c33e8a1.png differ
diff --git a/docs/06_SAP_Fiori_Elements/images/Smart_Templates_Folder_Structure_aeab6b5.png b/docs/06_SAP_Fiori_Elements/images/Smart_Templates_Folder_Structure_aeab6b5.png
deleted file mode 100644
index d46c5018..00000000
Binary files a/docs/06_SAP_Fiori_Elements/images/Smart_Templates_Folder_Structure_aeab6b5.png and /dev/null differ
diff --git a/docs/06_SAP_Fiori_Elements/images/copy-paste-filter-bar_e343435.png b/docs/06_SAP_Fiori_Elements/images/copy-paste-filter-bar_e343435.png
new file mode 100644
index 00000000..2a618ad7
Binary files /dev/null and b/docs/06_SAP_Fiori_Elements/images/copy-paste-filter-bar_e343435.png differ
diff --git a/docs/06_SAP_Fiori_Elements/loading-behavior-based-on-the-chosen-variant-9f4e119.md b/docs/06_SAP_Fiori_Elements/loading-behavior-based-on-the-chosen-variant-9f4e119.md
index 1d2316e3..db8f5291 100644
--- a/docs/06_SAP_Fiori_Elements/loading-behavior-based-on-the-chosen-variant-9f4e119.md
+++ b/docs/06_SAP_Fiori_Elements/loading-behavior-based-on-the-chosen-variant-9f4e119.md
@@ -6,7 +6,7 @@ Several factors affect the loading behavior of the content area based on the cho
These factors are also considered in the following use cases:
-- There is no tile context during intial navigation from tiles.
+- There is no tile context during initial navigation from tiles.
- There is no tile context, except for values from SAP Fiori launchpad user settings.
@@ -106,7 +106,7 @@ For multi-view scenarios, you can also change the manifest setting `enableAutobi
### SAP Fiori Elements for OData V4
-Application developers can set `initialLoad` to `Auto`\(default\), `Disabled` , and `Enabled`.
+Application developers can set `initialLoad` to `Auto` \(default\), `Disabled` , and `Enabled`.
> ### Sample Code:
> ```
@@ -127,7 +127,7 @@ These settings work for both single and multi-view applications.
This is the loading behavior:
-- `Auto`: An initial load of data only occurs if some default filter values have been set in the filter bar. The *Apply Automatically* checkbox is provided in the *Manage Views* dialog together with the following text: *If predefined filter values are available, the content loads automatically.*. This is the default setting.
+- `Auto`: An initial load of data only occurs if some default filter values have been set in the filter bar. The *Apply Automatically* checkbox is provided in the *Manage Views* dialog together with the following text: *If predefined filter values are available, the content loads automatically.* This is the default setting.
- `Disabled`: An initial load of data does not occur for the standard variant and the user has to actively click the *Go* button. End users can override this by selecting the *Apply Automatically* checkbox in the *Manage Views* dialog.
diff --git a/docs/06_SAP_Fiori_Elements/localization-of-ui-texts-b8cb649.md b/docs/06_SAP_Fiori_Elements/localization-of-ui-texts-b8cb649.md
index 22ce2a15..64a02299 100644
--- a/docs/06_SAP_Fiori_Elements/localization-of-ui-texts-b8cb649.md
+++ b/docs/06_SAP_Fiori_Elements/localization-of-ui-texts-b8cb649.md
@@ -26,8 +26,6 @@ Perform the following steps to replace the standard UI texts:
-
-
## Overriding Texts from Annotations
You can override the texts that come from annotations. To do so, the annotation must refer to the i18n key that is used in the application’s i18n file:
@@ -2102,7 +2100,6 @@ Example:
"i18n|sap.suite.ui.generic.template.ObjectPage|POItems": {
"type": "sap.ui.model.resource.ResourceModel",
"uri": "i18n/ObjectPage/POItems/i18n.properties"
- },
```
@@ -4346,31 +4343,21 @@ Applications should overwrite the default text with the concrete object.
|
- `OBJECTPAGESTATE_ISSUE`
-
|
-This object contains issues
-
|
-Error message text used in the message strip of an object page.
-
|
-Applications should overwrite the default text and replace "object" with their concrete object.
-
-Example: *The sales order contains issues.*
-
|
@@ -4378,14 +4365,16 @@ Example: *The sales order contains issues.*
|
- `OBJECTPAGESTATE_ERROR`
+`OBJECTPAGESTATE_ERROR`
+
+\(deprecated key: `OBJECTPAGESTATE_ISSUE`\)
|
-The object contains error messages
+The object contains errors.
@@ -4401,7 +4390,7 @@ Error message text used in the message strip of an object page.
Applications should overwrite the default text and replace "object" with their concrete object.
-Example: *The sales order contains error messages.*
+Example: *The sales order contains errors.*
@@ -4417,7 +4406,7 @@ Example: *The sales order contains error messages.*
|
-The object contains warning messages
+The object contains warnings.
@@ -4433,7 +4422,7 @@ Warning message text used in the message strip of an object page.
Applications should overwrite the default text and replace "object" with their concrete object.
-Example: *The sales order contains warning messages.*
+Example: *The sales order contains warnings.*
@@ -4449,7 +4438,7 @@ Example: *The sales order contains warning messages.*
|
-The object contains information messages.
+The object contains messages.
@@ -4465,7 +4454,7 @@ Information text used in the message strip of an object page.
Applications should overwrite the default text and replace "object" with their concrete object.
-Example: *The sales order contains information messages.*
+Example: *The sales order contains messages.*
@@ -4529,6 +4518,70 @@ Applications can choose to overwrite the default text with a more specific one.
+ |
+
+
+|
+
+ `M_COMMON_TABLE_CREATE`
+
+
+
+ |
+
+
+Create
+
+
+
+ |
+
+
+ *Create* button text in a table
+
+
+
+ |
+
+
+Applications can choose to overwrite the default text with a more specific one for a certain table.
+
+Example: `M_COMMON_TABLE_CREATE|_Items=MyCustomCreateText`
+
+
+
+ |
+
+
+|
+
+ `M_COMMON_TABLE_DELETE`
+
+
+
+ |
+
+
+Delete
+
+
+
+ |
+
+
+ *Delete* button text in a table
+
+
+
+ |
+
+
+Applications can choose to overwrite the default text with a more specific one for a certain table.
+
+Example: `M_COMMON_TABLE_DELETE|_Items=MyCustomDeleteText`
+
+
+
|
diff --git a/docs/06_SAP_Fiori_Elements/multiple-views-on-list-report-tables-a37df40.md b/docs/06_SAP_Fiori_Elements/multiple-views-on-list-report-tables-a37df40.md
index 2680180c..483ed4f2 100644
--- a/docs/06_SAP_Fiori_Elements/multiple-views-on-list-report-tables-a37df40.md
+++ b/docs/06_SAP_Fiori_Elements/multiple-views-on-list-report-tables-a37df40.md
@@ -6,7 +6,8 @@ By default, the list report displays only one table. You can define multiple vie
-This video shows the step-by-step procedure for defining multiple views:
+> ### Note:
+> We've removed videos showing step-by-step procedures using SAP Web IDE, which SAP no longer actively supports. You can still access the video using an older version of this document.
> ### Note:
> You can define variants for specific selections of data on the user interface, for example, based on filter settings. In the definition dialog, these variants are called views, however, the feature is called variant management. Therefore, for clarity, we use the term variant management in this section.
diff --git a/docs/06_SAP_Fiori_Elements/navigation-from-an-app-outbound-navigation-d782acf.md b/docs/06_SAP_Fiori_Elements/navigation-from-an-app-outbound-navigation-d782acf.md
index 1b68d8ef..ee915c75 100644
--- a/docs/06_SAP_Fiori_Elements/navigation-from-an-app-outbound-navigation-d782acf.md
+++ b/docs/06_SAP_Fiori_Elements/navigation-from-an-app-outbound-navigation-d782acf.md
@@ -108,7 +108,9 @@ To enable intent-based navigation, you must associate a semantic object. Navigat
To use a specific property that is always shown as a link in your application, you must annotate the property with a semantic object. Wherever the property is used as a `DataField`, it is always rendered as a link.
- When a user chooses the link, and only one navigation target is found, direct navigation to the target is triggered. If more than one target is found, the system displays a popover containing some text and links to the targets for the user to choose from. You can enhance the content of this popover and display a quick view containing more information about the navigation target. For more information, see [Enabling Quick Views for Link Navigation](enabling-quick-views-for-link-navigation-307ced1.md).
+ When a user chooses the link, and only one navigation target is found, direct navigation to the target is triggered. If more than one target is found, the system displays a popover containing some text and links to the targets for the user to choose from. The user can hide unwanted semantic object actions from the popover using `SemanticObjectUnavailableActions` annotation. The user can also annotate a property using multiple semantic objects. For more information, see [https://ui5.sap.com/\#/topic/f638884d0d624ad8a243f4005f8e9972](https://ui5.sap.com/#/topic/f638884d0d624ad8a243f4005f8e9972).
+
+ You can enhance the content of this popover and display a quick view containing more information about the navigation target. For more information, see [Enabling Quick Views for Link Navigation](enabling-quick-views-for-link-navigation-307ced1.md).
> ### Sample Code:
> XML Annotation
@@ -273,7 +275,7 @@ If `RequiresContext` is true, then the button is disabled until a selection is m
> XML Annotation
>
> ```xml
-> <
+>
>
>
>
diff --git a/docs/06_SAP_Fiori_Elements/passing-variant-ids-as-url-parameters-4132ffa.md b/docs/06_SAP_Fiori_Elements/passing-variant-ids-as-url-parameters-4132ffa.md
index 18b51f50..920bccdc 100644
--- a/docs/06_SAP_Fiori_Elements/passing-variant-ids-as-url-parameters-4132ffa.md
+++ b/docs/06_SAP_Fiori_Elements/passing-variant-ids-as-url-parameters-4132ffa.md
@@ -14,27 +14,27 @@ You can choose to pass a page variant or a control variant using these parameter
- `sap-ui-fe-variant-id`: Page variant ID you want to set
> ### Example:
- > https://abc.com/ui\#SalesOrder-analyze\_deliv\_perf?sap-ui-fe-variant-id=***id\_1542011587281\_980\_page***
+ > https://abc.com/ui\#SalesOrder-analyze\_deliv\_perf?sap-ui-fe-variant-id=`id_1542011587281_980_page`
- `sap-ui-fe-filterbar-variant-id`: Parameter for the filter bar control variant
> ### Example:
- > https://abc.com/ui\#SalesOrder-analyze\_deliv\_perf?sap-ui-fe-filterbar-variant-id=***id\_1542011587281\_230\_page***
+ > https://abc.com/ui\#SalesOrder-analyze\_deliv\_perf?sap-ui-fe-filterbar-variant-id=`id_1542011587281_230_page`
- `sap-ui-fe-chart-variant-id`: Parameter for the chart control variant
> ### Example:
- > https://abc.com/ui\#SalesOrder-analyze\_deliv\_perf?sap-ui-fe-chart-variant-id=***id\_1574157179885\_675\_chart***
+ > https://abc.com/ui\#SalesOrder-analyze\_deliv\_perf?sap-ui-fe-chart-variant-id=`id_1574157179885_675_chart`
- `sap-ui-fe-table-variant-id`: Parameter for the table control variant
> ### Example:
- > https://abc.com/ui\#SalesOrder-analyze\_deliv\_perf?sap-ui-fe-table-variant-id=***id\_1574157179595\_331\_table***
+ > https://abc.com/ui\#SalesOrder-analyze\_deliv\_perf?sap-ui-fe-table-variant-id=`id_1574157179595_331_table`
When both the chart variant and table variant are passed:
> ### Example:
- > https:/abc.com/ui\#SalesOrder-analyze\_deliv\_perf?sap-ui-fe-chart-variant-id=***id\_1574157179885\_675\_chart***&sap-ui-fe-table-variant-id=***id\_1574157179595\_331\_table***
+ > https:/abc.com/ui\#SalesOrder-analyze\_deliv\_perf?sap-ui-fe-chart-variant-id=`id_1574157179885_675_chart`&sap-ui-fe-table-variant-id=`id_1574157179595_331_table`
> ### Note:
diff --git a/docs/06_SAP_Fiori_Elements/prefilling-fields-using-the-defaultvaluesfunction-5ada91c.md b/docs/06_SAP_Fiori_Elements/prefilling-fields-using-the-defaultvaluesfunction-5ada91c.md
index 143a2be2..c79c8f48 100644
--- a/docs/06_SAP_Fiori_Elements/prefilling-fields-using-the-defaultvaluesfunction-5ada91c.md
+++ b/docs/06_SAP_Fiori_Elements/prefilling-fields-using-the-defaultvaluesfunction-5ada91c.md
@@ -7,9 +7,9 @@ When creating a new entity or item, or action parameters, you can provide defaul
> ### Note:
> This topic is currently only applicable to
>
-> - SAP Fiori elements for OData V2 non-draft applications.
+> - SAP Fiori elements for OData V2 and SAP Fiori elements for OData V4 non-draft applications.
>
-> - SAP Fiori elements for OData V2 draft applications in the empty rows mode. For more information, see [Enabling Inline Creation Mode or Empty Rows Mode for Table Entries](enabling-inline-creation-mode-or-empty-rows-mode-for-table-entries-cfb04f0.md).
+> - SAP Fiori elements for OData V2 draft applications in the empty row mode and for SAP Fiori elements for OData V4 draft applications in the inline and empty row modes. For more information, see [Enabling Inline Creation Mode or Empty Row Mode for Table Entries](enabling-inline-creation-mode-or-empty-row-mode-for-table-entries-cfb04f0.md).
For function import actions, the preference is given to the default values returned by the back end `DefaultValuesFunction`. If no value is returned by the `DefaultValuesFunction`, it is then read from the entity.
diff --git a/docs/06_SAP_Fiori_Elements/sap-fiori-elements-feature-map-62d3f7c.md b/docs/06_SAP_Fiori_Elements/sap-fiori-elements-feature-map-62d3f7c.md
index ec63da80..d7019926 100644
--- a/docs/06_SAP_Fiori_Elements/sap-fiori-elements-feature-map-62d3f7c.md
+++ b/docs/06_SAP_Fiori_Elements/sap-fiori-elements-feature-map-62d3f7c.md
@@ -3552,7 +3552,7 @@ Object page
|
-[Enabling Inline Creation Mode or Empty Rows Mode for Table Entries](enabling-inline-creation-mode-or-empty-rows-mode-for-table-entries-cfb04f0.md)
+[Enabling Inline Creation Mode or Empty Row Mode for Table Entries](enabling-inline-creation-mode-or-empty-row-mode-for-table-entries-cfb04f0.md)
diff --git a/docs/06_SAP_Fiori_Elements/share-functionality-022bf0d.md b/docs/06_SAP_Fiori_Elements/share-functionality-022bf0d.md
index 4734b05b..07c8be86 100644
--- a/docs/06_SAP_Fiori_Elements/share-functionality-022bf0d.md
+++ b/docs/06_SAP_Fiori_Elements/share-functionality-022bf0d.md
@@ -16,11 +16,11 @@ The "share" functionality allows users to share the current application state us
When a user chooses this option, the corresponding *Save as Tile* dialog is displayed. When a user chooses the tile, the application page opens in the same state in which the tile was created. Application developers can customize the title and the sub-title of the tile. In the list report, a dynamic tile with a record count is created, where the applied filter is also taken into account.
-- *Share Menu: Microsoft Teams*
+- *Share: Microsoft Teams*
- When a user clicks the *Share* button and then the *Share Menu: Microsoft Teams* option, a separate window opens with the available sharing options:
+ When a user clicks the *Share* button and then the *Share: Microsoft Teams* option, a separate window opens with the available sharing options:
- As Chat
@@ -33,11 +33,11 @@ The "share" functionality allows users to share the current application state us
Please note the following:
- - The *Share Menu: Microsoft Teams* option is only available if the required settings have been made by the system administrators of SAP S/4HANA Cloud.
+ - The *Share: Microsoft Teams* option is only available if the required settings have been made by the system administrators of SAP S/4HANA Cloud.
For more information, see [Integrating Microsoft Teams](https://help.sap.com/docs/SAP_S4HANA_CLOUD/0f69f8fb28ac4bf48d2b57b9637e81fa/257ec7408db6420682462cd1d000e744.html).
- - The *Share Menu: Microsoft Teams* option is part of collaborative ERP \(enterprise resource planning\), which integrates the best of SAP S/4HANA Cloud with Microsoft Teams. So this option is not available for all users.
+ - The *Share: Microsoft Teams* option is part of collaborative ERP \(enterprise resource planning\), which integrates the best of SAP S/4HANA Cloud with Microsoft Teams. So this option is not available for all users.
@@ -53,6 +53,8 @@ The "share" functionality allows users to share the current application state us
> - In SAP Fiori elements for OData V2, for draft objects with an existing active instance the "share" functionality will directly share the URL of the active instance.
>
> In SAP Fiori elements for OData V4, for draft objects with an existing active instance the "share" functionality will use the semantic bookmarking feature \(see the corresponding section in this topic below\), but if semantic keys are not defined then the URL of the active instance is shared.
+>
+> - The *Share: Microsoft Teams* functionality uses application states to shorten long URLs. These application state records are cleaned up in case they aren't accessed for a long time. For more information, see [Cleanup of Expired Application State](https://help.sap.com/docs/ABAP_PLATFORM_NEW/a7b390faab1140c087b8926571e942b7/6107ee41f89a43c9af0aa279fe039cca.html).
diff --git a/docs/06_SAP_Fiori_Elements/store-restore-the-application-state-46bf248.md b/docs/06_SAP_Fiori_Elements/store-restore-the-application-state-46bf248.md
index ffbf6d9c..186da892 100644
--- a/docs/06_SAP_Fiori_Elements/store-restore-the-application-state-46bf248.md
+++ b/docs/06_SAP_Fiori_Elements/store-restore-the-application-state-46bf248.md
@@ -27,7 +27,7 @@ The state of the application is preserved when users refresh or navigate away fr
- > ### Note:
> - If a potentially sensitive field \(a property that is annotated via the `PersonalData.v1.IsPotentiallySensitive` annotation\) is changed, SAP Fiori elements doesn't store/restore this information. Any changes added by users are therefore lost upon refresh. This is not applicable if the field is used in filter context.
>
- > - Changes to the visibility of filter fields in the filter bar aren't stored/restored. However, if any new filter fields containing values are added from the *Adapt Filters* dialog, then they are stored as a part of the `iAppState`.
+ > - In SAP Fiori elements for OData V2, changes to the visibility of filter fields in the filter bar aren't stored/restored. However, if any new filter fields containing values are added from the *Adapt Filters* dialog, then they are stored as a part of the `iAppState`.
>
> - Selections in a chart and a table, as well as the scroll position in a table, are not stored/restored.
>
@@ -74,7 +74,7 @@ Changes coming in from other flex layers, such as changes made by key users, are
> ### Note:
> - Any filter field value coming from other layers is still overwritten by values for this field coming from SAP Fiori launchpad. For more information, see [Configuring Default Filter Values](configuring-default-filter-values-f27ad7b.md).
>
-> - The logic that allows changes from other layers to be merged by the flex layer with the changes coming from an end user is only applied if the variant within the `iAppState` is available at the time when the restore takes place. If this is not the case, for example when the page was shared to another user and the target user doesn't have access to the variant shared in the `iAppState`, then the app loads using the *Standard* variant and the full state of the page when it is shared is applied on top, meaning without any other layer changes.
+> - The logic that allows changes from other layers to be merged by the flex layer with the changes coming from an end user is only applied if the variant within the `iAppState` is available at the time when the restore takes place. If this is not the case, for example when the page was shared to another user and the target user doesn't have access to the variant shared in the `iAppState`, then the app loads using the *Standard* variant and the full state of the page when it is shared is applied on top, meaning without any other layer changes. When this happens, the following changes will not be retained: the filter fields or table columns that were removed and changes in the filter field or table column position.
>
> - For a single-valued field, the merge logic always has priority over the other layer value \(the value of the key user, for example\) and the changes made by the end user for the same field are ignored.
>
diff --git a/docs/06_SAP_Fiori_Elements/the-chart-building-block-52d065a.md b/docs/06_SAP_Fiori_Elements/the-chart-building-block-52d065a.md
index bb21e3a0..fc01c477 100644
--- a/docs/06_SAP_Fiori_Elements/the-chart-building-block-52d065a.md
+++ b/docs/06_SAP_Fiori_Elements/the-chart-building-block-52d065a.md
@@ -10,7 +10,7 @@ The `Chart` building block provides an easy way to instantiate a chart based on
## Usage
-Make sure that the entity set referred for the `Chart` building block supports aggregation, as described under *Enabling Aggregation in the Back End* in the section *Additional Features in SAP Fiori Elements for OData V4* in [Configuring Charts](configuring-charts-653ed0f.md).
+Ensure that the entity set referred for the `Chart` building block supports aggregation. For more information , see the subsection *Enabling Aggregation in the Back End* in [Configuring Charts](configuring-charts-653ed0f.md).
> ### Sample Code:
> `Chart` Building Block
diff --git a/docs/06_SAP_Fiori_Elements/the-filterbar-building-block-7838611.md b/docs/06_SAP_Fiori_Elements/the-filterbar-building-block-7838611.md
index 9425bda8..9b293b02 100644
--- a/docs/06_SAP_Fiori_Elements/the-filterbar-building-block-7838611.md
+++ b/docs/06_SAP_Fiori_Elements/the-filterbar-building-block-7838611.md
@@ -16,7 +16,10 @@ The `FilterBar` building block allows application developers to embed a filter b
> />
> ```
-Default values via `UI.SelectionVariant` and `Common.FilterDefaultValue` as well as custom filters are supported. Check out our live example in the flexible programming model explorer at [Filter Bar](https://ui5.sap.com/test-resources/sap/fe/core/fpmExplorer/index.html#/buildingBlocks/filterBar/filterBarDefault).
+Default values via `UI.SelectionVariant` and `Common.FilterDefaultValue` as well as custom filters are supported. Check out our live example in the flexible programming model explorer at [Filter Bar - Overview](https://ui5.sap.com/test-resources/sap/fe/core/fpmExplorer/index.html#/buildingBlocks/filterBar/filterBarDefault).
+
+> ### Restriction:
+> The `FilterBar` building block has no provision to bring up the visual filter bar.
@@ -26,10 +29,25 @@ Default values via `UI.SelectionVariant` and `Common.FilterDefaultValue` as well
Applications can programmatically trigger the filter search on initial load using the `triggerSearch()` method. When called, it first validates that all the mandatory filter fields are filled out. The filter bar 'Go' is triggered only if all of them have valid values. If any of the mandatory filter fields aren't filled out, the focus is set to the first mandatory filter field that isn't filled. Note that in this case, the field won't be highlighted and no error messages will be sent to the user.
-For more information, see the [API Reference](https://ui5.sap.com/#/api/sap.fe.macros.FilterBar%23methods/triggerSearch) page. You can also check out our live example in the flexible programming model explorer at [Filter Bar](https://ui5.sap.com/test-resources/sap/fe/core/fpmExplorer/index.html#/buildingBlocks/filterBar/filterBarAnnotationDefaults).
+Check out our live example in the flexible programming model explorer at [Filter Bar - Default Values](https://ui5.sap.com/test-resources/sap/fe/core/fpmExplorer/index.html#/buildingBlocks/filterBar/filterBarAnnotationDefaults).
+
+
+
+
+
+## Using the SelectionVariant Format
+
+The following methods are available for interacting with the `FilterBar` building block using the `SelectionVariant` format:
+
+- `async getSelectionVariant () : Promise`
+
+- `async setSelectionVariant (selectionVariant : SelectionVariant)`
+
+
+Check out our live example in the flexible programming model explorer at [Filter Bar - Interacting with the Filter Bar via Selection Variant Format \(get and set\)](https://ui5.sap.com/test-resources/sap/fe/core/fpmExplorer/index.html#/buildingBlocks/filterBar/filterBarSVPublicAPIs).
> ### Restriction:
-> The `FilterBar` building block has no provision to bring up the visual filter bar.
+> Custom filters are not part of the `getSelectionVariant` and `setSelectionVariant` APIs.
diff --git a/docs/06_SAP_Fiori_Elements/visual-filters-1714720.md b/docs/06_SAP_Fiori_Elements/visual-filters-1714720.md
index ead5bf2d..ed29c988 100644
--- a/docs/06_SAP_Fiori_Elements/visual-filters-1714720.md
+++ b/docs/06_SAP_Fiori_Elements/visual-filters-1714720.md
@@ -801,7 +801,7 @@ Change the project value from `List Report` to `Analytical List Page` on the fil
|
-Specifying ***Analytical List Page*** as a value for the project in the filter bar, re-renders charts to display records for *In Progress* and *New* status values of the Analytical List Page project.
+Specifying `Analytical List Page` as a value for the project in the filter bar, re-renders charts to display records for *In Progress* and *New* status values of the Analytical List Page project.
> ### Note:
> The in/out parameter mapping values set for the other properties in the `SelectionVariant` annotation that are not part of the project field is considered as it is.
diff --git a/docs/07_APF/adding-an-application-1eef736.md b/docs/07_APF/adding-an-application-1eef736.md
index 4563555c..affadd80 100644
--- a/docs/07_APF/adding-an-application-1eef736.md
+++ b/docs/07_APF/adding-an-application-1eef736.md
@@ -50,7 +50,7 @@ Semantic Object
|
-For SAP Business Suite powered by SAP HANA, this field is prefilled with ***FioriApplication***. Keep this default entry if you use the generic APF runtime application. You can change the semantic object any time, but the entry here must be the same as the one you make when configuring the Smart Business KPI tile. In the KPI tile configuration, the semantic object filters the list of configurations so that only those are listed that have been created for the specified semantic object. Otherwise you have to type in your configuration manually.
+For SAP Business Suite powered by SAP HANA, this field is prefilled with `FioriApplication`. Keep this default entry if you use the generic APF runtime application. You can change the semantic object any time, but the entry here must be the same as the one you make when configuring the Smart Business KPI tile. In the KPI tile configuration, the semantic object filters the list of configurations so that only those are listed that have been created for the specified semantic object. Otherwise you have to type in your configuration manually.
For SAP S/4HANA, this field is not relevant and can be left empty.
diff --git a/docs/07_APF/application-configuration-in-sapui5-1-28-and-prior-releases-c9da7d5.md b/docs/07_APF/application-configuration-in-sapui5-1-28-and-prior-releases-c9da7d5.md
index 0fc5fe27..cda138f6 100644
--- a/docs/07_APF/application-configuration-in-sapui5-1-28-and-prior-releases-c9da7d5.md
+++ b/docs/07_APF/application-configuration-in-sapui5-1-28-and-prior-releases-c9da7d5.md
@@ -175,7 +175,7 @@ Contains two properties:
Specifies the service to determine the logical system.
- In most cases, you can set the service to ***null***.
+ In most cases, you can set the service to `null`.
diff --git a/docs/07_APF/configuring-the-sap-smart-business-kpi-tile-374364e.md b/docs/07_APF/configuring-the-sap-smart-business-kpi-tile-374364e.md
index 0c16464b..60d63342 100644
--- a/docs/07_APF/configuring-the-sap-smart-business-kpi-tile-374364e.md
+++ b/docs/07_APF/configuring-the-sap-smart-business-kpi-tile-374364e.md
@@ -116,7 +116,7 @@ The following sections differentiate the data you must enter depending on the us
## Using the SAP Smart Business Modeler Apps for SAP Business Suite powered by SAP HANA
-To configure a KPI tile for an APF-based application, open the *Configure KPI Tiles* app, go to the *Navigation* area and select the *Other Drill-Down* radio button. Select ***Analysis Path Framework*** as drill-down.
+To configure a KPI tile for an APF-based application, open the *Configure KPI Tiles* app, go to the *Navigation* area and select the *Other Drill-Down* radio button. Select `Analysis Path Framework` as drill-down.
Depending on your use case, enter the following data:
@@ -321,7 +321,7 @@ By clicking *Save and Configure Drill-Down*, you can navigate to the APF Configu
> ### Note:
> The KPI Modeler for SAP S/4HANA may also be used on SAP Business Suite powered by SAP HANA.
-To configure a KPI tile for an APF-based application in the SAP Smart Business modeler apps for SAP S/4HANA, open the *Create Tile* app and select your tile or create a new one. In the *Navigation* area, go to the *Select Drill-Down* field and select ***Analysis Path Framework***.
+To configure a KPI tile for an APF-based application in the SAP Smart Business modeler apps for SAP S/4HANA, open the *Create Tile* app and select your tile or create a new one. In the *Navigation* area, go to the *Select Drill-Down* field and select `Analysis Path Framework`.
Depending on your use case, enter the following data:
@@ -374,7 +374,7 @@ As defined in target mapping of the application
|
- ***FioriApplication*** \(automatically filled based on selected configuration\)
+ `FioriApplication` \(automatically filled based on selected configuration\)
@@ -404,7 +404,7 @@ As defined in target mapping of the application
|
- ***executeAPFConfigurationS4HANA*** or ***executeAPFConfiguration***\(automatically filled based on selected configuration.\)
+ `executeAPFConfigurationS4HANA` or `executeAPFConfiguration`\(automatically filled based on selected configuration.\)
diff --git a/docs/07_APF/creating-navigation-targets-d5762bc.md b/docs/07_APF/creating-navigation-targets-d5762bc.md
index 14c18de6..2ea073a2 100644
--- a/docs/07_APF/creating-navigation-targets-d5762bc.md
+++ b/docs/07_APF/creating-navigation-targets-d5762bc.md
@@ -67,7 +67,7 @@ Semantic object as defined in the corresponding target mapping configured in the
Semantic object as defined by the Fiori launchpad configuration.
> ### Note:
-> Currently, you can only navigate to other APF applications. Therefore, the semantic object must be ***FioriApplication***.
+> Currently, you can only navigate to other APF applications. Therefore, the semantic object must be `FioriApplication`.
@@ -86,7 +86,7 @@ Action
As soon as you enter a semantic object, the value help for the action is filled with all actions that are available for this target mapping and that you are authorized for. The *Action* field is prefilled with the first action in this list.
> ### Note:
-> Currently, you can only navigate to other APF applications. Therefore, the action must be ***executeAPFConfiguration***.
+> Currently, you can only navigate to other APF applications. Therefore, the action must be `executeAPFConfiguration`.
diff --git a/docs/07_APF/descriptor-manifest-json-74038a5.md b/docs/07_APF/descriptor-manifest-json-74038a5.md
index 40aaa007..aa809b0b 100644
--- a/docs/07_APF/descriptor-manifest-json-74038a5.md
+++ b/docs/07_APF/descriptor-manifest-json-74038a5.md
@@ -291,7 +291,7 @@ The following settings reside in the `sap.apf` name space:
- `activateLrep`
> ### Note:
- > If you use SAP S/4HANA, this property is mandatory and must be set to ***true***.
+ > If you use SAP S/4HANA, this property is mandatory and must be set to `true`.
This property defines that the layered repository of SAPUI5 flexibility is used for persistence of the analytical configuration.
diff --git a/docs/07_APF/enhancing-an-apf-based-application-b247999.md b/docs/07_APF/enhancing-an-apf-based-application-b247999.md
index b946097c..346c967b 100644
--- a/docs/07_APF/enhancing-an-apf-based-application-b247999.md
+++ b/docs/07_APF/enhancing-an-apf-based-application-b247999.md
@@ -9,7 +9,7 @@ You have installed an APF-based application that was shipped by SAP. If you want
1. In your SAP Fiori frontend server system, run transaction `SE80`.
-2. In the Repository Browser, select ***BSP Application*** and enter the name of your Business Server Page \(BSP\) application.
+2. In the Repository Browser, select `BSP Application` and enter the name of your Business Server Page \(BSP\) application.
3. In the folder structure, open *Page Fragments* \> *config* and double-click the analytical configuration file to open it.
diff --git a/docs/07_APF/using-the-generic-runtime-application-3aa6084.md b/docs/07_APF/using-the-generic-runtime-application-3aa6084.md
index 79e136a2..9b3edb01 100644
--- a/docs/07_APF/using-the-generic-runtime-application-3aa6084.md
+++ b/docs/07_APF/using-the-generic-runtime-application-3aa6084.md
@@ -9,7 +9,7 @@ The generic application already contains important elements that are required fo
To create a configuration and run it using the generic runtime application, proceed as follows:
1. Open the APF Configuration Modeler
-2. Click the + icon to create a new application and enter a description. The *Semantic Object* field is already filled with ***FioriApplication***. Save your application.
+2. Click the + icon to create a new application and enter a description. The *Semantic Object* field is already filled with `FioriApplication`. Save your application.
> ### Note:
> This step is not required if you use an already existing APF application and just create an additional configuration.
@@ -44,7 +44,7 @@ The following settings are relevant when you use the generic APF runtime applica
- You must activate the service `af_apf_launch` using transaction `SICF` in the Fiori frontend server system.
-- If you use BW OData queries, set the URL parameter `sap-apf-filter-reduction` to ***true***.
+- If you use BW OData queries, set the URL parameter `sap-apf-filter-reduction` to `true`.
**Related Information**
diff --git a/docs/07_APF/using-your-own-runtime-application-0d6ead1.md b/docs/07_APF/using-your-own-runtime-application-0d6ead1.md
index 975953fd..6b673794 100644
--- a/docs/07_APF/using-your-own-runtime-application-0d6ead1.md
+++ b/docs/07_APF/using-your-own-runtime-application-0d6ead1.md
@@ -132,7 +132,7 @@ The following steps are required:
|
- If you use SAP S/4HANA, this property is mandatory and must be set to ***true***. Otherwise set it to ***false***.
+ If you use SAP S/4HANA, this property is mandatory and must be set to `true`. Otherwise set it to `false`.
diff --git a/docs/09_Developing_Controls/jsdoc-guidelines-eeaa5de.md b/docs/09_Developing_Controls/jsdoc-guidelines-eeaa5de.md
index c109101d..d22be712 100644
--- a/docs/09_Developing_Controls/jsdoc-guidelines-eeaa5de.md
+++ b/docs/09_Developing_Controls/jsdoc-guidelines-eeaa5de.md
@@ -2,5 +2,5 @@
# JSDoc Guidelines
-General SAPUI5 JSDoc guidelines are available at [OpenUI5 JSDoc Guidelines](https://github.com/SAP/openui5/blob/master/docs/guidelines/jsdoc.md).
+General UI5 JSDoc guidelines are available at [OpenUI5 JSDoc Guidelines](https://github.com/SAP/openui5/blob/master/docs/guidelines/jsdoc.md).
diff --git a/docs/10_More_About_Controls/radial-micro-chart-aa93bdb.md b/docs/10_More_About_Controls/radial-micro-chart-aa93bdb.md
index 5017f665..f5919966 100644
--- a/docs/10_More_About_Controls/radial-micro-chart-aa93bdb.md
+++ b/docs/10_More_About_Controls/radial-micro-chart-aa93bdb.md
@@ -23,7 +23,7 @@ The percentage value in the `RadialMicroChart` control can be defined by:
- Setting the total and the fraction property and calculating the percentage value automatically.
> ### Note:
- > If the total property is set to ***0***, only a blank circle gets rendered because no valid value is returned. The error is described in the error log.
+ > If the total property is set to `0`, only a blank circle gets rendered because no valid value is returned. The error is described in the error log.
**Colors**
diff --git a/docs/10_More_About_Controls/sap-ui-mdc-experimental-1dd2aa9.md b/docs/10_More_About_Controls/sap-ui-mdc-experimental-1dd2aa9.md
index 1316f755..8677e703 100644
--- a/docs/10_More_About_Controls/sap-ui-mdc-experimental-1dd2aa9.md
+++ b/docs/10_More_About_Controls/sap-ui-mdc-experimental-1dd2aa9.md
@@ -5,7 +5,7 @@
The `sap.ui.mdc` library contains composite, metadata-driven controls that assemble UI elements with predefined user experience and various functionalities. The controls can be used as a basis for scalable application development and can be implemented for use with any SAPUI5 model and data protocol.
> ### Note:
-> In the context of OData V4, the `sap.ui.mdc` library can only be used with SAP Fiori elements.
+> For SAPUI5 applications for OData V4, SAP Fiori elements provides a flexible programming model based on the `sap.ui.mdc` library. It offers building blocks that can be used without additional integration effort. For more information, see [Building Blocks](../06_SAP_Fiori_Elements/building-blocks-24c1304.md).
> ### Note:
> The following sections only provide additional information for some of the controls. For a complete list of all controls and their documentation, see the [API Reference](https://ui5.sap.com/#/api) and the [Samples](https://ui5.sap.com/#/controls).
diff --git a/docs/10_More_About_Controls/sap-ui-vk-9be7f96.md b/docs/10_More_About_Controls/sap-ui-vk-9be7f96.md
index 186dee14..2fd3602c 100644
--- a/docs/10_More_About_Controls/sap-ui-vk-9be7f96.md
+++ b/docs/10_More_About_Controls/sap-ui-vk-9be7f96.md
@@ -13,9 +13,9 @@ Applications use the `sap.ui.vk` namespace. All other namespaces \(`sap.ui.vk.dv
The selection of the 3D rendering engine is done using the `sap.ui.vk.ContentResource` object and its parameter `sourceType`.
-- To use the legacy DVL rendering engine, set the `sourceType` parameter to ***vds***.
+- To use the legacy DVL rendering engine, set the `sourceType` parameter to `vds`.
-- To use the ThreeJs rendering engine, set the `sourceType` parameter to ***vds4***.
+- To use the ThreeJs rendering engine, set the `sourceType` parameter to `vds4`.
All examples and screenshots in this document use the **ThreeJs** rendering engine.
diff --git a/docs/10_More_About_Controls/smart-area-micro-chart-283cdca.md b/docs/10_More_About_Controls/smart-area-micro-chart-283cdca.md
index 5670c0ed..9a79950c 100644
--- a/docs/10_More_About_Controls/smart-area-micro-chart-283cdca.md
+++ b/docs/10_More_About_Controls/smart-area-micro-chart-283cdca.md
@@ -17,7 +17,7 @@ By using the `chartType` property *Area* of the *UI.Chart* annotation the corres
**Binding**
-The `SmartAreaMicroChart` control supports only `enableAutoBinding` = ***true***. This means it should be bound to only **one** entitySet, and should get a navigation property as a chartBindingPath to an entitySet \(for the relative binding\) or else the `entitySet` property will be used for the absolute binding.
+The `SmartAreaMicroChart` control supports only `enableAutoBinding` = `true`. This means it should be bound to only **one** entitySet, and should get a navigation property as a chartBindingPath to an entitySet \(for the relative binding\) or else the `entitySet` property will be used for the absolute binding.
**Colors of the Chart \(Criticality\)**
@@ -70,7 +70,7 @@ The control provides the *Title*, *Description* or *UnitOfMeasure* values retrie
For more information about the supported annotation terms *ISOCurrency* and *Unit*, see [http://docs.oasis-open.org/odata/odata/v4.0/os/vocabularies/Org.OData.Measures.V1.xml](http://docs.oasis-open.org/odata/odata/v4.0/os/vocabularies/Org.OData.Measures.V1.xml).
- The control takes into account only the *measure* annotation for the `entityType` property that is addressed by the `Value` property of the *DataPoint* annotation. In the following example, the `Value` property of the *DataPoint* points to the `Price` property in the `EntityType` \(`Path`="***Price***"\). This means that the control \(`Path`="***Currency***"\) uses the *measure* annotation with `Target="AmcNamespace.StockPrice/Price"`:
+ The control takes into account only the *measure* annotation for the `entityType` property that is addressed by the `Value` property of the *DataPoint* annotation. In the following example, the `Value` property of the *DataPoint* points to the `Price` property in the `EntityType` \(`Path`="`Price`"\). This means that the control \(`Path`="`Currency`"\) uses the *measure* annotation with `Target="AmcNamespace.StockPrice/Price"`:
```xml
diff --git a/docs/10_More_About_Controls/smart-bullet-micro-chart-b28959d.md b/docs/10_More_About_Controls/smart-bullet-micro-chart-b28959d.md
index 5dbd2b4f..3f70fcb7 100644
--- a/docs/10_More_About_Controls/smart-bullet-micro-chart-b28959d.md
+++ b/docs/10_More_About_Controls/smart-bullet-micro-chart-b28959d.md
@@ -15,7 +15,7 @@ By using the `chartType` property *Bullet* of the *UI.Chart* annotation the corr
## Binding
-The `SmartBulletMicroChart` control should be bound to **one** entity, and not a collection of entities \(entitySet\). It supports both `enableAutoBinding` = ***false*** \(no binding is done inside the control\) and `enableAutoBinding` = ***true*** :
+The `SmartBulletMicroChart` control should be bound to **one** entity, and not a collection of entities \(entitySet\). It supports both `enableAutoBinding` = `false` \(no binding is done inside the control\) and `enableAutoBinding` = `true` :
- If the `chartBindingPath` is provided, the control will be bound relatively to it. For example, the `chartBindingPath` can be a navigation property.
@@ -25,7 +25,7 @@ The `SmartBulletMicroChart` control should be bound to **one** entity, and not a
For information on how the control provides *Title*, *Description* and *UnitOfMeasure* values retrieved from the annotations, please see the *Title, Description and UnitOfMeasures* section in the [Smart Area Micro Chart](smart-area-micro-chart-283cdca.md) documentation.
> ### Note:
-> If `enableAutoBinding` = ***true*** and `chartBindingPath` is set then the `bindingContext` for the *Title*, *Description* and *UnitOfMeasure* is set to the value as well.
+> If `enableAutoBinding` = `true` and `chartBindingPath` is set then the `bindingContext` for the *Title*, *Description* and *UnitOfMeasure* is set to the value as well.
diff --git a/docs/10_More_About_Controls/smart-radial-micro-chart-f8b3103.md b/docs/10_More_About_Controls/smart-radial-micro-chart-f8b3103.md
index 7db22d5b..f180af00 100644
--- a/docs/10_More_About_Controls/smart-radial-micro-chart-f8b3103.md
+++ b/docs/10_More_About_Controls/smart-radial-micro-chart-f8b3103.md
@@ -27,7 +27,7 @@ In addition, the Smart Radial Micro Chart supports a *FreeText* value. This can
## Binding
-The `SmartRadialMicroChart` control should be bound to **one** entity and not to a collection of entities \(entitySet\). It supports both `enableAutoBinding` = ***false*** \(no binding is done inside the control\) and `enableAutoBinding` = ***true*** :
+The `SmartRadialMicroChart` control should be bound to **one** entity and not to a collection of entities \(entitySet\). It supports both `enableAutoBinding` = `false` \(no binding is done inside the control\) and `enableAutoBinding` = `true` :
- If the `chartBindingPath` is provided, the control will be bound relatively to it. For example, the `chartBindingPath` can be a navigation property.
@@ -35,7 +35,7 @@ The `SmartRadialMicroChart` control should be bound to **one** entity and not to
> ### Note:
-> If `enableAutoBinding` = ***true*** and `chartBindingPath` is set then the `bindingContext` for the *Title*, *Description*, *UnitOfMeasure* and *FreeText* is set to the value as well.
+> If `enableAutoBinding` = `true` and `chartBindingPath` is set then the `bindingContext` for the *Title*, *Description*, *UnitOfMeasure* and *FreeText* is set to the value as well.
diff --git a/docs/css/BusinessSuiteInAppSymbols.woff b/docs/css/BusinessSuiteInAppSymbols.woff
new file mode 100644
index 00000000..5a1bb492
Binary files /dev/null and b/docs/css/BusinessSuiteInAppSymbols.woff differ
diff --git a/docs/css/NS-SAP-icons.woff b/docs/css/NS-SAP-icons.woff
new file mode 100644
index 00000000..3bb4bd88
Binary files /dev/null and b/docs/css/NS-SAP-icons.woff differ
diff --git a/docs/css/sap-icons.css b/docs/css/sap-icons.css
index 276e21c2..2caab9a9 100644
--- a/docs/css/sap-icons.css
+++ b/docs/css/sap-icons.css
@@ -1,6 +1,8 @@
@font-face{font-family:'Ariba_icon_library';src: url('./Ariba_icon_library-Regular.woff') format('woff');font-weight: normal;font-style: normal;}
@font-face{font-family:'SAPGUI-Belize-Icons';src:url('./SAPGUI-Belize-Icons.ttf') format('truetype');font-weight:normal;font-style:normal;}
@font-face{font-family:'BusinessSuiteInAppSymbols';src: url('./BusinessSuiteInAppSymbols.woff') format('woff');font-weight: normal;font-style: normal;}
+@font-face{font-family:'BusinessSuiteInAppSymbols-V1';src: url('./BusinessSuiteInAppSymbols-V1.woff') format('woff');font-weight: normal;font-style: normal;}
+@font-face{font-family:'BusinessSuiteInAppSymbols-V2';src: url('./BusinessSuiteInAppSymbols-V2.woff') format('woff');font-weight: normal;font-style: normal;}
@font-face{font-family:'bwicons';src: url('./bwicons.ttf') format('truetype');font-weight: normal;font-style: normal;}
@font-face{font-family:'FPA-icons';src: url('./FPA-icons.woff') format('woff');font-weight: normal;font-style: normal;}
@font-face{font-family:'ITOA_FontIcon';src: url('./ITOA_FontIcon.eot');src: url('./ITOA_FontIcon.eot?#iefix') format('embedded-opentype'),url('./ITOA_FontIcon.ttf') format('truetype');font-weight: normal;font-style: normal;}
@@ -10,7 +12,9 @@
@font-face{font-family:'SAP-icons';src: url('./SAP-icons.woff') format('woff');font-weight: normal;font-style: normal;}
@font-face{font-family:'SAPiconsV3-2';src: url('./SAPiconsV3-2.ttf') format('truetype');font-weight: normal;font-style: normal;}
@font-face{font-family:'SAPiconsV3-6';src: url('./SAPiconsV3-6.ttf') format('truetype');font-weight:normal;font-style:normal;}
+@font-face{font-family:'SAP-icons-V4';src: url('./SAP-icons-V4.woff') format('woff');font-weight: normal;font-style: normal;}
@font-face{font-family:'SAPiconsV4-1';src: url('./SAPiconsV4-1.ttf') format('truetype');font-weight:normal;font-style:normal;}
+@font-face{font-family:'SAP-icons-V5';src: url('./SAP-icons-V5.woff') format('woff');font-weight: normal;font-style: normal;}
@font-face{font-family:'SAP-icons-extended';src: url('./SAP-icons-extended.woff') format('woff');font-weight:normal;font-style:normal;}
@font-face{font-family:'SAP-icons-TNT';src: url('./SAP-icons-TNT.woff') format('woff');font-weight: normal;font-style: normal;}
@font-face{font-family:'SAP-icons-watt';src: url('./SAP-icons-watt.ttf') format('truetype');font-weight:normal;font-style:normal;}
@@ -20,6 +24,8 @@
.Ariba-icons {font-family:Ariba_icon_library;}
.Belize-icons {font-family:SAPGUI-Belize-Icons;}
.BusinessSuiteInAppSymbols {font-family:BusinessSuiteInAppSymbols;}
+.BusinessSuiteInAppSymbols-V1 {font-family:BusinessSuiteInAppSymbols-V1;}
+.BusinessSuiteInAppSymbols-V2 {font-family:BusinessSuiteInAppSymbols-V2;}
.BW-icons {font-family:bwicons;}
.FPA-icons {font-family:FPA-icons;}
.ITOA_FontIcon {font-family:ITOA_FontIcon;}
@@ -29,7 +35,9 @@
.SAP-icons {font-family:SAP-icons;}
.SAPiconsV3-2 {font-family:SAPiconsV3-2;}
.SAPiconsV3-6 {font-family:SAPiconsV3-6;}
+.SAP-icons-V4 {font-family:SAP-icons-V4;}
.SAPiconsV4-1 {font-family:SAPiconsV4-1;}
+.SAP-icons-V5 {font-family:SAP-icons-V5;}
.SAP-icons-extended {font-family:SAP-icons-extended;}
.SAP-icons-TNT {font-family:SAP-icons-TNT;}
.SAP-icons-watt {font-family:SAP-icons-watt;}
diff --git a/docs/index.md b/docs/index.md
index 75535077..2f1fea77 100644
--- a/docs/index.md
+++ b/docs/index.md
@@ -4,9 +4,10 @@ Demo Kit Version
- [SAPUI5: UI Development Toolkit for HTML5](sapui5-ui-development-toolkit-for-html5-95d113b.md)
- [What's New in SAPUI5](01_Whats-New/what-s-new-in-sapui5-99ac68a.md)
+ - [What's New in SAPUI5 1.116](01_Whats-New/what-s-new-in-sapui5-1-116-ebd6f34.md)
- [What's New in SAPUI5 1.115](01_Whats-New/what-s-new-in-sapui5-1-115-409fde8.md)
- - [What's New in SAPUI5 1.114](01_Whats-New/what-s-new-in-sapui5-1-114-890fce1.md)
- [Previous Versions](01_Whats-New/previous-versions-6660a59.md)
+ - [What's New in SAPUI5 1.114](01_Whats-New/what-s-new-in-sapui5-1-114-890fce1.md)
- [What's New in SAPUI5 1.113](01_Whats-New/what-s-new-in-sapui5-1-113-a9553fe.md)
- [What's New in SAPUI5 1.112](01_Whats-New/what-s-new-in-sapui5-1-112-34afc69.md)
- [What's New in SAPUI5 1.111](01_Whats-New/what-s-new-in-sapui5-1-111-7a67837.md)
@@ -80,6 +81,7 @@ Demo Kit Version
- [UI5-TypeScript](02_Read-Me-First/the-ui5-ecosystem-b72ccb5.md#loioab4f18de7652442da85fc08b38a8a8ce)
- [wdi5](02_Read-Me-First/the-ui5-ecosystem-b72ccb5.md#loiof92b537272ba43abbfc157ba4ec8f010)
- [Best of UI5](02_Read-Me-First/the-ui5-ecosystem-b72ccb5.md#loio23a0a11a88df42578b5baae11c06a89b)
+ - [TypeScript in SAPUI5](02_Read-Me-First/typescript-in-sapui5-a7ee961.md)
- [Compatibility Rules](02_Read-Me-First/compatibility-rules-91f0873.md)
- [Browser and Platform Support](02_Read-Me-First/browser-and-platform-support-74b59ef.md)
- [Visual Degradations](02_Read-Me-First/visual-degradations-f08f296.md)
@@ -908,7 +910,7 @@ Demo Kit Version
- [Settings for Object Page Tables](06_SAP_Fiori_Elements/settings-for-object-page-tables-47425bb.md)
- [Adding Titles to Object Page Tables](06_SAP_Fiori_Elements/adding-titles-to-object-page-tables-d9a4539.md)
- [Adding Segmented Buttons to a Table Toolbar](06_SAP_Fiori_Elements/adding-segmented-buttons-to-a-table-toolbar-5532c89.md)
- - [Enabling Inline Creation Mode or Empty Rows Mode for Table Entries](06_SAP_Fiori_Elements/enabling-inline-creation-mode-or-empty-rows-mode-for-table-entries-cfb04f0.md)
+ - [Enabling Inline Creation Mode or Empty Row Mode for Table Entries](06_SAP_Fiori_Elements/enabling-inline-creation-mode-or-empty-row-mode-for-table-entries-cfb04f0.md)
- [Generic Action Buttons in Tables on the Object Page: Additional Considerations](06_SAP_Fiori_Elements/generic-action-buttons-in-tables-on-the-object-page-additional-considerations-d27ae99.md)
- [Adding Two Tables in a Subsection](06_SAP_Fiori_Elements/adding-two-tables-in-a-subsection-17564c2.md)
- [Rebinding a Table with Each Instance Change on an Object Page](06_SAP_Fiori_Elements/rebinding-a-table-with-each-instance-change-on-an-object-page-a6946a8.md)
diff --git a/docs/sapui5-ui-development-toolkit-for-html5-95d113b.md b/docs/sapui5-ui-development-toolkit-for-html5-95d113b.md
index 04d6dbb4..4e36d053 100644
--- a/docs/sapui5-ui-development-toolkit-for-html5-95d113b.md
+++ b/docs/sapui5-ui-development-toolkit-for-html5-95d113b.md
@@ -2,7 +2,7 @@
# SAPUI5: UI Development Toolkit for HTML5
-Create apps with rich user interfaces for modern web business applications, responsive across browsers and devices, based on HTML5. \(Documentation patch 1.115.0\)
+Create apps with rich user interfaces for modern web business applications, responsive across browsers and devices, based on HTML5. \(Documentation patch 1.116.0\)
|