FormPop-specific settings are located in the Hyland.Web.FormPop element of the Web Server's Web.config file. The only required setting is a data source. You can either configure one in the Web Server's Web.config or pass it along the query string.
FormPop results are displayed using the Web Client.
The following settings are located in the Hyland.Web.FormPop element of the Web Server's Web.config file.
username- Enter the user name to use with default login with FormPop, if you want to use a single user account for access. When enableDefaultLogin is set to true, users can automatically log on to FormPop using the credentials provided in the username and password settings.
password - Enter the password to use with default login with FormPop, if you want to use a single user account for access. When enableDefaultLogin is set to true, users can automatically log on to FormPop using the credentials provided in the username and password settings.
datasource- Enter the name of the data source to use with FormPop. This is a required value.
domain- Enter the domain to log on to if you are using Active Directory authentication.
embedded - Set this to true when you are embedding FormPop results in a custom Web page and you want the FormPop results to be displayed in a frame or iframe within the same browser window. When set to false, FormPop results are opened in a new window.
-
If embedded is set to true and results are not embedded in another Web page, then the address bar and browser toolbars will be displayed when a user accesses the FormPop URL.
-
If FormPop results will not be embedded in Web pages, set embedded to false. The address bar and toolbars will be hidden when FormPop results are displayed.
enableDefaultLogin- Set this to true to have FormPop use the username and password credentials specified in the Hyland.Web.DocPop element. Set this to false to have FormPop either attempt other authentication methods (if they are configured) or prompt the user for credentials.
enableHTTPLogin- Set this to true to pass login credentials to the server on the query string or to post them through an HTML form. Set this to false if FormPop should either attempt other authentication methods (if they are configured) or prompt the user for credentials.
enableAutoLogin- Set this to true to use domain credentials to log on to FormPop automatically. When this is set to false, FormPop either attempts other authentication methods (if they are configured) or prompts the user for credentials. If you enable this setting, ensure that the Web Server is configured for Active Directory authentication. See the Legacy Authentication Methods module reference guide for more information about Active Directory authentication.
Set enableAutoLogin to true if you are using Integration for Single Sign-On. If OnBase is configured for Active Directory or LDAP authentication, but you want to use Single Sign-On with FormPop, set both forceSSOAutoLoginOverDomain and FormPop's enableAutoLogin setting to true. For more information about Integration for Single Sign-On, see the Legacy Authentication Methods module reference guide.
enableHTTPDataSource- Set this to true to pass the data source on the query string. Set to false to use the FormPop data source in the Web Server's Web.config.
enableChecksum- If set to true, a checksum value will be added to the URL query string. To enable checksums, you are also required to enter a checksum key value in the FormPop checksum setting, which is used to create the checksum value in the URL. When a user attempts to retrieve a document using the URL, FormPop compares the checksum in the query string to the expected checksum. If the values match, the document is displayed. If the values do not match, the user is presented with an error. This is to prevent users from modifying query strings and accessing documents they should not access. If set to false, no checksum is created.
checksum- Enter the unique string value used as a key for external, dynamic checksum creation. This string value should not be well known. The checksum setting applies only when enableChecksum is set to true and an external automated process is being used to dynamically generate FormPop links.
Configuration of this setting is required for checksum creation and validation.
-
The Web Server web.config file also has an enableChecksum setting within the <Hyland.Web.DocPop> node that must be set to true. You must also set the checksum setting to the appropriate value within that node.
-
The Application Server web.config file also contains a Pop integration checksum setting: ChecksumKey. This setting is used for checksum generation when the docID is used from outside of the Web Client solution (for example, in Workflow notifications). If you use this feature, the ChecksumKey value in the Application Server web.config file must match the checksum value in the Hyland.Web.FormPop element of the Web Server web.config file. For more information about checksum generation, please refer to the Hyland SDK.
-
If you are using the Workflow action Med - Send HL7 Message, the Hyland.Web.FormPop checksum value should be empty. If an external process will generate the FormPop URLs and you want to use checksums, then a separate virtual directory for FormPop should be configured.
enableCoreQueryAPILicense- This setting requires OnBase to be licensed for Core Query API (Retrievals Per Hour). Set this setting to true if you want users to consume Core Query API licenses when using FormPop. Core Query API licenses help prevent the unnecessary consumption of Concurrent Client licenses. When this setting is set to true, a Core Query API license is consumed as soon as a user logs on to FormPop and is released immediately after the user logs off. When the enableCoreQueryAPILicense setting is set to false, a Concurrent Client license is used.
Core Query API licenses are only available for external users.
AutoDisplayOneDocument- Set this setting to true to always display only the viewer for FormPop queries that return a single result. When this setting is set to false, FormPop displays both the hit list and the viewer for queries that return a single result. This behavior can be overridden by the viewerOnlyForSingle variable in the FormPop query string. The viewerOnlyForSingle variable has no effect when AutoDisplayOneDocument is set to true.