Show TOC

Defining Extensions MetadataLocate this document in the navigation structure

The extensions metadata is defined in the Component.js file of the custom project. The Component.js file has an json object called metadata. The object metadata contains the following objects: routing, config, and customizing.

Object Name

Use

config

Used to define metadata for the following:

  • Custom OData URL

  • Custom i18N bundle name

customizing

Used to define metadata for the following:

  • View extensions

  • View modifications

  • View replacements

  • Controller extensions

routing

Used to define metadata for new navigation routes in the following cases:

  • Customer views are added

  • Customer wants to change a navigation route

The object customizing supports the following objects and their usages are mentioned in the table below:

Object Name

Use

sap.ui.viewExtensions

Used to add a new view element to the standard view at the defined extension points.

sap.ui.viewModifications

Used to change the property value of a control in the view.

sap.ui.viewReplacements

Used to replace a standard view with a view in the custom application.

sap.ui.controllerExtensions

Used to extend the functionality of the base controller.

The object config supports the following objects and their usages are mentioned in the table below. Refer to https://sapui5.hana.ondemand.com/sdk/#docs/guide/08608efbe1864607a80fb7c41a9645e5.html for more details.

Object Name

Use

sap.ca.i18Nconfigs

Used to replace or augment the internationalization strings with strings defined in the custom application.

sap.ca.serviceConfigs

Used to add or change the oData Service definition with oData service defined in the custom application.

For more information about the usage of the object routing, see https://sapui5.hana.ondemand.com/sdk/#docs/guide/688f36bd758e4ce2b4e682eef4dc794e.html.

For examples and more information about the object json, see http://www.w3schools.com/json/Information published on non-SAP site.