Home
IBM Domino Designer Basic User Guide and Reference
Basic product usage information and programming language reference information.
Programming Overview and User Interface
This section contains general guidelines and examples that show where to use Java, LotusScript, and the formula language.
Programming Overview
This documentation describes how to attach Java, JavaScript, LotusScript, and formula code to Domino design elements. Here are some overview topics:
Window title, section access, and insert subform formulas
Window title formulas
A window title formula generates the text that appears in the title bar of documents using the form. The formula must evaluate to a text or numeric value, except that a single field of any type is permissible.
Examples: Window title formulas

IBM Domino Designer Basic User Guide and Reference
Basic product usage information and programming language reference information.
- 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 in Domino core allowing for a terse shorthand syntax for finding documents according to a wide variety of complexity of terms. It leverages existing design elements without the need to write detailed code to access them.
- 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.
  - Programming Overview
    This documentation describes how to attach Java, JavaScript, LotusScript, and formula code to Domino design elements. Here are some overview topics:
    - Programming in IBM Domino Designer
      Formula, LotusScript, Java, and JavaScript code provide an integral programming interface to Domino Designer. You attach code to various design elements depending on need. For example, if you create a computed field on a form, you would attach a formula to compute the value of the field. Or you could attach JavaScript code to the onFocus event of a field; this code would execute whenever a user places focus on the field. Or you might decide to create a formula, LotusScript, or Java agent to automatically update all the documents in a database at scheduled times.
    - Where to use scripts and formulas
    - Table of programmable design elements
      The following table outlines the programmable design elements in Domino. The table specifies the scope of the design element and whether it supports simple actions, formulas, LotusScript, Java, or JavaScript.
    - Toolbars
    - Replication formulas
      A replication formula selects the documents that are pulled into the current database during replication.
    - Writing scripts and formulas for agents
      An agent is a user procedure that you can trigger through a number of mechanisms. An agent runs on:
    - Writing scripts and formulas for actions
      An action is a formula, LotusScript, JavaScript, or simple (no programming) procedure that you can associate with a view, form, subform, or page. You can create a standard action, an action with subactions, a shared action, or insert system actions that are supplied with Notes.
    - Hotspots
      In form design, subform design, page design, navigator design, layout region design, and rich text fields, you can create hotspots. A hotspot activates when the user selects it and can be any of several types:
    - Form, selection, and column formulas
    - Window title, section access, and insert subform formulas
      - Window title formulas
        A window title formula generates the text that appears in the title bar of documents using the form. The formula must evaluate to a text or numeric value, except that a single field of any type is permissible.
        Examples: Window title formulas
      - Section access formulas
        A section access formula specifies the names or ACL roles of users who can edit the fields in the section. Other users only have reader access to the section. However, this specification does not override the access control list for the database.
      - Insert subform formulas
        An insert subform formula specifies the name of a subform for insertion into the form. The formula must evaluate to a text value that is the name of a subform. An invalid name results in a run-time error.
    - Section title and hidden paragraph formulas
    - Hidden column and row custom color formulas
    - Named element formulas
    - Image formulas
      Formulas can be used to specify the name of an outline image, the background image in a view, the background image in an embedded outline, the twisties image in a column, and the twisties image in an embedded outline.
    - Writing scripts and formulas to handle events
    - Field design formulas
      As part of the field design process, you can write the following formulas to run on the user's workstation:
    - Event descriptions
      Simple action, Formula, LotusScript, JavaScript, and Java code executes in response to the occurrence of events in the following objects: actions, action hotspots, agents, hotspot buttons, databases, fields, folders, forms, formula pop-ups, outlines, pages, script libraries, subforms, and views.
    - Event sequencing
      The following table shows the sequencing of events during common Notes tasks.
  - User Interface
  - XML for Domino
    The following topics cover some general guidelines for using XML in Domino applications and list all the elements, attributes, and entities in the Domino Document Type Definition (DTD):
  - JSP Custom Tag Libraries
    A JavaServer Page (JSP) is a HTML Web page that contains code which executes application logic to generate dynamic content. The page is created at the time it is requested. JSP pages are compiled into servlets; the code they contain is executed by the server. For more information on JSPs, see the Sun Microsystems Web site: http://java.sun.com/products/jsp/.
  - Programming Domino for Web Applications
    You should be aware of certain procedures, restrictions, and enhancements available to you when using Domino Designer to program Web applications. This section describes the following areas:
- Formula Language
  This section documents the formula language.
- 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.
- Lotus® Connectors
  Lotus® 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: Window title formulas

This formula displays the static text "Focus Group Discussion" in the title bar.
```
"Focus Group Discussion"
```
This formula displays the static text "New Topic" for a new document. For an existing document, the formula displays the contents of the Subject field followed by text indicating the number of response documents associated with this document.
```
@If(@IsNewDoc; "New Topic"; Subject +
@DocDescendants(" (No Responses)"; "(1 Response)"; "(% Responses)"))
```

This formula displays a window title suited to a Response or a Response to Response document.

@If(@IsNewDoc; "New Response to " + Subject;
"Response " + @DocNumber("") + " of " + @DocSiblings + " to " + Subject)

This formula, which evaluates to a time-date value, is legal.
```
@Created
```
In this formula, the time-date field must be explicitly converted to text because it is part of an expression.
```
"Response created on " + @Text(@Created)
```