This section describes the new and changed features for the user interface add-on 1.0 SPS 04 for SAP NetWeaver.
The release notes for user interface add-on 1.0 SPS 04 for SAP NetWeaver describes the SPS 04 delta documentation on top of the documentation published for UI add-on 1.0 SPS 03. This documentation therefore reflects the changes since UI add-on 1.0 SPS 03. The content of this documentation represents the latest version of the documentation and is valid.
You register a CHIP in the Web Dynpro configuration so that it can be used in the Page Builder catalog service.
As a role administrator, you can now assign catalog pages to user roles in Role Maintenance (transaction PFCG) using new role menu type Catalog Provider. You have the following options:
You provide a name for your catalog provider that is visible as a PFCG node.
The Catalog Type is Catalog Page.
You can change and display the node.
You can test if the page you enter exists as Customizing or configuration. A value help is available for this.
Catalog pages are displayed as folders on a page. An end user can switch between the folders and can add CHIPs to the page.
In previous support packages, you had to select a CHIP catalog when creating a new page. In the current support package, assigning a CHIP catalog to a new page is no longer mandatory. This is due to the fact that you can now assign catalog pages to roles rather than to pages.
In the Outdated column, an icon is displayed if a page has been edited in a lower scope after you have stored the settings for the same page in the current scope.
For example, if you have edited a page in the Customizing scope, and another administrator updates the same page in the Configuration scope, an icon indicates that you do no longer have the most recent version of this page in Customizing scope. You can either decide that this is fine with you and leave everything as is, or you may want to delete the page from the Customizing scope in order to make sure that the updates that have been made in the Configuration scope are propagated to the Customizing scope again.
You can now define which page builder you want to use by clicking on the wrench icon that is located next to the Create button. All pages that you open from the page administration UI are opened in the page builder that you enter in this Settings dialog.
If you do not change this setting, the suite page builder is used by default.
This setting is stored in the Customizing scope and is valid for the client that you are currently logged on to.
The launch page is a home page that displays tiles from where users can launch applications. It depends on the user’s roles which app launcher tiles are displayed on the launch page.
Static app launchers only display static text and icons, and dynamic app launchers also display dynamic content read from a data source.
For more information, see Launch Page.
Using the writeConfiguration contract of the CHIP API, you can set parameter values to a CHIP configuration.
For more information, see http://help.sap.com/nw-uiaddon .
Callable entities allow applications built with any technology that consume OData services to navigate to applications related to that data, for example, what other applications can a user start in relation to a particular product. Callable entities work independently of the used UI technology (for example, SAPUI5 or Web Dynpro ABAP) of the target application or a shell (SAP NetWeaver Business Client, Portal, or other).
An OData service developer needs to provide only the details about the target application on the server side that will become a URL link on the client side and can be used by the application developer (user interface developer). The technical processing of the request is hidden from the service user by ABAP and JavaScript libraries.
For more information, see SAP Help Portal at http://help.sap.com/nw-uiaddon .
As of user interface add-on 1.0 SPS 04 the POWL enabling service has been enhanced to enable selection criteria.
The POWL selection criteria and result lists are interpreted by the Web Dynpro generic POWL UI (Web Dynpro application POWL) as follows: The POWL feeder method IF_POWL_FEEDER~GET_SEL_CRITERIA retrieves the selection criteria for a POWL query. Feeder method IF_POWL_FEDER~GET_OBJECTS applies the selection criteria to the database query which returns the result.
In the past the POWL enabling service only considered selection options fields of the result structure. With SPS 04 all selection criteria defined by feeder method IF_POWL_FEEDER~GET_SEL_CRITERIA are also considered. This is because theoretically the selection criteria might not appear as fields in the result list.
It is therefore now possible to expose any POWL application ID and its queries as an OData service.
For more information, see SAP Help Portal at http://help.sap.com/nw-uiaddon .
An OData service call can produce entity sets that are so large that it can take many seconds or even minutes to return them to the consumer. What is more, moving to the next page causes the data to be read from the database again before positioning to that page. Users do not want to wait a long time for the system to respond. In such a case it makes sense to use a cache mechanism for storing entity sets. We call this the cache for OData services.
For more information, see SAP Help Portal at http://help.sap.com/nw-uiaddon .
SAP NetWeaver Business Client 3.6 for HTML is shipped as part of user interface add-on for SAP NetWeaver. In addition to the features available in NWBC 3.5 for HTML, NWBC 3.6 for HTML supports theming with the UI theme designer.
For more information on UI theme designer, see UI Theme Designer.
For more information, see SAP Library for User Interface Add-On for SAP NetWeaver on SAP Help Portal at http://help.sap.com/nw-uiaddon .
Role SAP_UI2_ADMIN_700 Contains References on Page Building Service
Roles | Description |
---|---|
SAP_UI2_ADMIN_700 |
Example administration role for OData services that are available for back-end systems based on SAP NetWeaver 7.0 Enhancement Package 3 and higher. In the role menu, this example role contains authorizations for the following services:
|
Instead of using role SAP_UI2_ADMIN_731, from now on use role SAP_UI2_ADMIN_700.
A new authorization object /UI2/CHIP is available as of SAP NetWeaver 7.0 with the same properties as S_PB_CHIP.
For more information, see SAP Library for User Interface Add-On 1.0 SPS 03 for SAP NetWeaver on SAP Help Portal at http://help.sap.com/nw-uiaddon .
With SAP NetWeaver Business Client 4.0, you can also connect to SAP NetWeaver 7.0x and 7.40 based systems using the server runtime for SAP NetWeaver user interface services. This allows for improved maintenance of NWBC configuration using transaction /UI2/NWBC_CFG_CUST and supports the existing side panel tagging configuration for an easy migration to the newer runtime.
For more information, see SAP Library for User Interface Add-On 1.0 SPS 03 for SAP NetWeaver on SAP Help Portal at http://help.sap.com/nw-uiaddon .
In Customizing you define configuration parameters for versions of SAP NetWeaver Business Client that connect to the server runtime for SAP NetWeaver user interface services, for example Welcome Message.
Currently SAP NetWeaver Business Client for Desktop does not handle launchpad links. That means, if there is an entry in PFCG for a launchpad link, this entry does not appear in the navigation.
For release information for SAP NetWeaver Business Client 4.0 patch levels 6 to 7, see
1707626 .
For documentation about user interface add-on 1.0 SPS 03 for SAP NetWeaver, see:
SAP Service Marketplace at http://service.sap.com/instguides
SAP Library for User Interface Add-On for SAP NetWeaver on SAP Help Portal at http://help.sap.com/nw-uiaddon