Home
Administering Domino Leap
The following topics contain information for HCL Domino Leap admins.
Domino Leap Cleanup process
Domino Leap Cleanup primarily purges orphaned Builder attachments, orphaned application attachments, and old Preview databases. Prior to release 1.0.3, this process was done by the Domino Leap Cleanup Agent.

Administering Domino Leap
The following topics contain information for HCL Domino Leap admins.
- Controlling who creates HCL Domino Leap applications
  To configure who can create and delete applications, you need to modify the Access Control List (ACL) for VoltBuilder.nsf.
- Domino Leap configuration settings
  Domino Leap configuration settings are in VoltConfig.nsf in the volt folder of your Domino data directory (volt/VoltConfig.nsf). Use the Notes client or the Domino Administrator client to modify a configuration setting.
- Core Domino server configuration
  HCL Domino Leap is an add-on to the core HCL Domino server. Domino Leap runs in the context of the Domino web server (HTTP process). Therefore, Domino Leap is affected by the underlying Domino server configuration. This topic covers some of the core configuration settings that may affect Domino Leap.
- Upgrading from prior releases
  All Domino Leap NSF files set the database property Don't Maintain Unread Marks as default, which should improve performance. NSF files created in prior versions of Domino Leap are not changed.
- Adding a custom theme
- Domino Leap Cleanup process
  Domino Leap Cleanup primarily purges orphaned Builder attachments, orphaned application attachments, and old Preview databases. Prior to release 1.0.3, this process was done by the Domino Leap Cleanup Agent.
- Enabling basic authentication for HCL Domino Leap API requests
  If form-based authentication is enabled, you will see an HTML form for authentication instead of a pop-up window. This topic provides instructions on how to disable HTML form-based authentication for the HCL Domino Leap server API URL paths and enable basic authentication.
- Securing your Domino Leap deployment
- HCL Link integration
  HCL Link provides a platform for data and application integration.
- Strict CSP
  HCL Domino Leap has a limited capability to restrict the rendering of Domino Leap Forms using a “Strict CSP” policy.
- Admin Application Dashboard
  The Admin Application Dashboard is a page that is available to members of the Admin or SuperAdmin groups.
- Integrating with HCL Volt MX Foundry
  HCL Domino Leap can now use the integration services defined in HCL Volt MX Foundry.

Domino Leap Cleanup process

Domino Leap Cleanup primarily purges orphaned Builder attachments, orphaned application attachments, and old Preview databases. Prior to release 1.0.3, this process was done by the Domino Leap Cleanup Agent.

Orphaned Builder attachments

When a user creates a Domino Leap application, they can upload various files and store them as attachment documents in VoltBuilder.nsf. If the associated application is not saved, the uploaded files are no longer needed and should be deleted. This agent will purge these artifacts that have not been modified for the number of hours specified by the purgeOrphanFilesHours setting in VoltConfig.nsf

Orphaned application attachments

Domino Leap applications can have attachment uploads. These attachments are stored in the application .nsf on individual document notes. If the associated record is not saved, the uploaded file is no longer needed and should be deleted. This agent will purge these artifacts that have not been modified for the number of hours specified by the purgeOrphanFilesHours setting in VoltConfig.nsf.

Old Preview databases

When a Domino Leap Application is being designed, the user has the option of previewing their application prior to saving or deploying. A special preview-only nsf is generated for applications being previewed. This agent will delete all unused preview nsfs that have not been modified within the last seven days.

This clean-up process runs as part of the Domino Leap server process and no longer needs to be scheduled to run as an agent. The configuration and functionality are otherwise unchanged. To determine which hour of the day the clean-up process will run, set the orphanFileCheckHour parameter in VoltConfig.nsf. The default time is "0" for midnight.