Page History
Browse scripts are associated with extensible connections and are used to discover source systems. There are a number of environment variables and token replacements available to developers when writing browse scripts. All browse scripts must return information about the source model in a specific JSON format.
Environment variables scripts
The following script environment variables are available to all browse scripts.
Variable | Description |
|---|---|
WSL_SRCCFG_<configured_field_name> | The values of configured connection properties can be accessed using environment variables. |
WSL_BINDIR | The WhereScape 3D installation path. (The default location is 'C:\Program Files\WhereScape\WhereScape 3D'.) |
WSL_WORKDIR | The working directory where the script is executed. (The working directory will be in %UserProfile%\WhereScape\3D\scriptExecution.) |
WSL_TASK_NAME | A name used to identify the browse script discovery task. |
WSL_SEQUENCE | A sequence id to identify each browse script discovery process. |
WSL_SCRIPT_<Script_Name>_CODE | The full path to the script specified. The script should be stored in the WhereScape 3D metadata and will be automatically copied to the working directory before the workflow script is executed. |
Token replacement in scripts
...