SAP GUI for Windows 7.70: New Features & Lifecycle Information

[FrankKrauseGUI]

Update: Support for SAP GUI for Windows 7.70 ended on 9th of April 2024!

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 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.
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 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 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 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 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

[johnm16]

Hi Frank,

you're absolutely right - I was talking about the Belize/Quartz themes when I mentioned space.

But it is the "vertical offset" (and horizontal, actually) that I'm talking about,  and in particular the difference from the 7.50 Enjoy theme.

I will try pasting in two screenshots here.  They are both full screen height (my normal working screen),  so they will take up a lot of space (apologies),  I want to show the real difference.  The first is of the 7.50 Enjoy SAP sessions,  auto-cascaded.  The second is the 7.70 Signature theme.

The screenshots were saved without any alteration,  and I have done my very best to avoid increasing or shrinking either of them.  The first screenshot came off a Windows 7 machine,  the second from Windows 10, but both were displayed on and copied from the same NEC MultiSync screen.

Big difference, no?  Now, I have to launch each session then move it up and left.  Great fun when the internet goes down and the exercise has to be repeated.

It is easy to view this as a trivial issue,  but to me, it's a proper PIA.  Maybe it's a Windows thing,  but it would be just fantastic if we could set the vertical/horizontal displacement in pixels;  then everyone would be happy,  but I suspect it isn't possible.

Best regards,

John

[FrankKrauseGUI]

Hello John,

the vertical offset is set like this intentionally. You are not showing the Window titles at the left of your screenshots. If you did, one could see that the titles of the inactive Windows are displayed properly with the offset that SAP GUI 7.70 has. If we used less offset, the titles were cut off and this makes it much harder to find the right window in the stack if you are searching for a specific one.

Best regards,
Frank

 

 

[johnm16]

Hi Frank,

if I can only display a small number of windows on my screen before running out of space (instead of 15/16),  I really won't need to worry about which is which.

You might also want to look at the behaviour of SE80 with SAP Signature theme:  every time I drill down 1 level (starting with a package),  the screen refreshes.  After drilling down 2 levels, it double refreshes.  After 3 levels,  it triple refreshes... etc. etc.

Don't get me wrong:  I have nothing but respect for all the very difficult work you guys do,  and it is impossible to please all of the people all of the time.  But the approach of SAP is very prescriptive:  "you will work in the way we choose!".  There are a lot of people who are not so happy with that,  and who don't want to lose what was a very efficient way to arrange their desktop.

I've reverted to 7.50 until SAP begin to understand the value of compromise.

Thanks again,

John

[abo]

After upgrading from PL2 to the hotfix released today, I'm getting dumps in SE16 with ALV Grid output on a 7.31 system. Also another Z transaction is affected but I have yet to check which control is used. Works fine with ALV list, though. Hopefully I'll have time to recheck tomorrow.

EDIT: yup, direct upgrade from GUI770_2-70004692 to gui770_02_1-70004692 results in CNDP 0006 in SAPLOLEA for GRID controls. Removing all components and reinstalling from scratch apparently fixes the issue.

[barthp]

Hi Frank, hi SAPGUI Community,

Thank you for all the updates posted here, there is a lot of information!

I hope I can get feedback to one issue here, that we are experiencing since upgrading to patchlevel 2. I’m a little bit unclear, if this is a bug or just an incompatible change.

Anyways, here is our issue:
In some of our html controls in SAPGUI we are displaying websites that integrate pictures or iframe from a different origin (server) then the website itself. When using the chromium edge control under patchlevel 2 this external content is not displayed.

The issue is not present in patchlevel 1 and neither with the IE control. (In the IE there are some settings, which would lead to the same behavior).

I’m aware, that this is not the recommended build for websites, but it would cause a lot of effort for us to rebuild legacy applications. Thus my question is: Is this the intended behavior or is this something that might be fixed in a later patch?

Kind Regards and thanks for all your effort
Peter

[FrankKrauseGUI]

Hello Peter,

please report this as an incident for a deeper analysis. In patch 2 a number of changes needed to be done for handling of SSO and maybe this is a side-effect.

Best regards,
Frank

[barthp]

Hi Frank,

thank you for your prompt feedback. I will heed your advice and open an SSO.

Kind Regards

Peter

[jaroslav_mrazek]

Hello Badari,

thank you for the correction, "Code hint" with 7.70 PL 02 is correct displayed. The same problem is with the "Code template", the font is not clearly visible and he has to be increased too.

Code hint is correct displayed

Code template is not correct scaled, is scaled down. Description of code teplate is scaled correct.

My display resolution is 2560x1440, scalling 100%. In SAP GUI with Theme "Quartz" are used fonts:
- Monospaced font "Fira Mono", size 9
- Proportional font "Tahoma", size 9.

The scalling doesn't work correct for "Enhanced search", e.g. transaction SU01, I search user and I entry the letter "M". In "Enhanced search" are correct displayed alle user, that start with this letter. Submatch with letters "MR" returns only 1 user and the "Enhanced search" display horizontal scroolbar over the displayed result. The user name isn't visibile. With default font size of Theme "Belize" or "Quartz" works "Enhanced search" correctly.

Displaying of one matched user SAP_WFRT

From this reason I stayed by SAP GUI 7.60 with Theme "Belize" and I look forward for the next patch for SAP GUI 7.70.

Best regards,
Jaroslav

[marco-silva]

Hello Frank,

Just noticed that with the option "Edge (based on Chromium)" active, the Template Editor for ITS Mobile doesn't load. Had to switch back to "Internet Explorer", if it can help anyone going thru the same issue.

Regards,

Marco

[macarranza]

We upgraded from BC 7.0 to BC 7.70 SP3 and after the upgrade we are seeing 2 issues:

1. Missing icons for some options like Search (F4)


2. Cursor disappears in some fields

THe upgrade also considered SAPGUI. This issue is not happening in SAPGUI.

We applied SP5 to try to correct the issues and they are still happening.

Is this a known issue?

MC

[former_member759794]

Hello Frank (Product Owner)

Could you please let me know if SAPGUI 7.7 is compatible with SBOP 4.2 ??

This information is not yet available in PAM and also when I checked with SAP, they do not have the information. The latest GUI provided for SBOP 4.2 is SAPGUI 7.6.

Could you please assist in this ?? There is a GUI upgrade planned to GUI 7.7 and this seems to be one of the dependency by BW folks.

Thank you.

 

[FrankKrauseGUI]

Hello Ram,

this is something you need to ask SBOP and not SAP GUI.

SAP GUI is a generic framework which is compatible.
We do not test or release SAP products - if an SAP product believes they need to do own release statements for SAP GUI, it is their responsibility.

Best regards,
Frank

[FrankKrauseGUI]

Hello Miguel,

yes, it is a known issue.
Please try to use hotfix 2 for patchlevel 2 of SAP GUI for Windows 7.70.
This should solve the issue.

Best regards,
Frank

[pavelbaco]

Hi all,

 

is there any options how to set up, configure path for WebView2 component? I have installed it in diffrent path then default and i cant configure SAP Logon to use Edge (based on Chromium).

[manwell77t]

Installed latest Patch 3 on 770.

 

I'm experiencing an issue writing to the spool when there's an icon to render. For example:

write: / |@0A@|, | AAAAAAAAAAAAAAAAB|.
write: / |@0A@ AAAAAAAAAAAAAAAAB|.

The second write always truncate the last character; tested with a 750 Patch 4 everything's ok instead.

best regards.

[ChristianGünter]

Hi frank.krause

There are still some issues with chromium browser control and PL3.

Maybe you can have a look at here?

https://github.com/abapGit/abapGit/issues/4841

Best regards

Christian

[FrankKrauseGUI]

Hello Christian,

we are trying to resolve the issues as quickly as possible, but this is very tricky, because workarounds that are suggested by Microsoft are sometimes not as easy as they seem (and may lead to further issues). The second aspect is that WebView2 currently does not support all the features we need. With this status I believe that it will take some time for us to get the WebView2 based HTML Control into a state that is comparable with the IE based HTML Control. And it is obvious that some restrictions cannot be overcome at all (if your HTML is not working in Edge, it will not be working in WebView2 either).

Regarding the issues mentioned under the link you posted: Please report issues which are still open to us via the SAP support infrastructure. Such issues need a closer look and require interaction between the person who reports the issue and the persons who would like to resolve them (which may also require remote access to an affected system).

Best regards,
Frank

[FrankKrauseGUI]

Hello Manuel,

I can reproduce this - it seems to occur only with the wide icons like the traffic lights and how much of the last character is cut off also depends on the monospaced font used (in Quartz only half of the last character is cut off).
We will have a look at this.

Thank you for reporting this.
Frank

Update: The issue is fixed and the fix will come in 7.70 PL4

[jaroslav_mrazek]

Update 16.08.2021: Screenshots added

[RobA]

Hi frank.krause

We are seeing many users complain about working with select/deselct in ALV since GUI 7.70

I appreciate this is a known bug as per SAP note 3077008, but there is no fix released and our user base are complaining and there is no workaround.

Can we get any ETA on a fix or perhaps a hotfix be released here?

Thanks

[FrankKrauseGUI]

Hi Rob,

the correction has been implemented (the SAP Note you found is the right one).
We will include this in patchlevel 4 of SAP GUI for Windows 7.70. The creation of this patch will start soon, but the patch will be released as per our plans on 29th of October 2021 (see SAP Note 1053737).

Best regards,
Frank

[former_member610367]

All is good, but simple things such  as quick copy , paste and ins/ovr functions are difficult to find 😞

[Mishael]

Font that breaks still happens sometimes:

Broken ALV in AL11

 

[hech]

Strange cursor behavior in tcode. SE16N

The cursor keeps moving in front of the word entered in extended search.

We are at SAPGUI 7.70 SP3 hotfix 2

 

[RobA]

Hi Frank

Do you know when there will be a statement for SAP GUI 770 support on Windows 11?

I checked on support portal and the Lifetime and Support Matrix for SAP GUI for Windows document but could not find any mention of Windows 11

 

thanks

 

 

[FrankKrauseGUI]

Hello Rob,

there is already a statement in our requirements note 66971:
https://launchpad.support.sap.com/#/notes/66971

• Windows 11: Microsoft plans to release Windows 11 as of October 5, 2021 (see also https://blogs.windows.com/windowsexperience/2021/08/31/windows-11-available-on-october-5/). SAP will start tests for the release of SAP GUI for Windows 7.70 on this platform as soon as the final version of Windows 11 is available. Since previous tests of preview versions were positive, it is to be expected that a release will take place before the end of 2021. However, this depends on the actual results of the tests. A release of SAP GUI for Windows 7.60 on Windows 11 is not planned because the end of maintenance of this release is imminent.

I will slightly update the statement today, because we have of course already started our tests.
My intention is that we can start support with 7.70 patchlevel 4, but it is too early to promise this.

Best regards,
Frank

 

 

[sven_schneider2]

Hello Frank,

there have been some changes in notes recently, like in note 2957665, where the text says "... when running a 64bit version of SAP GUI for Windows ...".


Is there a 64bit SAP GUI on the road?

Best regads
Sven

[FrankKrauseGUI]

Hello Sven,

yes, we are indeed working on a 64bit version for the next SAP GUI for Windows release.
We will publish more information in 2022 when we know that we will be able to deliver this.

Best regards,
Frank

[mwn]

Is there a Windows registry entry for setting Edge as the default HTML control? I would like to make this the default via scripting. Thanks

[mwn]

It seems like this is the key

[FrankKrauseGUI]

Hello Michael,

yes, that is the right value, but please take into account that WebView2 must be installed.

Generally all settings that can be adjusted in the SAP GUI options dialog are documented in the SAP GUI Administration Guide.

In the concrete case you may want to check this page of the Administration Guide:
https://help.sap.com/viewer/dfad9ecd79db404eba46fdd709013a78/770.04/en-US/1f4508f4d417423aa7a70129e7...

Best regards,
Frank

[Kim_Heckscher]

Hi Frank,
do you have an example how to do it in EventScripts?
Or shoul I just use the Example "Execute an application and wait" ?

[chr_winkler]

Microsoft Teams Wizard is also an application that steal F8 key.

[Mark_Proctor]

By way of a piece of advice...

If you intend to enable the WebView2 control, I would also suggest setting up a centrally maintained file giving the SAP GUI a list of exceptions, where the IE control should still be used (i.e. where the WebView2 control does not work) as per SAP note 2957665.

Even if you do not populate the list initially, having it configured makes it easy to add an exception for all users, when required.

[andreas_thyssen]

Example for a rule, where everythings points/leads to internet explorer, can be adjusted later:

 

<?xml version="1.0" encoding="UTF-8"?>

<SAP>
<type>SAP HTML Control Fallback Rules</type>
<version>1.0</version>
<timestamp>2020-08-12 15:00:00</timestamp>
<rules>

<rule system="*" transaction="*" browsercontrol="Internet Explorer" />

</rules>
</SAP>

<!-- AT: Possibillities of rules: -->
<!-- rule system="SY1" transaction="TA1" browsercontrol="Internet Explorer" -->
<!-- rule system="SY2" transaction="TA2" browsercontrol="Edge" -->
<!-- rule system="SY2" transaction="*" browsercontrol="Internet Explorer" -->
<!-- rule system="SY3" transaction="TA3" browsercontrol="Internet Explorer" -->
<!-- rule system="SY3" transaction="TA4" screenname="SCREENNAME1" screennumber="SCREENNUMBER1" browsercontrol="Internet Explorer" -->

[Skirmantas]

I just tried SAP GUI 7.70 patchlevel 4 hotfix 1 on virtual machine with Windows 11 and it crashes with BSOD on launch... but 7.60 patchlevel 13 works fine.

[FrankKrauseGUI]

If this can be reproduced on a regular installation, please report an incident. It makes no sense discussing this in this blog.

And:
1) SAP GUI itself cannot directly cause a BSOD, because SAP GUI is not a driver.
2) Our tests do not show such issues.

[Skirmantas]

Yes, it could be because of virtual machine. Thanks for your response.

[tursko]

Thanks for making this blog post. I had issues displaying Web Dynpro views but changing the HTML control back to Internet Explorer resolved the issue.

[RobMoore]

Thanks for the info - is there a Compatibility matrix for the new GUI version? I am wondering if BEx Analyser is still supported on the new version.

[hech]

Where would you set this?

[Mark_Proctor]

The XML file can be stored anywhere users have read access to and you store the location in the registry as follows:

Key = HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\SAP\General (note drop the 'WOW6432Node' part if you are using a 32-bit operating system.

Type = REG_SZ

Name = BrowserControlFallbackConfiguration

Value = location of your XML file

[rainer_schuler5]

Hi Rob,

surely there is a BEx Addon for GUI 7.70.
You can also find patches for this component in the download section on SMP in section "BI ADDON FOR SAP GUI"

However, there is no functional development in BEx anymore.

[andrevo]

Hello Mr. Krause,
do you know where I can find applications ?

As described here in item
Add SAP GUI visual design options
https://documentation.tricentis.com/tosca/1420/en/content/sap_solutionmanager/sap_gui_security.htm

greetings Andre

[FrankKrauseGUI]

Hello Mr. Voss,

you need to start the options dialog from Control Panel for this.

Best regards,
Frank Krause

[andrevo]

Thanks this works now

[mendeseb]

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

[nanda_kumar21]

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

[FrankKrauseGUI]

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

 

[nanda_kumar21]

Thank you very much for the clarification.

Highly appreciate the details!

 

thanks

Nanda