Home
Reference
The documents in this section provide reference material and samples for Domino Leap.
Custom Widget API
This API provides a mechanism to incorporate custom widgets into the HCL Domino Leap product.
Known limitations

Reference
The documents in this section provide reference material and samples for Domino Leap.
- REST API reference
  The REST API can be used by other programs to communicate with Domino Leap.
- JavaScript™ API
- Services
  The following topics provide reference information about adding services to Domino Leap.
- Embedding items in an iframe
  You can use iFrames to embed charts and applications in a web page.
- Embedding API
  The Embedding API is used to embed a Domino Leap form directly in another webpage without using an <iframe>. The Domino Leap form is inserted into the DOM of the hosting page and can be interacted with using the JavaScript API or any custom JavaScript. Additionally, the style of items in the form can be customized by the CSS of the hosting page.
- Creating customized Cascading Style Sheets
  You can apply your own custom Cascading Style Sheet (CSS) to the rendering of your Domino Leap application. To create a custom theme, you must be familiar with the basic concepts of CSS.
- Custom Widget API
  This API provides a mechanism to incorporate custom widgets into the HCL Domino Leap product.
  - Data Widgets vs Display Widgets
    Some widgets are for collecting data (ie. "data widgets") and others are presentational in nature (ie. "display widgets").
  - Data Types
    Data widgets can declare one of the listed data types, each with additional optional constraints.
  - Rules
    App authors will be able to incorporate custom widgets in rules.
  - Built-In Properties
    Some properties that already exist in the product are general purpose, or, are integral to the proper functioning of a widget.
  - Custom Properties
    The custom widget can define an array of custom properties for the app author to modify.
  - Widgets with Options
    Widgets that allow the end-user to select from a set of options require specific treatment. This includes widgets such as dropdowns, radio groups, or checkbox groups. These options could be hardcoded in the custom widget, or defined by the app author.
  - Widget Instantiation
    The widget instantiate() function is called when an instance of the custom widget needs to be created. The function is expected to return an object that allows Domino Leap to interact with the instantiated widget.
  - Aggregation Widgets
    A custom widget with a datatype of aggregation is a special type of data widget that can achieve the use-case of a repeating section.
  - Validation
    Some intrinsic validation will be done according to the type and constraints declared in the widget's datatype property; however, it might be necessary for a widget to supply its own custom validation logic.
  - Internationalization
    Certain attributes of the widget definition can be displayed to app authors working in different locales. To support multiple languages during authoring, some properties can be specified as "multi-string" objects rather than a plain string values.
  - Usage of JavaScript API
    Custom widgets can use Domino Leap's JavaScript API to help achieve their objectives.
  - Versioning
    This topic describes the widget's version.
  - Upgrading
    The exact techniques for upgrading widgets from one major version to the next has not yet been established.
  - Security Considerations
    This topic describes security considerations for Custom Widget API.
  - Incorporating third-party libraries
    This topic describes incorporating third-party libraries.
  - Known limitations
  - Examples

Known limitations

Complex Data: Widgets that need to store complex data are expected to use a "parsable" string value (ex. JSON). There is no mechanism to handle customized rendering of this value in some parts of the product (ex. Print View), or to customize searching/filtering based on the intricacies of the complex value.
Containers: There is no support for custom container widgets, those being widgets that contain other widgets, such as a collapsible section.
Full Custom Properties: There is no mechanism to supply 100% custom properties. Properties of the custom widget will be from a set of common prescribed types.
In-line Editing: There is no mechanism to support the app author in direct in-line editing of a widget's properties on the canvas.
Multilingual Apps: There is no mechanism (beyond an app author's custom JavaScript) to allow app authors to supply property values for an application that is to be used by end-users who speak different languages.
Author-Defined Data Constraints - There are limited mechanisms for app authors to define data constraints on the values supplied by end-users. Values can be constrained in the UI by the custom widget itself, or by the author's custom JavaScript.