This statement can be used to determine if the current action run context supports the following execution contexts:
- Batch
- Batch+Grouped
- Batch+Stepwise
- Grouped
- Interactive
- Interactive+Grouped
- Interactive+Stepwise
- Stepwise
If the current action run context supports the specified context, the action test state is set to true, otherwise it is set to false.
Example 1: Interactive+Grouped will return true if the current action run context is both Interactive and Grouped.
Example 2: Grouped will return true if the current action run context is Grouped (Batch or Interactive).
You can elect to cancel action processing if the specified context is not supported. When this is the case, you can optionally specify a note to appear on the posted error message. The note can contain any of the escape sequences described in Escape Sequences.
The statement can also be used to test where the execution is taking place or how it was started. The following tests are available:
- Started Action
Test if the initially started action is executing. This will return false if an inline action is executing.
- Not Started Action
Test if the initially started action is not executing.
- Started Action File
Test if execution is taking place anywhere in the started action file. ie. inline actions will not return false.
- Not Started Action File
Test if execution is currently in a file outside the initially started action file.
- Multi Field Editor
Test if the action was started from the Multi Field Editor (directly or via a Function button).
- Not Multi Field Editor
Test if the action was not started from the Multi Field Editor (directly or via a Function button).
- Multi Field Editor (direct)
Test if the action was started directly from the Multi Field Editor (ie. not via a Function button).
- Not Multi Field Editor
Test if the action was not started directly from the Multi Field Editor (ie. not via a Function button).
- Droplet
Test if the action was started via a droplet.
- Not Droplet
Test if the action was not started via a droplet.
- Droplet with Files
Test if the action was started via a droplet which passes a list of dropped files directly to the action.
- Not Droplet with Files
Test if the action was not started via a droplet which passes a list of dropped files directly to the action.
- Droplet without Files
Test if the action was started via a droplet but was not passed a list of dropped files directly to the action.
- Not Droplet without Files
Test if the action was not started via a droplet which which does not pass a list of dropped files directly to the action.
- Always Fail
This test always fails and cancels action processing.
