Release 2108: improved CPI testing

We just released a new release of Figaf. The main part of this is to simplify the testing of SAP CPI and PI and then enable you to test with IDocs also.

Better error notification on testing

We have over the last few months got a lot more customers to try the SAP CPI testing part of the tool. It had been a bit of a challenge to figure out what was going on and we often needed to assist and look at the logs.

We wanted to simplify the process so it became much easier for users to find what was going on and where the potential problem was.

The most common errors we have seen:

Testing user or Key does not have credentials to send messages
Iflow is not deployed
The Iflow returns an error message because something unexpected happened in the process. Then you may want to see if the iflow was processed and if it matches with the test case
New copied Iflow needs to be deployed and started before the test can be run
If the iflow you are testing with is using ProcessDirect then you need to deploy an HTTP to ProcessDirect bridge

The UI has been improved in the following ways.

Figaf test run details page with test run info and an arrow pointing to the Message runs tab

In the Message runs tab you can see which runs caused problems.

Message runs tab showing a run with status SENT_WITH_ERROR, an error preview and an Error details icon

Then you can click Error details to see what is going on.

Error details dialog with the SENT_WITH_ERROR message and a stack trace showing the iFlow could not be found

We keep improving the error and resolution help as we see more types of errors.

This should make it much easier for you to test your integration and figure out what is wrong without needing access to the system logs.

New IDoc sender

We have added native testing of IDocs, so we don’t need to create a new iflow to handle the test of it. So now we support the following sending channels

HTTP
SOAP
ProcessDirect via a proxy iflow
IDoc

If the iFlow starts with something else, Figaf DevOps Suite will create a copy of the iFlow and replace the sender or schedule step with HTTP so we can always test it.

What came next

The following releases focused on two areas:

SAP PI to CPI migration, which is now handled by the Figaf Migration Tool
SAP PI/PO transports, which now make it possible to transport and configure ICOs and channels with much more precision

Better error notification on testing

New IDoc sender

What came next

See this working in your landscape