Skip to Content
Technical Articles
Author's profile photo Frank Krause

SAP GUI for Windows 7.70: New Features & Lifecycle Information

Hello Community,

as mentioned in SAP Note 147519, the shipment date for SAP GUI for Windows 7.70 is the 29th of January 2021. So, we are only 2 days away from the delivery!

With this Blog I would like to provide some general information on the lifecycle of this release as well as information on the new features coming with 7.70. Since the new features contained in 7.70 are quite complex compared to previous releases, I also mention additional prerequisites and potential consequences of each feature.

Our focus areas were:

  • New Fiori 3 theme family (“Quartz”) – for a harmonized look with other SAP UI frameworks, but you will see that Quartz is not just some new colors.
  • Edge (based on Chromium) as alternative browser control for use in the SAP GUI HTML Control – for becoming independent of the Internet Explorer Control
  • 64bit versions of NWRFC controls – for being able to use those controls also from 64bit processes like Microsoft Excel 64bit
  • Multi-Monitor-Scaling support – for correct display of SAP GUI in environments with multiple monitors using different scaling settings

All of these areas have been eagerly expected by several customers and required huge effort on SAP GUI side. However, in addition to these topics we could also work on a couple of other smaller topics that are explained below.

SAP GUI Lifecycle

SAP GUI for Windows 7.70 was created with Microsoft Visual Studio 2019 which is in mainstream support by Microsoft until 9th of April 2024 (see also https://docs.microsoft.com/de-de/lifecycle/products/visual-studio-2019).

Therefore, SAP GUI for Windows 7.70 is supported until 9th of April 2024.

The chart below shows the current dates (on 27th of January 2019) for the lifecycle of SAP GUI for Windows releases 7.50 (already out of support) up to 7.70. For the latest information always refer to SAP Note 147519.

SAP%20GUI%20Lifecycle

SAP GUI Lifecycle

As you can see in the image above, there is an overlap of support durations for releases 7.60 and 7.70 of about 14 months. During this timeframe patches for both releases will be supplied normally.

New Features in Release 7.70

  • New visual theme family “Quartz”
  • The successor to the Belize theme is the Quartz (Fiori 3.0) theme. For the first time we also offer a dark version of the theme that can be used by users who prefer a dark background.Quartz%20Family
    There are four Quartz Themes (see also image above):

    • Quartz (“Light”)
    • Quartz High Contrast White
    • Quartz High Contrast Black
    • Quartz Dark

    When you install SAP GUI for Windows 7.70, Quartz is the default theme and SAP GUI will choose either the light or the dark version depending on your Windows settings. Of course, we do not override a previous setting – you can continue using SAP GUI with the theme of your choice. We also did not remove any old themes in release 7.70.

    Some of the highlights of the Quartz Themes:

    • Fiori features (for SAP S/4HANA systems) are supported just like in Belize
    • All features of Belize themes including theme specific coloring are supported
    • New states like a hover on selected state for several UI elements are introduced
    • Improved contrast for many aspects of the UI (including also for selected items)
    • A new monospaced font (“72 monospace”) is used which suits the proportional font (“72”) much better (also for Belize themes)
    • The main menu is back by default (also for Belize themes)
    • The new ABAP Editor can also use theme specific colors (if a new option is activated)

    The feedback we have received so far on the Quartz Themes (also from the Beta program that we ran) is much better than the feedback related to Belize. However, one should keep in mind these SAP Notes when using Quartz Dark:

    • SAP Note 2930005: Some ABAP applications use the SAP GUI background colors, but not the SAP GUI font colors for content in HTML controls. In such cases, the application will display dark text on dark background. To solve this, corrections in the respective application are needed.
    • SAP Note 2981918: SAP GUI for Windows is re-using several UI elements provided by Windows. Some of these elements do not allow changing their background color – they simply expect that the background is bright (except when High Contrast themes are used in Windows). It proved very difficult to overwrite all these elements and until today some very minor issues are remaining which are listed in this SAP Note.
  • Edge (WebView2 Control) as alternative browser control
  • So far the SAP GUI HTML Control always uses the Microsoft Internet Explorer Control for hosting HTML content inside SAP GUI, but nowadays Internet Explorer has several disadvantages:

    • Modern web content may not work
    • Performance issues
    • Many users have moved to other browsers and want to use them also when working with SAP GUI
    • Some web-based SAP UI frameworks intend to stop support for Internet Explorer
    • There is a lot of confusion regarding the support lifecycle of Internet Explorer (even though Microsoft has not announced the end of life, yet)

    For all these reasons as of release 7.70 we have integrated the Microsoft WebView2 control (Edge based on Chromium) as an alternative to the Internet Explorer Control (see SAP Note 2913405 for more information). In order to allow a smooth patching and update process we have decided not to deploy the component ourselves – therefore, WebView2 is not contained in the SAP GUI installation. To use the new version of the HTML Control, you need to install the Microsoft WebView2 control (https://developer.microsoft.com/en-US/microsoft-edge/webview2/#download-section) separately. Updates to the component are then received via the regular Microsoft channels.

    Since the HTML Control based on WebView2 is very new and presently has some functional restrictions (see below), we decided to keep the Internet Explorer Control as the default browser control in SAP GUI for Windows for now. However, once installed, you can select “Edge (based on Chromium)” via a setting in SAP GUI options dialog:

    SAP%20GUI%20Options%20Dialog%20Setting%20for%20WebView2

    SAP GUI Options Dialog Setting for WebView2

    Once the setting is activated, the HTML Control will use the WebView2 Control and therefore offer a modern browsing experience with all the advantages of a current browser:

    SAP%20GUI%20HTML%20Control%20using%20WebView2

    SAP GUI HTML Control using WebView2

    The HTML Control based on Edge behaves like the HTML Control based on Internet Explorer with some technical differences:

    • Web content which is not compatible with Microsoft Edge / Google Chrome is obviously not compatible with the new HTML Control. If you are using this kind of content, you should migrate this to new HTML standards. See also SAP Note 2901278.
    • The WebView2 control does not take the default font settings for web pages which do not set a font from the Microsoft Edge browser (as opposed to the Internet Explorer control). Therefore, by default, the SAP GUI HTML Control based on WebView2 uses the proportional font set in the SAP GUI options dialog in this case. See SAP Note 2942740 for more information.
    • Furthermore, there are some differences between Microsoft Edge and Microsoft Internet Explorer which are intended by Microsoft. For example, when SAP GUI detaches a URL from an HTML Control inside SAP GUI, an external browser window opens. In case of Internet Explorer, this window offers a full navigation bar, but Edge does not offer a navigation bar.
    • To allow a “mixed-mode” while applications still using old HTML content migrate to something new, we have introduced the feature explained in SAP Note 2957665: The administrator can define a fallback to Internet Explorer for certain systems / transactions when WebView2 is configured to be the default browser control.

  • 64bit versions of NWRFC controls
    The SAP GUI shipment includes four controls which can be used for getting data from an SAP System without using SAP GUI:

    • Logon Control
    • Function Control
    • BAPI Control
    • Table Factory Control
  • Up to release 7.60 these controls are only available as 32bit versions. Especially with the stronger usage of Microsoft Office 64bit editions this has become a challenge, because 32bit controls cannot be easily invoked from a 64bit process.

    As of release 7.70 we offer 64bit versions (both non-Unicode as well as Unicode) of these controls which can be installed in parallel to the 32bit versions. With this, scripts using these controls can also be run from 64bit processes like Microsoft Office 64bit. To benefit from this, select the appropriate installation component to be part of your installation package. See also SAP Note 2724656.

    SAP GUI Installation showing the component for getting the 64bit RFC controls

  • Multi-Monitor-Scaling support
  • Up to release 7.60 SAP GUI supports scaling using the scaling settings of the primary monitor only. For other monitors we let the operating system scale the SAP GUI window. This has some drawbacks for example when SAP GUI is embedded in an application which is multi-monitor scaling aware. In case of SAP Business Client this just leads to a blurry display of SAP GUI, but when embedded in Microsoft Internet Explorer the dimensions of SAP GUI inside Internet Explorer are determined incorrectly. See SAP Note 2541592 for more information.

    As of release 7.70 multi-monitor scaling can be activated in the SAP GUI options dialog so that the issues with multiple monitor setups using different scaling settings are solved. The feature can be activated for Belize and Quartz themes if a sufficiently new Windows version is used via this setting:

    SAP GUI Setting for activating Multi Monitor Scaling

    Multi Monitor Scaling is an extremely complex topic that required a multitude of changes in SAP GUI and that will certainly require further changes – the topic may also require adjustments in external ActiveX components that you embed in SAP GUI. SAP Note 2985351 contains further information on this topic.

    Another frequent issue in the context of using SAP GUI on devices with high resolutions is an incorrect size of cells in splitter containers. This typically leads to buttons not being completely displayed (cut off). The root cause of these issues is explained in SAP Note 2767962 – the affected ABAP applications are typically defining the height (or width) of the cells in the splitter container without taking the scaling into account.

  • Overflow for buttons in the footer of dialog boxes (popups)
  • The maximum width of a dialog box (popup) is limited by the horizontal resolution of the display. When an application inserts many buttons or wide buttons in the application toolbar (footer) of a dialog box or the resolution is low or the used font size is big, this sometimes exceeds the maximum width. In SAP GUI releases up to release 7.60, such buttons could not be displayed.

    Therefore, as of SAP GUI for Windows 7.70 and starting with Belize themes, SAP GUI puts all buttons which do not fit into the dialog box into an overflow button. If needed, the footer of the dialog box displays a button “…” that offers a context menu containing all buttons for which not enough space was available. This ensures that all applications, even those with many wide buttons, can be properly used.

    Overflow%20for%20buttons%20in%20dialog%20boxes

    Overflow for buttons in dialog boxes

  • Customizable focus position in ALV Grid control
  • The ALV Grid control may consist out of a toolbar area, title area, column header and table area. If you move the focus to the ALV Grid control via keyboard, in SAP GUI for Windows the focus by default is set to the table area. This is since in many cases the user first wants to do something in the table area (like selecting a column) before using the buttons in the toolbar area (like for sorting the selected column). However, in case a different behavior is desired, this can now be achieved by setting a newly introduced registry value. You can decide whether the focus shall first move to the table area (default), to the toolbar area (value = 1) or column header (value = 2).
    See SAP Note 2973107 for more information.

  • Different background colors for hierarchical levels in tree control
  • In SAP Signature Theme the tree control shows different background colors for the first four hierarchical levels. In newer themes this functionality was removed by design, because it reduces contrast of text to background and the idea of the newer SAP GUI themes was having a display with fewer visual hierarchies. However, the different colors for tree levels are considered helpful by some users, because one can more easily understand on which level an item / node in the tree is located.

    Therefore, as of SAP GUI for Windows 7.70, we have introduced different background colors to differentiate tree control hierarchical levels also in newer SAP GUI themes starting with Blue Crystal theme (which excludes the Corbu theme). This functionality is inactive by default and can be activated as explained in SAP Note 2943146. For SAP Signature Theme the functionality remains active by default and cannot be deactivated. Please note that in High Contrast themes this functionality is not supported, because the contrast wouldn’t be enough to meet the minimum contrast requirements.

    Tree%20Level%20Colors%20in%20Quartz%2C%20Quartz%20Dark%2C%20Belize%20and%20Blue%20Crystal%20Themes

    Tree Level Colors in Quartz, Quartz Dark, Belize and Blue Crystal Themes

  • Improved version of SAP GUI Scripting “Record and Playback” dialog
  • SAP GUI scripting offers a dialog for recording and replaying scripts. This dialog had several functional and usability issues. Therefore, it has been reworked in release 7.70 and the following changes were applied:

    • The dialog is substantially larger, because it has been restructured with sections specific to recording and replaying. The “More / Less” button available in previous releases is no longer available.
    • The dialog is no longer topmost by default. If desired, the dialog can be made topmost again by setting a registry value
    • The dialog remembers the previous position at which it was closed. Therefore, you can move the dialog to a convenient position (or even a secondary monitor) while recording.
    • The dialog offers a new button for editing the recorded script in a text editor associated with the respective file extension.
    • When replaying a script, the dialog no longer asks for a file to be replayed, but uses the file specified in the respective input field. The name of the file recorded last is automatically taken over into the input field after completing the recording.
    • The usability has been improved (tabchain, focus, scaling,…)
    • The dialog can be launched or brought to the front if it was already started before by clicking the scripting indicator in the system information area in the SAP GUI main window or the SAP Business Client main window. This function can only be used if scripting is installed and permitted in the system you are connected to.
  • SAP Business Client Integration: User timeout
  • SAP GUI for Windows and SAP Business Client now exchange information on whether a user is still active to avoid timeouts when the user is still active in another window / tab.

  • Placeholder characters in password fields
  • A new option “Show placeholder characters” is introduced. If this option is deselected, SAP GUI does not fill password fields with placeholder characters. Instead the placeholder characters (dots or asterisk) appear as you type. This reflects the behavior of several other applications, but has the disadvantage that it is more obvious how many characters have been typed. The default setting remains unchanged, which means by default, SAP GUI keeps displaying the placeholder characters for empty password fields.

Removed features in SAP GUI for Windows 7.70

This time we haven’t removed any visual theme, but have just cleaned-up the theme selection and removed a rarely used legacy component that has a functional alternative:

  • The Belize theme offered a so-called “Fallback” theme in SAP GUI for Windows 7.50 and 7.60. This “Fallback” was used for SAP systems which do not support the Fiori feature set. As of SAP GUI for Windows 7.70 no “Fallback” theme is offered anymore. The theme set in the SAP GUI options dialog (or via other means like the SAP Business Client) is used for all systems a user connects to.
  • The Assignment Control used in transaction UCWB is no longer available. A technical alternative is available as mentioned in SAP Note 2704440.

Outlook

We hope that release 7.70 will live up to your and our expectations – especially since it adds very important and long-expected new features. Our experiences from the Beta Program and our SAP internal roll-out are very encouraging, but of course some of the major new features listed above will certainly need our attention during the next couple of patches. We will completely focus on closing remaining gaps and fixing issues you might find for the next months.

Kind regards,
Frank Krause
Product Owner SAP GUI for Windows
on behalf of the SAP GUI for Windows Team

Assigned Tags

      160 Comments
      You must be Logged on to comment or reply to a post.
      Author's profile photo Sebastian Mende
      Sebastian Mende

      Hello togather,

      i have some issues with edeting transformations in SAP BW.

      It is hard to see transformation-lines in view mode:

      But it is impossible in edit mode:

      Best regards

      Sebastian

      Author's profile photo Nandakumar Ramamoorthy
      Nandakumar Ramamoorthy

      Hello Frank Krause ,

      You mentioned that SAP is not investing anymore on old themes like classic during 7.60 release. Is there a reason, it is still available in 7.70?

      I tried searching the sap notes but cannot find the information on the maintenance support cycle for the GUI themes or any notes that suggests to discontinue certain themes. Could you please share if there is any?

      This will be helpful to nudge users who refuse to adapt to the new theme due to old habit.

       

      By the way, I am big fan of the Quartz Dark theme, thanks for making that.

      Looking forward to Horizon, is there a timeline on when horizon will be available?

       

      thanks

      Nanda

      Author's profile photo Frank Krause
      Frank Krause
      Blog Post Author

      Hello Nanda,

      SAP GUI for Windows does not just have a single rendering engine, but multiple ones.
      This also explains why we do not invest into old themes anymore: We would basically have to implement the same stuff multiple times in different ways (depending on the rendering used).

      If we keep adding new themes which require new rendering engines or at least substantial changes in existing engines, SAP GUI for Windows becomes slower and slower (which is due to the architecture). Therefore, since we simply do not have the capacity to completely re-shape the architecture, we need to remove themes every now and then. This is what we did in SAP GUI for Windows 7.60 with the Enjoy theme.

      Classic theme however is based on standard Windows rendering. If we removed this, we would not gain much and we would probably cause further customer frustration, because the removal of Enjoy was not directly appreciated by all customers. Therefore, without need we do not remove themes.
      I do not see Classic theme go away any time soon.

      In SAP GUI for Windows 8.00 we will not remove any old theme, but we will neither introduce a new theme as we do not have the capacity to implement Horizon in time. We rather invest into modernization of the Quartz rendering. My personal expectation is that we will deliver a Horizon theme with the release after 8.00.

      >By the way, I am big fan of the Quartz Dark theme, thanks for making that.

      Thank you for that, I personally also like this theme.

      Best regards,
      Frank

       

      Author's profile photo Nandakumar Ramamoorthy
      Nandakumar Ramamoorthy

      Thank you very much for the clarification.

      Highly appreciate the details!

       

      thanks

      Nanda

      Author's profile photo Kenji Eimura
      Kenji Eimura

      Hello Frank Krause ,

      Does SAP GUI 7.7 support IE?

      Best Regards,

      Kenji

      Author's profile photo Dino Philips
      Dino Philips

      Hi Kenji,

      BR Dino

      Author's profile photo Kenji Eimura
      Kenji Eimura

      Dear Philips-san,

      Thank you for your response.
      I know that as of 2022.6.15 we will stop supporting IE.

      Can I ask one more question?

      We are hoping to start evaluation testing of SAP GUI 7.7 tomorrow.

      Please let us know if there are any checkpoints or items to be checked.

      Best Regards,

      Kenji

      Author's profile photo Dino Philips
      Dino Philips

      Hi Kenji,

      Good luck

      Best regards, Dino

      Author's profile photo Aditya Palekar
      Aditya Palekar

      Hello Frank,

      Is there a compatibility matrix between SAP GUI version and corresponding SAP NW version? some of my customers are on SAP GUI 730 but still working with S/4HANA 1809 as they migrated from ECC. However I don't suppose they can continue using outdated GUI versions for too long.

      Best Regards,

      Aditya

      Author's profile photo Armin Hadersbeck
      Armin Hadersbeck

      Hello Frank,

      since two weeks, we test the SAP GUI 7.70PL7.
      Our Team found a issue, we can't find any article in the OSS.
      If we test this with 7.60, it works fine.

      for a short time, the original page will display and after a automatically reload, the following side will shown. Our SAP basis team and we have no idea what's wrong and what's the root cause. see attached screenshot.Webdynpro%20-%20connection%20is%20not%20secure

      Webdynpro - connection is not secure

      have you any hint for me.

      thanks a lot

      Armin

      Author's profile photo Frank Krause
      Frank Krause
      Blog Post Author

      Hello Armin,

      this is not about 7.60 versus 7.70, but about the browser control you are using.
      The screenshot shows that you are now using the HTML Control based on Microsoft WebView2.
      Unfortunately, WebView2 is not Internet Explorer in terms of behavior or functionality (as one can conclude from SAP Note 2901278).

      I believe the concrete issue you are facing is mentioned in SAP Knowledge Base Article 3209658.

      Best regards,
      Frank