Administrators must still perform all of the normal administrative tasks, such as creating form data entry templates, creating document and workflow policies, and creating workflow definitions. However, there are some minor differences in the results of those tasks or how some of those tasks are performed.
Saving form data
There is a difference betweenIBM
Forms and FileNet
eForms in how form data is saved when users complete and store a form. When a user saves a FileNet
eForm, only the form data is stored. If the form needs to be reopened, FileNet
matches the form data to the correct form template.
However, when a user saves an IBM
form, user data, form logic, and form presentation are not separated. Form data may be extracted and stored separately, but a complete copy of the entire form is preserved. This helps to ensure the legal non-repudiation of these forms by maintaining the context in which the user signed the form.
Mapping form elements to workflow tasks
When you map FileNet
eForms elements to data fields, the form elements are identified using their ids. As of release 126.96.36.199 you can specify a name instead of using the form element's id. When you map IBM
Forms elements to data fields, they are presented somewhat differently. Elements are not identified by their id. Instead, they are identified by a formatted version of the XPath reference. For example, an XPath of instance('Instance1')/strings/string1
will appear as Instance1_strings_string1
when viewed in FileNet
. Administrators should therefore use underscores with caution for naming IBM
Parent topic: Developing forms and applications