As mentioned in Thomas Kretz’s blog, SAP Cloud Applications Studio version November 2013 (1311) is now available. Please note that SAP Cloud Applications Studio is used for several Cloud solutions from SAP and these solutions have slightly different availability dates. While there are already some SAP Cloud for Customer 1311 tenants, the planned release date for SAP Business ByDesign 1311 is November 27th. 1311 tenants on SAP Cloud Applications Studio should be available shortly after this date.
Check out the SAP Cloud Applications Studio version 1311 What's New and documentation at http://help.sap.com/studio_cloud.
What's New in the SAP Cloud Applications Studio
This document provides information about what is new in the SAP Cloud Applications studio version 1311 (November 2013).
What Is New and What Has Changed
- Migrate Old Solutions to New Compiler
You can now migrate your solutions and solution templates that you created in a studio version older than 1302 to the new scripting language compiler. The new scripting language compiler was introduced in studio version 1302; since then, all newly created solutions and solution templates have used the new scripting language compiler.
You do not need to migrate solutions and solution templates that have been created with the SDK for SAP's On-Demand Solutions 1.5 for SAP Customer OnDemand, version 1211. These solutions and solution templates have already used the new scripting compiler.
You can but you do not have to migrate your solutions; however, to benefit from the advantages of the new compiler such as better performance and new functions, you need to migrate your old solution.
For more information, see Migration Quick Guide in the studio documentation.
- Enable/Disable Button for Solutions on Your Development Tenant
You can now also disable a solution that you are developing on your development tenant. When you create a new solution on your development tenant, this solution is automatically enabled for your business user in the SAP cloud solution. This means that your solution is visible in the SAP cloud solution when you log on with your business user.
When you are developing several solutions in parallel on your development tenant, you may want to disable a solution for your business user in the SAP cloud solution, for example, if this solution affects the solution that you want to test. To do this, open the solution you want to disable and in the Implementation Manager, click Disable.
What's New in the Integrated Development Environment
This document provides information about what is new in the integrated development environment in the SAP Cloud Applications Studio version 13011 (November 2013).
What Is New and What Has Changed
The following functions are new or have changed:
The following has changed in the My Solutions window:
- Enter Partner Contact Information: In the Create Solution dialog, you can now enter partner contact information
- Display Solution Properties: You can now display the solution properties by right-clicking a solution and selecting Solution Properties.
- Change Partner Contact Information: You can change the partner contact information for a solution by right-clicking a solution and selecting Solution Properties. The Solution Properties dialog opens, where you change the contact information.
In the Add New Item dialog box, the items are now listed in alphabetical order.
For more information, see Add New Item Dialog Box in the studio documentation.
- Test Shell for Business Objects
The Test Shell for Business Objects view has been removed from the Partner Development work center. You can now execute a query for SAP business objects in the Repository Explorer of the studio; for custom business objects you call up this function in the Solution Explorer.
For more information, see Execute a Query to Explore a Business Object in the studio documentation.
What's New in the Developer Desktop
This document provides information about what is new in the developer desktop in the SAP Cloud Applications Studio version 1311 (November 2013).
What Is New
The following functions are new:
You can now use the External Web Service Integration Wizard to integrate REST services into your solution and to consume them in a script file.
This procedure enables you to control the Web service call in your business logic in a more flexible way than the integration of mashup Web service.
For more information, see Integrate an External Web Service Using REST in the studio documentation.
If you want to learn how to use this function in a real-life example, see Example: Consume a REST Service in the studio documentation.
- New Example in Documentation: Create an Approval Process (Price Request)
You can use this example to learn how to create a multistep approval process. The example illustrates a use case in which a sales representative creates a price request that requires approval by a manager and an account manager.
For more information, see Example: Create an Approval Process (Price Request) in the studio documentation.
What Has Changed
The following functions have changed:
- Tracing, Debugging, and Dump Analysis Possible on Production Tenant
You can now also execute Tracing, Debugging and Dump Analysis on a production tenant.
- External Web Service Integration Wizard
The External Web Service Integration Wizard has been redesigned completely.
For general information on integrating external Web services in the studio and for the difference between SOAP and REST, see External Web Service Integration in the studio documentation.
For information on integrating external Web services using SOAP, see Integrate anExternal Web Service Using SOAP in the studio documentation.
- EmployeeID in Approval Process and Notification Rules
You can now use fields with the EmployeeID data type as the responsible person in approvals and notifications. This is in addition to the UUID fields, which you can still select.
For more information, see Create an Approval Process and Enable Notification Rules in the studio documentation.
The following elements (“supplementary components”) of structured codes and identifiers have been never used in cloud solutions from SAP.
- listVersionID
- listAgencySchemeID
- listAgencySchemeAgencyID
- schemeVersionID
- schemeAgencySchemeID
- schemeAgencySchemeAgencyID
As of studio version 1311, these elements have been removed from a lot of data types. This change has the following impact:
- As of studio version 1311, WSDL files will no longer include these elements (attributes in .xsd schema) for many data types. The behavior of
the services does not change. Possible former usages of these attributes had been ignored in the past and are further ignored after this change. - If you have used these elements in .absl coding, please remove these usages from your coding in solutions created in older studio versions
before you open them in studio version 1311. As mentioned before, these elements were never used in business objects, so there is no need to use them.
