The lack of quick launch in NWBC for HTML was a show stopper for us, most of our users still use transactions instead of finding the correct entry in the workset or favorites. See here for the list of other known limitations in NWBC for HTML. The biggest performance problem we faced was with traditional transactions (dynpros) since NWBC for HTML can't use SAP GUI for Windows but uses SAP GUI for HTML (webgui). So I guess the biggest performance problem we faced was more about SAP GUI than about NWBC.
↧