Specifications

For the first two editors, validation is always performed at design time. For the last two editors,
validation is performed at run time (except if the single-line text does not contain any variables).
In all cases, the property value is guaranteed to contain one of the following:
• A valid file path that points to an existing file.
• One of the library items returned for the property by the getLibraryForProperty entry point.
For most use cases it can be assumed that these values are mutually exclusive, and that the
script code can tell the data types apart from looking at the value. If needed however, the script
code can check which editor has been used to enter the value.
External property editor
Introduction
Switch supports a property editor called “External editor” that offers integrated editing capabilities
for third-party property sets (such as a preflight profile) without including third-party code in
Switch. The property set must be stored in a file, and an external editing application must be
supplied that behaves according to some specific guidelines.
Designing a flow with an external property editor
When a user invokes an external property editor while designing a flow, Switch launches the
associated external application and passes it the file path to a copy of the property set to be
edited. The external application brings up a dialog for editing the contents of the property set
and saves any changes back into the file. When the application exits, Switch recognizes the
updated property set.
The value of a property edited with the “External editor” property editor is a file path. The actual
file is stored in a temporary place allocated by Switch (similar to property sets created while
importing a flow).
The “External editor” property editor works well in conjunction with the “Choose file” property
editor, since both operate on a file path. Furthermore, Switch always makes a copy of the property
set before editing. This means that:
• A property set that was selected with the “Choose file” property editor is never changed.
• Edited property sets are never shared between multiple flow elements.
Specifying an external property editor in SwitchScripter
The “External editor” property editor supports the following extra properties (shown in
SwitchScripter and stored in the script declaration):
DescriptionProperty
The path to the application (executable) used to edit a property setApplication
If a relative path is specified (that is, the path does not start with a
drive letter or a forward slash), Switch looks for the external application
relative to the folder portion of the path returned by the
Environment.getApplicationPath( ) function
The argument string passed to the application when there is no
pre-existing property set, after substituting all occurrences of %1 and
%2 as described below
Arguments for new
365
Enfocus Switch 10