The MSPro Boomi Collection
About
ScriptEase For Boomi
ScriptEase For Boomi
  • ScriptEase
    • ScriptEase Development Environment
    • What AI says!
      • The limits of AI ...
  • Software Installation
    • Install a local Atom
  • Project Setup
    • IntelliJ Configuration
    • Verify Project Setup
  • Concepts
    • Use Test Data
  • Examples
    • 1 - Debug an existing process script
    • 9 - Aggregate Prices Example
  • Test Contexts
    • The Process Call Chain
  • Download
  • 💤Appendix
    • Script Templates
    • Java thoughts and recommendations
      • Chose newer JVM for local development
    • Boomi documentation and links
    • Initialize IntelliJ Templates
    • Script Contexts
  • Troubleshoot
    • Java the weed
    • ClassNotFoundException - GroovyStarter
    • Invalid VCS root mapping
    • An illegal reflective access operation has occurred
    • UnauthorizedAccess Error
  • Licensing
    • License Activation
    • Privacy Policy
Powered by GitBook
On this page
  1. ScriptEase

ScriptEase Development Environment

Last updated 1 month ago

ScriptEase is a development environment that allows you to develop and manage Groovy scripts for Boomi Integration.

ScriptEase allows you to develop / edit your Boomi Integration Scripts with JetBrains IntelliJ (Groovy IDE). Boomi Process- or Map Scripts are wrapped into repeatable unit tests to support local debugging and to ensure functionality and compatibility. The ScriptEaseLib provides the local run-time environment (ATOM script emulation) to make all this possible. Finally, when you are happy with your code, simply copy and paste your script into Boomi Integration!

ScriptEase for Boomi brings the following advantages without any disadvantage:

  • Develop Scripts in a full-featured IDE (IntelliJ)

    • with syntax highlighting

    • code completion (intelli-sense)

    • immediate (syntax) error checking etc.

  • Debug your scripts

    • breakpoints, single-step, debug variables, log messages

  • Full support for

    • All types of documents (JSON, XML, Flat-File)

    • Dynamic Document Properties

    • Process and Dynamic Process Properties

    • Logging

  • Write Unit Test

    • to ensure your scripts still provide the same expected results

    • in all scenarios

The only "cost" is to get used to it, which can take a little time. And it requires your personal commitment that you want to work with Groovy Script. If you don't like scripting, yet, you may want to give it a try. Maybe you will love scripting afterwards.

I recommend , or if you are looking for a Christmas or birthday present: .

Groovy-Learn
Groovy in Action, Second Edition
IntelliJ - Editing with syntax highlighting & code-completion, debugging and unit testing
Several unit tests ensure the function of the script at all times