Download
Download and Release History
Last updated
Download and Release History
Last updated
The ScriptEase Project contains sample scripts and templates to get started with ScriptEase.
is all you need when you start with ScriptEase. It includes the latest version of the ScriptEase library.
Git Repository
The Demo project is currently . 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 scriptEaseLib-x.y.z.jar provides the magic to edit, debug and test Boomi Process- and Map-Scripts on your local machine using JetBrains IntelliJ.
If you have an existing ScriptEase project on your local machine, to update the library.
1.3.0 - 2025-03-22
Licensing implemented (see Licensing )
1.1.4 - 2025-02-06
Fixed: outputDocuments are empty when more than one script is executed on the same test.
Logging DefaultFormatter no longer uses Thread, to support JDK 23 and JDK11.
testFileHelper supports getText()
Fixed compatibility issues when using logging with Java 11.
Fixed typos on property names
Changed some property names on ExcutionContext.
Please update to v1.1.1
All scriptEaseLib classes use: @CompileStatic and @TypeChecked
ProcessExecutionProperties fixed
Better typed, library internal classes restricted to @PackageScope
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
FIX getStream( docNo=0) called more than once. error when passing empty documents to the script.
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
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.
MapScriptContextProcessContext 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 ...
That was the date when it all started!