window=main

Starts a shell window with both top and left navigation.

window=app

Starts an application window without navigation elements.

window=embedded

Starts the shell in rendered format that is embedded in foreign portals; only relevant for NWBC for HTML.

decoration=no_branding

Hides the SAP branding logo in embedded mode. In the other window modes, this qualifier has no effect. Only relevant for NWBC for HTML.

transaction

This form is used to define that a specific (SAP GUI-based) transaction should be started. It is similar to starting a transaction within the OK field in SAP GUI. By default, NWBC for Desktop uses SAP GUI to start the transaction, and NWBC for HTML uses SAP GUI for HTML. Use the client_type qualifier to force a specific rendering engine. This is especially relevant when using NWBC for HTML, but needing the transaction to be executed in SAP GUI. For the transaction-specific sequence, specify the transaction that needs to be started.

wda

Use this form to start a Web Dynpro ABAP (WDA) application. By default, all Web Dynpro ABAP applications are started with an HTML-based rendering client. The client_type qualifier is used for possible future enhancements. For the specific sequence, specify the name of the Web Dynpro ABAP application. This can include an optional namespace if the application is not in the default SAP namespace.

url

Defines an absolute URL on the server that must be started. Note that this is a URL relative to the server against which NWBC is started. For the url-specific sequence, specify the server absolute URL with any number of segments, each separated by a / character.

roleEntry

Use this entry to start a specific entry in a specific role. This is an absolute form of addressing. Here the name of the role is used directly, and within the role, the assigned numeric ID. This number can be seen in PFCG on the Menu tab page when Other Node Details are displayed. For more information, see 5.5 Navigation Tree and PFCG.01 Searching for Technical Names. For the roleEntry specific sequence, specify the name of the role and the ID (numeric number) for the specific entry in the role.

sitemap

Use the sitemap sequence to embed a complete set of roles to an external portal. You can also only embed one role by specifying the role as an optional part of the URL directly after the /nwbc sequence. For more information, see 6.1.1 Short Form of URL. A typical use case is embedding a complete Employee Self Service scenario (expressed via the role SAP_ESS, for example) in a Microsoft SharePoint portal. With this one link, a service map is embedded in the external portal that represents the complete role. This can be used to start any transaction contained within the role.

obn

Specifies that for the startup application much be determined by resolving the OBN call. This is a good way to start a specific type of symbolic transaction, without knowing at that moment what the real transaction is that is mapped onto the user’s role. For example, assume the call sequence .../obn/process.Monitor. For a normal user, a role can be assigned in which this entry maps onto a monitoring application for the user's specific work area. However, the area supervisor can have a different role. This maps the OBN call in the supervisor's assigned role onto a special application that gives an overall view of all work areas. For this obn-specific sequence, both the object and method must be specified.

applicationAlias

Using an application alias is another way to start an application via a symbolic name. Within the role (in transaction PFCG), you can assign symbolic names to role entries. For the PFCG, this is just a user-defined string without any further meaning. This symbolic name can be used to enable NWBC at runtime to resolve the specific application that must be started.