Recently, I had a conversation with an SAP Integration Architect about how they manage Groovy development for integrations. Surprisingly, they had no clear idea about how developers worked on the Groovy. Groovy is crucial for SAP Cloud Integrations because it helps create efficient flows and customized logic and is something that requires some extra help.
So I ran an LinkedIn Survey recently.
You can use the build in Editor if you just need to make smaller changes to a script. The reason is that if you want to run it takes 1-2 minutes to get a response. In that period you get a way from the focus. So it is not something you want for larger solutions.
GroovyIDE or Contiva is substantial better as they allow you to work smarter with the data and get instance feedback on the result. I see 3 challenges with this.
- You are sending code and potential confidential data to 3th party. Contiva states they do not log the payloads and it would be strange if they decided to do it.
- They have no access to Cloud Integration related APIs for value mappings, or other resources.
- You need to copy and paste code between editor and Cloud Integration
Real Editors like IntelliJ/VS Code or other IDE had a much larger share than I had expected. It does require some effort to set it up and run effectively. Once you get them running you have a much better ability to run your script and of cause combine them with your AI editor could also be an option.
- In Figaf we provide all the framework you need to be able to run all of your Groovy code based on test cases. But you can also use some of the other stubs for it.
Figaf the editor is built-in allowing you to have a better flow. You can reuse your test case that you have used. So you don’t have to look for test message to find them. The script is run on your integration suite tenant, so you have access to all CPI APIs. And nothing leaves
- Support also XSLT running on Integration Suite allowing you to use all the XSLT 3.0 functions supported there.
- We have integration with OpenAI that allows you get help with improving your code. Notice you need to provide a AI key and data is send directly to your OpenAI provider and using the models at your own expense and company polices.
- It is limited to only a web editor and output to only a Message object, so you cannot write to the trace.
Best Practices
Working with team and external consultants? Ensure you understand their workflows and how they handle sensitive data. If they’re using tools or sources you don’t trust, assess this before involving them in integration projects.
Conclusion
Explore what the Figaf DevOps Suite can do to accelerate your Groovy and XSLT code development. Understanding developers’ workflows and leveraging the right tools can protect your data and streamline your integration processes.
See how Figaf can help you with your transport management process in the demo below: