Help Center>Studio v11 (Foundation)

Studio v11 release notes

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

Studio v11.2.12

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 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.
Improvements made to document attachment, including support for .zip files and uploading files from a SharePoint library.
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.
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.
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.2.12 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

VC redistributable 2013 is now installed during Studio MSI silent installation.
Read scripts can now read multiple lines when mapped to XML.
Queries run on systems that have an older version of Winshuttle Function Module installed no longer return the error Not enough storage available to process this command.
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 redistributable 2008 is 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.
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.
During a script run, Excel 2016 returns a read-only message. (This issue is fixed for Excel 2010 and earlier versions.)
Scripts that are mapped to SQL Server return truncated Run logs.
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.
Query scripts that include input files with http:// paths cannot be run from the command line. This is not an issue for input files with local paths.
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.
Log messages for Query scripts are replaced by a GUID in scripts that are mapped to Access or SQL Server. The workaround is to increase the size of the log cell in Excel.
Submitting linked scripts that were created in v10.x returns the "File with same name already exists" error message. Linked scripts that were created in v10.x must be renamed and resubmitted to Foundation.
Scheduled AutoRun times are not accurately reflected in the Excel Add-in.
Recurring scheduled Query scripts that return data to a SharePoint list must be recreated in Studio v11.4.0/v11.2.12.
Submitting supporting documents from multiple document libraries is not supported in Query script submission.
File names of scripts that are submitted to Foundation have a 128-character limit.
If a Query script is re-submitted by a different user, the data-required task is assigned to the user who first submitted the script.
The XML data type is no longer available and scripts can no longer be published as web services.
Studio is not automatically closed after a license expires or is revoked.

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 on the Foundation site, it is displayed in the SAP Logon box.
Auto Run now respects date and number formats if the user's locale is different from the server's locale.
Support for S4 HANA 1610 BASIS-751: WFM version 11.2 must be installed.
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.
Removed the 5 MB document file attachment limitation.
The default maximum file size for file attachment is set at 30 MB.
The tested maximum file size for attachments for web services is 20 MB.
You can change the maximum file size by changing the value for the DOCUMENTUPLOADSIZE parameter in Shuttlerule.xml.
<DOCUMENTUPLOADSIZE Size="20"></DOCUMENTUPLOADSIZE>
Important: Upload speed depends on the network and on the SAP system.

Bugs fixed

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.
Query scripts that contain more than one In operator pointing to dynamic lists, where one of those lists is the current data file, do not cause Studio v11.2 to shut down.
Sorting fields and setting fields as required now work in Query scripts that are published as web services
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.

Known issues

Studio v11.2.0 requires Foundation v11.2.0; it is not compatible with Foundation v11.1.1.
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.
The ALC drop-down list appears empty if you do not enter a description when you save the SAP server on the Foundation site.
Local scheduling is not supported for scripts that have a data file workflow.
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.
Transaction scripts cannot be scheduled from Studio; instead, they can be scheduled from the Excel Add-in.

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, except for in the case of scheduling on the server (see the known issue below).
Scripts that were created in v10.x and include a download field in a cell-based loop no longer return an error.

Known issues

Scripts cannot be scheduled on the server if the operating system Date/Time format uses a dot.
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.
If the script is being run on a server that is set to a language other than English, dates in an Excel worksheet need to be formatted as text and in the appropriate format for that language.
Sorting fields and setting fields as required does not work for Query scripts that are published as web services.
Transaction scripts cannot be scheduled from Studio; instead, they can be scheduled from the Excel Add-in.

Studio v11.1.1

Released September 30, 2016

New features

Support for EHP8 SAP server.
Winshuttle Utility Kit
Foundation upgrade and migration support: 10.x submitted test scripts and data files will work with Studio 11.1 clients after Foundation setups are upgraded to Foundation 11.1.

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.
Query scripts that contain more than one In operator pointing to dynamic lists, where one of those lists is the current data file, cause Studio v11.1.0 to shut down.
Sorting fields and setting fields as required does not work for Query scripts that are published as web services.
If an XML form contains a nested loop, results are not written to the Validate Log field.
If the script is being run on a server that is set to a language other than English, dates in an Excel worksheet need to be formatted as text and in the appropriate format for that language.
If a linked script has one or more spaces in the file name, it will not run in a macro because the space is converted to %20 in the URL.
Transaction scripts cannot be scheduled from Studio; instead, they can be scheduled from the Excel Add-in.

Studio v11.1.0

Released June 30, 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.

Workflow integration improvements

Studio v11.1 provides a more streamlined workflow between the client software and Microsoft Excel.

Enhancements include:

Templates are automatically saved.
The data file destination is chosen based on the process.
When using built-in workflows, the data reviewer is specified during data file submission. There is no separate task.
The data contribution process is easier.
In-progress indicators during file submission and approval processing.
The data template version is checked during opening and submitting.
The reviewer can specify a different SAP system.
Sheets can be locked during script submission.

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

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.
Query scripts that contain more than one In operator pointing to dynamic lists, where one of those lists is the current data file, cause Studio v11.1.0 to shut down.
If an XML form contains a nested loop, results are not written to the Validate Log field.
If the script is being run on a server that is set to a language other than English, dates in an Excel worksheet need to be formatted as text and in the appropriate format for that language.
If a linked script has one or more spaces in the file name, it will not run in a macro because the space is converted to %20 in the URL.