← Blog

Figaf DevOps Suite 2.13 released

Release 2.13 eases getting started and adds CPI package and value mapping transports, persisted message monitoring and SAP PI/PO testing improvements

May 7, 2020 · 2 min read

This week we are releasing the new version of the Figaf DevOps Suite. It contains quite a few improvements to make it easier to get started with the tool and make it easier to run your SAP Integration.

You can see a video of it here.

Watch on YouTube FIGAF IRT 2 13: Relase video. Making SAP PI/PO and SAP CPI easier

General

Easier to get started with the tool: login with the default user, guides to get started with adding license and agents. Updated tours to see the tool in action.

Improved EDIFACT comparison and ignoring of specific segments/fields. You can ignore rounding of values. So 5.2 is the same as 5.20.

Improved documentation of changes, so you can see what has been changed as a part of a ticket.

Bug fixes and improvements in the database performance.

CPI

Tracking and transports of Packages, Value mappings. So you can see what is changed between versions. They are also added to your Git repository.

Monitor to show persisted messages. So you can let business monitor the persisted messages.

For people working with the Git workflow, we have also added an option on an agent to prevent commits of iflow changes during synchronization in Figaf to avoid duplication of changes committed by user and IRT. This will only create the scaffolding for your Git repository including templates for all plugins. So you can still download/upload your CPI iflows from your IDE with the Gradle plugins. You can then follow your own workflows for working with the Git Repository. This is one of the areas where we need more input on how we can help make the flow better.

SAP PI/PO

We had a client using the Figaf DevOps Suite to test their Seeburger Migration, which was done with our SMT tool. It did lead to a number of improvements to be able to support this case. Existing data was saved in the separate archive so we have created a custom solution to build the test data. If you have migration and want our help to create the test data let us know and let’s create an estimation of the effort.

Improvement in the way testing is possible with the SAP Logging module. So it becomes much easier to use it for testing.

SAP PI/PO support for Decentral adapter engine in conjunction with Logging module.

Testing of BE/sync scenarios with mock data on PRO systems, which is really useful when testing secured interfaces. This will enable to test with confidential data.

Consolidation with SAP Logging module. This is useful if you send multiple messages and consolidate them into one message. Or have a BPM process between test cases. It is something that requires custom configuration on your scenarios.

Throttle the number of messages sent to a test case to limit the impact on the system. So the test will not overload the system.

Get started

You can start a free trial of the Figaf DevOps Suite.

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.
  • Regression testingYou cannot tell what a change broke until someone downstream complains.
  • Monitoring and alertingYou find out an integration failed when the business calls you.

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.