This section provides information to help you work with Clarity LIMS automation tokens in Clarity LIMS v5 and later.
When configuring automations in BaseSpace Clarity LIMS, copy tokens from the Tokens list and paste them into the Command Line field. These tokens are available for use in step automations. If using multiple variables, add a space between each entry. All tokens and parameters are case-sensitive.
| Token | Purpose | Example |
|---|
When configuring automations in the BaseSpace Clarity LIMS, copy tokens from the Tokens list and paste them into the Command-Line field.
These tokens are available for use in derived sample automations. If using multiple variables, add a space between each entry. All tokens and parameters are case-sensitive.
| Token | Purpose | Example |
|---|
{username} | Supplies the username of the current user running the step to the triggered automation script |
resolves to:
|
{password} | Supplies the password of the current user running the step to the triggered automation script. |
resolves to:
In log files, the password supplied on the command line is replaced with a series of *** characters. |
{baseURI} | Supplies the base API URI to the triggered automation script. |
resolves to:
|
{stepURI} | Supplies the URI of the step to the triggered automation script. Include the version parameter (ie, {stepURI:version}) to specify the version of the REST API to be accessed. |
resolves to:
|
{artifactsURI} | Supplies the URI of the artifacts root to the triggered automation script. Include the version parameter (ie, {artifactsURI:version}) to specify the version of the REST API to be accessed. |
resolves to:
|
{processURI} {stepURI} token is preferred. {processURI} is deprecated and less accurate. May be removed in future versions. | Supplies the URI of the step to the triggered automation script. If using the deprecated {processURI} token, the addition of the version and scheme parameters is recommended ({processURI:version:scheme}). Adding the version and scheme reduces the chance of a server and REST version upgrade unknowingly affecting your scripts. |
resolves to:
|
{processLuid} | Supplies the LIMS ID of the step that triggered the automation script. |
resolves to:
|
{udf:nameOfUDF} | Supplies the current value stored within a UDF configured as nameofUDF. |
resolves to:
|
{parentProcessUdf:nameOfUDF} | Supplies the current value stored within a UDF configured as nameofUDF of the immediate parent step to the step that triggered the automation script. The parent step must provide the inputs (derived samples) to the step. In cases where there are multiple parents (ie, the inputs are derived from various steps) only the first of these parents is returned. |
resolves to:
|
{parentProcessUdfN:nameOfUDF} | Supplies the current value stored within a UDF configured as nameofUDF of the immediate parent step to the step that triggered the automation script. The parent step must provide the inputs (derived samples) to the step. In cases where there are multiple parents (ie, the inputs are derived from various steps) all parent step IDs are treated as an array-based list. N specifies the array list index position 0..n of the desired step. {parentProcessUdf0:nameofUDF} is equivalent to {parentProcessUdf:nameofUDF}. |
resolves to:
|
{outputFileLuids} | Supplies the LIMS IDs of all step output file placeholders. |
resolves to:
|
{outputFileLuidN} | Supplies the LIMS ID for the specified step output file placeholder. All output file placeholders applying to inputs of the step are treated as an array-based list, where N specifies the array list index position [0..n] of the desired file. | Assuming the same eight output files as in the previous example:
resolves to:
resolves to:
resolves to:
|
{compoundOutputFileLuids} | Supplies the LIMS IDs for all shared step output file placeholders. |
resolves to:
|
{compoundOutputFileLuidN} | Supplies the LIMS ID for the specified step output file placeholder that applies to an individual input. All output file placeholders applying to individual inputs for the step are treated as an array-based list, where *N specifies the array list index position [0..n] of the desired file. | Assuming the same four output files as in the previous example:
resolves to:
resolves to:
resolves to:
resolves to:
|
Deprecated {parentProcessLuid*} tokens | The following tokens have been deprecated: • {parentProcessLuid} • {parentProcessLuids} • {parentProcessLuidN} These tokens were only applicable to steps that take file inputs. File inputs are no longer supported in the Clarity LIMS. |
{username} | Supplies the username of the current user running the step to the triggered automation script. |
resolves to:
|
{password} | Supplies the password of the current user running the step to the triggered automation script. |
resolves to:
In log files, the password supplied on the command line is replaced with a series of *** characters. |
{baseURI} | Supplies the base API URI to the triggered automation script. |
resolves to:
|
{derivedSampleLuids} | Supplies the derived sample LIMS IDs to the triggered automation script. |
resolves to:
|
{userinput:customParameterName} | Allows for data input to supply the triggered automation script. Custom parameters are identified with the prefix 'userinput:' | The following command line requires the user to input a value for 'more_yield':
|
When configuring automations in BaseSpace Clarity LIMS, copy tokens from the Tokens list and paste them into the Command Line field.
These tokens are available for use in project automations. If using multiple variables, add a space between each entry. All tokens and parameters are case-sensitive.
| Token | Purpose | Example |
|---|---|---|
{username}
Supplies the username of the current user running the step to the triggered automation script
cmd /c "C:\ai\ai.bat {username}"
resolves to:
cmd /c C:\ai\ai.bat adminuser
{password}
Supplies the password of the current user running the step to the triggered automation script.
cmd /c "C:\ai\ai.bat {password}"
resolves to:
cmd /c C:\ai\ai.bat 3BlindMice
In log files, the password supplied on the command line is replaced with a series of *** characters
{baseURI}
Supplies the base API URI to the triggered automation script.
cmd /c "C:\ai\ai.bat {baseURI}"
resolves to:
cmd /c C:\ai\ai.bat https://lims.lan.29/api/
cmd /c "C:\ai\ai.bat {baseURI}v2"
resolves to:
cmd /c C:\ai\ai.bat https://lims.lan.29/api/v2
NOTE: To access the endpoints, make sure that the {baseURI} is appended with v2. You can include this in the token in the command line, as shown above, or in the script itself.
{projectLuid}
Supplies the URI of the step to the triggered automation script. Include the version parameter (ie, {stepURI:version}) to specify the version of the REST API to be accessed.
cmd /c "C:\ai\ai.bat {C:\ai\ai.bat {projectLuid}"
resolves to:
cmd /c C:\ai\ai.bat ADM123