Home
HCL Domino Designer Basic User Guide and Reference
This guide provides information on using HCL Domino Designer and programming language reference information.
Application Management
Welcome to the Application Management section of Domino® Designer Help.
Security in an application
Domino® offers a multi-layered approach to security. Server administrators can secure databases, servers, and domains. Database designers and managers control the following:
Application design element security
An application developer can restrict access to design elements within an application. Application design security takes effect when users gain access to an application.
Creating public access pages, forms, subforms, outlines, views, agents, and style sheets

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 11 for developers?
  The following features are new for developers in HCL Domino® Designer 11.
- 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.
  - Security in an application
    Domino® offers a multi-layered approach to security. Server administrators can secure databases, servers, and domains. Database designers and managers control the following:
    - The database access control list
    - Application design element security
      An application developer can restrict access to design elements within an application. Application design security takes effect when users gain access to an application.
      - Controlling access to a database during design
      - Restricting who can read or edit documents
      - Using a Readers field to restrict access to specific documents
        To limit access to specific documents created from a form, include a Readers field on the form. A Readers field explicitly lists the users who can read documents created from the form. Without Reader access to a document, a user cannot see the document in a view. For example, to limit access to an employee's personnel file to members of the Human Resources department, the employee, and the employee's manager, list those people in a Readers field.
      - Using an Authors field to restrict who can edit specific documents
        An Authors field works in conjunction with Author access in the database ACL. If you assign users Reader access in the ACL, they can read documents in the database but cannot edit their own documents. If you list those users in an Authors field, they can edit documents in the database.
      - To create Readers and Authors fields
      - Tracking who edits a document
      - Updating Readers and Authors fields
      - Setting up the Administration Process for databases
      - Creating controlled-access sections of forms
      - Examples of access-controlled sections
        The following examples illustrate different uses for access-controlled sections on forms.
      - Limiting Editor access to sections of forms
        In workflow applications, use sections to restrict who can edit or sign parts of a document. If a document requires more than one approval signature, you create a section on the form for each signature or group. For example, you might create a section specifically for the Purchasing group.
      - Creating read access lists to limit view and folder access
      - Creating write access lists to limit folder access
      - Access-controlled forms and documents
      - Creating public access pages, forms, subforms, outlines, views, agents, and style sheets
    - Notes® and Domino® encryption
      Encryption is a digital security mechanism that protects data from unauthorized access. Encryption protects data from unauthorized access. Using Notes® and Domino®, you can encrypt:
  - Completing an application and managing design changes
    As you prepare to deploy an application, consider these finishing touches:
  - Deploying an application
    The tasks involved with application design, database design, database management, and DominoTMsystem administration may overlap, depending on the size of your organization and the structure of job responsibilities. In some organizations, an application developer may be responsible for both application and database design, while in others, a database manager may handle all database design and management tasks. In addition, database management overlaps with Domino® system administration.
  - Procedure for optimizing and troubleshooting databases
- 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.
- 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.

Creating public access pages, forms, subforms, outlines, views, agents, and style sheets

About this task

The database ACL controls access to specific design elements, such as pages, documents, forms, outlines, views, folders, and style sheets. Users with No Access or Depositor access in the ACL cannot access the design elements of a database. There are times, however, when you might want to make design elements accessible to all users, regardless of access level. To do so, you make the design elements available for Public Access.

For example, public documents are necessary for calendar applications where one user lets another user read or create appointments on his or her behalf. To create the public documents for this application, you must first create a public access form containing a public access field. Then you create a public folder or view to display the document.

Note that you can also make manually run agents available for public access.

To designate a page, form, or subform for public access

Procedure

Open the page, form, or subform.
Choose Design - <design element> Properties.
Click the Security tab.
Select "Available to Public Access Users."
On a form or subform, create a field.
In the Name field, enter $PublicAccess.
In the Type field, select Text and Computed when composed.
In the Programmer's pane at the end of the form, enter "1" as the default value for the field.
To hide this field from users, select the Field Hide When tab and specify hide-when conditions.

To designate a view for public access

Procedure

Open the view.
Choose Design - View Properties.
Click the Security tab.
Check "Available to public access users" if you want to make documents in this view or folder available to users with public access read or write privileges in the access control list for this database.

To designate an outline for public access

Procedure

Open the outline
Choose Design - Outline Properties.
Check "Available to public access users."

To create a style sheet for public access

Procedure

Click Resources - Style Sheets in the Design pane.
Highlight a style sheet and choose Resource - Resource Properties. The Style Sheet Resource Properties box appears.
Select the Security tab and check "Available to public access users."

To create an agent for public access

Procedure

Open the agent in Designer.
Click Options.
Select "Available to Public Access Users."