Home
HCL Domino Designer XPages User Guide
This guide focuses on the aspects of creating applications using XPages technology.
Designing XPages applications
HCL Domino® Designer provides the means to populate an XPage with controls and other artifacts, and to associate an XPage with data stores.
Previewing and running XPages
XPages run in Domino® server and Notes® client environments. From Domino Designer, you can preview XPages in both environments.
Signing XPages
XPages are signed with the ID of the current Domino® Designer user upon saving the XPage design element, and/or upon generating its implementation (i.e .class) file(s).

HCL Domino Designer XPages User Guide
This guide focuses on the aspects of creating applications using XPages technology.
- Product overview
  HCL Domino® Designer supports applications development for the HCL Domino platform using XPages, forms, views, and other elements such as controls.
- Tutorials
  This section contains tutorials and information about tutorials.
- Administering applications
  HCL Domino Designer provides features for administering and managing your work and related files while developing your application projects.
- Designing XPages applications
  HCL Domino® Designer provides the means to populate an XPage with controls and other artifacts, and to associate an XPage with data stores.
  - Previewing and running XPages
    XPages run in Domino® server and Notes® client environments. From Domino Designer, you can preview XPages in both environments.
    - Previewing an XPage
      You can preview an XPage in a Domino® server or Notes® client environment.
    - Opening an XPage upon application launch
      You can open an XPage upon application launch.
    - Opening another XPage
      From an XPage, users can open other XPages through navigation rules, a simple action, XSPContext methods, and opening the URL.
    - Opening an XPage instead of a view
      For Web access only, you can open an XPage instead of a view.
    - Signing XPages
      XPages are signed with the ID of the current Domino® Designer user upon saving the XPage design element, and/or upon generating its implementation (i.e .class) file(s).
    - Using XPages in the Notes® client
      You can run XPages applications in the HCL Notes® rich client.
    - Designing single copy XPages
      You can store XPage design elements in one database and redirect other databases there at run-time.
    - Creating accessible applications with XPages - an overview
      For Domino® developers creating Web applications, XPages is the recommended accessible solution.
    - Specific accessibility guidelines for XPages
      Making sure that an XPages application and controls are accessible.
  - Adding controls
    Controls are visual elements such as edit boxes, buttons, images, and text that allow users to manipulate data on an XPage.
  - Adding controls from the XPages Extension Library
    The XPages Extension Library provides additional controls ready to use. The controls include an application layout object, an improved dialog, pickers, in place forms, Dojo components, dynamic content, and much more. The controls support enhancements to the Domino(r)® templates.
  - Binding and submitting data
    The data store for XPages is Domino®. You can access the data store through Domino forms and views.
  - Adding images, styles, and themes
    You can enhance your design with images, styles, and themes.
  - Responsive web design support in XPages
    The XPages Extension Library supports Bootstrap, a Responsive Web Design (RWD) framework. This support comes in the form of an XPages Responsive Bootstrap plugin that you can use in your XPages applications.
- Designing composite applications
  You can create composite applications from XPages.
- Programming
  XPages uses JavaScript™ for programming while the forms-based design elements use the formula language, LotusScript®, Java™, and JavaScript.

Signing XPages

XPages are signed with the ID of the current Domino® Designer user upon saving the XPage design element, and/or upon generating its implementation (i.e .class) file(s).

About this task

Signing an XPage determines whether it will load at runtime, and thereafter whether it can run with or without restrictions on its methods and operations. Running with restrictions excludes certain features such as file or network I/O, which is the more common approach. Running without restrictions allows all supported features of the XPage implementation languages to be used (see topic Restricted LotusScript® and Java™ agent operations at Domino® Designer Basic User Guide and Reference > Application Design > Adding automation to applications).

As server access rights, the rights to execute restricted/unrestricted methods are assigned to specific signers or groups in the Programmability Restrictions section of the server document Security tab (see topic Controlling agents and XPages that run on a server at Domino® Administrator Help > Security > Server access for Notes® users, Internet users, and Domino® servers > Customizing access to a Domino® server).

When an XPage is invoked (as for Agents), Domino® checks the server document for the server security rights of the XPage signer, in addition to checking access rights for the authenticated Web user. For components of the XPage (e.g. included XPages, custom controls, JSF extensions, or server JavaScript™ libraries), Domino® checks each component signer’s server access rights, and if indicated, downgrades the XPage session to execute only with restrictions (if set for Domino®, the NoExternalApps notes.ini variable has the same effect). At runtime, signatures for DDE users without any server rights to sign XPages at all will generate HTTP 403 errors back to the browser.