Modifying the SCL search path

By design SCL scripts, referenced by the main FB are loaded from the SCL vault.

This is a folder underneath the Process Simulate installation folder (Scripting\SCL\Vault). For us the vault allows distributing out of the box scripts.

Users are also expected to update the vault with their own scripts before using them in the SCL editor. This is done via the 'Import SCL block' command or by simply copying the scripts there.

Q: What is the problem with this approach?

A: Depending on your Windows user's role you might not have permissions to modify the installation folder. It often requires administrative privileges.

B: When changing Process Simulate versions you need to import the same scripts in each and every version. This can become annoying when changing versions frequently.

To address these two limitations we have introduced the SCL_PATH environment variable. It simply points to the folder where you keep your scripts. When loading SCL scripts Process Simulate checks the vault first and if the script is not found there it checks the SCL_PATH. Version 2606 EAP will have this improvement. If you keep a collection of scripts this will definitely be of help.

Example:

set SCL_PATH=c:\SCL Scripts

The path variable points to a single folder for now. You can organize your scripts in subfolders underneath this path. Process Simulate monitors the path for changes (new files and modified files) so you don't have to restart. Just play the simulation again after the change.

Each .scl file that you put there should be UTF8 encoded and should contain the definition of a single FC/FB/UDT. The name of the file should match the name of the SCL block. These are the preconditions that allow Process Simulate to find and load the scripts.

Importing SCL blocks into the vault still works but I guess the vault will be for internal use from now on.