IBM Lotus should remove the 32K limit size on text fields and view colums. There should be no artifial limit on this
It's always a tedious job to find a field given its name especially when the form was designed by someone else and even so when it's a complex form.
An intuitive way can be to sort the fields alphabetically in the object list (also display the fields and other elements ...
Provide the ability to check off a box on the field properties box that indicates that the field is required. Also provide a UI clue that the field is in fact required. See screenshot.
Why can the user enter some non-number characters in a number field? Why isn´t this blocked just in time? It should be possible
Only when he save the form/document he will get a "cannot convert text to number" error message and this produces some user-frustrations.
What I would ...
In workflow applications we often need to save Fully Qualified names in Readers/Authors/Names type fields in order to reduce name ambiguities e.g. “Joe User/dev/demo” or “Joe User/adm/demo” however for display purposes people like to have “Joe User” only instead of complete fully qualified ...
It would be great if it was possible to copy attributes of a selected element in Designer and "paint" it onto other elements, much the way Format Painter does in Office products.
I'm thinking selecting a field and grabbing the "Computed for Display" property and being able to "paint" ...
The Field class in LotusScript only contains events. It would be great if it contained properties like Value (read/write) to make it easier to manipulate in the events. For example, if I want to handle the OnChange event in the client, I can use LotusScript but I have to write a ...
can we have an visual indicator on a field in designer which shows us HOW the data for a field is being generated?
something like E for editable, CFD for computed for display, CWC for computed when composed etcetera.
nowadays we have an indicator which shows us what ...
I think there are similar ideas for this but I'm not sure its totally covered....
Basically when you use the type-ahead on the Notes 8 To email field - you find it very useful very quickly.
So it'd be nice to have something similar for standard notes dialog ...
Make it possible to change the font color or background color of a field using @Formula.
You could for example warn the user if a required field is empty by changing the backgroundcolor,
red := 255:150:150;
black := 0:0:0;
@If( fieldvalue=""; red:black )
I would like to see a property of a field that can be used to set it's 'plain language' label.
It could be accessed via @ThisLabel or by item.label
This would be useful in any formula/script that needs to display a plain language description to the user, i.e. validation messages.......
Fields that involve a specific control for data entry, e.g. radio buttons, check boxes, combo boxes and dates also display the same way in read mode (although the control element may be greyed out). This is untidy and can be confusing to end users and so developers typically pair these ...
When I write code in a field event that give me a source parameter that represents the current field I would like to be able to get the current value of the field by simply doing this
and to return the previous value of the field (if any) ...
Scenario: If you have many hidden fields on your form and you want to change the properties of any hidden field, often it becomes really very difficult to physically locate that field to change the properties. This becomes more difficult if you have couple of subforms and you don't know ...
When adding aliases to a Person Document, many is the time when a errant space is added to a line. This causes mail routing issues as well as authentication problems. Also, this field allows all characters to be included in a short name (example: apostrophe). If the character is being ...
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...
just like available as in the column options....
It would be nice if there could be some type of indication on the field, like there is for Authors/Readers, when you have the field, on standard forms, as computed, computed for display, or computed when composed and on xpages as Visible/Not Visible, Read Only/Not Read Only, and Disabled/Not Disabled....
When input enable formula returns false the text on the field becomes tan (even in read mode). It makes the text hard to read even on white background. The selected text color should remain at least in read mode or there should be possibility to select the text color when input ...
Add a field to a chat where we can put the subject of the chat. I think You are also faced with the problem to find the right chat in the history. If there is a subject it is easy to find or remember. If it has ...
Just very hard to read all the properties without scrolling. copying them to compare them is even more difficult. A simple 'copy properties to clipboard' would be an improvement.
When you have fields that have a Formula that evaluate at True in the InputEnable Field event, this field has a gray background with dark gray text in it. This is really hard for the user to read it.
Please Please allow to select /copy a computed field text on Form. Currently we don't have any option to copy from the front end until if we go to the document properties and copy. However if field is of type computedForDisplay, we don't have even this option.
Imagine that the field properties contains "Remember old data" checkboxes with several options;
Since this is a field property, Notes will create a special field behind the scenes, for example on the format;
$History<original field name>...
Very are lacking the context menu with items:
- Select All. Also wanted to work in the field corresponding to the key combination Ctrl+A.
Did you ever open a document and wonder where a specific field is used? Of course, you can open a form in Designer, but then you don't see the value. So you'll have to go back to the client, look at that spot where you find your field and see ...
When you make a new DialogList type of field and select option "Use view dialog for choices", the view selection list below is way too small. It shows only few letters from the beginning of the view name which, in some cases, makes it hard to select the right view ...
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 ...
This would be an editable field that would not be saved. Essentially it's an area where I can edit some data and then have it parsed or in some way processed but the field itself would not be saved. It would exist only when the document is opened for editing.
I would love it if while creating a view I could select a form and have notes create a view with all of the fields in that form.
This would be extremely useful when I am creating a view with many fields. Especially when that view is specifically used for importing data. Thank You.
Current field limitations (for 4byte unicode ~127 symbols) are too small.
My Notes version is:
Revision 20091002.1006 (Release 8.5.1 FP2)
It runs on Windows. I replied a mail, dragged a file to the mail. If I moved the mouse over a field e.g. To/cc/Subject in the history part of the mail body and ...
Having just spent an age in maintenance mode tracking down a dodgy numeric field in a MASSIVE form, a simple suggestion for the Notes team is that if a numeric field is empty (i.e. in doc properties its value is ""), treat that as being the same as zero for ...
Whenever I insert/modify a field on a form, I would like to choose the field type (text, number, etc) from a sorted list,
not like the usual field type list you can see even in R8 (see my attachment).
Maybe some Notes programmers are now used to that list, ...
Hows about a new field for designer that is a sequence number (similar to an identity field on sql server/db2 etc).
So you could add a new field to a form and select datatype 'Sequence Number'. It auto-generates a sequence number in this field for every document that is ...