What is the transition plan from 10x to v11? (How do I upgrade?)
Studio v11 will coexist with 10.x. You just need to install Studio v11 and either keep 10.x or remove/uninstall it. If you wish to retain both products for a period of time, the only additional requirement is to disable 10.x add-ins and fully switch to the 11.x add-in (which is backwards compatible). User Governance and Foundation customers will need to wait until v11.1 to transition.
Do I need to recreate my current scripts/queries?
No! However there are new features you may want to use, and you will need to amend scripts accordingly.
Will my Excel templates with Macros be affected?
No, however if your macros are used to execute scripts, they may need to be modified to accommodate the new syntax, which has more features.
Who needs to be involved in the upgrade?
No one else typically needs to be involved if you have administrator rights on your machine. If you're a Foundation user, you will need to wait until the 11.1 release.
Does my entire company need to upgrade at the same time, or can I as an individual user upgrade to v11?
There is no requirement to upgrade all users, unless the installation is part of a standard software image on all machines. Because Studio v11 coexists with 10.x, you typically only need the additional installer to be incrementally added to the IT installer framework for PC software images. Reverting to an older format script means you will forfeit some of the new v11 features.
How long will the upgrade take?
The upgrade is generally completed in less than 10 minutes. Winshuttle can be used during the upgrade, but it is not recommended.
What are some of the usability improvements?
Studio v11's new UI mirrors the Excel interface, and you now have the option to work in Excel or the Studio application. Data can be edited, added and executed directly within the application. The Excel add-in includes additional run capabilities that align more closely to user capabilities in the full application. The application is now very compatible with contemporary display screens, and there are more options for data validation, scheduling of runs, script chaining, and mixing and matching query and transaction scripts.
What are the release dates for v11? v11.2 January 2017 v11.3 May 2017 v11.4 September 2017
Enhancements compared to v10, by feature.
Single Installer Customers no longer have to work out which products to install one download, easier to roll out to the organization and individual users. Improved Add-in consistency Having similar user interfaces across Excel and the Studio app accelerates and eases adoption and sustained use customers can now use the Studio app to set up data instead of Excel. More data pinning and validation options Script authors can more easily regulate what data is acceptable in their template. Simplified BAPI and rFM (remote function module) distillation Full Studio license now gives you the ability to use SAP APIs, which can make certain Transaction recordings easier. Improved ALF (auto logon file) management Log on to SAP one time without having to re-enter credentials multiple times. Significant script chaining advances It is now easier to link and chain scripts that can execute one after the other in a sequential fashion for example, a new material creation. More granular scheduling Schedule runs in increments of 30 minutes with additional options for frequency. Higher data validation throughput Faster validation allows you to get to the point where you push data to SAP faster. Improved the Excel upload and download speed to SAP Allows you to run your business faster.
What does licensing for v11 look like?
There is effectively no licensing change, and the single v11 product is now more aligned with what we sell and license. Your existing licenses will be automatically acknowledged and applied to this version. For example, if you are a Transaction Runner user, you will only be able to use Transaction scripts; if you are a Query license holder, you can only create and execute queries; etc. All license holders must be on Connect to use this product. A Studio license holder can use all tools.
Are new licenses required?
What products are (not) included in the v11 release?
Studio includes the Transaction, Query, Direct, Transaction Runner and Query Runner modules. What you're able to use is dependent on the license(s) you are assigned.
Why should I upgrade? What additional functionality is included?
Studio v11 has several advantages, like having one installer for all Winshuttle desktop products for 32bit and 64bit systems - the same product for Transaction, Query, Author or Runner users. There is extensive support for building and running Transactions, Queries and BAPIs all in one product. You can create scripts for numerous types of transactions and business objects in a variety of modes, including a new Winshuttle exclusive mode. Commonly used characteristics of recordings are now easily accessed during authoring and distilling activities when using the v11 Function Module. There are also new features enabled, such as whole document simulation and improved data validation and performance.
What functionality is lost, if any?
No core functionality is lost. Some features have moved to different areas of the application, and others have been deprecated due to lack of use (e.g.: pre-delivered macros and macro embedding). If these features are identified as important, they may be reintroduced. Please see the release notes for a comprehensive listing of issues.
Will there be a regular release cycle for new versions?
More regular release cycles are planned - v11.1 is planned for the end of the Summer 2016
Where did the non-batch recording mode go?
Non-Batch and other recording modes are available as alternative modes of recording when the WFM is not present.
You can change the default recording method under the application options in the backstage.
If you have the Winshuttle Function Module (WFM) installed, the preferred recording method is STANDARD, which may or may not be Non-Batch mode - depending on what Winshuttle determines is the 'best' recording mode.
The term 'Non-Batch' is not understood in the world of SAP unless you are a Winshuttle customer it is something unique to Winshuttle. For SAP ABAP and Integration veterans, the only understood methods are Batch Input, GUI Scripting, BAPI and Call Transaction over RFC. Call Transaction over RFC is Winshuttle's Non-Batch.
Is the Winshuttle Function Module required? If yes, what version?
The WFM is not required, but it is recommended. The latest version is 11. If you do not have the WFM, you may have to increase your user security authorizations.
Since it is one unified client, can I chain Transaction and Query scripts together?
This is not available with earlier releases of v.11.0, but is planned for future releases. The specific version this will be available in is still TBD.
Can I use v11 scripts in an older client?
This is only possible if you save your v11 script in a legacy format, which is a file save option.
What is simulate?
Simulate is available as a feature, and is only relevant to some SAP transactions that support this action.
Simulate performs a number of checks in SAP that are not undertaken when using the normal navigation options in the SAP GUI.
This is particularly useful with financial transactions.