Dear fans of SAP Cloud Platform Transport Management,
I would like to provide you with the brand-new (as of beginning of March 2020) roadmap for our product. As a roadmap is a forward-looking statement I have to start with a disclaimer, that the plans mentioned below can change at any time. The more formal disclaimer can be found at the end of this document.
I would like to point out three items which have become available recently:
Integration of Transport Management with SAP Solution Manager Change Request Management (and Quality Gate Management): From Support Package 10 of SAP Solution Manager 7.2 it is possible to connect Transport Management to Change Request Management, add Transport Management transport requests to change documents and trigger imports in Transport Management from SAP Solution Manager.
For more information see the blog 'Interplay of SAP Cloud Platform Transport Management, CTS+ and ChaRM in hybrid landscapes'
In the same blog you will also find information on the combination of Transport Management with Continuous Integration / Continuous Delivery. This is based on templates provided by the project 'Piper'.
Last not least Transport Management has been integrated with SAP Cloud Platform Alert Notification. This integration allows to trigger notifications of upcoming and performed transports and their outcome.
From the development we have planned for the next weeks and months I would like to point out two items:
With the planned support of Multi-Target Application (MTA) extension descriptor we plan to make it possible to add node specific configuration settings to the deployment of an application. That could be interesting if you for example would like to assign a different number of resources for your application in the test and the productive environment.
The node specific authorizations have been required by several customers. It would become possible to group your nodes by assigning parameters to specific nodes (for example 'productive'). The predefined roles could then be extended by these parameters and assigned to the corresponding users or user groups. So you could for example restrict the authorization to import into productive subaccounts to a small(er) group of people.
Call for Action
If you see something you like or miss something you urgently need please let us know by adding a comment. Thank you very much in advance.
SAP has no obligation to pursue any course of business outlined in this blog or any related document, or to develop or release any functionality mentioned therein.
This blog, or any related document and SAP's strategy and possible future developments, products and or platforms directions and functionality are all subject to change and may be changed by SAP at any time for any reason without notice. The information in this blog is not a commitment, promise or legal obligation to deliver any material, code or functionality. This blog is provided without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. This blog is for informational purposes and may not be incorporated into a contract. SAP assumes no responsibility for errors or omissions in this blog, except if such damages were caused by SAP’s intentional or gross negligence.
All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.