Skip to Main Content
HCL Domino Ideas Portal

Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.


For more information on products and upcoming events around #dominoforever, please visit: HCL Domino Page


Status Needs Review
Workspace Leap
Categories Documentation
Created by Guest
Created on Sep 9, 2026

Allow Reuse of Existing Services in Workflow

In HCL Leap, when configuring a Workflow for a form, if we need to invoke a service, we currently have to create a new service from within the Workflow configuration.

However, HCL Leap already provides a Services section where services can be created and maintained. It would be useful if existing services created under the Services section could be directly selected and reused within a Workflow instead of requiring developers to create the same service again.

Proposed Enhancement

Provide an option in the Workflow service configuration to:

  • Select an existing service from the application's Services section.

  • Reuse the selected service directly within the workflow.

  • Display available services along with their operations/actions.

  • Allow the workflow to map inputs and outputs to the existing service.

  • Maintain a single service definition that can be reused across multiple workflows.

Example

If an application already has a service such as:

Services → UserManagementService → GetUserDetails

When configuring a workflow, instead of creating a new service again, the developer should be able to select:

Workflow → Service → Use Existing Service → UserManagementService → GetUserDetails

This would follow a "Create Once, Reuse Anywhere" approach.

Benefits

  • Avoids creating duplicate services.

  • Reduces development and maintenance effort.

  • Promotes service reusability across multiple workflows.

  • Ensures changes to a common service can be centrally maintained.

  • Improves consistency across the application.

  • Makes application development more modular and maintainable.

  • Attach files