In this blog, I will cover how the Figaf DevOps Suite improves the way you work with transporting.
Before we get started, we need to find a clear definition of what “DevOps” is. According to Wikipedia it goes like this:
“DevOps is a set of software development practices that aim to shorten the systems development life cycle while delivering features, fixes and updates frequently in close alignment with business objectives”
Understand what is changed
Track what object is being changed, Is it a part of the BPMN model, Is it scripts or mappings, Is it configuration which is changed
Register changes with business reason
Make a service request in the Figaf DevOps Suite that allows you to link the changes to the reason.
Users can assign changes in iFlows to it.
Test the changes
With the built-in testing tool you can test that the modifications you make do not affect anything unexpected.
You can document what test you have run and the result of them.
iFlow configuration in the landscape
Configure an iFlow once and then let Figaf handle configuration in the landscape when importing the change.
Transport individual changes
Be able to import changes into target system. Figaf will import the object into the target system. Then the configuration will be applied.
Check out the demo
So, if you want to check out how this works, please take a look at the demo video below:
Watch on YouTube Transporting SAP CPI content with Figaf IRT
Are you ready to see what the Figaf DevOps Suite can do for you? Start a free trial.
