Transporting SAP CPI content with Figaf IRT

We want to make it a lot easier to do SAP CPI transports and document changes, and it is also one of the things that i see people struggling with. I mostly also wanted to make it possible to transport individual iFlows, because it makes the process a lot faster; otherwise, you must create some packages to contain it.

A few weeks back i posted an image of me deploying a CPI change after just 40 minutes in production. One of the comments that, yes that is fine you can make changes in production fast if you do not do any change management. We did not have any change management or documentation. I would argue that with the changes you see below we can make it in the same time.

Another pain with transport was that you needed to reconfigure afterward. In Figaf IRT you have a central repository that allows you to configure what values you want across the landscape.

IRT will enable you to see what was before on in IRT. The easy way to do SAP CPI transport with Figaf IRT.

It on the Figaf.com/IRTCloud now and will be in the next release of our onpremish tool figaf.com/IRT soon. We still have some areas that we want to improve with the process, but it is better to get feedback on what you think of the solution. With the approach, we are not able to keep the old versions on the target system.