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

ADD A NEW IDEA

Domino Designer

Showing 1249

Improve syntax-error reporting in LotusScript compilation

When compiling LotusScript in notes (either via Designer's Recompile All LotusScript or in C via NSFNoteLSCompile), it's very easy to run into a situation where the compiler reports just "Syntax Error", with no indication as to the source of the t...
over 2 years ago in Domino Designer / LotusScript 1 Under Consideration

Rest API XPAGES secure

I want to have an API that goes to a view and retrieves some data, but I don't want that user to access the database via the web. This is not possible because to create a REST API from XPages, you have to grant permissions to the database where yo...
4 months ago in Domino Designer / XPages 2 Already Exists

Find and Replace should work correctly for Formula inside a form

In the Domino Designer, finding all occurrences of some code in fields with Formula language is virtually impossible. Ctrl-F or Find and Replace doesn't search consistently everywhere in a form. LotusScript is ok, but then only LotusScript. If the...
about 1 year ago in Domino Designer / @Formulas 0 Needs Review

DQL: improvements on named variable handling and on documentation

Playing around with DQL, and especially with NamedVariables. The NotesDominoQuery class at the moment has 2 methods dealing with named variables: DQL.setNamedVariable("name", "value") DQL.resetNamedVariables() The more I try to use that concept th...
about 2 years ago in Domino Designer / LotusScript 3 Needs Review

Missing documentation for NotesDominoQuery class

Currently working my way through DQL and QRP topics. Tried to get a catch on NamedResults and was wondering for a couple of days why I couldn't get it to work: I'm working on a simple query like Set nQuery = myDb.CreateDominoQuery() sQuery = "task...
about 2 years ago in Domino Designer / LotusScript 1 Needs Review

Fix design synopsis so it handles applications with large designs

Currently, when trying to provide a design synopsis of a database with a large design, you can get the "Document has too many paragraphs". Creating multiple design synopsis manually (one per design element type) does not always help and so results...
over 5 years ago in Domino Designer 0 Under Consideration

Misleading documentation must be corrected esp. in the NotesDominoQuery area

I'm currently fighting my way into the DQL and QRP classes (LotusScript/Java), and found many bad and misleading information as well as missing parts in Designer help. To begin with, there are only examples in the LotusScript area, Java examples a...
about 2 years ago in Domino Designer / LotusScript 2 Under Consideration

Add preference for NOT using Option Public in LotusScript Agents and Script Libraries

I would like a preference to NOT use Option Public in LotusScript Agents and Script Libraries. It forces the developer to make things that can be shared explicitly Public, and promotes thinking abou what should be Public and what should be Private...
about 1 year ago in Domino Designer / LotusScript 2 Needs Review

Provide a "Enable inline view updates" advanced database property

Whilst there is a notes.ini setting (INLINE_VIEW_INDEX) to control which databases are enabled for "inline view updates", I would prefer to see a database property (or similar) to control this. If you have databases inside a folder structure, it w...
almost 4 years ago in Domino Designer 1 Under Consideration

Add a "No-Access" Field type to complement Readers/Authors field types at the document level

Document access rights are generally given on a group list or role basis. However we have frequent situations where a member of a group must be excluded (as an exception) to an individual document. The current design being assume no access unless ...
over 5 years ago in Domino Designer / LotusScript 7 Under Consideration