At times you might want to know how an action was started (launched).
The Test Run Context statement can be used to determine if an action is running in the Batch Processor.
Various named variables return information about how an action was started:
| Named Variable | Description |
|---|---|
| Droplet Files | If the action was started from a droplet created with the Run Action With a List of Dropped Files mode, the named variable will a list of the dropped items delimited by the Default List Delimiter (\~). |
| Droplet Name | If the action was started from a droplet, the named variable will contain the name of the droplet. |
| File Auto Selected | When the named variable is set to 1, the action was started without any selected files, but files were loaded. A single file was automatically selected. Note that this can only happen if the action has Always enabled in the Action Manager. |
| Pre Droplet Open Mode | If the action was started from a droplet created with the Load Dropped Files and Run Action mode, the named variable will contain a symbolic representation of the Open Mode prior to being modified by the droplet's forced Open Mode. The following characters are used:
|
| Run from Function Button | The action was started from a field function button's Multi Field Editor Actions context menu. The named variable contains the name of the field. When not empty, named variable Run from Multi Field Editor will be set to 1. |
| Run from Multi Field Editor | When the named variable is set to 1, the action was run from the Multi Field Editor or from a field function button's Multi Field Editor Actions context menu. If named variable Run from Function Button is empty, the action was started from the Multi Field Editor, otherwise it was started from the specified function button. |
| Temporary File Supplied | When the named variable is set to 1, the action was started without any loaded files. A temporary file was supplied. Note that this can only happen if the action has Always enabled in the Action Manager. |