Specifies a script to load and execute before the script containing the directive is executed. Multiple @include directives are interpreted in the order of their appearance in the script text.
New in package 165 Recursive @include directives are supported: the script to be loaded is parsed for the presence of its own @include directives, which are then interpreted, etc.
New in package 166 Added built-in support for a common pattern of separation client and server sections of the script. Including <script-name>.js now automatically triggers lookup, and, if found, execution of the corresponding <script-name>.client.js / <script-name>.server.js counterpart (depending on the context) immediately after the master script's execution.
|script-location|| Location prefix determining script-path interpretation. Can be one of the following:
|script-path||Path to the script to load and execute.|
- Scripts placed into <Application Server>/files/<database-name>/stored-files/scripts directory will automatically shadow identically named stored scripts in the <database-name> database (default <Application Server> location is %PROGRAMFILES(X86)%\MetaCommunications\Application Server).
- Further alternative script lookup location(s) can be specified by creating .<database-name>.ini file in the <Application Server>/files directory, with the content along the following lines:
- [package:...] directives can be used to automate repetitive [mapping] directives, in particular the following directive
is equivalent to the following [mapping] directives:
The following directive by default includes workflow.v5.js script from the Stored Scripts location in database: