Download and Release History

The Demo project

The ScriptEase demo project illustrates how to use ScriptEase and it contains some sample scripts to learn Groovy. It includes the latest version of the ScriptEase library.

📝 DOWNLOAD - ScriptEase Project

Git Repository

The Demo project is currently hosted on GitHub. I recommend, if you know how to use Git, to pull it from there (use it as a Git repository) instead of downloading the zip-file.

The ScriptEase library

The ScriptEase library scriptEaseLib.jar provides the magic to edit, debug and test Boom Process- and Map-Scripts on your local machine using JetBrains IntelliJ.

📀 DOWNLOAD - Latest ScriptEaseLib.jar

Library Version History

1.1.4 - 2025-06-02

• Fixed outputDocuments is cleared when more than one script is executed on the same test.

1.1.3 - 2024-12-10

• Logging DefaultFormatter no longer uses Thread, to support JDK 23 and JDK11.

• testFileHelper supports getText()

1.1.1 - 2024-12-04

• Fixed compatibility issues when using logging with Java 11.

• Fixed typos on property names

  • Changed some property names on ExcutionContext.

1.1.0 - 2024-12-03

Please update to v1.1.1

• All scriptEaseLib classes use: @CompileStatic and @TypeChecked

• ProcessExecutionProperties fixed

• Better typed, library internal classes restricted to @PackageScope

1.0.2 - 2024-11-18

• Finally renamed to ScriptEase.

  • MGF (Markus`s Groovy Framework) became ScriptEaseLib to avoid any confusion with the PSO Boomi Framework.

• NEW Licensing implemented

• FIX No more HashMap, uses Map everywhere to improve compatibility with Java

Personal Versions (pre-release)

0.6.1 - 2024-08-22

• FIX getStream( docNo=0) called more than once. error when passing empty documents to the script.

0.6.0 - 2024-08-08

• NEW Document.fromByteArray() and Document.fromStream() added

• NEW Text encoding added to Document.from functions so that it is no longer UTF-8!

• FIX After calling Document.toString() the document was empty

0.5.0 - 2024-07-04

Major changes for MapScripts were required to correctly simulate a Map context and the lifetime of map script objects. As long as the MapScript ran on a single property, everything was fine. However, to support a MapScript running on an Array (for each single array element) the new updates were required.

MapScriptContext was replaced by ProcessContext which can optionally be provided in the MapScript constructor.

OLD 0.4.x and earlier
----------
def scriptContext = new MapScriptContext([ a: 5, b: 7])
_testScript.run(scriptContext)


NEW 0.5.x 
----------
final MapScript _testScript = 
  new MapScript("msg" + SCRIPT_NAME + ".groovy", _sourceUri, new ProcessContext())

void Test() {
  def variables = _testScript.run([a: 5, b: 7])

  assert variables.total != null, "Script did not set 'total' as output parameter!"
  assert variables.total == (variables.a as int) + (variables.b as int), "Calculation result does not meet expectations!"
}

... continuous evolution ...

0.0.0 - 2020 August

• That was the date when it all started!