With Figaf our team could easily transport and configure integration. We could even reuse Dev system as Test with the same process. Allowing us to save costs.
Dürr
Dürr wanted a more reliable and governed way to move SAP Integration Suite changes from development to QA to production. Their integration team was dealing with risks tied to manual transport handling, limited native SAP transport maturity for their needs, the need to reuse their Dev tenant for testing without weakening governance, and a desire to restrict direct production access while still improving troubleshooting and developer productivity.
To address this, Dürr adopted Figaf DevOps Suite for transport management, automated configuration, a virtual tenant approach for a practical DEV/QA setup, daily Git backups, better Groovy script development, and more testing support. According to the case, this helped reduce operational risk and costs, enforce a more controlled deployment process, improve troubleshooting and the developer experience, and strengthen resilience through routine backups.
The case also notes that Dürr self-onboarded largely through Figaf’s documentation and may expand later into approvals for audit trails and broader automated testing.
Results
- Reduced operational risk by removing manual transport steps and enforcing a consistent deployment workflow
- Reduced cost for building and maintaining integration
- Structure by restricting production access and ensuring deployments go through a controlled mechanism
- Faster troubleshooting with easier context for iFlows
- Improved developer experience using a better Groovy editor
- Better resilience through routine backups of integration artifacts to Git
