Running the Hyland Electronic Signature Service Database Configuration Tool - Integration for Adobe Sign - Foundation 23.1 - Foundation 23.1 - Ready - OnBase - external

Integration for Adobe Sign

Integration for Adobe Sign
Foundation 23.1

You must run the Hyland Electronic Signature Service Database Configuration Tool (also known as Hyland-eSignature-Config) to update your database with the required schemas and tables.

CAUTION: Be very careful when updating the JSON configuration files. If a copy exists with a similar naming scheme (for example, appsettings.backup.json), and that copy is not deleted, the incorrect JSON configuration file may be used. Configuration files are read in lexicographic order, or the order in which they are loaded. This means that the last file saved is the first file loaded. The order of precedence for the loading of the configuration sources is: 1) appsettings.json file, 2) appsettings.{AltName}.json file, 3) Key-per-file directories, 4) Environment variables, and 5) Command Line arguments. As a result, if a JSON configuration file is configured with an alternate name, and is the most recently saved version of the JSON configuration file, the file with the alternate name will take precedence, which causes major errors during login.

See one of the following sections for information on running this configuration tool for a SQL or Oracle environment: