Specifications

Design-time validation requires that the value…Property editor
N/A (if the value contains no variables: Is non-empty)Single-line text with
variables
N/A (if the value contains no variables: Is non-empty)Multi-line text with
variables
N/ACondition with
variables
Has at least one item and each item has valid filename pattern syntaxFile patterns
Has at least one item and each item has valid filename pattern syntaxFolder patterns
Has at least one item and each item has valid filename pattern syntaxFile types
Has at least one item and each item is non-emptyString list
Has at least one item and each item is one of the strings returned by
the getLibraryForProperty entry point in the script
Select many from
library
Represents a valid absolute path and that a file exists at the pathExternal editor
Validation at run time
Validation of a particular property value is performed at run time if isPropertyValueStatic() returns
false for that property.
In this case the property editor used to enter the source value (example: the script expression
or text with variables) is no indication for the appropriate validation scheme. Therefore, as a
general principle, standard run-time validation allows the computed property value to conform
to the validation scheme of ANY of the property’s property editors.
Specifically, the validation algorithm works as follows:
• Compile a list of validation schemes by adding the validation scheme from the following table
for each of the property’s property editors (“--” means do not add a scheme for this editor).
• The computed property value must be non-empty AND it must comply with at least one of
the validation schemes in the list compiled above (unless the list is empty).
Run-time validation schemeProperty editor
--Single-line text
--Password
Same as design-time schemeNumber
Same as design-time schemeHours and minutes
Same as design-time scheme, or a Boolean value (*)No-yes list
Same as design-time schemeDropdown list
363
Enfocus Switch 10