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 and upcoming events around #dominoforever, please visit our Destination Domino Page

Status Under Consideration
Workspace Volt
Created by Guest
Created on Aug 12, 2021

flexible/maintainable paths to services in other applications

we work in different working environments (development, beta, ....). the problem is, if i configure one service (for example start of an agent) in a database and then i change with my volt-file from dev -> beta .... this service doesn't work anymore.

  • Attach files
  • Guest
    Reply
    |
    Mar 6, 2023

    I guess we have the same problem. We have a productive and a test environment. If we want our Domino Leap application to run correctly in the productive environment, we currently have to make sure that the path to the database on the productive server is the same as on the test server and that the database has the same name (e.g. application.nsf ) as on the test server. Then it works.

    However, when we develop Domino Leap applications for customers, it is rather unpleasant that we have to create the same folder structure for the DB used on our test server as in the customer's productive environment, because we are not able to change the path afterwards. Here we would like to be able to subsequently select the right database again for the services, instead of having to create completely new services.