Engine Script
Description
Example of an Engine Script Document:
Script Name: The script name is entered here. The syntax is SERVER_NAME!!SCRIPT_NAME. For scripts that should be available on all servers, the server name is omitted, for example !!TEST_HELLO_WORLD.
Legacy Support: Usually, nothing is selected here. However, older scripts may have compatibility issues; in such cases, options may be enabled here to avoid these issues.
Category: The script can be organized by category in the views here. This is a purely organizational field.
Distribution: A distribution can be assigned to the script here. This is a purely organizational field.
Project: A project can be assigned to the script here. This is a purely organizational field.
Application: An application can be assigned to the script here. This is a purely organizational field.
Toolbox: If a batch is part of a Toolbox application, this is configured here.
Version: The version of the script. It is also displayed in the views. This is a purely organizational field.
CryptInherit: Reserved. Usually left empty.
Definition: The actual Engine script program.
Comments: Optional comments about the batch.
Update History: Displays the modification history for this document.
The buttons "Open in VS Code" and "Get back from VS Code" allow the Engine script to be edited in Visual Studio Code (VS Code) using the API Engine Language Extension, which is included in the distribution package.
The "Open in VS Code" button transfers the code from the document into a file and opens VS Code.
The "Get back from VS Code" button retrieves the code from the file (save it in VS Code first), writes it back into the document, and closes the document automatically. Unfortunately, this is necessary.
Visual Studio Code can be downloaded from Microsoft.
VS Code then provides a comfortable working environment with Quick Help, syntax highlighting, syntax checking, and autocompletion.
Note:
The Engine can easily process large Engine scripts. However, Domino/Notes is not very good at storing large source texts.
Therefore, source texts should not become too large. To avoid this, it is useful, for example, to move DEFFN functions into separate files or to split the Engine script into several parts and then merge them again using INCLUDE.
Note : This text was machine-translated and may contain inaccuracies.