← Blog

Approve SAP CPI iflow changes

How Figaf lets you transport only iflow configuration in SAP CPI, so every configuration change gets an approval process and documentation.

February 4, 2021 · 1 min read

How do you ensure that changes to the SAP CPI iflows in production all have been approved?

The manual approach is pretty much impossible. You can only restrict the users that have access to apply configuration.

We have had an option to govern and transport iflows. But if you needed to make a modification to a configuration, you needed to transport a new version of the iflow to make modifications to the configuration.

With the new setup you can just use the normal Figaf Transport process to transport only iflow configuration. This will allow you to have approval process and documentation for each change you make of an iflow.

You can see how it works here.

Watch on YouTube SAP CPI Iflow configuration approval

Try it out

It is pretty easy to get started with the Figaf DevOps Suite: start a free trial. You can transport your first SAP CPI Transport in just 30 minutes. Then you can create the first configuration change.

This post covers these products

Capabilities covered

  • Change and transportMoving a change between systems is manual, undocumented, and often done by someone outside the integration team.

More from the blog

All posts →

See this working in your landscape

No credit card required.

Integration cost calculator →

Start your free trial

No credit card required

Try Figaf DevOps Suite free for 30 days. It takes less than an hour to get started, and we send everything you need by email.

Join our newsletter

Get the latest about Figaf, SAP and anything relevant to SAP integration, every week in Figaf Weekly.