An alternative to a user form that is accessed via a UNC path is to use an HTML form via URL. This configuration is only supported for Core-based user interfaces. Follow these steps to configure a user form that is accessible via URL:
The form is configured for use in the same way as a standard user form, however, OnBase must pass an “obTarget” parameter to the form. This can be accomplished by embedding script in the form to retrieve this parameter and set the form's “action” attribute. Whenever the user submits a form, the form needs to be directed back to the Workflow interface for further processing. The form must programmatically retrieve the value of a querystring parameter called ‘obTarget' and set the ‘action' attribute of the form to this value. The following is an example using JavaScript in the HTML page's OnLoad event:
document.forms.item(0).action = decodeURIComponent(window.location.search.split("obTarget=")[1]);
E-Forms are also utilized in Workflow when using certain form actions. These differ from user forms in that they must be imported into OnBase and the system must be licensed for the E-Forms module.