|
|
If you've enabled any of the options under "instant corrections" in your Notes Client spell check preferences then these are applied when you work on a form in the Designer Client too. The most annoying of these is "Capitalize first letter of every sentence" - a feature you really don't
|
|
|
I have been struggling this for now. Can we have a dojo control equivalent for NotesUIScheduler just like we have it in our Notes client where we just need to pass additional parameters to check the availability of room/resources.
Similarly if we want to levergae this feature in XPages (or
|
|
|
Whenever you build a form in a place with rooms you have to rebuild that form in each and every room. Why can't there be an option to "inherrit forms into all rooms" option that will automatically inherrit the form into each room? This makes it easier to maintain as you
|
|
|
When you build forms into quickr you have to build/add them to each and every place and room you want to use them. This makes it very hard to maintain as any change requires updates to multiple places/rooms.
It would be better if you could for instance have a central
|
|
|
It would be really handy to allow users to search for forms and then have them be able to create a document from the form using a link in the search results.
|
|
|
I would like to see that it would be easier to control the alignment of elements on a form. There are alreay a number of techniques, but many of them are so superficial and sometimes very hard to modify later.
A sample: I have a table cell with an editable text
|
|
|
The view and form design elements are the single most used design elements within Notes. Even with Xpages I expect it will be a long time before it gets even close to have the same level of adoption/use. For the next major release of Notes (9.0?) I would like to
|
|
|
When viewing the Objects list for a form in designer, instead of just fieldname (Field), tell me what kind of field "(Field)" is.
e.g. (Field - Text)
|
|
|
The ACL has a couple of valuable check boxes available for Reader and below: "Read public documents" and "Write public documents"
However, we just discovered that there's no option for "Create public documents"
Here's where we would use it.
We define a group of people that have Reader access.
The form's query open event
|
|
|
Short description: Refresh to an existing Redbook. This IBM Redbook describes the features and functionality of Lotus Forms and each of its component products. After introducing the products and providing an overview of features and functionality, we discuss the underlying product architecture and address the concept of integration.
Detailed Description: This
|
|
|
Lotus Notes designer is good .. you can get stuff done way quicker due to all the options you have .. often just a check box. The down side is that sometimes you lose that bit of flexibility.
Like when you want to refresh fields on keyword change .. great when
|
|
|
I guess this is more a fix than an idea, but never late then never:
If I select a color for a checkbox field it is not supported (mines become standard black)
Bold and italic is supported...
|
|
|
This is long overdue: The ability to programmatically expand and collapse sections. It's a difficult limitation to work around.
|
|
|
Right now there is NO way to use an API or exposed program method to write an agent which will check or uncheck the replication advanced options which would prevent design and form updates.
This is useful when doing a slow progressive migration or upgrade from r5 to r7 in this
|
|
|
Notes (Hotspot) buttons are pretty dull.
The option to use an icon/image could improve the user experience.
The support for 'Notes client only' would already be an improvement.
http://www.codestore.net/store.nsf/unid/BLOG-20040712?OpenDocument
|
|
|
for the Notes client I sometimes think it is strange that you can present a view within a frame, but as soon as you open a document it breaks out of the frame and is presented in new tab window.
if you compare it to the web at least you have
|
|
|
I worked recently on an application where people could subscribe to a Newsletter, which was basically a NotesDocumentCollection transformed as a NotesNewsLetter.
Some problems I faced where:
- you can only specify 1 SubjectItemName. Multiple options/fields presented in a nice table would be much more nice.
- when creating the final document to be send I
|
|
|
Provide a helper/wizard to create a view based one or more forms.
While having one or more forms highlighted I can click a button to create a view that will show documents created with these forms. When I open this view creation wiazard I can further refine which forms to base
|
|
|
Workflow capabilities within Quickr for the "typical" end-user are limited to one type of sequential/concurrent workflow per form. I would like to have the Quickr superusers be able to have different workflows triggered from a form based on the values in specific fields within the form.
|
|
|
Currently you can create easily create forms with fixed fields in Quickr. I would like to create forms where you could vary the fields based on the value of the preceeding field. For example, if I am reporting sofftware and hardware issues using a form, today I have to create
|