So, how can the Figaf DevOps Suite help you to optimize your workflow while working on the CPI? You can do a lot of error handling in your flows. It does sometimes mean you will have to spend more time setting up correct error handling in each flow. We want to make it faster for you to develop and deliver your integrations.
In the standard CPI monitoring it is pretty fast to find errors, but if you want to find the iflows you have where there are extra attachments on it becomes more complex. You will have to use the OData interface yourself.
The Figaf DevOps Suite has many cool functions that will make your work a lot easier. It allows you to support and monitor all your different systems in one place. If you, for example, have many different kinds of errors in your system, it can be a big challenge to handle all of them, but with Figaf you can set up rules, based on criteria of your choice.
A rule is defined with XPath, making it easy to figure out how to set it up with the information. Then you can send data to Jira, Slack or email, so the right people are informed about the error. You also have labels to identify what the error is related to and how critical it is.
In this video I explain much more about how to monitor SAP CPI using the Figaf DevOps Suite:
Watch on YouTube SAP CPI monitoring with Figaf IRT
Do you want to try it? It is really easy to get started: start a free trial.
