|
|
In the design client, with a list of all forms, select all or some of them, and be able to change all the form properties (specifically background images and colours, action bar properties, include in various menus etc.)
|
|
|
A field that is computed for display and located in the header seems not to be available in the rest (body) of the form.
Computed fields however are.
|
|
|
We have
@IsDocBeingEdited
@IsDocBeingMailed
@IsDocBeingRecalculated
@IsDocBeingSaved
@IsDocBeingLoaded
Why can't we have @IsDocBeingPrinted
No problem to trade it for @IsDocBeingLoaded
|
|
|
Hello,
Not an entire Db template. Just a list of common sample forms to choose from to get you started. The list could also include other previously created forms on that server. I was working with Adobe Live Cycle for the first time and when you select a new form to create
|
|
|
I wanted to make a universal formula and put it in the Shared Computed For Display (CFD) Field $hf_WindowTitle (inherit to all databases), and that it was calculated at the opening of the Form.
Code:
@If(@NoteID!="NT00000000";
@If(Form!="DeletedDocument";
$hf_WindowTitleDoc;
"(Deleted document)");
"New document")
$hf_WindowTitleDoc - CFD-field that contains
|
|
|
When creating a new View, you can choose one of which will be produced inheritance. Exactly the same wants and the Form / Subform, since we have a very long time to configure all options again:
- Action Bar and its properties;
- basic properties of
|
|
|
The option to display an action button as a menu separator has only effect for sub-actions.
I find it hard to make it clear that certain actionbuttons can be considered as grouped. A horizontal menu separator could make this more clear.
like in:
Close Publish Withdraw | Set Fontstyle Attach File Append Link
|
|
|
If we could extend this form property (include in menu) to be available when right-click a database from the workspace a lot of times we avoid that in a default frame a view is being loaded from which the index will be rebuilt first.
Okej, this is inproper application design but
|
|
|
Currently, when Domino presents a form to a web browser, the FORM tag only contains the NAME attribute. Many JavaScript frameworks have issues accessing the form using the name attribute, especially in Firefox. it would be much better if the ID attribute was also set. I know this can be done
|
|
|
We have the option to add a header section to a Notes Form.
It would be really nice to be able to add a similar secton for a footer to the Form. Then I could select as option: 'always show footer' Y/N.
By this way I could easily add some legal text
|
|
|
I wish Designer would have a layout grid for better/easier layout of forms. This would allow for easier alignment of fields and text,and thus, better looking forms. There are layout regions, but the items you can put in it are limited.
I use tables for layout, but this can cause lots
|
|
|
Add an Is Summary checkbox to the Field Properties Dialog box in Domino Designer.
By default the value would be true.
Deselecting the option would mean that NotesItems created via the field would not have the Summary property set.
The most important benefit of this option would be that data entered into such
|
|
|
Support of groupboxes. There are workarounds using layers but yeah these are workarounds...
|
|
|
Make available an option to never save a form on the form properties so that whether the form is closed via a button or the ' X ' for the database tab you don't have to worry about coming up with some ingeniuos programming to prevent the user from being
|
|
|
When you put a button above e.g. a RichText field, to perform a simple action as 'EditInsertFileAttachment', the user would like it to insert the attachment where the cursor is at that moment.
Currenty when clicking a button, this button get's the focus, and you don't know where the cursor/focus was
|
|
|
A lot of websites have a menubar/actionbar below the banner/logo/title. This gives the user a better experience, and looks nicer too. Notes currently has the actionbar always at the top.
I propose to have a setting in the actionbar to define/compute an optional subform to put above the actionbar.
When scrolling is
|
|
|
To avoid user errors, give form designers control what types of addressbook entries will be selectable for a given Names/Readers/Authors field. E.g. to define that for a SendTo field should appear only entries which are mailable; in a field which controls document access should appear only entries which can control
|
|
|
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" that property
|
|
|
Add a way to automatically enable "CAPTCHA" for a web form in order to stop form spammers from auto posting forms against that neat new form created. Ideally it would allow the developer to specify either images/questions to present to the end user along with customized error messages if an invalid answer was
|
|
|
When you try to select who can Read/Author, if you want to select a ROLE from the list, you have to scroll through the list which may be very long as it includes users, groups and roles. It would be nice to have a way to edit the list from
|