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:
    - 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
      - Examples: 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: Performing time-date operations

(@Created) This agent example writes "Archive" to the Status field if the current document was created before 1995, and writes "Current®" otherwise.
```
SELECT @All;
FIELD Status := @If(@Created < [01/01/95 12:00:00 AM]; "Archive"; "Current");
```
(@Modified, @Date, @Today, @Yesterday) This agent example writes "Today," "Yesterday," or "Old" to the ViewStatus field, depending on the date that the current document was last modified.
```
FIELD ViewStatus := @If(@Date(@Modified) = @Today; "Today"; @Date(@Modified) = @Yesterday; "Yesterday"; "Old");
SELECT @All
```
(@Modified, @Date, @Weekday, @Today, @Adjust, @Yesterday) This agent example modifies the preceding example to exclude weekends in assigning "Yesterday." If today is Monday, y is set to today's date minus 3 days; otherwise y is set to yesterday's date. Then y instead of @Yesterday is tested against the @Modified date.
```
d := @Date(@Modified);
y := @If(@Weekday(@Today) = 2; @Adjust(@Today; 0; 0; -3; 0; 0; 0); @Yesterday);
FIELD ViewStatus := @If(d = @Today; "Today"; d = y; "Yesterday"; "Old");
SELECT @All
```

(@Now, @Month, @Year, @Day) This example of a computed text field displays today's date in letterhead form. For example, 6/30/95 displays as "June 30, 1995."

months := "January" : "February" : "March" : "April" : "May" : "June" : "July" : "August" : "September" : "October" : "November" : "December";
month := @Subset(@Subset(months; @Month(@Now)); -1);
year := @Year(@Now);
day := @Day (@Now);
month + " " + @Text(day) + ", " + @Text(year)

(@Adjust, @Weekday, @Created) This example of a computed time field displays a date two days from the creation date for the document. The calculation eliminates the weekend by adding 4 days if the creation date is a Friday.
```
increment := @If(@Weekday(@Created) = 6; 4; 2);
@Date(@Adjust(@Created; 0; 0; increment; 0; 0; 0))
```

(@BusinessDays) This agent displays the number of days in 2001 excluding Saturdays, Sundays, and 10 holidays.

@Prompt([Ok];
@Text(
@BusinessDays([01/01/2001]; [12/31/2001]; 1 : 7;
[01/01/2001] : [01/15/2001] : [02/16/2001] : [05/28/2001] : [07/04/2001] :
[09/03/2001] : [10/08/2001] : [11/22/2001] : [11/23/2001] : [12/25/2001])
);
"Business days in 2001")

Have feedback?
Google Analytics is used to store comments and ratings. To provide a comment or rating for a topic, click Accept All Cookies or Allow All in Cookie Preferences in the footer of this page.