← Blog

New Groovy editor integrated in Figaf

The Figaf Groovy editor lets you open a script from an iFlow, add input or test data, run it on your Cloud Integration tenant and compare results.

June 21, 2023 · 2 min read

How do we make SAP Integration Developers more effective at creating new integrations to resolve some challenges?

Most Cloud Integration developers have used GroovyIDE to run the Groovy script. It is much easier to edit and run code than inside Cloud Integration. But it still has some challenges.

  • Giving access to your code and test data
  • Manually copying and pasting the code between systems
Figaf Groovy editor for a Cloud Integration script with input XML and headers on the left, the script in the middle and output on the right
The Groovy editor in Figaf

We do have our Pro code option, where we are providing a git repository with Gradle templates and mocking services that allows you to run your groovy code and debug it. I do think this is for the most hardcore developers. It can be a little intimidating and challenging to get it to work in organizations where things are locked down.

You can see a short video of the new editor.

Enable the editor

The editor is available to users with the IRTAdmin role, who can run and upload scripts.

You will need to enable usage on the development agent to run and upload content.

Development agent setting in Figaf with the checkbox Enable IDE to run and upload scripts selected

If you just have smaller scripts to edit and have test data for it we can make the process smarter. In the new release of Figaf we have added an editor that will allow you to

  • Select a script from an iflow and open the editor with it
  • Allow you to fill in input data
  • Run the code
  • Select test data you already created
  • Compare with the test result

How to run the code securely

We want to be able to run the code in a secure manner and not allow you access to the Figaf system. The best way was to use your Cloud Integration tenant to run the code in. This has some advantages.

  • Developers would anyway be able to run the code here themselves.
  • It will run in the same runtime as Cloud Integration.
  • It is isolated in the same way as normal Iflows so if you perform heavy CPU or Memory intensive processing, it could bring down your system.
  • Same code as you would see when running the script in a real iflow.

Ideas for improvement

When we released the editor, these were some of the ways we saw it could be improved.

  • Adding support for XSLT
  • Enabling the ability to run multiple tests at once
  • Running of Message Mapping UDFs
  • Ability to run with the jar of a iflow
  • Improve the security if there are any challenges with this approach
  • Adding role for user
  • Security for not editing virtual objects

When you have tried it let us know how we can improve it and what will speed up your process.

This post covers these products

Capabilities covered

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.