The majority of E-Form issues have to do with improper configuration of the E-Form or improper import of the E-Form into OnBase.
-
Make sure form fields do not contain extra spaces.
-
Make sure all form field mappings are spelled correctly and use the proper case.
-
When using radio buttons or drop-down lists, set initial state to not selected in the form field properties.
-
Verify that any scripts in the E-Form run without error.
HTML Documents vs. E-Forms
HTML documents and E-Forms can look very similar when displayed in OnBase. However, unlike E-Forms, information entered in an HTML document does not persist. This means that, even if an HTML document has a Save or Submit button, you cannot save information entered into an HTML document.
For more information on why this is, see Limitations When Mapping Form Fields to Keyword Types.
E-Forms That Work Outside of Unity Client Do Not Work Inside Unity Client
As of OnBase 15, the Unity Client renders HTML Forms using the IE 9 Standards Mode. This is not a configurable option, and it can impact how E-forms function within the Unity Client.
If E-forms that work outside of the Unity Client are not functioning correctly within the Unity Client, you may try one of the following methods to have the E-forms function correctly:
-
Update the Windows registry.
-
Include the X-UA-Compatible setting in the E-form itself.
E-forms will support setting the X-UA-Compatible value in meta tags. However, this setting should be thoroughly tested in a testing environment before being implemented system-wide.
Some XML documents are not being displayed correctly.
Beginning in Microsoft .NET Framework 2.0, the XslTransform class was deprecated and replaced with a new XSLT implementation, XslCompiledTransform. This change to the Microsoft .NET Framework enforced stricter standards for how style sheets must be created, and may cause display issues when viewing XML documents in OnBase with style sheets that do not conform to these stricter standards. For example, XML documents may be displayed as shifted down and to the right, or other unexpected behavior may occur when viewing documents with the affected style sheets.
Beginning with OnBase 9.0, this issue has been corrected for all custom and standard style sheets created by Hyland Software, including style sheets for the EDI processors. However, this issue may still affect style sheets created by Hyland Software prior to the release of OnBase 9.0, as well as any style sheets that users have developed on their own, depending on how they were created.
If you are upgrading from OnBase 8.2 or earlier, or if you believe that style sheets created for your OnBase solution are, or may be, affected, please contact Hyland Software's Technical Support for additional information and assistance in resolving this issue.