| |
|
| |
When creating or marking data as public in the Designer, specify the data type using a Model Item Property. Example Below are some examples of Model Item Property data types: xforms:bind nodeset"instance('INSTANCE1')PAGE1ffloat" type"xsd:float" xforms:bind xforms:bind ... |
| |
|
| |
When mapping data, do not crossreference data types. Data should be mapped type to type, for example string to string rather than string to integer. |
| |
|
| |
A Lotus form imported into FileNet is submitted using the SaveLaunchComplete buttons located in the FileNet toolbar. The form itself should contain no submission or cancellation buttons. When creating a form for FileNet using the Designer, do not insert submission or cancellation buttons into ... |
| |
|
| |
When rendering forms, toolbar hotkey accessibility differs between Lotus Forms and FileNet. Lotus Forms accessibility also varies based on the browser. FileNet eForms use Java Script key listeners, which means toolbar hotkeys will always be Ctrl + Alt + key. Lotus Forms forms use the HTML based ... |
| |
|
| |
When a form is created for use in FileNet, use the ufvsettings in the Designer to turn off the menu toolbar. Forms rendered in FileNet use the FileNet toolbar to control form submission. The menu used by Lotus Forms is not required and should be turned off. Example ufvsettings menu ... |
| |
|
| |
The FileNet toolbar does not recognize the ufvsettings used by Lotus Forms. FileNet will not allow a user to submit a form if there are errors on it. If a form designer creates a form using the ufvsettings to allow submission with errors, FileNet will not accept the form. The validity check ... |
| |
|
| |
Set the pagesize property of the globalpage in the Designer when creating forms to ensure they are rendered properly when imported into FileNet. When creating a form in the Designer, ensure you set the pagesize property of the globalpage, located in the Properties view under Appearance to the size ... |
| |
|
| |
A Lotus form must have an extension of .xfdd in order to be imported into FileNet. A form with any other extension cannot be used. The file extension can be changed to .xfdd in one of two ways: When saving the file in the Designer, change the extension from .xfdl to .xfdd . After the file has been ... |
| |
|
| |
When mapping the FResponse to a public data widget in a Lotus form, use a popup list as the corresponding form item. Prior to mapping the FResponse to the popup list, the popup list must be marked as public data in the Designer. The popup list must also be populated with cells containing the set ... |
| |
|
| |
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. |
| |
|
| |
When you create a Lotus form for FileNet P8, you must build page navigation buttons into the form using the Designer. The page navigation options in the FileNet toolbar do not affect Lotus forms. |
| |
|
| |
When importing a Lotus form into FileNet, you must change the document class to ITX Form Template. 1. Browse to the folder where you want to add the form. 2. Click Add Document. 3. Click Change Class. 4. Expand the Lotus Objects tree until Form Template is visible. 5. Select ITX Form Template and ... |
| |
|
| |
You may find that Webform Server forms that contain Japanese fonts do not print correctly. While this does not interfere with the presentation of forms online, it may negatively effect users who wish to print the form for their own records. To avoid this problem, use standard Japanese fonts: MS ... |
| |
|
| |
Webform Server does not properly render Symbol or Wingdings fonts. Not only do some of the symbols display incorrectly, but text and the items containing the text may be sized improperly as well. If you need to include a symbol on your form that is normally contained within the Symbol or Wingdings ... |
| |
|
| |
When Webform Server displays a form on the client computer, the Web browser relies on the fonts installed on that computer. This means that if the appropriate font is not available, the browser will substitute a "closest match" font. This can change the appearance of the form, and may actually ... |
| |
|
| |
Many items point to another item for their values, images, and help messages. These items are considered related. Related items include lists, popups, and comboboxes with cells, buttons and images, or any item linked to a help message. For the best security, when you sign an item, you must sign ... |
| |
|
| |
Scope identifiers, or sids, uniquely identify each item within the XFDL code. Each item on a page should have a different sid to differentiate it from other items on that page. You may use the following characters: az, AZ, 09, dollar sign (), and underscore (). Spaces are not permitted. Each ... |
| |
|
| |
Absolute positioning allows you to precisely place items by setting their x and y coordinates in pixels. Each absolutely positioned item contains its own location and extent information and is therefore independent of other items on the form. On the other hand, items with relative positioning are ... |
| |
|
| |
When using checkvalidformat, set the compute on each page of the form, rather than on the form as a whole. This will improve performance as well as informing users of any incorrectly entered data when they try to leave a page. If checkvalidformat is set to only check when the entire form is ... |
| |
|
| |
Item positioning specifies where each item is displayed on a form. When creating signature filters, always ensure that you secure the positioning information of all of your form items. Even items that you have omitted from your signitems option should have a signoptions or signoptionrefs option ... |
| |
|
| |
If you need custom information to update after the user signs the form, place the information in a custom item rather than in the form or page globals. This allows you to sign form and page global options without freezing the custom option. Why use this practice You should set signatures to sign ... |
| |
|
| |
Set signatures to sign global and page options such as global fonts and background colors. While omit filters automatically sign form and page globals unless they are specifically excluded, it is easy to neglect global options when using a keep filter. However, modification of nonsecure ... |
| |
|
| |
When creating multiple and overlapping signatures, you may be able to use keep instead of omit. If you want a secondary signature to sign the primary signature, you can use keep to sign only the primary signature. For example, you could use this strategy if you wanted a manager to sign an ... |
| |
|
| |
When creating signature filters, use the omit flag rather than the keep flag. Digital signatures with omit flags sign everything in the form except those elements that you specifically exclude. Consistently using this practice prevents you from accidentally excluding items and options that ... |