This version of OnBase has additional Upgrade Considerations when upgrading to it from one of the following earlier versions:
-
Any pre-Foundation releases prior to 18 SP 2
-
Foundation EP1
-
Foundation EP2
-
Foundation EP3, prior to Patch 23
-
Foundation EP4
If your solution depends on using checksums for validating Pop integration URLs, you are now required to configure a unique checksum key value, which is used to create the checksum value added to the URL.
If your solution did not previously use a unique string value to create checksum values, you must take the following actions in order for any previously created Pop integration URLs to validate:
-
In the Web Server web.config file:
-
Enter a unique checksum key value in the checksum setting for the Pop integration being used (for example, the checksum setting within the Hyland.Web.DocPop element).
-
Set the EnableLegacyChecksumFallback setting to true.
-
Setting the EnableLegacyChecksumFallback setting to true should be considered a temporary method of validating legacy checksums until you can recreate and replace the Pop integration URLs using the unique string value as the checksum key.
In addition to these actions, if your solution also uses an Application Server that generates Pop integration URLs outside of the Web Server, you must also take the following action to ensure successful checksum generation and validation:
-
In the Application Server web.config file, enter the same unique checksum key value in the ChecksumKey setting within the Hyland.Web.AppServerPop element. The values in the Application Server ChecksumKey setting and Web Server checksum setting must match exactly.
If your solution was already using a unique string value to create checksum values, any Pop integration URLs that were previously created will continue to validate with no additional action needed.