|
| 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 ... |