Help Center>Studio (Connect)

Studio v11 release notes

The best practice is to run the same version of Studio and the Winshuttle Function Module.

Studio v11.4.1

Released February 20, 2018

To provide greater transparency, Winshuttle is providing more information in the release notes than was available for previous versions. The list of known issues is a cumulative list from all versions.

New features

Support for SAP S4/HANA-1709.

Bugs fixed

VC redistributables 2008 and 2013 are now installed during Studio MSI silent installation.

Known issues

SAP GUI 750: For GUI scripting transaction scripts, incorrect background color gets filled for the log message and incorrect error count is displayed on running the script.
The total time saved calculation for ROI data of scripts that were run in v10.x is not displayed correctly Studio v11.
Script developers who do not have DD03L object authorizations will not be able to map scripts.
Converting a script from Non-Batch mode to Batch mode does not give any warning about Read from SAP fields and downloads the data in Batch mode.
Workbooks that contain multiple script macros require multiple logins to SAP.
The option for saving an auto logon credential (ALC) is not supported for EP logon with browser.
Scheduling linked Query scripts that contain run-time variables returns an object reference error.
When a transform is applied, Studio continues to process rows in which there is no data, and log messages are returned for those rows.
Long text fields are omitted from the backup file when you choose the Backup Data option on the Run tab.
The RTV form does not open when scheduling a Query run from the Scheduled Tasks screen.
The maximum size for attached files is 30 MB, but performance might be affected by the SAP system.
The message returned when auto logon credentials point to an SAP system that is no longer available is not informative. .
Query scripts cannot be run successfully from the command line when using SAP SSO.
After backup and restore, Query scripts that contain input files cannot be run.
S/4HANA does not support EP logon and SP Nego.
When a Query script is run manually from the client and the user was not the creator of the SharePoint list, the Query results are not properly written to the SharePoint list. This issue does not occur for the end FORM user.

Studio v11.4.0

Released January 31, 2018

New features and improvements

Support for SAP GUI 750.
Support for Secure Network Connection (SNC) without Single Sign-On (SSO).
The SAPNetWeaver RFC library is required for using Secure Network Connection (SNC) without Single Sign-On (SSO), and it must be downloaded from SAP.
The classic RFC library is included in the Studio v11.3.0 installation.
The same fields in alias tables can now be selected as criteria fields on the Criteria tab.
You can now search for intermediate joins immediately, without first searching for direct joins.
You can now change the maximum file size for attached documents in the Studio Options box.
You can now change the Recording Time (core recording time) and Transaction code script properties in the Properties panel.
You can now add custom fields and map them.
Scripts that use BAPI_ACC_DOCUMENT_POST now take the user name directly from the script properties.
Studio now includes a BAPI that supports uploading documents that contain multiple currencies when WFM v11.4.0 is installed on the SAP system.
You can write header items, line items or both. You can use the Preserve header item formatting option to avoid writing over customized formatting for headers.

Bugs fixed

ME21N no longer returns false errors during validation or simulation.
Scripts that contain SSO auto logon credentials (ALCs) can now be run from the Excel Add-in.
Running selected rows and filtered rows now works in linked scripts.
PFCG scripts can now be run.
Skip screen indicator is respected in download scripts, and data is downloaded to the correct columns.
The production server warning is now shown when scheduling Query scripts to run on production servers (if the production warning option is set in the Studio options).
Query script files with file names that contain ( and ) characters can now be submitted to Foundation.
Data is no longer committed to SAP when running validation on PA30 scripts.
Transform formulas are now processed even if the Start row for the run is greater than the row specified in the formula.
Running validation on unprocessed rows now limits the validation to those rows, instead of validating all rows.
Transaction scripts can now be scheduled from the Studio client.
Studio now respects the recording mode of individual scripts in a chain that begins with a script that was recorded in Non-Batch with Controls mode.
Clicking Check Data after validating or simulating no longer returns an object reference error.

Known issues

The total time saved calculation for ROI data of scripts that were run in v10.x is not displayed correctly Studio v11.
Script developers who do not have DD03L object authorizations will not be able to map scripts.
Converting a script from Non-Batch mode to Batch mode does not give any warning about Read from SAP fields and downloads the data in Batch mode.
Workbooks that contain multiple script macros require multiple logins to SAP.
VC redistributables 2008 and 2013 are not getting installed during Studio MSI silent installation.
The option for saving an auto logon credential (ALC) is not supported for EP logon with browser.
Scheduling linked Query scripts that contain run-time variables returns an object reference error.
When a transform is applied, Studio continues to process rows in which there is no data, and log messages are returned for those rows.
Long text fields are omitted from the backup file when you choose the Backup Data option on the Run tab.
The RTV form does not open when scheduling a Query run from the Scheduled Tasks screen.
The maximum size for attached files is 30 MB, but performance might be affected by the SAP system.
The message returned when auto logon credentials point to an SAP system that is no longer available is not informative. .
Query scripts cannot be run successfully from the command line when using SAP SSO.
After backup and restore, Query scripts that contain input files cannot be run.
S/4HANA does not support EP logon and SP Nego.
When a Query script is run manually from the client and the user was not the creator of the SharePoint list, the Query results are not properly written to the SharePoint list. This issue does not occur for the end FORM user.

Studio v11.3

Released June 9, 2017

New features and improvements

Support for Secure Network Connection (SNC) without Single Sign-On (SSO).
The SAPNetWeaver RFC library is required for using Secure Network Connection (SNC) without Single Sign-On (SSO), and it must be downloaded from SAP.
The classic RFC library is included in the Studio v11.3.0 installation.
The same fields in alias tables can now be selected as criteria fields on the Criteria tab.
You can now search for intermediate joins immediately, without first searching for direct joins.
You can now change the maximum file size for attached documents in the Studio Options box.
You can now increase the SAP screen size when you are recording, debugging, or using GUI Scripting. To increase the screen size, add the following parameters to Appoptions.xml:
- Maximum size: <SapDefSize /><SapNoBiend />
- Minimum size: <SapDefSize>X</SapDefSize><SapNoBiend />
Simulate support for the following t-codes: F-02, F-05, F-22, F-43, F-65, FB01, FB01L, FB50L, FB65, FB75, FBB1, FBV1, FV50, FV50L, FV60, FV65, FV70, FV75. The t-code FBD1 Simulate no longer works in SAP and therefore is no longer supported.

Differences from v11.2.x

During installation, Studio now prompts to close all open instances of Excel.
Passwords can now be copied and pasted into the Password box.
When scheduling a Query script to run locally from the Excel Add-in, success scheduling is now confirmed by a message.
The "Object reference not set to an instance of an object" error no longer appears when running linked Query scripts that use individual settings.
The "Object reference not set to an instance of an object" error no longer appears when you click Cancel in the SAP Logon box of the second script in a script chain.
The "Object reference not set to an instance of an object" error no longer appears when you install Studio and then open Excel before you open Studio.
The correct message is now returned from SAP, instead of "No message is returned from SAP" or "Control data is obsolete."
The PFCG "No favorites exist" message is now suppressed when running a script that was recorded in GUI Scripting mode, and the script no longer fails. The message suppression is controlled by a <GuiMessage Id="S#" Number="287" /> entry in ShuttleRule.xml.
Production policy is no longer applied to non-production servers.
Success message now appears when scheduling a script from the Excel Add-in.
Changes to the Log description are now retained.
In cell-based mapping, log files can no longer be mapped to columns.
Runners can no longer change script properties on the Map tab.
In ME51N, the PR number is now returned in the Log message.
Queries no longer fail when criteria values include single quotation marks.
Studio no longer returns success messages for Validate and Simulate when the run will fail because the material, customer, or vendor is already in the SAP system.
The Find feature now works correctly.
Description fields can now be mapped in Access from the Add Column box.
Scripts that were recorded in GUI Scripting mode no longer return an error when the skip field indicator is blank.

Known issues

The ROI data of scripts that were run in v10.x are not displayed in Studio v11.
Script developers who do not have DD03L object authorizations will not be able to map scripts.
Converting a script from Non-Batch mode to Batch mode does not give any warning about Read from SAP fields and downloads the data in Batch mode.
Workbooks that contain multiple script macros require multiple logins to SAP.
The option for saving an auto logon credential (ALC) is not supported for EP logon with browser.
Scheduling linked Query scripts that contain run-time variables returns an object reference error.
When a transform is applied, Studio continues to process rows in which there is no data, and log messages are returned for those rows.
Long text fields are omitted from the backup file when you choose the Backup Data option on the Run tab.
Clicking Check Data after validating or simulating returns an object reference error.
The RTV form does not open when scheduling a Query run from the Scheduled Tasks screen.
The maximum size for attached files is 30 MB, but upload performance will depend specifically on the network speed and the SAP server load.
Studio does not respect the recording mode of individual scripts in a chain that begins with a script that was recorded in Non-Batch with Controls mode. Previously, linked scripts that were recorded in Batch mode were being run in Non-Batch with Controls mode.
EP logon and SP Nego are not currently supported in S/4 HANA.

Studio v11.2.0

Released January 31, 2017

New features

The Between operator appears as >=*=< to represent that it is inclusive in Studio v11.x.
The Between operator for Studio v10.x scripts that are run in Studio v11.2 appears as A > 2 and A < 3 to represent that it is not inclusive.
Studio v11.2 converts the v10.x From-To operator to Between; v10.x will display the v11.x Between operator as From-To.
Support for Service Port through Studio: If you are logging on to a Group Logon SAP server, you can enter the port number in the SAP Logon box. If the port number is already specified in the .ini/.xml file, it is displayed in the SAP Logon box.
Support for S4 HANA 1610 BASIS-751: WFM version 11.2 must be installed.

Bugs fixed

The Edit button now works when you try to change a scheduled task in Connect mode.
The Winshuttle Function Module (WFM) now respects the recording mode that is chosen in Studio v11.2 even if it differs from the preferred mode that is specified in /WINSHTLQ/ADMPANEL.
Scripts that were created in v10.x and include a download field in a cell-based loop no longer return an error.
Query now adjusts when one operand is left blank while using the Between operator:
- If the left operand is blank, Query returns all data less than or equal to the right operand value.
- If the right operand is blank, Query returns the data that equals the left operand value.
- If both operands are blank, Query returns all the data.
Document attachment support for t-code MIR4 added.
An object reference error is no longer returned when you schedule an InfoSet query.
A GUI Scripting error is no longer returned while recording in GUI Scripting mode when the Allow multithreaded GUI scripting option is checked on the SAP Settings tab in the Studio Options box.
Excel files that are closed are now removed from the Project list in the Excel Visual Basic Editor.
Studio v11 no longer returns a logon error when switching the network or the network cable is unplugged.
If the operating system language is not supported by Studio v11 client or add-in, the client or add-in opens in English.
Clicking the Check Update button no longer returns a Not authorized to upgrade error when the license is still in the maintenance period.
Query scripts running on non-WFM servers no longer return an object reference error.
The Write Header command now writes the File Attachment Log header in the Excel Add-in.
An error is no longer returned if you click Add to Workspace before entering any tables in the Quick Add box.

Known issues

Studio v11.2.0 is not compatible with Winshuttle Function Module (WFM) 11.1.1.
The ROI data of scripts that were run in v10.x are not displayed in Studio v11.
Converting a script from Non-Batch mode to Batch mode does not give any warning about Read from SAP fields and downloads the data in Batch mode.
Workbooks that contain multiple script macros require multiple logins to SAP.
The option for saving an auto logon credential (ALC) is not supported for EP logon with browser.
Clicking Check Data after validating or simulating returns an object reference error.
An object reference error is returned if you click Cancel in the SAP Logon box of the second script in a script chain.
Using SNC without SSO is not supported in Studio v11.x. Be sure that the SNC logon with user/password (no Single Sign-On) box is not checked.
The RTV form does not open when scheduling a Query run from the Scheduled Tasks screen.
If a Query criteria value includes quotation marks, the query fails, because Studio adds double quotation marks. This applies both to Studio v11 scripts and to 10.x scripts that include single quotation marks.
Script developers who do not have DD03L object authorizations will not be able to map scripts.

Studio v11.1.6

Released January 18, 2017

New feature

Document attachment support for t-code MIR4 added.

Bug fixed

Transaction script files can now be opened directly from File Explorer.
Query now adjusts when one operand is left blank while using the Between operator:
- If the left operand is blank, Query returns all data less than or equal to the right operand value.
- If the right operand is blank, Query returns the data that equals the left operand value.
- If both operands are blank, Query returns all the data.
Excel files that are closed are now removed from the Project list in the Excel Visual Basic Editor.
Clicking the Check Update button no longer returns a Not authorized to upgrade error when the license is still in the maintenance period.
If the operating system language is not supported by Studio v11 client or add-in, the client or add-in opens in English.
Studio v11 no longer returns a logon error when switching the network or the network cable is unplugged.
Studio v11 now recognizes Date/Time formats that use a dot.
Scripts that were created in v10.x and include a download field in a cell-based loop no longer return an error.

Known issues

The GUI Scripting error continues to be returned if you are connecting through EP Logon with Browser on a 64-bit computer and recording in GUI Scripting mode and the Allow multithreaded GUI scripting option is checked.
Query scripts running on non-WFM servers return an object reference error.
The Write Header command is not writing the File Attachment Log header in the Excel Add-in.
The RTV form does not open when scheduling a Query run from the Scheduled Tasks screen.
An error is returned if you click Add to Workspace before entering any tables in the Quick add box.
Fields that are not supported as criteria fields can no longer be selected as criteria fields.
Using SNC without SSO is not supported in Studio v11.x. Be sure that the SNC logon with user/password (no Single Sign-On) box is not checked.
If a Query criteria value includes quotation marks, the query fails, because Studio adds double quotation marks. This applies both to Studio v11 scripts and to 10.x scripts that include single quotation marks.
Script developers who do not have DD03L object authorizations will not be able to map scripts.

Studio v11.1.1

Released September 30, 2016

New features

Support for EHP8 SAP server.
Winshuttle Utility Kit

Bugs fixed

Script is no longer blocked in the add-in when a cell is selected for the Run on Selected Rows command.
Proxy authentication error is no longer returned when you try to connect through the company proxy settings in Transaction v10.7 after installing Studio v11.
Linked Query scripts no longer return the "same fields should be used with alias" error, which was blocking the Query run.
If restrictions are applied, Studio extracts data but returns a message that displays the object or field that is restricted.
Start Row no longer changes to the End Row value in instances where the Start Row is greater.
The Studio search results no longer display InfoSets that have been deleted from SAP.

Known issues

Query scripts running on non-WFM servers return an object reference error.
The Write Header command is not writing the File Attachment Log header in the Excel Add-in.
The RTV form does not open when scheduling a Query run from the Scheduled Tasks screen.
An error is returned if you click Add to Workspace before entering any tables in the Quick add box.
Fields that are not supported as criteria fields can no longer be selected as criteria fields.
Using SNC without SSO is not supported in Studio v11.x. Be sure that the SNC logon with user/password (no Single Sign-On) box is not checked.
If a Query criteria value includes quotation marks, the query fails, because Studio adds double quotation marks. This applies both to Studio v11 scripts and to 10.x scripts that include single quotation marks.
Script developers who do not have DD03L object authorizations will not be able to map scripts.

Studio v11.1.0

Released June 30, 2016

New features

Studio v11.1.0 supports SAP GUI 740, Windows 10, and Microsoft Office 16.
The Simulate feature now supports FB01, FBD1, and FBS1.
Cluster tables for queries are now supported.
Only data files that contain unsupported elements (PivotTables, charts, and graphs) open as read-only in Studio v11.1.0.
Multiple fields can be mapped as download fields.
Auto logon credentials can be edited.
Macros can be used to run scripts that are not published to Excel.
Run reason is required for scripts that are run by using macros.
Installation is automatically based on the locale setting on the computer.
Chained scripts support relative paths. If someone sends you a script chain in email, you can copy all of the linked scripts into one folder.

Bugs fixed

Clicking Restore Defaults in the Studio Options box now sets Auto Update at 30 days.
The TSTC.CINFO hex field is now supported in queries.
When scheduling a script to run weekly, you can select multiple days of the week.
Complete run reason is shown for Access-based Query scripts.
Criteria fields require valid values.
Criteria fields can no longer be selected in the right table of a left outer join.
Document attachment logs are now written for scripts that contain both long text fields and document attachment fields.
For queries based on LDBs, field descriptions in the Mapper and in the Excel data file now match.
If on Index fields can now be used with multiple-sheet loops.
Validate is now supported for nested loops.
Query performance is now equal to or faster than performance in 10.x.
Data type options are now scoped correctly for Connect mode.

Known issues

Fields that are not supported as criteria fields can no longer be selected as criteria fields.
Scripts are blocked in the add-in when a cell is selected for the Run on Selected Rows command.
Proxy authentication error is returned when you try to connect through the company proxy settings in Transaction v10.7 after installing Studio v11.
Linked Query scripts return the "same fields should be used with alias" error, which was blocking the Query run.
Start Row changes to the End Row value in instances where the Start Row is greater.
The Studio search results display InfoSets that have been deleted from SAP.
Using SNC without SSO is not supported in Studio v11.x. Be sure that the SNC logon with user/password (no Single Sign-On) box is not checked.
If a Query criteria value includes quotation marks, the query fails, because Studio adds double quotation marks. This applies both to Studio v11 scripts and to 10.x scripts that include single quotation marks.
Script developers who do not have DD03L object authorizations will not be able to map scripts.

Studio v11.0.5

Released November 23, 2016

New features and improvements

Added an option for configuring the file location of the auto logon credential (ALC) file. The ALC file can now be kept on a network and shared.
Note: When you change the location of the ALC files, the list of available credentials is cleared. To keep existing logons, manually copy the LogonSettings.xml, WsSAPConnector.xml, and EpLogonSettings_11.xml files to the new location.

Bugs fixed

ALC location is now available for use when running scripts from the command line.

Studio v11 no longer returns a logon error when switching the network or the network cable is unplugged.

Known issues

If a script contains multiple commit codes, disabling the extra commit code rows will not prevent the multiple-commit code error. Note that deleting the extra commit code rows will prevent the error.
When running an FB03 script with attached documents, the run log shows No message returned from SAP as an error and the document attachment does not work. Note that this works for scripts that were recorded in Batch mode. This issue can also appear in MM03 and VA03 scripts.
If you are using the Tab and Arrow keys to navigate through Studio v11, you will find options for data file types that Studio v11 does not support. For example, in Query, you will find options for using SQL Server or a SharePoint list. These data file types are not allowed with Connect licensing. This issue is not visible if you are using the mouse to work with Studio v11.
Using SNC without SSO is not supported in Studio v11.x. Be sure that the SNC logon with user/password (no Single Sign-On) box is not checked.
If a Query criteria value includes quotation marks, the query fails, because Studio adds double quotation marks. This applies both to Studio v11 scripts and to 10.x scripts that include single quotation marks.
Script developers who do not have DD03L object authorizations will not be able to map scripts.

Studio v11.0.3

This version continues to work with Winshuttle Function Model v11.

New features and improvements

Studio v11 configuration options can be managed before installation; this applies to both .exe and .msi installations.
Support for TLS 1.1 and higher.

Bugs fixed

The "Not a legal OleAut date" error fixed.
Problems fixed for dates on non-EN locales. Dates are now uploaded in the correct format.
The Mapper no longer disables the mapping option in the ribbon for other fields when the value for a document attachment field is <Use current file>.
Editing options on the Map tab are now available when the Use current file box is checked.
In If conditions that use Compare with column, the Insert Before option now inserts the column before, instead of in the same column.
Restarting Studio after switching to a different date format no longer returns the "String not a valid DateTime" error.

Known issues

If a script contains multiple commit codes, disabling the extra commit code rows will not prevent the multiple-commit code error. Note that deleting the extra commit code rows will prevent the error.
When running an FB03 script with attached documents, the run log shows No message returned from SAP as an error and the document attachment does not work. Note that this works for scripts that were recorded in Batch mode. This issue can also appear in MM03 and VA03 scripts.
If you are using the Tab and Arrow keys to navigate through Studio v11, you will find options for data file types that Studio v11 does not support. For example, in Query, you will find options for using SQL Server or a SharePoint list. These data file types are not allowed with Connect licensing. This issue is not visible if you are using the mouse to work with Studio v11.
Using SNC without SSO is not supported in Studio v11.x. Be sure that the SNC logon with user/password (no Single Sign-On) box is not checked.
If a Query criteria value includes quotation marks, the query fails, because Studio adds double quotation marks. This applies both to Studio v11 scripts and to 10.x scripts that include single quotation marks.
Script developers who do not have DD03L object authorizations will not be able to map scripts.

Studio v11.0.1

Bugs fixed

Resolved conflicts with mapped drives.

Known issues

If you are using the Tab and Arrow keys to navigate through Studio v11, you will find options for data file types that Studio v11 does not support. For example, in Query, you will find options for using SQL Server or a SharePoint list. These data file types are not allowed with Connect licensing. This issue is not visible if you are using the mouse to work with Studio v11.
Using SNC without SSO is not supported in Studio v11.x. Be sure that the SNC logon with user/password (no Single Sign-On) box is not checked.
If a Query criteria value includes quotation marks, the query fails, because Studio adds double quotation marks. This applies both to Studio v11 scripts and to 10.x scripts that include single quotation marks.
Script developers who do not have DD03L object authorizations will not be able to map scripts.

Studio v11.0.0

Released April 20, 2016

New features

Single program, single add-in, single installer

The Transaction, Query, and Direct modules for both script developers and script runners are all installed at the same time. Your license determines which modules you can use.

The Excel Add-in is included in the installation.

New look and experience

Studio v11 features a familiar, ribbon-based user interface that is similar to Microsoft Office.

The improved user experience includes instructions on the program screens, so you can get help without leaving Studio.

Edit your data from inside Studio

Studio v11 displays a live, embedded Microsoft Excel worksheet.

More control over data formats

New features give you more control:

Excel transforms: Use Excel formulas to ensure consistent data formatting.
Padding options: Use padding options in both Query and Transaction to hide complexity from runners.
Allowed values: Configure a list of allowed values or rules that a field should conform to.

Winshuttle Function Module dependency

Studio v11 comes with a richer set of integration opportunities when deployed together with Winshuttle Function Module (WFM) v11. This ABAP component supports the use of Long Text and Document Attachment extensions for change and display transactions. WFM v11 also includes support for Vendor and Customer IBAN transactions.

In addition, for customers that use the query capabilities of Winshuttle Studio v11 with Connect or with Foundation, WFM v11 features unique functions that support more advanced integration scenarios.

The Winshuttle Function Module is not a prerequisite for Winshuttle Studio users, but it reduces the number of SAP authorizations that users require. Certain functions also perform faster with the WFM, such as data validation and data simulation.

Other new features and improvements

Complex If conditions
Industry-standard Between operator (value 1 <= x <= value 2)
Offline validation
Locking for run settings
Improved application feedback
Better document attachment and long text handling
Streamlined process for linking scripts
No administrator options layer or restrictions on the number of tables and joins

Known issues

If you are using the Tab and Arrow keys to navigate through Studio v11, you will find options for data file types that Studio v11 does not support. For example, in Query, you will find options for using SQL Server or a SharePoint list. These data file types are not allowed with Connect licensing. This issue is not visible if you are using the mouse to work with Studio v11.
Using SNC without SSO is not supported in Studio v11.x. Be sure that the SNC logon with user/password (no Single Sign-On) box is not checked.
If a Query criteria value includes quotation marks, the query fails, because Studio adds double quotation marks. This applies both to Studio v11 scripts and to 10.x scripts that include single quotation marks.
Script developers who do not have DD03L object authorizations will not be able to map scripts.