Develop and Sync Scripts

Developing and testing Groovy Scripts is a pain ... if you don't have ScriptEase.

Here is the description how to connect and synchronize your local Scripts with your Boomi Integration repository.

chevron-rightPre-Conditionshashtag
  • Boomi Console is connected to your Boomi Account.

  • You can run bc code pull.

  • You have set-up ScriptEase.

chevron-rightPreparation - One-time setuphashtag

Create a new Script Component

You cannot create new scripts from the command-line but you can pull existing scripts to your local workspace. For that reason, you start creating a new plain script in Boomi Integration.

Plain / blank Script

Once done, run a bc CODE PULL to update your local Workspace - to pull the created script. You will find it then on your local hard-disk.

The next step is to create a symbolic link: MKLINK Link Target

  • Link: from the CODE-File that is synchronized with Boomi Integration (source - Boomi Console Workspace)

  • Target: to the file in your development space (target - ScriptEase Workspace).

circle-info

Using symbolic links (with Windows) allows you to have one physical (target) file (the one in your ScriptEase development Workspace) and any number of (symbolic) links to that file. The file-explorer will clearly state: it is a symbolic link. You can safely remove the link without deleting the physical file.

But before you can create the link,

  • copy the name of the downloaded CODE-File, and

  • delete the CODE-File you just downloaded because it will be replaced by the link.

MKLINK 
  ...\BC\Code\...\NumberValidation\psg.GRQueryBuilder.a7448fef-...groovy
  ...\Scripts\src\processScript\dataHub\psgGRQuery.groovy
  
symbolic link created for 
  ...\BC\Code\...\NumberValidation\psg.GRQueryBuilder.a7448fef-...groovy
  <<===>> 
  ...\Scripts\src\processScript\dataHub\psgGRQuery.groovy
  

Push your local file back to Boomi Integration

Push your new code back to Boomi: bc CODE PUSH /force

circle-info

Use the /force option to force pushing the local file to Boomi, even if the component in Boomi was created later than the local file itself. Once, forced to push, everything goes normal and you can omit the force option.

Last updated