Hi Simon and Samuli,
Transactions linked in the service map show up in SAP GUI for Windows (embedded in a new tab), the same as transactions started from the Index page, New Tab page, Quick Launch, navigation panel etc.
I tested it with NWBC 4.0 PL11 and role SAP_SR_BUYER_5, selecting e.g. "Create Purchase Order" from the service map, and it works well (and I also don't have problems when using the UI2 NWBC runtime):
As Melinda said, a verbose trace would be helpful to see what's going wrong in your environments.
It should be like that (trace snippet):
=== AsyncNavigateLast:
canvasAppType=SapguiTransaction
suspendCurrentSession=False
url=https://<server>:<port>/sap/bc/gui/sap/its/webgui;~sysid=<sid>;~service=<4 digit service nr>?%7etransaction=ME21N&%7enosplash=1&sap-client=<nr>&sap-language=EN&sap-nwbc-context=[...]
connectionName=on <server>:<port> [CsRuntime: SAP NWBC Managed Runtime for ABAP]
nodeId=Q63~SAP_SR_BUYER_5:283
callingSessionId=cs-session:#2<null>
DisplayName=Create Purchase Order (ME21N)
window=[ShellWindow#cw1: Create Purchase Order (ME21N)]
(search for '=== AsyncNavigateLast';
=== AsyncNavigateLast:
canvasAppType=BrowserServiceMap
is set when the service map rendering is complete. The next '=== AsyncNavigateLast' block designates the page that is called from the service map, in the above case transaction 'Create Sales Order (ME21N).)
It is important that the url contains a ~service parameter. If this one is missing, NWBC is not able to launch a SAP GUI for Windows, but only a Web GUI. And if even the Web GUI URL is missing or wrong...
So please, provide a trace for further analysis.
Best,
Claudia