The following are limitations of Unity Forms:
-
WorkView objects cannot be created from a Unity Form in Workflow.
-
Unity Forms are not supported in the OnBase Client.
-
When sending Unity Forms using the Distribution Service, section and page security configured on a Unity Form is not respected. The entire form is sent regardless of the security settings on the form.
-
When sending a Unity Form using the Distribution Service or via the right-click Send to option, page tabs are not displayed in the form. The contents of the form is displayed laterally.
-
When using Send to | File in a client and selecting Native Format, attachment controls, images, drawing controls, and signature controls are not supported and do not function in this context. Choosing Default/TIFF Format will display these controls.
-
When using Send to | File in a client and selecting Native Format, Unity Forms may not have all of the same functionality they have when inside the OnBase system. For example, when not connected to the OnBase system, custom actions may not function as they would within the system.
-
You cannot use Send to | File in the OnBase Client for Unity Forms
-
Printing Unity Forms from a remote/network print queue is not supported. (These are queues configured as Network Print Queue or Print Cluster Queue in the Configuration module.)
-
Workflow forms do not support printing.
-
Print formats are not respected when printing Unity Forms.
-
When using the Unity Client, if a Unity Form's information exceeds an 8.5” x 11” space, the information outside of this page size is not included on the printed page.
-
The following Keyword Type configurations are not supported on Unity Forms: hidden, security masking, encrypted, and Specific Currency data type.