Workflow Interaction - E-Forms - English - Foundation 22.1 - OnBase - Premier - external - Standard - Premier - Standard

E-Forms

Platform
OnBase
Product
E-Forms
Release
Foundation 22.1
License
Premier
Standard

Limit the Number of HTML Fields on the driving document in a Workflow life cycle if it is an E-Form. When the driving document is an E-Form with many HTML fields, loading the driving document if it is an E-Form with many fields 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.

If you have a E-Form in a system that you want to import into another system, you can create a Workflow life cycle containing that E-Form. You can export the Workflow life cycle containing the E-Form and upon importing the Workflow life cycle, the E-Form, the associated Document Type, and all associated Keyword Types are imported.

Perform data validation on the 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).

Always appropriately configure buttons. Default submit button functionality is processed as a cancel button when an E-Form is used in Workflow and a button function is not specified using oBBtn_ syntax.