| |
|
| |
Defines if an object is drawn on a form. If it is not, it takes up no space on the form. |
| |
|
| |
Defines the direction of plain and rich text in items. This is typically used when working with bidirectional languages, such as Arabic and Hebrew. |
| |
|
| |
Defines the direction of text on a form. This option is typically used for bidirectional languages, such as Arabic and Hebrew. |
| |
|
| |
Determines whether Arabic (European) numerals or national numerals are used. This option is typically used for bidirectional languages, such as Arabic and Hebrew. |
| |
|
| |
Defines the order in which the text is stored in memory. This option is typically used for bidirectional languages, such as Arabic and Hebrew. |
| |
|
| |
In this example, a action is set so that if one field in the group is completed, the user must fill in all fields. An IfThenElse action is used on each of the fields so if one of the fields is filled in, the remaining fields become mandatory. |
| |
|
| |
Actions are used to limit completion to one field in a group of fields. In the example below, each entry field is mandatory until the user completes one of them. After that, the other entry fields become inactive. |
| |
|
| |
This example uses an IfThenElse action to require completion of at least one field in a group of fields. Each entry field is mandatory until the user completes one of them. After that, the other fields become optional. |
| |
|
| |
This example uses an IfThenElse action to require completion of at least one field in a group of fields. Each entry field is mandatory until the user completes one of them. After that, the other fields become optional. |
| |
|
| |
Actions are used to limit completion to one field in a group of fields. In the example below, each entry field is mandatory until the user completes one of them. After that, the other entry fields become inactive. |
| |
|
| |
In this example, a action is set so that if one field in the group is completed, the user must fill in all fields. An IfThenElse action is used on each of the fields so if one of the fields is filled in, the remaining fields become mandatory. |
| |
|
| |
You can format an email address field so it only accepts a valid email address format or an email address from a specific domain. |
| |
|
| |
The FileNet workflow definition and workflow policy should not be relied upon to control whether an item in a Lotus Forms form is modifiable. If there are items in your form that are required to be readonly, set the item's readonly property when creating the form in the Designer. |
| |
|
| |
You should avoid using writeonly fields in your forms as much as possible. Writeonly fields do not display the text typed by the user. Instead, these fields replace each character with an asterisk. They are frequently used to allow users to enter sensitive information, such as passwords. ... |
| |
|
| |
"Mirroring" allows you to copy data between form items, such as two fields. This means that both items will always contain the same value. Generally, this is most useful in forms with multiple pages that use common data. For example, you may have a form that requires the user to provide their ... |
| |
|
| |
Postal codes (also known as post codes or ZIP codes) are a series of characters appended to a postal address for the purpose of sorting mail. Many countries use 4, 5, 6, or 9 digit numeric strings, while others use both numbers and letters. In your form, you may want to accept a wide range of ... |
| |
|
| |
Phone number fields come in a number of formats. Some locales may include periods, others dashes, while others include parentheses. In your form, you may want to accept a wide range of phone number formats, force a particular phone number format, or ensure that users can only input numbers and not ... |
| |
|
| |
There are several miscellaneous form design issues that you should be aware of when creating forms for Webform Server. If you draw a line that overlaps a combobox or popup, the Viewer will show the line on top. However, Webform Server will show the combobox or popup on top, which will cause a ... |
| |
|
| |
You should not use rich text formatted fields in Webform Server forms as most browsers cannot properly display the resulting rich text. Typically, any rich text formatting used to modify the field’s text is stripped out, leaving only plain text. As a result, we recommend modifying text using XFDL ... |
| |
|
| |
When creating a form for use in Webform Server, you cannot limit the amount of text the user can enter by setting the size of the field. In some cases, form designers may rely on the size of a field to limit the amount of text the user can enter. For example, a multiline field with a scrollhoriz ... |
| |
|
| |
Do not require users to enter a large amount of text within a single field. Text fields can support up to 500K of text. If the user tries to insert more than 500K of text (about 7,500 lines in a 60character wide field), the text will be truncated at the 500K mark. If you expect users to enter ... |