Shared - common replacement variables

Common Client Variables

Variable	Replacement	Since
entry	Entry being processed from the list parameter of the runFromList action
entry2	Entry being processed from the list2 parameter of the runFromList action
renderRequest	Last result from the renderRequest action modified by findReplace processing
server	Server URL available for clients accessing a remote server	9.0
hosting	Available with getServerInfo for clients accessing a remote server with server, cloud, datacenter as values	9.3
version	Available with getServerInfo for clients accessing a remote server	9.3
runDate	For run action scripts, it is the client date at the time of the *first* action referencing the value The replacement date will be exactly the same for all subsequent references for consistency across actions Formatted according to current dateFormat parameter or default as usual for date fields	9.0
file	File path name for last get or get list action that used the file parameter	9.3
fileSize	File size for the last get or get list action that used the file parameter	9.3
fileContent	File text content for the last get or get list action that used the file parameter limited to a file with size < 10MB	9.3

The syntax is @<variable>@. See How to use replacement variables for more details.
Variable names are case-sensitive!
Action help and document lists variables set by specific actions.
Variable replacements are different than substitution variables. Don't confuse them or their unique syntax.
Last created means the variable is set from the last create or add action.
Referenced means the variable is set from one of the runFrom or get actions.
Within a run script, the getReplacementVariableList action will list currently defined variables except for pre-defined variables (server, runDate).
Within a run script, the setReplacementVariableList action can be used to set custom variables.
Some actions support a reference parameter that provides an opportunity to set a custom variable based on specific information from running the action.
Variables are available within the scope of run action that contains the action that sets the variable or a parent run action. Sibling (runFromList scripts) variable sets are independent of each other.