Studio License Definitions
The licensing structure for Automate Studio is based on the number of licenses and the Studio capabilities that are associated with each type of license. Automate 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. (Automate does not offer a Developer license for RPA bots.)
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 - Digital Access API License
| API License | Capabilities |
|---|---|
|
Digital Access License |
A Digital Access License allows licensed customers to expose solutions (which have been pre-approved by Automate) to access from a third-party application. |
The terms below define the scope of the Digital Access License; they are also relevant to the applicable license restrictions. Digital Access License usage is priced according to the anticipated and actual usage levels.
| Digital Access License Terminology | Capabilities |
|---|---|
|
Digital Access API ("API") |
The API refers to process extensions APIs provided for the Foundation platform to allow third-party systems to integrate with workflows created on the Foundation platform for the purposes of creating or updating data in SAP Third-party system users are not named users on the Foundation platform. |
|
Business Object |
A business object is defined as a unique data element that can be identified by a unique key which is a combination of one or more of its parameters. An instance of a business object can be identified by this unique key. Examples: Customers or vendors in SAP. A customer number would be an instance of a business object |
|
Solution |
The term solution refers to the workflow and its associated forms that collectively are used to work on a business object. Solutions can be hierarchical if they operate on a single instance of a business object. |
|
Process |
A single process is defined as the Foundation workflow process that ultimately creates or updates data in SAP. Example: for a customer update solution, a workflow process updates one or multiple customer records in SAP. |
|
Usage |
License usage is defined as the number of business objects updated in SAP for the solution for which the Digital Access License is in use. Foundation processes that do not use the Digital Access API will not count against this usage. |
Foundation Server License
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 contact Customer Support to acquire additional non-production environments free of charge.
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 contact Customer Support to acquire additional non-production environments free of charge.
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 |
|
Platform User |
Administrators or Auditors |
| 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 contact Customer Support to acquire additional non-production environments free of charge.
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 Data extraction from SAP via Query and/or export to Excel, Access, SQL, text, XML files or web form solutions Post and Extract data to and from SAP via Direct by leveraging SAP BAPIs and remote-enabled function modules (RFMs) 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 Upload/Edit Reference Data using Excel, the Excel Add-in, or scheduled queries |
|
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 workflow that touches SAP system or EnterWorks data using Evolve Forms. |
| Limited Standard User |
Maximum of 4 logins per year with the Evolve system and these interactions are limited to:
|
|
Platform User |
Users for processes that do not contain data that has either come from SAP ERP or will end up in an 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 |
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 contact Customer Support to acquire additional non-production environments free of charge.
Evolve - Digital Access API License
This asynchronous API is installed and available with the Evolve installation. It is activated using a unique license activation code. Technical details on the API can be found here .
Digital Access licenses are priced according to the anticipated usage level over the multi-year license term period. API usage is billed upfront on the basis of the defined number of SAP records in the sales contract. Each license purchased has a defined term of 3 years or longer. Actual usage is tracked in Evolve and usage reporting will be made available on-demand or on a monthly basis. You can purchase additional numbers of records at any point by purchasing an additional multi-year usage license. We are unable to provide partial credits for an early stop to a subscription term or to roll over unused records into a subsequently purchased license.
|
License |
Capabilities |
|---|---|
|
Digital Access License |
A Digital Access license allows licensed customers to expose Automate solutions for access by third-party applications that only the customer is using. |
For the purpose of Digital Access API agreements, the terms below define the scope of the third-party Digital Access license. These terms are also relevant to the applicable license restrictions.
| Digital Access License Terminology | Capabilities |
|---|---|
|
Digital Access API or API |
The API refers to process extension APIs provided for the Evolve platform to allow third party systems to integrate with workflows created on the Evolve platform. These APIs are used to launch or interact with a workflow. The users of third-party systems are not named users on the Evolve platform. |
|
Business Object |
An SAP business object is defined as a unique data element that can be identified by a unique key which is a combination of one or more of its parameters. An instance of a business object can be identified by this unique key. Examples: Customers or vendors in SAP. A customer number would be an instance of a business object. |
|
Solution |
The term solution refers to the Evolve workflow and its associated forms that are used to possibly work with an SAP business object. The Solution can be hierarchical if it is operating on a single instance of a business object. |
|
Process |
A single process is defined as the Evolve workflow process that ultimately queries data from SAP and/or creates or updates data in SAP. Example: for a customer update solution, a workflow process updates one or multiple customer records in SAP. |
|
Usage |
License usage is defined as the number of business objects updated in SAP for the solution for which the Digital Access License is in use. Named users that interact with Evolve processes that do not use the Digital Access API will not count against this usage. |
Evolve & Studio Manager – SAP Data API License
This synchronous API is installed and available with the Evolve & Studio Manager installations. It is activated using a unique license activation code. Technical details on this API can be found here.
The SAP Data API is priced according to the anticipated usage levels over a multi-year license term period. API usage is billed upfront on the basis of the defined number of SAP records in the sales contract. Each license purchased has a defined term of 3 years or longer. Actual usage is tracked in Evolve or Studio Manager and usage reporting will be made available on-demand or on a monthly basis. You can purchase additional numbers of records at any point by purchasing an additional multi-year usage license. We are unable to provide partial credits for an early stop to a subscription term or to roll over unused records into a subsequently purchased license.
|
License |
Capabilities |
|---|---|
|
SAP Data API license |
The SAP Data API License allows licensed customers to expose Automate Studio solutions for access by third-party applications that only the customer is using. |
For the purpose of SAP Data API agreements, the terms below define the scope of the third-party SAP Data API License . These terms are also relevant to the applicable license restrictions.
| SAP Data API Terminology | Capabilities |
|---|---|
|
SAP Data API or API |
The API refers to functionality provided for the Evolve or Studio Manager platforms to allow third party systems to call and execute Automate Studio scripts. This API is used to query data from SAP and/or create or update data in SAP. The users of third-party systems are not named users on the Evolve or Studio Manager platform. |
|
Business Object |
An SAP business object is defined as a unique data element that can be identified by a unique key which is a combination of one or more of its parameters. An instance of a business object can be identified by this unique key. Examples: Customers or vendors in SAP. A customer number would be an instance of a business object. |
|
Solution |
The term solution refers to the Studio script and its associated data files that are used to work on a business object. The solution can be hierarchical if it is operating on a single instance of a business object. |
|
Process |
A single process is defined as an execution of a Studio script that ultimately queries data from SAP and/or creates or updates data in SAP. Example: for a customer update solution, a Studio script updates one or multiple customer records in SAP. |
|
Usage |
License usage is defined as the number of business objects updated in SAP for the solution for which the SAP Data API License is in use. Named users who interact with Evolve or Studio Manager processes will not count against this SAP Data API usage. |
Evolve – Portal Framework License
The Portal Framework is installed and available with the Evolve platform. It is activated using a unique license activation code. The Portal Framework is priced according to the number of externally facing portals that will be created, however there will be additional costs to host the portal in Azure. A Automate Portal Framework license does not include any Azure services. You can add additional numbers of portals at any point.
|
License |
Capabilities |
|---|---|
|
Portal Framework License |
A Portal Framework license allows customers to create portals as a front end for their Evolve system. Customers can create internal portals for their licensed users or create external portals to involve external users (like customers or vendors) in their processes. |
EnterWorks Licenses
EnterWorks is licensed as a product package based on the numbers of domains, numbers of users, types of users, and the inclusion of optional modules. Please refer to your sales order and the Automate License Restrictions for further license information.
| Named User License | Capabilities |
|---|---|
|
Full User |
Full use of the system. Can view and edit content. For example, can update the workflow. |
|
Limited/Portal User |
Limited use of the system. Can view but not edit content. Works via a web portal. |
|
Administrative User |
Full rights and privileges to enable administration of the solution. For example, provides user access and manages security.
|