Help Center>Winshuttle Connect Help

Winshuttle License Definitions

Studio License Definitions

The licensing structure for Winshuttle Studio is based on the number of licenses and the Studio capabilities that are associated with each type of license. Winshuttle offers named user Runner and Developer licenses for humans. A Runner license enables scripts for SAP to be run; a Developer license enables scripts for SAP to be created and run. For clarification of proper license use, including the differences between a named user license and an RPA bot license, please refer to the License Restrictions page.

Runner license

A Runner license includes the use of the Transaction and Query modules. See the table below for Studio capabilities included with each module.

Developer license

A Developer license includes the use of the Transaction, Query, and Direct (BAPI) modules. See the table below for Studio capabilities included with each module.

Bot license

A bot license includes the use of the Transaction and Query modules with a Studio RPA Runner or Professional User for RPA license for RPA bots. (Winshuttle does not offer a Developer license for RPA bots.)

Note: Each named user license in the tables below includes the capabilities noted in its row in addition to all capabilities for each license type listed below it in the table.

Studio Licenses

Each named user license includes the capabilities noted in addition to all capabilities noted for each license type appearing below it in the table. For example, in the table below, the Studio Developer license includes the capabilities noted in its row in addition to the Studio Runner license capabilities.

Named User
License
Capabilities

Studio Developer

SAP Integration via Transaction (recording and mapping) for Excel and Access

SAP Table Authoring via Query for Excel, Access, and text

BAPI Authoring via Direct

Studio Runner

Transaction and Query script execution for SAP

Foundation Licenses

Each named user license includes the capabilities noted in its row in addition to the capabilities of each license type appearing below it in the table. For example, the Studio Developer license includes the capabilities noted in its row in addition to those capabilities noted for the Professional, Standard, and Platform User licenses. And, the Standard license includes the capabilities noted in its row in addition to those noted for the Platform User license.

Named User License Capabilities

Studio Developer

SAP integration via Transaction (recording & mapping) for Excel, Access, & XML

SAP table authoring via Query for Excel, Access, SQL, XML, SharePoint list & text

BAPI authoring via Direct

Composer Solution Development

Professional

Transaction script execution for SAP (multiple records) - Excel & Access

Query script execution for SAP (multiple records) - Excel, Access, SQL, XML, SharePoint list & text

SAPIS Server based script execution (multiple records)

Forms execution (multiple records)

Standard

Transaction script execution to SAP (single record) - Excel & Access

Query script execution for SAP (multiple records) - Excel, Access, SQL, XML, SharePoint list & text

SAPIS Server based script execution (single record)

Forms execution (single record)

Platform User

Users for processes not containing data that has come from SAP ERP or will end up in an SAP ERP system

Administrators or Auditors

 

Foundation
User Role
License Type
  Studio
Developer
Professional Standard Platform
Studio Scripts        
Author X      
Script Approver X X X  
Data Reviewer X X X  
SAP Posting using
Excel & Access
X X X*  
         
Composer        
Author X      
         
Excel Workflow        
Originator X X X  
Contributor X X X  
Reviewer X X X  
Approver X X X  
SAP Posting X X X*  
         
Form Workflow
for SAP processes
       
Originator X X X  
Contributor X X X  
Reviewer X X X  
Approver X X X  
SAP Posting X X X*  
         
Form Workflow
for non-SAP processes
       
Originator X X X X
Contributor X X X X
Reviewer X X X X
Approver X X X X

*Standard licenses can only upload a single record at a time during SAP posting.

Bot License Capabilities

Professional User for RPA

Transaction script execution for SAP using a bot

Query script execution for SAP using a bot

SAPIS Server based script execution using a bot

Forms execution using a bot

Foundation also has a server license which is offered on a ‘per environment’ basis. Each environment is priced according to a maximum number of users (50 or fewer users, 200 or fewer users, for example). An environment can have multiple machines/instances of Foundation to scale for a higher number of users.

The Foundation license includes two non-production environments for testing. Customers can purchase an additional non-production server if they want more than two non-production environments.

User Governance Licenses

Each named user license includes the capabilities noted in its row in addition to all the capabilities of each license type appearing below it in the table. For example, the Studio Developer license includes the capabilities noted in its row in addition to the Studio Runner license capabilities.

Named User
License
Capabilities

Studio Developer

SAP Integration via Transaction (recording and mapping) for Excel and Access

SAP Table Authoring via Query for Excel, Access, and text

BAPI Authoring via Direct

Studio Runner

Transaction and Query script execution for SAP

 

Bot License Capabilities

Studio RPA Runner

Transaction script execution for SAP using a bot

Query script execution for SAP using a bot

User Governance also has a server license which is offered on a ‘per environment’ basis. Each environment is priced according to a maximum number of users (50 or fewer users, 200 or fewer users, for example). An environment can have multiple machines/instances of User Governance to scale for a higher number of users.

The User Governance license includes one non-production environment for testing. Customers can purchase an additional non-production server if they want more than one non-production environment.

Studio Manager Licenses

Each named user license includes the capabilities noted in its row in addition to all the capabilities of each license type appearing below it in the table. For example, the Studio Developer license includes the capabilities noted in its row in addition to the Studio Runner license capabilities.

Named User
License
Capabilities

Studio Developer

SAP Integration via Transaction (recording and mapping) for Excel and Access

SAP Table Authoring via Query for Excel, Access, and text

BAPI Authoring via Direct

Studio Runner

Transaction and Query script execution for SAP

 

Bot License Capabilities

Studio RPA Runner

Transaction script execution for SAP using a bot

Query script execution for SAP using a bot

Studio Manager also has a server license which is offered on a ‘per environment’ basis. Each environment is priced according to a maximum number of users (50 or fewer users, 200 or fewer users, for example). An environment can have multiple machines/instances of Studio Manager to scale for a higher number of users.

The Studio Manager license includes one non-production environment for testing. Customers can purchase an additional non-production server if they want more than one non-production environment.

Evolve Licenses

Each named user license includes the capabilities noted in its row in addition to all the capabilities of each license type appearing below it in the table. For example, the Studio Runner license includes the capabilities noted in its row in addition to those capabilities noted for the Standard User and Platform User licenses.

Named User
License
Capabilities

Studio Developer

SAP Integration via Transaction (recording and mapping) for Excel, Access, & XML

SAP Table Authoring via Query for Excel, Access, SQL, text, & XML

BAPI Authoring

Solution Designer Development

Studio Runner

Transaction script execution for SAP using Excel and Access

Query script execution for SAP using Excel, Access, and SQL, text, & XML

Get data from SAP and other capabilities that require interaction with SAP

Standard User

Review Scripts and Data Files

Transaction or Query script execution to post to SAP or get data from SAP using web forms

Reviewer, Contributors, or Originators for a workflow that touches SAP

Platform User

Users for processes that do not contain data that has come from SAP ERP or will end up in SAP ERP system

Administrators or Auditors

 

Evolve
User Role
License Type
  Studio
Developer
Studio
Runner
Standard Platform
Studio Scripts        
Author X      
Script Approver X X X  
Data Reviewer X X X  
SAP Posting using Excel & Access X X    
         
Solution Builder        
Author X      
Reference data upload/edit using Excel X X    
Reference data edit using Evolve UI X X X  
Reference data edit using scheduled queries X X    
Reference data schema creation X      
         
Excel Workflow        
Originator X X X  
Contributor X X X  
Reviewer X X X  
Approver X X X  
SAP Posting X X    
         
Form Workflow (includes smart table/repeating web services)
for SAP processes
       
Originator X X X  
Contributor X X X  
Reviewer X X X  
Approver X X X  
SAP Posting X X X  
         
Form Workflow (includes smart table/repeating web services)
for non-SAP processes
       
Originator X X X X
Contributor X X X X
Reviewer X X X X
Approver X X X X

Note: SAP interactions via the Studio application or Excel require a Studio Developer or Studio Runner license. SAP interactions include the following actions: validate, debug, test, post, and F4 look-up.

Bot License Capabilities

Standard User for RPA

Transaction script execution for SAP using a bot

Query script execution for SAP using a bot

SAPIS Server based script execution using a bot

Forms execution using a bot

Evolve also has a server license which is offered on a ‘per environment’ basis. Each environment is priced according to a maximum number of users (50 or fewer users, 200 or fewer users, for example). An environment can have multiple machines/instances of Evolve to scale for a higher number of users.

The Evolve license includes two non-production environments for testing. Customers can purchase an additional non-production server if they want more than two non-production environments.