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
Design guidelines for developing Notes Client and Nomad applications
The development of applications for the Notes Client is very fast and easy, in addition to having good features such as security and offline replication, the problem is that there are few visual resources to modernize the look of old applications,...
Update Lotus Script Editor for legacy Notes design
When editing lotus script for form or view event, we have to use the interface like legacy notes designer. Please update it like script library editer.
I would like to use pop-up help and my classes with type-ahead in the legacy design.
Add InternetAddress and ShortName as new parameters for renameNotesUser method in AdministrationProcess class
Renaiming a person using the Admin Client, the old ShortName and InternetAddress is moved to the FullName item in the person document. When you rename a user programmatically with LS or Java, there is no method available with the same functionalli...
Currently we're limited to 32 characters in a field name when creating them in Domino Designer.This is sometimes limiting in regards to describing field names. If possible, it would be nice to be able to have longer field names.
In addition to restriction for field size, it is necessary to remove shameful restriction for data size, received by dbLookup. I so think! Periodically happens it is impossible to use too much key word in the choice of field values.
Lotus Script stack trace function instead of the unsupported Lsi_info(14)
Please add a regular and offical function to get a Lotus Script stack trace instead of the buggy and unsupported function Lsi_info(14).
Mark Reiser, sirius-net GmbH
LotusScript, Script, LS, LSI, Lsi_info
We nowadays can use our Notes application on mobile phones, tablets and other devices with smaller screens. That's why HCl allowed us developers to take care of the screen size in views and forms. But in the Notes Outline the most important option...
Don't always use an idea's vote count to prioritise work
Just because an idea has a low vote count doesn't make it less urgent. For example, "drag & drop support to re-order LS functions & subs" (DDXP-I-363) is more useful than "Show LotusScript variables that are declared, but not used" (IDEAAD...