Home
HCL Domino Designer Basic User Guide and Reference
This guide provides information on using HCL Domino Designer and programming language reference information.
Formula Language
This section documents the formula language.
Formula Language Coding Guidelines
Handling errors
Errors are of two types:
Run-time errors
Run-time errors occur when the formula runs. These errors can be categorized as follows:
Examples: Run-time errors

HCL Domino Designer Basic User Guide and Reference
This guide provides information on using HCL Domino Designer and programming language reference information.
- What's new in HCL Domino Designer 12?
  The following features are new for developers in HCL Domino® Designer 12.
- Accessibility and keyboard shortcuts
  Accessibility features assist users who have a disability, such as restricted mobility or limited vision, to use information technology content successfully.
- Application Design
  Welcome to the Application Design section of Domino® Designer Help.
- Application Management
  Welcome to the Application Management section of Domino® Designer Help.
- Domino® Query Language
  Domino® Query Language (DQL) is a facility running on a Domino server that provides a terse, shorthand syntax for finding documents. It supports a wide variety and complexity of search terms. It leverages existing design elements, avoiding the need to write detailed code to access them. DQL consolidates all methods in Domino for searching document contents.
- Composite Applications - Design and Management
  Composite applications are a key element in a service-oriented architecture (SOA) and contextual collaboration strategy. The ability to create and edit composite applications lets you easily integrate different types of components and technologies.
- DB2® Access views
  Domino® Designer includes two types of design elements to assist you in managing data contained in DB2® enabled Notes® databases:
- Programming Overview and User Interface
  This section contains general guidelines and examples that show where to use Java, LotusScript, and the formula language.
- Formula Language
  This section documents the formula language.
  - Formula Language Rules
    Formula language provides syntax and @functions for evaluating constants and variables, and for performing simple logic. Variables can be fields in Notes® documents or temporary variables (also called temporary fields) used only for the immediate formula.
  - Formula Language Coding Guidelines
    - Formulas
      A formula consists of one or more statements that are executed in order. Depending on the object associated with the formula and other criteria, the formula may execute once or it may execute multiple times on selected documents (one execution per document).
    - Writing messages and getting user input
      You can communicate with the user through these techniques:
    - Handling errors
      Errors are of two types:
      - Syntax errors
        Syntax errors are reported when you either check or attempt to exit the formula you are writing. You receive a message specifying the error, and the line containing the error is highlighted. You must determine and then correct the error before proceeding. Common syntax errors include the following:
      - Run-time errors
        Run-time errors occur when the formula runs. These errors can be categorized as follows:
        Examples: Run-time errors
    - Working with @functions
      All @functions evaluate to a value and can be placed in a formula anywhere a value of that type can be placed. When the formula executes, the value of the formula takes the place of the formula. Some formulas also have side-effects, that is, they cause actions to occur. For example, @Prompt causes a message box to appear.
    - Working with @commands
      @Commands are special @functions that perform immediate actions in the user interface. Most @commands mimic menu commands. For example, the following formula, if executed from a button, puts the current document in Edit mode and moves the insertion point down twice:
    - Performing string operations
      Formula language @functions enable you to:
    - Performing arithmetic operations
      The * / + - operators multiply, divide, add, and subtract. Multiplication and division have precedence over addition and subtraction; otherwise, evaluation is left to right. Parentheses can be used to change the order of evaluation. The following are the arithmetic @functions.
    - Performing time-date operations
    - Accessing the user environment
      The user environment is the server or workstation containing the database for: replication formulas, agents with the triggers "After new mail has arrived" or "On schedule," selection formulas, or column formulas. Otherwise, the user environment is the Notes® workstation of the user running the formula.
    - Accessing the current database and view
      You have immediate access to the database in which the formula is running, except for toolbar button formulas, which have no database context. You have immediate access to the view in which the formula is running if you are in the context of a view. In the context of a document, you have immediate access to the view from which the document was opened.
    - Accessing the current document in the formula language
    - Accessing data outside the current document and database
      The following @functions get data values from a specified database. You cannot set values with these @functions.
    - Accessing external databases through LS:DO using @functions
      The following @functions access an external database through ODBC and return a value or list of values:
  - Formula Language @Functions A-Z
    Formula Language @Functions A-Z
  - Formula Language @Commands A-Z
- LotusScript® Language
  Welcome to the LotusScript® Language section of Domino® Designer Help.
- LotusScript/COM/OLE Classes
- Java/CORBA Classes
  This section documents the Java/CORBA classes.
- Connectors
  Connectors provide native access to a wide variety of DBMS products, ODBC, the platform File system, Enterprise Resource Planning systems, and Transaction Processing systems.
- Javadoc™ for Domino® Designer related APIs
  As part of providing additional Java™ reference documentation, Domino® Designer ships with a help plugin that contains Javadoc™ for additional Domino Designer related APIs.

Examples: Run-time errors

This validation formula for the Price field causes a save operation for the document to fail with the specified message if the Price field contains an error.
```
@If(@IsError(Price); @Failure("The Price field must be numeric"); @Success)
```
This example contains input translation and input validation formulas. The input translation formula puts an error into the Price field if its value is greater than 14.99. The input validation formula causes a save operation for the document to fail with the specified message if the Price field contains an error.
```
REM "Input translation formula for Price field";
@If(Price > 14.99; @ERROR; Price)
REM "Input validation formula for Price field";
@If(@IsError(Price); @Failure("The Price field must be numeric and 14.99 or less"); @Success)
```

This button formula checks the Price field for an error before applying a discount. If the field contains an error, the formula returns first giving the user a message.

FIELD Price := @If(!@IsError(Price) & @IsNumber(Price) & Price < 15; Price * 0.85; @Return(@Prompt([Ok]; "Error in price field"; "Must be numeric and less than 15.00"; "")));
@All

This button formula tests the Price field for an error. If the field contains an error, the formula resets it to a value taken from the user by @Prompt.

FIELD Price := @If(!@IsError(Price) & @IsNumber(Price) & Price < 15; Price; @TextToNumber(@Prompt([OkCancelEdit]; "Error in price field"; "Enter a number under $15.00"; "")));
@All

This agent formula tests the return value of an @DbLookup statement for an error. If the statement causes an error, the formula returns the text "Not available."

result := @DbLookup("";"Snapper":"names.nsf";"People";
@Right(Name;" ") + " , " + @Left(Name; " "); "OfficePhoneNumber");
FIELD Phone := @If(@IsError(result);"Not available";result)