Attribute |
Version* |
Description |
---|---|---|
sap.ui5/dependencies/minUI5Version |
V64 (1.124) | The attribute minUI5Version can now be an array of
versions where each major version can only be included once. If you specify an
array that contains more than one version, and if version 1 is included, it must
be at least 1.120.x. |
|
V51 (1.110) |
Release status for the developer adaptation in SAP S/4HANA Cloud Public Edition and SAP BTP, ABAP environment (SAP-internal). Supported types:
For more information, see Releasing an SAP Fiori Application to Be Extensible in Adaptation Projects on SAP S/4HANA Cloud and SAP BTP, ABAP Environment. |
(deprecated) |
V37 (1.94) |
Since 1.94 the usage of |
|
V35 (1.92) |
Dictionary of (catalog) objects offered by an INA datasource, consisting of:
{ ... "dataSources": { "cdsService": { "uri": "/sap/bc/ina/ina1/sap/example_cds", "type": "INA", "settings": { "localUri": "localService/metadata.xml", "objects": { "assets": { "objectName": "SAPFinAssets", "objectType": "cdsprojectionview", "packageName": "package", "schemaName": "schema" }, "liabilities": { "objectName": "SAPFinLiabilities", "objectType": "cdsprojectionview" } } } } }, ... } |
|
V32 (1.87) |
Indicates whether an app is an abstract (generic) app, which may not used directly, but needs to be specialized in the SAP Fiori launchpad content. { ... "sap.fiori": { "registrationIds": [ "F1234" ], "archeType": "transactional", "abstract": false }, ... } |
|
V22 (1.77) |
The Additional resource bundles can be made available by defining
{ ... "models": { "i18n": { "type": "sap.ui.model.resource.ResourceModel", "settings": { "bundleName": "myapp.i18n.i18n", "supportedLocales": ["de", "en"], "fallbackLocale": "de", "terminologies": { "sports": { "bundleUrl": "i18n/terminologies/sports/i18n.terminologies.sports.properties", "bundleUrlRelativeTo": "manifest", "supportedLocales": ["en", "de"] }, "travel": { "bundleUrl": "i18n/terminologies/travel/i18n.terminologies.travel.properties", "bundleUrlRelativeTo": "manifest", "supportedLocales": ["en", "de"] }, "services": { "bundleUrl": "i18n/terminologies/services/i18n.terminologies.services.properties", "bundleUrlRelativeTo": "manifest", "supportedLocales": ["en", "de"] } } } } } ... } |
|
V20 (1.75) |
The { ... "componentUsages": { "myreuse": { "name": "reuse.component", ... } }, "routing": { "config": { ... }, "routes": [{ "name": "home", "pattern": "", "target": { "name": "attachment", "prefix": "atch", "propagateTitle": true } }], "targets": { "attachment": { "type": "Component", "usage": "myreuse", "options": { ... }, ... } } } ... } |
|
V17 (1.70) |
Specifies provided commands with a unique key/alias. { ... "commands": { "Save": { "shortcut": "Ctrl+S" } }, ... } |
|
V16 (1.66) |
A component can be configured as a routing target by defining it in the
{ ... "componentUsages": { "myreuse": { "name": "reuse.component", "settings": {}, "componentData": {}, "lazy": false } }, "routing": { "config": { ... }, "routes": [{ "name": "home", "pattern": "", "target": { "name": "attachment", "prefix": "atch" } }], "targets": { "attachment": { "type": "Component", "usage": "myreuse", "options": { // optional // define the additional parameter for // instantiating the component instance }, "containerOptions": { // optional // define the additional parameter for // instantiating the component container // which enables the component to be rendered // in the parent control }, "controlId": "page", "controlAggregation": "content" } } } ... } |
|
V15 (1.62) |
A routing target can load either a view or a component. With the { "routing": { "config": { ... }, "routes": [ ... ], "targets": { "/attachment/": { "type": "Component", "path": "reuse.component", "name": "attachment", "options": { ... }, "containerOptions": { ... }, "controlId": "page", "controlAggregation": "content" } } } } |
|
V12 (1.56) |
The attribute Additional attributes can be found in Terminologies. { ... "models": { "i18n": { "type": "sap.ui.model.resource.ResourceModel", "uri": "i18n/i18n.properties", "settings": { "enhanceWith": [{ "bundleUrl": "i18n/i18n.properties", "bundleUrlRelativeTo": "manifest" }] } }, ... }, ... } |
|
V12 (1.56) |
Indicates whether the component usage should be lazily loaded. Default value:
For more information see:Using and Nesting Components { ... "componentUsages": { "myusage": { "name": "my.used", "settings": {}, "componentData": {}, "lazy": false } }, ... } |
|
V10 (1.52) |
Determines whether the library contains an i18n resource. The value can be either a boolean, a string, or (since 1.78) an object. A string value represents a bundle URL. Relative URLs are always resolved to
the library origin. If no value is set, the default
An object can contain additional resource bundle configuration, e.g.
terminologies and supported locales. For the supported features and for
sample definitions, see the respective entries at Terminologies (without
This attribute is beneficial if the name of the main resource bundle (properties file) used by your UI5 library differs from the default name messagebundle.properties { ... "library": { "i18n": true }, ... } |
|
V8 (1.48) |
Specifies the used components with the a unique key/alias. Contains the following:
For more information see:Using and Nesting Components { ... "componentUsages": { "myusage": { "name": "my.used", "settings": {}, "componentData": {} } }, ... } |
|
V6 (1.42) |
Allows to define titles declaratively in the configuration
( { ..., "routes": [{ "pattern": "product/{id}/parts", "name": "ProductParts", "target": ["product", "productParts"], "titleTarget": "productParts" }], "targets": { "product": { "type": "View", "path": "shop.products", "name": "Product", "title": "Product" }, "productParts": { "type": "View", "path": "shop.products", "name": "Product", "title": "Product Parts" } }, ... } |
|
V5 (1.38) |
Defines whether or not the model is initialized (preloaded) before the component instance is created and while loading the component preload and its dependencies "equipment": { "preload": true, "dataSource": "equipment", ... } |
|
V4 (1.34) |
General setting for routing that indicates how the views are loaded; if set
to For performance reasons, we recommend to always use the
"sap.ui5": { "_version": "1.2.0", ... "routing": { "config": { "viewType": "XML", "async": true ... }, ... |
|
V4 (1.34) |
If Example for "sap.ui5": { "_version": "1.2.0", ... "dependencies": { "minUI5Version": "1.34.0", "libs": { "sap.m": { "minVersion": "1.34.0" }, "sap.ui.commons": { "minVersion": "1.34.0", "lazy": true } }, "components": { "sap.ui.app.other": { "minVersion": "1.1.0" "lazy": true } } }, |
|
V4 (1.34) |
Indicates whether an app shall run in full screen mode ( "sap.ui": { "_version": "1.3.0", "technology": "UI5", ... "fullWidth": true |
|
V4 (1.34) |
Used to overwrite the
Text symbols must be part of the properties file which is defined in
"sap.app": { "_version": "1.3.0", ... "crossNavigation": { "inbounds": { "contactCreate": { "semanticObject": "Contact", "action": "create", "icon": "sap-icon://add-contact", "title": "{{title}}", "subTitle": "{{subtitleOther}}", |
|
V4 (1.34) |
Added to the
Text symbols must be part of the properties file which is defined in
"sap.app": { "_version": "1.3.0", ... "title": "{{title}}", "subTitle": "{{subtitle}}", |
|
V3 (1.32) |
Contains navigation information and is a mandatory attribute in the
|
|
V3 (1.32) |
Needs to be updated in the
{ "_version": "1.4.0", "sap.app": { ... |
* Available as of manifest version (SAPUI5 version)