LabKey Server supports a number of substitutions that can be used with transformation scripts. These substitutions work both on the command-line being used to invoke the script (configured in the Views and Scripting section of the Admin Console), and in the text of transformation scripts themselves. See Transform Scripts for a description of how to use this syntax.

Script Syntax	Description	Substitution Value
${runInfo}	File containing metadata about the run	Full path to the file on the local file system
${srcDirectory}	Directory in which the script file is located	Full path to parent directory of the script
${apikey}	A session-scoped API key	The string value of the Session API key, used for authentication when calling back to the server for additional information
${rLabkeySessionId}	Information about the current user's HTTP session	labkey.sessionCookieName = "COOKIE_NAME" labkey.sessionCookieContents = "USER_SESSION_ID" Note that this is multi-line. The cookie name is typically JSESSIONID, but is not in all cases.
${sessionCookieName}	The name of the session cookie	The string value of the cookie name, which can be used for authentication when calling back to the server for additional information.
${baseServerURL}	The server's base URL and context path	The string of the base URL and context path. (ex. "http://localhost:8080/labkey")
${containerPath}	The current container path	The string of the current container path. (ex. "/ProjectA/SubfolderB")
${httpSessionId}	(Deprecated) The current user's HTTP session ID	(Use ${apikey} instead.) The string value of the session API key, which can be used for authentication when calling back to the server for additional information

Related Topics

• Transform Scripts
• Compliant Access via Session Key