Front Office Scanning Properties - Signature Deficiencies for Epic - Foundation 23.1 - Foundation 23.1 - Ready - OnBase - external

Signature Deficiencies for Epic

Platform
OnBase
Product
Signature Deficiencies for Epic
Release
Foundation 23.1
License

The following table outlines configuration properties available for command line installations of the Front Office Scanning integration.

Property ID

Description

EPIC_OVERWRITECONFIGFILE

Indicates whether the file specified in the EPIC_CONFIG_SOURCE_PATH directory will be copied to the component's installation directory.

Set this property's value to 1 to allow the specified configuration file to be copied to the installation directories. Otherwise, leave the property empty.

EPIC_CONFIG_SOURCE_PATH

Specifies the full path to a pre-configured EpicIntegrations.config file. When this property is specified and EPIC_OVERWRITECONFIGFILE is set to 1, the specified configuration file is copied to the installation directory.

EPIC_FOS_CONFIG_NETWORK_STORE_OPTION

Indicates whether the EPIC_FOS_CONFIG_NETWORK_LOCATION path will be set as the EpicConfigFile value in the Windows registry.

Set this property's value to 1 to use the specified path as the EpicConfigFile registry value. Otherwise, leave the property empty.

EPIC_FOS_CONFIG_NETWORK_LOCATION

Specifies the full path to a shared EPICFOSCONFIG.xml file. When this property is specified and EPIC_FOS_CONFIG_NETWORK_STORE_OPTION is set to 1, the installer creates a string value named EpicConfigFile in the following registry location:

HKLM\SOFTWARE\Hyland\Front Office Scanning1

The specified network location becomes the value for the EpicConfigFile registry key.

Set this property to the network location where EpicFOSConfig.xml is accessible. Otherwise, leave the property empty.

FOS_LOCAL_DATASET_PATH

Specifies the local path where the dataset XML files for Front Office Scanning are located. The specified path is created on the installation machine. This value is also written to the <SharePath> element in EPICFOSCONFIG.xml.

For example: FOS_LOCAL_DATASET_PATH="C:\EPICFOS\Datasets"

Note:

This value must be a path local to the installation machine in order for the installer to create it. Network (UNC) paths must be created by a network administrator.

If no value is entered, the value is not valid, or the property is not included at all, then no path is created and EPICFOSCONFIG.xml is not updated.

1 This assumes that Registry Editor is opened using C:\Windows\SysWow64\regedt32.exe on a 64-bit system. If you open Registry Editor using C:\Windows\system32\regedt32.exe on a 64-bit system, then the registry location is HKLM\SOFTWARE\Wow6432Node\Hyland\Front Office Scanning.