Home
Building applications
The following topics contain information on how to build and efficiently use applications in HCL Domino Leap.
Domino Leap document integration
HCL Domino Leap's document integration feature lets you use previously built PDF files and populate them with data captured by Domino Leap in a Domino Leap form.
Creating the PDF trigger
The following instructions describe how to create a trigger that calls the PDF service, and triggers the service when the user clicks the button.

Building applications
The following topics contain information on how to build and efficiently use applications in HCL Domino Leap.
- Creating an application
  This topic gives a general overview of the application creation process, from opening the Domino Leap interface to launching a completed application.
- Creating an application from an excel spreadsheet
  Domino Leap allows you to create an application from an excel spreadsheet, automatically creating the widgets and importing the data found in the spreadsheet.
- Styling your application with a custom theme
  Style the colors, fonts, and other characteristics of the application by creating or importing a custom theme.
- Moving items in an application
  Form items are not static after they are added to a form. You can move items around on a single page, duplicate form items, and move items between pages on your form.
- Copying items
  Items may be copied from one form to another form within any application.
- Creating an accessible application
  When you create an application, the following information helps you make it accessible for users with disabilities.
- Enabling dynamic layout
  When you build applications, you can now set the display width of your Domino Leap application. Setting this feature reduces or removes the need for horizontal scrolling when you have an unknown or limited amount of space.
- Globalization features
  The following information describes the languages formatting features supported by Domino Leap.
- Creating rules in your application
  Rules help you gather the correct information from users and organize your information after data is entered in a form or app page. You can create composite rules that govern how your form or app page - and the data in it it - behaves.
- Labeling data, performing data analysis, and exporting data
  You can add labels to data elements in your application that become the label in the export file.
- Incorporating services into your applications
  The following topics describe how to incorporate services into your Domino Leap application.
- Adding formulas to your application
  Use formulas to assign values to items on an HCL Domino Leap form or app page. They are divided into two categories: Item Formulas, which list formulas created from the Properties panel, and General Formulas, which list complex formulas created from the Settings tab.
- Adding specialized items
  You can use specialized form or app page items to style text, echo text back, create dynamic lines, or add HTML.
- Managing the files associated with your application
  You can upload a variety of files, such as images, for use with your application. Managing these embedded files is done in the Files section of the Settings tab
- Domino Leap document integration
  HCL Domino Leap's document integration feature lets you use previously built PDF files and populate them with data captured by Domino Leap in a Domino Leap form.
  - Adding a PDF to Domino Leap
    The following instructions describe how to add a PDF to Domino Leap.
  - Mapping form items to PDF fields
    The following instructions describe how to create a Service Configuration to map Domino Leap fields to fields in an existing PDF and, when triggered, returns the filled PDF to the user.
  - Mapping form items to PDF fields and storing the filled PDF
    The following instructions describe how to create a Service Configuration to map Domino Leap fields to fields in an existing PDF and, when triggered, stores the filled PDF as an attachment to the record.
  - Creating the PDF trigger
    The following instructions describe how to create a trigger that calls the PDF service, and triggers the service when the user clicks the button.
  - Saving a PDF to a file location
  - Document integration usage details
    The following usage details describe the best practices and limitations for integrating your Domino Leap application with a PDF.
- Adding Stages to an application
  It is often desirable to have an application, or form, transition through a set of phases or stages. At each stage the form might be used by different people in different roles. The form also might be presented in a slightly different manner in each stage, such as having some items or pages hidden, or in a read-only state.
- Deploying applications and viewing responses
  After a Domino Leap application is built it must be deployed. After it is deployed, you can supply users with the URL of the application so they can launch it. After users submit completed forms, you can view the responses.

Creating the PDF trigger

The following instructions describe how to create a trigger that calls the PDF service, and triggers the service when the user clicks the button.

About this task

When the user clicks the button, the service that maps information from the form to the PDF is triggered. The PDF is displayed, or stored as an attachment, with user supplied information in the PDF fields.

Procedure

Add a Button to your form from the Palette.
Change the Caption of the button so users know that clicking it populates a PDF.
For example, change the caption of the button to Create PDF.
Select the widget in the form.
The Properties panel displays on the side of the screen.
Select Call a service when clicked.
Select the Service Configuration you created from the menu.
Save your application.

Results

When the application is deployed, you can click the Create PDF button and a PDF is populated containing the values that are entered in the Domino Leap application.

Note: You can use other common form events as triggers, including validateButtonPressed. Stage action buttons cannot be used as triggers.