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.
- 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.
  - Java™ Classes Coding Guidelines
    - Running a Java™ program
      You can call the Domino® Objects from a Java™ program by importing the lotus.domino package. The program can be coded as an application, a Domino agent, an applet, or a servlet. Local calls access run-time code on the local computer, which must have Domino installed. CORBA-based remote (IIOP) calls access run-time code from a remote Domino server; in this case, the local computer need not have Domino installed. Compilation must be on a computer with Domino Designer installed.
    - Accessing databases
    - Accessing views and folders using Java™
    - Accessing documents in Java™ classes
    - Accessing items in Java™ classes
    - Accessing rich text items in Java™ classes
    - Accessing Domino® sessions
  - Java™ Classes A-Z
- 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.

Collecting documents by searching in Java™ classes

FTSearch, FTSearchRange and Search in Database, and unprocessedFTSearch, unprocessedFTSearchRange, and unprocessedSearch in AgentContext return a DocumentCollection object containing documents that match a search query. FTSearch in DatabaseCollection refines a DocumentCollection so that only documents that match a search query are retained. FTSearch in View and FTSearch in ViewEntryCollection do the same for those objects. Use FTDomainSearch to search a domain.

For FTSearch, unprocessedFTSearch, and unprocessedFTSearchRange, the search query is a string that meets the Notes® rules for full-text search queries, requiring that a search entity be a single word or multiple words enclosed in quotes (escape the quotes in string constants). Search entities can include ? and * wildcards, and can be combined by ! (not), & (and), and | (or) operators. For the complete syntax rules, see "Refining a search query using operators" in Notes® Help. Search for "query syntax" in the Domino® Designer Eclipse help system or information center (for example, http://publib.boulder.ibm.com/infocenter/domhelp/v8r0/index.jsp), both of which include Notes®.

For search and unprocessedSearch, the search query is a Domino® formula.

A database does not have to be full-text indexed for FTSearch, unprocessedFTSearch, and unprocessedFTSearchRange to work, but the search is slower. Use updateFTIndex to create or update a full-text index. Use isFTIndexed to test for the existence of an index.