$(execution)
Description
This built-in function expose the execution-level metadata, both the runtime and design-time information.
Available Functions
$(execution|step|index)
Display the row number of the step currently in execution
Example
We can use this function to expose execution metadata as part of Event Notification. This can provide helpful information towards troubleshooting.. In this example, we use this function in combination with email
notification to expose the step that had failed during execution.
In datasheet
_01.png)
The notification email would appear as like
_02.png)
$(execution|step|name)
Display the step currently in execution, in the format of
[ script name ][ scenario name ][ activity name ][ row number ]
Example
We can use this function to expose execution metadata as part of Event Notification. This can provide helpful information towards troubleshooting. In this example, we use this function in combination with email
notification to expose the step that had failed during execution.
Input datasheet
_03.png)
The notification email would appear as like
_04.png)
$(execution|step|script)
Display the script name (without file extension) currently in execution
Example
We can use this function to expose execution metadata as part of Event Notification. This can provide helpful information towards troubleshooting. In this example, we use this function in combination with email
notification to expose the step that had failed during execution.
In datasheet
_05.png)
The notification email would appear as like
_06.png)
$(execution|step|scenario)
Display the scenario currently in execution
Example
We can use this function to expose execution metadata as part of Event Notification. This can provide helpful information towards troubleshooting. In this example, we use this function in combination with email
notification to expose the step that had failed during execution.
In data sheet
_07.png)
The notification email would appear as like
_08.png)
$(execution|step|activity)
Display the activity currently in execution
Example
We can use this function to expose execution metadata as part of Event Notification. This can provide helpful information towards troubleshooting. In this example, we use this function in combination with email
notification to expose the step that had failed during execution.
In datasheet
_09.png)
The notification email would appear as like
_10.png)
$(execution|step|iteration)
Display the iteration index currently in execution
Example
We can use this function to expose execution metadata as part of Event Notification. This can provide helpful information towards troubleshooting. In this example, we use this function in combination with email
notification to expose the step that had failed during execution.
In datasheet
_11.png)
The notification email would appear as like
_12.png)
$(execution|step|command)
Display the command currently being executed
Example
We can use this function to expose execution metadata as part of Event Notification. This can provide helpful information towards troubleshooting. In this example, we use this function in combination with email
notification to expose the step that had failed during execution.
In datasheet
_13.png)
The notification email would appear as like
_14.png)
$(execution|step|description)
Display the description of the step currently in execution
Example
We can use this function to expose execution metadata as part of Event Notification. This can provide helpful information towards troubleshooting. In this example, we use this function in combination with email
notification to expose the step that had failed during execution.
In datasheet
_15.png)
The notification email would appear as like
_16.png)
$(execution|activity|name)
Display the activity currently in execution
Example
Here we are using io » writeFile(file,content,append) in
conjunction with this function to write custom log files containing the details of the activity under execution.
Input function
_17.png)
Output
_18.png)
$(execution|activity|script)
Display the script name currently in execution
Example
Here we are using io » writeFile(file,content,append) in
conjunction with this function to write custom log files containing the details of the activity under execution.
Input function
_19.png)
Output
_20.png)
$(execution|activity|iteration)
Display the iteration index currently in execution
Example
Here we are using io » writeFile(file,content,append) in
conjunction with this function to write custom log files containing the details of the activity under execution.
Input function
_21.png)
Output
_22.png)
$(execution|activity|scenario)
Display the scenario currently in execution
Example
Here we are using io » writeFile(file,content,append) in
conjunction with this function to write custom log files containing the details of the activity under execution.
In script file
_23.png)
Log File
_24.png)
$(execution|scenario|name)
Display the scenario currently in execution
Example
We can use this function to expose execution metadata as part of Event Notification. This can provide helpful information towards troubleshooting. In this example, we use an event notification in the form of an email to
expose the details of the scenario which has just started execution.
Input function
_25.png)
Output
_26.png)
$(execution|scenario|script)
Display the script name currently in execution
Example
We can use this function to expose execution metadata as part of Event Notification. This can provide helpful information towards troubleshooting. In this example, we use an event notification in the form of an email to
expose the details of the scenario which has just started execution.
Input function
_27.png)
Output
_28.png)
$(execution|scenario|iteration)
Display the iteration index currently in execution
Example
We can use this function to expose execution metadata as part of Event Notification. This can provide helpful information towards troubleshooting. In this example, we use an event notification in the form of an email to
expose the details of the scenario which has just started execution.
In datasheet
_29.png)
The notification email will appear as like.
_30.png)
$(execution|iteration|index)
Display the iteration index currently in execution
Example
We can use this function to expose execution metadata as part of Event Notification. This can provide helpful information towards troubleshooting. In this example, we use these functions in combination with console
event notification to find out which iteration has started execution.
In datasheet
_31.png)
The console will appear like so
_32.png)
_33.png)
_34.png)
$(execution|iteration|script)
Display the script name currently in execution
Example
We can use this function to expose execution metadata as part of Event Notification. This can provide helpful information towards troubleshooting. In this example, we use these functions in combination with console
event notification to find out which iteration has started execution.
In datasheet
_35.png)
The console will appear like so
_36.png)
$(execution|script|name)
Display the script name (without file extension) currently in execution
Example
We can use this function to expose execution metadata as part of Event Notification. This can provide helpful information towards troubleshooting. In this example, we use an event notification in the form of an email to
expose details of a script that has just completed its execution.
In datasheet
_37.png)
The notification email will appear as like
_38.png)
$(execution|script|fullpath)
Display the fullpath of the script currently in execution.
Note: The script used during execution is the output file created at the start of execution. Not to be confused
with artifact/script/script-file.xlsx.
Example
We can use this function to expose execution metadata as part of Event Notification. This can provide helpful information towards troubleshooting. In this example, we use an event notification in the form of an email to
expose details of a script that has just completed its execution.
In datasheet
_39.png)
The notification email will appear as like
_40.png)
$(execution|plan|fullpath)
Display the fullpath of the plan file currently in execution.
Example
We can use this function to expose execution metadata as part of Event Notification. This can provide helpful information towards troubleshooting.. In this example, we use this function in combination with email
notification to expose the step that had failed during execution.
$(execution|plan|name)
Display the plan name (without file extension) currently in execution
Example
We can use this function to expose execution metadata as part of Event Notification. This can provide helpful information towards troubleshooting.. In this example, we use this function in combination with email
notification to expose the step that had failed during execution.
$(execution|plan|index)
Display the row index of script in plan file currently in execution
Example
We can use this function to expose execution metadata as part of Event Notification. This can provide helpful information towards troubleshooting.. In this example, we use this function in combination with email
notification to expose the step that had failed during execution.
$(execution|meta|nexial)
Display the current Nexial version.
Example
We can use this function to expose execution metadata as part of Event Notification. This can provide helpful information towards troubleshooting. Here, we are using this function in combination with sms event notification
to expose metadata about the the nexial version used for the execution.
Input function
_41.png)
Output
_42.png)
$(execution|meta|java)
Display the current Java version.
Example
We can use this function to expose execution metadata as part of Event Notification. This can provide helpful information towards troubleshooting. Here, we are using this function in combination with sms Event Notification
to expose metadata about the the java version used for the execution.
Input function
_43.png)
Output
_44.png)
$(execution|meta|user)
Display the username of the current Nexial execution.
Example
We can use this function to expose execution metadata as part of Event Notification. This can provide helpful information towards troubleshooting. Here, we are using this function in combination with sms Event Notification
to expose metadata about the username which carried out the execution.
Input function
_45.png)
Output
_46.png)