Application startup now prevents preloading the Template Browser and Upload Mapping Browser sections to accommodate for user cases in which the sections will not be accessed (such as users that only perform recordings or the Administrator user)
The Template Browser section loading times have been decreased by up to 70%
Few minor logic improvements to reduce nesting (not exhaustively across the entire solution)
Added support for the SAPROUTER parameter to determine the SAP Router string in all connections. The previous functionality (based on saplogon.ini) has been kept.
Previously, the SAP Router string was only determined from the ASHOST and MSHOST parameters, in compliance with the saplogon.ini file. Modern SAP systems use the XML Landscape file instead of an saplogon.ini file, so a new connection string parameter is used as a result: SAPROUTER.
Added support for duplicate keys in the SAP connection string. This is needed in some situations (OU in an SNC partner name, for example).
GUI Scripting templates will now connect using a method from the same GUI Scripting API that establishes the connection directly from the System Instance in SAP GUI, so any SAP Instance that works from SAP GUI will work with GUI Scripting.
Warning: GUI Scripting templates use the available connections in your local SAP GUI. Please make sure the “Description” value of the SAP System is the same as the “NAME” value for the instance on the System Instances section.
Previously, GUI Scripting templates were established by using a method from the SAP GUI Scripting API (SAPFEWSELib) that was based in an old version of the SAP connection string (/H/<sap router>/S/<router
port>/P/<sap router password>/H or M/<ashost or mshost>/S/<port
or service name>/G/<mshost group>). This was not compatible with newer versions of the SAP Router string (e.g. using W for the password parameter instead of P), and did not support connections via SNC.