The following best practices are related to E-Forms and user forms.
-
Limit the number of fields on an E-Form. E-Forms are a very powerful tool which make it is easy to expand the amount of information stored on the form. The more fields on the form, the longer it takes to load.
-
Perform data validation on the E-Form rather than with Workflow logic. Performing data validation should be handled on the E-Form with simple scripting rather than performing the validation within OnBase Workflow. The scripting runs on the client and is lightweight compared to performing the similar logic behind Workflow rules and actions (which may update the database and add overhead to perform the logic).
-
Limit the Number of HTML Fields on the driving document if it is an E-Form. When the document driving a Workflow process is an E-Form with many HTML fields, loading the document can directly impact performance as OnBase must parse the HTML fields and extract the correct field values from post data stored in the Disk Groups.
-
Exchange information between user forms and Workflow using the property bag. In OnBase versions 7.2 and higher, user form fields can be mapped to property bag values using the following naming convention: OB_WFPROPERTY_PropertyName_InstanceNumber. This allows for an efficient exchange of information between Workflow Logic and user forms using the property bag. Using the property bag in this way avoids database processing overhead.
-
Always appropriately configure buttons. Default submit button functionality is processed as “OBBtn_Yes” when an E-Form is used in Workflow and a button function is not specified otherwise. Prior to OnBase 9.2, buttons that were not configured specifically as submission buttons would function as cancel buttons. In 9.2 and beyond, you must configure appropriate cancel buttons, as button not specifically configured will be processed as a “yes” submit button.