Over the last two months, we have written a lot about all the features that are in the coming release, and that it can automate the migration. To be able to auto migration we have added quite a number of new functions, which also makes the platform more useful for everyday usage. The biggest is to make governance much tighter integration with the transports.
Transports
One of the big things we needed to figure out was how to do transports. It is one of the areas where I do not think SAP PI/CPI is lacking modern change management. Sure CTS transports work but they don’t really give good visibility of what is transported.
Figaf can handle full transport no more need for CTS+. A number of our customers are not using CTS+ and therefore have not really been able to leverage a good way to do change management. So now you can just switch a flag on the landscape definition in Figaf Integration Tool and then be able to use Figaf to handle all your transports.
In the transport, we have now added an option to set up approval. So Architects can approve all transports before they can be imported.
Speaking of transports we have added two new options for the transport.
- Direct access to transport configuration from one view. So you can configure what hostnames should be in production. Once the transport has been approved it is not possible to change the configuration, otherwise, you will need to create a new transport.
- Virtual comparisons of change of what is change when applying the change. This makes it a lot easier to see what really will be changed when applying the patch.
Transport overview with approval 
Simulated import and affected change 
Landscape configuration to specify non transportble values in QA and production
We are considering how we can improve transport better. That there should be required testing on QA/Test system or secondary approval before transport can be imported to production. Only specific users can approve transports or they are imported at specific times.
Releases
Normally you will just develop single development and fix an interface at the time with a link to the service request. Other times you have a release or wave with some new interfaces that need to be applied on at special time and that contains a number of changes. Which this functionality it is possible to group and manage multiple tickets and interface at the mime.
Demo
See the video about how these functions work together, making governance possible.
So now we are just waiting on our tests is working satisfying so we can create our release. There is still a number of regressions and flows that we need to optimize. We hope to release a beta of it soon.
Be the first to know
You can signup now and be one of the first to know when something changes.