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.

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 will use SAP GUI to start the transaction, and NWBC for HTML will use SAP GUI for HTML. Use the client_type qualifier to force a specific rendering engine. This is specifically of interest 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 here just used for possible future enhancements. For the specific sequence, specify the name of the Web Dynpro ABAP application. This could 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 an 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 in the usual form by a / character.

roleEntry: Use this entry to start a very specific entry in a very specific role. This is an absolute form of addressing. Here the name of the role is directly used, and within the role, the assigned numeric id. This number can be seen within PFCG on the Menu tab when Other Node Details is turned on (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. It is also possible to only imbed one role by specifying the role as optional part of the URL directly after the /nwbc sequence (see chapter 6.1.1 Short Form of URL). Typical use case would be to imbed a complete Employee Self Service scenario (for example, expressed via the role SAP_ESS) into a Microsoft SharePoint portal. With this one link a service map is embedded into the external portal that represents the complete role and 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 very good way to start a specific type of symbolic transaction, without knowing at that moment what the real transaction is that is mapped into the user’s role. For example, assume the call sequence .../obn/process.Monitor. Then for a normal user, a role could be assigned where this entry maps onto a monitoring application for his specific work area, whereas the area supervisor can have a different role which maps this OBN call in his assigned role onto a special application that gives an overall view over all work areas. For this obn-specific sequence, both the object and method must be specified.

applicationAlias: Using an application alias is another form to start an application via a symbolic name. Within the role (in transaction PFCG), it is possible to 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.