Welcome to the #dominoforever Product Ideas Lab! 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 jointly by the IBM & 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.

Fix all source control issues

There are currently a number of issues with DXL round-tripping that affects use of source control. These include:

  • All day agents are stored as running from 00:00 to 00:00. Somewhere in the DXL export / import that gets corrupted
  • Something on navigators?, see https://www.slideshare.net/gregorbyte/using-source-control-for-domino-development-auslug-2016
  • Image Resources used in Outline entries include database replica id in DXL
  • JavaScript Library resources in JS Header are lost from DXL
  • Datestamps cause conflicts, see https://domino.ideas.aha.io/ideas/IDEAAD-I-35
  • Binary / Non-Binary DXL setting is global. This may need to differ at NSF level depending on sharing of projects (think open source or HCL template pull requests).

I discussed this with Andre Guirard at Lotusphere 2014 when I (Paul Withers) also presented a Show and Tell session with Declan Lynch. The impression I got at Ask The Developers was that there are other issues I hadn't identified. I know DDE does something to extract Java agents as a separate "Project" when you edit them, so I'm not sure how DXL round-trips those. When analysing DXL for design elements recently, I've encountered failures to read the DXL sometimes, possibly related to older databases. I believe there may have been some improvements around DXL for or in ApplicationInsights, I don't know what they were or whether they're in recent Domino or Domino Designer versions.


With the news about HCL Nomad there has been an increased focus on traditional Notes Client applications. But the issues identified and potential for others makes this an inadvisable route for source control management. Other proprietary solutions are limited to Domino, meaning differing source control tools and experiences for Domino and non-Domino solutions. In the current landscape and the desired future for Domino, that also is not desirable.


Source control requires single flat files rather than the Design Notes in an NSF. I don't know if that can be addressed. It's not beyond the realms of possibility that opening a database in DDE could actually generate an ODP or allow conversion to an ODP, and an "Applications Navigator" could launch the simulated, "Views" of design element types (Forms, Framesets etc) generated based on metadata, with the appropriate editor launched automatically.


  • Faithful DXL round-tripping could result in developers using a consistent toolset, which is a benefit for everyone.
  • It would also mean source control could properly be used for all Domino projects on OpenNTF.
  • It could also provide flexible deployment options for users / developers / administrators from an "Application Catalog"
  • It could allow OpenNTF / Business Partners to more easily deploy applications to servers/ end users
  • It could allow IBM / HCL to easily deploy updated templates outside the traditional release cycles
  • It would allow developers to easily send pull requests to open source projects
  • There are some IBM templates already open-sourced on OpenNTF. Future versions or other templates could then be open-sourced. It would allow IBM / HCL to receive pull requests for standard templates accepting bug fixes, new features, improvements for interface, extensions for integration outside of the NSF etc.
  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Aug 16 2018
  • Investigating
  • Attach files
  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    August 18, 2018 13:54

    Adding to the list of issues:

    1. Hotspot button became large when re-imported back to Domino since there are non visible characters added to the text
    2. Sometimes Database icon does not appear even if the $DBIcon file still exist in the image resource. Have to delete the $ DBIcon file and re-add image via database icon page.
    3. Image in Outline Entry sometimes does not appear. Have to delete the image name in the Outline Entry properties and select the image again.

    Pretty sure there are other issues as well.

  • Admin
    Thomas Hampel commented
    October 27, 2018 07:51

    Moving this idea to product : Domino Designer

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    November 15, 2018 15:23

    when using swiper to remove noisy parts of dxl you sometimes ends up in a loop. export -> swipe > import > changed element > export > swipe  ... and at the end some design elements get broken. 

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    05 Feb 05:13

    Build and deploy tools need to be able to pull the branch, build it and deploy it.  There is no reason for organizations to have Domino as this island when organizations have a DevOps culture, Cloud first, QA team that will run tests against a deployed build.